PWS - Performance Work Statement - Chase Aircraft Supporting FTU Operations.pdf

Performance Work Statement (PWS)

Project Title: GRAY FLAG 2026 CHASE AIRCRAFT SUPPORT

Organization: 163d Attack Wing, California Air National Guard

Date: 18 Aug 2026

1.0 Introduction & Background

This Performance Work Statement (PWS) defines the requirements for a contractor to provide chase aircraft support for Remotely Piloted Aircraft (RPA) operations conducted by the 163rd

Attack Wing, California Air National Guard, based at March Air Reserve Base (KRIV). The primary and single most important objective of this support is to ensure the safety of non-participating aircraft during RPA takeoff, landing, and transit to and from restricted airspace.

2.0 Scope of Work

The contractor shall provide a fully mission-capable chase aircraft, along with a qualified pilot and observer crew, to accompany the RPA during all phases of flight outside of restricted airspace. This includes takeoff, traffic pattern operations, transit along established routes, and recovery. The chase crew is responsible for uninterrupted visual scanning, collision avoidance, maintaining communication with both the RPA and Air Traffic Control (ATC), and executing all procedures outlined in this PWS.

3.0 Applicable Documents

The following documents govern the performance of this PWS. The contractor shall maintain copies of the latest versions of these documents as applicable.

• Current Federal Aviation Administration (FAA) Certificate of Authorization (COA) for

RPA operations.

• Current Letter of Agreement (LOA) between the 163rd Operations Group and 425th

Operations Group.

• Air Force Instruction (AFI) 11-2MQ-1 and 9 Vol. 3 (to be provided by 163d ATKW).

• Title 14 Code of Federal Regulations (CFR), specifically Parts 61, 67, and 91.

4.0 Specific Tasks and Requirements

4.1 General Flight Operations

• Takeoff & Transit: The chase aircraft shall be overhead March ARB (KRIV) at the scheduled RPA takeoff time. The chase will accompany the RPA during pattern operations and transit to restricted airspace (R-2515 or R-2503) per the current COA and

LOA. After drop-off, the chase will return to base and remain on standby.

• Recovery: The chase aircraft will report to the designated pick-up point (R-2515 or R-

2503) 10 minutes prior to the scheduled handover time and orbit. Upon clearance, the chase will rejoin the RPA and escort it back to KRIV, remaining in formation until the

RPA completes a full-stop landing.

• Transfer of Control: The chase will maintain visual responsibility until the RPA enters the KRIV traffic pattern and a ground observer officially takes over visual responsibilities.

4.2 Safety of Flight

• The chase crew must provide uninterrupted visual scanning of the flight path in front of and on all sides of the RPA.

• If a possible flight conflict is observed, the chase shall immediately contact the RPA with a clear, concise, and directive order to maneuver for conflict avoidance (e.g., “RPA 1234 this is Chase, turn right.”). This order will be repeated if not immediately executed.

4.3 Scheduling and Ordering

• Scheduled Operations: Expected days of operation are 29, 30, and 31 July. Daily schedules will be provided to the chase aircraft crew by 1600 local time the day prior to scheduled flying. Expected days of operation are subject to change.

• Emergency Standby: While the RPA is in restricted airspace, the chase crew will maintain standby status, defined as the ability to be at the designated handover point within 30 minutes (R-2515/R-2503) or 40 minutes (R-2501) of notification.

4.4 Contractor-Furnished Aircraft & Equipment Requirements

• Performance: Capable of a sustained speed of 150 knots true airspeed at an altitude of

12,000 feet and below.

• Communication: Equipped with radios capable of communicating on two separate frequencies simultaneously (one for RPA inter-plane, one for ATC).

• Insurance & Liability: All chase aircraft shall be fully insured. The Contractor is solely responsible for damages to the aircraft or personnel. Absent Government negligence, the

Government shall not be held liable for any damages sustained by the contractor.

• Onboard Equipment:

o Chase and RPA will operate beacons and strobe lights during both day and night operations.

o The RPA will squawk the assigned formation transponder code. The chase will set its transponder to 'standby' with the same code, ready to transmit if the RPA's transponder fails.

o All onboard equipment must comply with FAA standards.

4.5 Contractor Personnel & Qualifications

• General: Only pilots and observers submitted in the contractor's proposal may be used.

Any changes or substitutions require prior written approval from the Ordering Officer.

Resumes for all personnel must be submitted to the Government.

• Crew Composition: Standard operations require one (1) chase-qualified pilot and one

(1) chase-qualified observer. Two (2) qualified chase pilots are required when oxygen use is mandated by FAA regulations.

• Crew Responsibilities:

o Chase Pilot: Responsible for aircraft control and visual separation with the RPA.

o Chase Observer: Responsible for clearing for traffic and advising the RPA of potential conflicts or deteriorating weather.

• Pilot Qualifications:

o Must hold all certifications, ratings, and endorsements required by 14 CFR to act as Pilot in Command.

o Possess a current airman medical certificate (FAA Class 2 or military equivalent) per 14 CFR 67.

o Must be current per 14 CFR 61.56 (Flight Review) and 61.57 (Recent Flight

Experience).

o Shall comply with 14 CFR 91.17 regarding alcohol and drug use.

• Observer Qualifications:

o Must have a comprehensive understanding of federal aviation regulations for the operational airspace.

o Shall not perform crew duties for more than one RPA at a time, nor perform concurrent duties as both a pilot and observer.

o Possess a valid FAA Class 2 medical certificate per 14 CFR 67.

o Shall comply with 14 CFR 91.17 regarding alcohol and drug use.

4.6 Flight Parameters & Minimums

Parameter Requirement

Weather

Operations will be conducted in Visual Meteorological Conditions (VMC) from

9,500 ft MSL to the surface. Standard cloud clearance applies. For rejoins under a ceiling, minimums are 1,000 ft ceiling and 3 NM visibility.

Altitude Chase aircraft will not operate below 500 feet Above Ground Level (AGL) during enroute procedures.

Distance Maintain a distance of 300 to 1,500 feet from the RPA. The ideal position is slightly higher or lower, 20 to 45 degrees left or right of the RPA's center.

5.0 Operational & Emergency Procedures

5.1 Communication Procedures

• Two-way radio communication shall be maintained between the chase and RPA at all times.

• A radio check will be accomplished every 10 minutes if no other communications have occurred.

• RPA Calls: The RPA will call out all altitude/airspeed changes, all turns in close formation, and its descent to the airport.

• Chase Calls: The chase will call prior to entering Class C/D airspace, report positions in the pattern, report RPA gear status, call "in position," and relay ATC communications as needed.

• Frequency Change: Upon each frequency change, the chase will verify the RPA has followed by calling "Grizzly Check," to which the RPA will respond "Two."

5.2 Join-Up Procedures

• Initial Takeoff: Chase will orbit southeast of KRIV (or as directed) at 2,500 ft MSL.

When ready, the chase will call “Ready for departure.” After confirming the departure route with the RPA, the chase will maneuver to join the formation and call “In position.”

• Airborne Join-Up: Chase will acquire the RPA's position and altitude, then climb to maintain 500 feet below the RPA while visually scanning. Once joined, the chase will call "In position."

5.3 Range Procedures

• Range Drop-Off (from KRIV): Chase will follow the RPA on a Runway 32 departure, climbing to 8,500 ft MSL on the WOLFSKILL VFR Departure. Chase will monitor communications until the RPA establishes contact with the range controlling agency, then break formation upon the RPA's request within R-2515/R-2503 and return to base for standby.

• Range Pick-Up: Chase will depart KVCV/KAPV to arrive at the pick-up point on time, climbing to 9,000 ft MSL (500 ft above the RPA). After contacting ATC and making radio contact with the RPA, the chase will visually acquire the RPA (requesting radar vectors if needed), call "have visual," complete join-up procedures, and call "In position."

5.4 Night Chase Procedures

• The contractor shall provide training to crews on night formation flight, spatial disorientation, and collision avoidance.

• Prior to launch for night operations, the chase crew will check in with the Supervisor of

Flying (SOF) for a formal crew briefing.

• The contractor must be able to support short-notice night missions, having an aircraft overhead KRIV within six (6) hours of notification.

5.5 Lost Communications

• Chase Detects Loss: Chase will continue the mission while attempting to re-establish communications (e.g., asking RPA to raise a wing if they can hear, making blind calls).

Chase will attempt to contact the Ground Control Station (GCS) or SOF via a cockpit cellular device. If unable to safely continue, Chase will RTB.

• RPA Detects Loss (Outbound): RPA will continue to the restricted area, making radio calls for the formation.

• RPA Detects Loss (Inbound): RPA will recover to the local area, making radio calls for the formation.

• RPA Lost Comms Protocol: If comms are lost before the WOLFSKILL departure point, the RPA will signal intent to return to base by lowering its gear for one minute. If lost after committing to transit, the RPA will hold in the R-2515 four-corners region for 30 minutes before deciding to RTB, signaled by another one-minute gear cycling.

• Rejoin: If communications are regained, the chase may rejoin only with the RPA's explicit permission.

5.6 Loss of Visual Contact (VMC)

• The crew member who loses sight will immediately call “LOST VISUAL.” The RPA will acknowledge and transmit its heading, altitude, and airspeed, and remain predictable.

• Chase will maneuver to establish a minimum of 500 feet altitude separation until visual contact is regained.

• If visual contact is lost for more than 30 seconds, the chase will proceed to orbit as directed by KRIV tower. Rejoin requires RPA permission.

5.7 Inadvertent IMC Penetration

• If IMC is encountered and results in lost visual contact, the chase pilot will immediately call “LOST VISUAL – POPEYE,” transition to instruments, and maneuver away from the RPA's last known position.

• The RPA will acknowledge, transmit its flight parameters, and remain predictable.

• A minimum of 500 feet altitude separation will be maintained. Both aircraft will independently coordinate with ATC for an IFR clearance and separation.

• Rejoin may only occur once clear of IMC, visual contact is re-established, and the RPA grants permission.

5.8 Aircraft Emergencies

• RPA Emergency: Chase will maintain position and provide assistance as requested until the RPA is successfully recovered.

• Chase Emergency: Chase will communicate intentions to the RPA and follow its own emergency procedures. Continuation of the RPA mission is at the discretion of the 160th

Attack Squadron.

5.9 Chase as "Weather Ship"

• While in transit, the chase aircraft can act as a "weather bird." If conditions arise that would prohibit safe RPA operations, the chase pilot must make every attempt to contact the SOF as soon as possible. Chase pilots are required to know the operating criteria for safe RPA operations.

6.0 Period and Place of Performance

• Place of Performance: March Air Reserve Base (KRIV), Edwards Air Force Base

(KEDW), and associated transit routes to restricted airspace R-2515, R-2503, and R-

2501.

• Period of Performance:

o DATES for which this Chase plane is needed 07 SEPTEMBER 26 to 30

OCTOBER 26.

7.0 Deliverables & Reporting

Deliverable Frequency /

Due Date Description

Personnel & Equipment

List

Prior to contract start

Submit resumes for all pilots and observers and a list of equipment. Any substitutions require prior written approval from the Ordering Officer.

Document

Acknowledgment

Prior to contract start

Contractor shall confirm all chase pilots have read the current LOA and COA and will keep a copy in their onboard SOP.

Contract Man-hours

Reporting Application

(CMRA)

Annually

(NLT 31

October)

Report all contractor and subcontractor labor hours for the fiscal year (Oct 1 - Sep 30) via https://www.ecmra.mil/.

8.0 Security & Administration

• Operations Security (OPSEC): All contractor personnel require initial and annual

OPSEC education on protecting critical information, understanding threats, vulnerabilities, and countermeasures.

• CMRA Details:

o Requiring Activity UIC: FS710G o Issuing Office DoDAAC: WF0S74

• SAM DETAILS:

https://www.google.com/url?q=https%3A%2F%2Fwww.ecmra.mil%2F o SAM reporting pursuant to DoD policy is used to comply with most of the reporting required by 10 U.S.C. § 2330a “