Airline load factor: connect traffic, capacity and yield
An airline can fill more of its seats while generating less passenger revenue per unit of capacity. Load factor measures occupied capacity; it does not include ticket yield. Combine traffic, available capacity and revenue per passenger-kilometer before interpreting fuller aircraft as stronger operating economics.
Match distance-weighted units
IATA defines revenue passenger kilometers, available seat kilometers and passenger load factor as RPK divided by ASK. These are industry traffic definitions rather than accounting profit measures. They weight flights by distance, so they cannot be replaced by unweighted passenger counts without changing the question.
Record whether the company reports kilometers or miles and whether scheduled, charter or regional operations are included. Passenger revenue and RPK should cover the same operating population. Total company revenue may include cargo, loyalty arrangements and ancillary items that need a separate bridge.
Hypothetical fuller aircraft
Assume a fictional airline has 100 million ASK, 80 million RPK and passenger yield of 0.10 per RPK. Load factor is 80% and passenger revenue is 8 million. In a second equal-length period, ASK rises to 110 million, load factor reaches 85%, and RPK becomes 93.5 million. Yield falls to 0.08, producing passenger revenue of 7.48 million.
| Traffic worksheet | First period | Second period |
|---|---|---|
| ASK, millions | 100 | 110 |
| RPK, millions | 80 | 93.5 |
| Load factor | 80% | 85% |
| Passenger yield | 0.10 | 0.08 |
| Passenger revenue, millions | 8.00 | 7.48 |
| Passenger revenue per ASK | 0.080 | 0.068 |
The worksheet identity is passenger revenue = ASK × load factor × passenger yield, provided the inputs share scope. More occupied capacity has not offset the lower yield in this invented case. It does not establish what happened at any real airline or explain the cause of the price change.
Investigate the route mixture
Longer routes can change distance-weighted traffic even when passenger counts barely move. A shift between domestic and international operations can change average yield, costs and seasonality. Split the traffic table into meaningful route groups where the issuer provides the data, then aggregate RPK and ASK before dividing.
Do not average two route load factors equally when their capacity differs. Nor should an increase in average trip length automatically be called stronger demand. It can reflect network design, frequency changes or the loss of short routes. Keep the operating explanation separate from the measured distance effect.
Connect revenue with cost evidence
Passenger revenue per ASK is not total revenue per ASK. Compare the appropriate revenue measure with a compatible cost-per-ASK series and explain fuel, lease and currency treatment. A fuller aircraft may require lower fares or additional connections, while flight disruptions can increase costs despite strong bookings.
For a claim about capacity discipline, observe whether ASK growth is matched by traffic and sustainable revenue yield. For a claim about pricing, inspect comparable routes and fare mix rather than group load factor. If only group data are published, limit the conclusion to group observations.
The next review should keep the same units, reporting window and network coverage. Schedule changes and aircraft groundings can alter the denominator; a high load factor caused by canceled capacity is a different mechanism from increased travel demand. The worksheet tests those alternatives without forecasting ticket prices or investment returns.
FAQ
Does an 85% load factor mean 85% of flights were full?
No. It is a distance-weighted ratio of passenger traffic to available capacity. Individual flights can have very different occupancy.
Can total revenue divided by RPK be called passenger yield?
Only if that is the issuer’s stated definition, with its scope explained. Otherwise isolate passenger revenue and keep cargo and other revenue separate.