{{ selectedAirport.iata || selectedAirport.icao || 'N/A' }} {{ selectedAirport.icao || 'No ICAO' }}
{{ summaryTitle }}
{{ summaryDetail }}
{{ confidenceBadge }} {{ sourceBadge }} {{ resultCountBadge }} Disabled
Open map
Loading public airport registry...
Exact IATA and ICAO matches rank first; city, country, timezone, and airport-name matches remain searchable.
{{ sampleHint }}
Use Code when cleaning manifests, Place when starting from a city or country, and Airport name for partial airport names.
Keep IATA passenger codes for booking and baggage work; use all registry entries for aviation data cleanup.
Use All regions unless you are narrowing a known airport market.
{{ limitLabel }}
Accepted range: 3-25 rows.
rows
The lookup is client-side; no user search text is sent to simplified.tools.
{{ registryActionHint }}
Metric uses kilometers; aviation-style output uses nautical miles.
Field Value Evidence Copy
{{ row.field }} {{ row.value }} {{ row.evidence }}
Rank IATA ICAO Airport Place Score Matched fields Source Copy
{{ row.rank }} {{ row.iata }} {{ row.icao }} {{ row.airport }} {{ row.place }} {{ row.score }} {{ row.matched }} {{ row.source }}
Cue Current evidence Action Copy
{{ row.cue }} {{ row.evidence }} {{ row.action }}
Code ICAO Airport Place Distance Bearing Copy
{{ row.code }} {{ row.icao }} {{ row.airport }} {{ row.place }} {{ row.distance }} {{ row.bearing }}
Tags: Aviation, Transport
Flight Tracker Track an aircraft by callsign, ICAO hex, or region, then compare OpenSky freshness, map position, heading, and candidate matches.
Flight Delay Tracker Check a flight number by departure date with sample or provider data, then compare delay minutes, route matches, and timeline evidence.
Flight Emissions Tracker Estimate flight CO2e from airport codes or manual leg distances, compare cabin, SAF, RF, and offset scenarios, and audit each leg.
Country Information Lookup Find country details from a name, ISO code, calling code, currency, capital, or region, with match ranking, source status, maps, and scale charts.
Customize
Advanced
:

Airport codes compress a long place name into a short identifier that can travel through tickets, baggage tags, schedules, operations records, and data exports without spelling drift. The familiar three-letter code is usually an IATA location code, while the four-letter code used in flight planning and air-traffic contexts is an ICAO location indicator. They often point to the same airport, but they are not interchangeable labels.

The difference matters most when the clue is incomplete. A traveler may remember "Heathrow" instead of LHR, a spreadsheet may contain WMKK instead of KUL, and a city such as Tokyo can refer to more than one airport. IATA also assigns location codes to cities, metropolitan areas, and some intermodal locations, so a three-letter code can describe a passenger place rather than a single runway or terminal.

Identifier Typical shape Common use Where people misread it
IATA location code Three letters, such as KUL or LHR Passenger, booking, baggage, schedule, and commercial airline contexts. A code can represent an airport, city, metropolitan area, rail station, ferry point, or another commercial location.
ICAO location indicator Four letters, such as WMKK or EGLL Operational aviation references, flight planning, aeronautical data, and air-traffic systems. It may exist for airports that do not have a passenger-facing IATA code.
City or metropolitan code Usually three letters in passenger systems Grouping several airports under one commercial city market. The code may not identify a single airport row, runway, or terminal.
Local or registry identifier Varies by country or dataset Data cleanup, local aerodrome records, and broader airport registries. It can be useful evidence without being valid for airline booking or operations use.
IATA code, ICAO code, place match, and coordinate evidence cards for an airport lookup.

Good code matching is therefore more than a dictionary lookup. The safest answer is the row where the passenger code, operations code, airport name, city or country, and coordinates all support the same place. A city match by itself can be useful for discovery, but it should not be copied into a manifest, itinerary, booking note, or operations record until the airport row makes sense.

Airport-code records change when airports open, close, rename, gain service, lose service, or move between commercial and operational systems. A lookup can narrow the candidates and expose useful evidence, but official airline, airport, IATA, ICAO, or state aeronautical sources remain the right authority for travel-critical, regulatory, billing, or flight-planning decisions.

How to Use This Tool:

Start with the clue that is least likely to be ambiguous, then use the filters only when they reflect something you already know about the airport market.

  1. Type an Airport code, city, or name. Exact three-letter IATA codes such as KUL and four-letter ICAO codes such as WMKK get the strongest match evidence.
  2. Set Search focus to match your clue. Use Code-first lookup for manifests and copied code lists, City or country lookup for place clues, and Airport-name lookup for partial names such as Heathrow.
  3. Choose the Airport set. IATA passenger codes fits booking and baggage work, Major passenger airports reduces broad city searches, and All loaded registry entries can show ICAO-only or local airfields when the public registry has loaded.
  4. Leave Region filter at All regions unless the region is known. A wrong region can hide the correct row even when the code or name is valid.
  5. Use Result limit when the Match Ledger needs more alternatives. The control accepts 3 to 25 rows; nearby-coordinate context is shown separately for up to 10 surrounding airports.
  6. Open Advanced when coverage matters. Public registry plus fallback loads the larger registry in the browser and keeps the starter list available; Built-in major-airport starter stays with the included major-airport rows.
    Public-registry mode downloads airport rows, then ranks your typed clue in the browser. The page does not send the search phrase to simplified.tools for lookup processing.
  7. Read the summary badge with Code Match, Review Cues, and Match Ledger. If the result says No airport match or the registry warning appears, clear the region filter, switch to all loaded entries, shorten the query, retry the registry, or use the starter rows only for common airports.
    A city or airport-name match is a candidate, not an official clearance to use the code. Check the place, source, coordinates, and nearby alternatives before copying it into a travel, billing, or operations record.

Interpreting Results:

An Exact code badge is the strongest cue because the query matches the selected row's IATA or ICAO value. That still does not prove the airport is active, open to the public, served by a carrier, or valid for the business process you are checking. Compare the airport name, place, dataset source, and coordinates before using the code outside the page.

City, country, and airport-name searches are ranked suggestions. They are useful when the clue starts as ordinary text, but cities with multiple airports can produce several convincing rows. Use Match Ledger for close alternatives, Review Cues for code-role and source checks, and Nearby Codes or Coordinate Map to catch a row that is geographically wrong for the intended airport.

Result cue Meaning Best verification step
Exact code The query exactly matches the selected IATA or ICAO code. Confirm that the Airport name and Place fields match the record you are cleaning.
High confidence The match score is at least 100 without an exact-code override. Check Matched fields and nearby alternatives, especially for city searches.
Likely match The match score is 55 through 99. Treat the first row as a lead and inspect the Match Ledger before copying a code.
Review match The match score is positive but below 55. Use a more specific code, airport name, city, or country clue before relying on the result.
No airport match No row survived the current query, airport set, source, and region choices. Clear filters, choose All loaded registry entries, or verify that the clue is not a city, rail, ferry, or metropolitan code.

Technical Details:

IATA location codes and ICAO location indicators are maintained for different aviation needs. IATA's three-letter system is oriented around commercial airline locations and intermodal passenger use, while ICAO's four-letter indicators support operational aviation references and cover a wider aerodrome context. An airport row may have both identifiers, only one identifier, or a missing passenger code when the facility is not part of normal commercial-airline workflows.

The lookup ranks evidence from several fields rather than assuming every query is a code. Code equality receives the most weight, prefixes help while typing or cleaning partial lists, and text matches across city, state, country, region, timezone, and airport name help when the starting clue is human-readable. The selected airport set and region filter remove candidates before the final ranking is shown.

Lookup Core:

Stage Mechanism Visible evidence
Code comparison Alphanumeric code text is uppercased and compared with IATA and ICAO values. Exact matches outrank prefix matches. IATA code, ICAO code, summary code tokens, and Matched fields.
Place comparison City, state, country, country code, region, and timezone text can match exact text, prefixes, or all query tokens. Place, Region bucket, and place-related rows in Match Ledger.
Airport-name comparison Airport names can match exact text, prefixes, or all query tokens. The selected search focus changes the relative weight. Airport name, summary title, and airport-name evidence in Matched fields.
Scope filtering IATA-only mode removes rows without passenger codes. Major-airport mode keeps the starter major-airport set. All-entry mode keeps every loaded registry row. Airport set, result-count badge, and the rows that appear in Match Ledger.
Source coverage The public registry is merged with starter rows when it loads. Starter mode uses only the included major-airport records. Dataset source, source badge, registry retry action, and registry warning text.

Ranking and Confidence Rules:

The match score is a whole-number ranking aid, not an official confidence certificate. The same airport can score differently when the search focus changes because code, place, and airport-name evidence receive different weights.

Evidence type Base score before focus weighting Interpretation note
Exact IATA or ICAO code 120 Produces the Exact code badge when the selected row's code equals the query.
Code prefix 72 Helpful for partial code cleanup, but it should be confirmed against the full row.
Exact place text 72 Applies to city, state, country, country code, or broad region text.
Airport-name exact or prefix 84 or 54 Useful for common names, but official and commercial names can differ.
All query tokens present in the row 14 to 34 Adds weaker evidence for broad text searches.
Major airport or IATA row bonus 8 or 4 Helps common passenger airports rank ahead of less common rows when other evidence is close.

A score of at least 100 displays High confidence, a score from 55 to 99 displays Likely match, and a score from 1 to 54 displays Review match. Ties are sorted toward major passenger airports, then rows with IATA codes, then the airport's code or name.

Formula Core:

Nearby-code distance uses a great-circle calculation from decimal latitude and longitude. The calculation treats each airport coordinate as a point on a sphere, so it is a geographic reference distance rather than a drive route, taxi path, gate-to-gate distance, or runway survey.

a = sin ( dlat 2 ) 2 + cos ( lat1 ) cos ( lat2 ) sin ( dlon 2 ) 2
distance km = 2 ⁢ 6371.0088 ⁢ asin ( a )

Latitude and longitude differences are converted from degrees to radians before the distance equation is applied. Nautical-mile output divides kilometers by 1.852. Bearing uses the initial course from the selected airport to the nearby airport, normalized from 0 through 359 degrees, rounded to the nearest degree, and labeled with N, NE, E, SE, S, SW, W, or NW.

Field and Data Boundaries:

Field Meaning Boundary
IATA code Three-letter commercial location code when one is listed for the row. Not every airport has one, and some IATA codes refer to city, metropolitan, rail, or ferry locations.
ICAO code Operational location indicator when available in the selected data row. Use current aeronautical publications for operations-critical confirmation.
Coordinates Decimal latitude and longitude used for nearby rows and the coordinate chart. The point may represent an airport reference location, not a terminal, gate, runway end, or route.
Elevation Source elevation in feet with a meter conversion for readability. Flight-planning elevation should come from official aeronautical information.
Dataset source The row's public-registry or starter-list origin. Community-maintained and starter data can lag code changes, closures, renames, or service changes.

Accuracy and Privacy Notes:

Public-registry mode requests a public airport dataset in the browser, then applies the typed search text on the page. The search phrase is not sent to simplified.tools for lookup processing. If the registry cannot be loaded, the page reports the issue and uses the included major-airport starter rows.

  • Registry rows may be incomplete, stale, renamed differently, or missing recent commercial-service changes.
  • Opening the map sends the selected latitude and longitude to OpenStreetMap in a new tab.
  • Copied tables and JSON can include the current query, selected airport details, coordinates, score evidence, and source labels.
  • Critical travel, billing, regulatory, or flight-planning use should be verified against official airline, airport, IATA, ICAO, or state aeronautical sources.

Worked Examples:

A manifest cleanup row contains KUL. With Code-first lookup, IATA passenger codes, and Asia-Pacific, the selected row should show KUL and WMKK for Kuala Lumpur International Airport. The score is high enough for Exact code, but the practical check is still the Place field: Kuala Lumpur, Malaysia should match the manifest context.

A support note says "Heathrow" without a code. Airport-name lookup, IATA passenger codes, and Europe should lead to London Heathrow Airport when that row is present. Airport-name evidence usually lands in Likely match territory rather than an exact-code result, so Matched fields and Dataset source matter before copying LHR or EGLL.

A city search for Tokyo is better handled with City or country lookup and Major passenger airports. HND and NRT can both appear as strong city matches, and each may pass the High confidence score boundary. Use Match Ledger, Nearby Codes, and the itinerary text to choose the actual airport instead of accepting the first city result blindly.

A small aerodrome may return No airport match while IATA passenger codes is selected. Switch to All loaded registry entries, clear the Region filter, and search by ICAO code or airport name. If a registry warning remains, the starter rows may not include that aerodrome, so absence from the result is not proof the airport does not exist.

FAQ:

What is the difference between IATA and ICAO airport codes?

IATA codes are three-letter commercial location codes used heavily in passenger, booking, and baggage contexts. ICAO codes are four-letter operational location indicators used in aviation operations, flight plans, and many airport registries.

Why does an airport show no IATA code?

Some local, private, military, cargo, or small aerodromes do not have passenger-facing IATA codes. Choose All loaded registry entries and search by ICAO code, airport name, city, or country when IATA-only mode hides the row.

Why did a city search return several good matches?

Large cities and metropolitan areas can have multiple passenger airports. Compare Place, Matched fields, Distance, and Bearing before deciding which code belongs in the itinerary or data row.

What should I do if the public registry is unavailable?

The page falls back to the built-in major-airport starter list. That is usually enough for common airports such as KUL, LHR, HND, and JFK, but smaller ICAO-only airfields may require retrying the registry or checking an official source.

Does my search text leave the page?

The ranking runs in the browser. Public-registry mode downloads the airport dataset, but the typed search phrase is applied locally and is not sent to simplified.tools for a lookup request.

Are nearby distances route distances?

No. Nearby Codes uses great-circle distance between airport coordinates and can display kilometers or nautical miles. It does not estimate drive time, taxi distance, walking distance, route distance, or terminal separation.

Glossary:

IATA code
A three-letter commercial location code commonly used in passenger, booking, baggage, and airline schedule contexts.
ICAO code
A four-letter operational location indicator used in aviation operations and aeronautical records.
Match score
The whole-number ranking value built from code, place, airport-name, major-airport, and IATA-row evidence.
Match Ledger
The result table that ranks candidate airport rows and shows codes, place, score, matched fields, and source coverage.
Review Cues
The result table that turns the selected row into code-role, ambiguity, source, coordinate, and safe-use checks.
Great-circle distance
The shortest spherical distance between two latitude and longitude points, used for nearby airport context.
Nautical mile
A navigation distance unit equal to 1.852 kilometers, available as an alternative to kilometer output.

References: