Demand, Networks and Traffic Types
5 min read
Lesson objectives
- Distinguish passenger, movement, freight and airline metrics in demand analysis.
- Calculate passenger events and distinct people in a defined transfer case.
- Identify missing data before sizing a processing point.
Please sign in to use all the tools
Once you sign in, the reading tools are yours: larger or smaller text, typeface, line spacing, focus mode, highlighting and bold, and notes saved to your account and gathered in My study.
When two teams say “traffic grew by 10%,” ask what each counted. A passenger is counted under a stated statistical definition; an aircraft movement is a take-off or landing; freight measures goods rather than passenger bags. Passenger numbers can rise with unchanged movements if airlines use larger aircraft or fill more seats. Movements can rise without a comparable passenger increase if aircraft become smaller. A capacity decision therefore starts with unit, location, period and traffic type, not one growth percentage.
Distinguish the airport view from the airline view. Airport passenger counts describe use of facilities at one location. Revenue passenger kilometres multiply paying passengers by distance travelled for an airline; available seat kilometres multiply offered seats by distance. Their ratio is passenger load factor. Those metrics help analyse a carrier network, yet alone they cannot explain a security queue at one airport. That queue depends on people arriving in a particular hour and the service capacity there. A long flight can create many passenger kilometres while occupying one gate during its stand time.
Passenger type also matters. An originating traveller generally enters departure processing; an arriving traveller ends at the airport; a transfer passenger connects to another flight. A direct transit passenger who continues on the same service may follow a different local path. Do not assume every passenger uses every processing point: trace the actual journey. In a hub, connecting flights collect and disperse transfer flows. An airport focused on local origin and destination demand can have a different peak pattern despite the same annual total. The label “hub” alone does not determine a schedule or capacity policy.
Suppose 300 arriving passengers in that case connect to listed departures and each appears once in the arrival events and once in the departure events. Distinct people across those events equal 1,200 + 1,200 − 300 = 2,100, assuming no other repeat within the defined data. But public baggage reclaim demand is not automatically 1,200: transfer bags may bypass it. Security capacity likewise depends on whether connecting travellers are screened again under local procedures. The calculation shows why each indicator needs a route map; an annual total cannot substitute for an hourly process peak.
Before comparing two airports, inspect reporting definitions. Datasets may treat regional operations, general aviation or direct transit differently. ICAO distinguishes commercial movements from other movements and excludes passenger baggage from freight; IATA’s carrier measures are not automatically counts for one airport. Label a dashboard measure “departing passengers in the peak hour” or “daily commercial movements,” rather than just “traffic.” If a definition changes between months, rebuild the comparison or flag the limitation. Exact arithmetic using incompatible denominators still produces a bad decision.
Lesson summary
A useful metric names its unit, period and passenger path. Passenger events are not distinct people, airline network metrics or a peak-hour capacity requirement.