PWS - Chase Plane June 2021.pdf

Ver. January 2021

PERFORMANCE WORK STATEMENT (PWS)

FOR

Chase Plane Services

1.0 General:

1.1 Scope: The contractor shall provide all personnel, equipment, tools, materials, supervision, and quality control necessary, except as specified in Paragraph 3.0 as Government Furnished, to perform Chase Plane Services, as defined in this PWS.

1.2 Background: Currently, Remotely Piloted Aircraft (RPA) are required to provide an alternate means of complying with Title 14 of the Code of Federal Regulations (14 CFR) 91.113, which requires pilots to “See and avoid” other aircraft. The MQ-9 is not certified to meet the see-and-avoid requirement but tasked to launch sorties to provide ANG MQ-9 enterprise training. Therefore, the 119th Wing is contracting with a civilian operator to provide a chase aircraft and minimum crew of a pilot and an observer.

Chase support must be available in the event Ground Based-Detect And Avoid (GBDAA) radar systems are unavailable. All attempts will be made to provide the Chase contractor as much notice possible when Chase services are required.

However, unforeseen circumstances may require short notice notification. In these situations, the Government will provide the Chase contractor a minimum of 48 hours advanced notice prior to circumstances requiring Chase services. Basic procedures are described in this document; however, some operational details may be altered due to agreements with Air Traffic Control (ATC).

1.3 Period of Performance (PoP): 1JUL2021-30JUN2022. The Period of Performance will be 1 Year.

1.4 General Information:

1.4.1 Place and Performance of Services: The contractor shall provide services between the hours of 0730-1730 on Monday through Friday except on recognized U.S.

holidays. The contractor shall occasionally perform services outside of these hours and on weekends (Unit Training Assemblies) due to mission requirements. Mission requirements driving the requirement to perform these services outside of the 0730- 1730, Monday through Friday work schedule shall be scheduled in accordance with paragraph 5.3, SCHEDULING/ORDERING PROCEDURES. The contractor shall at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.4.1.1 Telework: The Government does not permit the contractor to telework in support of this requirement.

1.4.1.2 Unscheduled gate closures by the Security Police may occur at any time causing all personnel entering or exiting a closed installation to experience a delay. This cannot be predicted or prevented. Contractors are not compensated for unexpected closures or delays. Vehicles operated by contractor personnel are subject to search pursuant to applicable regulations. Any moving violation of any applicable motor vehicle regulation may result in the termination of the contractor employee’s installation driving privileges.

1.4.1.3 The contractor’s employees shall become familiar with and obey the regulations of the installation; including fire, traffic, safety and security regulations while on the installation. Contractor employees should only enter restricted areas when required to do so and only upon prior approval. All contractor employees shall carry proper identification with them at all times, and shall be subject to such checks as may be deemed necessary. The contractor shall ensure compliance with all regulations and orders of the installation, which may affect performance. The Government reserves the right to direct the removal of an employee from Government property or revoke access to Government systems for misconduct, security reasons, or any overt evidence of communicable disease. Removal of contractor employees for reasons stated above does not relieve the Contractor from responsibility for total performance of this contract.

1.4.2 Recognized Holidays: The following are recognized United States (US) holidays.

The contractor shall not perform services on these days:

1.4.3.1 New Year’s Day: January 1st

1.4.3.2 Martin Luther King, Jr.’s Birthday

1.4.3.3 President’s Day

1.4.3.4 Memorial Day

1.4.3.5 Independence Day: July 4th

1.4.3.6 Labor Day

1.4.3.7 Columbus Day

1.4.3.8 Veteran’s Day: November 11th

1.4.3.9 Thanksgiving Day

1.4.3.10 Christmas Day: December 25th

1.4.3 Quality Control (QC): The contractor shall develop and maintain an effective QC Plan (QCP) to ensure services are performed in accordance with this PWS. The contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The contractor’s QCP is the means by which it assures itself that its work complies with the requirements of the contract. As a minimum, the contractor shall develop QC procedures that address the areas identified in Technical Exhibit 1, Performance Requirements Summary (PRS).

1.4.4 Quality Assurance (QA): The Government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government will do to ensure that the contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and acceptable quality level(s) or defect rate(s).

1.4.5 Access and General Protection/Security Policy and Procedures. The contractor shall comply with all applicable installation/facility access and local security policies and procedures, which may be obtained from the Contracting Officer’s Representative (COR). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by the local installation’s Security Forces, Director of Emergency Services or local Security Office. The contractor shall ensure compliance with all personal identity verification requirements as directed by DoD, Headquarters Air Force (HAF) and/or local policy. Should the Force Protection Condition (FPCON) change, the Government may require changes in contractor security matters or processes.

1. The contractor shall obtain base identification and vehicle passes, if required, for all contractor personnel who make frequent visits to or perform work on the Air Force installation(s) cited in the contract. Contractor personnel are required to wear or prominently display installation identification badges or contractor-furnished, contractor identification badges while visiting or performing work on the installation.

2. The contractor shall submit a written request on company letterhead to the contracting officer listing the following: contract number, location of work site, start and stop dates, and names of employees and subcontractor employees needing access to the base. The letter will also specify the individual(s) authorized to sign for a request for base identification credentials or vehicle passes. The contracting officer will endorse the request and forward it to the issuing base pass and registration office or Security Forces for processing. When reporting to the registration office, the authorized contractor individual(s) should provide a valid driver s license, current vehicle registration, valid vehicle insurance certificate, and [insert any additional requirements to comply with local security procedures] to obtain a vehicle pass.

3. During performance of the contract, the contractor shall be responsible for obtaining required identification for newly assigned personnel and for prompt return of credentials and vehicle passes for any employee who no longer requires access to the work site.

4. When work under this contract requires unescorted entry to controlled or restricted areas, the contractor shall comply with AFI 31-101, Integrated Defense.

5. Upon completion or termination of the contract or expiration of the identification passes, the prime contractor shall ensure that all base identification passes issued to employees and subcontractor employees are returned to the issuing office.

6. Failure to comply with these requirements may result in withholding of final payment.

1.4.5.1. Reserved

http://static.e-publishing.af.mil/production/1/af_a4/publication/afi31-101/generic_wms.pdf

1.4.5.2 Reserved.

1.4.5.3 Reserved.

1.4.5.4 Reserved.

1.4.5.5 Communications Security/Information Technology (COMSEC/IT) Security. All communications with DoD organizations are subject to COMSEC review. All telephone communications networks are continually subject to intercept by unfriendly intelligence organizations. DoD has authorized the military departments to conduct COMSEC monitoring and recording of telephone calls originating from, or terminating at, DoD organizations. Therefore, the contractor is advised that any time contractor personnel place or receive a call they are subject to COMSEC procedures. The contractor shall ensure wide and frequent dissemination of the above information to all employees dealing with DoD information. The contractor shall abide by all Government regulations concerning the authorized use of the Government's computer network, including the restriction against using the network to recruit Government personnel or advertise job openings.

1.4.5.6 Use of Government Information Systems (IS) and access to Government networks is a revocable privilege, not a right. Users are the foundation of the DoD strategy and their actions affect the most vulnerable portion of the Air Force Infostructure. Contractor employees shall have a favorable background investigation or hold a security clearance and access approvals commensurate with the level of information processed or available on the system. Contractor employees shall:

1.4.5.6.1 Comply with the command's Acceptable Use Policy (AUP) for Government owned IS and sign an AUP prior to or upon account activation.

1.4.5.6.2 Complete initial and/or annual Information Assurance (IA) training as required by applicable Air Force/ANG policy.

1.4.5.6.3 Mark and safeguard files, output products, and storage media per classification level and disseminate them only to individuals authorized to receive them with a valid need to know.

1.4.5.6.4 Protect IS and IS peripherals located in their respective areas in accordance with physical security and data protection requirements.

1.4.5.6.5 Practice safe network and Internet operating principles and take no actions that threaten the integrity of the system or network.

1.4.5.7 Reserved

1.4.5.8 Reserved

1.4.5.9 Reserved

1.4.5.10 Reserved

1.4.5.11 Requirement for OPSEC Training. In accordance with AFI 10-701, Operations Security, OPSEC PMs/Signature Managers/Coordinators will provide OPSEC training or training materials to contract employees within 30 days of employees’ initial assignment to the contract and prior to having access to any critical information (CI) and annually thereafter. General organizational orientations may need to be supplemented by duty-related orientations in the work center targeted toward specific critical information and vulnerabilities associated with the work. Initial training (OPSE 1301 - OPSEC Fundamentals) is located on the ADLS website and refresher OPSEC training is conducted annually (at Commander's Call). The contractor shall submit certificates of completion for each contractor employee to the COR within 15 calendar days after completion of training.

1.4.5.12 Reserved.

1.4.5.13 Reserved.

1.4.5.14 Reserved

1.4.6 Physical Security. The contractor shall safeguard all Government property provided for contractor use. At the close of each work period, Government facilities, equipment and materials shall be secured.

1.4.7 Special Qualifications: The contractor shall ensure all employees possess all required licenses for operating Chase aircraft used in the performance of this contract.

This does not include education or other qualifications for the position in which the contractor employee is performing, dress codes, or other information. (NOTE: The Government does not provide training to contractors. Contractors must ensure that any personnel performing under a contract are fully trained, licensed, certified, and otherwise qualified to provide services.)

1.4.7.1 CHASE AIRCRAFT REQUIREMENTS: The contractor provided Chase aircraft shall be capable of flying at a sustained speed of 120 knots indicated airspeed at an altitude of 12,000 feet and below, and shall possess a sustained climb rate of at least 700fpm at 110 KIAS, to 8,000’ Mean Sea Level (MSL). The contractor shall submit to the government performance information specific to the plane intended to be used to provide chase aircraft support. This information shall include, but is not limited to:

make, model and year of manufacture of proposed aircraft. All Chase aircraft shall be fully insured and the Contractor shall be solely responsible for damages to the aircraft or personnel during the performance of this contemplated contract. Under no circumstances, absent Government negligence, shall the Government be held liable or responsible for any damages sustained by the contractor, subcontractors, and personnel during performance of the contract. The contractor shall submit aircraft specifications with quote submission before the closing on the solicitation period.

1.4.7.2 CHASE OBSERVER QUALIFICATIONS: Observers shall have an understanding of Federal Aviation Regulations applicable to the airspace in which the RPA will operate. Observers shall be considered a crewmember of the RPA and shall not perform crew duties for more than one RPA at a time. Observers shall not perform concurrent duties as both a pilot and observer at any time throughout contract performance. All Chase observers shall maintain, at a minimum, a valid FAA (Federal Aviation Administration) Second Class medical certificate issued under 14 CFR Part 1, Medical Standards and Certification, at all times under contract performance. 14 CFR 91.17, Alcohol or Drugs, applies to all RPA crewmembers, including observers. The contractor shall submit FAA Class 2 medical certificate(s) issued under 14 CFR 67 with quote submission for all prospective observer(s) before the closing on the solicitation period.

1.4.7.3 CHASE PILOT QUALIFICATIONS: Pilots of any aircraft to be considered for contract award in support of this requirement shall be operated by the contractor in accordance with the Federal Aviation Regulations. All Chase pilots shall maintain, at a minimum, a valid FAA (Federal Aviation Administration) Second Class medical certificate issued under 14 CFR Part 1, Medical Standards and Certification, at all times under contract performance. Chase pilots shall comply with 14 CFR 91.17, Alcohol or Drug use. Pilots shall maintain a current biennial flight review in accordance with 14 CFR 61.56, Flight Review, and maintain currency in manned aircraft pursuant to 14 CFR 61.57, Recent Flight Experience: Pilot in Command. All pilots shall be properly certified to serve as the pilot of any aircraft that the supplier will operate in accordance with all applicable regulatory guidance. The contractor shall submit FAA Class 2 medical certificate(s) issued under 14 CFR 67 with quote submission for all prospective observer(s) before the closing on the solicitation period.

1.4.8 Post Award Conference/Periodic Progress Meetings: The contractor agrees to attend any post award conference convened by the KO in accordance with FAR 42.5.

The KO, COR and other Government personnel, as appropriate, may meet periodically with the contractor to review the contactor’s performance. At these meetings, the KO will apprise the contractor of how the Government views the contractor’s performance and the contractor shall apprise the Government of problems, if any, being experienced.

The contractor shall resolve outstanding issues raised by the Government. Contractor attendance at these meetings shall be at no additional cost to the Government.

1.4.9 Contract Manager (CM): The contactor shall designate a CM who shall ensure performance under this contract. The name of this person, and an alternate who shall act for the contractor when the CM is absent, shall be designated in writing to the KO.

The CM or alternate shall have full authority to act for the contractor on all contract matters relating to daily operation of this contract. The CM shall work through the COR, to resolve issues, receive technical instructions, and ensure adequate performance of services. The CM shall ensure that contractor employees do not perform any services outside the scope of the contract without an official modification issued by the KO. The CM shall ensure contractor employees understand that services performed outside the scope of the contract are performed wholly at the expense of the contractor.

1.4.10 Reserved

1.4.11. Combating Trafficking in Persons: The United States Government has adopted a zero tolerance policy regarding trafficking in persons. Contractors and contractor employees shall not engage in severe forms of trafficking in persons during the period of performance of the contract; procure commercial sex acts during the period of performance of the contract; or use forced labor in the performance of the contract. The Contractor shall notify its employees of the United States Government’s zero tolerance policy, the actions that will be taken against employees for violations of this policy. The contractor shall take appropriate action, up to and including termination, against employees or subcontractors that violate the US Government policy as described at

FAR 22.17.

1.4.12 Reserved

1.4.13 Reserved

1.4.14 Organizational Conflicts of Interest (OCI): The contractor and subcontractor personnel performing services under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent OCIs, as defined in FAR Subpart 9.5. The contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO. In the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may impose other remedies as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.4.15 Reserved

2.0 Definitions and Acronyms:

2.1 Definitions:

2.1.1 Chase Aircraft: Aircraft provided by the contractor under contract performance in support of Chase Plane Services meeting the requirements in paragraph 1.4.7.1 of this Performance Work Statement.

2.1.2 Chase Crew: The Chase Pilot and Chase Observer provided by the contractor under contract performance in support of Chase Plane Services as described in this Performance Work Statement.

2.1.3 Chase Pilot: Pilot provided by the contractor under contract performance in support of Chase Plane Services meeting the requirements in paragraph 1.4.7.3 of this Performance Work Statement. Also referred to as “pilot” in this document.

2.1.4 Chase Observer: Observer provided by the contractor under contract performance in support of Chase Plane Services meeting the requirements in paragraph 1.4.7.2 of this Performance Work Statement. Also referred to as “observer” in this document.

2.1.5 Contractor: A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.6 Contracting Officer (KO): A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the government. Note: The only individual who can legally bind the government.

2.1.7 Contracting Officer Representative (COR): An employee of the U.S. Government designated by the KO to monitor contractor performance. Such appointment will be in writing and will state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications.

This individual does NOT have authority to change the terms and conditions of the contract.

2.1.8 Defective Service: A service output that does not meet the standard of performance associated with the PWS.

2.1.9 Deliverable: Anything that can be physically delivered and includes non-manufactured things such as meeting minutes or reports.

2.1.10 Federal Aviation Administration: Operating mode of the U.S. Department of Transportation.

2.1.11 Key Personnel: Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the PWS. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.12 Physical Security: Actions that prevent the loss or damage of Government property.

2.1.13 Quality Assurance: The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.14 Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.15 Quality Control: All necessary measures taken by the contractor to ensure that the quality of an end product or service shall meet contract requirements.

2.1.16 Quality Assurance Surveillance Plan (QASP): An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.17 Quality Control: All necessary measures taken by the Contractor to ensure that the quality of an end product or service shall meet contract requirements.

2.1.18 Subcontractor: One that enters into a contract with a prime contractor. The Government does not have privity of contract with the subcontractor.

2.2 Acronyms:

AGL Above Ground Level ANG Air National Guard ARTCC Air Route Traffic Control Center ATC Air Traffic Control AT/OPSEC Antiterrorism/Operational Security CFR Code of Federal Regulations CM Contract Manager COA Certificate of Authorization COR Contracting Officer Representative DD254 Department of Defense Contract Security Classification Specification DFARS Defense Federal Acquisition Regulation Supplement DoD Department of Defense FAA Federal Aviation Administration FAR Federal Acquisition Regulation GBDAA Ground-Based Detect and Avoid GFP/M/E/S Government Furnished Property/Material/Equipment/Services HQDA Headquarters, Department of the Army HSPD Homeland Security Presidential Directive IA Information Assurance IFR Instrument Flight Rules IMC Instrumental Meteorological Conditions IS Information System(s) KFAR Hector International Airport KO Contracting Officer

LOA Letter of Agreement LRE Launch/Recovery Element NM Nautical Mile NGB National Guard Bureau OCI Organizational Conflict of Interest PII Personally Identifiable Information PIPO Phase In/Phase Out POC Point of Contact PRS Performance Requirements Summary PWS Performance Work Statement QA Quality Assurance QASP Quality Assurance Surveillance Plan QC Quality Control QCP Quality Control Program SOF Supervisor Of Flying SOP Standard Operating Procedures TRACON Terminal Radar Approach Control VFR Visual Flight Rules VMC Visual Meteorological Conditions RPA Remotely Piloted Aircraft SSN Social Security Number TE Technical Exhibit USD(I) Under Secretary of Defense for Intelligence

3.0 Reserved

4.0 Contractor Furnished Property, Materials, and Equipment (CFP/M/E):

4.1 General: Except for those items specifically stated to be Government-Furnished in Paragraph 3.0, the contractor shall furnish everything required to perform these services as indicated in Paragraph 1.1.

4.2 Reserved

4.3 Reserved

5.0 Requirements: The contractor shall comply with all standards set forth in this section of PWS for contracted services:

5.1 The Chase crew (contractor) shall rendezvous with the RPA within the confines of Hector IAP (KFAR), Class D airspace. When rendezvous is complete, Chase shall accompany the RPA while transiting to the training airspace (generally less than 110NM of Fargo, e.g. R-5403 and R-4301) via the guidelines set forth within a Certificate of Authorization (COA) and Letter(s) of Agreement (LOA) with ATC. Once the RPA is established within the training airspace, Chase shall hold or land to await the completion of the RPA training mission. The chase aircraft and crew shall standby until scheduled handover time, or until notified of an early return by the RPA crew. At the end of the RPA training mission, Chase shall rendezvous with the RPA at the border of the training airspace and accompany the RPA back to Hector IAP. A ground observer shall assume observer duties once the RPA is in the Class D, and Chase will be released. The 119th Wing may request the chase aircraft to perform sorties supporting LRE (Launch / Recovery) initiatives, e.g., Ground Based Detect and Avoid (GBDAA) radar testing.

These sorties will be of similar duration to a restricted area sortie and shall be considered as inclusive of any resulting contract issued as a result of this Performance Work Statement provided. It should also be noted that sorties of this nature may not require an observer in the chase aircraft crew. Contractor-provided Chase Aircraft shall comply with the requirements set forth in paragraph 1.4.7.1 at all times while performing services under contract performance.

5.2 SAFETY: The contractor shall follow all standard safety precautions. The objective of the Chase aircraft is to protect the safety of non-participating manned aircraft operating in the vicinity of the RPA. The Chase crew (contractor) shall provide uninterrupted visual scanning of the flight path, and on all sides, of the RPA. If the Chase crew recognizes a traffic conflict, the Chase crew shall immediately direct the RPA to turn left or right, and/or climb or descend to avoid the conflict. The Chase crew shall use clear & concise communication, such as “RPA 11, Chase, turn right, traffic 10 O’clock,” and repeat the message if an immediate maneuver is not executed. A Chase crew order to maneuver is very rare; however, the Chase crew shall be continuously alert for a maneuver order, and shall maintain two-way communications at all times.

5.3 SCHEDULING/ORDERING PROCEDURES: The contractor shall follow ordering procedures identified in this section of the PWS. The contractor shall ensure Chase aircraft are available to provide approximately 3.2 flight hours of Chase support total per RPA sortie (to and from the restricted area). A mission shall consist of an outbound trip from Hector IAP and a return trip from the training airspace, regardless if the Chase aircraft lands between the two events. Additionally, the Chase aircraft and crew shall remain on “standby” while an RPA is airborne. The flying schedule is subject to change but anticipated to average 9-12 flying days per month (Up to 90 sorties total for this requirement), including drill weekends and on-call Domestic Operations Support during day or night operations. RPA sorties shall be scheduled for 3 to 8 hours in length, occasionally longer for off-station taskings. Total flying hours for the Chase aircraft shall be approximately 30 hours per month. Operations will schedule typically during daylight hours; however, night operations may occasionally be required.

5.3.1 Scheduled Operations: A weekly operations schedule shall be issued to the contractor no later than Friday of the previous week. The schedule shall be provided by the Contracting Officer’s Representative (COR).

5.3.2 On-call operations: The contractor shall be prepared to provide “On call” Chase support, defined as “the ability to commence Chase operations within 6 hours of the request for services.” (On-call operations would result from a federal or state tasking in support of a natural disaster or assistance to civil authorities and anticipated to occur rarely.) Only the COR or Contracting Officer (KO) may order on-call services or authorize any changes to the weekly schedule.

5.3.3 While the RPA is in the training airspace, Chase crew shall stand by, ready to launch in support of an emergency return of the RPA. Standby is defined as: “the ability to be at the designated handover point within 45 minutes of notification.

5.4 CHASE CREW REQUIREMENTS: For Chase operations, a Chase qualified pilot and a Chase qualified observer shall be required. The contractor shall comply with paragraph 5.19, CHANGES TO CHASE CREW AND EQUIPMENT.

5.4.1 Chase crew pilot shall be responsible for aircraft control and visual separation with the RPA while maintaining compliance with FAA and ANG instructions.

5.4.2 Chase crew observer shall be responsible for clearing for additional traffic.

5.4.3 Chase crew shall advise the RPA if the flight path indicates a possible conflict with other aircraft or if weather minimums cannot be maintained.

5.4.4 The contractor shall submit to the Government, resumes of all pilots and all observers that the contractor will utilize if awarded the contract. Upon award of the contract, the contractor shall not use any other pilots or observers without prior written approval from the COR or the KO.

5.5 WEATHER MINIMUMS: The contractor shall provide Chase plane support under the following conditions.

5.5.1 The RPA shall operate under Instrument Flight Rules (IFR) but will make every effort to maintain Visual Meteorological Conditions (VMC).

5.5.2 Chase operations shall operate under Visual Flight Rules (VFR), surface to

14,000’ MSL.

5.5.3 Standard VFR cloud clearance requirements shall apply, in accordance with 14 CFR 91.155, Basic VFR weather minimums.

5.6 ALTITUDE MINIMUMS: Chase crew/aircraft shall not operate below 500 feet Above Ground Level (AGL) while performing enroute Chase procedures.

5.7 RENDEZVOUS PROCEDURES: The contractor shall follow established rendezvous procedures.

5.7.1 Initial rejoin on takeoff – Chase crew shall be airborne prior to the Remotely Piloted Aircraft (RPA) and orbit as directed by Fargo Tower within Class D airspace.

Chase crew shall maneuver into position behind the RPA and report “In position” on inter-plane frequency within 5 minutes when joined with the RPA.

5.7.2 Airborne rejoin – The RPA shall notify Chase of current position and altitude.

Chase will climb and maintain 500 feet below the RPA’s altitude until visual. Chase will report “visual,” maneuver to rejoin, and report “in position” on inter-plane frequency.

5.8 DISTANCE MINIMUMS: The contractor shall follow established distances when Chase crew has the RPA in sight and has reported: “In position.”

5.8.1 Chase crew shall maintain a distance of 300’ to 2500’ laterally from the RPA.

5.8.2 Chase crew shall remain within +/-500’ of the RPA altitude.

5.8.3 Chase crew shall maintain a position slightly higher or lower and 20 to 45 degrees left or right of the RPA.

5.9 EQUIPMENT PROCEDURES: The contractor shall follow established equipment procedures.

5.9.1 Chase crew and RPA shall operate beacons and strobe lights during all operations to increase visibility for other aircraft.

5.9.2 Once the Chase crew is “in position,” the RPA will transmit the transponder code for the formation. Chase shall squawk ‘standby’ while joined with the RPA.

5.9.3 Chase crew shall comply with FAA standards for onboard equipment.

5.10 CHASE COMMUNICATION PROCEDURES: The contractor shall follow established communication procedures.

5.10.1 Two-way radio communications shall be maintained between the Chase crew and the RPA at all times.

5.10.2 The RPA will verbalize all altitude and airspeed changes over the radio.

5.10.3 Once Chase calls “In position,” the RPA crew will perform ATC radio communications for the formation, and Chase crew shall monitor the appropriate frequencies.

5.10.4 Once released by the RPA crew, Chase crew shall advise ATC of intentions.

5.11 RESTRICTED AREA ENTRY: The contractor shall follow established procedures for rejoin at KFAR and transit to the restricted airspace.

5.11.1 Chase crew shall execute a rejoin on takeoff and escort the RPA to the restricted airspace. Approximate entry coordinates for restricted airspace are as follows:

5.11.1.1 R-5403 – N 47 35 36 W 098 23 34 (FAR 300 Radial at 81 nm).

5.11.1.2 R-4301 – N 46 19 54 W 094 28 11 (FAR 095 radial at 102 nm).

5.11.1.3 The RPA will de-conflict altitude with Chase aircraft once established in restricted airspace. (floor of R-5403 is 10,000’ MSL; floor of R-4301 is SFC).

5.11.2 RPA will release Chase crew once established in restricted airspace.

5.11.3 Chase crew shall squawk mode 3 and advise ATC of intentions once released from observer duties.

5.12 RESTRICTED AREA DEPARTURE / RETURN TO KFAR: The contractor shall follow established procedures for rejoin at restricted airspace and transit to KFAR.

5.12.1 Chase crew shall arrive at the rendezvous point no later than the scheduled time.

5.12.2 Rendezvous procedures shall be conducted in accordance with entry coordinates identified in paragraph 5.1.10.1 above. Once Chase crew has visually acquired the UA, the RPA pilot will obtain an ATC clearance for the flight to exit restricted airspace and return to KFAR.

5.12.3 Chase crew shall be released once a ground-based observer assumes visual scanning responsibilities.

5.13 LOSS OF COMMUNICATIONS BETWEEN CHASE & RPA: The contractor shall follow established procedures in the event of loss of communication between Chase crew and the RPA.

5.13.1 Loss of communications between the RPA & Chase is an emergency condition and must be communicated to ATC by either party (Chase crew or RPA pilot) through any means necessary.

5.13.2 If a loss of communication between the RPA & Chase crew is recognized by either party, Chase crew shall maintain position on the RPA and continue visual observer duties. Chase crew & the RPA will attempt to contact each other via cellular device, and Chase crew shall continue to make radio calls to the RPA in the blind. The RPA will report the loss of communications capability to ATC & advise ATC of intentions.

5.14 LOSS OF VISUAL CONTACT: The contractor shall follow established procedures in the event of loss of visual contact between Chase crew and the RPA.

5.14.1 Loss of visual contact between the RPA & Chase crew is an emergency condition. The RPA will notify ATC of the emergency and shall advise of intentions.

5.14.2 If Chase crew loses visual with the RPA, immediate separation is essential.

Upon losing sight of the RPA, Chase crew shall report “Lost visual” on inter-plane frequency. The RPA will acknowledge the “Lost visual” call and immediately transmit heading, altitude, and airspeed. Chase crew shall turn 15° away from the RPA’s heading and obtain 500’ altitude separation. The RPA will remain predictable and continue its current flight path unless directed otherwise. The RPA will continue to make position reports and Chase crew shall maintain a minimum of 500 feet altitude separation until visual contact is regained.

5.15 ENCOUNTERING IMC (Instrument Meteorological Conditions): The RPA will attempt to avoid IMC penetration during Chase operations; however, if inadvertent IMC penetration occurs resulting in lost visual contact, immediate separation from the RPA is essential. Chase crew shall maintain VMC and execute the Loss of Visual Contact procedures in paragraph 5.1.13 above. If Chase encounters IMC, the RPA will notify ATC of the emergency and advise of intentions.

5.16 AIRCRAFT EMERGENCY: The contractor shall follow all established aircraft emergency procedures.

5.16.1 If the RPA experiences an in-flight emergency, the RPA will communicate intentions to Chase crew. If able, Chase crew shall maintain position through recovery and provide assistance, as requested by the RPA.

5.16.2 If Chase crew experiences an in-flight emergency, Chase crew shall communicate intentions to the RPA. Chase crew shall comply with aircraft flight manual and contractor standard operating procedures in response to the emergency.

5.16.3 If Chase crew is unable to continue executing scanning responsibilities safely for any reason, (i.e. weather penetration, low on fuel, potential threat of collision, or aircraft emergency), Chase crew shall break formation with the RPA & report intentions to ATC.

The RPA will notify ATC of the emergency and shall advise of intentions.

5.17 NIGHT CHASE: The contractor shall follow established night flying procedures.

5.17.1 The contractor shall ensure that all qualified crew members are trained adequately to provide night chase support. Night rendezvous procedures are inherently dangerous; therefore, it is imperative that Chase crew pilots and observers receive contractor-provided training in formation flight path de-confliction, terrain awareness/avoidance, night spatial disorientation, and mid-air collision avoidance. This responsibility is incumbent upon the contractor and the Government retains no responsibility for providing this training.

5.17.2 As outlined in paragraph 5.1.2, night chase requests shall be requested by no later than Friday of the previous week. However, the possibility exists that night chase support will be requested on short notice due to real-world State and Federal tasking.

These missions require Chase Aircraft/Chase Crew to be overhead KFAR within 6 hours of notice.

5.17.3 Prior to launch for night operations, the contractor shall contact the Supervisor of Flying (SOF) for a formal crew briefing. The SOF will be identified at the time of award.

5.18 LETTER(s) OF AGREEMENT (LOA): The contractor shall be familiar with the current Certificate of Authorization (COA) as well as applicable Letters of Agreement (LOAs) between Fargo Terminal Radar Approach Control (TRACON), Minneapolis Air Route Traffic Control Center (ARTCC), and the 119th Wing, NDANG. These documents will be supplied to the contractor by the 119th Wing upon contract award.

The contractor shall maintain a copy of the current LOAs and attachments in their on-board Standard Operating Procedures (SOP). Updates to LOAs may necessitate slight changes to the operating procedures prescribed in this document.

5.19 CHANGES TO CHASE CREW OR EQUIPMENT: Only the Chase Aircraft (equipment), Chase Pilots, and Chase Observers described/offered/identified in the contractor’s proposal shall be considered for contract award. Only the Chase Aircraft (equipment), Chase Pilots, and Chase Observers described/offered/identified in the contractor’s proposal shall be utilized in the contract performance of the required services. If the status of any Chase Aircraft, Chase Pilots, or Chase Observers change or become no longer available at any time throughout contract performance, the contractor shall notify the COR immediately, prior to any subsequent flight operations.

In any case where an alternative aircraft (equipment) is being considered for contract performance, the alternative aircraft must meet those requirements identified in paragraph 1.4.7.1. In any case where a new Chase Pilot is being considered for contract performance, the prospective Chase Pilot’s medical credentials must meet those requirements identified in paragraph 1.4.7.3. In any case where a new Chase Observer is being considered for contract performance, the prospective Chase Observer’s medical credentials must meet those requirements identified in paragraph

1.4.7.2. Revised qualifications and/or substitutions of personnel (Chase Pilots or Chase Observers) or equipment (Chase Aircraft) shall be approved in writing by the COR prior to contract performance. The COR will advise the KO of any required changes and shall provide written approval of any required changes to both the contractor and the

KO.

6.0 Applicable Publications: Publications applicable to this PWS are listed below:

Publication (Chapter/Page)

Date of Publication

Mandatory or Advisory

Website

Federal Acquisition Regulation Mandatory https://www.acquisition.gov/?q=browsefar or http://farsite.hill.af.mil/

Defense Federal Acquisition Regulation Supplement

Mandatory http://www.acq.osd.mil/dpap/dars/dfarspgi/current /index.html or http://farsite.hill.af.mil/

14 CFR 67

February 24, Mandatory https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=t rue&node=pt14.2.67&rgn=div5

14 CFR 91.113

February 24, Mandatory https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=t rue&node=se14.2.91_1113&rgn=div8

14 CFR 91.17

February 24, Mandatory https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=t rue&node=se14.2.91_117&rgn=div8 FAA Sectional Chart – Twin Cities

January 2, Mandatory https://aeronav.faa.gov/content/aeronav/sectional_files/

PDFs/Twin_Cities_99_P.pdf http://www.acquisition.gov/?q=browsefar http://farsite.hill.af.mil/ http://www.acq.osd.mil/dpap/dars/dfarspgi/current http://farsite.hill.af.mil/ https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=pt14.2.67&rgn=div5 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=pt14.2.67&rgn=div5 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=pt14.2.67&rgn=div5 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_1113&rgn=div8 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_1113&rgn=div8 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_1113&rgn=div8 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_117&rgn=div8 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_117&rgn=div8 https://www.ecfr.gov/cgi-bin/text-idx?SID=5f742e9e117b0d797db1e4db441be348&mc=true&node=se14.2.91_117&rgn=div8 https://aeronav.faa.gov/content/aeronav/sectional_files/PDFs/Twin_Cities_99_P.pdf https://aeronav.faa.gov/content/aeronav/sectional_files/PDFs/Twin_Cities_99_P.pdf

TECHNICAL EXHIBIT 1

Performance Requirements Summary (PRS)

Performance Objective Performance Standard Acceptable Quality Levels

(AQL)

Surveillance

Method / By Whom

5.1 Aircraft

Performance

Chase crew (contractor) shall accompany the RPA, maintaining the capability of 120 kts at 12,000’ and below and climb rate of at least 700fpm at 110KIAS to 8,000’ MSL, while transiting to the training airspace.

The contractor shall comply with Chase Aircraft Requirements identified in paragraph 1.4.7.1. Contractor shall meet this standard at a 99% or greater performance standard. QA surveillance forms will be generated within 10 days of the end of the month to determine compliance.

Random Monitoring

/ COR

5.3 Scheduling /

Ordering Procedures;

Sortie Generation

The contractor shall ensure Chase Aircraft are available to provide approximately 3.2 flight hours of Chase support total per RPA sortie.

The contractor shall follow established Scheduling / Ordering Procedures. COR will confirm contractor status and availability of required flight duration with contractor.

The contractor must meet compliance with these standards at a 90% or greater performance standard. QA surveillance forms will be generated within 10 days of the end of the month to determine compliance.

Random Monitoring

5.4.1 Compliance

with FAA and ANG Instructions

Chase crew pilot (contractor) shall be responsible for aircraft control and visual separation with the RPA while maintaining compliance with FAA and ANG instructions.

The contractor shall maintain compliance with FAA and ANG instructions. The contractor must meet compliance with these instructions at a 90% or greater performance standard.

QA surveillance forms will be generated within ten days of the end of the month to determine compliance.

Random monitoring

/ COR

5.7.1 On-time for

join-up

Chase crew (contractor) shall maneuver into position behind the RPA and report “In position” on inter-plane frequency, when joined with the RPA within 5 minutes of entering Class D airspace.

The contractor shall follow established join-up procedures and meet required time from at a 90% or greater performance standard. The contractor will generate QA surveillance forms within ten days of the end of the month to determine compliance.

Random monitoring

/ COR

5.12.1 On-time for

rejoin

Upon departure from the restricted air space to return to KFAR, the Chase crew (contactor) shall arrive at the rendezvous point no later than the scheduled time.

The contractor shall follow established rejoin procedures and meet required time from at a 95% or greater performance standard. The contractor will generate QA surveillance forms within 10 days of the end of the month to determine compliance.

Random monitoring

TECHNICAL EXHIBIT 2

Deliverables Schedule

PWS Reference / Deliverable Title

Frequency Number of

Copies Medium/Format Submit To

1.4.7.1 Chase Aircraft

Technical Requirements Information

Submit with RFQ *For Evaluation

1 Electronic Submission

KO

1.4.7.2 Observer

Qualifications / FAA Class 2 Medical Cert compliant with 14 CFR 67

Submit with RFQ *For Evaluation

1 Electronic Submission

KO

1.4.7.3 Pilot Qualifications

/ Current Airman or Military Equivalent Medical Certificate compliant with 14 CFR 67.

Submit with RFQ

*For Evaluation

1 Electronic Submission

KO

5.19, Changes to Chase Crew or Equipment. Must be compliant with paragraphs 1.4.7.1,

1.4.7.2 or 1.4.7.3, as applicable.

As needed during contract performance;

required in any occurrence when Chase Aircraft (equipment), Chase Pilots, or Chase Observers are being replaced or added to perform under contract performance.

1 Electronic Submission

COR