About AeroRoute Guide

What's in the directory

Every page is built from a snapshot of the OpenFlights public dataset of airports, airlines, and scheduled routes. The current snapshot has 6,071 airports with valid IATA codes, 983 active airlines, and 66,934 scheduled routes covering 235 countries. Every page is pre-rendered and served as static HTML. There's no JavaScript framework, no database server, and no API to call.

How pages are organised

Pages are organised the way travelers actually think about flying. Start broad and work your way down, or jump straight to a code you already have:

• By country. The countries index lists every country on file with its airport and airline counts. Each country page covers the airports and carriers registered there.
• By US state. The US states index covers all 50 states, plus DC and Puerto Rico. We assign each US airport to the nearest state by geographic centroid, so a small airport sitting near a state line can land under its neighbour.
• By airport. Each airport page shows the airport's IATA and ICAO codes, location, time zone, and tables of destinations and operators on file.
• By airline. Each airline page shows the carrier's IATA and ICAO codes, home country, callsign, and a sample of routes operated under that code.
• By route. The routes section ranks city pairs by how many distinct airline codes file against them. Treat that count as a rough signal of how well-served a market is.

Data source and methodology

The primary source is the OpenFlights database. The seed script in this project downloads airports.dat, airlines.dat, and routes.dat from openflights.org/data, keeps the airports with three-letter IATA codes, keeps the active airlines with two-character IATA codes, and joins routes back to both ends of each pair.

Country grouping uses the country name as the OpenFlights record gives it. For US state grouping, we take each US airport's latitude and longitude and assign it to the closest of 52 state-level centroids (50 states, DC, and Puerto Rico) using haversine distance. Every state ends up with a populated page that way, but the result doesn't follow official state lines exactly. A small airport near a border can get filed under the neighbour.

The "operators on file" count on each route page is the number of distinct airline-route entries in the OpenFlights routes table. It isn't a count of weekly flights or seats, so read it as a relative signal of how well-served a market is, not as a published schedule.

What this directory is not

AeroRoute Guide is a reference, not a booking engine. It doesn't show fares, real-time schedules, or seat availability. The OpenFlights routes snapshot is a community-contributed list of city pairs that airlines have operated. Read it as a slowly changing record of which markets each carrier flies, not as proof that any specific flight runs on any specific day. Always confirm schedules and bookings with the airline before you travel.

Why a multi-page static site

Most people land on pages like these from a search engine, not from a homepage. Every URL here maps to a real HTML document with its own title, meta description, and structured data block. Pages are plain HTML and don't need JavaScript to read. That makes them easy to crawl, easy to print, and pleasant to share as plain links.

Source code and licensing

The OpenFlights dataset is distributed under the Open Database License. Full terms are at openflights.org. AeroRoute Guide republishes derived statistics (airport directories, airline summaries, route counts) and points back to the underlying source.

BTS T-100 domestic traffic data (added July 2026)

OpenFlights records which airlines file a route. It has no passenger counts, no freight figures, and no departure frequency — and it's a static snapshot generated in 2014, never updated since. In July 2026 we added a second, independent, government-sourced layer on top of it: real 2025 passenger, freight, and departure-frequency data from the U.S. Bureau of Transportation Statistics' T-100 Domestic Segment (All Carriers) table, a monthly-updated database that certificated U.S. and foreign air carriers are required to file for every non-stop domestic segment they operate.

Pipeline. We fetched the full calendar-year-2025 T-100 Domestic Segment (All Carriers) file directly from BTS's TranStats download tool (DL_SelectFields.asp, no API key, no login), keeping only BTS service class F (scheduled passenger/cargo service — the class relevant to a passenger route directory; all-cargo and non-scheduled service are excluded). That gave us 359,156 real carrier/route/aircraft-type/month rows, which we aggregated to one totals block per directed (origin, destination) IATA pair: passengers, freight, mail, departures scheduled, departures performed, seats, a per-carrier passenger/departure breakdown (carrier names are BTS's own record values), and the aircraft types flown (names resolved against BTS's own published aircraft-type lookup table).

Matching. We matched by exact (origin, destination) IATA-code equality against this site's existing route-page keys — no fuzzy matching, no combining nearby airports, no filling in a gap with an estimate. Of the 5,349 existing route pages where both endpoints are in the United States or a US territory (Puerto Rico, Guam, the US Virgin Islands, American Samoa, and the Northern Mariana Islands, alongside the 50 states and DC), 4,879 (91.2%) matched a real 2025 BTS record and now show a "BTS domestic traffic" section. The remaining 470 domestic-eligible pages, and every international route page, are untouched — they still show only the original OpenFlights operator/distance/connecting-hub content, exactly as before this addition. See the BTS domestic traffic hub for the full coverage numbers and a top-50-routes table.

Fields rendered: 2025 passengers, freight (lb), mail (lb), departures scheduled, departures performed, an approximate seats-filled percentage (passengers ÷ seats), a per-carrier passenger/departure breakdown, and aircraft types flown by departures performed. Fields withheld: internal BTS numeric ID columns (airport/city-market/carrier-entity IDs — no reader value), `RAMP_TO_RAMP` and `AIR_TIME` (not part of this build's displayed stats), and any month-by-month breakdown (we show full-year totals only, to keep 4,879 pages readable rather than adding 12 rows of near-duplicate detail to each).

Cadence. BTS publishes T-100 Domestic Segment data monthly, roughly two months after month-end. We used full calendar year 2025 (the most recent complete year) because as of this fetch (July 2026) BTS's own download tool did not yet offer a 2026 option. We plan to refresh this section when a complete 2026 year becomes available; we do not claim a monthly-refresh cadence for this site.

Corrections. Every figure on a "BTS domestic traffic" section traces to a real BTS-filed row for that exact route in 2025 — nothing is estimated, interpolated, or carried over from a different route or year. If you spot a mismatch between what's shown here and BTS's own published data, or a route you believe should have matched but didn't, contact us with the route and we'll check it against the source file.