If you have ever searched for flights to New York and seen both JFK and NYC, you have already run into one of the most confusing parts of travel planning: the difference between an airport code and a city code.
They look similar, they both appear in booking tools, and they are often used side by side. But they do very different jobs. Understanding the difference helps you search more efficiently, compare airports within the same metro area, and avoid paying extra just because you started with the wrong query.
What an Airport Code Means
An airport code is the three-letter IATA identifier assigned to a specific airport.
Examples:
- JFK = John F. Kennedy International Airport
- LHR = London Heathrow Airport
- HND = Tokyo Haneda Airport
When you search with an airport code, you are telling a booking tool that you want flights to or from that exact airport. This is the most precise way to search if you already know the airport you want.
Airport-code searches are useful when:
- You need to arrive close to a city center or a specific neighborhood
- You want a particular airline hub or terminal experience
- You already know the airport offers the best connection for your route
- Ground transportation after landing matters more than the airfare difference
If you are looking up a code first, our airport directory is the fastest place to confirm whether you should search for JFK, LGA, EWR, or another nearby option.
What a City Code Means
A city code is a metro-area code that groups multiple airports serving the same city or region.
Common examples:
- NYC = New York area airports
- LON = London area airports
- PAR = Paris area airports
- TYO = Tokyo area airports
When you search with a city code, the booking tool can return results for multiple airports at once. This is useful when your real question is not “Which flight goes to Heathrow?” but rather “What is the cheapest or most practical way to get to London?”
That distinction matters because secondary airports often change the total trip cost in ways that are not obvious from the airfare alone.
Why Travelers Get Confused
Most travel sites do not explain clearly whether you are seeing:
- A single airport result
- A city-wide group result
- A mix of both inside the same fare comparison
That confusion creates three common mistakes:
1. Searching Too Narrowly
If you search only LHR, you might miss cheaper fares into LGW, STN, or LTN. Those airports can serve the same trip purpose, even if the ground transfer is different.
2. Searching Too Broadly
If you search NYC, you might get a low fare into EWR even though your hotel, meeting, or onward train connection makes JFK or LGA more practical.
3. Comparing the Wrong Costs
A lower ticket price does not automatically mean a cheaper trip. A secondary airport can reduce the airfare while increasing:
- train or taxi costs
- connection time
- overnight hotel risk
- baggage transfer complexity
That is why city-code searches work best as a discovery step, and airport-code searches work best as a decision step.
When to Use a City Code First
Start with a city code when:
- You are flexible about which airport you use
- You are traveling for leisure and want the cheapest overall option
- You are comparing low-cost carriers with full-service airlines
- The city has multiple major airports with very different fare structures
For example, a search using LON may reveal that one airline is much cheaper into Gatwick while another looks strongest into Heathrow. That gives you a broader market view before you narrow the decision.
When to Use a Specific Airport Code First
Start with a specific airport code when:
- You need a nonstop route that only exists at one airport
- You have a tight arrival window
- You are booking around a cruise port, conference venue, or family pickup
- You want to avoid long bus or rail transfers after landing
This is especially important in cities where airport choice changes the practical experience more than the headline fare.
Real-World Examples
New York: NYC vs JFK vs LGA vs EWR
NYC helps you compare the whole metro area.
Use JFK if you want the largest long-haul international network.
Use LGA for many short domestic routes.
Use EWR if United or a New Jersey arrival is more convenient.
London: LON vs LHR vs LGW
LON is useful if your goal is “get me to London at the best total value.”
Use LHR if you want alliance connectivity and long-haul frequency.
Use LGW if you are comparing leisure routes and price-sensitive options.
Use STN or LTN only after checking the full ground-transfer tradeoff.
Tokyo: TYO vs HND vs NRT
TYO lets you compare both Tokyo airports quickly.
Use HND for convenience and shorter city transfers.
Use NRT when long-haul schedules or fares make the outer-airport tradeoff worthwhile.
The Best Workflow for Smarter Flight Searches
If you want the best balance of price and practicality, use this sequence:
- Start with the city code to discover the fare range
- Identify which airports keep appearing in the best options
- Check each airport individually
- Add ground transport, arrival time, and baggage needs into the comparison
- Choose the best total trip, not just the cheapest fare
This process takes a little longer, but it consistently beats searching only one airport by habit.
Where This Site Fits In
Airport Codes Info is most useful in the middle of that workflow:
- Use the airport directory to confirm the right code
- Open a specific airport page to understand the airport context
- Compare a long-haul route page if fuel costs and distance matter for the trip
- Read our evergreen guides when you want the planning logic behind the data
Bottom Line
An airport code identifies one specific airport. A city code groups multiple airports serving the same metro area.
If you remember only one rule, make it this:
Use city codes to explore, and airport codes to decide.
That simple distinction makes flight search results easier to read, gives you better price coverage, and helps you avoid booking choices that look cheaper at first glance but cost more once the rest of the trip is counted.