House Democrats seek safety audit of FAA’s AI-assisted air traffic tools
The request targets safety reviews, testing plans and performance measures. Officials say humans remain in control, while lawmakers question training and safeguards.
Loading page…
The request targets safety reviews, testing plans and performance measures. Officials say humans remain in control, while lawmakers question training and safeguards.
Listen to this story
On Oct. 13, 23 House Democrats asked the Government Accountability Office to review the FAA’s SMART and FMDS systems, seeking independent answers on safety analysis, operational testing and certification, performance measures, and deployment consultation. The request is scrutiny, not a finding that either platform is unsafe; lawmakers also raised concerns about controller input, with Rep. Don Beyer joining a separate call to pause SMART. The review could clarify what evidence and oversight the FAA needs before expanding AI-assisted tools beyond the initial Washington-area rollout.
SMART launched Sept. 21 at Reagan National, Dulles, and Baltimore/Washington, combining 200 data streams into a view for aviation specialists.
The FAA says FMDS will replace its current traffic-flow system and SMART will enhance it; both sit within a 12-year, $875 million contract with Air Space Intelligence.
Lawmakers cited possible controller interference and false safety-critical outputs as risks, not documented failures; the FAA says humans will continue managing airspace.
The FAA’s new AI-assisted air traffic tools face a demand for independent scrutiny of their safety, testing and rollout. On October 13, 2026, Democrats on the House Transportation and Infrastructure Committee asked the Government Accountability Office to audit two platforms, including SMART, which the agency deployed last month to monitor Washington-area airspace.
Committee ranking member Rick Larsen, Aviation Subcommittee ranking member André Carson and 21 other Democratic committee members signed the request. Their letter to Acting Comptroller General Orice Brown covers SMART and the related Flow Management Data and Services system, or FMDS. It requests an audit, not a finding that either platform is unsafe.
The Democrats warned that SMART could interfere with experienced controllers’ decisions or generate false, safety-critical information, often called hallucinations. These are potential risks, not documented failures. They also questioned piloting a recently developed, complex tool in heavily congested Washington-area airspace.
SMART stands for Strategic Management of Airspace, Routes and Trajectories. The FAA announced its deployment on September 21. The limited rollout covers Ronald Reagan Washington National, Washington Dulles International and Baltimore/Washington International Thurgood Marshall airports.
The tool is designed to combine 200 data streams, including flight paths and weather patterns, into a centralized view for aviation specialists. Its stated goal is to help reduce delays and cancellations.
Both platforms fall under a 12-year, $875 million contract the FAA announced with Air Space Intelligence in June. The FAA says FMDS will replace its current traffic flow management system, while SMART will enhance the new system.
The committee’s letter said frontline aviation safety workers apparently had little or no input into SMART’s development and received limited training and information during deployment.
Rep. Don Beyer told Nextgov/FCW that a conversation with FAA Administrator Bryan Bedford eased some concerns. According to Beyer, Bedford assured him that veteran air traffic controllers had designed SMART, though they were not currently working in towers.
Beyer nevertheless joined a related call to pause SMART pending answers about safety testing, implementation and oversight. In his accompanying statement, Beyer called for controller feedback and independently verified testing, with findings clearly communicated to the public.
The pause letter asks how SMART performs during severe weather or outages, whether safety review requirements were waived during contracting, and what standards must precede nationwide expansion. It also asks who would be responsible if a recommendation contributed to a safety incident.
Loading discussion...
Join the conversation
Explain whether public evidence should come before or during a limited rollout.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.