Why India's Regional Carriers Can't Plan Like IndiGo (and Shouldn't Try)

Why India's Regional Carriers Can't Plan Like IndiGo (and Shouldn't Try)

There's a template for how you're supposed to run an airline in India. High utilisation, single fleet type, dense trunk routes, sell the sandwich. IndiGo wrote it, executed it better than anyone, and now controls more than 60% of the domestic market.

So when a regional carrier sits down to plan its network, the gravitational pull is obvious: do what IndiGo does, smaller. Chase utilisation. Add frequencies on the busiest routes you can reach. Benchmark your CASK against theirs and feel bad about it.

This is a mistake, and it's worth being precise about why.

Scale changes the physics, not just the size

IndiGo's playbook works because of things a small fleet structurally cannot replicate:

Utilisation arithmetic. With 350+ aircraft, a broken rotation gets absorbed. Spare aircraft exist. With 8 aircraft, chasing 13 block hours a day means your schedule has no slack, and one AOG morning cascades through your entire network for two days. High utilisation on a small fleet isn't the same strategy at a smaller scale. It's a different, riskier strategy wearing the same clothes.

Cost benchmarking is a trap. A regional carrier flying ATRs or E-jets on 350 km sectors will never see trunk-route CASK, because short sectors carry fixed per-departure costs (airport charges, turnaround, climb fuel) over fewer available seat kilometres. Comparing your CASK to IndiGo's tells you nothing except that you fly shorter sectors with smaller aircraft. The relevant question is whether your RASK-CASK spread per departure works on the specific markets you serve, and that's invisible in fleet-average numbers.

Trunk routes are a losing battlefield. On BOM-DEL you compete against a carrier whose marginal cost of adding a frequency is lower than yours will ever be. The regional opportunity is precisely the markets where the big airline's economics don't work: city pairs too thin for a 180-seat A320 to serve profitably, where a 70-seater with the right timing owns the market by default.

What the regional game actually is

The regional carriers that survive are playing a different game, and it rewards different capabilities:

1. Market selection over market share. On thin routes, the win isn't outcompeting anyone. It's picking city pairs where you're the only sensible option and the demand pool covers your per-departure economics. That requires understanding demand at a resolution national statistics don't provide: catchment behaviour, rail substitution on sub-400 km sectors, day-of-week patterns of a tier-2 business community.

2. Timing as the product. On a monopoly thin route, your fare isn't really competing with another airline. It's competing with the Vande Bharat and an overnight bus. A 7 AM departure that enables a same-day return to the metro is a fundamentally different product from a 2 PM departure on the same sector, and it can command a fare the afternoon slot never will. For a regional carrier, schedule design is product design.

3. Rotation architecture over route lists. With a small fleet, you don't really choose routes. You choose rotations: closed loops of 4 to 6 sectors that an aircraft flies in a day. One weak sector inside an otherwise strong rotation might be worth keeping; a decent sector that forces an awkward overnight might not. Evaluating routes one at a time, the way a big carrier's route development team does, actively misleads a small operator. The unit of decision is the rotation.

4. UDAN with eyes open. Subsidised regional connectivity routes have been a graveyard for operators who treated Viability Gap Funding as profit rather than as partial compensation for structurally hard economics. The subsidy expires. If the route hasn't built self-sustaining demand by then, you've spent three years training a market to expect fares that vanish. The carriers using UDAN well model the post-VGF economics on day one and pick routes where organic demand can plausibly grow into the gap.

The tooling gap nobody talks about

Here's the uncomfortable part. Everything above requires more analytical precision than trunk-route planning, not less. Thin markets punish estimation error brutally: overestimate demand by 15% on BOM-DEL and you're mildly annoyed; do it on a 70-seat regional sector and the route is dead.

Yet the analytical tooling in the industry is priced and designed for the carriers that need it least. Sabre and Amadeus planning suites assume a planning department of twenty. A regional carrier's network team is often two people and a spreadsheet, making rotation-level bets that each represent 10% of the fleet.

That's the gap we started Aviation Oasis to close. AvioIQ reconstructs departure-level economics for Indian carriers from DGCA-validated data and simulates network decisions before they're flown, at a price point built for a 10-aircraft operator rather than a 300-aircraft one. Not because small carriers deserve charity, but because the next decade of Indian aviation growth is in exactly the markets they serve. India plans to have 200+ operational airports by 2030-and change; someone has to connect them, and it won't be widebodies.

The regional carriers that make it won't be the ones that imitated IndiGo hardest. They'll be the ones that understood their own economics at a resolution the giants never needed to.

Aviation Oasis builds AvioIQ, an aviation intelligence platform for network planning and strategy teams, with departure-level digital twin economics and multi-agent simulation calibrated for the Indian market.