AI for Air Cargo and Freight Aviation
Air cargo is a revenue management business with a physical constraint, and its defining data problem is that a booking is a statement of intent rather than a fact.
The central question in air cargo capacity management is how much of what has been booked will actually arrive at the airport, and the answer differs systematically by forwarder, lane, commodity and season.
AI for air cargo covers capacity and revenue management, show-up and no-show prediction, load planning and unit load device build-up optimisation, ground handling and turnaround analytics, special cargo handling, and rate and lane pricing.
Bookings, show-up rates and overbooking
Cargo bookings are made speculatively and cancelled or reduced routinely. Airlines respond by overbooking, and the quality of that decision depends entirely on how well the show-up rate is understood for the specific booking rather than in aggregate.
- Show-up varies systematically by forwarder. Some book speculatively as a matter of practice and their patterns are learnable from your own history.
- Commodity, lane and season all matter. Perishables behave differently from general cargo; peak season differs from trough.
- Both volume and weight constrain, and the binding one changes. Dense cargo hits weight limits first; light bulky cargo hits volume. Overbooking must respect whichever binds on that flight.
- Offload cost is asymmetric and reputational. A shipment offloaded is a customer relationship damaged, and it costs more than an empty position.
- Model at booking level, not flight level. Aggregate show-up rates conceal exactly the variation that makes overbooking safe or dangerous.
Overbook on the constraint that actually binds
Air cargo has two capacity constraints — volume and weight — and which one binds depends on the cargo mix on that specific flight. An overbooking model tuned on volume will over-accept dense cargo and produce weight-limited offloads; one tuned on weight leaves volumetric capacity unsold. Modelling both, per flight, against the predicted mix is the difference between an overbooking system that improves load factor and one that generates offloads.
Load planning and build-up
Unit load device build-up is a packing problem with rules
Fitting shipments into containers and pallets, respecting weight distribution, dangerous goods segregation, temperature requirements and destination sequencing, is a constrained packing problem with well-established method — and with rules that are non-negotiable.
Segregation rules are hard constraints
Dangerous goods compatibility and segregation requirements are safety rules, encoded as inviolable, never as preferences. The same applies to temperature-controlled and live animal handling requirements.
Weight and balance is aircraft-specific and safety-critical
Load distribution affects aircraft handling. Optimisation supports the load planner and the final plan is signed by a person with that responsibility — this is not a boundary to automate across.
Build-up decisions are made under time pressure
A recommendation that arrives after the build-up has started is a report. Cut-off timing matters more than marginal optimisation quality, and it should be established before anything is built.
Ground handling, special cargo and forwarder relationships
| Application | Value | The catch |
|---|---|---|
| Turnaround and handling time prediction | High | Ground handler data quality varies enormously by station |
| Special cargo handling compliance | High | Rules are hard constraints; the value is in checking, not deciding |
| Rate and lane pricing | High | Air cargo rates are volatile; regime awareness matters |
| Capacity allocation across forwarders | Moderate | Commercial relationships override optimisation, correctly |
| Damage and irregularity analytics | Good | Patterns by station, handler, commodity and packaging |
| Document and AWB automation | Strong | High volume, structured, immediately measurable |
Forwarder relationships legitimately override the optimiser
Allocating capacity purely on expected yield will cut across long-term forwarder relationships that carry value the model cannot see — volume commitments, reciprocal arrangements, strategic lanes. The right design surfaces the yield trade-off explicitly and lets commercial leadership decide, rather than presenting an allocation as an answer. A capacity model that ignores relationships gets ignored in turn, which is the correct outcome.
How an engagement runs
Show-up modelling at booking level, because it is where the capacity value concentrates.
Scope and cut-off timing
What the capacity and build-up processes can act on, and by when. This decides whether the work is useful.
Data foundation
Bookings joined to flown cargo, by forwarder, commodity, lane and season, with volume and weight both captured.
Build
Booking-level show-up prediction and dual-constraint overbooking, or build-up optimisation with segregation rules encoded.
Trial
Shadow running against current decisions, with offload rate and load factor measured together.
Operation
Retraining as forwarder behaviour and lane mix change, offload rate monitored as a standing control.
What you receive
Higher load factor without more offloads, and build-up plans that respect the rules.
Booking-level show-up model
By forwarder, commodity, lane and season rather than in aggregate.
Dual-constraint overbooking
Volume and weight modelled together, against the predicted mix per flight.
Offload risk management
Asymmetric cost reflected explicitly in the acceptance decision.
Build-up optimisation
Packing with segregation and temperature rules as inviolable constraints.
Handling and turnaround analytics
Station and handler performance, with irregularity patterns identified.
Document automation
Air waybills and manifests, with uncertainty routed rather than guessed.
Is this the right starting point?
Worth being direct. There are situations in air cargo where custom AI work is the wrong spend, and those are listed rather than buried.
Worth doing if
- Overbooking is set by fixed percentages rather than modelled per booking.
- Offloads are frequent and the causes are not analysed by constraint type.
- Load factor is measured on one constraint while the other binds regularly.
- Build-up planning is manual and cut-off pressure produces suboptimal loads.
- Handling irregularities vary by station and nobody has quantified the pattern.
Do something else if
- Booking-to-flown data cannot be joined, so show-up cannot be modelled.
- You want weight and balance sign-off automated. That belongs to the load planner.
- The capacity decision is made commercially regardless of yield modelling.
- Cut-off timing means a recommendation arrives after build-up has begun.
Frequently asked questions
Marked up with FAQPage schema so these answers can surface directly in search results and inside AI assistant responses.
How should we set overbooking levels?
At booking level rather than by fixed percentage, and against both capacity constraints. Show-up rates vary systematically by forwarder, commodity, lane and season, and those patterns are learnable from your own history. Crucially, model volume and weight together — a system tuned on volume will over-accept dense cargo and generate weight-limited offloads, which is the expensive failure.
Can build-up planning be automated?
The packing optimisation, yes — it is a constrained packing problem with established method. Dangerous goods segregation, temperature requirements and destination sequencing are hard constraints encoded as inviolable. Weight and balance sign-off stays with the load planner who carries that responsibility, and the practical constraint is cut-off timing: a recommendation arriving after build-up has started is a report.
Why do our load factors look good but offloads keep happening?
Usually because load factor is being measured on the constraint that is not binding. If you report volumetric utilisation while weight is the limit on dense cargo lanes, the numbers look healthy while shipments get offloaded. Report both, per flight, and analyse offloads by which constraint bound — that alone frequently changes acceptance policy.
Should capacity be allocated purely on yield?
No, and a model that assumes so will be ignored, correctly. Forwarder relationships carry value the optimiser cannot see: volume commitments, reciprocal arrangements, strategic lanes. The right design makes the yield trade-off explicit and leaves the decision with commercial leadership. Presenting an allocation as an answer rather than as evidence is how these systems lose credibility in the first month.
Is ground handling data usable?
It varies enormously by station, which is itself a finding. Where handling and turnaround data is reliable, predicting handling time and identifying irregularity patterns by station, handler, commodity and packaging is valuable. Where it is not, quantifying the data gap is the first deliverable — and it is frequently commercial evidence for a conversation with the handler rather than a modelling problem.
Related verticals
Organisations in air cargo usually share data, buyers or regulators with these. All fourteen are listed on the Transport & Logistics page.
AI for Shipping and Maritime
Voyage optimisation, fuel and emissions, port call planning and container repositioning.
Read more →AI for Customs and Trade Compliance
Classification support, declaration automation and screening — with the EU customs reform timeline mapped.
Read more →AI for Courier and Postal Operators
Sortation and network flow, peak forecasting and address quality — at network scale.
Read more →Tell us what the problem looks like.
Thirty minutes, no charge, no deck. We will tell you whether this is an AI problem, a data problem, or a process problem — and we will say when the honest answer is to buy something rather than build it.