Logistics · Freight operations
Which arrivals will run late, ranked for a freight desk two to four hours out
Two scores for flight-linked freight: one the evening before from the timetable, one on the day once the aircraft lands on its previous leg. Tested on three months of US domestic flights the models never saw.
Executive summary
Scoring each arrival when its aircraft lands on the previous leg makes 73% of a freight desk’s alerts real, against 62% for the inbound-delay rule desks use today.
Situation
Freight desks learn a flight is late when the status page changes, often after the truck is waiting or the customer has a delivery window. A list where most flagged flights land on time gets ignored.
Approach
Two LightGBM scores on 7.08 million US domestic flights: a plan score the evening before from the timetable, and a day-of score once the aircraft lands on its previous leg. Trained January to September, tested October to December.
Result
At a list of 10% of flights, 73% of day-of alerts are real and the list catches 45% of all late arrivals. The day-ahead score is weaker (AUC 0.654) and suits booking choices, not customer promises.
The business problem
A freight forwarder’s control tower watches the flights its shipments are booked on. When a flight runs late, a connection can be missed and a customer has to be told, but the team often learns of it only when the aircraft fails to land on time. Forwarders and airlines that combine schedules, previous-leg delays and airport conditions say the value is in hours of warning, which leaves time to rebook or set expectations.
I built two scores: one the evening before from the timetable, and one on the day once the aircraft lands on its previous leg, and measured how many late arrivals each puts in the top of the alert list two to four hours out.
- Team
- An ops desk of 2 to 5 per shift, plus drivers or ramp crews on rosters
- Scale
- 200 to 3,000 flight-linked shipments a day
- Systems
- CargoWise or a forwarding system, airline and airport flight status feeds, email or Teams alerts
- Constraint
- Alerts only matter if few enough to act on; a desk ignores a list where most flagged flights land on time
What was built
Two scores. A plan score runs the evening before from the timetable: route, hour, airline, which leg of the day the aircraft is on, and its planned turnaround. A day-of score reruns as each aircraft lands on its previous leg and adds how late it was. The desk sees a ranked list, sized to what it can act on.
Results
On the day: most late arrivals are already late on the previous leg
What the desk gets
Tested on 1,765,279 flights from October to December 2024, after training on January to September. 16.3% of test flights arrived late.
| Flights flagged | Route × hour history | Plan model (day ahead) | Inbound-late rule | Day-of model |
|---|---|---|---|---|
| Top 5% | 27% | 46% | 64% | 96% |
| Top 10% | 26% | 36% | 62% | 73% |
| Top 20% | 24% | 29% | 40% | 48% |
| Top 30% | 23% | 26% | 31% | 37% |
Share of flagged flights that arrived late, at each list size. Higher is better: it is the share of alerts that are worth acting on.
At a list of the top 10% of flights, 73% of day-of alerts are real, against 62% for a rule that flags any flight whose aircraft is 15+ minutes late inbound. That list catches 45% of all late arrivals. At the top 5%, 96% of alerts are real.
| Method | When it runs | AUC (95% CI) | PR-AUC |
|---|---|---|---|
| Route × hour history | Day ahead | 0.612 (0.610–0.615) | 0.223 |
| Plan model (a day ahead) | Day ahead | 0.654 (0.652–0.656) | 0.315 |
| Inbound late > 15 min rule | On the day | 0.720 (0.718–0.723) | 0.423 |
| Day-of model (+ inbound delay) | On the day, 2 to 4 hours out | 0.800 (0.798–0.802) | 0.627 |
The day ahead is harder
From the timetable alone the plan score reaches AUC 0.654, against 0.612 for each route and hour's own history (gain 0.040 to 0.043, 95% CI). At the top 10% it flags 36% real late arrivals, against 26% from history. It is useful for choosing which bookings get a wider window, not for promising a customer anything.
Why flights run late
| Signal (day-of model) | Share of model gain |
|---|---|
| Inbound delay on the previous leg | 60.7% |
| Planned turnaround (minutes) | 15.7% |
| Scheduled departure hour | 5.2% |
| Leg of the day | 4.3% |
| Origin airport | 4.2% |
| Destination airport | 3.8% |
| Airline | 2.4% |
| Month | 2.0% |
Data and method
- Source
- US Bureau of Transportation Statistics, Reporting Carrier On-Time Performance, monthly files for 2024 (public domain)
- Size
- 7,079,061 flights, 15 airlines, 348 airports; 96,315 cancelled and 17,499 diverted, excluded from scoring
- Split
- Out of time: train January to September (1,500,000 of 5,199,968 flights used), settings chosen on August to September, test October to December
- Audit
- 20,152 flights with no aircraft registration (no rotation features); 836 duplicate rows; 73% of flights linked to the aircraft's previous leg
Four methods: each route and departure hour's late rate from training months; a rule that flags a flight when its aircraft is more than 15 minutes late inbound; a LightGBM plan model on timetable fields; and a LightGBM day-of model adding the inbound delay. Confidence intervals from 200 bootstrap redraws of 400,000 test flights.
A random split, which mixes days from the test months into training, puts the plan model at AUC 0.719 instead of 0.654. It learns which days were bad. The figures above use the out-of-time split, which is what a live desk would see.
Assumptions and limitations
- US domestic flights: the Australian regulator (BITRE) publishes on-time figures monthly by route, not per flight, so an Australian desk needs its own status-feed history to refit
- The day-of score assumes the inbound delay is known when the aircraft lands on its previous leg; a status feed with a few minutes’ lag is enough
- Freight moved and what an alert is worth are not in the data; list sizes should be set from the desk’s own cost of a missed truck against a wasted call
- Cancellations are excluded; they need a separate alert
- Late is the airline definition, 15+ minutes; a freight cut-off may need a different threshold
What a freight desk would do next
- Weeks 1 to 2: collect six months of flight status history for the routes in use from the status feed
- Weeks 3 to 4: refit, agree a list size with the desk lead, connect alerts to the TMS
- Next two months: run day-of alerts on half the shipments and compare missed truck slots and customer complaints
- Then: add the plan score to booking rules for the most time-critical freight
Technical depth
Each aircraft is followed through its day by registration: leg number, planned turnaround from the previous scheduled arrival, and the actual delay on that previous leg. The day-of model is trained with the inbound delay as known; the plan model never sees it. Rounds are chosen by early stopping on August and September, then refit on all training months.