IATA Delay Codes Explained: Passenger's Quick Reference
IATA delay codes are the two-digit identifiers airlines use to classify each late departure. Learn the groups, your EU261 rights, and what traders track.
What IATA delay codes are, how they work, and why they matter — whether you are filing for EU261 compensation or pricing a position in a flight-delay event market.
What IATA Delay Codes Actually Are — and Why Every Flight Has One
Every non-on-time departure must be coded. That is the operating rule most passengers never encounter. IATA delay codes are two-digit numeric identifiers, standardised in the IATA Airport Handling Manual (AHM 730), that airlines log against each flight to record the primary cause of a delay or cancellation.
The system was designed for operational intelligence: a network operations team reviewing a carrier’s fleet performance can filter by code, isolate recurring technical failures, quantify handling disruptions by hub, and allocate rectification resources. Delay codes are the structured vocabulary that makes comparative operational analysis possible across carriers, airports, and regulators.
For passengers, the significance is different. The code logged against your delayed flight determines, in broad terms, whether the airline has a viable extraordinary-circumstances defence under EU Regulation 261/2004 — and therefore whether you are owed financial compensation. For event-contract market participants, the same codes are the attribution layer that gives flight-delay data its analytical signal.
Inside the Code: Format and Group Structure
The IATA AHM 730 code set runs from 00 to 99, organised into bands of roughly ten codes per operational category. Each code has a defined primary meaning; airlines can record multiple codes on a single flight when causes overlap.
| Code Range | Operational Category |
|---|---|
| 11–18 | Passenger and baggage (late check-in, late boarding, excess baggage) |
| 21–28 | Cargo and mail (documentation, late delivery to aircraft) |
| 31–39 | Aircraft and ramp handling (loading, unloading, fuelling, catering, cleaning, ground equipment) |
| 41–48 | Technical / aircraft and maintenance (defects, scheduled maintenance, unscheduled maintenance, aircraft change) |
| 51–58 | Damage to aircraft / automated equipment failure (de-icing, contamination, EDP failure) |
| 61–69 | Flight operations and crew (crew shortage, late crew, flight plan issues) |
| 71–77 | Weather (adverse conditions at origin, destination, or en route) |
| 81–89 | Air Traffic Management and airport/governmental authorities (ATFM slot restrictions, airport capacity, route closures; sub-codes 85–87 cover immigration, customs, and security) |
| 91–96 | Reactionary / knock-on (late inbound aircraft or crew from a previous sector) |
The groupings above follow the canonical IATA AHM 730 taxonomy as documented by Eurocontrol’s Aviation Intelligence Unit. Sub-codes within each band add specificity — code 41 (aircraft technical defects) differs from code 43 (unscheduled maintenance) — but the leading digit is usually sufficient for rights and market-analysis purposes.
One nuance worth noting: codes 00–05 are reserved for each airline’s own internal classification purposes and are not part of the standardised AHM 730 taxonomy visible in external datasets.
The EU261 Divide — Airline-Controlled vs Extraordinary-Circumstance Codes
No distinction in IATA coding cuts sharper for EU passengers than the line between delays the airline owns and delays it can attribute to extraordinary circumstances.
Airline-controlled delays arise from events within the carrier’s reasonable operational control. The 41–48 technical/maintenance band is the clearest example: a maintenance defect that should have been detected during routine servicing, a component failure attributable to deferred maintenance, or a scheduled aircraft change the airline could have mitigated. The 61–69 operations/crew band — late crew due to scheduling failure, insufficient standby coverage, flight planning issues — similarly reflects operational choices. Ramp handling delays (31–39, covering loading, fuelling, catering, and ground-equipment failures) and damage or automated-equipment failures (51–58) also fall within the airline’s sphere of control. EU courts have consistently held that technical faults discovered during the regular course of an aircraft’s operation do not constitute extraordinary circumstances unless caused by a hidden manufacturing defect or sabotage.
Extraordinary circumstances under EU261 are events genuinely outside the airline’s control and unavoidable even if all reasonable measures were taken. The code groups most reliably associated with this defence are:
- 71–77 (Weather): severe conditions at origin, destination, or en route. Not every weather code succeeds — airlines must demonstrate conditions actually prevented safe departure, not merely that they were suboptimal.
- 81–89 (ATFM and governmental authorities): air traffic flow management restrictions issued by bodies such as Eurocontrol, as well as airport-authority actions including immigration, customs, and security measures (sub-codes 85–87). ATFM constraints are external impositions on the carrier and represent the most consistently upheld basis for extraordinary circumstances in EU case law. Security incidents and government restrictions that ground an airport similarly fall within this band.
For EU261 treatment of strikes — which straddles airline-controlled and extraordinary territory depending on whether the action involves the airline’s own staff or third-party ATC/ground crew — see Airline Strikes and EU261 Compensation. For the full extraordinary-circumstances framework and the case law that defines its outer limits, see EU261 Extraordinary Circumstances: The Complete Guide.
The reactionary band (91–96) is contested ground. A knock-on delay caused by a preceding sector held by ATFM may carry the extraordinary-circumstances character of that upstream restriction — but the airline must establish the unbroken causal chain. Case outcomes vary, and alternative dispute resolution bodies apply different thresholds.
Reading Your Rights: How the Delay Code Changes Your Options
If your flight arrived more than three hours late and you are within EU jurisdiction or travelling on an EU carrier, the delay code is the document that most directly supports or undermines your EU261 position.
What each group signals in practice:
- Codes 41–48 (technical/maintenance) or 61–69 (crew/operations): strong indicator that compensation applies. The airline cannot credibly invoke extraordinary circumstances unless a secondary external cause is simultaneously on record. Ramp handling codes (31–39) and damage or equipment failure codes (51–58) similarly point to airline-controlled events where compensation is typically owed.
- Codes 71–77 or 81–89 (weather / ATFM and governmental): the extraordinary-circumstances defence is well-grounded. Compensation is unlikely, though the airline’s care obligations — meals, accommodation, rebooking — remain in force regardless.
- Codes 91–96 (reactionary): investigate the root cause. If the inbound delay was itself technical or operational, the extraordinary-circumstances chain is broken and compensation may apply from the originating disruption.
Request the delay code in writing. Provide your flight number, departure date, and airport, and ask specifically for the IATA delay code(s) under AHM 730 classification. If the code the airline provides contradicts its stated reason for denying compensation, that contradiction is the basis for escalation to your National Enforcement Body or an accredited alternative dispute resolution scheme.
For independent support navigating this process, our comparison of AirHelp, Compensair, and ClaimCompass covers how these services access and use delay-code data.
Why Delay Codes Matter for Event-Contract Traders
For market participants, IATA delay codes are the attribution infrastructure that turns flight-departure data into a tradeable signal.
Event contracts on flight delays resolve on a binary framework: a contract specifies whether a flight departs or arrives on schedule, is delayed beyond a defined threshold (commonly 15 minutes or more), or is cancelled. Settlement is determined by independently verifiable departure and arrival records. The outcome — On Time, Delayed, or Cancelled — is objective.
The delay-code layer adds analytical depth. Understanding which code groups are statistically prevalent on a given route, carrier, or hub across a given season provides informational signal:
- Code-group prevalence by operation type: short-haul turnaround-intensive routes accumulate reactionary codes (91–96) faster than long-haul point-to-point services. Routes served by older narrowbody fleets show higher technical-code frequency (41–48) than those on newer-generation aircraft, particularly in winter.
- Duration profiles by code group: technical delays (41–48) tend toward heavier right tails than ATFM holds (81–89), which are bounded by slot windows. Reactionary delays are bounded by the upstream sector’s delay. Duration distribution matters for event contracts with differentiated outcome tiers.
- Seasonal patterns: ATFM codes concentrate during peak summer operations at congested European hubs; weather codes peak in northern-hemisphere winter. Historical code data at the airport and route level is aggregated in Eurocontrol CODA publications and commercial OTP datasets — the foundation on which systematic delay-probability views can be built.
On Gaduin, event contracts on flight delays, train delays, and vessel arrivals settle in USDT through a peer-to-pool mechanism. Settlement relies on objective outcome data from the same flight-status infrastructure that delay codes feed into. Traders who understand the attribution chain — from IATA delay code to OTP statistic to contract settlement — are better placed to price risk, apply position-sizing discipline, and assess the informational conditions that move market probabilities.
This content is for informational purposes only and does not constitute financial or legal advice. Trading event contracts involves risk; positions may settle against you.
How to Find Your Flight’s Delay Code
Delay codes are operational records held by airlines. They are not printed on boarding passes or booking confirmations, but they can be obtained through several routes.
Ask the airline directly. Write to customer relations — email creates a paper trail — and request the IATA delay code(s) under AHM 730 for your specific flight. Provide your booking reference, flight number, departure date, and departure airport. Most reputable carriers respond within 14 days; EU carriers subject to enforcement have regulatory obligations to respond to substantiated disruption queries.
Use the National Enforcement Body process. If the airline disputes your EU261 position, your country’s National Enforcement Body — typically the civil aviation authority — can compel production of delay records. This route is slower but creates a formal regulatory record.
Commission a claim service. Firms such as AirHelp and ClaimCompass access delay-code data through industry channels and identify the applicable code as part of their assessment process — useful if you prefer not to negotiate directly with the airline.
Access commercial OTP data. For institutional or trading purposes, structured delay-code data is available from Eurocontrol’s CODA publications, national regulator filings, and commercial flight-data providers including OAG and FlightAware. These datasets aggregate code frequency at the route, carrier, and airport level across defined periods — the analytical layer used to build systematic delay-probability views.