The industry has spent a decade focused on the hardware. The coordination layer that makes it all work is still missing.
Billions of dollars and a decade of engineering effort have gone into building aircraft that can carry passengers through city skies. Archer. Joby. Overair. The certifications are advancing. The timelines are compressing. The hardware story is real.
But there is a second story running parallel to the hardware race — quieter, less well-funded, and arguably more consequential for whether urban air mobility ever reaches commercial scale.
It’s the infrastructure story. And right now, it isn’t going nearly as well.
What the Aircraft Manufacturers Can’t Build
Each eVTOL manufacturer is, by necessity, solving the problems within their own boundary. Airframe certification. Propulsion efficiency. Battery density. Pilot training and type ratings. These are substantial engineering challenges, and the companies working on them deserve the attention they’re receiving.
What none of them can build — and what none of them are incentivized to build — is the shared coordination layer that manages interactions between their aircraft and every other aircraft operating in the same urban airspace.
The reason is structural. A coordination layer built by Archer serves Archer’s operational interests. It sees Archer’s traffic. It optimizes for Archer’s fleet. The moment Joby’s aircraft enters the same corridor, you have two siloed systems with no shared picture — which is precisely the condition that produces dangerous blind spots.
The infrastructure that urban air mobility requires is, by definition, neutral. It has to serve every operator, every aircraft type, every city simultaneously. No single OEM can build that. The economic model doesn’t support it, and the operational logic forbids it.
What Legacy ATC Was Actually Designed For
The natural assumption is that air traffic control — the system that already manages tens of thousands of daily commercial flights — can simply absorb urban air mobility operations as they come online.
This assumption is wrong, and it’s worth understanding exactly why.
Legacy ATC infrastructure was designed for high-altitude commercial aviation operating in well-defined corridors, at relatively low traffic density, with standardized aircraft types, managed by certified controllers working from radar displays with meaningful update intervals.
Urban air mobility is none of those things. It operates below 2,500 feet — in the most complex, obstacle-dense, weather-variable portion of the airspace. It involves dozens of operators with heterogeneous aircraft types. It requires coordination at densities that will eventually reach hundreds of operations per hour in a single city. And it demands real-time responsiveness that legacy radar systems were never built to provide.
You cannot solve a fundamentally different problem by scaling a system designed for a different context. The physics don’t change. The operational requirements don’t bend to accommodate legacy architecture.
The Controller Shortage Makes This Worse
Layered on top of the architectural mismatch is a staffing reality that receives far less attention than it deserves.
The FAA is currently short hundreds of certified air traffic controllers. Training pipelines are slow — controller certification takes years, not months. Attrition is accelerating as an aging workforce retires. The tools controllers are working with in many facilities are decades old.
Urban air mobility, at commercial scale, does not add a modest increment of coordination burden to the existing system. It introduces a categorically different type of airspace activity: high-frequency, highly dynamic, multi-operator, with rapid position changes and complex interaction geometries.
The only viable path through this isn’t hiring. It’s infrastructure — a digital coordination layer that handles the volume of routine coordination events automatically, surfaces the exceptions that require human judgment, and gives controllers the situational awareness they need to manage a fundamentally more complex airspace environment.
The Design Window Is the Urgent Point
None of this is a future problem. The decisions being made right now — about which infrastructure gets built, to what standard, managed by whom — will shape urban air mobility for decades.
Airspace operational standards have long half-lives. Corridor geometries get established and persist. Regulatory frameworks get written around the operational data that exists when they’re written. Interoperability requirements get locked to the systems that are already deployed.
The organizations that are operationally present during this design window — 2026 through 2030 — aren’t just capturing early revenue. They’re participating in the process that determines what the rules are for everyone who comes after them.
The aircraft problem is well on its way to being solved. The infrastructure problem requires the same level of serious, sustained investment. The window to make that investment, and to have it matter, is narrower than most people in this industry are treating it.
Urban air mobility will arrive on the backs of remarkable engineering achievements in aircraft design. Whether it scales safely — whether it actually works as a city transportation system — will be determined by what gets built in the coordination layer underneath those aircraft.
That’s the problem that needs solving. And it needs solving now.