All posts
Transportation
7 April 20267 min read

Load factor vs yield: the two numbers every transport operator should track

Load factor, yield, and the metric that ties them together (RASK). Worked examples, the most common trade-off mistakes, and how the same logic applies to hotels and cruises.

L

Luska Research

Pricing & Yield Team

Load factor and yield are the two numbers every transport operator watches. They sound similar, get conflated constantly, and pull in opposite directions. Understanding the difference — and the metric that combines them — is the difference between a network that looks busy and one that's actually profitable.

The formulas

  • Load Factor (LF) = Revenue Passenger Kilometres (RPK) ÷ Available Seat Kilometres (ASK).
    In plain English: what % of your seats got bums on them.
  • Yield = Passenger Revenue ÷ Revenue Passenger Kilometres (RPK).
    In plain English: how much you got paid per seat-kilometre actually flown.
  • Unit Revenue (RASK / PRASK) = Passenger Revenue ÷ Available Seat Kilometres.
    The metric that combines both. RASK = Yield × LF.

Worked example

A 200-seat aircraft flies 1,000 km. ASK = 200,000. 160 passengers fly the full distance, paying €80 average. RPK = 160,000. Load Factor = 80%. Passenger Revenue = €12,800. Yield = €0.080/km. RASK = €0.064/km. RASK = 0.080 × 0.80 = €0.064 ✓.

Why each one alone is misleading

A 95% load factor sounds excellent — until you realise the operator gave away seats to fill them. A €0.20/km yield sounds excellent — until you realise only 30% of seats sold. Both can mask the same underlying problem: the operator doesn't know what its capacity is actually worth.

82–85%

Industry-typical airline load factor (IATA, 2024)

65–75%

Healthy intercity bus load factor

RASK

The single number that ties both together

The trap of "fill the seat at any price"

It's almost always more profitable to fly with one fewer passenger at a higher fare than to discount that last seat to zero. The marginal cost of carrying one extra passenger is small — but the dilution caused by signalling cheap fares to the booking engine is huge.

How yield managers actually use these

Decisions are framed in trade-offs:

  1. Drop fares to lift LF — only if the LF gain × new yield > old yield. Otherwise you've just filled the plane with cheap revenue.
  2. Hold fares to protect yield — only if the LF you'll lose isn't going to permanently shift customers to competitors.
  3. Adjust capacity — bigger or smaller aircraft, additional or cancelled departures — when the LF/yield trade-off on a route consistently sits in the wrong place. This is the slowest lever but often the highest-leverage.

Beyond passenger transport

The same logic applies to any reserved-capacity business:

  • Hotels — Occupancy = LF, ADR = Yield, RevPAR = RASK. Same math, different vocabulary. See what is RevPAR.
  • Cruises — Occupancy × Net Cruise Yield per available passenger cruise day.
  • Trucking and freight — Load factor (cubic utilisation) × Revenue per loaded mile.
  • SaaS and cloud — Seat utilisation × ARPU. Same structure, different industry.

What "good" looks like

  • Trend matters more than level. A 78% LF that's climbing month-over-month with stable yield beats an 88% LF that's falling.
  • Comp set matters more than absolute. A 75% LF on a route where competitors run at 65% is winning. A 90% LF on a route where competitors run at 95% is losing share.
  • Always read RASK alongside. Either of LF or Yield alone can be gamed. RASK can't.

Track LF, yield, and RASK in one view

Luska's transportation dashboard surfaces load factor, yield, and unit revenue per route per departure — with comp-set benchmarks and reprice recommendations attached.

See it for transportation

Pricing tactics, weekly.

One short email every Thursday: a dynamic-pricing tactic, a market signal, and a number worth knowing. No spam.