Your Route P&L Is Lying to You

Your Route P&L Is Lying to You

Ask a network planner whether a route is profitable and you'll get a number. One number. Revenue minus cost, divided over a quarter, presented in a monthly review deck with a green or red cell next to it.

That number is an average. And averages are where bad routes hide.

The same route is four different businesses

Take a typical metro-to-tier-2 sector in India. Say it runs 21 weekly departures. The route P&L says it's marginally positive. Fine. Keep it.

Now break it open by departure:

• The 6:40 AM bank feeder runs 88% load with strong corporate yield. It's carrying the route.
• The 11:15 AM rotation runs 61% load against a competitor's better-timed frequency. It loses money every single day it operates.
• The Friday evening departure prints cash. The Tuesday version of the same flight doesn't.
• The last rotation of the day exists mostly to reposition the aircraft, and its "profitability" depends entirely on how you allocate ownership cost across the day.

One route. Four completely different economic realities. The route-level average blends them into a single mediocre number that tells you nothing actionable. You can't fix "the route." You can fix the 11:15.

This is the whole argument for departure-level economics, and it's surprisingly rare in practice below the top tier of carriers. IndiGo can afford a large planning department and expensive tooling. A regional carrier with 8 to 12 aircraft usually cannot, so decisions get made on quarterly route averages and planner intuition.

Why the averages problem is worse for regional carriers

Small fleets amplify everything. When you operate 300 departures a day, one badly-timed rotation is noise. When you operate 40, it's 2.5% of your entire network sitting in the wrong place.

Regional networks also have structurally higher variance between departures:

Thinner demand pools. A tier-2 city pair doesn't have the depth of BOM-DEL. Demand by day-of-week and time-of-day swings hard, so the gap between your best and worst departure on the same route is wider than it would be on a trunk route.

Aircraft utilisation dependencies. On a small fleet, every departure is a link in a chain. A weak rotation often survives review because "the aircraft needs to get to X anyway." That logic is sometimes right. But nobody checks whether restructuring the whole rotation would beat patching it, because the tools to test that don't exist in-house.

Cost allocation distortions. Spread fixed ownership and crew costs evenly across departures and your early-morning high-yield flights look worse than they are while your late-night repositioning flights look better. The allocation method quietly decides which flights look profitable. That should worry you more than it probably does.

What departure-level reconstruction actually involves

The reason most carriers don't do this isn't that nobody thought of it. It's that reconstructing true per-departure economics is genuinely hard. You need to bring together, per individual departure:

1. Fuel burn by stage length, aircraft variant, and realistic block time (not the padded schedule number)
2. Airport and navigation charges at actuals, which in India vary widely by airport operator and slot timing
3. Crew cost mapped to actual pairing patterns, not a flat hourly average
4. Ownership/lease cost allocation that reflects how the departure contributes to utilisation rather than a naive per-flight split
5. Revenue decomposed by booking class mix, point-of-sale, and connection contribution, since a feeder flight's fare revenue understates its network value

We built AvioIQ's Digital Twin to do exactly this reconstruction and validated it against DGCA-reported actuals for Indian carriers. The honest finding from that work: on almost every network we've modelled, roughly a fifth of departures are subsidising the rest, and a visible tail of departures loses money persistently in ways the route-level view never surfaces.

The decisions that change

Once you can see economics per departure, a different class of questions becomes answerable:

• Which specific frequencies should move, not which routes should close?
• Is the weak Tuesday departure fixable with a retime, or is the demand simply not there on Tuesdays?
• What does the repositioning flight actually cost the network, and is there a rotation structure that eliminates it?
• If we add one aircraft, which departures does it enable, and what do those specific departures earn?

None of these are exotic questions. Planners ask them constantly. The difference is answering them with reconstructed economics instead of instinct.

The route P&L isn't useless. It's just the wrong resolution for the decisions that matter. Routes don't make money. Departures do.

Aviation Oasis builds AvioIQ, an aviation intelligence platform that reconstructs departure-level economics for airline networks, validated against actuals. If you plan a network on route averages today, we should talk.