EU261 in plain terms
EU261 is an EU law that can require airlines to pay fixed compensation after certain disruptions. The amount depends on flight distance and the delay length at arrival, not on your ticket price. For example, short-haul flights can fall into the €250 bracket, while longer routes can reach €400 or €600. Many people mix up “delay at departure” with “delay at arrival,” and that mistake changes the outcome.
Compensation is usually discussed in three tiers: €250, €400, and €600. The tiers map to distance bands and whether the delay reaches the legal thresholds. For most passengers, the key number is 3 hours: if arrival is delayed by 3 hours or more, the claim may qualify, subject to the airline’s “extraordinary circumstances” defense. Skip the screenshots of your boarding pass. They rarely prove the arrival delay.
Workflows around claims have also changed. Airlines and claim platforms increasingly route requests through online forms, then attach automated “cause codes” to the case file. That means your evidence and wording must match what the system expects, or the claim can stall for weeks. Learning trends mirror this: more travelers use structured checklists and templates, then ask for document-level feedback before submitting.
EU261 claims often hinge on causation. The airline may argue the disruption came from events outside its control, like severe weather or air traffic management constraints. Evidence can include ATC logs, maintenance records, and operational reports, but passengers rarely see the full file. That gap is why the same delay can lead to different outcomes across routes and carriers.
Where people go wrong
People often assume the compensation amount depends on how late the flight felt. The law focuses on arrival delay, and it measures that against the scheduled arrival time. If you track only “departure delay,” you can end up claiming the wrong bracket. That mismatch also affects whether the airline’s internal review marks the case as eligible.
Another common error involves “extraordinary circumstances.” Many travelers treat this as a generic excuse, but the airline must connect it to the specific disruption and show it could not have been avoided even with reasonable measures. The airline’s explanation may sound plausible, yet it still needs to align with the event timeline. If your documentation contradicts the airline’s timeline, the case can move faster.
System interactions matter. Your claim form feeds into a triage process, then a human reviewer checks the distance, the scheduled times, and the airline’s cause code. If you enter the wrong flight number or date, the system can attach the wrong disruption record. That can lead to a denial that looks final, even when the underlying facts might support a claim. You can see this in practice when a “denied” email arrives before any request for missing documents.
Skip the “I heard it was weather” narrative. It rarely survives document review. You need a timeline: scheduled departure, actual departure, scheduled arrival, actual arrival, and any rerouting details. Without that, the reviewer cannot test the airline’s causation story.
How to decide €250, €400, or €600
Start with arrival delay
Measure delay at arrival, not at departure. Use the airline’s official schedule and the actual arrival time shown on your itinerary or arrival notification. If the arrival delay reaches the legal threshold, your case moves to the next step. If it does not, the compensation claim may fail even when the trip felt badly disrupted.
Arrival delay is the gate. Departure delay is noise. That one distinction drives many denials.
When you calculate, use the scheduled arrival time for the same flight number and route segment. If your flight was rerouted, the “arrival” reference can become more complex, and you may need to compare the final destination arrival against the original scheduled arrival. Keep the timestamps consistent with the timezone used in your documents, or you’ll create an avoidable arithmetic dispute.
Use the distance bands
EU261 compensation tiers align with flight distance bands. The €250 tier typically applies to shorter routes, while €400 and €600 apply to longer routes. The exact distance cutoffs depend on the legal framework and how the route is categorized. If you guess the distance, you risk placing the claim in the wrong bracket.
Distance decides the tier. Delay decides eligibility.
In practice, you can compute distance using the great-circle distance between departure and arrival airports. Many travelers use online distance calculators, but you should cross-check the airports used in your booking. If your itinerary includes a stop, the relevant segment can differ from what you expect, and the claim may depend on the final destination segment.
For a concrete example, a flight from London to a mid-range European destination often lands in the €250 or €400 range depending on the distance band. A transcontinental route within the EU context can push into the higher tier. The exact bracket still depends on the distance calculation method and the legal classification.
Check the airline’s cause
Ask what the airline says caused the disruption, then test whether it fits the “extraordinary circumstances” concept. The airline’s explanation should connect the event to the timing of the flight disruption. If the airline cites an event that does not match the timeline, the claim can gain traction.
Extraordinary claims need evidence. Vague explanations stall.
Look for cause codes in the airline’s email or claim portal responses. Some airlines use internal categories that map to weather, ATC, strikes, or technical issues. Technical problems can be treated differently depending on whether they relate to routine maintenance or an event outside normal operations. If the airline blames “technical,” request clarification on what failed and why it qualifies.
Side note: if you’re using a claim template, version it. I’ve seen people reuse a 2023 template against a 2026 portal that asks for different fields, and the mismatch slows review.
Document the timeline cleanly
Build a one-page timeline with four core times: scheduled departure, actual departure, scheduled arrival, actual arrival. Add rerouting details if you changed airports or flight numbers. Attach boarding pass scans only if they show the flight number and date; otherwise, they add clutter.
Use one source for times. Pick the itinerary email.
If you have multiple documents, keep them consistent. For example, if your itinerary shows “scheduled arrival 18:40” but your arrival notification shows “arrived 21:05,” record both and note the timezone. If you later submit a claim, the reviewer can verify your numbers quickly.
Also capture proof of communication. If you received a cancellation notice, a delay SMS, or a gate change alert, save it. Those messages can help establish when the airline informed you, which sometimes matters for how the airline frames the disruption.
Claim with a structured packet
Submit a claim packet that matches what reviewers can check. Include flight number, date, route, booking reference, and the arrival delay calculation. Add a short explanation that ties your facts to the legal criteria: arrival delay threshold and distance tier.
Skip long essays. Use bullet points.
Many online forms accept limited text, so compress your argument into a few lines. If the portal asks for “reason for claim,” state the arrival delay length and the distance tier you believe applies. Then attach your timeline and supporting documents. If the portal supports file uploads, name files with dates, like “2026-10-12_arrival_delay.pdf.”
Opportunity cost matters here. If you spend 3 hours drafting and uploading, that time competes with other tasks like studying for a certification or applying for a job. If your case is weak on arrival delay or distance, the time cost can outweigh the likely payout.
Know what you might not get
EU261 compensation is not automatic. The airline can deny based on extraordinary circumstances, and some cases settle for less after review. Also, compensation does not cover every cost you might have incurred, like all hotel expenses, unless another legal basis applies.
Assume partial outcomes. Plan for friction.
If you pursue reimbursement for expenses, keep receipts and note which costs relate to the disruption. But don’t mix expense reimbursement with the fixed compensation claim in a way that confuses the reviewer. Separate the fixed compensation request from any separate cost claims, if the platform supports it.
Some passengers also confuse EU261 with travel insurance. Insurance may cover additional costs, but it follows its own terms and deductibles. If you file both, keep records consistent so you don’t create contradictions.
Track progress and deadlines
After submission, monitor the case status and keep copies of everything you send. If the airline requests missing documents, respond quickly with the exact items requested. Delays often come from missing fields rather than from legal disagreement.
Follow the portal timestamps. They matter.
Deadlines vary by country for filing and by the legal route you use. Check the relevant limitation period for your residence or the departure/arrival jurisdiction. If you’re unsure, ask a qualified legal professional rather than guessing, because missing a deadline can end the claim regardless of merits.
Side observation: some portals show “submitted” but never send an email confirmation. Screenshot the submission page, then store it with the case reference number.
Case examples
Example 1: €250 bracket attempt
A passenger flies from an EU departure airport to another EU destination on a short-haul route. The itinerary shows scheduled arrival at 14:10, but the plane lands at 17:05, creating a 2 hour 55 minute delay at arrival. The passenger believes the delay at departure was longer, but the arrival delay does not reach 3 hours. The airline denies the claim because the arrival threshold is not met, even though the trip felt late.
Lesson: the arrival gate decides eligibility. The distance tier only matters after that.
Example 2: €600 bracket with technical dispute
A passenger’s long-haul EU route is delayed at arrival by 4 hours. The flight distance falls into the highest distance band, so the passenger requests €600. The airline replies that a technical issue occurred and labels it “extraordinary,” but the explanation lacks a clear link to why the event could not have been avoided. The passenger submits a timeline and asks for clarification on the specific failure and maintenance context, then the case moves to review rather than immediate denial.
Lesson: causation needs a timeline match. “Technical” needs specifics, not just a label.
Distance and delay decision checklist
| Step | What to check | Your evidence | Why it matters |
|---|---|---|---|
| 1 | Arrival delay length | Scheduled vs actual arrival times | Eligibility often hinges on reaching the 3-hour threshold |
| 2 | Flight distance band | Departure/arrival airport pair used for distance | Distance bands map to €250, €400, or €600 |
| 3 | Airline’s cause explanation | Email/portal response with reason and timeline | Extraordinary circumstances can reduce or block compensation |
| 4 | Consistency across documents | Same flight number/date in every file | Inconsistent inputs can trigger wrong case matching |
Common mistakes
Using departure delay
Why it happens. Travelers track the moment they felt late, then copy that number into the claim form. Many airline notifications highlight departure time changes, which trains the habit.
Impact. The reviewer checks arrival delay against the legal threshold, so your claim can fail even when the trip was badly disrupted.
How to avoid it. Calculate delay from scheduled arrival to actual arrival using the same timezone source across documents.
Guessing the distance tier
Why it happens. People estimate distance from geography or route length, then pick a compensation tier that “feels right.”
Impact. A wrong tier request can slow review, and some portals auto-reject mismatched tiers.
How to avoid it. Use the airport pair from your booking and compute distance with a consistent method, then record the inputs you used.
Accepting the airline’s label
Why it happens. The airline’s email often uses short cause labels like “technical” or “weather,” and readers stop there.
Impact. The legal question depends on whether the event qualifies and whether it matches the timeline. A label without a timeline link can weaken the airline’s position.
How to avoid it. Ask for clarification tied to the specific flight segment and timing, and keep your timeline ready for comparison.
Submitting without a timeline
Why it happens. People focus on receipts and inconvenience stories, then forget the four core times.
Impact. Reviewers spend time verifying basics, which increases the chance of a delay or a request for more information.
How to avoid it. Put scheduled arrival, actual arrival, and the computed delay length at the top of your packet.
FAQ
How do I calculate the delay for EU261?
Use the scheduled arrival time for your original flight and compare it to the actual arrival time at the final destination airport. Do not use departure delay as the main number. If your flight was rerouted, the “final destination” reference can shift, so compare the arrival at the destination you ultimately reached against the original scheduled arrival for that destination. If your documents show different timezones, convert consistently before subtracting.
When does a 2-hour delay qualify?
A 2-hour arrival delay usually does not meet the common EU261 threshold for fixed compensation. The law uses specific delay cutoffs, and the most frequently cited one is 3 hours at arrival for many cases. Some situations involve different thresholds depending on the disruption type and route classification, so you should check the exact scenario for your flight. If you only know the departure delay, you may be under- or over-estimating eligibility.
What if the airline says “extraordinary circumstances”?
The airline can deny or reduce compensation if it argues the cause qualifies as extraordinary and could not have been avoided with reasonable measures. “Extraordinary” is not a blanket permission to deny; the explanation should connect to the specific event and the timing of your flight. Ask for details that let you compare the airline’s timeline with your own. If the airline provides only a generic label, request more specific information.
Does EU261 cover hotel and meal costs?
EU261 fixed compensation targets the disruption itself, not every expense you incurred. The law also includes duties around care (like meals and accommodation) in certain circumstances, but those are separate from the fixed compensation amount. If you want reimbursement for specific costs, check whether your claim is framed as fixed compensation, care, or another legal basis such as contract terms or consumer protection rules. Keep receipts, but do not mix everything into one unclear request.
Can I claim if my flight was cancelled?
Cancellation claims follow related but distinct rules from delay claims. The compensation tier still depends on distance, and the timing of notice can affect eligibility. If you received notice close to departure, the airline’s obligations can differ from cases where you were informed earlier. Gather the cancellation notice time, the scheduled departure time, and the actual rebooking or alternative arrival details. Then match those facts to the cancellation criteria.
Author's Insight
Most EU261 disputes turn into a document-matching problem, not a “who suffered more” problem. Your best leverage comes from clean arrival-delay math and a timeline that aligns with the airline’s stated cause. When a portal asks for short fields, a one-page packet beats a long narrative. If you feel stuck, rewrite your claim around the four core times and the distance tier inputs, then submit again.
Key takeaways
- Calculate delay at arrival, then check the 3-hour threshold logic.
- Use the airport pair from your booking to place the flight in the correct distance band.
- Treat “extraordinary circumstances” as a timeline claim, not a slogan.
- Submit a structured packet with scheduled/actual arrival times and consistent flight details.
- Track deadlines and portal requests, because missing fields often causes delays.