Remote Tower Systems (RTS) for the National Airspace System (NAS)

Questions & Answers / Clarifications

This document provides responses to vendor questions regarding the Remote Tower Systems (RTS) for the National Airspace System (NAS) opportunity.

• Airport Participation: Airports with non-operational control towers are eligible. Participation is open to small or rural community airports, not exclusively those in the Essential Air Service (EAS) program.
• Teaming: Non-airport entities can be teaming partners, but the airport must remain the prime/signatory. Specific teaming documentation is not required, but relationships and roles must be clearly stated.
• RTS Vendors: Currently, Raytheon/Frequentis is the only vendor pursuing FAA's System Design Approval (SDA). Other vendors will be added to the Qualified Vendor System List (QVSL) upon achieving SDA.
• Funding: The FAA will contribute towards minimum SDA-compliant equipment, installation, and controller training. Airports are responsible for siting, civil/construction work, Minimum Equipment List (MEL) items, and maintenance. FCT MEL items, FTI comms for shout lines, and FDIO are not eligible for funding.
• Siting & Infrastructure: Siting will be a joint effort between the RTS vendor and Airport Sponsor, verified by the FAA. The RTS vendor and airport will propose locations, with the vendor conducting on-site tests. Airports are responsible for mast construction, civil engineering, and power systems.
• Multi-Runway Airports: While the initial SDA is for single-runway airports, FAA is working on SDA for multi-runway configurations. Deployments will initially focus on single-runway airports.
• Controller Staffing: Sponsor-funded controller staffing is the expected long-term model. Airports demonstrating commitment to this model will score higher. Future FAA Contract Tower (FCT) program support for RTS is anticipated.
• Proposal Submission: Supporting visual materials like ALPs and diagrams are considered appendices and not subject to the 10-page limit.
• Evaluation Timeline: Proposal evaluations are planned for July-August 2026, with staggered OTA awards from August to December 2026.

These clarifications provide essential details on eligibility, teaming, funding responsibilities, technical requirements, and evaluation criteria, directly impacting how vendors should prepare and submit their proposals.

Solicitation / RFP / RFQ

This Request for Proposal (RFP) from the Federal Aviation Administration (FAA) seeks proposals from non-towered airports serving small or rural communities for the implementation and deployment of Remote Tower Systems (RTSs). The FAA has approximately $36 million available to allocate for this initiative, aiming to enhance air traffic control services at qualified airports. This RFP is an amendment to the original solicitation (693KA8-26-T-00016).

• Proposals should detail technical, operational, and programmatic approaches for designing, constructing, deploying, and operating RTSs.

• Offerors must provide detailed cost proposals and implementation plans for a cost-sharing arrangement with the FAA.

• Estimated cost for the remote tower system (excluding site construction) is between $4-$10 million.

• Offerors must demonstrate experienced and qualified staff, financial ability, capability, and past performance.

• Specific requirements include providing an Airport Layout Plan (ALP) or airport description, details on existing/planned infrastructure (e.g., fiber-optic connectivity), operational environment, proposed control room space, estimated construction costs, planned air traffic services, and potential impacts from nearby facilities.

• Airports are encouraged to describe how RTS technology will impact safety and future growth.

• The FAA intends to make multiple awards.

• The anticipated North American Industry Classification System (NAICS) code is 488119 – Other Airport Operations.

• The FAA may award an Agreement or contract.

• Q&A Due: May 10th, 2026, by 5:00 PM EST

• FAA Response to Q&A Due: May 22nd, 2026, by 5:00 PM EST

• Response Due: June 22nd, 2026, by 5:00 PM EST, submitted electronically to Saaduddin.Khan@faa.gov.

• Proposals shall not exceed 10 pages (excluding Business Qualifications and Capabilities).

• Evaluation will be based on a best-value tradeoff approach, prioritizing Technical Approach over Cost/Price. Proposals offering a higher cost share will be more favorably evaluated.

• Primarily directed towards non-towered airports serving small or rural communities.

• Sponsor-owned Federal Contract Towers (FCTs) may apply, but priority will be given to Non-Federal Control Towers.

• Offerors must be registered and active in the System for Award Management (SAM.gov) at the time of submission and through award.

• This RFP is an amendment, indicating updates to the original solicitation.

• Attachments referenced include "Airport Eval Criteria" and a Sample Other Transaction Agreement.

• Costs for optional RTS components and site construction are detailed separately.

Solicitation / RFP / RFQ

The Federal Aviation Administration (FAA) is issuing this Request for Proposal (RFP) to solicit proposals from non-towered airports for the planning, development, and deployment of Remote Tower Systems (RTSs). The objective is to enhance air traffic control services, particularly for rural and small community airports, as authorized by Congress. The FAA has approximately $36 million available to allocate for RTS implementation at qualified airports. This RFP seeks responses from non-towered airports and Sponsor-owned Federal Contract Towers (FCTs), with priority given to Non-Federal Control Towers.

• Technical Approach: Proposals must detail technical, operational, and programmatic approaches for designing, constructing, deploying, and operating RTSs in alignment with FAA requirements.

• Cost Sharing: Offerors must provide detailed cost proposals and implementation plans for a cost-sharing arrangement with the FAA. Estimated RTS cost is $4-$10 million, excluding site construction.

• Airport Readiness: Respondents must demonstrate technical capability, organizational readiness, and commitment to advancing aviation technology.

• SAM.gov Registration: Offerors must be registered and active in SAM.gov at the time of proposal submission and through contract award.

• NAICS Code: 488119 – Other Airport Operations.

• Award Type: The FAA intends to make multiple awards, potentially through an Other Transaction Agreement (OTA).

• Proposal Due Date: May 15, 2026, by 5:00 PM EST.

• Submission Method: Electronic submission via email to Saaduddin.Khan@faa.gov.

• Format: Microsoft WORD (.doc/.docx) for the main proposal and Excel (.xls) for cost information. Proposal page limit is 5 pages (excluding Business Qualifications and Capabilities).

• Evaluation Criteria: Proposals will be evaluated on a best-value tradeoff basis, with Technical Approach being the most important factor, followed by Cost/Price. Higher cost-sharing contributions will be viewed favorably.

• Q&A Due: April 27, 2026.

• Q&A FAA Response Due: May 6, 2026.

• Primarily targeted at non-towered airports serving small or rural communities.

• Sponsor-owned Federal Contract Towers (FCTs) are eligible, but priority is given to Non-Federal Control Towers.

• Offerors are responsible for all proposal preparation costs.

• Attachments referenced include "Airport Eval Criteria" and "Sample Other Transaction Agreement."

Form / Attachment / Pricing Sheet

This document outlines the technical and price evaluation criteria for the opportunity. It details how proposals will be scored, providing bidders with insight into the government's priorities and expectations for a successful submission.

Technical Evaluation Criteria:

• Scoring Scale: Proposals are scored on a scale of 1 (Unacceptable) to 5 (Outstanding), with descriptions for each level.
• Specific Criteria (15 points): Evaluates the planned airport's suitability for RT implementation, including:
  • Runway configuration and length
  • Annual operations volume
  • Existing infrastructure (fiber, building space for control/server rooms)
  • Plans for supporting controllers and RTS maintenance
  • Partnerships (SLTT, academic, industry)
  • Readiness for near-term implementation
  • Demonstrated safety and economic benefits
  • Prior RT experience and willingness to participate in future FAA research.
• Additional Criteria (4 points): Assesses the respondent's understanding of the RFP scope, RTS components, benefits/limitations, and post-installation maintenance.

Price Evaluation Criteria:

• Scoring Scale: Similar 1-5 scale as technical criteria.
• Specific Criteria (2 points): Evaluates:
  • Willingness to participate in a cost-sharing agreement (percentage-based).
  • Provision of detailed information on revenue sources or documentation supporting system maintenance and controller support plans.

This document is crucial for bidders as it directly informs proposal strategy. Understanding the scoring for each technical and price criterion allows vendors to tailor their proposals to emphasize strengths that align with the government's evaluation priorities. Bidders should pay close attention to the specific scoring notes for each criterion to maximize their potential score.

Other / Unclassified

This document outlines an "Other Transaction Agreement" (OTA) between the Federal Aviation Administration (FAA) and "Non-Fed Airports" (acting as the Air Navigation Service Provider - ANSP). The primary purpose is to define roles and responsibilities for advancing, strengthening, implementing, and evaluating System Design Approval (SDA)-aligned Remote Tower (RT) systems at Non-Fed Airports. This initiative supports the FAA's Remote Tower Program and BNATCS initiatives, aiming to integrate innovative technologies into the National Airspace System (NAS) while maintaining safety and efficiency.

• Scope: Focuses on implementing and evaluating SDA-aligned RT systems for air traffic control services at selected airports. Goals include evaluating operational performance, safety, reliability, and scalability, and generating data to inform future FAA baselines for RT deployment.
• Roles & Responsibilities: Non-Fed Airports will act as the RT system integrator, responsible for design, installation, operation, and maintenance. The FAA will provide program management, technical oversight, and funding for pilot and evaluation purposes.
• Contributions: FAA funding is subject to availability and covers airfield/infrastructure upgrades and Remote Tower Center build-out. Non-Fed Airports must provide in-kind contributions including project management, staffing, facilities, and sustainment.
• Agreement Type: This is an "other transaction" agreement, not a standard procurement contract, grant, or cooperative agreement. It does not incorporate Federal acquisition law or regulation by reference.
• Intellectual Property: The Government retains Government Purpose Rights in all data developed under the agreement.
• Funding: FAA funding is limited to obligated amounts. Advance payments may be provided for equipment procurement, secured by the equipment itself.
• Termination: Either party may terminate the agreement with 30 days' written notice.
• Disputes: Disputes will be resolved through informal discussion or by the Office of Dispute Resolution for Acquisition (ODRA).
• Insurance & Liability: Non-Fed Airports must secure insurance for third-party liability. The FAA assumes no liability for Non-Fed Airports' actions. Liability claims are limited to direct damages up to the obligated funding amount.