Diverted Flight Event Contract Settlement: 8 Edge Cases
What happens to a flight delay event contract when a flight diverts? Eight settlement edge cases, from air turnbacks to same-city airports, explained.
A flight can leave the gate on schedule and still end its day somewhere unexpected: a fuel stop in Bangor, a medical landing in Keflavik, or a slow taxi back to the gate it just left. For anyone holding a flight delay event contract on that flight, the question is practical: how does this position settle, and at what moment? New to these markets? Start with how flight delay event contracts work — this article assumes the basics and goes straight to the awkward cases.
Diversions break the clean mental model of “the flight arrives, the delay is measured, the contract resolves.” Sometimes the flight arrives late. Sometimes it arrives somewhere else. Sometimes it arrives nowhere at all. Each path leaves a different trace in official flight data and maps to a different settlement result. This guide walks through the full taxonomy, using the definitions US reporting rules and EU passenger law actually use — not the loose language of airline apps.
What the Data Calls a Diverted Flight
Start with the official definition — it is narrower than everyday usage. US Department of Transportation reporting rules, 14 CFR 234.2, state: “Diverted flight means a flight which is operated from the scheduled origin point to a point other than the scheduled destination point in the carrier’s published schedule.” The regulation even covers multi-leg schedules: for a published A-to-B-to-C routing flown as A-to-C, “the A to B segment is a diverted flight, and the B to C segment is a cancelled flight.”
Two things follow. First, a diversion is a property of where the aircraft actually went, not of what the airline announced. Second, diversion status is recorded per segment — relevant when your contract references one leg of a longer routing.
In the Bureau of Transportation Statistics on-time performance database — the reference dataset for US flights — a diverted flight carries a dedicated indicator, and since October 2008 the record includes the full diversion path: up to five alternate landings, with wheels-on and ground times. How settlement infrastructure consumes data like this is covered in how GADUIN verifies flight delay outcomes; here we focus on what the records mean.
Arrival Time Means Gate-In, Not Wheels-On
Before any edge case, pin down the measurement itself. Official US flight records carry two distinct arrival timestamps: WheelsOn, the moment of touchdown, and ArrTime, the actual arrival time. They are not interchangeable. The BTS glossary defines the second one precisely: “Gate arrival time is the instance when the pilot sets the aircraft parking brake after arriving at the airport gate or passenger unloading area. If the parking brake is not set, record the time for the opening of the passenger door.”
In other words, arrival is an event at the gate, not on the runway. The gap between the two is normal taxi time on a good day — and much worse on a bad one, when a flight touches down and then waits for a gate to open. Disruption scenarios like diversions are exactly when gates are scarce.
Delay measurement follows the gate timestamp. Under 14 CFR 234.2, a flight counts as on-time when it arrives less than 15 minutes after its published arrival time — and “arrives” means the gate event, not touchdown. When you evaluate a contract against its threshold, think parking brake, not runway. Why a market uses a 15-minute, 2-hour, or 4-hour threshold is covered in how to choose a settlement threshold.
Case 1: Diverted, Then Flown On to the Original Destination
The most common diversion shape: the aircraft lands at an alternate airport, takes fuel or resolves the problem, then continues and arrives at the originally scheduled destination. Passengers are hours late, but they get where they were going.
The data captures this cleanly. BTS records DivReachedDest, defined as “Diverted Flight Reaching Scheduled Destination Indicator (1=Yes)”. For these flights the delay lives in a dedicated field, DivArrDelay: “Difference in minutes between scheduled and actual arrival time for a diverted flight reaching scheduled destination. The ArrDelay column remains NULL for all diverted flights.” That footnote is worth rereading — even the delay database treats diversions as a special case, moving the number to a different column.
The settlement logic is straightforward. The flight did arrive at the scheduled destination, so a real gate arrival time exists to compare against the contract threshold. The settlement moment is the final gate-in at the original destination — not the landing at the alternate. A three-hour detour sits far beyond any threshold, so holders of the Delayed side see the market resolve in their favor once arrival data is confirmed. Note the causality: the market settles on the measured arrival delay, not on the diversion label itself.
Case 2: Diverted With No Onward Leg
Now the harder version: the aircraft lands at the alternate, passengers are deplaned, and the flight never continues. It terminates at an airport the contract never mentioned.
Here the record shows a diversion without destination arrival — DivReachedDest is not set, and DivDistance (“Distance between scheduled destination and final diverted airport (miles). Value will be 0 for diverted flight reaching scheduled destination.”) shows how far away the operation ended. There is no gate arrival at the scheduled destination, ever. An arrival-delay comparison has nothing to compare.
This is why GADUIN’s settlement rules treat a diversion as its own event class rather than forcing it into “Delayed”: a terminated diversion cannot be measured as a delay, and the contract terms specify how diversion events are classified. The practical instruction is unglamorous but essential: read the diversion clause in the contract specification before opening the position. The market page shows which outcome the event maps to and when resolution happens; it will not improvise an arrival time that never existed.
Air Turnbacks and Returns to the Gate
Two scenarios look similar from a window seat but differ sharply in the data.
An air turnback: the flight departs, gets airborne, and returns to the origin airport. The BTS glossary handles it explicitly in the departure-time definition: “In cases of an air return, report the last gate departure time before the gate return.” If the aircraft is patched up and re-departs, the flight can still complete, and settlement follows the final gate arrival at the destination, as in Case 1. If it never re-departs, the operation ends with no arrival at the scheduled destination — the same settlement situation as a terminated diversion, resolved by classification rules rather than by an arrival measurement.
A return to gate happens before wheels-off: the aircraft pushes back, taxis, then comes back to the gate — often during long ground holds — and eventually departs. The glossary again: “In cases where the flight returned to the departure gate before wheels-off time and departed a second time, report the last gate departure time before wheels-off time.” The recorded departure is the last one, the flight still operates, and settlement waits for the destination arrival as usual. Ground holds have their own regulatory layer, compared in tarmac delay rules under DOT and EU261, but for settlement purposes a return to gate is just a slow departure, not a separate event class.
Equipment Swaps and Flight Number Changes
A delay contract references a specific operation: carrier, flight number, date, and airport pair. Disruption recovery can quietly change what is flying under that designator — or move the passengers off it entirely.
An equipment swap replaces the aircraft but keeps the flight. The data model is built for this: BTS records tail numbers per operation, and the diversion fields carry a tail number per diverted leg (Div1TailNum, “Aircraft Tail Number for Diverted Airport Code1”) because airlines sometimes substitute aircraft mid-recovery. A swap usually costs time, but the flight’s identity is unchanged: same designator, same record, settlement on its actual arrival.
A flight number change is different. If the airline abandons the original designator and rebooks passengers onto a new flight number, the original operation is typically closed out under the 14 CFR 234.2 definition of a cancellation — “a flight operation that was not operated” — while the replacement flies as a distinct flight the contract never referenced. The contract follows the designator in its specification, not the passengers, so the replacement flight’s punctuality is irrelevant to your position. Before trading around irregular operations, confirm the exact designator and date in the specification — that is the identity the settlement data will be matched against.
A Cancellation Announced After a Diversion
Airlines often announce a “cancellation” after a diversion terminates: the app pushes a notification, the continuation disappears, passengers are rebooked. Does the contract now resolve as a cancellation?
Look at the reporting definition again. 14 CFR 234.2: “Cancelled flight means a flight operation that was not operated, but was listed in a carrier’s computer reservation system within seven calendar days of the scheduled departure.” A flight that departed, flew, and landed somewhere was operated. In the official record it is a diversion, not a cancellation — whatever the notification said. The airline’s message describes your rebooking situation; the data describes the aircraft’s actual operation, and settlement reads the data.
This distinction is why the Cancelled outcome on a delay market is defined by the flight not operating at all, a boundary explored in flight cancellation versus delay event contracts. For a diverted-then-terminated flight, expect resolution under the diversion classification in the contract terms, not under the cancellation branch — and expect the data record, not the push notification, to be the reference.
Early at the Alternate, Late at the Destination
A subtle case that trips up intuition: weather closes the destination, and the flight lands at a nearby alternate ahead of its scheduled arrival time. The aircraft was on the ground somewhere before the scheduled arrival minute. Hours later it completes the short hop and reaches the destination far behind schedule. Which time counts?
The destination one. The alternate landing exists in the record — BTS stores a wheels-on time for each diverted airport — but none of those timestamps is the flight’s arrival. The delay measure, DivArrDelay, is defined against “scheduled and actual arrival time for a diverted flight reaching scheduled destination”, meaning the gate arrival at the airport the contract references. An early touchdown at the wrong airport is operational trivia; the settlement clock runs until the aircraft parks where the schedule said it would. Traders watching a live tracker should resist treating “it landed early somewhere” as an On-time signal. Until the flight is at its scheduled destination gate, the relevant number does not exist yet.
Same City, Different Airport
Metropolitan areas with multiple airports produce the most counterintuitive case. A flight bound for one airport diverts to another airport serving the same city. Passengers shrug and take a longer taxi ride. The data disagrees: the scheduled destination is an airport code, not a city, and landing anywhere else fits the 14 CFR 234.2 definition of a diverted flight.
Passenger-rights law, interestingly, takes the opposite view. EU Regulation 261/2004 defines “final destination” in Article 2(h) as “the destination on the ticket presented at the check-in counter”, and Article 8(3) provides: “When, in the case where a town, city or region is served by several airports, an operating air carrier offers a passenger a flight to an airport alternative to that for which the booking was made, the operating air carrier shall bear the cost of transferring the passenger from that alternative airport either to that for which the booking was made, or to another close-by destination agreed with the passenger.” In other words, EU law thinks in cities and makes the carrier pay for the bus.
Settlement data does not think in cities. If the contract references a specific airport pair and the flight ends at a sibling airport, the record shows a diversion without destination arrival — Case 2 mechanics, however painless the outcome felt to passengers. Check which airport code the market references before assuming a cross-town landing counts as arrival.
A Pre-Trade Checklist for Diversion Scenarios
The eight cases compress into one question: did the flight produce a gate arrival at the scheduled destination airport?
| Scenario | Arrival at scheduled destination? | What governs settlement |
|---|---|---|
| Diverted, continued to destination | Yes, late | Final gate arrival vs. threshold |
| Diverted, terminated at alternate | No | Diversion clause in contract terms |
| Air turnback, re-departed | Yes, late | Final gate arrival vs. threshold |
| Air turnback, never re-departed | No | Diversion/cancellation classification |
| Return to gate, then departed | Yes (usually late) | Final gate arrival vs. threshold |
| Equipment swap, same number | Yes | Same flight identity, arrival vs. threshold |
| New flight number after rebooking | Original flight: no | Original designator’s record |
| Diverted to same-city airport | No (different code) | Diversion clause in contract terms |
Before opening a position on a disruption-prone route, five checks cover most of the risk: read the diversion clause in the specification; confirm the exact designator, date, and airport codes; remember the threshold measures gate arrival, not touchdown; expect announcements and data to disagree, with data winning; and know how resolution and settlement in USDT proceed once the outcome is confirmed, as described in how GADUIN settles contracts in USDT.
Diversions reward traders who read specifications the way reporting rules are written: literally. The flight that “basically arrived” and the flight that arrived are different flights in the data — and the data is what settles.
This content is for informational purposes only and does not constitute financial or investment advice. Trading event contracts involves the risk of loss. U.S. persons are excluded from participation. See gaduin.com/user-agreement and gaduin.com/terms for full terms.