PWS TOTAL NAVIGATON SOLUTION AND INTERNATIONAL TRIP PLANNING AND GROUND SUPPORT 5.27.2025.pdf

PDF 193 KB Posted

Attached to
Flight Program’s Total Navigation Solution (TNS)
Solicitation number
6973GH-25-T-TNSITPS
Issued by

About this file

This Performance Work Statement (PWS) outlines the Federal Aviation Administration (FAA) Flight Program Operations' requirements for a Total Navigation Solution (TNS) and International Trip Planning Services. The contract seeks a comprehensive solution to support the FAA's fleet of approximately 29 aircraft, including flight planning, electronic charting, navigation databases, and international trip support across global regions.

Key requirements include providing advanced flight planning tools with web-based and mobile interfaces, comprehensive electronic aeronautical charts, navigation databases compatible with multiple avionics systems, and 24/7 international trip planning services. The contractor must support approximately 25 international missions annually, generate around 16,000 filed flight plans per year, and offer services such as flight plan preparation, overflight and landing permit coordination, diplomatic clearances, ground handling support, and real-time flight monitoring. The solution must comply with FAA, ICAO, and other international aviation regulations, with capabilities for secure data management, cyber security compliance, and adaptable technical support across various aircraft types.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

PWS Page 1 of 13

FEDERAL AVIATION ADMINISTRATION

FLIGHT PROGRAM OPERATIONS

TOTAL NAVIGATION SOLUTION AND INTERNATIONAL TRIP PLANNING SERVICES

1. GENERAL

1.1. This Performance Work Statement (PWS) outlines the requirements for the operational, integration, maintenance, and support of Federal Aviation Administration (FAA) Flight

Program’s Total Navigation Solution (TNS) to enhance flight planning, operational navigation capabilities, International Trip Planning Services, and ground handling support.

2. SCOPE

2.1. The FAA Flight Program Operations currently operates a fleet of approximately 29 aircraft in accordance with Title 14 of the Code of Federal Regulations (14 CFR) Part 91 and Part

135. All aircraft do not operate every day. The daily maximum is 23 aircraft flying predominantly domestic US missions.

2.2. The Flight Program Operations conducts approximately 25 international missions annually (including Pacific/Asia, Europe/Middle East, Caribbean, South America, and

African theaters), averaging 21 days in length for each mission and a minimum of two flights per/day. Note: Missions get revised frequently, we average 8 to 9 revisions.

20 legs/mission minimum

40 legs/mission maximum

2.3. Flight Program Operation generates approximately 16,000 filed Flight Plans per year and will require an unlimited number of “what if” Flight Plan calculations.

Support services will be coordinated through the Flight Program Operations

Service Center or organization operating the aircraft. The Flight Program

Operations Service Center is centrally located at the Operations Control Center

(OCC) in Herndon, VA and coordinates all Flight Program Operations flight schedules and operations.

Approximately 200 users will need access to the flight planning services/internet-based application at any given time in live/real time.

2.4. The current composition of aircraft and capabilities is summarized below. The composition and capabilities are subject to change.

PWS Page 2 of 13

Aircraft Manufacturer/Type # Company Designation

Datalink Capable

XMWX

Capable

GoGo Capable

Beechcraft 300** 17 BE-300

Beechcraft 360** 1 BE-360 X X

Beechcraft 350 1 BE-350

Beechcraft C90GTi 3 C-90GTi X

Bombardier Challenger 605SB 6 CL-605 X X

Bombardier Global 5000 1 BD-700 X

**FAA Flight Program Operations anticipated gradual retirement of the BE-300 fleet, transitioning to the

BE-360 platform.

2.5. Regulatory Compliance. All services provided herein shall allow Flight Program

Operations to obtain operational authorizations required under the applicable 14 CFR parts or rules of any foreign country in which Flight Program Operations conducts operations.

2.6. The FAA has established cybersecurity and privacy policies, procedures, and processes to protect the Confidentiality, Integrity, an Availability of its networks, systems, services information, and data.

2.6.1. All contractor employees that access FAA systems shall comply with all Faa cybersecurity and privacy policies, procedures and processes, including

Presidential Directives, Executive Orders, OMB Memorandum DHS CISA Binding

Order Directives and other Federal policies.

2.6.2. A copy of FAA information security and privacy orders, including Faa Order

1370.121B FAA Information Security and Privacy: Policy is found at the following link:

https://employees.faa.gov/tools_resources/orders_notices/index.cfm/go/docume nt.information/documentID/1040976. (Internal FAA Link only). Provided upon request.

3. REQUIREMENTS

The contractor shall provide a (1) Total Navigation Solution (TNS) products and services, including flight planning tools, electronic charts, navigation databases, associated updates and technical support, (2) International Trip Planning administrative, operational support, and

24 hours-a-day/365 days-a-year flight planning services assistance, (3) Ground handling support services to include but not limited to flying/landing arrangements and permit processing, (4) Flight Monitoring, and (5) Additional services.

PWS Page 3 of 13

3.1. Total Navigation Solution:

The contractor shall provide comprehensive Jeppesen Total Navigation Solution (TNS) of products and services. These services shall include, but are not limited to, the following:

3.1.1. Flight Planning Tools: The contractor shall provide advanced, fully integrated flight planning tools that support end-to-end mission planning, route optimization, real-time updates, and compliance with national and international aviation standards. These tools shall be user-friendly, highly reliable, and compatible FAA platforms.

3.1.1.1. The contractor shall provide a web-based portal solution for primary interaction with the Flight Program Operations that allows full visibility of the immediate status of flight planning services provided, including trip execution status, overview, services, documents, messages, computer flight plans (CFP), and the itinerary.

3.1.1.2. The web-based portal shall be available to the Flight Program Operations with full access upload documents in the following formats, PDF, DOC, XLS, XML, KML, KMZ, and other industry standards. The web-based portal shall have an iOS mobile application for mobile access to the same data.

3.1.1.3. The web-based portal/server shall have an API that is supported and modifiable to exchange mission and crew information from the FAA Flight

Operations Management System (FOMS) software.

3.1.1.4. The iOS application shall support, integrate, and update on the AIRAC cycle, navigation data, charts from the FAA, DoD, and Jeppesen worldwide.

3.1.1.5. The iOS application shall also support electronic oceanic plotting of

Category II navigation legs and provide the capability to save all flight plans, weather, plotting, and documents used for the Category II navigation flight. Portal servers shall be assessed, authorized, and monitored in accordance with FAA cybersecurity standards. Maintain compliance with relevant FAA, DoD and ICAO navigation data regulations.

3.1.1.6. The contractor shall provide a Software Application Programming

Interface (API) that supports the exchange of flight mission and crew data.

3.1.1.7. Integrated iPad electronic charting receives and displays all flight planning data.

3.1.1.8. The contractor shall provide current and continuously updated navigation data and software products, ensure full compatibility with existing avionics and EFB platforms.

PWS Page 4 of 13

3.1.1.9. The flight planning tool will provide a method to perform weight and balance calculations for each flight. Also, ensure compatibility with current and future EFB/Avionics platforms.

3.1.1.10. The flight planning tool will also include the capabilities to provide

Comprehensive runway suitability assessment and aircraft performance calculations.

3.1.1.11. Fuel and performance calculations will use aircraft manufacturers approved performance data and offer options for all available manufactures provided climb, enroute cruise, and decent performance modes (e.g., 300Kts climb, Long Range Cruise (LRC), Max Range, High

Speed Cruise (HSC), etc.).

3.1.1.12. Airport and enroute charts

3.1.1.13. Weight and balance computations/load manifest

3.1.1.14. Aircraft performance calculations and performance models customized for each aircraft type listed herein and the ability to bias for each aircraft’s performance variances.

3.1.1.15. Extended Twin Engine Operations Performance Standards (ETOPS), drift down, and Equal Time Point (ETP) calculations.

3.1.1.16. Integrated United States airport data that includes every airport

(regardless of runway length, surface type, or owner) with Fixed Base

Operator (FBO) information, Aircraft Rescue and Firefighting (ARFF) Index, contract fuel providers, etc.

3.1.1.17. Integrated worldwide airport data that includes all hard surface runways with at least 4000 feet or more in length.

3.1.1.18. Critical fuel summaries/ETP calculations/Tankering

3.1.1.19. Route cost comparison

3.1.1.20. Integrated Safety Management System (SMS) tools

3.1.1.21. Recently and frequently cleared routes

3.1.1.22. Coded Departure Routes (CDRs)

3.1.1.23. Air Traffic Control (ATC) preferred routes

3.1.1.24. ETOPS computations

3.1.1.25. Runway analysis including obstacle data

3.1.1.26. RAIM analysis

3.1.1.27. Contractor will generate test and preliminary CFPs for all aircraft operated by Flight Program Operations using a suitable Contractor provided flight planning application, or a suitable third-party system as determined by both parties. CFPs will be electronically computed using:

3.1.1.28. Current, forecast, and historical weather and the ability to validate with

FAA, EUROCONTROL, and other international computer flight planning validation systems.

PWS Page 5 of 13

3.1.1.29. Consider current NOTAMs, custom defined airspace and FIR avoidances, weather, and winds optimization, TFRs and flight planning restriction avoidance, and flow control by international civil aviation authorities

(CAA). Flight planning capability for Special Areas of Operation (North

Atlantic Minimum Navigation Performance Specifications (NAT/MNPS), Reduced Vertical Separation Minimum (RVSM), Area Navigation (RNAV), and Required Navigation Performance (RNP) airspace).

3.1.2. Electronic Charts - The contractor shall provide comprehensive Jeppesen electronic charting products and services that support safe and efficient flight operations for FAA Flight Programs.

3.1.2.1. Chart Types and Coverage The contractor shall supply the following types of electronic aeronautical charts:

Enroute Charts (High and Low Altitude): Depicting airways, waypoints, airspace boundaries, and navigation aids.

Terminal Area Charts (TACs): Showing complex airspace structures near major airports.

Standard Instrument Departures (SIDs), Standard Terminal Arrival

Routes (STARs), and Instrument Approach Procedures (IAPs): Fully geo-referenced and compliant with FAA and ICAO standards.

• Airport Diagrams and Ground Movement Charts: Including taxiways, ramps, gates, and runway data for situational awareness during surface operations.

All available Special Instrument Departures (SIDs), Standard Terminal

Arrival Routes (STARs), and Instrument Approach Procedures (IAPs):

Fully geo-referenced and compliant with FAA and ICAO standards.

Visual Flight Rules (VFR) Charts (where applicable): For operations in

Class G and Class E airspace.

Special Use Airspace (SUA) and Military Training Routes (MTRs): Clearly identified with effective times and altitudes.

3.1.2.2. Chart Format and Compatibility

All electronic charts shall be provided in formats compatible with supported Electronic Flight Bags (EFBs), onboard avionics systems, and ground planning stations

Charts shall support both raster and vector formats, with full geo-referencing to enable overlay on moving maps and navigation displays.

Shall support interactive features such as zoom, pan, and layer toggling on compatible devices.

3.1.2.3. Data Accuracy and Timeliness

PWS Page 6 of 13

Chart data shall be updated and distributed in accordance with the standard Aeronautical Information Regulation and Control (AIRAC) 28-day cycle.

The contractor shall verify published data accuracy against FAA, ICAO, and Jeppesen sources and ensure compliance with other approved providers.

Urgent amendments (e.g., NOTAM-related changes) shall be available in a timely manner and flagged to end users.

3.1.2.4. Chart Usability and Features

Users shall be able to annotate, highlight, and save personalized notes on electronic charts. •

Enable integration with real-time weather overlays, aircraft position, and traffic displays were supported by aircraft systems.

Provide filters or toggles to simplify chart displays based on user preference (e.g., IFR-only, VFR-only, terrain, airspace).

3.1.2.5. Accessibility and Redundancy

Charts shall be downloadable and viewable offline in case of connectivity loss.

Multiple methods of access shall be available (e.g., secure cloud-based portal, app, direct data feed).

Contractor shall provide mechanisms to store and archive previous versions of charts for reference and legal compliance.

3.1.2.6. Compliance

All charts shall comply with applicable FAA, ICAO, and DoD standards, including FAA AC 120-76 and RTCA DO-257/DO-272 standards for electronic charts.

Charts used for navigation in military operations shall meet relevant

Joint Military Symbology standards where applicable.

3.1.3. Navigation Database: The contractor shall provide and maintain comprehensive, Jeppesen-sourced navigation databases supporting all required avionics systems and mission planning tools. These databases shall be compatible across FAA platforms.

3.1.3.1. Content and Coverage

Aeronautical data, airports, NAVAIDs, SUA, comms, terrain/obstacles, global airspace structures

PWS Page 7 of 13

Full global coverage per operational requirements

3.1.3.2. Format and System Compatibility

Compatible with FMS from Honeywell, Collins, Thales, and Universal

Support JMPS, FalconView, Jeppesen FliteDeck, and others

Support formats: ARINC 424, XML, CSV, proprietary

Signed and validated files

3.1.3.3. Update Frequency and Delivery

Standard AIRAC 28-day cycle

Out-of-cycle updates for critical changes

Delivery via web portal, APIs, or physical media

3.1.3.4. Update Management Tools

Upload/verification tools

Version tracking and rollback

End-user executable update processes

3.1.3.5. Security and Compliance

FIPS 140-2 compliant encryption

FAA cybersecurity compliance

User authentication and access logging

3.1.3.6. Updates

Provide timely and secure updates for all Jeppesen products

Enable automated and manual updates with integrity verification

3.2. International Trip Planning Service

The Contractor shall provide comprehensive international trip planning support services to ensure the safe, compliant, and efficient execution of global aviation operations. These services shall include, but are not limited to, the following:

3.2.1. Flight Plan Preparation and Filing- Contractor personnel shall be responsible for preparing, validating, and filing all international flight plans. Flight plans shall comply with ICAO, FAA, EASA, and local civil aviation authority requirements. The contractor shall ensure accurate routing based on real-time weather, NOTAMs, and airspace restrictions. - Contractor shall maintain 24/7 operational readiness to perform re-routing services to support in-flight or short-notice operational changes.

PWS Page 8 of 13

3.2.2. Provide a final flight plan which includes all the information required in accordance with the applicable 14 CFR Parts and/or International Civil Aviation Organization

(ICAO) Flight Plan requirements.

3.2.3. The Contractor shall reply/update flight planning data (e.g. aircraft weight & balance, aircraft equipment or performance data) and/or ground handling service within 2 hours of government requests.

3.2.4. The contractor shall use experienced flight planners with a minimum of 3 years’ experience with planning international trips for state/DoD aircraft using Aircraft and Personnel Automated Clearance Systems (APACS) and the DoD Foreign

Clearance Guide (FCG).

3.2.5. Route and Airspace Management- Optimize flight routing based on cost, fuel efficiency, weather, and geopolitical considerations. - Advise and file for required airspace reservations including RVSM, NAT HLA, and special use airspace access as applicable.

3.2.6. Overflight and Landing Permits- Secure all necessary overflight and landing permits for each international destination and enroute airspace. Provide documentation and regulatory support required by foreign civil aviation authorities. Maintain an active database of permit lead times and country-specific requirements

3.2.7. Diplomatic Clearances and Regulatory Compliance - Coordinate with U.S.

government agencies and foreign embassies for diplomatic flight clearances when required. Ensure all international flights adhere to applicable aviation treaties, security protocols, and export control regulations.

3.2.8. Customs, Immigration, and Visa Coordination- Support the crew and passengers with visa requirement guidance, customs pre-clearance (where available), and immigration compliance. Coordinate with international airports to streamline entry and exit procedures.

3.2.9. Operational Package and Briefing - Provide a comprehensive trip briefing package to flight crews, including:

Validated and filed flight plans

Weather forecasts and turbulence analysis

NOTAM summaries

Airport information and charts

Permit status summaries

PWS Page 9 of 13

3.2.10. The Contractor will provide CFPs textual and graphical in a customizable format and delivered as digital files in portable document format (PDF), text, and machine-readable file formats. They will also be deliverable via facsimile machine

(i.e., FAX), email attachment, file download from secure web portal, and delivered to a companion mobile iOS application. Also, maintain a database of readily available CFPs for a minimum of 12 months. Shall have pre-formatted

International Civil Aviation Organization (ICAO) flight plan printing capability and the ability to electronically file flight plans which contain en route holding or delay information. Finally, provide customized flight plan formats with options to select the fastest route, the most fuel-efficient route or another user defined route.

3.2.11. Transmit flight plans defined in 3.1.5, using ARINC standards via Aircraft

Communication Addressing and Reporting System (ACARS)/ Aeronautical (airline)

Operational Control (AOC), directly to aircraft flight management systems (FMS) anywhere in the world and be compatible with the commercial standard avionics and FMS.

3.2.12. For each flight leg, provide a separate electronic machine-readable full CFP data file in ARINC 633 standard format (e.g., xml, text, etc.). The data shall be delivered in a machine-readable format compatible with AA and third-party electronic flight bag (EFB) applications situational awareness. This file will include the entire digital representation of all information contained in the printed flight plan (non-exhaustive list): aircraft performance and fuel calculations, winds, temperatures, ETP, PNR, ETOPS, reclear calculations, and divert airfields.

3.2.13. The Contractor shall provide flight planning assistance and technical support 24 hours-a-day, 7 days-a-week dispatch center support, with an immediate response time, Slot and STMP reservations (US/Canada), Worldwide technical support, Dosimetry reporting, Security briefings, and US and Mexico APIS manifest

3.3. International Ground Handling Support Services

The Contractor shall provide full-service ground handling coordination and support to ensure safe, efficient, and compliant operations. This includes pre-arrival coordination, on-the-ground services, and post-departure support, with 24/7 availability. These services shall include, but are not limited to, the following capability:

3.3.1. To obtain Diplomatic clearances using the Department of Defenses’ Aircraft and

Personnel Automatic Clearance System (APACS) and conduct coordination with

Defense Attaché Offices.

3.3.2. Facilitating fuel, aircraft servicing (i.e. ground power, lavatory, etc.)

PWS Page 10 of 13

3.3.3. Customs and special authorizations

3.3.4. Obtaining foreign government clearances (upon request),

3.3.5. Catering (upon request),

3.3.6. Crew/passenger transport and baggage handling from the secure ramp area to the customs/in-processing area (upon request),

3.3.7. Overnight accommodation and crew transportation (to/from hotel etc., as requested)

3.3.8. Arrange aircraft security ground handling support on behalf of the Government at

International locations (upon request).

3.3.9. The United States considers FAA aircraft to be state aircraft. Under U.S.

Government policy on aviation-related fees, state aircraft are not required to pay navigation or overflight fees ***

3.3.9.1. Airport Expenses: Any additional fees billed from airport handlers for items such as but not limited to: hangars, landing fees, parking fees, security screening (if required), crew identification badges (as required), vendor communications/arrangement fees, departure fees and ramp fees

(not subject to U.S. Government exemption for FAA aircraft) will be reimbursed in accordance with 5.2 of this document. Fuel purchases will be direct billed and are not included under this contract.

3.4. Flight Monitoring

The contractor shall:

3.4.1. In real-time, monitor the progress of each international flight including enroute, destination and alternate airport NOTAMS, weather trends, enroute winds and weather, including pilot reports (PIREP), TFRs, other flight restrictions, and the status of airport and navigational facilities.

3.4.2. During each trip leg, report to the Pilot in Command (PIC) any additional information that could affect the safety of the flight, including when weather or issues reported in NOTAMS and PIREPS that may negatively affect the successful completion of the current trip leg as filed. Contractor shall have the capability to deliver this information to the PIC while in flight or during intermediate technical stops, including data in 3.3.1, via ACARS/AOC, e-mail, and/or satellite voice and data communication.

3.4.3. Maintain communication with ground handling agents and keep them informed as to the progress of the flight. Inform the PIC via ACARS/AOC, e-mail, and/or satellite

PWS Page 11 of 13 voice and data communication of updated arrival information such as parking locations or arrival changes and/or restrictions.

3.4.4. Provide Graphical Flight Tracking with Flight Aware interface that will:

3.4.4.1. Include Global Beacon service when available

3.4.4.2. Securely track aircraft from any computer and/or mobile device

3.4.4.3. View other IFR traffic, weather and ATC trends

3.4.4.4. Monitor in-flight movements and diversions

3.4.4.5. Point-and-click communication with the flight crew for data link equipped aircraft

3.4.4.6. Access Aircraft Situational Display Information (ASDI)

3.5. Additional Services

The contractor shall provide User Training/Travel/Over-and-Above (O&A)

3.5.1. Upon contract start or flight planning system software modifications, government on-site user training may be required by the government. Contractor shall provide instructors, course materials, syllabus, timelines, supplies, books, and other materials as required.

3.5.2. New user training, if required, will be conducted on government sites or via internet web meetings. The contractor shall provide instructors, course materials, syllabus, timelines, supplies, books, and other materials as required at the negotiated per course.

3.5.3. The contractor shall provide User Training as an O&A on an as needed basis for educational purposes. O&A actions shall be requested IAW the contract. The contractor shall have the capability to provide the User Training within one month of the official request.

3.5.4. Travel may be associated with requirements for onsite training at any facility designated by the FAA. Travel estimates for each person per trip shall be identified in writing when the FAA issues requests for training. After government receipt of estimated travel expenses, the Contracting Officer (CO) via coordination with the Contracting Officer’s Representative (COR) will authorize Contractor travel by the Travel Authorization (TA) Form. All travel arrangements are the responsibility of the Contractor and are reimbursable in accordance with FAA

Travel Policy.

4. INVOICING

The Contractor shall submit billing information as support for the payment of invoice as described in Section G of the contract document on a per mission basis and in accordance with CDRL A001. Acceptance and payment are contingent upon FAA receipt of

PWS Page 12 of 13 acceptable service, accurate invoice, and the supporting documentation of services rendered (e.g., handler’s bill).

5. DELIVERABLES

The Contractor shall provide all reports to the Contracting Officer (CO) and the Contracting Office

Representative (COR). The Contractor shall be responsible for providing the following deliverables:

5.1. Monthly Status Report - The Contractor shall provide a Monthly report that details

Invoice Details – detailing charges by Region, Country, City, Airport w/Qty & Admin Fees and invoice summary

Issues/Risks

Next Steps

5.2. Quarterly Report of Trip Legs – The Contractor shall provide a quarterly summary report of the following:

Total legs

Non-cancelled legs

Cancelled legs

Domestic legs

International legs

Missions

Training missions

Non-cancelled missions

Average Revision/mission

Deliverable Title Frequency Deliverable Date

Monthly Status Reports Monthly 5 business days after the end of the month send a copy to the

Contracting Officer Representative

(COR)

Quarterly Report of trip Legs Quarterly 5 business days after the end of each 90-day period send a copy to the Contracting Officer Representative (COR)

User Training Course Plan As Required 5 days after request

6. DEFINITION OF TERMS

BE Beech King Air Aircraft

CFR Code of Federal Regulations

CL Challenger aircraft

PWS Page 13 of 13

CLIN Contract Line-Item Number

CO Contracting Officer

COR Contracting Officer’s Representative

COTR Contracting Officer’s Technical Representative

CDRL Contract Data Requirements List

ETOPS Extended Twin Engine Operations Performance Standards

ETP Equal Time Point

FAA Federal Aviation Administration

Flight Program Operations

FAA Flight Program Operations

HTTPS Hypertext Transfer Protocol Secure

ICAO International Civil Aviation Organization

NAT/MNPS North Atlantic Minimum Navigation Performance Specifications

NOTAM Notices to Air Missions

RNAV Area Navigation

RNP Required Navigation Performance

RVSM Reduced Vertical Separation Minimum

SOW Statement of Work

SSL Secure Socket Layer

TA Travel Authorization

File details come from the government source that posted it. Updated .