About AeroGuide Hub

Illustrative photo of an airliner parked on an airport tarmac

About AeroGuide Hub

AeroGuide Hub is an independent reference for travellers who want a quick, consistent read on an airport before they fly. Every guide covers the same essentials. Terminals and concourses. Lounges and amenities. Ground transport. A practical tips section. The point is that you spend less time hunting across forums and more time on the trip itself.

Where the data comes from

The first dataset behind AeroGuide Hub is the OpenFlights Airport, Airline and Route Database (https://openflights.org/data.html), an openly licensed (ODbL) collection of more than ten thousand airports and several thousand airlines, plus the published route network linking them. We use OpenFlights for IATA and ICAO codes, geographic coordinates, time-zone data and the route adjacency that powers our network views and rankings. Where OpenFlights is incomplete or out of date for an individual airport, we cross-reference public airport-operator websites and Wikipedia or Wikidata for descriptive context.

How the guides are put together

Every airport, airline, country and city page is rendered server-side from the seeded dataset at request time. We use a structured template that mixes the airport-specific data points (codes, elevation, time zone, route counts) with general guidance that applies to airports of similar size, and then layers in the destination list from the actual route schedule. That gives us consistent guides across hundreds of airports without inventing facts.

What this site is not

Schedules change. AeroGuide Hub is a planning aid, not a live source for flight times, gates or fares. Always confirm the current schedule with your airline and the official airport operator before you travel, and check entry, transit and visa requirements with your government and the destination country.

OurAirports runway & record enrichment (fetched 2026-08-29)

In addition to the OpenFlights/Wikidata base described above, every airport overview page on this site has been checked against OurAirports' open airports.csv (85,986 rows) and runways.csv (48,201 rows) data files (davidmegginson.github.io/ourairports-data mirror), released to the Public Domain. We fetched both files once, on 2026-08-29; OurAirports' own downloads page states the source dataset is regenerated nightly, so we cannot claim a fixed “version date” beyond our own fetch timestamp, and figures on OurAirports may have moved on since.

Join method: exact match only, ICAO code first, IATA code as a fallback when no ICAO match exists — never by airport name, because OurAirports carries several thousand similarly-named airports and a name match risks attaching the wrong airport's runway data to a real page. Of 800 existing airport pages, 794 matched exactly (781 by ICAO, 13 by IATA fallback) and 6 did not match any current OurAirports row and were left completely untouched:

berlin-berlin-tegel-airport-txl (iata=TXL, icao=EDDT)
bishkek-manas-international-airport-fru (iata=FRU, icao=UAFM)
donetsk-donetsk-international-airport-dok (iata=DOK, icao=UKCC)
siem-reap-siem-reap-international-airport-rep (iata=REP, icao=VDSR)
tripoli-tripoli-international-airport-tip (iata=TIP, icao=HLLT)
west-palm-beach-palm-beach-international-airport-pbi (iata=PBI, icao=KPBI)

We checked why those six did not match: four (Donetsk, Siem Reap, Tripoli International, Berlin Tegel) are now listed by OurAirports with type=closed and blank ICAO/IATA columns; two (West Palm Beach and Bishkek Manas) now carry different ICAO/IATA codes in OurAirports than the ones this page displays (the old codes survive only in OurAirports' free-text keywords field, which we deliberately do not join on to avoid a wrong-airport match). None of these six pages were modified.

Fields added to the 794 matched pages, copied verbatim from the matching OurAirports row and clearly labelled “(OurAirports)” so they are never confused with the page's original OpenFlights-derived facts: airport type, scheduled-service flag, municipality, GPS code, local code (where present), elevation in feet, and a link to the OurAirports-linked Wikipedia article (where present). We also added a runways table — identifier, length, width, surface, lighted flag and open/closed status — sourced from runways.csv and joined by the airport's internal OurAirports id (runways.airport_ref = airports.id), the same row used for the ICAO/IATA match. 1,486 runway records were attached across the matched pages; 1 matched airport had no runway rows in the current OurAirports file (also shown honestly on its page, not hidden).

What we deliberately left alone: the generic “Terminals and concourses”, “Lounges and amenities”, “Getting to and from the airport” and “Tips for travellers” prose on every airport page is templated copy that varies by airport size category, as already described above (“a structured template that mixes airport-specific data points with general guidance”). Adding real OurAirports/runway data to a page does not mean that templated prose has been individually verified for that specific airport — it has not, and we are not presenting it as such. We also did not touch the four secondary guide pages (lounges/layover/terminals/transport) per airport, or generate any new per-airport-record page tier; this was a targeted data augment of the 800 existing overview pages only, keeping the same page count and URLs.

Spotted a mismatch between this page and OurAirports or another public source? See Contact for how to send a correction.

Get in touch

Spotted a mistake or want to suggest an addition? The contact page has a short form for corrections, editorial suggestions and press enquiries. We read every message and we update fast when the source is something we can verify.