Ghost Flights and Legacy Code: Why Travel Tech is Broken

Episode summary: Behind the sleek interface of your favorite travel app lies a fractured world of 1960s mainframes, cryptic UN-standardized messaging protocols, and a mountain of technical debt that makes modern flight booking a digital ghost hunt. This episode explores the "Big Three" Global Distribution Systems—Amadeus, Sabre, and Travelport—uncovering how decades-old Transaction Processing Facilities still dictate the price and availability of every seat in the sky. From the rise of the New Distribution Capability (NDC) and the "Dual Track API Tax" to the hidden complexities of interlining agreements and the "Look-to-Book" caching traps that cause prices to vanish at checkout, we break down why building in travel tech remains one of the most difficult engineering challenges in the world today. Show Notes The travel industry presents a unique paradox: while consumers enjoy modern, high-speed mobile apps, the backend infrastructure powering those apps is often older than the internet itself. When a user searches for a flight, they aren't querying a single, centralized database. Instead, they are tapping into a "house of cards" built on 1960s-era protocols and mainframe technology. ### The Titans of GDS At the heart of global travel are the Global Distribution Systems (GDS), dominated by three major players: Amadeus, Sabre, and Travelport. These systems were the original pioneers of e-commerce, with Sabre evolving from a partnership between IBM and American Airlines in the mid-20th century. They utilize Transaction Processing Facility (TPF) technology, designed for extreme speed and high volume long before the advent of modern cloud computing. The native language of these systems is EDIFACT, a cryptic, non-human-readable messaging standard developed by the United Nations. Because it was designed when bandwidth was prohibitively expensive, EDIFACT is incredibly dense, using shorthand codes and delimiters to save every possible byte. For modern developers, working with this "alphabet soup" is like trying to fit a high-performance racing engine into a steam locomotive. ### The NDC Pivot and the API Tax To modernize this landscape, the International Air Transport Association (IATA) introduced the New Distribution Capability (NDC). This was intended to replace legacy EDIFACT messages with modern XML and JSON APIs, allowing airlines to sell "ancillaries" like extra legroom or Wi-Fi. However, rather than simplifying the stack, this has created a "Dual Track API Tax." Developers must now maintain two separate integration paths: one for legacy GDS content and one for the newer NDC connections. Because NDC is often a modern wrapper around old internal airline databases, it can be prone to synchronization errors, leading to the "disappearing ticket" phenomenon where a flight appears available but fails during the booking process. ### The Complexity of Interlining One reason the legacy GDS players remain indispensable is the complexity of interlining. This is the legal and technical framework that allows a traveler to book a single itinerary involving multiple, different airlines. This requires massive backend coordination for baggage transfers, liability, and rebooking during delays. While a direct NDC connection works well for a single airline, only the GDS can navigate the "Multilateral Interline Traffic Agreement" that connects the global aviation web. ### The Caching Trap Finally, the industry struggles with "Look-to-Book" ratios. Querying an airline's system in real-time for every search is computationally expensive. To save costs and increase speed, aggregators cache flight data. This results in "stale" data, where a user sees a price that was valid ten minutes ago but has since changed. This lag is a primary reason why new AI-driven travel agents often struggle with accuracy, as they are frequently making plans based on information that is no longer true the moment the user clicks "buy." Listen online: https://myweirdprompts.com/episode/travel-booking-legacy-tech