These community reference lists support optional suggestions. They are not complete or authoritative IATA/ICAO registries; codes can be reused and historical entries are retained. Your custom and imported entries are not replaced.
The airline catalog contains 8,372 reference entries, combining all 6,162 original OpenFlights records with code-supported name/alias enrichment and additional Wikidata records, retrieved September 6, 2026. Search uses brand/legal names, aliases, IATA and ICAO codes. Missing and uncertain codes stay unassigned; historical codes remain searchable and reused codes are not silently merged. Aircraft suggestions combine 269 core entries (OpenFlights plus curated subtype/code additions) with a September 6, 2026 snapshot of 12,785 aircraft models and families from Wikidata, deduplicated by model name. Wikidata structured data is CC0. Broad families, historical models, and military types are included; these are not guaranteed to match myFR24’s proprietary catalog. Model names without verified IATA/ICAO mappings remain uncoded rather than guessed. Your own imported aircraft names are also offered privately within your logbook. Viva (Mexico) is a curated correction of the existing VIV entry, including VB and Viva Aerobus aliases; source notes are in the downloadable README. Airline active flags and assignments are not treated as verified current operating status. Historical airlines and operators without both codes are included. OpenFlights identifiers are never treated as Flightradar24 identifiers.
Reference databases are distributed under the Open Database License 1.0; individual contents under the Database Contents License. OpenFlights notes that Wikipedia-derived contents may also be subject to the GNU Free Documentation License.
Airport locations: OurAirports, public-domain data. IANA zone suggestions were derived for 9,768 airport locations using geo-tz 8.1.8 (MIT), its comprehensive historical-zone lookup, and timezone-boundary-builder boundaries. Boundary-derived data is ODbL 1.0, © OpenStreetMap contributors. All candidates are retained for ambiguous locations.
Download the derived airport-to-time-zone database. Historical airport location changes and disputed boundaries can affect suggestions; automatic timing is available when one airport time zone can be resolved. Otherwise use recorded duration. Elapsed time uses IANA time-zone rules via the Temporal polyfill. New and edited timing infers the first possible arrival day, or uses recorded duration to identify multi-day arrivals. Imported timing stays unchanged on unrelated edits.
Atlas land boundaries: Natural Earth (public domain). Interactive rendering: MapLibre GL JS (BSD 3-Clause).
Satellite imagery in Atlas and Fleet is supplied by Esri World Imagery, with credit to Esri, Vantor, Earthstar Geographics and the GIS User Community. Imagery dates and detail vary by location; it is not live. Satellite tile requests include map tile coordinates, not your flight records or notes. Flight routes are separate diary overlays.
Atlas land and country outlines share the same Natural Earth geometry. Regional borders are clipped to that land; satellite international borders exclude coastlines. These are generalized reference boundaries, not survey data.
Routes are illustrative great-circle connections, not recorded flight tracks. Mint highlights count flights between an airport pair in both directions within your current filters. Map-only visibility controls do not change flight statistics.
flightlab.io flight log uses the supplied Tailfin · Brand Guide 03 identity. The blank-fin signature follows Brand Guide 03. The compact fl mark and the Ink, Paper, Orange and Teal palette are unchanged from Edition 02. Manrope and IBM Plex Mono are self-hosted under the SIL Open Font License 1.1.