IATA Delay Codes Explained: Passenger's Quick Reference

What IATA delay codes are, how they work, and why they matter for an EU261 compensation claim and for pricing a position in a flight-delay event market.

What IATA Delay Codes Actually Are and Why Every Flight Has One

Every departure that isn’t on time has to be coded. Most passengers never hear about this rule. IATA delay codes are two-digit numbers, standardised in the IATA Airport Handling Manual (AHM 730), that airlines log against each flight to record the main cause of a delay or cancellation.

The system was built for airline operations. A network operations team reviewing its fleet can filter by code, spot recurring technical failures, measure handling problems by hub and decide where to put repair resources. Delay codes give carriers, airports and regulators a shared set of terms, so they can compare performance with each other.

For passengers, the code matters for a different reason. The code logged against your delayed flight decides, broadly, whether the airline has a workable extraordinary-circumstances defence under EU Regulation 261/2004, and so whether you’re owed compensation. For event-contract traders, the same codes explain why flights were late, which makes flight-delay data more useful for analysis.

Inside the Code: Format and Group Structure

The IATA AHM 730 code set runs from 00 to 99, in bands of about ten codes per operational category. Each code has a defined main meaning, and airlines can record several codes on one 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)

These groupings follow the standard IATA AHM 730 taxonomy. Individual codes within each band are more specific. For example, code 41 (aircraft technical defects) differs from code 43 (unscheduled maintenance). For passenger rights and market analysis, the first digit is usually enough.

Codes 00–05 are reserved for each airline’s own internal use. They aren’t part of the standard AHM 730 taxonomy you’ll see in external datasets.

The EU261 Divide: Airline-Controlled vs Extraordinary-Circumstance Codes

For EU passengers, the most important split in IATA coding is between delays the airline is responsible for and delays it can blame on extraordinary circumstances.

Airline-controlled delays come from events within the carrier’s reasonable operational control. The 41–48 technical/maintenance band is the clearest example: a defect routine servicing should have caught, a component failure caused by deferred maintenance or a scheduled aircraft change the airline could have managed. The 61–69 operations/crew band also reflects the airline’s own choices, such as late crew from a scheduling failure, too few standby crew or flight planning problems. Ramp handling delays (31–39, covering loading, fuelling, catering and ground-equipment failures) and damage or automated-equipment failures (51–58) are also within the airline’s 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 that couldn’t have been avoided even if all reasonable measures were taken. The code groups most often linked to this defence are:

• 71–77 (Weather): severe conditions at origin, destination or en route. Not every weather code works as a defence. The airline must show the conditions actually prevented a safe departure. Poor weather alone isn’t enough.
• 81–89 (ATFM and governmental authorities): air traffic flow management restrictions from bodies such as Eurocontrol, and airport-authority actions including immigration, customs and security measures (sub-codes 85–87). ATFM restrictions are imposed on the carrier from outside, and EU case law upholds them as extraordinary circumstances more consistently than anything else. Security incidents and government restrictions that shut an airport also fall in this band.

Strikes can count as airline-controlled or extraordinary depending on whether the airline’s own staff or third-party ATC or ground crew walk out. See Airline Strikes and EU261 Compensation. For the full extraordinary-circumstances framework and the case law that sets its limits, see EU261 Extraordinary Circumstances: The Complete Guide.

The reactionary band (91–96) is disputed. A knock-on delay from an earlier sector held by ATFM may share the extraordinary-circumstances status of that earlier restriction, but the airline has to prove an unbroken chain of cause. Case outcomes vary, and alternative dispute resolution bodies apply different standards.

Reading Your Rights: How the Delay Code Changes Your Options

If your flight arrived more than three hours late and you’re within EU jurisdiction or flying with an EU carrier, the delay code is the document that most directly helps or hurts your EU261 claim.

What each group usually means:

• Codes 41–48 (technical/maintenance) or 61–69 (crew/operations): a strong sign that compensation applies. The airline can’t credibly claim extraordinary circumstances unless a second, external cause is also on record. Ramp handling codes (31–39) and damage or equipment failure codes (51–58) also point to airline-controlled events where compensation is usually owed.
• Codes 71–77 or 81–89 (weather / ATFM and governmental): the extraordinary-circumstances defence is well founded and compensation is unlikely. The airline still has to provide care, such as meals, accommodation and rebooking.
• Codes 91–96 (reactionary): look for the root cause. If the inbound delay was itself technical or operational, the extraordinary-circumstances chain is broken and compensation may apply based on the original disruption.

Ask for the delay code in writing. Give your flight number, departure date and airport, and ask specifically for the IATA delay code(s) under AHM 730. If the code contradicts the airline’s stated reason for refusing compensation, you can take that to your National Enforcement Body or an accredited alternative dispute resolution scheme.

If you want help with this process, our comparison of AirHelp, Compensair, and ClaimCompass covers how these services get and use delay-code data.

Why Delay Codes Matter for Event-Contract Traders

For traders, IATA delay codes explain the causes behind flight-delay data, and that makes the data more useful for pricing.

A flight market has three outcomes: On time, Delayed or Cancelled. The line between the first two is a delay threshold fixed when the market opens. On a flight it’s 15 minutes, so arriving more than 15 minutes late is Delayed, and that can’t change afterwards. The market settles on the destination airport operator’s published arrival time against its published schedule. Nobody decides the result. The record does.

Delay codes add detail. Knowing which code groups are common on a route, carrier or hub in a given season tells you something about how a flight is likely to run:

• Code-group prevalence by operation type: short-haul routes with many quick turnarounds build up reactionary codes (91–96) faster than long-haul point-to-point flights. Routes flown by older narrowbody fleets show more technical codes (41–48) than routes on newer aircraft, especially in winter.
• Duration profiles by code group: technical delays (41–48) more often run very long than ATFM holds (81–89), which are limited by slot windows. Reactionary delays are limited by the delay on the earlier sector. How long delays last matters because it decides how far past the 15-minute line a flight is likely to go, and how close it comes to being cancelled.
• Seasonal patterns: ATFM codes cluster in peak summer at congested European hubs, and weather codes peak in the northern-hemisphere winter. Eurocontrol CODA publications and commercial OTP datasets collect historical code data by airport and route, and you can build systematic delay-probability estimates from them.

On Gaduin, event contracts on flight delays, train delays and vessel arrivals settle in USDT. Each market settles on the operator’s own published record for that journey, under terms fixed before trading opened. For a flight, that’s the destination airport operator’s published arrival time against its published schedule. A delay code never settles anything. It explains what the record already shows. Traders who follow the chain from IATA delay code to OTP statistic to settlement are better placed to price risk, size positions sensibly and judge what information is moving prices.

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

Airlines hold delay codes as operational records. They don’t appear on boarding passes or booking confirmations, but you can get them in several ways.

Ask the airline directly. Write to customer relations (email gives you a record) and ask for the IATA delay code(s) under AHM 730 for your flight. Give your booking reference, flight number, departure date and departure airport. Most reputable carriers reply within 14 days, and EU carriers subject to enforcement have regulatory obligations to answer substantiated disruption queries.

Use the National Enforcement Body process. If the airline disputes your EU261 claim, your country’s National Enforcement Body, usually the civil aviation authority, can require it to produce delay records. It’s slower, but it creates a formal regulatory record.

Use a claim service. Firms such as AirHelp and ClaimCompass get delay-code data through industry channels and find the relevant code as part of their assessment. That helps if you’d rather not deal with the airline yourself.

Access commercial OTP data. For institutional or trading use, structured delay-code data is available from Eurocontrol’s CODA publications, national regulator filings and paid aviation-data subscriptions. These datasets show how often each code appears by route, carrier and airport over set periods, which is what systematic delay-probability estimates are built on.