{{ 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
Export to PDF Fullscreen
Customize
Advanced
:

Airport codes are short identifiers that keep booking, baggage, schedules, flight planning, and data cleanup from relying on long airport names. The code most travelers see is usually the three-letter IATA code, while the four-letter ICAO location indicator is common in aviation operations, flight plans, and many airport registries.

A code lookup is useful because airport names rarely stay simple. One city can have several airports, one airport can be known by a commercial name and a formal name, and a metropolitan area can have its own code apart from the airports that serve it. Some small airfields have no IATA passenger code at all, so a missing three-letter code is not the same as a missing airport.

Passenger codes, operations codes, place matches, and coordinate evidence connected in an airport lookup path.

Place and coordinate evidence help separate look-alike results. A city search for Tokyo can lead to multiple airports, while an exact code search for KUL should lead directly to Kuala Lumpur International Airport when the data contains that row. The right result is the row whose code, airport name, place, and coordinates agree with the real trip, manifest, schedule, or aviation record you are checking.

Airport-code data can still lag official changes or omit local details. Use lookup results as practical reference evidence, then verify travel-critical, operational, regulatory, or billing decisions against an airline, airport, IATA, ICAO, or another authoritative source.

How to Use This Tool:

Start with the most specific clue you have, then widen the airport set only when the first result does not match the airport you meant.

  1. Enter an Airport code, city, or name. Three-letter IATA codes such as KUL and four-letter ICAO codes such as WMKK are matched first when they are exact.
  2. Choose Search focus. Use Code-first lookup for manifests and baggage work, City or country lookup for place searches, and Airport-name lookup when you only know part of the airport name.
  3. Set Airport set. IATA passenger codes keeps the output close to booking and baggage workflows, Major passenger airports narrows broad city searches, and All loaded registry entries can surface ICAO-only or local airfields when the public registry is available.
  4. Use Region filter only when the market is known. Leave it at All regions when a code or airport name could appear outside your first guess.
  5. Adjust Result limit if the Match Ledger needs more alternatives. The accepted range is 3 to 25 rows, while Nearby Codes uses up to 10 coordinate-bearing neighbors around the selected airport.
  6. Open Advanced when source behavior matters. Public registry plus fallback loads the larger public airport set in the browser and uses the starter list if it cannot load; Built-in major-airport starter keeps the lookup to the included major-airport rows.
  7. Review the summary badge, Code Match, Review Cues, and Match Ledger before copying a code. If the status is No airport match or the registry warning appears, broaden the airport set, clear the region filter, shorten the query, retry the public registry, or switch the data source before trusting the absence of a result.

Interpreting Results:

The strongest result is an exact IATA or ICAO match whose airport name, place, and coordinates all agree with the record you are checking. A high score from a city or name search is still a ranked suggestion, not proof that the airport is active, official, or correct for a specific ticketing or operational use.

Use Code Match for the selected row, Review Cues for source and ambiguity checks, Match Ledger for close alternatives, Nearby Codes for geographic context, and Coordinate Map to spot obvious coordinate mismatches. When a city has several airports, compare the Place, Matched fields, Distance, and Bearing fields before copying the leading code.

Result cue What it means What to verify
Exact code The query exactly matches the selected row's IATA or ICAO code. Check the airport name and place because some workflows mix city, airport, and operational codes.
High confidence or Likely match The ranking found strong code, place, or airport-name evidence. Review the Matched fields and close alternatives before using the code in a manifest or itinerary.
Review match The row has some matching evidence, but the query did not settle the airport clearly. Narrow the query, choose a better search focus, or add a region only after confirming the market.
No airport match The current airport set, source, and region filter returned no positive row. Clear the region filter, choose all loaded entries, or try the airport's city, country, IATA code, or ICAO code.

Technical Details:

IATA location identifiers and ICAO location indicators solve different naming problems. IATA codes are compact commercial identifiers used heavily in passenger-facing systems, while ICAO indicators are four-letter operational identifiers that cover a broader set of aerodromes and aviation facilities. A complete airport row can carry both, one, or neither, depending on the airport type and the available registry data.

Airport lookup is a ranked evidence problem rather than a single exact dictionary read. Code equality is the strongest clue, code prefixes can help while typing, and place or airport-name matches are useful when the starting point is a city, country, state, timezone, or partial airport name. Region filters and airport-set choices narrow the candidate rows after the source data has been prepared for searching.

Lookup Core:

Stage Matching behavior User-visible evidence
Code match Uppercase alphanumeric code text is compared with IATA and ICAO values; exact matches outrank prefixes. IATA code, ICAO code, summary code tokens, Matched fields, and Review Cues.
Place match City, state, country, country code, broad region, and timezone text can match exact terms, prefixes, or all query tokens. Place, Region bucket, and place-related ledger evidence.
Airport-name match Airport names can match exact text, prefixes, or all query tokens, with the search focus changing how strongly that evidence is weighted. Airport name, summary title, and airport-name ledger evidence.
Scope filter IATA-only mode removes rows without a passenger code; major-airport mode keeps the starter major-airport set; all-entry mode keeps loaded registry rows. Airport set, Result count, and the rows shown in Match Ledger.
Source selection The larger public registry is merged with the starter rows when it loads; starter mode uses only the included major-airport records. Dataset source, source badge, registry retry action, and any registry warning.

Confidence Rules:

Displayed badge Boundary Interpretation limit
Exact code IATA or ICAO exact match, regardless of score band. Still verify the airport name and place when the code appears in a copied schedule or third-party list.
High confidence Score greater than or equal to 100 without an exact-code override. Strong ranked evidence does not confirm official status or current commercial service.
Likely match Score greater than or equal to 55 and less than 100. Review alternatives when the query is a city, country, or partial airport name.
Review match Score greater than 0 and less than 55. Use the ledger evidence as a lead, not as a final code choice.
Needs input No positive match in the current filtered rows. A filter, source issue, or missing registry row may be the cause.

Formula Core:

Nearby-code distance uses a spherical great-circle calculation from decimal latitude and longitude. Coordinates are treated as points on Earth, not as road routes, terminal walking distances, or airport-boundary polygons.

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 formula is applied. Nautical-mile output divides the kilometer distance by 1.852. The initial bearing is normalized to 0 through 359 degrees, rounded to the nearest degree, and labeled with one of eight compass points: N, NE, E, SE, S, SW, W, or NW.

Data and Code Boundaries:

Field Meaning Boundary
IATA code Three-letter passenger and commercial location code when one is listed. Some airfields and facilities have no IATA code, and IATA city or metropolitan codes can differ from individual airport codes.
ICAO code Operational location indicator when listed by the data source. It is useful for aviation records, but it does not replace checking the current official location-indicator publication.
Coordinates Decimal latitude and longitude used for nearby-code distance and the coordinate chart. Coordinates represent a source point for the airport, not a gate, terminal, route, or runway-end survey.
Elevation Source elevation in feet with a metric conversion. Use aeronautical publications for flight-planning-critical elevation values.
Dataset source The selected row's public registry or starter-row origin. Community-maintained and starter datasets can be incomplete, stale, or differently named from airline systems.

Accuracy and Privacy Notes:

The public registry option requests a public airport dataset in the browser, then ranks the current search text on the page. The search phrase itself is not sent to simplified.tools for lookup processing. If the registry cannot be loaded, the page reports that condition and uses the included major-airport starter rows.

  • Registry rows may lag code assignments, airport renames, closures, or commercial-service changes.
  • Opening the map sends the selected coordinates to OpenStreetMap in a new tab.
  • Copied tables and JSON can include the current query, selected airport details, coordinates, and source labels.
  • Use official airline, airport, IATA, ICAO, or state aeronautical sources before making travel-critical or operational decisions.

Worked Examples:

A manifest cleanup starts with KUL, Code-first lookup, IATA passenger codes, and Asia-Pacific. The summary should show KUL with WMKK, Code Match should list IATA code as KUL and ICAO code as WMKK, and the badge should read Exact code. The follow-up check is the Place field: Kuala Lumpur, Malaysia should match the manifest context.

A travel support note says only "Heathrow." With Airport-name lookup, IATA passenger codes, and Europe, the expected lead row is London Heathrow Airport with LHR and EGLL when that row is available. Matched fields should point to airport-name evidence, while Dataset source tells you whether the row came from the public registry or the starter list.

A city search for Tokyo works better with City or country lookup and Major passenger airports. The Match Ledger can include both HND and NRT, and Nearby Codes can show distance and bearing between them. That is a cue to choose the airport from the itinerary, not merely the top-ranked city match.

A query for a small airfield may show No airport match while IATA passenger codes is selected. Switch to All loaded registry entries, clear the Region filter, and try the ICAO code or airport name. If a registry warning remains, the starter data may simply not contain that airfield.

FAQ:

What is the difference between IATA and ICAO airport codes?

IATA codes are three-letter commercial location codes that passengers often see on tickets, baggage tags, and booking systems. ICAO codes are four-letter operational identifiers used in flight planning and aviation records, so an airport can need both depending on the task.

Why does an airport have no IATA code?

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

Why did a city search pick one airport over another?

City searches rank rows by place evidence, airport-name evidence, major-airport status, and available passenger codes. Use Match Ledger and Nearby Codes to compare alternatives when a city has more than one airport.

What should I do when the public registry is unavailable?

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

Does my search text leave the page?

The lookup ranking runs in the browser. Public registry mode requests 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 the same as travel 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, route distance, or distance between terminals.

Glossary:

IATA code
A three-letter location code used mainly in passenger, baggage, booking, and commercial airline contexts.
ICAO code
A four-letter location indicator used in aviation operations, flight planning, and many airport registries.
Match Ledger
The result table that ranks matching airport rows and shows code, place, score, matched fields, and source.
Review Cues
The result table that turns the selected match into checks for code role, ambiguity, source coverage, coordinate evidence, and safe-use boundaries.
Region bucket
The broad geographic grouping derived from the airport country code for optional filtering and review.
Great-circle distance
The shortest spherical distance between two coordinate points, used here for nearby airport context.
Nautical mile
A navigation distance unit equal to 1.852 kilometers, used as an alternative to kilometer output.

References: