Airport Code Lookup

Find IATA / ICAO codes, coordinates and timezone for ~200 major airports worldwide.

Open tool

Overview

The Airport Code Lookup is a search-as-you-type reference for roughly two hundred of the busiest passenger airports worldwide. Type a city, an IATA three-letter code or an ICAO four-letter code and the table filters live, showing coordinates, elevation and the canonical Olson timezone for each match.

Travel planners, pilots filing flight plans, logistics dispatchers and developers building flight-search UIs all need a quick way to translate an IATA code lookup into a location. The tool answers questions like "what city is LHR?", "what is the ICAO code for JFK?" and "what timezone does NRT use?" without making you wade through a Wikipedia table.

How it works

The dataset is shipped as a static C# table compiled into the assembly, so lookups run entirely client-side with no network call. Each row carries the airport name, city, country, IATA code, ICAO code, latitude, longitude and timezone in IANA Continent/City format.

The filter is a case-insensitive contains match across every column, so partial searches like "heath" or "tokyo" surface the right airport even if you don't remember the code. Coordinates are in signed decimal degrees so you can paste them directly into a mapping API or great-circle distance calculator.

Examples

LHR  →  London Heathrow, GB, 51.4700°N 0.4543°W, Europe/London
tokyo  →  HND Haneda + NRT Narita
JFK  →  John F. Kennedy Intl, New York, US, America/New_York
EDDF  →  Frankfurt am Main, DE, Europe/Berlin

FAQ

What's the difference between IATA and ICAO codes?

IATA codes are three letters used on boarding passes and tickets. ICAO codes are four letters used by air traffic control and flight plans. A single airport has one of each; for example Los Angeles is LAX (IATA) and KLAX (ICAO).

Why is my small regional airport missing?

The dataset covers roughly two hundred of the world's busiest commercial airports. Private fields, military bases and very small regional strips are excluded to keep the bundle compact.

Are the timezones DST-aware?

Yes. The IANA timezone identifier is what you feed into a date library, and those libraries apply the correct DST rules for the date you supply.

How accurate are the coordinates?

Coordinates are taken from official AIP charts and are precise to four decimal places, which is about eleven metres. Plenty for mapping a flight; not enough for taxiway routing.

Can I search by country?

Yes. The filter checks the country field as well, so "japan" returns every Japanese airport in the dataset.

Try Airport Code Lookup

An unhandled error has occurred. Reload ×