Att 1_EW Jet PBWS DRAFT.pdf

Performance Work Statement Attachment (1)

N0042124R0003

ATTACHMENT 1

ELECTRONIC WARFARE (EW) JET SERVICES

PERFORMANCE-BASED WORK STATEMENT (PBWS)

Naval Air Systems Command

Program Manager Air (PMA) 226

Specialized and Proven Aircraft Program Office

Contracted Air Services (CAS)

27 June 2023

Distribution Statement C: Distribution authorized to U.S. Government agencies and their contractors; administrative and operational use; 27 June 2023. Other requests for this document shall be referred PMA-226.

1.0 SCOPE

1.1 Naval Air Systems Command (NAVAIR or NAVAIRSYSCOM) Program Manager Air (PMA) 226

Specialized and Proven Aircraft Program Office, Contracted Air Services (CAS) Integrated Product Team (IPT) has a requirement for Contractor Owned Contractor Operated (COCO) Electronic Warfare (EW) Jet services. These aircraft are used to simulate a wide variety of airborne threats to train and test/evaluate shipboard and aircraft squadron weapon systems operators and aircrew on how to counter potential enemy EW and Electronic Attack (EA) operations in today’s Electronic Combat (EC) environment. This support is provided in a variety of venues, from basic “schoolhouse” Air Intercept Control (AIC) training to large multinational exercises or small, single unit training exercises, including Target/Banner Tow (TBT) missions.

1.2 Performance locations include multiple Continental United States (CONUS) sites and foreign or remote operating bases Outside Continental United States (OCONUS). Aircraft will predominantly operate from designated or home bases on the East Coast and West Coast CONUS or from any operating site identified in Section 6.6 of the

Performance-Based Work Statement (PBWS) during temporary periods of support and/or detachment.

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. For clarity, all references to the Federal Aviation Regulations in this

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, which are derived from 14 CFR and Defense Contract Management Agency Instruction

(DCMA INST) 8210-1D (also known as NAVAIR Instruction (NAVAIRINST) 3710.1H), apply to all situations and conditions relating to flight operations, aircraft maintenance, and flight crew certifications and qualifications.

a. 18 United States Code (USC) § 793, Gathering, Transmitting or Losing Defense Information

b. 49 USC § 40125 Qualifications for Public Aircraft Status

c. Aeronautical Information Circulars of the Country of Intended Operation

d. Air Force Instruction (AFI) 10-1001 Civil Aircraft Landing Permits 23 August 2018

e. AFI 10-1002 Joint Use Agreements for Military and Civilian Flying Facilities 08 August 2018

f. Brevity, Multi-Service Tactics, Techniques, and Procedures for Multi-Services Brevity Codes (Allied

Tactical Publication (ATP) 1-02.1, Marine Corps Reference Publication 3-30B.1, Navy Tactics, Techniques and Procedures 6-02.1 and Air Force Tactics, Techniques and Procedures 3-2.5) May

2020*

g. CFR, Title 14, Aeronautics and Space (14 CFR)

h. CFR, Title 14 Part 43, Maintenance, Preventive Maintenance, Rebuilding and Alteration

i. CFR, Title 14 Part 61, Certification: Pilots, Flight Instructors, and Ground Instructors

j. CFR, Title 14 Part 91, General Operating and Flight Rules

k. CFR, Title 32, Part 766, Use of Department of the Navy Aviation Facilities by Civil Aircraft

l. CFR, Title 49, Transportation (49 CFR)

m. Civil Aircraft Regulations Applicable to the Airspace or Country of Intended Operation

n. Commander Naval Air Forces (CNAF) M-3710.7, Naval Air Training and Operating Procedures

Standardization (NATOPS) General Flight and Operating Instructions Manual

o. DCMA INST 8210-1D, Contractor’s Flight and Ground Operations

p. DCMA-Manual 8210-2 Change 1, Aircraft Operations

q. Department of Defense Directive (DoDD) 4500.54E, Department of Defense (DoD) Foreign Clearance

Program

r. DoDD 5030.61, DoD Airworthiness Policy

s. Department of Defense Instruction (DoDI) 4500.53 DoD Commercial Air Transportation Quality and

Safety Review Program

t. DODI 4540.01 Use of International Airspace by United States (U.S.) Military Aircraft and for Missile and Projectile Firing

u. DoDI 4715.4 Pollution Prevention

v. DoDI 5200.48, Controlled Unclassified Information (CUI)

w. Department of Defense Manual (DoDM) 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

x. DoDM 5220.22-M, National Industrial Security Program Operating Manual (NISPOM)

y. DoDM 8570.01 Information Assurance Workforce Improvement Program

z. Federal Aviation Administration (FAA) Advisory Circular (AC) 00-1.1B, Public Aircraft Operations

— Manned and Unmanned

aa. FAA AC 91-70B Change 1 Oceanic and Remote Continental Airspace Operations

bb. FAA AC 91-91 Maintaining Public Aircraft

cc. FAA Order 8300.16A CHG 1, Major Repair and Alteration Data Approval

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

ee. International Civil Aviation Organization (ICAO), Annex 1-18

ff. ICAO, Annex 19 Safety Management

gg. Military Standard (MIL-STD)-105E Sampling Procedures and Tables for Inspection by Attributes

hh. Military Handbook (MIL-HDBK)-516C DoD Handbook Airworthiness Certification Criteria

ii. National Aeronautical Information Publications (AIPs)

jj. National Security Agency (NSA) Classified National Security Information Program for State, Local, Tribal and Private Sector Entities (Policy Manual 3-16)

kk. National Security Decision Directive (NSDD) 298 Operations Security (OPSEC) Program

ll. NAVAIRINST 13034.1G - NAVAIR Airworthiness and Cybersafe Process Manual

mm. NAVAIRINST 3700.4A, Safe-For-Flight Operations Certification

nn. Naval Supply Systems Command (NAVSUP) Instruction 4200.97A – Policies and Procedures for the

Operation and Management of the Aviation Into-Plane Reimbursement (AIR) Card Program

oo. Naval Operations Instruction (OPNAVINST) 3432.1A, OPSEC

pp. Secretary of the Navy (SECNAV) Instruction M-5510.30C DON Personnel Security Program

* These documents are not publicly releasable (Distribution Statement C or D). These documents will be provided to the awardee 10 days after contract award.

3.0 GENERAL REQUIREMENTS FOR EW JETS

The Contractor shall provide FAA certified aircraft and personnel capable of providing the services outlined in the

PBWS. The Contractor shall utilize Government Furnished Property (GFP) and Government Furnished Mission

Equipment (GME) in accordance with (IAW) Contract Section J, Attachment 5 as well as Contractor Furnished

Equipment (CFE) to meet the EW Jet requirements. The Contractor shall operate its aircraft under the direction of the mission controllers or pre-exercise instructions provided by the Government Scheduling Officer (SO).

The Contractor shall ensure all aircraft are equipped with the communication and navigation capability necessary to operate in the U.S. National, international, or foreign nation airspace as applicable. Within the context that these aircraft may deploy to the locations identified in section 6.6, the Contractor shall comply with other FAA, ICAO or foreign nation equipment pre-requisites and shall be solely responsible for providing such equipment.

3.1 EW Services Performance Requirements

3.1.1 AIC Services

The Contractor shall operate its aircraft under the direction of mission controllers or pre-exercise instructions provided by the SO. The Contractor’s aircraft and personnel shall be capable of flying profiles simulating blue or red force scenarios. Blue force scenarios include intercepting Government aircraft through bearing/range/altitude calls.

Red force scenarios include acting as aircraft that get intercepted or take appropriate actions as directed to avoid interception.

3.1.2 Air Defense and EW Presentations

The Contractor shall operate COCO aircraft to provide Air Defense and EW presentations. Air Defense and EW presentations are typically flown at all altitudes. These missions are under direct control of a designated exercise coordinator. At times, the Contractor will participate in exercises that include supporting aircraft from other CAS providers also carrying pods and/or internal mission equipment to simulate airborne radar systems and/or EA jammers. EW presentations typically consist of a kill chain assessment pass, which begins by simulating a medium altitude threat and escort jammer, then simulating a missile launch and low altitude fly out at targeted vessels.

Services continue by rotating through AST/ ALQ codes and exposing operators to EW jamming equipment as defined in this PBWS in support of the Opposing Force (OPFOR). The Contractor shall support air defense presentations below or above the radar horizon, with the aircraft simulating threats interacting with the training audience through various stages of Rules of Engagement (ROE) including missile fly outs. The Contractor’s similar aircraft shall fly in close formation. The Contractor’s dissimilar aircraft shall fly in a loose tactical wing formation.

3.1.3 Communications Relay Services

The Contractor shall operate its aircraft to provide Communications relay services. Communications relay services are used to enable shore-based communications with the at-sea training audience. The Contractor aircraft typically flies a medium altitude cap at max endurance. The Contractor shall perform airborne encrypted and unencrypted

Ultra High Frequency (UHF), bidirectional, continuous communications relay to include voice and data utilizing

GME systems (e.g., Navy Common Data Link (NCDL) Model 600RLNCDL, Unmanned Aerial Communications

Relay (UACR), Portable Radio Communications (PRC) 158 dual channel radio, Tactical Autonomous Airborne

Relay Package (TAARP)). The Contractor shall have the ability to electronically receive, handle, store in an internal safe (See PBWS Appendix C, Aircraft Capability and Configuration Requirements for storage safe requirements) and load Cryptographic Key Material (KEYMAT) as required IAW with the NSA Classified National Security

Information Program for State, Local, Tribal and Private Sector Entities (Policy Manual 3-16). The communication relay shall not preclude the aircraft’s ability to navigate or communicate on an independent UHF radio.

3.1.4 Test and Evaluation (T&E) Services

The Contractor shall operate its aircraft to provide T&E services. T&E services are used to evaluate the continued effectiveness of Government-owned production assets. Other users include, but are not limited to, NAVAIRSYSCOM, Naval Sea Systems Command (NAVSEASYSCOM), Naval Research Laboratory (NRL), United States Air Force (USAF), and Non-DoD Government agencies.

3.1.5 Target Tow Services

The Contractor shall provide target tow services. The Contractor shall provide and utilize four (4) tow reels. The tow reels must be either RM-30A/A1 or MTR-101 and be operationally staged on the East Coast base (two (2) tow reels) and on the West Coast base (two (2) tow reels). The aircraft must carry and deploy GFP targets, Government furnished cable and other consumable materials. Contractor furnished target towing systems (including cartridges) must be FAA approved for carriage and operation. The Contractor shall obtain and maintain, for the duration of the contract, a Class 1.4 Explosive license through the Bureau of Alcohol, Tobacco, Firearms and Explosives (BATFE) for this purpose.

3.1.6 Banner Tow Services

The Contractor shall provide banner tow services. The aircraft must carry and deploy GFP banners, cables and material. Each banner is laid out with the associated Government-furnished cable (takeoff launch towline) and is paid out upon aircraft takeoff. Upon completion of the banner tow mission, the banner is dropped by the aircraft at a pre-determined location. Banner towing systems must be FAA approved for carriage and operation.

3.1.7 Unmanned Aerial System (UAS) Visual Observer Services

The Contractor shall provide UAS escort aircraft services as requested by the SO. The escort services are required to assist the Navy with meeting DoDI 4540.01 requirements for Due Regard. The escort aircraft must be operated by its own Pilot in Command (PIC), with the Second in Command (SIC) acting as the primary visual observer and will maintain communications with the UAS mission commander. The UAS will normally be operated in Visual

Meteorological Conditions (VMC) but may operate in less than VMC. The UAS may have LSRTU and/or an

Automatic Dependent Surveillance – Broadcast (ADS-B) beacon installed to assist the escort aircraft maintaining situational awareness. The Contractor’s visual observer and PIC must maintain continuous and direct line-of-sight visual observation of the UAS’ and surrounding airspace. The escort PIC shall immediately notify the UAS mission commander and flight controller in the event of a loss of visual contact with the UAS. UAS operate as slowly as 80

Knots Indicated Air Speed (KIAS). The Contractor aircraft shall either perform weaving S turns or fly racetrack around the UAS to maintain situation awareness of the surrounding airspace. As flight following of the escort aircraft is required, the escort aircraft shall have a mode III Identification Friend or Foe (IFF) and may be equipped with LATR or Tactical Combat Training System (TCTS).

3.2 Simultaneous Presentations

The Contractor shall provide aircraft for up to six (6) simultaneous presentations for EAST COAST EW Jet missions and four (4) simultaneous presentations for WEST COAST EW Jet missions. The Contractor shall meet the

Mission Completion Rate (MCR) identified in the Quality Assurance Surveillance Plan (QASP), Attachment 4, Metric 1.

This contract does not require exclusive use of the aircraft. GFP that is installed or is aboard the aircraft shall not be used to conduct operations not related to performance of this contract.

3.2.1 East Coast

The Contractor shall provide a minimum of the below simultaneous presentations on the East Coast. The

Contractor’s aircraft may be reconfigurable for any mission. At the Government’s discretion, these presentations may be:

i. up to six (6) EA; or,

ii. up to five (5) EA, and one (1) TBT; or,

iii. up to four (4) EA, and two (2) TBT

3.2.2 West Coast

The Contractor shall provide a minimum of the below simultaneous presentations on the West Coast. At least two

(2) of the West Coast aircraft must be capable of traveling to Hawaii (HI). The Contractor’s aircraft may be reconfigurable for any mission. At the Government’s discretion, these presentations may be:

i. up to four (4) EA; or,

ii. up to three (3) EA, and one (1) TBT; or,

iii. up to two (2) EA, and two (2) TBT

3.3 EW Jet Aircraft Capability and Configuration Requirements

The Contractor shall base aircraft IAW PBWS Section 6.0. The Contractor shall ferry aircraft to and from mission locations. The Government will reimburse per ferry flight minute. A subset of the flight operations required by EW

Jet tasking will be Civil Aircraft Operations (CAO) and be conducted within the 14 CFR. However; the majority of flight operations will be Public Aircraft Operations (PAO) and require the Contractor to operate their aircraft in

Public Aircraft status. The Contractor shall provide the FAA a copy of their PAO Declaration Letter prior to conducting a PAO mission. All Public Aircraft flights must be preapproved by the Government Flight

Representative (GFR) IAW PBWS section 4.1.6. All mission requirements shall be either CAO or PAO and not a combination thereof and is identified prior to each mission under the applicable Task Order (TO). EW Jet Aircraft

Capability and Configuration Requirements are identified in PBWS Appendix C and Interface Reference Document

(IRD) (Contract Section J, Attachment 2).

3.4 EW Jet GFP/GME Installation Requirements

The Contractor shall install and remove GFP/GME listed in Contract Section J, Attachment 5 from aircraft as identified at the TO level. The Contractor shall install and maintain GFP/GME systems IAW the aircraft’s airframe, engine, and avionics manufacturer’s specifications. Additional installation requirements are identified in the IRD

(Contract Section J, Attachment 2).

3.5 EW Jet Aircraft Mission Controller and Profiles

The Contractor shall fly missions as defined by the SO at locations specified at the TO level.

3.5.1 Mission Profiles

The aircraft mission profiles below represent the typical operation profiles conducted in a training environment. The

Contractor shall provide aircraft capable of meeting the mission criteria provided below IAW the aircraft requirements in PBWS Appendix C and the IRD (Contract Section J, Attachment 2). Specific training scenarios are subject to change based on the mission profiles at the request of the customer (See PBWS Section 4.1.4 Scheduling).

All mission profiles are at “Standard Day” conditions (see Appendix A for Standard Day definition).

3.5.1.1 EA Mission Profiles

TABLE 1

EA Profile Including Start, Taxi, Takeoff, then climb to cruising altitude of 20,000 ft.

Mean Sea Level (MSL) and transit 150 Nautical Miles (NM) at max range airspeed to push point. Continue level transit 100 NM at 300 KIAS, then simulate 100 NM missile launch/fly out (descend to 200 ft. MSL at 4,000 ft./min rate of descent within 25 NM, then completing the remaining transit at

300 KIAS). Off target, aircraft will Return to Base (RTB) by climbing 20,000

ft. and transit 350 NM at max range airspeed and normal descent for recovery.

Total range for the profile is 700 NM.

For Drag Count calculations: Aircraft in proposed mission configuration including an AST-9 and ALQ-167 pod on the wings.

NOTE: EA equipped aircraft must be capable of flying in tactical wing formation for escort missions.

3.5.1.2 TBT Mission Profiles

TABLE 2

Target Tow Profile Including Start, Taxi, Takeoff, then climb to cruising altitude of 20,000 ft. MSL and transit 150 NM at max range airspeed to rendezvous with ship/aircraft. Fly an additional 80 minutes at 3,500 ft. to 15,000 ft. MSL at airspeeds between 200-

250 KIAS which includes streaming the target, providing services, and retrieving the target. Aircraft will then RTB 150 NM at max range airspeed and normal descent.

including a RM-30A/A1 or MTR-101.

Banner Tow Profile Including Start, Taxi, Takeoff, then climb to cruising altitude and transit to rendezvous with ship/aircraft at maximum airspeed of 200 KIAS. Fly additional minutes at airspeeds between 200-250 KIAS at 8,000 ft. to 13,000 ft. MSL which includes providing the banner services. Aircraft will then RTB at max airspeed of

200 KIAS and normal descent and drop the banner at designated drop zone.

Aircraft must be capable of a 2-hour total flight time.

including associated hardware/banner.

3.5.1.3 UAS Visual Observer Profiles

TABLE 3

MQM-170C Outlaw

Escort

During launch the UAS ground team visually observe the UAS until the

Contract aircraft report visual on the UAS. Once the Contractor aircraft has a visual on the UAS, the aircraft will escort the UAS through U.S. National

Airspace and warning areas while remaining within visual proximity of the

UAS. The Outlaw will typically transit between 80 and 95 KIAS and at 1000 ft MSL. The Contractor escort aircraft will typically fly 200 ft above the UAS and either perform S turns weave or fly racetrack around the UAS to maintain situation awareness of the surrounding airspace. The Contractor aircraft shall make Guard calls (243.00 MHZ) to alert other aircraft of the UAS presence in the operating area and shall make altitude and heading change recommendations to the UAS mission commander to assist in traffic avoidance or maintaining VMC.

MQ-9 Reaper

Escort

The Reaper will typically launch in U.S. National Airspace and transit to the warning areas under an FAA Certificate of Waiver or Authorization (COA) at about 150 KIAS and above Flight Level (FL) 180. The Reaper will then hold until the Contractor aircraft establishes communications and visual. The

Reaper will typically have a mode III squawk to assist the Contractor escort in maintaining situational awareness. The Contractor aircraft will typically fly

500 ft above the UAS and fly a racetrack around the UAS to maintain situational awareness of the surrounding airspace. Reaper escorts missions may be as far as 300 nm.

3.6 Capability Stand Up

The Contractor shall complete a Capability Stand Up period per the requirements identified in PBWS sections 3.6.1 through 3.6.10. Capability Stand Up consists of achieving Initial Operating Capability (IOC) and Full Operating

Capability (FOC). The Government will conduct a Physical Configuration Audit (PCA) and a Functional

Configuration Audit (FCA) (PBWS section 3.7.1.4) for at least the first aircraft in each Type/Model/Series (T/M/S) of aircraft utilized during Capability Stand Up. Also, throughout the Capability Stand Up process, it is the

Contractor’s responsibility to continuously work with the GFR to ensure that aircraft capabilities, pilot training and associated procedures will align to the Integrated Master Schedule (IMS) stated timeline (PBWS section 3.6.4) prior to conducting Public Aircraft flights.

3.6.1 IOC

To meet IOC the Contractor shall possess (own or lease) at least four (4) unmodified aircraft at time of contract award capable of meeting EW Jet Aircraft Capability and Configuration Requirements as identified in PBWS

Appendix C and Interface Reference Document (IRD) (Contract Section J, Attachment 2).

3.6.2 FOC

FOC shall be completed no later than 24 months from award of the contract. The Contractor’s aircraft will comply with the aircraft configuration requirements listed in Appendix C, Tables 3 and 4 to meet FOC, to include installation of GFP IAW PBWS section 3.4. FOC consists of a minimum of 10 EA aircraft which includes four (4) aircraft configured for TBT missions. At FOC, all aircraft shall be provided in the FOC configurations (PBWS

Appendix C, Tables 3 and 4) and operated from the East and West Coast (PBWS section 6.0) to meet simultaneous presentation requirements (PBWS Section 3.2). The Contractor shall provide a test report validating platform performance with required equipment IAW this PBWS for Government approval (Contract Exhibit A, Contract

Data Requirements List (CDRL) A001) to achieve FOC.

As individual Contractor aircraft reach FOC as determined by the Government (IAW PBWS sections 3.6.1 through

3.6.10), the Government may award TOs for EW missions.

3.6.3 NAVAIR Interim Flight Clearance (IFC)

The Contractor shall obtain a NAVAIR IFC as identified in PBWS sections 3.7.3.3 and 3.7.3.4 prior to achieving

FOC. The Contractor should plan for 45 calendar days after completion of aircraft modifications and Government receipt and approval of data identified in Contract Exhibit A, CDRL A002 for initial and each subsequent

NAVAIR IFC release.

3.6.4 IMS

The Contractor shall deliver an IMS IAW Contract Exhibit A, CDRL A003. This IMS shall include all required tasks necessary to complete the Capability Stand Up effort and achieve FOC. If applicable, the IMS shall include the following:

- The aircraft acquisition and import plan for each aircraft proposed

- An aircraft regeneration plan for aircraft which are not currently airworthy detailing efforts required to bring the aircraft into flyable status

- An aircraft modification plan for each aircraft that requires modifications to meet the requirements of

PBWS paragraph 3.0, Appendix C and the IRD (Contract Section J, Attachment 2).

The Contractor shall include each aircraft intended to conduct missions under this contract. At a minimum, the schedule shall be inclusive of the following plans and major milestones (if applicable):

3.6.4.1 Aircraft Acquisition and Airworthiness

i. Aircraft Acquisition(s)

ii. Obtain FAA Airworthiness Certificate(s)

iii. Aircraft(s) to Modification Facility (if applicable)

3.6.4.2 Aircraft(s) Modification Plan

i. Dates of Required Modification Kits Available and Complete

ii. Modification Start Date(s)

iii. Significant Modification Events

iv. Flight Testing or Functional Checks of all Aircraft

v. Aircraft(s) Modification Completion Date(s)

3.6.4.3 Approvals and Flight Plan

i. Obtain Approved Civil Aircraft Landing Permit (CALP)

ii. Aircraft Flight to Basing Location (see PBWS section 6.0)

3.6.5 The Contractor shall submit all Airworthiness Substantiation Data, as required by the Airworthiness

Checklist (Contract Section J, Attachment 6), IAW Contract Exhibit A, CDRL A002.

3.6.6 For operations determined as PAO by PMA-226 (See PBWS section 3.7.3.2):

3.6.6.1 PMA-226 Engineering or the COR will provide the Contractor with an approved PAO Assessment

/ Determination letter.

3.6.6.2 The Contractor shall develop and submit the following documents to the GFR for approval:

i. Flight Operating Procedures (FOPs) (see PBWS section 3.7.5) IAW Contract Exhibit A, CDRL A002

ii. Ground Operating Procedures (GOPs) (see PBWS section 3.7.5) IAW Contract Exhibit A, CDRL A002

iii. Safety Program

iv. Mishap Response Plan (see PBWS section 4.2.3.1) IAW Contract Exhibit A, CDRL A00A

v. Applicable Pilot and Maintainer Training Programs

3.6.6.3 Upon completing an initial GFR inspection, the Contractor shall be required to complete a Safe for

Flight (SFF) inspection IAW NAVAIRINST 3700.4. The Contractor shall address or mitigate all

SFF Team findings or non-conformances prior to conducting Public Aircraft operations; a SFF determination will be provided by the NAVAIR SFF team prior to conducting PAO. SFF is also required when any of the circumstances in PBWS section 3.7.4.2 apply.

3.6.7 The Contractor shall complete required Fuel Card training and obtain Government-issued Fuel cards (see

PBWS section 4.2.2) for each aircraft operating under this contract.

3.6.8 The Contractor shall obtain required CALPs (see PBWS section 4.2.6) to achieve FOC.

3.6.9 The Contractor shall have a SECRET facility clearance prior to completion of FOC. Security clearance requirements are identified in PBWS section 7.0 and the DD Form 254 (Contract Section J, Attachment 3).

3.6.10 The Contractor shall provide and position aircraft (PBWS 6.0) capable of meeting the Aircraft Performance and Configuration requirements (Appendix C Tables 3 and 4) stated herein.

3.7 Aircraft Certification and Maintenance

3.7.1 The Contractor shall ensure all aircraft are certified, maintained, and operated IAW 14 CFR, its NAVAIR

IFC, and PBWS Section 2.0 Applicable Documents.

3.7.2 FAA Airworthiness and Related Substantiation Data (Contract Exhibit A, CDRL A002)

All Contractor aircraft must possess a current FAA Airworthiness Certificate. The Contractor shall provide a copy of

FAA certificates and all other related airworthiness substantiation data for review IAW Contract Exhibit A, CDRL

A002. The Contractor shall comply with all Airworthiness Directives (AD) and service bulletins for mission effectiveness.

3.7.2.1 FAA Standard and/or Special Restricted Category Airworthiness Certificates

Aircraft must possess a current FAA Standard and/or Special Restricted Category Airworthiness

Certificates, and the Contractor shall maintain the aircraft IAW 14 CFR § 43. 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 IAW Contract Exhibit A, CDRL A002. 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. The

Contractor shall demonstrate that major alterations to aircraft with Standard and/or Special Restricted

Category Airworthiness Certificates were 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.

3.7.3 NAVAIR Airworthiness and Supporting Data

3.7.3.1 Contractor Airworthiness Representative

The Contractor shall provide a single point of contact to manage the airworthiness certifications and to coordinate Contractor and Government certification efforts during any significant aircraft modification requiring a new or updated NAVAIR IFC.

3.7.3.2 CAO and Public Aircraft Status

The flight operations required by this contract are generally assessed as PAO and shall abide by all FAA

"Public Use" notification procedures. However, for missions not declared as Public, the Contractor’s flight operations shall be conducted IAW14 CFR.

3.7.3.3 IFC

All aircraft under this contract require a NAVAIR issued IFC (See NAVAIRINST 13034.1G). All flights conducted under a NAVAIR IFC, including operations outside of U.S. National Airspace, shall be approved by the designated GFR. The Contractor shall provide airworthiness substantiation data IAW this

PBWS, Contract Exhibit A, CDRL A002 and as required by NAVAIR. If additional substantiation data is required during the Government’s review, the Contractor shall deliver the data IAW the timelines identified in CDRL A002.

3.7.3.4 PCA and FCA

The Contractor shall support a Government lead PCA and FCA to support a NAVAIR Airworthiness evaluation prior to NAVAIR IFC issuance. The purpose of these audits is to formally examine the ready-to-operate aircraft and verify the accuracy of the aircraft's configuration as described by the documentation provided in support of the aircraft's IFC. The PCA and FCA provide confirmation that the contractor is meeting the requirements as defined by the PBWS. The Government will conduct an onsite aircraft assessment for each T/M/S that is fully configured to meet the performance requirements of the PBWS.

3.7.3.5 Notification of Proposed Aircraft Changes

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, minimum essential equipment, or operating limitations and procedures prior to any change made. The

Government will assess the changes and determine if modifications to the NAVAIR-issued IFC are warranted. The Contractor shall provide airworthiness substantiation data IAW Contract Exhibit A, CDRL A002 for the proposed change.

3.7.4 Policy and Procedures

3.7.4.1 GFR / Ground-GFR (GGFR) Inspections

Per DCMAINST 8210.1D / NAVAIRINST 3710.1H, GFRs are responsible for oversight and surveillance of contractor aircraft flight and ground operations. The designated GFR or Alternate GFR will perform reoccurring surveys of the contractor’s flight and ground operating procedures (FOPs and GOPs) to determine if they are safe and effective. Prior to the contractor’s initial NAVAIR Safe-for-Flight (SFF) evaluation, the GFR must review and approve the contractor’s FOPs and GOPs IAW DCMAINST

8210.1D.

The designated PMA-226 GFR, or Alternate GFR, will conduct a survey prior to the start of contracted flight operations. The results of that survey will be forwarded to the NAVAIR SFF team for review prior to their SFF evaluation. When the SFF team has determined the contractor has been approved SFF or

Conditionally-SFF, the contractor can begin contracted flight and ground operations. Once contractor operations begin, the GFR, or Alternate GFR, will conduct reoccurring surveys IAW DCMAINST

8210.1D. During the GFR survey, the GFR will assess the contractor’s compliance with its approved

FOPs/GOPs, applicable Service guidance, and applicable sections of the contract.

At the conclusion of each subsequent survey, the GFR will send the results documenting contractor observations and discrepancies to the Administrative Contracting Officer (ACO). Within 5 working days, the ACO will make comments, endorse the survey, and forward it to the contractor. If, after those 5 working days, there is no response from the ACO, the GFR (or Alternate GFR) is authorized to forward the survey results to the contractor. The contractor then has 30 days (unless a specific case warrants other action) to resolve any reported discrepancies or non-compliance and shall revise their FOPS and GOPS with the appropriate corrective actions. All FOPs and GOPs manual revisions shall be submitted to the

GFR within 30-days of the contractor receiving the final GFR survey results, unless otherwise determined by the GFR.

3.7.4.2 NAVAIR SFF Inspections

A NAVAIR SFF inspection shall be conducted IAW NAVAIR INST 3700.4 prior to the start of PAO. The

COR or GFR will advise the SFF when the contractor is ready for their SFF assessment. Contracted flight operations will not begin until the SFF team has issued a SFF determination. Additionally, a new SFF inspection shall be conducted if any of the following occur during the contract ordering period:

i. The Contractor relocates to a new facility, airport, or location that has not been previously evaluated by the SFF team and where such contracted flight operations or maintenance will be conducted for more than 30-days in a FY (fiscal year); or,

ii. A new aircraft type or T/M/S is being used to support the contracted mission (“aircraft type” as defined by the FAA); or,

iii. A new kind of contracted service or mission is being requested of the Contractor; or,

iv. A new contract is awarded (with a new contract number)

The Contractor shall take the necessary steps to resolve any reported findings of non-compliance and shall revise their procedures manual to avoid such findings in the future. All procedure manual revisions shall be submitted to the GFR within 30-days of receiving the final inspection results.

3.7.4.3 Management Plan (MP) and Procedures

The Contractor’s management policy and procedures shall ensure that contract execution and quality control are effective and in continuous compliance with DCMA INST 8210-1D. The Contractor’s policies and procedures shall allow for biannual Government management review of the quality system to ensure effective development, implementation, and execution of processes, systems, and requirements for support of and compliance with all contractual requirements. The Contractor shall develop and execute a specific written MP to address all ground and flight operation items and submit it IAW DCMA INST 8210-1D

(Contract Exhibit A, CDRL A004) for approval. The Contractor shall be responsible for writing, implementing, and enforcing its procedures and for identifying and correcting deficiencies noted by the

GFR. The procedures shall describe aircraft ground and flight operations required IAW DCMA INST

8210-1D. If the Contractor references documents, such as existing company procedures, and operating instructions in these procedures, the referenced documents shall be made readily available for review and become part of the GFR approval process. If the Contractor possesses a 14 CFR § 121 or 135 operating certificate, the associated FAA-approved § 121 or §135 procedures may be used to satisfy the applicable portions of the FOPs and GOPs.

3.7.4.4 NAVAIR Aviation Maintenance Management Team (AMMT) Inspections

The NAVAIR AMMT will perform an inspection of the Contractor’s aircraft, maintenance facilities, maintenance records, and GOPs within 12-24 months after a Contractor begins performing on contract, and then every 12-24 months thereafter. The AMMT inspection shall be performed at each Contractor facility where maintenance is performed on aircraft possessing a NAVAIR IFC. The Contractor will receive a report at the conclusion of each AMMT inspection and shall follow the AMMT team’s direction in resolving any reported findings.

3.7.5 FOPs and GOPs (Contract Exhibit A, CDRL A002)

The Contractor shall establish standard FOPs and GOPs IAW DCMA INST 8210-1D and ensure compliance with all applicable 14 CFR, ICAO Standards, and the civil aviation regulations of the country(s) of intended operation.

Procedures must be up to date and reflect the current scope of operations. FOPs and GOPs, and any revisions, shall be approved by the GFR prior to use. FOPs/GOPs shall be developed and IAW DCMA INST 8210-1D and submitted to the GFR for review and approval 30 days after contract award IAW Contract Exhibit A, CDRL

A002. The FOPs, which includes the pilot training program, must provide mission-specific training for close formation, low altitude and TBT flights. Training is expected to be conducted as CAO and therefore the Contractor must obtain all required FAA authorizations to conduct such training flights.

The Contractor shall comply with its GFR-approved FOPs and GOPs and shall be responsible for identifying and correcting deficiencies for both Contractor and Subcontractor operations. The Contractor shall be responsible for ensuring its Subcontractors’ aircraft operations under this contract are conducted IAW with the prime Contractor’s contract and GFR approved GOPs and GOPs.

3.8 Aircraft Modifications

When ordered by a TO that contains Contract Line-Item Number (CLIN) 0009, the Contractor shall be required to modify their aircraft to incorporate new capabilities. These capabilities may include modifications such as the installation and/or removal of additional GFP and GME not previously identified at contract award or during

Capability Stand Up to enhance EW Jet services. The contractor may be required to perform aircraft modifications such as internal/external modifications, special provisioning, antenna mounting, etc. Final modifications are approved by Supplemental Type Certificate (STC) signed FAA Form 8110-3 and FAA Form 337. Aircraft modifications may drive a requirement to obtain new NAVAIR IFC(s), see PBWS Section 3.7.3.3.

4.0 OPERATIONAL REQUIREMENTS

4.1 Mission Planning

4.1.1 The designated SOs will execute administrative tasks such as mission scheduling and coordination, travel order issuance and reconciliation, and invoice certification. The SO will authorize all flight operations and communicate requirements through the designated Contractor Representative (CR). The CR shall coordinate with the SO on all formal requests for services (for missions under an active TO) to determine feasibility of support, associated cost of support, implications of support on other scheduled or potentially scheduled missions, and any other necessary details requiring coordination. The CR shall coordinate scheduled and planned maintenance requirements that may preclude aircraft availability at least 14 calendar days in advance with the SO to avoid conflicts with mission event scheduling. The CR shall inform the Government upon any determination that aircraft are not available to meet assigned or future missions, via email to the COR and SO. The EW Jet flight crew shall attend customer pilot mission briefs that include detailed information on the mission profile to facilitate mission execution. As required by the SO, the CR shall attend the pilot mission brief. The CR shall coordinate ground and flight crew daily schedules as necessary to meet the operational tasking of the SO (the SO schedules tasking IAW

PBWS section 4.1.4).

4.1.1.1 The SO at Fleet Area Control Surveillance Facility (FACSFAC) Virginia Capes (VACAPES), Virginia (VA), will coordinate the United States Navy (USN) and FMS Fleet requirements and schedule all USN and FMS Fleet missions for the east coast.

4.1.1.2 The SO at FACSFAC San Diego, California (CA) will coordinate the USN and FMS Fleet requirements and schedule all USN and FMS Fleet missions for the west coast.

4.1.1.3 The SO at PMA-226 Patuxent River, Maryland (MD), office will coordinate all other contract flight requirements schedules, and missions not scheduled or coordinated by FACSFAC

VACAPES or FACSFAC San Diego CA.

4.1.2 The Contractor’s designated CR shall coordinate with the appropriate SO on all formal requests for CAS to determine feasibility of support, associated quantity of flight minutes, estimated travel requirements and expenses, implications of support on other scheduled or potentially scheduled mission and any other necessary details requiring coordination with the objective of executing successful missions. The CR shall provide scheduling support

24 hours a day, seven days a week, to include rapid response to SO inquires (1 hour) after duty hours via internet electronic mail account or phone (land-line or mobile). The CR shall have authority to schedule and assign

Contractor aircraft and crews in response to Government requirements.

4.1.3 The CR shall serve as liaison between the Government SO and the Contractor’s personnel, and shall:

4.1.3.1 Communicate with the SO weekly regarding the Contractor’s aircraft availability and scheduled down time; if the number of available aircraft falls below the requirements of PBWS section 3.2 the SO shall be notified immediately.

4.1.3.2 Provide Contractor flight crews with any additional mission information and details of tasking, as needed.

4.1.3.3 Obtain exercise scheduling and operational procedures from the supported units and in turn provide these requirements to the Contractor flight crew for their compliance.

4.1.3.4 Provide a comprehensive post mission debrief and other feedback as requested by the SO or COR at the conclusion of each mission to assist with effective and efficient utilization of Contractor assets for future events.

4.1.4 Scheduling

The Contractor shall utilize a CR-monitored system or process that evaluates operational risks, experience levels of crewmembers, and ensures the proper pairing of aircrews on all flights. All crewmember flight, duty, and rest requirements shall adhere to DCMA INST 8210-1D, and if applicable to the Contractor, 14 CFR. The Contractor shall support the following operations: 1) Normal flight operations (operations flown from home base (east or west coast)); 2) Remain Over Night (RON) missions originating from home base to a detachment site (operational locations away from a home base); 3) Fleet exercises (named events normally associated with CSG-4/CSG-15 requiring operations from home base and detachment sites);, or 4) Any combination thereof. Scheduling will be accomplished through weekly and long-range schedules as described below.

4.1.4.1 The Contractor shall support normal scheduling for flight operations, which is typically Monday through Friday, 0600 to 2000 local time (where the missions are occurring, east or west coast).

- However, during fleet exercises, the Contractor shall support flight operations which could occur at any time, 24 hours a day/seven days a week. Notwithstanding other requirements of this PBWS, the Government may schedule flight operations at any time, 24 hours a day/seven days a week. The weekly schedule provided by the SO will identify when operations are required, to include events outside of the normal operating schedule or that are of longer duration than 12 hours per day.

- For home base operations which are not exercise related, the Government will give the

Contractor a minimum of 24 hours’ advance notice for any changes to the published weekly schedule / 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; however, once the baseline weekly schedule is published (published on

Wednesday for Monday through Sunday the following week), there is no requirement for the

Contractor to support short notice tasking (less than 24 hours' notice for non-exercise events) to meet emergent requirements in that same scheduling week.

4.1.4.2 The SO shall provide the CR with a long range (revolving one-year planning calendar) schedule depicting requirements in calendar days, expected number of missions, and supporting unit(s) to facilitate direct communication between the CR and the end user. The CR shall communicate scheduled maintenance requirements that preclude availability of any aircraft at least 30 calendar days prior to any scheduled maintenance activity. The Government will not make any special scheduling arrangements or considerations to meet the Contractor’s maintenance requirements.

During non-scheduled maintenance or if the Contractor is unable to meet the published flight schedule (missions cannot be met), the Contractor shall inform the Government as soon as possible via email or phone to the SO and additionally for Public Aircraft missions the GFR. Any missed missions may count against the QASP, Attachment 4.

4.1.4.3 The long-range schedule will provide the expected airfield location proposed for detachment exercises. The weekly schedule will update any changes to the proposed detachment locations as requirement or schedule changes emerge during exercise execution. During fleet exercises, the contractor may conduct operations using their home base and/or detachment airfields. During a detachment operational exercise, the Government will provide the Contractor a 12-hour expedited advance notice (via phone, text or email) for any change affecting their tasking for operations out of the Contractor’s home base or detachment site and issue an update to the weekly schedule. This

12-hour advance notice is for days that already have a Contractor flight scheduled (fly day). The

Government will follow compliance with crew/duty day requirements before issuing a tasking change during detachment operations since aircrew are deployed with the aircraft. Operations out of the home base may require additional time to identify aircrew and generate aircraft availability to support the “new add,” thus the Government will provide a minimum of 24 hours’ notice for changes to home base operations to schedule aircrew during an exercise day that was previously a scheduled no fly day.

4.1.4.4 If the Contractor is supporting missions at a detachment site and the SO determines that repositioning the Contractor’s aircraft is needed to better support the event, the SO will provide at least 18 hours’ notice before the redeployment is to occur (this accounts for logistics and management concerns). Operations may begin at one detachment airfield and end at another detachment airfield. Thus, a reposition change is 18 hours’ notification, whereas a schedule only change (event time, mission, etc) is a 12 hour’s notification (no change in detachment airfield).

Detachment operations can be conducted at a civilian or military airfield that the SO (with assistance from the CR) has determined as the best suited airfield to meet the mission requirements for the exercise duration. Final approval for detachment site use remains with the

SO. The SO will consider the runway length, density altitudes for the time of year, fueling capacity, anticipated turnaround services, and proximity to operations when selecting a detachment site. The Contractor shall plan, schedule, ship, and deploy its personnel and equipment, including all GFP/GME when directed by the SO in writing, as applicable. At least

14 calendar days prior to detachments (normally 30 calendar days), the SO will release a pre-detachment message to the airfields that are intended for use by the Contractor to ensure coordination of requirements, services, and accommodations can be met.

During periods of intensive test operations or major fleet exercises, flight operations may run in excess of 12 hours a day, seven days a week for up to four weeks in length, although large fleet exercise detachments do not normally exceed 14 days. When detachments exceed seven days, consist of high tempo operations, or extended fly days are anticipated, the Government will notify the Contractor at least 14 calendar days in advance. These events are included on the

SO’s long range schedule. Additionally, the Government will provide the CR the actual schedule of events for intensive test operations or major fleet exercises a minimum of 14 days before the first fly day and update as necessary as the schedule is refined. CSG-4's larger fleet exercises

(e.g. Composite Training Unit Exercise (C2X)) may also warrant a face-to-face Concept of

Operations (CONOPS) meeting with the exercise planners which normally include Contractor detachment aircrew and maintenance leads.

If the Contractor requests to substitute aircraft or aircrew during a scheduled detachment, all costs associated with the substitution, (e.g. transit of aircraft or aircrew to/from the detachment base) shall be entirely at the Contractor’s expense. Before commencement of fleet exercises or detachment operations, planning between the CR, SO, and end user/exercise planner should identify the specific requirements.

4.1.4.5 The CR shall coordinate ground and flight crew daily schedules as necessary to meet the operational tasking of the SO. Additionally, the Contractor shall immediately inform the SO and

COR if any aircraft are unable to meet any missions. Any missed missions may count against the

QASP, Attachment 4, Metric 1.

4.1.4.6 The Government reserves the right to cancel or not schedule flight services on any given day where flight operations are scheduled.

4.1.4.7 If the Contractor cancels a mission during Mission Flight Time (see Appendix A), the Contractor is not authorized to submit an invoice for any of the minutes flown during the cancelled mission unless the mission was partially completed prior to the moment of cancellation and with the written approval of the SO. The Government may count any scheduled flights canceled by the

Contractor towards the minimum guaranteed minutes (see Clause 5252.216-9506 Minimum and

Maximum Quantities) even when those minutes are not invoiced.

4.1.4.8 The Contractor aircraft and personnel shall remain at the detachment site until released by the SO at the conclusion of the event or directed to an alternate detachment site.

4.1.5 Shipment of Equipment

Actual…