Data sources

Airport data — OurAirports

Airport names, IATA and ICAO codes, city, country, coordinates, elevation, facility type and scheduled-service status come from OurAirports, a community-maintained database released into the public domain and updated nightly.

This site downloads the dataset at build time and pins a snapshot, rather than fetching it in your browser. That means the search is fast, works offline, and does not depend on a third-party host being up while you use the site — at the cost of being as current as the last build rather than as current as last night.

Known limitations:

• Community-maintained data contains errors and omissions, particularly for smaller airports
• Airport names change with renamings and rebrandings; records lag
• Scheduled-service flags can be stale where service has recently started or stopped
• Coordinates are the airport reference point, not a terminal or gate
• Terminal information is not in the dataset and is not shown anywhere on this site

For anything that matters, verify against the official airport website. See methodology for exactly which records are kept and which are filtered out.

Time zone data

Each airport's IANA time zone is derived from its coordinates at build time using a coordinate-to-timezone lookup. Offsets are then resolved in your browser, for the specific date in question, using the Intl API and the IANA time zone database your browser ships.

This means daylight saving and non-whole-hour offsets are handled correctly, and it also means the accuracy of an offset depends on how current your browser's timezone database is. Browsers update these regularly; a very old browser may be wrong about a recent rule change.

Known limitations:

• Coordinate-based lookup can be wrong near a zone boundary, which is rare for airports but possible
• Countries occasionally change time zone rules at short notice, ahead of database updates

Airline data — manually curated

The 30 airlines in the airline lookup and directory are maintained by hand: IATA and ICAO designators, home country, alliance membership, primary and secondary hubs, official website and founding year.

There is no comprehensive public-domain airline dataset with the licence terms this site needs, so the trade-off is a small, verified set rather than a large, uncertain one.

Known limitations:

• Hubs and alliance membership change; these are updated between builds, not automatically
• Only 30 major carriers are covered. A code not listed is not necessarily invalid
• Ticket-stock accounting prefixes shown in the guides are illustrative examples, not a complete table

What this site does not use

Worth stating explicitly, because it bounds what the tools can honestly claim:

• No live flight schedules. No GDS, no airline API, no schedule database. Nothing here knows whether a flight exists.
• No fare or availability data. Any fare shown on a sample is a figure you typed.
• No reservation system access. Which is why no booking reference or ticket number can be issued.
• No third-party runtime requests. All data is served from this site; no external calls are made while you use it.

Refresh policy

• Airport data: refreshed from the source when the site is rebuilt. The snapshot timestamp is shown above and in the footer.
• Airline data: reviewed periodically and corrected on report.
• Regulatory guidance: reviewed quarterly, with a review date shown on the relevant guides.

Reporting an error

Data errors are worth reporting even when small. Get in touch with the airport or airline concerned and what the correct value should be. Errors originating in the OurAirports dataset are best fixed at the source, where the correction benefits everyone using it.