Atch 1 - AUTEC PWS 2025.03.18.pdf

ATLANTIC UNDERSEA TEST AND EVALUATION CENTER (AUTEC)

PALM BEACH FL (KPBI)—ANDROS TOWN BAHAMAS (MYAF)

October 1, 2025

1.0 GENERAL REQUIREMENTS

1.1 Scope. Except as stated in this contract, the contractor shall provide all personnel, equipment, tools, material, supervision and other items and services necessary to perform fixed wing transportation services for military and Government commuter passenger transportation and movement of essential cargo (including contractor personnel and equipment performing on unrelated contracts) between KPBI airport and MYAF airport, in support of the Atlantic Undersea Testing and Evaluation Center. If necessary for operational purposes, the aircraft may operate from an alternate location within the state of Florida.

1.2 Aircraft Condition. The contractor shall provide air transportation capable of moving at minimum fifteen (15), and maximum of nineteen (19) passengers and baggage in 1.25 flight hours or less between Palm Beach International Airport, FL (KPBI), and Andros Town/Fresh Creek International Airport, Bahamas (MYAF). The aircraft shall be capable of transporting baggage of 50lbs per manifested passenger. The aircraft shall be able to provide a climate-controlled cabin for personnel safety at both KPBI & MYAF to address high heat and humidity at these locations.

1.2.1 FW Aircraft Communications. FW Aircraft must be Instrument Flight Rules (IFR) capable with Traffic Collision Avoidance System (TCAS), one (1) Very High Frequency (VHF) radio, and one Ultra High Frequency (UHF) radio.

1.3 Mission Requirements. The contractor shall perform at minimum 2 round trip flights per day typically Monday through Friday. Air transportation services are for passengers and baggage movement between KPBI and MYAF, in accordance with this PWS and daily schedule. Additional missions between these locations may be required mid-day during the week, weekends and holidays as requested by the Government. Table 1 below displays a daily schedule which is subject to change. Variations to the times of this schedule may be proposed for efficiency or effectiveness but shall not normally reduce the total number of flights per day.

Table 1:

Tentative Flight Scheduled Monday - Friday

KPBI –

MYAF

MYAF - KPBI

AM 0815 0945

PM 1430 1600

Approximate Yearly Flight Hours ~ 1250

1.3.1 Cancelations. Flights are subject to cancellations with no cost to the Government with advance notice.

1.4 Airfield Suitability & Restriction/ Certification Airfields. The Bahamian government owned and operated Andros Island Fresh Creek International Airport (MYAF) paved runway 09/27 is 4,362 x 100 feet and should be considered suitable only for daylight operations. This airport is in an uncontrolled air space and the runway is maintained by the Bahamian Government. The airport is open to the public and foreign aircrafts. All carriers are responsible for ensuring that the proposed aircraft can operate at MYAF.

Landing fees may be required. Landing and all other airport fees will be paid by the contractor and will be submitted for reimbursement by the Government.

1.5 Operational Readiness (OR). The Contractor shall ensure each aircraft maintains an Operational Readiness (OR) rate of 95% or better, which equates to 2 or less Not Mission Capable (NMC) days per month (including February). The OR rate is calculated by dividing the number Fully Mission Capable (FMC) days for each particular aircraft by the number of workdays in the month. A month begins on the 1st day of the month and ends on the last day of that month, unless there is a partial month of service (i.e., Contract period of performance starts on 16 Sep or ends on 15 July). For partial months of services, the OR will be calculated using the day the period of performance starts through the last day of the month or using the first day of the month through the last day of the period of performance.

1.5.1 Not Mission Capable/Fully Mission Capable Aircraft. Not Mission Capable (NMC) is defined as any day the aircraft cannot fly due to carrier- controlled reasons, i.e., maintenance, operations, and crew availability. The aircraft will be considered Fully Mission Capable (FMC) if it is available for flight as scheduled by the Tasking Authority. An aircraft is not to be considered available unless both the aircraft is FMC, and the aircrew is available as defined by the FAA or comparable regulations. In addition, the aircrew must be co-located (same hub) with the aircraft and be in stand-by status for the aircraft to be considered FMC. If an aircraft is reported as FMC and launches on a tasked sortie but returns to base for carrier-controlled reasons without completing a mission leg, and without completing any legs for that day, then the aircraft will be considered NMC for that entire day. Any day an aircraft is NMC for carrier-controlled reasons, it will be factored into the carrier’s OR rate and could impact the monthly billable amount. If there are extenuating circumstances, the NMC days can be waived on a case-by-case basis by the Contracting Officer (CO) after coordination with the Contracting Officer’s Representative (COR).

1.6 Contract Management. This task consists of the functional activities relating to the management, administration, staffing and reporting requirements of this effort. The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, limited security, non-personal services, and other items necessary to perform the services required by this Performance Work Statement. Limited Security is defined as security of Contractor’s assets, bed down locations, and personnel, etc., such that the Contractor maintains 100% accountability at all times and can alert appropriate authorities should there be an emergency.

1.6.1 Personnel Requirements. The Contractor shall provide adequate personnel and manage its personnel resources, including its subcontractors, to partner with DoD and its stakeholders to successfully accomplish the tasks outlined in this PWS. All personnel are required to speak English fluently.

1.6.1.1 The Contractor shall designate principal point(s) of contact (POC) to interface with the CO and/or COR on issues concerning aircraft transport.

The Contractor is responsible for ensuring the POC contact information remains current throughout the life of the contract.

1.6.1.2 The POC contact information shall be provided in writing to the CO and COR within five workdays of Contract award. At a minimum, the Contractor shall provide a 24-hour contact number, e-mail address, business address, and hours of operation for the POC. The Contractor shall also identify Emergency POC(s), if different than the primary POC(s), by name, email address, and mobile number to be available 24-hours a day, 7-days a week, to resolve all matters in performance of this requirement.

1.6.1.2.1 The Contractor shall notify the CO and COR within twenty-four

(24) hours of the employment or termination of any on-site Contractor personnel by providing an updated list of personnel which includes, at a minimum, the following information: name (last, first, middle initial), primary position title, level of investigation/security clearance and date of approval, and date of on-site employment or termination.

1.6.1.3 A Post Award Conference shall be held after Contract award and prior to commencement of any work on this contract. The Contractor's authorized representative shall attend the Post Award Conference at the expense of the Contractor. Exact date, time, and location will be provided in writing by the CO as soon as possible but at least 7calendar days prior to the conference.

1.6.1.4 The Contractor shall provide at least one aircrew for each primary aircraft assigned to this contract. The Contractor’s aircrew members shall be trained, qualified, and maintain proficiency in accordance with the applicable Federal Aviation Regulation Part 135, Code of Federal Regulations (CFR) 32 CFR 861, and/or other applicable Civil Aviation Authority regulations.

1.6.1.5 Aircrew Duty Day Requirements. Crew duty day requirements are governed by the applicable Federal Aviation Regulation Part 135, 32 CFR Part 861, and/or other applicable Civil Aviation Authority (CAA) regulation.

1.6.1.6 The Contractor shall, when required, provide all support personnel necessary to complete assigned missions in a stand-alone capacity (i.e., Air Planner, Meteorology/Weather).

1.6.1.7 Contractor’s aircraft maintenance personnel shall be trained, qualified, and maintain proficiency in accordance with the applicable Federal Aviation Regulation Parts 135, Code of Federal Regulations (CFR) 32 CFR Part 861, and/or other applicable Civil Aviation Authority regulations.

1.6.1.8 The Contractor shall obtain any necessary certifications (i.e., FAA or Department of State licenses, etc.) to operate in the area of operations.

1.6.1.9 The Contractor shall be responsible for the routine rotation of Contractor personnel for employment at the operations location to be executed with Contractor resources. The Contractor shall plan for and be responsible for a contingency evacuation of its personnel.

1.6.1.10 If the Government notifies the Contractor that the employment or the continued employment of any contract employee is prejudicial to the interests or endangers the security of the United States of America, that person shall be removed, barred from the worksite, and replaced at Contractor expense. This includes security deviations/incidents and credible derogatory information on Contractor personnel during the course of the contract period. The Contractor shall make any changes necessary in the appointments.

1.6.2 Reports.

1.6.2.1 Daily Situation Report (SITREP). The Contractor will maintain a daily record to monitor the status of the aircraft in country, as well as verify the number of personnel working on site. The Contractor shall make these records available to the CO and COR upon request.

1.6.2.2 Daily Sortie Report. The Sortie Report will be in a Microsoft Excel format and include, at a minimum, a row entry for each calendar day (one row entry per aircraft), aircraft type, registration number, aircraft status, aircrew names, starting location, ending location, passengers carried (onloaded, offloaded and continued through), cargo carried (in pounds), flight hours flown, a comment block, fuel added (in gallons), total legs flown, and all intermediate locations flown. Each row will include all of this information per day whether the aircraft flew or not. The comment block will be used to annotate reasons for not flying or mission abort, (e.g., maintenance, weather, no tasking, etc.). The report will also include cumulative totals, as well as filterable totals by selected date range and additional selectable column filters. The Contractor shall make these records available to the CO and COR after the mission day but no later than the deadline for the following day’s SITREP.

1.6.2.3 Daily Log. The Contractor will maintain a daily record of all scheduled and completed missions. The log shall be maintained by the Contractor’s aircrew for each mission and shall detail the number of passengers moved (getting on, off, and traveling through) and/or the internal and external cargo load information for each destination. This log will include entries that will code reasons missions were not performed as scheduled to include (weather, maintenance, threat, safety, etc.) and who authorized the mission cancellation. The contractor shall maintain the daily logs for the calendar month, then transfer them to the CO by the 15th calendar day after the end of the month. (i.e., the reports for 1-31 May will be provided to the CO by 15 June) The contractor shall make the logs available, within 24 hours, to the CO, COR and FAA upon request.

1.6.2.4 Event Reporting. The Contractor shall notify the CO, COR, and/or designated points of contact of any event involving the aircraft, aircrew, or other contractor employees. Notification is not restricted to safety events, but includes events which do, or could, impact the health or welfare of personnel, such as sickness from disease; death of employee;

animal bites, etc. The Contractor shall also notify the CO of any engagements with other government agencies, such as the FAA or AMC, related to performance under this contract. Notification shall be made by the most expeditious means available considering the seriousness of the event but under all circumstances is to be made no later than the next business day. A final notification, which provides a summary of the event and the cause, is to be provided to the CO and COR within 30 calendar days of resolution. Interim reports may be requested by the CO when a final notification cannot be provided within 30 calendar days of the event.

Notifications shall include:

• Contractor Name, and employee name(s), as applicable

• Date and time of the event

• Nature of the event

• Summary of event including personnel involved, actions taken, and actions planned

• Expected date for follow-up or resolution

1.6.2.5 Notice of Accidents or Incidents. All Carrier Operations: When a

Contractor’s aircraft is involved in any accident, DoD or otherwise, the Contractor shall transmit the information in paragraph above to Headquarters Air Mobility Command (AMC), via HQ AMC/A3B, Scott AFB IL (618) 229-4801/DSN 779-4801 or the HQ AMC/A3B Safety Manager at 618-2292106/DSN 779- 2106. Accident and incident information shall be provided to HQ AMC, the CO and the COR on the next business day by the most expeditious means available. Accidents and incidents are defined in 49 CFR, Part 830.

1.6.2.5.1 Contractor and trip number.

1.6.2.5.2 Aircraft type and number.

1.6.2.5.3 Date and time of the accident or incident.

1.6.2.5.4 Last point of departure and point of intended landing of the aircraft, as applicable.

1.6.2.5.5 Nature of the accident or incident and extent of known damage to the aircraft, if any.

1.6.2.5.6 Total number of crewmembers and passengers on board.

1.6.2.5.7 Number of injured and fatalities aboard the aircraft.

1.6.2.5.8 Condition of baggage or Government-owned material, if any, on board.

1.6.2.6 Aircraft Medical Incidents. Report all aircraft medical incidents in flight, or while passengers are under the control of the pilot in command, to the first available COR, at the next enroute station for in flight incidents, or the station where the incident occurs. On the next business day, notification shall also be made to the CO, via telephone or e-mail.

1.6.2.7 DoD Casualties. In cases where a death occurs on a Contractor’s aircraft, the passenger information shall be furnished to the applicable geographical commander based on this Contract and CO instructions. If available, include the following: Full Name, Department of Defense Identification Number (DoD ID), Passport number for contractors/civilians, and component of service identified as Army-USA, Air Force-USAF, Navy- USN, Marine Corps-USMC, Coast Guard- USCG, or other DoD agency, as appropriate. The Contractor shall notify the first available COR at the next enroute station for in flight incidents, or the station where the incident occurs. The CO shall be notified no later than the next business day.

1.6.2.8 Hazard Reporting. The Contractor shall report any condition involving cargo that constitutes a hazard to operations, the Contractor, and airport safety personnel. This report should contain the following information:

location; date and Greenwich Mean Time (GMT); nomenclature of cargo (proper shipping name of hazardous cargo); shipper’s organization/unit and name of cargo representative; destination of cargo; Transportation Control Number (TCN) or bumper/increment number; facts and circumstances. Report this information to the CO.

1.6.2.9 Spotlighting and Hostile Event Reports. Timely threat reporting is essential to safe aircraft operations. In the event a Contractor operating a mission is illuminated or “spotlighted,” or is fired upon in the air or on the ground, the crew shall note the date, time, and approximate area from which the event originated. All incidents, including any hostile action (potential or realized) directed at the aircraft, shall be reported immediately to the cognizant air traffic control agency. Additionally, upon landing, at the first airfield or airbase with a U.S. military presence, the crew shall notify the base operations center, and joint operation center concurrently of the occurrence. The Contractor shall also notify the COR immediately of any information regarding a threat to an aircraft, or of any attempts to elicit information from the crew on their mission or cargo. The Contractor shall also report any incidents to the CO on the next business day.

1.6.3 Quality Control Plan.

1.6.3.1 The Contractor shall develop and implement a commercial quality control plan to ensure safe and reliable air transportation in accordance with applicable Federal Aviation Regulation Part 135, Code of Federal Regulations (CFR) 32 CFR Part 861, and/or other applicable Civil Aviation Authority regulations. Contractors are responsible for amending or supplementing their quality programs to assure management oversight in austere locations. The contractor shall provide a Quality Control Plan to the Government within 15 days of contract award.

1.6.3.2 The Contractor shall ensure risk management procedures are in place and effectively implemented.

1.6.4 Insurance.

1.6.4.1 The Contractor shall procure and maintain a level of aircraft, cargo, and/or passenger liability insurance as required by the FAA and 14 CFR 205.5.

1.6.4.2 The Contractor will maintain minimum insurance coverage, as defined in 14 CFR 205.5, for bodily injury to or death of a person, and for damage to the property of others, resulting from the carrier's operation or maintenance of aircraft.

1.6.4.3 The United States Government accepts no financial liability should any Contractor personnel be taken hostage or be killed during any mission or while under contract with the Government.

1.6.4.4 The Contractor shall maintain control of cargo and passengers transported while conducting air operations. The Contractor is liable for refunding the cost of any cargo lost while in possession of the carrier, except as a result of hostile action. The Contractor shall be liable for injury or death to passengers while those passengers are being transported by the Contractor, except as a result of a friendly fire incident, enemy fire incident, a passenger expires enroute from pickup to medical facility or any other circumstance outside of the Contractor or Subcontractor’s control.

1.6.5 Positioning and Depositioning. Following contract award, the contractor shall position personnel, equipment and aircraft in accordance with the lead-in/positioning plan no more than 60 days prior to the start of performance.

Contractor shall be fully positioned and operational by performance start date.

Depositioning of personnel, equipment, and aircraft shall occur no later than 30 calendar days after the last day of performance under this contract or notification from the CO, whichever occurs first. The CO will notify the Contractor to deposition only when the Government terminates this contract for any reason, including no longer having a need for services to continue through the performance periods of this contract. The Contractor forfeits payment for depositioning if employees and aircraft are not depositioned out of the AUTEC terminal and hangar within 30 calendar days after the end of this contract, unless otherwise approved, in writing, by the CO. The Government will not pay for any positioning or depositioning costs associated with alternate aircraft used for the convenience of the Contractor.

1.6.6 Transition-In Plan. The contractor shall ensure minimal service disruption to vital Government business and no service degradation during and after the Transition-In period. All transition-in activities shall be completed thirty (30) calendar days after the start date of the contract. The contractor shall deliver their proposed Transition-In Plan with proposal submission.

1.6.7 Transition-Out Plan

1.6.7.1 During the transition period, the incumbent contractor shall provide the assistance and support required to ensure the orderly transition of all logistics support and provide transitional planning necessary to enable the follow-on contractor to commence uninterrupted operations at the end of the transition period. The contractor shall also establish and maintain effective communication with the incoming contractor/Government personnel for the period of the transition via weekly status meetings. The contractor shall ensure follow-on contractor personnel are permitted access to observe all operations, including workflow, priorities, scheduling, equipment handling/processing, parts storage, safety, and security.

Familiarization visits shall not interfere with the activities of the incumbent contractor or Government personnel.

1.6.7.2 The contractor shall provide and implement a Transition-Out Plan within 45 (forty-five) calendar days prior to expiration or notification of contract termination. To ensure a seamless transition, the contractor shall identify how it will coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

• Project management processes

• Points of contact

• Location of technical and project management documentation

• Schedules and milestones

• Status of ongoing technical initiatives

• Appropriate contractor-to-contractor coordination

• Transition of key personnel Actions required of the Government

• File plan, work related documents, files, policies and processes

• Inventories of hardware (H/W), software (S/W), Government

Furnished Equipment (GFE)

• Access permission by individuals to locations in which they support

1.6.7.3 The contractor shall organize all work-related documents and files, store them on the designated Government collaboration tool and provide a file plan outlining the file structure. Status for any requirements shall be documented, to include recent, current, and pending actions. The contractor shall provide all-inclusive H/W and S/W inventories. In addition, the contractor shall provide a complete list of all badges, vehicle passes (if applicable), and Common Access Card (CAC) list of all individuals currently working on the contract.

1.7 Operational Services.

1.7.1 The Contractor shall provide safe transportation of personnel and cargo throughout the AOR. The Contractor shall provide, operate, maintain, and fuel aircraft throughout the AOR to meet the requirements identified herein. Support shall also include natural disaster evacuation from Andros Island and will be coordinated in advance with AUTEC. USTRANSCOM will notify the Contractor of the Tasking Authority for this contract. Only the authorized Tasking Authority may order services under this contract PWS.

1.7.2 Mission Planning. Missions will be planned and scheduled in accordance with this Contract. The Government may suggest flight plan based on mission requirements, but the Contractor is solely responsible for the eventual flight plan. When planning missions, the Contractor will consider elevations and distances. If required and approved by the Government, the Contractor is authorized to remain overnight (RON) at other locations due to weather, maintenance, routine or non-routine missions.

1.7.2.1 Aircraft shall be available to fly missions as scheduled.

1.7.2.2 The Contractor’s aircrew shall remain on the approved/filed flight plan, unless deviation for safety of flight is required.

1.7.2.3 The Contractor shall coordinate with all airfield operations centers to obtain Prior Permission Required (PPR), as required. The Contractor shall coordinate logistics (parking, fuel, maintenance, etc.) with the airfield where performance is to occur. Aircraft are chartered, meaning that every seat, and all cargo capacity, is considered sold to the Government. It is the responsibility of, and sole right of, the Government to fill the seats/cargo capacity, not the Contractor. This may lead to some legs of the flight being empty. The Contractor shall not solicit for unused seats or cargo space.

1.7.2.4 The Contractor may refuse any mission for flight safety reasons. However, the mission must be rescheduled and flown as agreed to by the Government and Contractor, as soon as possible after the circumstances causing the flight safety issue are mitigated/resolved.

1.7.3 Flight Planning.

1.7.3.1 Clearances. The Government will provide the Contractor with all passenger and cargo data necessary for the completion of aircraft clearance including customs, immigration, public health and similar documents. On arrival at the destination airport, the Government will accept passengers at the airport terminal and assume all responsibility with respect to such passengers. The Government may generate immigration and border clearance documents, such as Diplomatic Clearances and Visas. The Contractor shall retain responsibility for furnishing appropriate agencies with all required manifest, immigration, and border clearance documents, covering all personnel and cargo aboard the aircraft upon entry into the U.S. or a foreign country.

1.7.3.2 Landing Rights. The Contractor is responsible for obtaining necessary landing rights or privileges and visas, passports, restricted area passes, and gate passes for crews, route support personnel and Contractor employees to ensure total compliance with all local security requirements.

1.7.3.3 Flying in Controlled Airspace. All contract flights shall fly over established airways, domestic or international, and in controlled airspace.

Exceptions may be made to this requirement where it is impractical to follow airways or fly in controlled airspace, provided airways are intersected at the first practical point and departed at the last practical navigational fix near destination, or when area controller established airways do not exist within a flight information region. Economic considerations will not justify deviation from this procedure.

Authority to Leave Unsafe Aircraft. According to 10 USC §2640, the following determinations shall apply with regard to the authority to leave unsafe aircraft:

Determinations to Leave Unsafe Aircraft: AMC Air Carrier Survey Team members. (i.e., HQ AMC/A3B), ramp inspectors, the Military Surface Deployment and Distribution Command (MSDDC), or such other agencies as may be designated by the Secretary of Defense (or if there is no such representative reasonably available, the senior officer on-board a contract mission) may order members of the armed forces to leave a contract mission if the representative (or officer) determines a condition exists on the aircraft which may endanger the safety of the passengers. If serious deficiencies exist, the appropriate AOR POC/regional representative will initiate an operational immediate message to the next higher headquarters with a copy to the CO. In cases where such deficiencies exist, only the FAA/CAA representative and the Contractor have the authority to ground the commercial aircraft in question.

1.7.4 Airlift Passenger Service.

1.7.4.1 The Contractor shall provide airlift passenger service when requested. The actual number of passengers will be determined by cargo, distance, altitude, and temperature at the desired location. The Pilot in Command (Contractor) is responsible for determining the safe loading limits and cargo/passenger combinations.

1.7.4.2 The Contractor will be provided a passenger manifest prior to boarding.

The Contractor shall not permit any personnel to board the aircraft that is not manifested. A copy of the passenger manifest will be left with the appropriate ground personnel at the departure airfield. The Contractor will maintain the approved passenger manifest until mission is complete. The passenger manifest information contains personally identifying information and that such is controlled unclassified information that requires compliance with Defense Federal Acquisition Regulation (DFARS) 252.204-7012. For informational purposes, eligible passengers could include military forces approved by the AOR/regional commander.

Local, provincial and national government representatives are not authorized to utilize airlift services provided under this contract for personal transportation.

1.7.4.3 The Contractor is ultimately responsible for determining passenger weight and cargo weight. If calibrated scales are not available or feasible, the Contractor may elect to use handheld and portable type scales. If scales are not available, interrogated weights can be used if in compliance with applicable Federal Aviation Regulations.

1.7.4.4 All aircraft will utilize appropriate aviation restraining devices in order to ensure the safe transport of passengers.

1.7.4.5 Aircraft and aircrews must be compliant with requirements in 32 CFR Part 861, DODI 4500.53 and Additional Standards for Department of Defense (DOD) Contract Aircraft Operations under applicable Federal Aviation Regulation Part 135, and Non-FAA Governed Aircraft Operations (Noncommuter) (Passenger), or CAA equivalent. The Contractor will ensure that all mission aircraft are operated by the number of pilots required by the FAA for the specific mission (i.e., cargo/passenger service). The pilot(s) will be rated in the type, design, and series for the aircraft being flown. Pilots shall be instrument rated and current. Failure to meet pilot requirements will result in that aircraft being Not Mission Capable impacting the Contractor’s operational readiness.

1.7.4.6 Offloading personnel shall be accomplished within 30 minutes or less to comply with potential Maximum on Ground (MOG) restrictions and safety considerations, unless deviation is approved by the government or controlling airfield authority.

1.7.4.7 The Government will provide passenger screening, weighing of all passengers and baggage, baggage loading/unloading, and boarding services at both MYAF and KPBI. On occasion, short notice conveyance of emergent equipment may be requested. This should be considered as Space Available (Space A) baggage/cargo if aircraft weight and balance allow. These short notice items are typically no larger than 2’ x 2’ x 3’ and weigh no more than 50 lbs.

2.0 BILLING

2.1 Invoicing. Invoices will be submitted monthly through Procurement Integrated

Enterprise Environment (PIEE) Wide Area Workflow (WAWF) e-Business Suite. The contractor shall bill for actual hours flown, monthly basing cost, actual fuel costs, and other allowable reimbursable costs. The contractor may invoice for additional flight hours outside of their control, including weather and other unexpected events. The contractor shall provide all receipts applicable to all reimbursable expenses. All indirect costs, such as overhead, G&A, profit, etc., are specifically prohibited.

2.2 Flight Hour Calculations. Contractors will only be paid for flight hours flown in support of missions as assigned by the Tasking Authority. Flight hours are calculated from the moment the aircraft moves under its own power (block out) and ends when the aircraft engines are shut down after landing (block in). In no event shall the flight hour calculation include time when the aircraft’s engine(s) are shutdown, or the aircraft is not being flown in support of missions directed by the Tasking Authority. Contractor flights not directed by the Government are non-billable, e.g., flights to an offsite maintenance location.

2.2.1 Flight hours shall be reported and billed in hours and tenths of hours. When entering hours or tenths of hours on forms and reports, a zero is entered on either side of the decimal (i.e., 2.0 when entering two full hours of flight time or

0.7 when entering 38 minutes of flight time). Fractions of flight hours shall be determined using the following table:

Table 2:

Minutes Parts of hour 0 0.0 1-6 0.1 7-12 0.2

13-18 0.3 19-24 0.4 25-30 0.5 31-36 0.6 37-42 0.7 43-48 0.8 49-54 0.9 55-60 1.0

2.2.2 Recovery. The Contractor is responsible for recovering disabled, damaged, or destroyed aircraft. The Government may, at its discretion, assist if resources and time are available. Any recoverable cargo will be returned to the Government.

2.2.3 Fuel. All fuel costs shall be separately priced and reimbursed by the Government. The Government will not supply fuel and will not supply fuel systems or equipment to support contract fixed wing operations. Fuel consumed as a result of the Contractor determining to replace, swap out aircraft or aircrew shall not be reimbursed by the Government. The contractor shall be responsible, at its own expense, for properly disposing of expired fuel.

2.2.4 Expenses. The Government will not reimburse expenses that are considered normal operating costs and are not unique to this requirement. For example:

Additional office space, additional storage space, rent for storage containers, Value-Added-Tax Fees, waste management fees, container fees, ferrying costs for crews or alternate aircraft not required by the Government, and other common business and operation expenses.

2.2.5 Taxes. Any Federal transportation taxes that the Contractor is required to pay for performance of this contract shall be added to the Contractor’s invoices as a separate item, and the Government shall reimburse the Contractor, at cost, for the amount of such taxes (Reference Public Law 97-248, Tax Equity and Fiscal Responsibility Act of 1982).

2.3 Monthly Billable Services. The monthly service rate billed by the Contractor is based upon Monthly Billable Service. The monthly service rate billed by the Contractor is based upon the mission status of each aircraft; FMC or NMC (See paragraph 1.5.1).

Billable days for each aircraft will be calculated using formulas in the table below:

Table 3:

2 or less days NMC Billable Amount = Full Monthly Service Rate

3-7 days NMC

Billable Amount = Full Monthly Service Rate (this is below 95% standard and may impact

CPARS)

8-14 days NMC Billable Amount = 80% of Full Monthly Service

Rate

15-21 days NMC Billable Amount = 60% of Full Monthly Service

Rate

22 or more days NMC Billable Amount = 0% of Full Monthly Service

Rate

3.0 DELIVERABLES SCHEDULE

3.1 Deliverables Schedule Table. All deliverables shall be submitted directly to the (COR) electronically in Microsoft Office format (e.g., Word, Excel, Power Point, Project).

Deliverables shall be identified by contract number/task order number, PWS task/subtask number, and deliverable title. All deliverables must meet professional standards and comply with the requirements set forth in this PWS.

PWS Para. Deliverable Title Initial Delivery Due Date

Government Review Time Frame

1.6.2.1. Daily Situation

Report (SITREP)

As Requested Within 5 days of submission

1.6.2.2. Daily Sortie

Report

By the 15th calendar day after the end of the month

Within 5 days of submission

1.6.3. Quality Control

Plan

Within 15 days of contract award

Within 10 days of submission

7.2. Cybersecurity

Incident Reporting

As soon as practical but no later than 72 hours after discovering a reportable cyber-incident;

Follow-on cyber-incident report within 5 days of becoming aware of a reportable cyber-incident

Ongoing until cyber-incident is resolved.

4.0 SERVICES DELIVERY SUMMARY (SDS)

4.1 Fixed Wing Matrix.

Desired Outcome PWS

Para

Performance Threshold (Metric)

Source of Data

How Often Collected

Calculation

Operational Readiness 1.2, 1.3, 1.5

Supporting aircraft(s) are available 95% or greater of the month.

Sortie report from the contractor

Data is collected daily and submitted upon request

# of flights / # of scheduled flights in a month

Aircrew shall remain on flight plan filed unless re-tasked by mission authority or deviation for safety of flight is required.

1.3, 1.4, 1.5

100% of Missions Daily

Submitted Sortie Reports

Daily # of flights that remain on flight plan/total number of scheduled flights.

Fuel Cost Control

2.2.3 Purchase 75%

fuel from DLA/ military fuel, when available.

Fuel Receipts Monthly Gallons purchased from DLA/total number of gallons purchased for the month.

Provide Reports/Invoices/ Receipts free of discrepancies and errors.

1.6.2.2, 2.1

100% accuracy of submitted reports/ invoices/ receipts.

Daily Sortie Reports, WAWF and emails

Monthly There should be no discrepancies on their reports.

5.0 GOVERNMENT FURNISHED SERVICES & EQUIPMENT

5.1. Ramp Space (KPBI). The Government will provide an AUTEC Terminal facility, which includes an attached hangar currently located (subject to change) at 1624 Perimeter Road, West Palm Beach, FL 33406. This facility includes ramp space for passenger boarding and baggage loading/unloading and is adjacent to the US Customs and Boarder Facility at

PBIA.

5.2. Fuel. The Government is available to provide military, Defense Logistics Agency (DLA) Jet- A fueling services at MYAF. No other fuel is available at this airport location.

The contractor shall have a DLA agreement for purchasing fuel at MYAF within 45 days of award of this contract. Fueling at KPBI is provided by the airport’s Fixed Based Operator (FBO). Upon approach to MYAF, the contractor shall communicate to the

AUTEC Andros Air Ops (AUTEC Contractor) for fuel requirements. When available and manifesting requirements allow the contractor shall purchase a majority of the monthly fueling on Andros. Fuel for non-contract flights should be purchased by the contractor and will not be reimbursed by the government. Contractor flights not directed by the Government are non-billable, e.g., flights to an offsite maintenance location.

5.3. Loading & Unloading. The contractor shall work directly with the Government and/or the Government’s prime contractor who provides passenger screening, passenger and baggage weighing, baggage loading/unloading and boarding services at both MYAF and KPBI. The Government will provide an immigration and customs liaison services at MYAF. The US Government prime contractor will pay all landing and other required airport fees directly to the Bahamian authorities.

6.0 OPERATIONAL SECURITY

OPSEC must be included in contracts to ensure that critical information is protected.

Disclosing this information to the adversary could potentially affect mission success and cause harm to military members, civilians, and contractors and their families. OPSEC is a process used to protect unclassified sensitive information from exploitation by an adversary.

Sensitive unclassified information—which is also referred to as critical information or critical program information (CPI)—is defined as information that is not classified but which needs to be protected from unauthorized disclosure. Examples are information labeled CUI, such as proprietary information, contractor sensitive information, limited distribution information, or PII.

6.1 Operations Security Requirements. The prime contractor and all subcontractors shall provide protection for sensitive unclassified information to limit unauthorized disclosures of critical information. The prime contractor and all subcontractors shall employ the countermeasures listed below to protect that information. These OPSEC requirements will be in effect throughout the life of the procurement from award through the conclusion of services at the end of the period of performance or other procurement termination. In any case where uncertainty or ambiguity regarding OPSEC measures exists, the contractor shall consult the requirements or contracting office’s OPSEC coordinator as soon as possible.

6.2 Countermeasures to Unauthorized Disclosure of Critical Information.

Countermeasures are required to negate the susceptibility of critical information to exploitation by an adversary or competitor. The contractor shall protect all critical information listed in a manner appropriate to the nature of the information, including use of the necessary countermeasures as listed below applicable to specific items:

• Refrain from including critical information in contract and budget documents, presentations, press releases, and other publications to that which is essential to the performance of this requirement.

• Encryption or password protection of electronically stored critical information.

• Encryption or password protection of e-mail containing critical information.

• Storage of hard copy critical information and storage media in locked containers when not in use.

• Transmission of critical information to the minimum set of recipients with a need to know.

• Immediate and appropriate destruction in a manner precluding reconstruction of all critical information no longer needed under this contract.

• Restricting verbal discussion of critical information to venues and circumstances that prevent the monitoring and interception of the discussion by unauthorized personnel.

• Refraining from the use of unencrypted telephones to transmit critical information.

• Refraining from the use of foreign postal systems to ship critical information.

• Promptly retrieving documents containing critical information printed on printers accessible by persons without a need to know the critical information.

• Use of cover pages or other appropriate means to prevent the viewing of critical information by unauthorized persons.

• The contractor shall notify the COR and USTRANSCOM security office immediately of all known and suspected compromises of critical information. If the COR cannot be reached, the contractor shall notify the supported command duty officer if after normal work hours.

7.0 CYBERSECURITY

7.1 Operationally Critical Support. The services designated under this contract are

“operationally critical support” as defined in DFARS 252.204-7012.

7.2 Cybersecurity Incident Reporting.

7.2.1 In addition to the DFARS 252.204-7012 reporting requirements for unclassified systems and 32 Code of Federal Regulations (CFR) Part 117, National Industrial Security Program Operating Manual (NISPOM) for classified systems, reportable cyber-incidents (regardless of whether the information system contains CDI or there is an impact to performance such as delivery schedule delay) include, but are not limited to, the following:

7.2.1.1 Cyber-incidents as defined in Table 4.

7.2.1.2 Notifications by a federal, state, or local law enforcement agency or cyber-center (i.e., National Cyber Investigative Joint Task Force (NCIJTF), National Cybersecurity & Communications Integration Center (NCCIC)) of being a victim of a successful or unsuccessful cyber-event, anomaly, incident, insider threat, breach, intrusion, or exfiltration.

Table 4:

Incident Category Description

Root Level Intrusion Unauthorized privileged access to an IS. Privileged access, often referred to as administrative or root access, provides unrestricted access to the IS. This category includes unauthorized access to information or unauthorized access to account credentials that could be used to perform administrative functions (e.g., domain administrator). If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

User Level Intrusion Unauthorized non-privileged access to an IS. Non-privileged access, often referred to as user level access, provides restricted access to the IS based on the privileges granted to the user. This includes unauthorized access to information or unauthorized access to account credentials that could be used to perform user functions such as accessing Web applications, Web portals, or other similar information resources. If the IS is compromised with malicious code that provides remote interactive control, it will be reported in this category.

Denial of Service Denial of Service (Incident)—Activity that denies, degrades, or disrupts normal functionality of an IS or DoD information network.

Malicious Logic Installation of software designed and/or deployed by adversaries with malicious intentions for the purpose of gaining access to resources or information without the consent or knowledge of the user. This only includes malicious code that does not provide remote interactive control of the compromised IS. Malicious code that has allowed interactive access should be categorized as Root or User Level Intrusion incidents. Interactive active access may include automated tools that establish an open channel of communications to and/or from an IS.

Ransomware Malware designed to encrypt files on a device, rendering any files and the systems that rely on them unusable. Malicious actors then demand ransom in exchange for decryption. Ransomware actors often target and threaten to sell or leak exfiltrated data or authentication information if the ransom is not paid. Ransomware is a reportable incident that may be associated with multiple incident categories depending on the attack vector and execution.

7.2.2 If the cyber-incident affects a classified system, vulnerabilities associated with the incident will be classified per the current version of USTRANSCOM Instruction 31-02, Security Classification Guide.

7.3 Cybersecurity Incident Reporting Timelines. In addition to providing the notification required by DFARS 252.204-7012, the contractor is required to notify USTRANSCOM as soon as practical, but no later than 72 hours after discovering a reportable cyber-incident. The reporting timeline begins when the incident is discovered or reported to the company, its employees, contractors, or cybersecurity firm responsible for providing cybersecurity and response for the company. The contractor shall contact the USTRANSCOM Cyber Operations Center (CyOC) via phone at 618-817-4222. If the contractor does not immediately reach the CyOC via phone, the contractor shall send an email notification to transcom.scott.tcj6.mbx.cyoc-dodin-operations@mail.mil.

7.4 Mandatory Reporting Data.

7.4.1 The contractor shall work with the USTRANSCOM CyOC through resolution of the incident. Within 72 hours of becoming aware of a reportable cyber-incident, the contractor shall provide an initial notification of the incident, even if some details are not yet available, which includes, but is not limited to, the following information:

7.4.1.1 Company Name

7.4.1.2 Who will be the POC with contact information

7.4.1.3 Contracting Officer POC (name, telephone, email)

7.4.1.4 Overall Assessment - Description of incident, data at risk, mitigations applied

7.4.1.5 Indicators of compromise

7.4.1.6 Vector of attack (if known)

7.4.1.7 Estimated time of attack (if known)

7.4.2 The contractor shall provide a follow-on cyber-incident report to the

USTRANSCOM CyOC within 5 calendar days of becoming aware of a reportable cyber-incident, which includes, but is not limited to, the following information:

7.4.2.1 Contractor unique Commercial and Government Entity (CAGE) code

7.4.2.2 Contract number affected

7.4.2.3 Facility CAGE code where the incident occurred if different than the prime Contractor location

7.4.2.4 POC if different than the POC recorded in the System for Award

Management (name, address, position, telephone, email)

7.4.2.5 Contracting Officer POC (name, telephone, email)

7.4.2.6 Contract clearance level

7.4.2.7 DoD programs, platforms, systems, or information involved

7.4.2.8 Location(s) of compromise

7.4.2.9 Date incident discovered

7.4.2.10 Type of compromise (e.g., unauthorized access, inadvertent release, other)

7.4.2.11 Description of technical information compromised

7.4.2.12 Any additional information relevant to the information compromised

7.5 Incident Reporting Coordination.

7.5.1 In the event of a cyber-incident, USTRANSCOM may conduct an on-site review of network or information systems where DoD information is resident on or transiting to assist the contractor in evaluating the extent of the incident and to share information in an effort to minimize the impact to both parties. Date and time of on-site visits will be mutually agreed upon by USTRANSCOM and the contractor in advance.

7.5.2 The contractor agrees to allow follow-on actions by the Government (e.g., USTRANSCOM, Federal Bureau of Investigation, Department of Homeland Security, DC3, etc.) to further characterize and evaluate the suspect activity.

The contractor acknowledges that damage assessments might be necessary to ascertain an incident methodology and identify systems compromised as a result of the incident. Once an incident is identified, the contractor agrees to take all reasonable and appropriate steps to preserve any and all evidence, information, data, logs, electronic files and similar type information (reference NIST Special Publication 800-61, Computer Security Incident Handling Guide, (current version)) related to the incident for subsequent forensic analysis so that an accurate and complete damage assessment can be accomplished by the Government.

7.5.3 The contractor is not required to maintain an organic forensic capability, but must ensure data is preserved (e.g., remove an affected system, while still powered on, from the network) and all actions documented until forensic analysis can be performed by the Government or, if the Government is unable to conduct the forensic analysis, a mutually agreed upon third party (e.g., Federally Funded Research and Development Center (FFRDC), commercial security contractor, etc.). Any follow-on actions shall be coordinated with the contractor via the Contracting Officer.

7.5.4 The contractor agrees to indemnify and hold the government harmless for following any recommendations to remedy or mitigate the cyber-incident following the actions under 1.5.1. and 1.5.2.

7.6 Confidentiality and Non-Attribution Statement. The Government may use and disclose reported information as authorized by law and will only provide attribution information on a need-to-know basis to authorized persons for cybersecurity and related purposes (e.g., in support of forensic analysis, incident response, compromise or damage assessments, law enforcement, counterintelligence, threat reporting, and trend analysis).

The Government may share threat…