Airport reference

Airport facility lookup

Search indexed airports by ICAO, IATA, or FAA identifier, airport name, city, or state. Review available location, elevation, runway, and frequency records.

What the airport facility lookup shows

Search the indexed airport records by ICAO, IATA, or FAA identifier, airport name, municipality, state, or country. Select a result to review its identifiers, coordinates, field elevation, runway records, and frequency records. The current record count is shown beside the search field.

The lookup searches the airport data bundled with this site. It does not query a live FAA service or check whether an airport, runway, or frequency is currently available. The URL stores the search and selected airport, so a particular lookup can be bookmarked or shared.

Enter part or all of an identifier, airport name, city, or state. The list ranks exact airport codes before broader matches. Search terms can be combined, such as Denver CO. Choose a result to display its facility record. The example buttons load sample airports already present in the dataset.

If a search returns several airports, use more of the name or add a location term. The result list shows up to eight matches at a time. For a broader airport index, open the airport directory, which links to the individual airport profiles.

Reading the airport record

The identifier row distinguishes the ICAO, FAA, and IATA codes stored for the airport. These identifiers are not interchangeable. Many US airports have a three-character FAA location identifier that is also used as an IATA code, while the ICAO identifier commonly adds a leading K. Other countries use different identifier patterns.

Coordinates are displayed in decimal degrees with a hemisphere letter. Field elevation is shown in feet. These values describe the airport record, not a surveyed position for every runway end or a current altimeter indication.

Runway rows include the runway end identifiers, recorded true headings where present, length and width in feet, surface classification, and the dataset lighting flag. A runway end without a recorded heading is shown as not listed rather than treating a zero value as a usable heading. Surface labels are reproduced from the source record and may use abbreviations.

Frequency rows show the stored description and value in MHz. The dataset may contain different facility types, such as tower, ground, ATIS, or CTAF. Treat these as reference records only. A frequency can change, be out of date, or have a context that is not fully expressed by its short label.

Example lookup

Search for KAPA to find Centennial Airport in Colorado. The record lists field elevation as 5,885 FT and includes three runway records. One listed runway is 17L / 35R, with recorded dimensions of 10,001 x 100 FT. The result also includes the frequency entries stored for this airport and a source date.

This example describes the static record in the site's airport dataset. It is not confirmation of current runway status, a clearance, or an instruction to use a particular frequency. Check current official publications and airport information for operational use.

Data coverage and limitations

Airport coverage is limited to the records currently included in the site's dataset. A search with no match means only that no matching local record was found. It does not establish that an airport or facility does not exist.

The current airport records contain basic identifiers, location, elevation, runway data, and frequencies when those fields are available. They do not provide verified fuel availability, FBO services, instrument approach procedures, nearby flight schools or examiners, or live METAR and TAF information. A missing field is not evidence that the service or facility is unavailable.

Runway and frequency records can lag real-world changes. Temporary closures, construction, displaced thresholds, special procedures, and other changes may be published separately. This tool does not include NOTAMs, airport diagrams, current charts, or live weather. It does not calculate runway suitability or make an operational flight decision.

Sources and methodology

The source recorded for the current airport entries is the OurAirports public data download, which provides airport, runway, and airport-frequency datasets. Each result displays the source and update date stored with that airport record. The date describes the local dataset vintage; it is not a live freshness check.

The FAA NASR Subscription is an official source for US aeronautical data and publishes updates on a recurring cycle. This lookup does not fetch NASR or other current FAA data at search time. Confirm operational details against current FAA publications, airport information, and NOTAMs.

Common questions

Does this lookup cover every airport?

No. It searches the airport records currently included in this site. The number beside the search field is the number of local records, not a count of every airport worldwide or in the United States.

Does a missing frequency or service mean it is unavailable?

No. It means the field is not present in the record or is not covered by this dataset. Check current official publications or contact the airport for services and availability.

Are the frequencies current?

The lookup displays static source records with their stored update date. It does not validate frequencies against a current chart or live FAA service. Verify a frequency using current official publications before relying on it.

Can I use this instead of an airport chart or NOTAM briefing?

No. This reference does not contain current airport diagrams, procedures, weather, or NOTAMs. Use current official aviation publications and sources for flight planning and operations.

Reference use

For training and reference only. Airport data can be incomplete or out of date. Verify identifiers, runway information, frequencies, procedures, weather, and operating conditions against current official sources. This lookup is not an operational flight decision.