Airports & Hubs
Hub-and-Spoke vs Point-to-Point: Why America's Flights Are Built the Way They Are
It's a frustration most frequent US travelers will recognize. You're looking for a flight from your city to a destination that seems like it should…
Home › Airports & Hubs › Why Airport Codes Like ORD, MCO and YYZ Don't Match the City
Airports & HubsWhy Airport Codes Like ORD, MCO and YYZ Don't Match the City Name
Airport codes can seem like an arbitrary jumble of letters, especially when you're in a rush to book a flight. But the three-letter codes managed by the International Air Transport Association (IATA) and the four-letter ones governed by the International Civil Aviation Organization (ICAO) each follow clear systems. The famous "weird" codes - like ORD for Chicago, MCO for Orlando, and YYZ for Toronto Pearson - have their own fascinating origin stories that reveal a great deal about aviation history.
What this piece covers
The ICAO four-letter codes are more systematic than the IATA three-letter codes. ICAO codes break down by world region, country, and airport within that country. The U.S. codes are K followed by the airport identifier. C codes are Canada, F codes are France, and so on. Europe has two groups. U.S. codes use one identifier for airports and another for weather. Canada uses one. At least four-countries have Y** for airports that use it as a weather reporting indicator (yes,no).[1]11
ICAO codes can often be a useful check for international travellers. They're used on international air navigation charts. The ICAO airport code is what you would be routed on by Air Traffic Control- and what you would get from a flight information centre. The ICAO code is what pilots would (usually) be using in their planning and flight logs (and you would (usually) be able to look up on the nav maps or planning software).[8] You would know why your international plane got to its gate but your flight to Chicago ORD might be delayed on the tarmac of Los Angeles LAX.** 27
Two Code Systems, Two Purposes
Airport codes are not purely random; in fact, they reflect two distinct systems to accommodate different needs and stakeholders. The IATA three-letter codes are the ones you see in search results, ticket bookings, and airports, covering many thousands of locations worldwide. IATA governs these codes to ensure they are unique and assigned to airports or other locations that receive scheduled air services or must be identified in intermodal transportation, as per its Resolution 763.[1][3][6]
Then there are the ICAO four-letter codes, used primarily for air traffic control, flight operations, and technical documentation. Coordinated by ICAO - the United Nations aviation agency - these codes aim to systematically cover all aerodromes globally, including many smaller fields that may not have commercial IATA codes. ICAO's approach is to structure the codes by region, country, and the specific airport - the first letter often denotes the region, the second letter the country, and the last two letters the airport. That's why you'll see U.S. codes like KJFK (John F. Kennedy International Airport, New York), Canadian codes like CYYZ (Toronto Pearson International Airport), and so on.1114
How IATA Assigns Airport Codes Today
The IATA three-letter codes might seem straightforward, but the process behind their assignment is actually quite nuanced. The total possible IATA three-letter combinations is 17,576 (26³)[5]. When an airport or airline applies for a new code, IATA's first choice is to use an unassigned combination of the first three letters of the location's name, and the second choice is an unassigned combination that preferably starts with the first letter of the location's name. Applicants can suggest preferred codes from the available list, but IATA makes the final decision based on the Resolution 763's rule of uniqueness. This is one of the reasons you see so many codes that resemble the airport or city name, like ATL for Atlanta, BOS for Boston, DEN for Denver, or MIA for Miami.15 [3][4]10
But with only 17,576 possible combinations, there are inevitably constraints. When the obvious city-name abbreviations are already taken, airports may receive codes based on alternative spellings, historical names, or the airport's own name rather than the city. And this is where the "weird" codes come from. Today, you can decode many of the "odd" codes from knowing historical airport names or origins, such as historical airfield names, O'Hare (Chicago, ORD, Orchard Field)1213, and Orlando's MCO (McCoy Air Force Base)13. - and some airport naming decisions don't necessarily make the most sense to outsiders.
The Logic Behind Everyday Codes
Most of the time, IATA codes make intuitive sense. Take the codes for Atlanta (ATL), Boston (BOS), Denver (DEN), and Miami (MIA) - these directly use the first three letters of the city names. But there are also codes like Orlando (MCO), Chicago (ORD), and Toronto (YYZ) that seem to have no connection to the city names. If you misspell a code, your booking can go awry, so it pays to check carefully.
These "weird" codes usually relate the history of the location. For example, Chicago O'Hare International Airport was originally known as Orchard Field, and this name has been retained in its ORD code, and O'Hare was a naval aviator honored for his wartime service.1213 Similarly, Orlando International Airport's code, MCO, originates from McCoy Air Force Base, the military facility on whose site the airport now operates.13 And Toronto Pearson International Airport's code, YYZ, doesn't include letters from the city or airport name at all - instead, it comes from a nearby railway station code used by telegraph operators, with the leading "Y" indicating the presence of a weather station under a Canadian convention.[8]
ORD and MCO: Military and Orchard Field Legacies
Two of the most confusing IATA codes - ORD for Chicago and MCO for Orlando - have specific histories that explain why they seem so improbable.
Chicago's O'Hare International Airport started life as Orchard Field, a small airport and farming area in the 1920s. After World War II, it was greatly expanded and renamed O'Hare International Airport in 1949 in honor of naval aviator Lieutenant Commander Edward "Butch" O'Hare. Despite the name change, the airport retained the ORD code that had been assigned to Orchard Field, and this is why Chicago's code seems to bear no relation to the city name today.1213
17
Similarly, Orlando International Airport began life as Orlando Army Air Field in 1939, and later became McCoy Air Force Base, a major military installation. In the 1960s, the base began transitioning to civilian use, and the McCoy name was eventually retired in favor of Orlando International Airport. Despite the name change, the MCO code that had been assigned to McCoy Air Force Base was preserved for the commercial airport, and this is why Orlando's code is not immediately intuitive to travelers.13
YYZ and Canada's "Y" Airports
One of the most perplexing IATA codes is YYZ, which serves Toronto Pearson International Airport - Canada's busiest airport by passenger traffic. The code might make you wonder if there's a secret meaning or some sort of joke, but the answer is actually rooted in Canada's aviation history and infrastructure.
Historically, in Canada, a leading "Y" in an airport identifier indicated "Yes" for the presence of a weather station at the airport. This convention contributed to the widespread use of Y-prefix codes such as YYZ, YUL (Montréal-Trudeau), and YHZ (Halifax International). The "YZ" portion of YYZ comes from a nearby railway station code originally used by telegraph operators.[7][8]
This system of prefixing airport codes with "Y" for weather stations isn't unique to Canada -. In Canada, however, the "Y"-prefix codes have persisted even as the original weather station logic has become more outdated. And while some Y-prefix codes, like YVR (Vancouver International), do manage to approximate their city names, many like YYZ seem to be a relic of a bygone protocol.[8][9]
Reading Codes to Avoid Mistakes
Armed with the rules and histories of airport codes, travelers can start to decode even the most bewildering of codes. The key is to start with the assumption that IATA codes try to reflect a location name, unless they're constrained by limitations or history. So if an airport's name starts with A-B-C-D, it's likely to get an intuitive code, while ones starting later in the alphabet might end up with a less-obvious code. And if you see a code that looks nothing like the city, it's likely to have a military, historical, or infrastructural origin - and many of these stories have been preserved in the code itself.
But why do these codes even matter? Industry guides and commentary suggest that booking mistakes and traveler confusion often arise because passengers assume that an IATA code will be a straightforward abbreviation of the city name, when in reality it may be tied to an airport's history or infrastructure.[4]13
By understanding the framework behind airport codes, travelers and airline employees can avoid misunderstandings, reduce booking errors, and treat odd codes as a portal into aviation's past. And the good news is, you're already well on your way to decoding the alphabet soup that is airport codes. Next time you see a code that makes you scratch your head, remember - there's a very good chance it's not random, but deeply meaningful to some aviation historian, military officer, or even telegraph operator. And with that knowledge, you're free to book your flights, pack your bags, and travel the world liberated from the confusion and unnecessary errors.4,26
Why we published this. A rule set that makes any airport code readable, including the odd ones.
