Hub or point-to-point? What the schedule tells you

You can tell a lot about how an airline thinks by reading its schedule. Not the mission statement — the actual SSIM file. Hub-and-spoke and point-to-point are two answers to the same question — how do you connect a lot of places with a limited number of aircraft? — and each leaves a distinct fingerprint in the data. Once you know what to look for, you can read the philosophy straight off the schedule.

The two philosophies, briefly

Hub-and-spoke funnels traffic through a small number of hub airports. Most flights touch a hub; passengers connect there rather than flying direct. It trades a connection (and time) for reach: a hub with 60 spokes offers a huge number of city pairs from a modest number of routes.

Point-to-point flies passengers directly between the cities they want, hub or no hub. It trades connectivity-per-aircraft for simplicity and speed: fewer connections, faster journeys, but every market needs its own flying.

Most real carriers are a blend. The interesting question isn’t “which one” — it’s “how much of each, and where.” The schedule answers it three ways.

Signal one: banks at the hub

The clearest tell is temporal. A hub operates in banks (also called waves): a cluster of inbound flights lands in a tight window, passengers connect, then a cluster of outbound flights departs. Arrivals bunch, then departures bunch, several times a day.

  arrivals    ▁▁▇▇▇▁▁▁▁▁▇▇▇▁▁▁▁▁▇▇▇▁▁
  departures  ▁▁▁▁▇▇▇▁▁▁▁▁▇▇▇▁▁▁▁▁▇▇▇
              06   09    12    15   18
              └ bank 1 ┘└ bank 2 ┘└ bank 3 ┘

(Illustrative. Each pairing of an arrival wave feeding a departure wave is a connecting bank.) Plot departures and arrivals per hour at a station and a hub shows this pulse plainly. A point-to-point station doesn’t: its movements spread evenly across the day because nobody’s waiting to connect — the aim is to fly the aircraft, not to gather passengers.

The gap between an arrival wave and the departure wave it feeds isn’t arbitrary, either: it has to clear the airport’s minimum connect time. Bank spacing is connection engineering made visible.

Signal two: station degree

The second tell is structural. Treat the network as a graph — stations are nodes, routes are edges — and count each station’s degree: how many distinct destinations it connects to.

• A hub has very high degree. A handful of stations connect to dozens or hundreds of others; the rest of the network has low degree.
• A point-to-point network spreads degree more evenly. No single station dominates; many stations connect to a moderate handful.

Rank every station by degree and the shape of the ranking tells you the philosophy. A steep cliff — a few stations far above the rest — is hub-and-spoke. A gentle slope is a mesh. The busiest stations by degree are the carrier’s operational centres of gravity, whatever the marketing calls them.

Degree tells you where the network concentrates. Banks tell you whether it’s built to connect there. You want both.

Signal three: the shape of the route graph

Draw the graph and the two philosophies look different at a glance. Hub-and-spoke is a star (or a few overlapping stars): dense spokes radiating from a centre, few edges between the spoke tips. Point-to-point is a web: edges between many pairs, no obvious centre.

The connection window ties it together. In a hub network, count the viable same-station connections — inbound flights whose arrival, plus a realistic connect time, lets a passenger make an outbound to somewhere new. A hub manufactures thousands of these one-stop city pairs from a few hundred routes. That multiplication is the hub-and-spoke value proposition, and it’s measurable directly from the schedule once you apply a connection window.

Read this	Hub-and-spoke	Point-to-point
Movements over the day	Banked (waves)	Spread evenly
Station degree ranking	Steep — a few dominate	Flat — evenly shared
Route graph shape	Star / radial	Mesh / web
One-stop connections	Many (manufactured)	Few (incidental)

Why it’s worth reading

Network philosophy isn’t academic. It drives where capacity concentrates, how resilient the schedule is to a delay (a banked hub propagates disruption; a point-to-point network isolates it), and how a carrier competes. When schedules get rebuilt — and in a year of tight capacity and long aircraft backlogs, they’re rebuilt often — knowing the shape you’re starting from is the first step in changing it.

And a caution the OD matrix post makes too: all of this reads the planned network. It shows how the carrier has chosen to connect places, not how many passengers actually flow through — that needs traffic data the schedule doesn’t carry.

Where it fits

Reading philosophy off a schedule used to mean writing your own graph code over a parsed feed. SSIM Toolkit builds the views for you: a hub analysis that ranks stations by departures, arrivals, and connectivity; a network map and OD matrix that show the route graph and where it concentrates; and connection analysis that measures the one-stop markets a hub creates — all on your own machine, over your own schedule.

Point it at a carrier and the star-or-mesh answer is a glance away. More on the SSIM Toolkit product page.