J-5_Sec_J_Attachment_5_DRAFT_PWS.pdf

CONTRACTED AIR SERVICES (CAS)

FLEET FIGHTER JET SERVICES

PERFORMANCE BASED WORK STATEMENT (PBWS)

DRAFT Working Copy as of 2 October 2019

FLEET FIGHTER JET SERVICES Draft PBWS

1.0 SCOPE

1.1 Naval Air Systems Command (NAVAIR) Program Manager Air (PMA) 226 Specialized and Proven Aircraft Program Office, Contracted Air Services (CAS) Integrated Product Team (IPT) has a requirement for Fighter Jet Services to provide contractor owned and contractor operated (COCO) aircraft to the Department of the Navy (DoN) for Fleet Training and Exercise Support for a wide variety of airborne threat simulation capabilities to train aircraft squadron aircrew and shipboard system operators on how to counter potential enemy advanced airborne threats, tactics, Electronic Warfare (EW) to include Electronic Warfare Support (ES), Electronic Attack (EA), and Electronic Protection (EP) operations; and, Acquisition Program Testing and Evaluation (T&E) Support. The Contractor will provide support in a variety of venues, from basic “schoolhouse” Air Intercept Control (AIC) training to large multi-national exercises or small, single unit training exercises. Exercises may include target tow.

Additionally, an F-35 Production Support option is being included for provision of airborne chase during aircraft first flights and product assurance flights for F-35 production. Locations include multiple continental United States (CONUS) sites and foreign or remote operating bases outside continental United States (OCONUS) (Ref: Appendix C). Aircraft will operate from designated or home bases on the East Coast, West Coast, Middle Pacific (MIDPAC) Hawaii, Western Pacific (WESTPAC) Japan and from any operating site world-wide during periods of support and/or deployment. Other customers for CAS, under this contract, may include other Department of Defense (DoD) agencies and services, non-DoD Government agencies, and Foreign Military Sales (FMS) customers.

1.2 For clarity, all references to the Federal Aviation Regulation in this Performance Based Work Statement (PBWS) will be by reference to Title 14, Code of Federal Regulations (CFR) and abbreviated with the acronym “14 CFR”. All references to the Federal Acquisition Regulation will be abbreviated with the acronym “FAR”. When the requirements of this PBWS exceed the minimum requirements of 14 CFR, this PBWS takes precedence.

Definitions contained in 14 CFR Part 1, in which are derived from the 14 CFR and Defense Contract Management Agency (DCMA) Instruction (INST) 8210.1C Change 1, apply to all situations and conditions relating to flight operations, aircraft maintenance, and flight crew certifications and qualifications.

2.0 APPLICABLE DOCUMENTS

The Contractor shall utilize and adhere to the following documents, and updates or revisions to them, in satisfying the performance requirements of this PBWS.

(a) CFR Title 14, Aeronautics and Space (14 CFR)

(b) Federal Acquisition Regulations (FAR)

(c) Defense Contract Management Agency (DCMA) INST 8210.1C Change 1, April 5, 2017, Contractor's Flight and Ground Operations and Naval Air Systems Command (NAVAIR) Instruction (NAVAIRINST) 3710.1G Change 1

(d) Federal Aviation Administration (FAA) Advisory Circular (AC) 91-91 Maintaining Public Aircraft

(e) NAVAIR Instruction (NAVAIRINST) 13034.1F - NAVAIR Airworthiness and Cybersafe Process Manual

(f) DoD 4140.25-M, Volume 2, "DoD Management of Bulk Petroleum Products, Natural Gas, and Coal, Chapter 16 Government Fuel Card Program Management Office DoD Fleet Card, Air Card and Sea Card

(g) United States Code (USC) Title 49 Part 830 Notification and Reporting of Aircraft Accidents or Incidents and Overdue Aircraft, and Preservation of Aircraft Wreckage, Mail, Cargo and Records

(h) 32 CFR 766 - Use of DON Aviation Facilities by Civil Aircraft

(i) Air Force Instruction (AFI) 10-1001 Civil Aircraft Landing Permits

(j) AFI 10-1002 Agreement for Civil Aircraft Use of Air Force Airfields

(k) FAA AC 00-1.1B Public Aircraft Operations (PAO)

(l) DD Form 1348-1A DoD Single Line Item Requisition System Document Requisition and Invoice/Shipping Document Jan 2016

(m) DCMA Instruction 8210.2, Chapter 4: Flight Operations

(n) DoD Instruction 4715.4 Environmental Compliance at Installations Outside the United States

(o) DoD Manual (DoDM) 5200.01 (DoD Information Security Program: Controlled Unclassified Information (CUI)) Vol. 4 (enclosure 3 pages 11-18)

(p) DoD Instruction (DoDI) 5230.24 (Distribution Statements on Technical Documents)

(q) Homeland Security Presidential Directive-12 (HSPD-12) August 27, 2004

(r) DoD 5220.22-M National Industrial Security Program Operating Manual (NISPOM)

(s) Secretary of the Navy (SECNAV) M-5510.36 October 6, 2006

(t) National Security Decision Directive (NSDD) 298 Operations Security (OPSEC) Directive

3.0 GENERAL REQUIREMENTS

3.1 Aircraft Performance Requirements

3.1.1 Airframes: Type III and Type IV aircraft must be distinctly different Type/Model airframes.

3.1.2 Substitution of aircraft: With advanced Scheduling Officer (SO) approval, Type IV aircraft may be substituted for Type III missions; however, contractor payment shall be at the Type III rate.

3.1.3 Regardless of other stores configuration, aircraft must be equipped with either Tactical Combat Training System (TCTS), Large Area Tracking Range (LATR) or equivalent pods when operating on controlled ranges.

3.1.4 Aircraft must be capable of conducting tactical maneuvering through a maximum of 180 degrees of turn within the visual arena with blue force aircraft. This maneuver may be offensive or defensive in nature.

3.1.5 All performance requirements shall be assessed under Standard Day Conditions.

3.2 Type III Aircraft: The Contractor shall provide Type III aircraft that meet the following performance criteria:

Matrix 1 TYPE III – Performance Requirements

Speed and Altitude: Threshold: Accelerate to and maintain Mach 0.85 at optimum altitude level with one AST-9 and either one TCTS or LATR pods and in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Objective: Accelerate to and maintain Mach 0.90 at optimum altitude level with one AST-9 and either one TCTS or LATR pods and in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Ceiling: 35,000 feet Mean Sea Level (MSL) Turn: 6.0G Instantaneous turn rate at corner velocity below 15,000 feet MSL Range: 1,200 NM OCONUS with Visual Flight Rule (VFR) fuel reserves at zero wind un-refueled in ferry configuration;

and VFR fuel reserves are defined as 10% of planned fuel or 20 minutes at max endurance at 10,000 ft. MSL, whichever is greater.

Minimum Take-off to landing duration time:

Threshold: 2.0 hours at optimum loiter with one AST-9 and either one TCTS or LATR pod.

Objective: 3.0 hours at optimum loiter with one AST-9 and either one TCTS or LATR pod.

Note: Where available, external tanks may be used to meet the requirement. Fuel calculations shall include fuel required for start, taxi, takeoff, climb to altitude and a descent to land and recovery with VFR fuel reserves.

Configuration and Special Equipment:

1. Every Type III mission-capable aircraft shall be able to perform the basic and external stores missions. The aircraft shall have a minimum of two (2) hardpoint stations configured with interfaces for the external stores identified in paragraph 3.5.1.2.

2. Every Type III aircraft shall be equipped with:

Threshold:

a. Operational ejection seats with FAA accepted training and maintenance program.

b. Permanently installed Technical Standard Order (TSO)-C147-compliant

Traffic Advisory System (TAS) or Traffic Collision Avoidance System

(TCAS).

c. Global Positioning System (GPS) based navigation capability

d. At least three (3) Very High Frequency (VHF)/Ultra High Frequency

(UHF) radios. Aircrew must be able to monitor one (1) VHF and two (2) UHF frequencies simultaneously.

e. Air-to-Air Tactical Air Navigation (TACAN)

f. Capable of squawking IFF Mode 1

g. Aircraft shall be RedNet or RedNet equivalent system compatible, tied into TCTS Inc II/LVC

h. Mission Recording: Each aircraft shall be capable of recording select mission data. These recordings shall be easily digitally transferable to an audio/video playback system for the primary use of mission debriefs.

Any recordings of classified communications or videos of classified locations, aircraft, or maneuvers shall be erased after being transferred to the Government or debriefing playback. Each aircraft shall be capable of recording Heads Up Display (HUD) data or radar display data, at a minimum.

Objective:

a. IR Captive Air Training Missile (CATM)

b. Helmet mounted cueing (HMC) capability

3. Every Type III aircraft shall be capable of being equipped with:

a. At least one LAU7

b. All EW external stores defined in paragraph 3.5.1.2 Government

Furnished Property (GFP)

c. RM-30 Tow Reel (GFP) or equivalent capable and RADALT for tow mission for OCONUS aircraft only Additional Performance Criteria:

1) Launch from East Coast operating base with one AST-9 and either one TCTS or LATR pods, fly to N3515 W07515 entry to OPAREA, perform two profiles of 15 minute loiter/ 3 minute Military (maximum non-afterburning) power at 22,000 MSL, and return to base (RTB) with IFR fuel reserves. IFR fuel reserves are defined as 10% of planned fuel to fly to the destination initial approach fix, then to an alternate airfield, or 20 minutes at max endurance at 10,000 ft. MSL, whichever is greater.

2) Launch from East Coast operating base with one AST-9 and either one TCTS or LATR pods, fly to N3515 W07515 entry to OPAREA, Cruise at .7 Indicated Mach Number (IMN) for 1hr at 22,000 MSL, and return to base (RTB) with IFR fuel reserves.

3.2.1 The Contractor shall provide aircraft for a simultaneous presentation as identified in the matrix below.

Matrix 2

LOCATION

Minimum Number of Aircraft Required for

Simultaneous Presentation

Required Tow Reel Presentations

Maximum daily turn pattern East Threshold: 6 Objective: 8 N/A 4 x 4 x 4 (KW) 1

1. Normal turn pattern for Key West operations is 2 x 2 x 2.

3.3 Aircraft Performance Requirements – Type IV Aircraft: The Contractor shall provide Type IV aircraft that meet the following performance criteria:

Matrix 3 TYPE IV – Performance Requirements

Speed and Altitude: Threshold: Accelerate to and maintain Mach 1.2 at optimum altitude with one AST-9 and either one TCTS or LATR pod and in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Objective: Accelerate to and maintain Mach 1.5 at optimum altitude with one AST-9 or equivalent drag and either one TCTS or LATR pods and in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Ceiling: 35,000 feet MSL with AST-9 and either TCTS or LATR pod.

Turn: 6.0G Instantaneous turn rate at corner velocity below 15,000 feet MSL with AST-9 and either TCTS or LATR pod.

Range: 1,200 NM OCONUS with VFR fuel reserves at zero wind un-refueled in ferry configuration.

Minimum Take-off to landing duration time:

Threshold: 2.0 hours at optimum loiter with one AST-9 and either one TCTS or LATR pod.

Objective: 3.0 hours at optimum loiter with one AST-9 and either one TCTS or LATR pod.

Where available, external tanks may be used to meet the requirement. Fuel calculations shall include fuel required for start, taxi, takeoff, climb to altitude and a descent to land and recovery with VFR fuel reserves.

Configuration and Special Equipment:

1. All Type IV mission-capable aircraft shall be able to perform the basic and external stores missions. The aircraft shall have at least two (2) hardpoint stations configured with interfaces for the external stores identified in paragraph 3.5.1.2.

2. Every Type IV aircraft shall be equipped with:

Threshold:

a. Operational ejection seats with FAA accepted training and maintenance program.

b. Permanently installed TSO-C147-compliant TAS or TCAS.

c. GPS based navigation capability

d. At least three (3) VHF/UHF radios. Aircrew must be able to monitor one (1) VHF and two (2) UHF frequencies simultaneously.

e. Air-to-Air TACAN.

f. Capable of squawking IFF Mode 1

g. Aircraft shall be RedNet or RedNet equivalent system compatible, tied into TCTS Inc II/LVC.

h. Mission Recording: Each aircraft shall be capable of recording select mission data. These recordings shall be easily digitally transferable to

West 6 N/A NA Hawaii (MIDPAC) 2 1 NA Japan (WESTPAC) 2 1 NA Additional CONUS Capability (CLINs 0X15)

1 per each 15,000 minute increment of a task order

Matrix 3 TYPE IV – Performance Requirements an audio/video playback system for the primary use of mission debriefs.

Any recordings of classified communications or videos of classified locations, aircraft, or maneuvers shall be erased after being transferred to the Government or debriefing playback. Each aircraft shall be capable of recording Heads Up Display (HUD) data or radar display data, at a minimum.

Objective:

a. Radar – Airborne radar capable of Track or Track While Scan modes.

Minimum detection requirement for radar is a 5-meter square target at 30 NM with 50% detection probability.

3. Every Type IV aircraft shall be capable of being equipped with:

a. At least one LAU7

b. All EW external stores identified in paragraph 3.5.1.2 (GFP).

Additional Performance Criteria:

The Type IV aircraft must be able to routinely execute the following flight profile:

Launch from East Coast operating base with one AST-9 and one LATR or TCTS POD, fly to N3515 W07515 for entry into OPAREA, perform Mach 1.1 dash for 75 miles on a 090 heading at 22,000 feet MSL, followed by 0.8 IMN 100 mile RTB with IFR fuel reserves.

3.3.1 The Contractor shall provide aircraft for simultaneous presentations as identified in the matrix below.

Matrix 4

Location Minimum Number of Aircraft Required for

Simultaneous Presentation

Maximum daily turn pattern East 3 NA West 2 NA Japan (WESTPAC) 2 NA Additional CONUS Capability (CLINs 0X16)

1 per each 12,000 minute

3.4 Aircraft Performance Requirements – Type J (Option for F-35 Production Support): The Type J aircraft may be the same model aircraft as Type III or Type IV. The Contractor shall provide Type J aircraft that meet the following performance criteria:

Matrix 5 TYPE J – Performance Requirements

Speed and Altitude: Mach 0.95 in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Ceiling: 40,000 feet MSL in a configuration that meets the "Minimum Take-off to landing duration time" requirement below.

Turn: Greater than or equal to 5.0 G 180 degree turn at corner velocity at 10,000 feet MSL.

Greater than or equal to 3.0 G 180 degree turn at corner velocity at 30,000 feet MSL Constant airspeed 360 degree turn while maintaining altitude between 35,000 feet to 40,000 feet MSL

Range: N/A Minimum Take-off to landing duration time:

Threshold: 1.7 hours at or below 20,000 feet MSL at 300KCAS (Knots Calibrated Air Speed) and above 20,000 feet MSL at 0.85 Mach. Where available, external tanks may be used to achieve airborne time.

Objective: 2.0 hours at or below 20,000 feet MSL at 300KCAS and above 20,000 feet MSL at 0.85 Mach. Where available, external tanks may be used to achieve airborne time.

Configuration and Special Equipment:

1. Every Type J aircraft shall be equipped with:

Threshold:

a. Operational ejection seats with FAA accepted training and maintenance program.

b. Permanently installed TSO-C147-compliant TAS or TCAS.

c. At least one (1) type of FAA-approved navigation equipment such as

Very high frequency Omni directional Range (VOR); global positioning system (GPS), etc. A GPS must be available for operations in remote areas where other navigational aids are not available.

d. At least three (3) VHF/UHF radios. Aircrew must be able to monitor one (1) VHF and two (2) UHF frequencies simultaneously.

e. Air-to-Air TACAN.

f. Radar –Capable of Track or Track While Scan modes. Minimum detection requirement for radar is a 1-meter square target at 25 NM with 90% detection probability.

g. Aircraft shall be RedNet or RedNet equivalent system compatible, tied into TCTS Inc II/LVC.

Objective:

a. Link-16 capability (On all Type J aircraft)

Additional Performance Criteria:

1. Acceptance check flight profiles consist of the following:

a. MAX power takeoff to 350KCAS, climb at 350KCAS within 5NM of airfield to arrive at 15,500 feet MSL within 360 degrees of turn. (Note: Field elevation = 650 feet MSL)

b. Subsequent close formation during engine cycles and configuration changes ranging from 250KCAS to 350KCAS.

c. From 15,500 feet MSL, climb at 350 KCAS to 23,000 feet MSL then climb at Mach 0.85-0.90 to 35,000 feet MSL at a minimum 5 degrees pitch angle.

d. At 35,000 – 40,000 feet MSL and Mach 0.65-0.95, make multiple energy-and altitude-sustaining 90-360 degree turns in close formation between 2.0 and 3.0 G.

e. Accomplish an energy sustaining maneuvering Beyond Visual Range (BVR) to Within Visual Range (WVR) radar intercept, against a fighter-sized target, from no less than 25NM, at 35,000-40,000 feet MSL, providing a radar lock and targeting communications to the F-35.

f. Following intercept, execute a descent below 18,000 feet MSL for follow on checks.

g. Accomplish a low-altitude maneuvering intercept below 5,000 feet MSL providing a radar lock and targeting to F-35.

h. Complete other acceptance checks in close formation, ranging from 135KCAS in landing configuration to 400KCAS.

i. Accomplish generator cycles resulting in near-total mission, navigation, and communication system loss/degradation with chase providing visual lookout, radar sanitization, position reporting, and communication with Fort Worth Center through landing rollout.

2. Routine operations require contractor aircraft and/or aircrew to:

a. Attend a 30-minute brief at 1+30 hours before takeoff and be airborne with 1+00 hour from brief end.

b. The Start, Taxi, and Takeoff sequence shall be less than 20 minutes.

c. Descend at 20,000 feet per minute from 35,000 feet MSL to 10,000 feet MSL in the event of an emergency.

d. Provide UHF communication relay, Mode 3C squawk, RADAR/Visual lookout for up to 25 minutes.

e. Operate up to crosswind limits of 25 knots dry/20 knots wet.

f. Be capable of instrument approaches to 300 foot ceiling and one (1) mile visibility.

g. Be able to turn an aircraft between sorties to enable less than 3 hours from landing until next scheduled takeoff.

h. Attend a 30-minute mission de-brief within 45 minutes from landing.

3.4.1 The Contractor shall provide aircraft for simultaneous presentations as identified in the matrix below.

Matrix 6

Location Minimum Number of Aircraft Required for

Simultaneous Presentation

Fort Worth Naval Air Station (NAS) Joint Reserve Base (JRB) (NFW)

Standard daily flying = 2x2 or 3x0, with surge day maximum

= 3x2 (max 5 sorties/day)

Additional CONUS Capability (CLINs 0X17) 1 per each 12,000 minute

Note: It is anticipated that Type J will fly approximately 600 hours annually in support of F-35 production.

Average operations will result in approximately eight (8) sorties per week. Routine operations require the ability for the contractor to generate up to four flights on any given fly-day. Production may demand the equivalent of a morning 2-ship and afternoon 2-ship from the contractor (2-turn-2), or the equivalent of a single 3-ship in the morning or afternoon (3-turn-0). Surge fly days, needed to overcome production or weather-driven delays, will require up to a maximum of five (5) sorties (3-turn-2).

3.5 Specific Requirements

3.5.1 Type III and Type IV Aircraft during mission performance

3.5.1.1 Communication and Navigation Capability. The Contractor shall ensure all aircraft are equipped with the applicable communication and navigation capability to operate in the International Air Space, or foreign nation airspace requirements as applicable. Within the context that these aircraft may deploy worldwide, the Contractor shall comply with other FAA, International Civil Aviation Organization (ICAO) or foreign nation equipment pre-requisites, and shall be solely responsible to provide such equipment.

3.5.1.2 The aircraft must be capable of carrying and employing a combination of either a LATR or TCTS pod and one of the following external stores simultaneously: ALQ-167, AST-6, AST-9, or other current EA, Electronic Surveillance (ES), and tracking pods. The Government will provide C-9492/ALQ Control Indicators and the United States Navy (USN) Universal Control Box (UCB) (standard and mini-UCB) for use with EA pods as appropriate. The Contractor’s aircraft must be configured to use either control box interchangeably. The EA pods and control boxes are Government provided mission equipment and will be maintained by the Government. The Government will provide interface control documents for all PODS and equipment to be utilized in the training missions (includes pods and internal suite systems). Additional external stores types may be provided as GFP to support evolving requirements. See Section J, Attachment 3.

3.5.1.3 For Type III Aircraft only – the aircraft must be capable of carrying and employing a RM-30 tow reel (GFP) (or equivalent). The Contractor shall provide at least one (1) coaxial cable for video to at least one (1) pylon on each side of the aircraft. The aircraft must be Government certified to carry GFP provided RM-30 tow reels plus any equivalent type tow reel provided by the Contractor as Contractor Furnished Equipment (CFE).

3.5.1.4 Missions. The Contractor shall provide services to include, but not limited to, the following types of missions (Presentations may be flown as singles, sections, and mixed divisions). Other missions within aircraft operating limitations may be tasked.

1) Typical profiles will require extended flight and loitering as far as 250 miles off-shore, operating between 200 feet during daylight hours and 1,000 feet at night and 35,000 feet (MSL).

2) Mission Flights under positive control, with the pilot responding to vectors and instructions by

NAVAIR controllers as designated by the Scheduling office.

3) Mission Flights with indirect control or independent un-vectored flight executed in accordance with a pre-briefed scenario driven presentations.

4) EW Pod Missions. Employ at least two external stores to present increasingly complex scenarios to ship weapons controllers, fighter squadron aircrews, and AIC trainees. EW Pod Missions, ES & EA Pods, up and downloads, and flight times are included as part of the basic flight minute rate applies to CLINs 0003, 0006 and 0014.

5) Dry Close Air Support, not including the use of live or inert ordnance.

3.6 Type J Aircraft (Option)

1) The Contractor shall provide mutual support, radio relay, and checklist aid during formation flying and/or during aircraft emergencies.

2) The Contractor shall provide chase for all F-35 Acceptance Check, Functional Check, and Operational Check Flight profiles and maneuvers.

3.7 Full Operational Capability

3.7.1 Type III Aircraft: The Contractor shall provide Full Operational Capability (FOC) within 6 months or less, from date of task order award. FOC consists of sufficient aircraft that are configured to meet performance requirements of the Type III Aircraft shown in Matrix 1, and which meet the threshold requirements of Matrix 2. At FOC, aircraft shall be operated from the East Coast (Para 5.1.2), West Coast (Para 5.1.1) and OCONUS (paras 5.1.3, and 5.1.4) basing to meet simultaneous presentation requirements.

3.7.2 Type IV Aircraft: The Contractor shall provide FOC within 6 months or less, from date of task order award. FOC consists of sufficient aircraft that are configured to meet performance requirements of the Type IV Aircraft shown in Matrix 3, and which meet the requirements of Matrix 4. At FOC, aircraft shall be operated from the East Coast (paragraph 5.1.2), West Coast (paragraph 5.1.1) and OCONUS (paragraphs 5.1.3, and 5.1.4) basing to meet simultaneous presentation requirements.

3.7.3 Type J Aircraft (Option): The Contractor shall provide FOC within 6 months or less, from date of option exercise. FOC consists of sufficient aircraft that are configured to meet performance requirements of the Type J Aircraft shown in Matrix 5, and which meet the requirements of Matrix 6. At FOC, aircraft shall be operated from the F-35 Production Support Basing (paragraph 5.1.5) to meet simultaneous presentation requirements.

3.7.4 Type III Aircraft – Additional CONUS Capability: The Contractor shall provide aircraft to support additional CONUS Capability within 90 days from date of task order award that are configured to meet performance requirements of the Type III Aircraft shown in Matrix 1, and which allows for scheduling of one

(1) additional presentation for each 15,000 flight minute increment.

3.7.5 Type IV Aircraft – Additional CONUS Capability: The Contractor shall provide additional CONUS Capability within 90 days from date of task order award that are configured to meet performance requirements of the Type IV Aircraft shown in Matrix 3, and which allows for scheduling of one (1) additional presentation for each 12,000 flight minute increment.

3.7.6 Type J Aircraft – Additional CONUS Capability: The Contractor shall provide additional CONUS Capability within 90 days from date of task order award that are configured to meet performance requirements of the Type J Aircraft shown in Matrix 5, and which allows for scheduling of one (1) additional presentation for each 12,000 flight minute increment.

3.7.7 The Contractor shall provide a test report validating a successful demonstration of platform performance with required equipment In Accordance With (IAW) this PBWS for Government approval Contract Data Requirements List (CDRL) A001. Approval of the CDRL data is a pre-requisite to achieving

FOC.

3.7.8 The Contractor shall provide an Integrated Master Schedule (IMS) with milestones for all events and activities required to achieve FOC (CDRL A007). Approval of CDRL A007 data is a pre-requisite to achieving FOC. At a minimum the following milestones shall be included in this IMS starting from estimated award date;

a) Provision of Federal Aviation Administration (FAA) Airworthiness Certification supplemental type certificates or systems safety analysis to support NAVAIR issuance of Type 2 CAS Interim Flight Clearance (IFC), Reference NAVAIR Instruction (NAVAIRINST) 13034.1F - NAVAIR Airworthiness and Cybersafe Process Manual;

b) Submission of Required NAVAIR Interim Flight Clearance (IFC) /Airworthiness Substantiation Documentation (Aircraft in a PWS Mission Ready Configuration);

c) NAVAIR IFC Issuance;

d) Verification of Contractual Required Aircraft Performance;

e) Full Operational Capability

3.8 Aircraft Certification, Maintenance Practices and Operating Procedures

Aircraft must be certified, maintained and operated IAW 14 CFR and its NAVAIR Interim Flight Clearance (IFC), including, but not limited to, the following areas:

FAA AC 91-91 – Maintaining Public Aircraft Part 21 – Certification Procedures for Products and Parts Part 43 – Maintenance, Preventive Maintenance, Rebuilding and Alteration Part 91 – General Operating and Flight Rules

3.8.1 FAA Airworthiness and Related Substantiation Data (CDRL A001) Aircraft must possess a current FAA Airworthiness Certificate and be certified to fly in actual and forecasted icing conditions. Former military aircraft, regardless of source, must meet the original design standards for forecasted icing condition. The Contractor shall provide a copy of FAA certificates and all other related airworthiness substantiation data for review within 30 calendar days of contract award and as generated or requested (CDRL A001). The Contractor shall comply with all Airworthiness Directives (AD) and service bulletins for mission effectiveness.

3.8.1.1 FAA Standard Airworthiness Certificates

For aircraft with FAA Standard Certificates, the Contractor shall maintain the aircraft IAW 14 CFR. The Contractor shall secure FAA approval for each change to the configuration that is not defined in the aircraft’s Airworthiness Certificate before the change is used in support of this contract. For each such modification, the Contractor shall secure and provide the valid FAA-approved data within 15 days of contract award and as generated or requested (CDRL A001). For Type Certificated aircraft, if this data references FAA regulations as the standard, the Contractor shall provide Approved Data as defined in the FAA Order 8300.16 for any major alteration or major repair. Major alterations to aircraft with Standard Airworthiness Certificates shall have been certified as airworthy and properly documented using FAA Form 337 signed in blocks six (6) (Conformity) and seven (7) (Return to Service) by persons authorized under 14 CFR § 43, and citing FAA Approval Data. Only the FAA may certify modifications relating to powered systems for captive carriage.

3.8.1.2 FAA Special Certificates

For aircraft with FAA Special Certificates, the Contractor shall provide the Program Letter (PL) submitted to the FAA for application of the airworthiness certificate used in support of this contract or latest PL associated with the current airworthiness certificate. Under this certificate, the aircraft must be maintained in accordance with the operating limitations issued as part of that certificate. For each subsequent aircraft modification deviating from the FAA issued certificate, the contractor shall secure and provide an updated FAA airworthiness certification, and associated operating limitations (CDRL A001), before the modification is used in support of this contract. Where the modification is a Major Change (as defined by 14 CFR), the Contractor shall provide the PL and secure the FAA's determination regarding the need for new or amended certificates. All major alterations incorporated before contract award and during contract execution shall have sufficient data to determine that the equipment or provisions for the equipment meet the applicable civil, Original Equipment Manufacturer (OEM), Military Standard (MIL- STD), or some other recognized engineering substantiation data, for the type of aircraft concerned. Unless directed otherwise by the Government, the Contractor shall remove any major alteration incorporated before contract award that was not certified as airworthy by an appropriately rated FAA certified mechanic, aircraft manufacturer or repair station.

3.8.1.3 NAVAIR Airworthiness Supporting Data

3.8.1.3.1 The Contractor shall provide a single point-of-contact to manage the airworthiness certifications and to coordinate Contractor and Government certification efforts during the Stand-up phase of each Aircraft Type or during any significant aircraft modification requiring a new or updated NAVAIR IFC.

3.8.1.3.2 All aircraft under this contract require a NAVAIR issued IFC (NAVAIRINST 13034.1F).

The Contractor shall provide airworthiness substantiation data IAW this PBWS, CDRL A001 and as required by NAVAIR. To ensure timely IFC release required to conduct PAO mission, aircraft must be fully operational and all substantiation data shall be provided at least thirty (30) days prior to FOC.

3.8.1.3.3 For all aircraft operating under a NAVAIR IFC, the Contractor shall notify the Contracting

Officer’s Representative (COR) of any proposed changes to the aircraft configuration, FAA certificate status, or operating limitations and procedures so an assessment of the changes can be made and a modified NAVAIR IFC issued, if warranted. In addition, the Contractor shall provide airworthiness substantiation data IAW CDRL A001 for the proposed change.

4.0 OPERATIONAL REQUIREMENTS

4.1 Mission Planning

4.1.1 Under the Commander, Naval Air Systems Command (NAVAIRSYSCOM), PMA-226 is the overall CAS Program Manager. PMA-226 will designate SOs to execute administrative tasks such as mission scheduling and coordination, and invoice certification. The Contractor Representative (CR) shall coordinate with the SO on all formal requests for Fighter Jet services to determine feasibility of support, implications of support on other scheduled or potentially scheduled mission and any other necessary details requiring coordination.

4.1.2 The Contractor shall support normal schedule for flight operations, which is Monday through Friday, 0600 to 2000 local time. However, flight operations may be scheduled at any time, 24 hours a day/seven days a week, subject to a minimum mission flight time. The weekly schedule provided by the SO will identify when operations are required outside of the normal operating schedule or that are of longer duration than 14 hours per day. The schedule is typically published on Wednesday of the week prior to the execution week.

Once this weekly schedule is published, the Government will give the Contractor 24 hours advance notice for any changes to the tasking and issue an update to the weekly schedule. To meet emergent demands, the Contractor may be asked to provide services with less than 24 hours’ notice during home base operations.

4.1.3 If an aircraft has deployed and is currently on a detachment (away from home base), the Government will provide at least 18 hours’ notice before redeploying to another site. During periods of intensive test operations or major exercises, flight operations may run in excess of 14 hours a day, seven days a week for up to four weeks. When detachments (greater than 7 days), high tempo operations or extended fly days are anticipated, the Government will notify the Contractor via email at least 14 business days in advance.

Scheduled and planned maintenance requirements that may preclude aircraft availability should be coordinated as far in advance as possible with the SO. Pilot mission briefs are held prior to mission execution and will include detailed information for mission profile execution.

4.1.4 The Contractor shall coordinate ground and flight crew daily schedules as necessary to meet the operational tasking of the SO. The Contractor shall provide a CR contact to cover scheduling 24 hours per day/seven days a week. Scheduled and planned maintenance requirements that will preclude availability of any aircraft should be coordinated as far in advance as possible so that supportable commitments can be adjusted. As soon as it is determined that missions cannot be met, the Contractor shall inform the Government if any aircraft are not able to meet assigned or future missions, via email or phone to the COR.

4.1.5 F-35 Production Support (Option)

4.1.5.1 Production Support sorties are required year-round, typically Monday through Saturday, between one hour after sunrise and one hour before sunset (night flying will not be required). Sunday and holiday flying (to include major holidays) will be required when necessary to overcome production delays.

4.1.5.2 Scheduling. A notional schedule will be published at 1600 daily for the next flying day. That schedule is typically revised mid-morning on the day of execution, making adjustments for afternoon flying based on production aircraft readiness and weather; however multiple “real-time” schedule changes are expected each day of execution.

4.2 Scheduling Officer Communications with Contractor

A. The designated SO for East Coast Task Orders (TOs) is the CAS office at Fleet Area Control Surveillance Facility (FACSFAC) Virginia Capes (VACAPES), VA. The SO will coordinate the Government’s Navy Fleet and FMS Fleet requirements and schedule all Fleet and FMS Fleet missions for the East Coast.

B. The designated SO for West Coast TOs is FACSFAC San Diego, CA. The SO will coordinate the Government’s Navy Fleet and FMS Fleet requirements and schedule all Fleet and FMS Fleet missions for the West Coast.

C. The designated SO for the MIDPAC and WESTPAC is the CAS office at FACSFAC Pearl Harbor, HI.

The SO will coordinate the Government’s Navy Fleet and FMS Fleet requirements and schedule all Fleet and FMS Fleet missions for MIDPAC and WESTPAC.

D. The CAS Flight Service Manager (to be identified at time of option exercise) is the designated SO for Special Project aircraft and all other contract flight requirements, including coordination with DCMA Lockheed Martin Fort Worth regarding F-35 production support.

E. The SO and CR will communicate as often as required to develop the short range and long range schedule, but at a minimum, the CR will provide a weekly schedule to the SO reflecting events as flown, currently scheduled, flying hour execution and proposed aircraft maintenance schedule. This scheduling should include planned operations using Standard Mission support personnel.

F. The Government reserves the right to cancel or not schedule flight services on any given day of detachment operations.

4.2.1 Authorization of Flight Operations

All flight operations must be authorized by the SO and communicated to the CR by the SO or their designated representative.

4.2.2 Released by the Government

When all flights for detachment operations have been completed, the SO or their designated representative will notify the CR via email that the deployment is complete. Following this notification, the CR shall complete and implement arrangements to return the aircraft, personnel, and equipment to the home base.

4.3 Contract Coordination

4.3.1 Post-Award Conference

The Contractor shall host a Post-Award Conference (PAC) with the Government no later than 30 days after contract award at the Contractor’s location. The PAC agenda must be established following contract award and is intended to orient both Government and Contractor personnel with contract requirements, schedule, and performance expectations. The PAC shall be conducted IAW FAR Subpart 42.5.

4.3.2 Program Management Reviews

The Government will schedule and conduct Program Management Reviews (PMRs) on a semi-annual basis at NAVAIRSYSCOM PMA-226, Cherry Point, North Carolina, the Contractor’s facility, or other locations as directed by the COR. The Contractor shall attend all PMRs with appropriate personnel.

A. At each PMR, the Contractor shall make a presentation consisting of the following:

i. Overview of the work accomplished to date or since last review, the projected plan of action for completion of contract effort, and handout material documenting presentations.

ii. Identification and discussion of problems encountered, if any, and action taken to resolve the problems.

iii. Identification and discussion of problems anticipated and the Contractor’s plan of action for mitigation.

B. The contractor shall also:

i. Address experiences working as a team with other CAS Contractors (when applicable) and the Government, identifying successes and areas needing improvements.

ii. Record minutes and provide list of action items for each review.

4.3.3 Contractor Management Plan (CDRL A002)

The Contractor shall provide a Contractor Management Plan (MP) within 30 days of contract award that describes the Contractor’s organization, management procedures and modification schedules that are established for the initiation, monitoring, control and completion, test and verification, and reporting of contractual requirements to complete the tasks outlined in this PBWS and IAW CDRL A002.

4.4 Mission Coordination (Operational Reporting)

4.4.1 Scheduled Maintenance Requirements

The Contractor shall coordinate with the SO and COR no less than once per month to discuss requirements and identify potential aircraft scheduled maintenance. No special scheduling arrangements or considerations will be made to meet the Contractor’s maintenance requirements.

4.4.2 Mishap Response Plan for Accidents and Incident Reporting As required by DCMA INST 8210.1C Change 1, the Contractor shall report all aircraft accidents and incidents to include all air and, ground mishaps and Occupational Safety and Health Administration (OSHA)/Safety violations, IAW its approved Mishap Response Plan (MRP), Ground Operations Procedures (GOP) and Flight Operations Procedures (FOP). The Contractor shall immediately contact the local base Commanding Officer or Command Duty Officer or the officer conducting the exercise, as applicable and the COR. Leaving a voicemail alone is not sufficient.

PMA-226 incident reporting phone numbers will be provided at award. Accident/Damage reports, at a minimum, must be marked FOR OFFICIAL USE ONLY (FOUO) or classified IAW the appropriate security classification guide.

4.4.3 Waiver Requests

Each aircraft used in the performance of this contract must be operated and maintained IAW 14 CFR and its NAVAIR IFC. If, in the performance of this contract, for any reason a contract requirement cannot be met, the Contractor shall notify the Procuring Contracting Officer (PCO) and the COR, and obtain approval from the Government Flight Representative (GFR), prior to conducting operations. The waiver request must cite the specific requirement that cannot be adhered to IAW DCMA INST 8210.1C Change 1.

4.5 Fixed Rate Work Tasks

4.5.1 Fuel

4.5.1.1 This is a “dry” contract. The Government will provide access to fuel at United States Government (USG) bases and civil fields. The Contractor shall purchase fuel with the Government provided appropriate fuel Aviation Into-plane Reimbursement (AIR) cards for each of the Contractor’s aircraft.

All fuel purchased by the Contractor should be obtained from a military base whenever possible.

Whenever “into plane” (Government rate) fuel needs to be obtained from a civilian airport, the Contractor shall record the circumstances and justification IAW the DoD 4140.25-M. Commercial non “into plane” fuel may only be used by exception with SO or COR advance approval.

4.5.1.2 The Contractor shall not use any Government provided fuel for any flight other than those scheduled under this contract.

4.5.1.3 The Contractor shall provide Fuel Chits, which track all fuel consumption and provide fuel receipts, flight logs, and Fuel Reports to the Government in accordance with (CDRL A003).

4.5.2 Fuel Card Training

The Contractor shall complete AIR card training IAW DoN Consolidated Card Program Management Division (DoN CCPMD) at least 30 days before first flight. All users of the AIR cards (pilots/flight commanders/aircraft commanders/crew chiefs) must perform DoN role-based refresher training every 2 years. Common Access Cards (CAC) are required to register for training via the CCPMD website. For users new to this site, the individual shall register their CAC the first time they access the site. The CCPMD training system uses the email associated with the users CAC when registering completion of training and to provide certificate. All Contractor fuel card users shall:

i. Register the CAC at: https://www.navsup.navy.mil/registration

ii. Register for and complete the Card User Certification Course via CCPMD home portal -https://my.navsup.navy.mil/webcenter/portal/ccpmd and select AIR Card or go directly to AIR Card training at https://my.navsup.navy.mil/webcenter/portal/ccpmd_ac/Training

iii. Complete the Online Certification

iv. Print the Certificate of Completion and provide a copy to the COR within 5 working days.

v. Contract users shall sign a Card User Statement of Understanding (SOU) after conducting training.

4.5.3 Aviation Safety and Mishap Prevention Program

The Contractor shall establish and maintain an Aviation Safety and Mishap Prevention Program and ensure it is reviewed by all aircrew members on an annual basis IAW DCMA INST 8210.1C Change 1.

4.5.4 Aviation Safety Official

4.5.4.1 The Contractor shall designate an Aviation Safety Official with specific duties and responsibilities defined in accordance with DCMA INST 8210.1C Change 1

4.5.4.2 The Contractor shall establish and maintain an Operational Risk Management (ORM) Program, IAW

DCMA INST 8210.1C Change 1 and the MRP. Per DCMA INST 8210.1C Change 1, the Contractor shall establish and execute written procedures for responding to an aviation incident or accident as part of the MRP. The Contractor shall deliver all Accident and Incident reports to PMA-226 per its MRP. In addition to safety and reporting requirements outlined in PBWS paragraphs 4.5.3, 4.5.4,

4.5.5 and 6.4.1, the MRP must establish policies, responsibilities, and actions to be initiated if any aircraft becomes overdue from its active Flight Plan. The Contractor shall conduct an exercise of the MRP on an annual basis. In addition to the requirements of DCMA INST 8210.1C Change 1, the Contractor shall also establish procedures, which conform to USC Title 49 Chapter 8 Part 830 National Transportation Safety Board (NTSB).

4.5.5 Mishap Response Plan

The Contractor shall establish and execute a MRP to include written procedures for responding to an aviation incident or accident. The MRP shall establish policies, responsibilities, and actions to be initiated if any aircraft https://www.navsup.navy.mil/registration https://my.navsup.navy.mil/webcenter/portal/ccpmd https://my.navsup.navy.mil/webcenter/portal/ccpmd_ac/Training becomes overdue or involved in an incident or mishap. The Contractor shall re-evaluate the MRP on an annual basis and make any required updates. As a minimum, this plan shall include the following:

i. Procedures that conform to USC Title 49 Part 830 NTSB;

ii. Immediate action checklist to ensure command, control, and coordination of the rescue or recovery effort;

iii. A notification plan which includes a current roster of Contractor and Government personnel

(including duty and non-duty phone numbers) to be notified in the event of an aircraft mishap; and

iv. Procedures for Contractor and subcontractor cooperation and participation in mishap investigations conducted by the Government. Procedures shall clearly define the differences between a Government legal investigation (used to satisfy claims) and a Government safety investigation (used for mishap prevention). The procedures shall clearly state the contractual obligation of Contractor personnel to provide information and participate in interviews by the Government safety investigation immediately upon request. The Contractor shall have procedures that require, to the maximum extent possible, aircrew medical and toxicological testing immediately following a mishap. The results of medical and toxicological testing shall be provided to the Government safety investigation board immediately upon request. The toxicological samples shall be provided to the Government legal investigation board immediately upon request.

4.5.6 Contract/Task Order Status

The Contractor shall track flight minutes and all costs associated with each TO on a per CLIN level. The Contractor shall submit a Monthly Status Report in accordance with CDRL A004 during the Period of Performance (PoP) of each TO.

4.5.7 Transient Military Aircraft

When in support of scheduled missions, aircraft provided under this contract are considered transient military aircraft and not subject to landing fees at DoD controlled airfields.

4.5.8 Civil Aircraft Landing Permits

The Contractor shall submit DD Form 2400 - Civil Aircraft Certificate of Insurance, DD Form 2401-Civil Aircraft Landing Permit and DD Form 2402-Civil Aircraft Hold Harmless Agreement IAW 32 CFR766 to the COR. These agreements must be kept current during the entire ordering period of the contract and through the final PoP for all TO’s. Landing permits will be submitted by PMA-226 for landing at USN, United States Marine Corps (USMC) and United States Air Force (USAF) airfield facilities worldwide, i.e. all CONUS/OCONUS, without restriction, to include the purchase of USG fuel, and support services on a not-to-interfere basis. USAF landing permits will comply with AFI 10-1001 Civil Aircraft Landing Permits and AFI 10-1002 Agreement for Civil Aircraft Use of Air Force Airfields.

4.5.9 Maintenance Program

4.5.9.1 Aircraft used in the performance of this contract must be maintained in accordance with 14 CFR, their NAVAIR IFC and this PBWS.

4.5.9.2 The Contractor shall manage remaining fatigue life to allow the aircraft to be safely operated throughout the ordering period of the contract and provide fatigue life status as part of configuration management in the MP (CDRL A002).

4.5.9.3 The Contractor shall provide a list of all categories of parts with OEM defined life limits, and define in the MP, the path for replacing those parts on/before the required dates (CDRL A002).

4.5.10 Aeronautical Regulations

The Contractor shall comply with all FAA PAO procedures IAW FAA AC 00-1.1B and local military flying directives (including foreign Government requirements). The Contractor shall only utilize aircraft that possess current FAA Airworthiness Certifications and will require NAVAIR IFC prior to conducting PAO. The Contractor shall operate and maintain the aircraft IAW 14 CFR, and its NAVAIR IFC unless a waiver is granted in accordance with this PBWS, and CDRL A001).

4.5.11 General Deployments

When directed by the SO, the Contractor shall deploy its aircraft, personnel, and required support equipment to perform at any airfield capable of supporting its aircraft. The Contractor shall plan, schedule, ship, and deploy its personnel and equipment, including all GFP, as applicable. At least 30 days prior to deployments, the SO will release a pre-deployment message to the Contractor to ensure coordination of requirements, services, and accommodations. Travel and per diem will be reimbursed on a fixed-price per day basis. If aircraft or aircrew substitutions are accomplished at the Contractor's request during a scheduled deployment, transit to and from the deployment base to accomplish the substitution shall be entirely at Contractor expense. Shipment of Equipment will be reimbursed on a fixed-price per pound basis.

4.5.12 Equipment Installer

The Contractor shall provide maintenance personnel to install and remove GFP. GFP installation will be reimbursed on a fixed-price per hour basis. Government property for the performance of this contract will be limited to mission-specific GFP identified in Section J, Attachment 3 and transferred to the Contractor via DD Form 1348-1A.

4.5.13 Equipment Maintainer

The Contractor shall provide maintenance personnel to maintain the…