About the data

Everything here comes from the US Bureau of Transportation Statistics' T-100 segment data, 1990–2025. It is easy to read more into it than it says, so this page sets out what each number means and where the data has gaps.

Routes are one-way

Each row of T-100 is one nonstop flight segment in one direction, from an origin airport to a destination airport. A route page for ATL–LAX shows flights from ATL to LAX; the flights back are the route LAX–ATL. An airport's page counts flights from that airport, and its passenger figure is people departing it, not arriving.

Nearly every busy route has a return: of airport pairs with at least 100 departures in a year, 99% also have flights the other way. Counting every pair, however small, only about 71% do. The ones without a return are mostly:

T-100 only includes flights with a US airport at one end. For an airport outside the US, only its US routes appear: Heathrow's page lists its flights to and from the US, not to Paris. Flights between two foreign airports are not in the data at all, even by US airlines.

Freight-only and belly cargo

BTS gives each segment a service class. Scheduled and non-scheduled passenger flights (classes F and L) are passenger flights, and any cargo they carry in the hold is belly cargo. All-cargo flights (classes G and P) are freight-only, flown by freighter aircraft. The charts' "passenger flights", "freight flights" and "all flights" options mean exactly these. "Freight" totals on a passenger flight are belly cargo; a freight-only flight has essentially no passengers.

Freight and mail are separate columns in the data, and the site shows freight only, not mail. The data is in pounds; the site converts to short tons (2,000 lb), the US ton.

What the numbers measure

How things are grouped

Known gaps and breaks

What is and isn't covered

Source

The data is the Bureau of Transportation Statistics' Data Bank 28DS and 28IS: T-100 Domestic Segment and T-100 International Segment. Airport names and coordinates come from OpenFlights, with some corrections of our own, and city names are BTS's. The grouping rules and the code behind the site are in the project on GitHub.

Every page links to the data it draws, under “This page's data” at the foot of the page (on a map, “This map's data” among its controls). That opens the query behind the page, filled in with the page's settings. The fields at the top of it can be changed: most queries that read an airline group take group, the group's id as it appears in its page's address (delta, united), and left empty it means every airline. The underlying segments can be browsed and filtered column by column in the t100 table, though that uses BTS's own carrier and aircraft codes rather than this site's groups and families.