One Ticket, Every Continent: How a Pricing Glitch Gave One Man the Flight Plan of a Lifetime

Airlines price their tickets using systems so complex that the people who built them don't fully understand them anymore. That's not an exaggeration — it's a structural reality of the industry. Fare codes, booking classes, alliance agreements, fuel surcharge calculations, and interline ticketing rules layer on top of each other in ways that occasionally produce outcomes nobody planned for. Usually those outcomes are boring. Occasionally, they are spectacular.

This is one of the spectacular ones.

The Man Who Read the Fine Print

In 2004, a frequent flyer named Corey Christensen — a project manager from Seattle with a serious travel habit and a deeper-than-average understanding of how airline ticketing actually worked — was browsing fare databases looking for a business-class deal from the U.S. to Australia. This was the kind of thing Christensen did for fun. He understood that airline pricing systems had quirks, and he'd learned over years of searching that the quirks occasionally produced fares that were technically valid but wildly mispriced.

What he found that afternoon was something he'd never seen before.

A particular fare code — a business-class round-trip originating in the United States — had been filed with a major international airline alliance in a way that, due to an error in how the routing rules were entered, permitted an almost unlimited number of stopovers across the alliance's partner network. Normally, business-class round-trip tickets permit one or two stopovers. This one, as filed, permitted open-jaw routing with stopovers in any city served by any alliance partner, with no clear limit on the number of segments, as long as the itinerary ultimately returned to the point of origin.

In plain English: if the fare was valid, it could theoretically cover a round-the-world itinerary in business class for a fraction of what that journey would normally cost.

The Ticket That Shouldn't Have Worked

Christensen spent two days mapping out an itinerary. Seattle to New York. New York to London. London to Dubai. Dubai to Bangkok. Bangkok to Sydney. Sydney to Auckland. Auckland to Los Angeles. Los Angeles back to Seattle. Fourteen segments across six countries on four continents, all routed through alliance partners, all technically permitted under the fare rules as filed.

He called the airline's reservations line and booked it.

The agent who took his call paused at several points during the booking process. She put him on hold twice. When she came back the second time, she told him the fare had been validated by the system and she was issuing the ticket. The total price: $1,918 in business class for an itinerary that, priced normally, would have cost somewhere between $18,000 and $22,000.

He paid. The ticket was issued. He had a confirmation number.

What Happened Next Is Where It Gets Interesting

Christensen, unlike some people who find airline pricing errors, did not immediately post about it online. He knew from experience that widespread publicity about fare glitches tends to result in the airline canceling the tickets and issuing refunds, citing "pricing error" clauses in their terms of service. He kept quiet, packed his bags, and showed up at Seattle-Tacoma International Airport on his departure date.

He boarded without incident.

Every subsequent leg of the journey — London, Dubai, Bangkok, Sydney, Auckland — checked in without a problem. Gate agents scanned his ticket. It cleared. He sat in business class. He ate the warm nuts. He slept on the flat bed. He landed in cities on four continents on a ticket that cost less than a round-trip coach fare to Europe.

When he returned to Seattle, he wrote a detailed account of the experience and posted it to a frequent flyer forum. The post went viral within the travel community. Within 48 hours, the fare code had been pulled from the system.

The Airline's Response

The airline — which Christensen declined to name publicly, and which forum members speculated about extensively without reaching consensus — issued a statement acknowledging that a fare had been "incorrectly filed" due to a "data entry error in the routing rule parameters." The statement noted that the airline had honored all tickets issued under the fare code and would not be seeking refunds or compensation from passengers who had booked it.

That last part is important. The airline could have fought it. Airlines frequently invoke pricing error clauses to cancel mistakenly issued tickets, and courts have generally sided with them when the error is obvious enough. But this airline chose not to. Whether that decision was driven by customer relations considerations, legal uncertainty, or simple embarrassment about the error is unclear. Possibly all three.

Christensen, for his part, said in a follow-up post that he felt the airline had done the right thing. "I found a valid fare in their system," he wrote. "I booked it through their official channels. Their agent confirmed it. Their system issued a ticket. At some point, that's a contract."

The Glitch That Keeps Giving

Airline pricing errors are more common than the industry likes to admit. In 2015, British Airways accidentally priced business-class tickets from the U.S. to India at around $400 — and honored thousands of them after a public outcry. In 2012, United Airlines briefly sold first-class tickets for $0 plus taxes due to a system error; they canceled those tickets, which resulted in a class-action lawsuit that was eventually settled.

The rules around pricing errors vary by country and by airline policy. In the U.S., the Department of Transportation has gone back and forth on whether airlines are required to honor mistakenly priced tickets. The current guidance generally allows airlines to cancel obvious errors — but "obvious" is doing a lot of work in that sentence.

Christensen's ticket wasn't obviously wrong. It was a valid fare code, correctly entered into the booking system, confirmed by a human agent. The error was upstream, buried in the routing rules where almost nobody would think to look.

He looked. He booked. He flew.

And somewhere in an airline's IT department, someone had a very long week.