When risk first became visible
Earliest breached core MCT checkpoint in the filtered flights.
Where the bottleneck sits
Primary process signal based on event sequence; cause codes are not available.
Flights requiring attention
Click any row for the complete flight → ULD → AWB evidence trail.
| Risk | Flight | Scheduled | Airline / type | Risk first visible | Bottleneck | FBL · RCS · Build · UWS | Load | Departure outcome |
|---|
Recurring risk by airline
Operating airline is the default. Main carrier can be selected where the source distinguishes the two.
Airline performance detail
Click a row to return to the risk board filtered to that airline.
| Airline | Flights | UWS breach | Build issue | RCS issue | Median dep. delay | Weight on UWS-late flights |
|---|
Cargo destinations with recurring exposure
These are AWB cargo destinations, not aircraft sector endpoints.
| Destination | Flights carrying cargo | AWBs | Chargeable weight | Weight on UWS-late flights | Late RCS AWBs |
|---|
Measured process chain
Counts are flight-level unless stated otherwise; filtered scope applies.
How late UWS presents
Separates upstream build/acceptance signals from inferred flight-close handoff cases.
UWS timing vs departure outcome
Each point is a real flight. Association is shown; no delay-reason codes exist to prove causation.
Flights with the strongest measured readiness chain
Sorted by late UWS, upstream breaches, cargo weight and actual departure impact.
| Flight | Airline | Evidence chain | Late Build/Bulk ULDs | Late RCS AWBs | UWS delta | Departure delay | Weight |
|---|
Data coverage
What is directly available in the supplied files.
Known data gaps
These prevent a complete operational cause model.
- Flight route endpoint
- Not present. “Destination” is the AWB cargo destination and a single flight may carry cargo for many destinations.
- 90% general acceptance
- No direct event exists. The cockpit shows a clearly labelled proxy using manifested pieces and last-piece-received timestamps.
- Delay reason / root-cause code
- Not present. “Flight-close handoff” is an inference only when UWS is late and all measurable upstream core milestones are on time.
- Resources and locations
- No staffing, forklift, build-station, dolly, VOP, loading-start or live ULD-location data is supplied.
- Live status
- The files are historical. A production cockpit would require event streaming or frequent refresh.
Applied MCT rules
Targets are taken directly from the supplied Export Cargo Flow MCT pages.
| Milestone | Freighter / Cargo | Passenger | How used |
|---|
Data quality signals
Visible as review flags; records are not silently deleted.
Interpretation guardrails
- Risk state
- Rule-based against core milestones: Final FBL, RCS, Build (Build/Bulk only), and UWS. It is not a trained prediction model.
- Recovered
- An upstream core milestone was late or missing, but UWS was on time.
- Critical
- UWS was late or missing at the flight-close checkpoint.
- Actual departure
- The outbound master field “Flight.ATA” is treated as actual departure because it exactly matches “ATA/ATD” on every matched non-null export row.
- Volume matching
- Flight numbers were normalized only for leading zeros (for example 6E-022 to 6E-22). All shared-period export rows matched after this normalization.
- Scope
- Export Cargo/Freighter and Passenger flights only. Truck, Transit out and Transfer out are excluded because the supplied MCT does not define their rules.