From the Transportation edition of November 1, 2026
DOT AI program easing flight traffic, control tower headaches — but still Dems oppose
U.S. Department of Transportation / Federal Aviation Administration · Federal aviation agency serving public airports · Washington, D.C. region (DCA, IAD, BWI), United States
- Publisher
- New York Post
- Original publication
- 2026-10-30
- Source retrieved
- 2026-11-02
What happened
The FAA's SMART tool (Strategic Management of Airspace, Routes and Trajectories), developed with Air Space Intelligence and deployed at three Washington-area airports in September, has helped reroute 110 flights in its initial stage, averaging more than 10 minutes and 56 gallons of fuel saved per flight and affecting 14,644 passengers, according to DOT. It combines about 200 data streams. DOT says aviation specialists monitor the tool and relay information to controllers, who make the decisions. DOT plans nationwide expansion; Reps. Ocasio-Cortez and Beyer have called for a pause, citing testing and training concerns and arguing it is no substitute for rebuilding the controller workforce.
Why it matters
Federal, not SLED, but it directly affects operations at publicly owned airports (Reagan National and Dulles under the Metropolitan Washington Airports Authority; BWI under the Maryland Aviation Administration). Airport authorities should understand how upstream AI planning changes departure timing and gate demand.
Evidence and measured results
DOT/FAA-reported initial results relayed by the reporter: 110 rerouted flights, more than 10 minutes and 56 gallons saved per flight on average, 14,644 passengers, some flights up to 30 minutes. No baseline method, counterfactual or independent evaluation is described. The article is openly favorable to DOT, quotes an unnamed source, and summarizes the critics' letter. The FAA's SMART one-pager (opened as corroboration) describes SMART as a cloud-based platform using AI and says initial operations begin in fall 2026.
Limitations and uncertainty
Results are early, self-reported by DOT, and relayed by a partisan-leaning article; savings methods are not explained. 110 flights is a small sample. The 'source told The Post' commentary is unattributed. Federal ATC is outside SLED operations.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Airport authorities may see departure timing and gate demand change because of an FAA AI planning tool they do not control.
- Stakeholders
- Airport operations directors
- Airline station managers
- Airport IT and data teams
- State aviation administration (for BWI)
- Discovery questions
- Does the airport receive SMART-informed departure changes, and when?
- What baseline on-time and gate-use data does the airport hold for comparison?
- Who at the airport coordinates with FAA traffic management?
- Value hypothesis
- Earlier awareness of planned departure changes could help airports schedule gates and staff; benefit size is unknown.
- Potential engagement
- An operations-impact assessment of FAA SMART for an airport in the deployment area, with baselines and a data-sharing request.
- Unsupported claims
- The 10-minute and 56-gallon savings as verified
- Any national-scale savings
- That controllers' workload is reduced
Pre-sales engineering
Role takeaway
- Fit
- Fits as context for airport operations data integration; the AI system itself is federal.
- Architecture and integration
- Receive FAA and airline planning updates into airport operational databases and gate management systems.
- Prerequisites
- Access to FAA or airline planning data feeds
- Historical on-time and gate data
- Airport operational database integration
- Constraints
- Federal ownership; airports cannot change SMART
- Deployment limited to three airports initially
- Cloud platform details not public
- Security
- Airports should treat any received planning feed as operationally critical and monitor its integrity and availability.
- Proof of value
- Compare scheduled versus actual departure times before and after SMART at the airport
- Track gate conflicts on days with SMART reroutes
- Check how early reroute information reaches airport operations
Delivery
Role takeaway
- Work
- Track SMART's effects on airport operations and coordinate data access with FAA and airlines.
- Dependencies
- FAA willingness to share data
- Airline cooperation
- Airport data quality
- Ownership
- Airport operations department, with IT supporting data integration.
- Skills and adoption
- Operations staff need to interpret planning changes; analysts need baseline methods.
- Governance checkpoints
- Establish baselines before nationwide rollout reaches the airport
- Review results with airlines quarterly
- Escalate data-sharing gaps to FAA
- Acceptance criteria
- Proposed: baseline on-time and gate data compiled for 12 months before SMART
- Proposed: quarterly comparison report
- Proposed: named FAA coordination contact
- Risks
- Federal pause or policy change
- Attribution difficulty amid weather and other factors
- Limited data access
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
A cloud-based decision-support layer over existing FAA traffic management systems, fusing schedules, weather, capacity and airspace data. Human specialists sit between the tool and controllers, so the integration is advisory, not automated control.
Governance
Who approves, reviews and stays accountable for outcomes?
Contested expansion: DOT plans national rollout while lawmakers ask for a pause over testing and training. The human-in-the-loop design (specialists relay, controllers decide) is DOT's main governance argument. Independent evaluation before national expansion is not described.
Security and privacy
What data, permissions and controls need testing?
Cloud hosting of an air traffic planning tool raises availability and integrity questions the article does not address. No passenger personal data is described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Workforce is the critics' core concern: controller shortages and training. DOT reports more than 2,200 trainee controllers hired. Effects on airport staff are not discussed.
Procurement
What should contracts, pricing and exit terms secure?
Federal development with Air Space Intelligence; no airport procurement implied.
Operating model
Which teams own the service once it runs?
Introduces a specialist intermediary role between AI outputs and controllers; airports should expect upstream planning changes earlier in the day.
Publication history
- 2026-11-01Transportation · Issue 047 resources
Stable resource ID: faa-smart-ai-airspace-planning-initial-results