FAA AI Air Traffic Control Is an $875M Bet on Prediction, Not Autonomy

The FAA is launching an $875 million AI program to predict traffic conflicts before controllers must resolve them under pressure. The FAA AI air traffic control initiative begins around Washington, D.C., placing new software inside one of America’s busiest aviation regions.

The system is called SMART, short for Strategic Management of Airspace, Routes, and Trajectories. It will combine schedules, weather, airport capacity, airspace conditions, and operational limits in one predictive platform.

That description sounds more autonomous than the planned system actually is. SMART will not replace controllers, direct aircraft independently, or eliminate the need for upgraded radar and communications equipment.

Instead, it will recommend earlier adjustments to routes and departure times. Human traffic managers and controllers will remain responsible for operational decisions.

That distinction defines the real test. The FAA is betting that better forecasts can reduce the conflicts controllers face, even while staffing shortages and aging infrastructure remain unresolved.

Air Space Intelligence, or ASI, received the 12-year contract in June 2026. Its software must now move from airline planning into a public system that manages more than 80,000 flights each day.

The rollout also creates a difficult benchmark for government AI. Success will depend on fewer delays, usable recommendations, reliable data, and controller trust, not the presence of an AI label.

The FAA AI Air Traffic Control Rollout Starts in Washington

SMART changes when traffic problems are addressed, moving decisions from late operational reactions toward earlier planning.

According to the initial rollout details, the FAA plans to deploy SMART first in the Washington metropolitan area. Expansion to other regions would follow the initial implementation.

Washington offers a demanding proving ground. The region combines several commercial airports, military activity, restricted airspace, dense traffic, and frequent weather disruptions.

Those conditions produce constraints that cannot be solved by finding a shorter line on a map. A useful recommendation must respect runway capacity, sector workload, weather, airspace restrictions, and airline operating plans.

SMART is designed to examine those variables before flights depart. It can then identify projected congestion and suggest changes to schedules or trajectories.

A trajectory is the planned path of an aircraft through space and time. Coordinating trajectories early can prevent several individually reasonable flights from competing for the same limited capacity.

The FAA says SMART will continuously evaluate airline schedules, weather, airport capacity, airspace conditions, and operational constraints. Its models will predict traffic flows and flag potential conflicts before they occur.

That capability sits within Flow Management Data and Services, or FMDS. FMDS is intended to become the data and software backbone of the FAA’s Air Traffic Control System Command Center.

The distinction between the two systems matters. FMDS provides the shared operational foundation, while SMART adds predictive planning capabilities using that data.

The agency’s program announcement says FMDS will estimate current and anticipated traffic flows. Command Center managers can use those estimates to adjust schedules and trajectories.

SMART extends that process further into the future. The FAA says the software can help identify capacity problems days, weeks, or months before an operation.

Not every forecast will remain useful as departure time approaches. Weather changes, maintenance problems, runway closures, and airline decisions continually alter the operating picture.

The platform therefore needs more than an impressive long-range prediction. It must update recommendations quickly and show operators why the underlying picture changed.

The first deployment should reveal whether SMART can perform that work in a live setting. It will also show how much training and workflow redesign the system requires.

A recommendation that arrives too late offers little operational value. A recommendation that arrives early but lacks credibility will be ignored.

That makes Washington more than a limited launch market. It is the first public test of whether the FAA can integrate predictive AI without adding another layer of operational friction.

SMART Tries to Move Decisions Ahead of the Delay

The program’s central idea is simple: prevent congestion before aircraft leave the gate instead of managing its consequences in the sky.

Air traffic management often becomes reactive because the system cannot fully anticipate how separate constraints will interact. A storm in one region can disrupt routes, aircraft rotations, crews, gates, and airport arrival rates elsewhere.

Airlines and the FAA already plan for those conditions. However, their data, priorities, and tools do not always produce one shared view of future capacity.

SMART is supposed to create that view. It will aggregate operational data and calculate where demand is likely to exceed available airspace or airport capacity.

The software might identify several departures converging on a constrained route during severe weather. Traffic managers could then adjust departure times or trajectories before those aircraft join the flow.

That intervention differs from tactical separation, the immediate work of keeping aircraft safely apart. Controllers will continue handling tactical decisions through established systems and procedures.

FAA Administrator Bryan Bedford described the existing problem as thousands of scheduling conflicts entering the system each day. Those conflicts eventually appear as congestion, reroutes, ground stops, or delays.

SMART targets the planning layer where some of those conflicts originate. It does not make additional runway space, create clear weather, or certify new controllers.

Its value comes from allocating limited capacity more coherently. The platform could also expose unused routes that existing processes overlook during complex operations.

FMDS supports that objective with flight plans, schedules, and real-time position updates. Predictive models can compare expected demand with changing capacity across the National Airspace System.

For severe weather, the FAA says the platform will support localized rerouting. That matters because broad restrictions can delay flights that never needed to enter the affected area.

More precise interventions could reduce those unnecessary effects. Airlines would also gain more predictable information for managing gates, crews, fuel, and passenger connections.

Yet optimization creates competing priorities. The shortest system-wide plan may not provide the best outcome for every airline, airport, or individual flight.

The FAA must therefore define how recommendations balance efficiency, equity, safety margins, and operational resilience. Those rules cannot remain hidden behind a model output.

Traffic managers also need to understand what changed between successive recommendations. Without that context, frequent updates can look like instability rather than improved information.

This is where the FAA AI air traffic control program faces a human factors challenge. The system must communicate uncertainty without overwhelming people already managing a complex operation.

A confidence estimate can help, but only when users understand what it represents. A polished score cannot compensate for incomplete weather information or inaccurate schedule data.

The best outcome is not automatic compliance with every prediction. It is faster, better-informed coordination among the FAA, airlines, airports, and controllers.

That makes SMART a decision-support platform rather than an autonomous controller. The difference should remain explicit throughout testing, procurement, and public communication.

Better Software Does Not Erase the Controller Shortage

Predictive software can reduce avoidable workload, but it cannot substitute for enough trained controllers at critical facilities.

The staffing problem predates the SMART award. Hiring disruptions, retirements, training attrition, and pandemic-era effects have left the FAA below earlier workforce levels.

A December 2025 workforce review found that the FAA employed 13,164 controllers at the end of fiscal 2025. That was about 6 percent fewer than in 2015.

Traffic moved in the opposite direction. Total flights using the air traffic control system rose about 10 percent between fiscal 2015 and 2024.

That combination places more demand on a smaller workforce. Short staffing can force traffic restrictions, increase overtime, lengthen training burdens, and reduce operational flexibility.

The shortage cannot be repaired quickly. Applicants must pass aptitude screening, medical and security reviews, academy training, and facility-specific instruction.

GAO found that the complete process can take two to six years. Many applicants leave or fail to qualify before becoming certified controllers.

The FAA has increased hiring and streamlined parts of the process. The Transportation Department said nearly 2,400 controllers were hired after March 2025, although certification still takes time.

SMART addresses a different part of the problem. It can help staff manage demand more effectively, but it cannot fill an empty position or train a new controller.

That boundary has become central to public skepticism. Some controllers and aviation observers question whether software spending distracts from compensation, retention, training, and facility staffing.

The criticism becomes misleading if the choices are treated as perfectly interchangeable. A software contract and a workforce program use different budgets, capabilities, and implementation paths.

Still, the underlying concern is valid. The FAA should not report lower planning workload as proof that staffing needs have disappeared.

Automation sometimes removes repetitive tasks while creating new monitoring duties. Operators must review recommendations, investigate anomalies, and recover when integrations fail.

New tools can also increase demand temporarily. Controllers and traffic managers may need parallel procedures while the FAA validates the platform and preserves existing safety protections.

The system should therefore be measured against operational workload, not merely processing speed. A model that produces more options can create work if people must evaluate each one manually.

Staff acceptance will matter as much as technical accuracy. Controllers are unlikely to trust a platform that changes established flows without a clear operational explanation.

Their feedback should shape interface design, alert thresholds, and fallback procedures. It should also identify recommendations that look efficient in data but fail under real conditions.

The FAA AI air traffic control effort works best as one component of a broader capacity strategy. That strategy still requires hiring, certification, retention, facilities, communications, and surveillance equipment.

Software can help controllers manage complexity. It cannot make the workforce question disappear.

The $875M Bet Is Part of a Much Larger Rebuild

SMART is not a standalone cure for air traffic control; it is one software layer inside a costly and compressed modernization program.

The FAA awarded ASI a 12-year contract covering SMART and FMDS. The program joins a broader attempt to replace aging communications, surveillance, weather, training, and automation systems.

Peraton serves as the prime integrator for the wider modernization effort. That role includes coordinating contractors and installations across thousands of FAA locations.

Congress provided an initial $12.5 billion for the program. The Transportation Department has said the complete modernization will require substantially more funding beyond that first appropriation.

The plan divides the work into phases. Early projects emphasize communications, radar, weather systems, information displays, surface awareness, and training technology.

Later automation work includes FMDS and a common platform for systems used to display and track aircraft. Those components are more closely connected to traffic optimization.

The administration has targeted the end of 2028 for major first-phase work. That schedule is far faster than traditional federal aviation modernization programs.

Speed responds to a real problem. Some FAA infrastructure remains dependent on old equipment, limited replacement parts, and communications links installed decades ago.

However, compressed delivery creates its own risks. Critical systems must remain available while contractors replace equipment and connect new platforms.

The latest modernization assessment raises significant questions about planning. GAO found no comprehensive lifecycle cost estimate and no integrated master schedule for the first phase.

As of May 2026, the broader program consisted of more than 11,000 individual project schedules. Those schedules had not been fully integrated or optimized.

That finding matters for SMART because software depends on infrastructure and data supplied by other projects. Delays elsewhere can limit the quality or reach of predictive capabilities.

GAO also reported that the FAA estimated first-phase system modernization at $10.615 billion. Available program appropriations left a projected gap that required annual funding and other sources.

A second phase was expected to require an additional $10.2 billion as of May 2026. The FAA had not established a complete implementation timeline because that phase lacked full funding.

SMART therefore enters an environment with overlapping contracts, unfinished infrastructure, and uncertain long-term appropriations. Its own contract value does not capture those dependencies.

Historical experience encourages caution. The FAA’s NextGen modernization produced meaningful capabilities, but projects also encountered delays, changing requirements, and complicated integration work.

The new strategy emphasizes commercially developed software instead of building every capability internally. ASI already provides routing and operational tools to major airlines.

Commercial experience gives the company relevant data and deployment knowledge. It does not automatically establish that the same product will meet federal safety, scale, security, and transparency requirements.

The National Airspace System also contains users beyond large airlines. Cargo operators, business aviation, general aviation, military users, drones, and future air taxis compete for access.

A national platform must account for those different operating models. It cannot optimize only for carriers with the deepest data integrations.

The FAA’s system plan pairs software with new radar, telecommunications, voice switches, and facilities. That combined approach is necessary because prediction cannot repair a failed communications link.

The larger rebuild is thus both SMART’s opportunity and its greatest dependency. Modern infrastructure can provide better data, while troubled integrations can weaken even an accurate model.

Safety Depends on Data, Explanations, and Fallbacks

The hardest question is not whether SMART can produce forecasts, but whether the FAA can safely rely on them during unusual conditions.

Machine learning performs best when current conditions resemble patterns represented in its data. Aviation disruptions often involve combinations that rarely occur in exactly the same form.

A fast-moving storm may coincide with a runway closure, communications failure, staffing restriction, or military airspace change. Historical averages offer limited guidance in such moments.

SMART must recognize when its predictions become less reliable. Operators also need an obvious way to reject recommendations and return to established procedures.

That requirement separates safety-critical decision support from ordinary business analytics. An incorrect office forecast wastes time, while an aviation recommendation can reshape traffic across several regions.

The platform’s data creates another risk. Airline schedules can change, weather forecasts can diverge, and airport capacity estimates can become obsolete within minutes.

A centralized visualization helps only when each input has a clear timestamp and provenance. Users must know whether a recommendation reflects current conditions or an outdated feed.

Cybersecurity is equally important. FMDS will exchange live operational data among the FAA and airspace users, making availability and integrity essential.

An attacker would not need to seize direct control of aircraft to cause disruption. Corrupted capacity estimates or false route constraints could still damage confidence and efficiency.

The FAA must test degraded modes, not just normal performance. Those tests should include unavailable data feeds, delayed updates, conflicting inputs, model failures, and communications outages.

Human factors require the same attention. Too many low-value alerts can produce alert fatigue, while unexplained recommendations can encourage either distrust or overreliance.

Automation bias occurs when people give excessive weight to a computerized recommendation. A good interface should support judgment rather than reward passive acceptance.

That means showing the constraints behind each proposal. A traffic manager should see whether weather, runway capacity, sector demand, or another factor drove the recommendation.

The system should also preserve accountability. Logs must record which data supported a proposal, what a human decided, and how the operational outcome differed from the prediction.

Those records will help investigators, auditors, and engineers distinguish model errors from data failures or reasonable decisions made under uncertainty.

Public claims should remain narrower than the evidence. The FAA says SMART will reduce delays, improve traffic flow, and increase capacity, but live results have not established those outcomes nationally.

A regional rollout can provide early evidence. It cannot prove that the platform will perform equally well across every facility, weather pattern, and traffic mix.

Safety should not be measured only by the absence of an accident. Relevant indicators include rejected recommendations, unstable plans, workload changes, loss-of-service events, and procedural deviations.

Delay reduction also needs careful attribution. Weather, demand, airline operations, staffing, and equipment conditions can change independently of SMART.

The FAA should compare similar operating periods and publish the methodology behind reported benefits. Otherwise, favorable conditions could be mistaken for software performance.

Transparency does not require releasing sensitive operational data or proprietary code. It does require clear metrics, evaluation boundaries, and honest reporting about failures.

Without those elements, the FAA AI air traffic control program risks becoming a public relations label attached to ordinary modernization. With them, it can become a meaningful test of accountable operational AI.

Three Signals Will Show Whether SMART Is Working

The next evidence should come from operations: controller use, measurable traffic improvements, and reliable expansion beyond Washington.

The first signal is whether traffic managers use SMART recommendations during real disruptions. Adoption rates alone will not be enough, because operators might accept only trivial suggestions.

The FAA should examine how recommendations affect severe-weather planning, departure sequencing, reroutes, and recovery after constraints clear. It should also track why operators reject proposals.

Consistent use during complex operations would strengthen the case for SMART. Frequent overrides caused by missing constraints or unstable outputs would weaken it.

The second signal is a measurable change in delay and workload. That evaluation should compare similar traffic levels, weather conditions, and staffing situations.

Useful metrics include planning lead time, ground-delay duration, reroute frequency, sector overload events, and workload reported by controllers and traffic managers.

System-wide efficiency also matters. Moving a delay from one airport to another does not represent a genuine improvement.

Neither does prioritizing one group of operators while imposing hidden costs on another. The FAA needs measurements that capture network effects, not a single airport’s result.

The third signal is the pace and quality of expansion. A successful Washington deployment should produce a documented operational baseline before the software enters additional regions.

Expansion will test whether the platform can adapt to different airspace designs, weather patterns, traffic mixes, and local procedures. It will also test training and technical support.

A rapid national schedule might look impressive while concealing unresolved defects. Staged deployment offers more value when each stage has explicit acceptance criteria.

Congress and oversight bodies should also watch the relationship between SMART and the broader modernization schedule. Software milestones mean little if critical infrastructure cannot supply dependable data.

Likewise, new radar or communications equipment will not guarantee better traffic management. The value appears only when systems exchange information reliably and people can act on it.

ASI’s role deserves continuing scrutiny because the company will influence a central operational platform for years. Contract oversight should examine performance, security, portability, and dependence on proprietary technology.

The FAA should retain the ability to audit results and move data between vendors. Long contracts can become expensive constraints when interfaces or performance measures remain vague.

Airlines have reasons to support earlier and more predictable planning. Better forecasts can improve aircraft utilization, crew planning, fuel decisions, gates, and passenger connections.

Controllers have a different but complementary interest. They need fewer avoidable conflicts without losing authority, situational awareness, or reliable fallback tools.

Passengers will experience the program indirectly. They will not see a model running at the Command Center, but they may notice fewer cascading delays and last-minute changes.

Those benefits are not guaranteed. The initial deployment must prove that predictions translate into operational decisions under the conditions that make aviation difficult.

The FAA’s bet is ultimately narrower than the headline suggests. It is not handing American airspace to an autonomous AI system.

It is testing whether better forecasts can give skilled people more time to manage scarce capacity. That goal is credible, measurable, and still demanding.

The next few months should establish whether SMART earns controller trust in Washington. They should also reveal whether recommendations remain useful during weather, congestion, and system failures.

If those results are published with meaningful comparisons, the FAA AI air traffic control initiative can offer a model for responsible public-sector AI. If evidence stays vague, the contract will remain a costly promise.

The question for travelers, controllers, and policymakers is therefore concrete: will the FAA publish enough operational evidence to show that prediction improved decisions, rather than merely adding software?