We Checked 330 Race-Travel Routings

The 38 failed routings by cause. Wrong-airport and dead-route errors accounted for nearly two-thirds.

Route maps rot faster than race calendars do.

That is the finding. When 330 individual flight routings for destination races were checked against live schedule data, 38 of them described flights that no longer operate, operate from a different airport, or never existed in the form they were being recommended. Roughly one in eight.

The number itself is less useful than the shape of it. These were not random errors scattered across obscure regional carriers. They fell into four repeatable categories, and once you know the categories you can check your own plan in about ten minutes.

One: the right city, the wrong airport

London is the clearest case. British Airways runs an enormous long-haul operation from Heathrow and a largely separate leisure network from Gatwick. Lanzarote, Gran Canaria, Antalya, Cagliari, Kalamata, Sharm El Sheikh and Porto are Gatwick routes. An athlete who books a transatlantic flight into Heathrow expecting to connect onward to a Mediterranean or Canaries race finds no connection at all — the onward flight leaves from an airport an hour away, on the far side of London, with a bike box.

The same trap exists in miniature all over the world. Milan has three airports. Rome has two. Paris has two that matter, and they are not airside-connected.

Two: dead routes that still get recommended

American Airlines ended Philadelphia–Frankfurt in 2018, Philadelphia–Munich in 2019, Philadelphia–Manchester in 2023, and Philadelphia–Brussels back in 2016. All four still turn up in race reports, forum threads and travel guides written when they were live. Route recommendations have a long half-life on the internet and no expiry date stamped on them.

This is the failure mode that catches experienced travellers hardest, because it usually comes from a source that was genuinely reliable — a friend's race report, a well-regarded blog — that simply describes a world that no longer exists.

Three: the airport moved

Goa is the sharpest example. Qatar Airways shifted its Goa service from Dabolim (GOI) to the new Manohar airport at Mopa (GOX) in June 2024. The codes are different, the airports are 35 kilometres apart, and a plan built around the old code lands in the wrong place. Balmaceda in Chilean Patagonia is BBA, not BAL — a wrong code that silently returns no flights, so the traveller concludes there is no service when there is.

Four: the domestic leg leaves from somewhere else

This is the one most likely to break an actual race trip. In Taiwan, the domestic flights to Taitung and Penghu depart from Songshan, the close-in city airport, not from Taoyuan, where the international flights land. The two are 40 to 50 kilometres apart. An itinerary that shows a tidy connection is in fact an international arrival, a cross-city ground transfer with a bike box, and a separate check-in — and the connection time shown on the booking is meaningless.

Why this happens

Airline networks change on a commercial cycle that has nothing to do with when races are scheduled. Routes get cut in the northern winter and restored in summer. Carriers move between airports. Public-service-obligation contracts on island and regional routes get retendered and change operator entirely — Sardinia's Rome connections shifted from ITA Airways to Aeroitalia in March 2026, mid-planning-cycle for anyone booking a summer race there.

Meanwhile the information athletes actually plan from — race reports, forum threads, destination guides, an old spreadsheet from the last time someone in the group did this race — is written once and rarely revised. The gap between the two compounds every year.

The ten-minute check

The audit's practical lesson is that verification is cheap and specific. For any race-travel plan, confirm four things against a live schedule source rather than a secondary one.

Confirm the airport code, not the city name, and check whether the city has more than one field. Confirm the operating carrier flies the leg you think it does, on its own metal rather than as a codeshare. Confirm the route is running in your race month, because seasonal suspension is the single most common reason a real route is unavailable on a real date. And confirm the domestic connection departs from the airport you land at.

None of that requires a travel agent. It requires treating the routing as a claim to be checked rather than a fact to be inherited.

Key takeaways

Route information decays. An audit of 330 race-travel routings found roughly one in eight described flights that no longer operate as described.
The errors are patterned, not random: wrong airport for the city, dead hub routes still circulating, seasonal suspension, and moved or renamed airports.
The most dangerous failure is a domestic leg departing from a different airport than you arrive at — it looks like a valid connection until you are in the wrong terminal.
Verify four things against a live schedule source: airport code, operating carrier, service in your race month, and whether the onward leg departs where you land.
Race reports, forum threads and guides are written once and almost never revised. Treat them as leads, not itineraries.

Sources

The 38-of-330 figure is an internal audit conducted in August 2026 against live schedule data at a single point in time. It describes the error rate of drafted routings, and is offered as evidence of a pattern rather than as an industry-wide statistic.

Part one of a three-part series on race travel. Next: Your Home Airport Decides Your Race Calendar More Than Your Fitness Does.