Carriers¶
Start here when you want to see how each carrier is doing overall. These charts help you look at revenue, passenger bookings, and how much of the available capacity is being used.
You can read about the underlying data and how to collect it in Carriers.
Revenue¶
Let’s start with average revenue for each carrier. This is a useful first check when you want to know whether a change to the simulation helped or hurt revenue.
For one run, call
fig_carrier_revenues on a single
SimulationTables object:
summary.fig_carrier_revenues()
To compare runs, use fig_carrier_revenues on a
Contrast object:
contrast.fig_carrier_revenues()
Yield¶
Yield tells us how much revenue a carrier earns for each passenger mile (not available seat mile, only occupied seats count). Looking at it alongside total revenue can help you understand whether a revenue change comes from pricing or from carrying more traffic. The values use your simulation’s currency per mile.
The comparison supports the same orientation, width, and ratio options as carrier revenues.
For one run, call fig_carrier_yields
on a single SimulationTables object:
summary.fig_carrier_yields()
To compare runs, use fig_carrier_yields on a
Contrast object:
contrast.fig_carrier_yields()
Revenue per Available Seat Mile (RASM)¶
RASM stands for revenue per available seat mile. It relates revenue to the capacity offered, so both ticket prices and the number of occupied seats affect the result.
For one run, call fig_carrier_rasm on
a single SimulationTables object:
summary.fig_carrier_rasm()
To compare runs, use fig_carrier_rasm on a
Contrast object:
contrast.fig_carrier_rasm()
Bookings¶
This chart shows average bookings for each carrier. A passenger on a connecting itinerary counts once here, even though that passenger occupies seats on more than one leg.
For one run, call
fig_carrier_total_bookings
on a single SimulationTables object:
summary.fig_carrier_total_bookings()
To compare runs, use
fig_carrier_total_bookings on a
Contrast object:
contrast.fig_carrier_total_bookings()
Load Factor¶
Load factor describes how much of the available capacity is used. The default system measure,
sys_lf, divides passenger miles by available seat miles, so longer flights contribute more to the
result.
Use load_measure="avg_leg_lf" for average leg load factor instead. This version weights all legs
equally, regardless of their length. Both measures are available for comparisons.
For one run, call
fig_carrier_load_factors on a
single SimulationTables object:
summary.fig_carrier_load_factors(load_measure="avg_leg_lf")
To compare runs, use fig_carrier_load_factors on
a Contrast object:
contrast.fig_carrier_load_factors(load_measure="avg_leg_lf")
Local and Connecting Mix¶
Here we can see the percentage of passengers traveling locally (a single leg is their entire itinerary) rather than making a connection. Differences in this mix can help explain why similar numbers of bookings produce different amounts of traffic on the legs.
There are two ways to measure this percentage, which is a ratio of two totals. The numerator is
always the number of local passengers, but the denominator can be either the total number of
passenger legs (leg_pax, the default) or the total number of bookings (bookings). For example,
if you have only two total bookings, one for a single non-stop itinerary and one for a connecting
itinerary with two legs, the local share is 33% if you use leg_pax (one leg has two passengers and
another leg has one, totalling 3) but 50% if you use bookings (1 local booking out of 2 total
bookings).
For one run, call
fig_carrier_local_share on a
single SimulationTables object:
summary.fig_carrier_local_share(load_measure="leg_pax")
To compare runs, use fig_carrier_local_share on a
Contrast object:
contrast.fig_carrier_local_share(load_measure="leg_pax")
Revenue Passenger Miles¶
Available seat miles (ASM) describe the capacity offered: seats multiplied by distance. Revenue passenger miles (RPM) describe the traffic carried: passengers multiplied by distance. This chart shows both for each carrier, averaged over the samples kept after burn-in.
For one run, call
fig_carrier_mileage on a single
SimulationTables object:
summary.fig_carrier_mileage()
To compare scenarios, make this chart once for each result. There isn’t a combined comparison method for this figure.