Flight details
Maintenance Flight Disruptions
Primary disruptions and affected downline flights grouped by tail chronology

Display boundary: Only the approved maintenance delay and cancellation codes are shown. For multi-code delays, only the code marked
root_cause = 1 in FTT is evaluated and displayed. Code-2 rotational delays may cross actual tails when the child tail matches the structured por_tail_no of a strictly earlier code-46 primary, or when an otherwise unresolved row has a reason-tail whose verified immediately previous routing flight is a code-41 primary. A consequential cancellation starts a new originally disrupted line when its immediate same-tail predecessor was not cancelled and had no maintenance delay, unless that predecessor is an additional-revenue flight and the preceding same-tail flight was cancelled; that cancellation remains downline in the existing disruption line. Unresolved relationships are listed separately.Primary disruptions—
Promoted consequential—
Downline flights—
Unresolved flights—
Lookback anchors—
| Date/Departure | Flight | FTT Link | Carrier | Tail | Route | Disruption Code | Disruption Reason | Downline |
|---|
Unresolved selected flights
Flights that cannot be classified or attached without inventing a tail, chronology, source status, or earlier primary.
| Resolution Issue | Date/Departure | Flight | FTT Link | Carrier | Tail | Route | Disruption Code | Disruption Reason |
|---|