Flight Route Database — How to Analyze Global Airline Route Networks

Flight route database explained. How to analyze global airline route networks, hub-and-spoke vs point-to-point structures, route frequency, competitive density and network metrics. Flight route data analysis patterns for aviation professionals.

Sergey St.

Published on Jun 17th 26

Share:

• 
• 
• 

What Is a Flight Route Database?

A flight route database is a structured dataset that records every regularly scheduled connection between airports in the global aviation system. For each route, the database stores which airline operates it, which days of the week the service runs, the typical duration, the terminals used at each end and other operational characteristics. Together, these records describe the global airline network as a graph — airports are nodes, routes are edges, and the resulting structure reveals the entire shape of commercial aviation.

Unlike a flight schedule, which records every individual flight by departure time, a route database operates at a higher level of abstraction. The route "Heathrow to JFK on British Airways" is a single entry — encompassing the daily 09:00 flight, the daily 13:00 flight and the daily 17:30 flight as one operational service. This higher-level view is what aviation analysts, consultants, investors, regulators and route planners actually need to study network structure, competitive dynamics and capacity allocation.

This guide explains the analytical patterns and use cases for flight route databases. It covers how to think about network structure, what metrics matter, and how to combine route data with the broader AirLabs platform to answer strategic questions about global aviation. For developer-level reference on querying the routes API directly — the parameters, response fields and integration patterns — see the Routes Database API documentation.

"A route database is the closest thing aviation has to a structural map of the entire industry. Reading it correctly tells you which airlines compete where, which airports anchor the system, which markets are saturated and which are underserved — information that drives billions of dollars in strategic decisions every year."

The Structure of an Airline Route Network

Airline networks fall into three main structural patterns, each with very different operational economics:

Hub-and-Spoke Networks

Most legacy carriers operate hub-and-spoke networks. Traffic from many origin airports is funneled through one or more major hub airports, where passengers connect to onward flights. The hub model concentrates capacity, simplifies aircraft routing and enables the airline to serve smaller markets that would not support point-to-point services on their own.

Hub-and-spoke airlines show characteristic patterns in route data: a small number of airports appear as the departure airport for an outsized share of the carrier's routes. Querying the Routes Database for an airline like Lufthansa, then aggregating routes by departure airport, immediately reveals Frankfurt and Munich as the network anchors.

Point-to-Point Networks

Low-cost carriers and many regional operators run point-to-point networks. Aircraft fly direct between secondary airports without funneling traffic through a central hub. This model produces high aircraft utilization and lower operating costs, but limits the airline's ability to serve very thin routes that require connecting traffic to be economical.

Point-to-point carriers show flatter network distributions in route data — no single airport dominates the operator's departure pattern. Many low-cost airlines operate from a portfolio of bases, each serving its own surrounding region without connecting traffic feeding through.

Hybrid Networks

Many modern airlines combine elements of both models. A hybrid carrier might run hub operations at one or two large airports while operating significant point-to-point service from smaller bases. The Routes Database makes these mixed structures visible: high concentration at one or two airports plus a more distributed pattern across the remainder of the network.

Key Metrics for Route Network Analysis

A handful of metrics derived from route data form the foundation of most network analysis:

Each of these metrics can be computed directly from the AirLabs Routes Database. A single API call returns the route inventory for an airline, after which the metrics are derived through application-side aggregation.

Identifying an Airline's Hubs

Hub identification is the most common analytical task for new route data users. The approach is straightforward: fetch all routes for an airline, group by departure airport, count routes per airport and sort by count. The airports with disproportionately high route counts are the carrier's hubs.

GET https://airlabs.co/api/v9/routes?airline_iata=LH&_fields=dep_iata,arr_iata&api_key={KEY}

A typical response contains hundreds or thousands of route records. Aggregating by dep_iata produces a distribution showing each airport's share of the carrier's departures:

[
  { "airport": "FRA", "route_count": 287 },
  { "airport": "MUC", "route_count": 195 },
  { "airport": "HAM", "route_count": 22 },
  { "airport": "DUS", "route_count": 18 }
]

For Lufthansa, Frankfurt and Munich together account for the dominant share of routes — clear hub identification. Compare this with a low-cost carrier like Ryanair, where the equivalent analysis produces a much flatter distribution across many European bases, none dominating.

Combining this analysis with the Airports Database — which provides the connections field showing total destinations from each airport — allows analysts to validate hub identification against airport-level data. A true hub for an airline should also be among the most-connected airports in the carrier's home country.

Route Frequency and Capacity Analysis

Beyond the existence of a route, the frequency of operation determines actual capacity. The Routes Database days field encodes which days of the week each route operates — as an array of values 1 through 7 (Monday through Sunday). A route operating all seven days represents far more capacity than a route operating twice a week.

Analyzing frequency distributions across an airline's network reveals which routes are core operational priorities and which are secondary or seasonal. Core routes typically operate daily (days: [1,2,3,4,5,6,7]); business-traveler-focused routes often peak Monday and Friday with reduced weekend service; leisure routes show weekend-heavy or seasonal patterns.

Cross-referencing route frequency with the Schedules API for specific dates provides the next level of detail — exact departure times and any short-term variations in the published schedule.

Competitive Density on Routes

A central question for many route analyses is: how many airlines operate each route? Routes served by a single carrier function as effective monopolies, often with premium fare pricing. Routes served by 2–3 carriers form duopolies and competitive markets. Routes served by 5+ carriers represent highly contested markets with aggressive pricing.

Querying the Routes Database by city pair, without an airline filter, returns every carrier operating between the two airports:

GET https://airlabs.co/api/v9/routes?dep_iata=LHR&arr_iata=JFK&_fields=airline_iata,days&api_key={KEY}

The response shows every airline-route combination on the city pair. London Heathrow to JFK typically returns multiple operators — British Airways, American Airlines, Virgin Atlantic, Delta and others — confirming this as a highly competitive transatlantic route. Comparing this with a route like Heathrow to a smaller European city reveals fewer competitors and indicates a less contested market.

Aggregating competitive density across an entire network — counting routes by number of competing carriers — produces a profile of the airline's exposure to competitive pressure. High exposure (most routes have 3+ competitors) implies fare pressure; low exposure (many monopoly routes) implies pricing power.

Route Network Comparison Across Carriers and Countries

The Routes Database supports cross-carrier comparison through the same query pattern, varying the airline_iata filter:

GET https://airlabs.co/api/v9/routes?airline_iata=BA&api_key={KEY}
GET https://airlabs.co/api/v9/routes?airline_iata=AF&api_key={KEY}
GET https://airlabs.co/api/v9/routes?airline_iata=LH&api_key={KEY}

Running parallel queries for British Airways, Air France and Lufthansa produces three separate route inventories that can be compared on the metrics above. Side-by-side analysis reveals each carrier's distinct network strategy — different hub concentrations, different international versus regional balances and different competitive positions on specific routes.

For country-level network analysis, combine the Routes Database queries with the Airlines Database country_code filter to identify every airline of a country, then query routes for each. Aggregating across the result builds a complete national route network profile — total routes flown by carriers of the country, total destinations served and the most heavily concentrated airports.

Combining Route Data with Other AirLabs Datasets

Route data becomes substantially more useful when combined with the other AirLabs reference databases. Several integration patterns appear repeatedly in network analyses:

Route + Airport Infrastructure

Cross-referencing routes with the Airports Database adds airport context to each route: country, timezone, runway count, total connections and city. This enables analysis like "average route length by departure country" or "destinations served per regional airport," neither of which is possible from route data alone.

Route + Aircraft Type

Linking a route to the aircraft type usually operating it requires combining route data with the Fleets Database and Real-Time Flights API. For each route, query the airline's fleet to identify which aircraft types are eligible, then check the live tracking feed to see which type is currently in service. This is the foundation of capacity analysis — a route operated with an A380 represents radically different capacity than one operated with an A320.

Route + Live Operations

The Schedules API provides actual departures and arrivals for any airport, allowing analysts to validate the route database against current operations. Routes that exist in the database but show no recent activity may be seasonal, suspended or about to be discontinued. Routes that show in schedules but are absent from the route database may be new additions.

Use Cases for Flight Route Data

Network analysis based on flight route data serves several industries:

Aviation Consulting and Strategy

Consulting firms preparing market entry studies, route launch business cases, network design recommendations and capacity strategy assessments need route data as the foundational input. The Routes Database provides the network baseline against which proposed changes can be modeled.

Equity Research and Investment Analysis

Analysts covering airlines use route network metrics — hub concentration, competitive exposure, international scope — to model revenue potential, predict margin pressure and benchmark carriers against each other. Network breadth and density correlate with revenue stability; concentration in highly competitive markets correlates with margin pressure.

Regulatory and Antitrust Analysis

Civil aviation authorities and competition regulators use route data to evaluate market concentration, identify routes where consolidation has reduced competition, and assess proposed merger effects. The route-level view of competitive density is the standard tool for these assessments.

Airport Operations and Marketing

Airport authorities use route data to identify gaps in their network — destinations not served from the airport but in demand — and to prepare cases for attracting new carriers. Route data also supports passenger forecasting by route, capacity planning and slot allocation analysis.

Aviation Research and Academia

University researchers studying network topology, transportation economics, urban accessibility and air transport policy use route data as primary inputs to academic models. The structured nature of the dataset — every route as a discrete record with consistent fields — supports rigorous comparative analysis.

Travel Technology and Search

Travel applications use route data to identify which airlines fly between any two cities, supporting "available carriers" displays in search results, route comparison features and itinerary planning that goes beyond direct flights into one-stop and multi-stop possibilities.

Practical Patterns for Network Analysis

If you are working with route data for analytical or research purposes, several patterns improve both efficiency and accuracy:

• Cache route data at the airline level. Routes change slowly. Cache an airline's full route inventory locally and refresh weekly rather than re-querying for every analysis.
• Use field selection. For network metrics, you typically need only airline_iata, dep_iata, arr_iata and days. Passing _fields with only these fields keeps responses small and aggregations fast.
• Run cross-carrier comparisons in parallel. When comparing networks across multiple airlines, issue queries in parallel and aggregate the results in your application layer rather than running sequential calls.
• Validate against operational data. A route in the database is a scheduled service. Cross-reference with the Schedules API for the current operational window to confirm the route is actively operating. Routes that no longer appear in current schedules may have been suspended.
• Account for codeshare relationships. A route operated by one airline and codeshared by another appears in both airlines' route inventories. For competitive density analysis, deduplicate by airport pair and identify the operating carrier. See our Codeshare Flights guide for details.
• Combine with Airlines Database for context. Each route is operated by an airline that has its own characteristics — fleet size, average aircraft age, IOSA registration. These attributes add interpretive context to raw route counts.

Flight Route Data for Developers and Analysts

If you are building a route network analytics product, an airline benchmarking dashboard, a market intelligence platform or a research database focused on global aviation networks, the AirLabs API provides the structured route data and complementary reference databases needed.

Supported API Features

Our Developer API allows you to create a custom experience for your users and increase the value of your product:

• Routes Database with airline, departure airport, arrival airport, days of week, duration and terminal data.
• Filtering by airline (airline_iata, airline_icao), by departure airport (dep_iata), by arrival airport (arr_iata) or by combinations.
• Airlines Database with carrier details and operational scope for joining with route data.
• Airports Database for adding country, timezone, connections and infrastructure context to routes.
• Fleets Database for linking routes with the aircraft types operating them.
• Real-Time Flights API to validate route data against current operational activity.
• Schedules API for cross-checking against actual departures and arrivals.
• Countries Database for adding national context when analyzing routes by country.
• Field selection via _fields for efficient querying of large route inventories.
• JSON, XML and CSV response formats.

You can try it right now without any obligation! Get a free flight API plan and see for yourself that we have exactly the data you need!

If you need more information, don't hesitate to contact us. We are always happy to chat with our customers and are sure to find a customized solution for each request.