Many airport codes feel intuitive.
- LAX looks close enough to Los Angeles.
- SIN clearly points to Singapore.
- MAD is easy to connect to Madrid.
Then you run into ORD, EWR, MCO, or MSY and the logic seems to disappear.
It has not disappeared. It is just historical.
The Main Reason: Codes Rarely Change Once Assigned
Airport codes are deeply embedded in:
- booking systems
- airline schedules
- baggage routing
- ticketing databases
- travel agency tools
Once a code becomes standard across the industry, changing it is expensive and risky. So even when an airport gets renamed, rebuilt, or rebranded, the old code often stays.
That is why strange codes survive for decades.
The Four Most Common Reasons a Code Looks Strange
1. The Airport Used To Have a Different Name
This is the classic reason.
ORD = Chicago O’Hare
Before it became O’Hare, the airport was known as Orchard Field. The code ORD stayed even after the name changed.
MCO = Orlando International Airport
MCO comes from McCoy Air Force Base, the military site that used to occupy the airport area.
MSY = New Orleans
MSY traces back to Moisant Stock Yards, tied to the older field and land use around the airport.
If you only look at the modern airport name, these codes feel random. If you look at the airport’s earlier life, they make much more sense.
2. The Obvious Code Was Already Taken
There are only so many sensible 3-letter combinations.
If the cleanest match is already assigned elsewhere, IATA has to find another option.
This is one reason airport codes sometimes use:
- consonants from the city name
- nearby place names
- older spellings
- the airport name instead of the city name
In multi-airport markets, the clean city logic breaks down even faster because a metro area needs multiple distinct airport codes.
3. The Code Reflects the Airport, Not the City
This often happens in cities with more than one major airport.
For example, New York does not have one airport code. It has several:
- JFK
- LGA
- EWR
If you search the metro-area code NYC, you are grouping multiple airports together. But each physical airport still needs its own unique IATA code.
That is why our guide to airport code vs city code matters so much in real booking work.
4. The Code Reflects an Older Geography or Naming Convention
Some codes reflect a neighborhood, airfield, or legacy naming pattern that modern travelers no longer use day to day.
EWR = Newark
At first glance, EWR looks strange. But once the natural three-letter city options are constrained, airports often end up with a code built from available letters rather than a perfect city match.
CDG = Paris Charles de Gaulle
This one does not match the city because it is based on the airport name itself, not “Paris.”
NRT = Tokyo Narita
Narita serves Tokyo long-haul demand, but the code reflects the airport location, not the city code TYO.
Why This Confuses Travelers
Odd airport codes create three common problems:
1. People Assume the Code Must Belong to a Different City
That is how travelers miss airports like EWR when planning a New York trip or ignore NRT when planning Tokyo.
2. People Search the Wrong Airport by Habit
If the code does not look obvious, travelers are more likely to search the city name loosely and trust whatever booking tools return first.
That is risky in cities with multiple airports because the “wrong” airport can change transfer time, total trip cost, and even whether a trip is practical.
3. People Misread the Real History of the Airport
An unusual code often tells you the airport is older, has military roots, or evolved from an earlier field. It is a clue about history, not a mistake.
A Better Way to Read Strange Codes
When an airport code looks odd, ask:
- Did the airport used to have another name?
- Is this one of several airports in the same metro area?
- Is the code tied to the airport name instead of the city name?
- Was the obvious 3-letter version already taken?
That framework solves most mysteries quickly.
Why This Matters for Booking
The code itself is not just trivia. It affects how you search and compare.
If you do not understand why codes differ, you are more likely to:
- miss alternative airports
- confuse airport and city codes
- compare the wrong arrivals
- book an airport that makes the rest of the trip harder
That is why a code guide is often the first step before you decide between airports in the same city or try to avoid booking the wrong airport.
Bottom Line
Airport codes do not always match the city name because aviation systems are built on continuity, not perfect modern branding.
Most strange codes come from one of four things:
- an older airport name
- a military or legacy airfield
- a city with multiple airports
- the fact that the obvious code was already taken
Once you know that, codes like ORD, MCO, and EWR stop looking random and start looking like useful historical clues.