Autonomous Shuttle Pilots in University Towns and Airports

Long before most people had ridden in anything resembling a robotaxi, a much smaller and slower category of autonomous vehicle was already circling university campuses and airport parking lots. EasyMile and Navya, among others, began deploying fixed-route autonomous shuttles at business parks, campuses, and airports starting in the mid-2010s, years ahead of the robotaxi services that would later get most of the attention.

Some of the earliest and most visible pilots became well known for reasons that had little to do with the technology working as intended. A Navya shuttle running a pilot route in downtown Las Vegas made national news within hours of its debut in 2017, not because it malfunctioned but because a human-driven delivery truck backed into it while the shuttle sat correctly stopped. The story that spread wasn't really about autonomous vehicles at all; it was a small, telling illustration of how much of the risk in a mixed-traffic pilot comes from everything else on the road rather than from the shuttle itself. Business-park pilots like the ones EasyMile ran drew far less attention precisely because nothing comparable happened there, which is itself a kind of evidence for how much a slow, well-controlled route reduces the odds of an incident worth reporting on at all.

These shuttles operate in a different world from urban robotaxi service, and the difference is worth being specific about rather than just noting it exists. They typically run under 25 kilometers per hour, on short routes that have been mapped in detail in advance, often the same loop repeated for years. There's no unpredictable turn onto a street the vehicle has never seen, no need to interpret a construction detour or a jaywalking pedestrian on an unfamiliar block. A fixed loop between a parking structure and a terminal building doesn't need to solve the same open-ended perception problem an urban robotaxi does. It's a narrower problem, deliberately so.

Part of why these shuttles could deploy years before urban robotaxis did comes down to how they're classified. Many of them, including Navya's platform, were built from the ground up without a steering wheel or pedals rather than retrofitted into an existing car design, which routes them through a different set of federal vehicle-safety requirements than a converted passenger sedan faces. Operating at low speed on a private or semi-private route also keeps a pilot within a regulatory category that a full-speed public-road deployment could never fit into, regardless of how capable the underlying software was. The shuttles' early arrival wasn't purely a technology story; it was also a story about which vehicles happened to fit through the narrowest available regulatory gap first.

That narrowness is exactly why so many of these pilots have lasted as long as they have without ever becoming something bigger. A shuttle that has run the same loop at a business park for years looks, from a distance, like a quiet success story. In a real sense it is one. But running well on a fixed low-speed loop for years doesn't automatically translate into the ability to handle open urban roads, and plenty of pilots that started with real ambitions to expand never made that jump. The gap between local success and broader expansion shows up across the mobility industry generally, but the shuttle pilots are an unusually clean example of it, precisely because so many of them have run largely unchanged for so long.

The fixed-route model didn't disappear, though. May Mobility's approach to fixed-route service picks up a version of the same idea, applied with a different set of assumptions about what counts as a viable route.