Istanbul Sabiha Gökçen International Airport (SAW) flight compensation: delays and cancellations
Short answer: The first distinction at Istanbul Sabiha Gökçen International Airport is geographical: SAW is not an EU or EEA departure airport. On the documented SAW facts, EU261 may reach the outbound leg when an eligible European airline operates it; in the opposite direction, departure from a covered European airport supplies territorial scope. On the documented SAW facts, local rights in Türkiye remain a distinct route, so the claim should identify which framework covers which sector.
Free eligibility check
Check your case in the form
Enter your route, date and type of disruption. We will check whether your case qualifies for a claim under EU 261/2004 or UK261.
What happened to your flight?
Claim up to €600 for a delayed or cancelled flight.
Choose the situation that applies to your flight:
This SAW assessment uses sources checked on 12 September 2026 and intentionally leaves unstable flight numbers out of the analysis.
At SAW, do not separate the operator from the route. In this SAW claim, a ticket involving Pegasus Airlines and European cities can have a different coverage answer from one involving international low-cost operators and the Middle East. On the documented SAW facts, verify both combinations in the original itinerary before deciding which regime or amount to claim.
Airport-specific facts at Istanbul Sabiha Gökçen International Airport
A generic city guide misses the operating character of SAW: it is a major low-cost and regional gateway on Istanbul's Asian side. In this SAW claim, its passenger cases can involve Pegasus Airlines, AJet and international low-cost operators, serving European cities, Türkiye, the Caucasus, North Africa and the Middle East.
SAW and IST are far apart; an airline-proposed substitution can create substantial ground-transport and timing consequences.
The named SAW markets explain likely claim patterns without promising current daily service. Confirm both the itinerary and aircraft operator for the individual travel day.
The local coordinates of a SAW claim
Do not address a SAW file from memory of the logo. For travel through SAW, even where Pegasus Airlines or international low-cost operators appears on the itinerary, the e-ticket's operator disclosure and replacement boarding pass provide the stronger answer.
The network examples, from European cities to the Middle East, create different legal paths through SAW. On the documented SAW facts, record origin, endpoint and every ticketed connection instead of reducing the case to the name of the city containing the airport.
A clear Istanbul Sabiha Gökçen International Airport case begins with identifiers rather than adjectives: IATA code SAW, city Istanbul, country Türkiye, operator and date. That format makes the factual request harder to misunderstand.
Before submission, compare these local facts with the airline's own disruption notice. Any mismatch about SAW, the performing carrier or final destination should be resolved in the chronology, not left for the claims team to guess.
For this airport, the working record links SAW, Pegasus Airlines, international low-cost operators, European cities and the Middle East only where the passenger's own ticket and day-of-travel documents support that connection.
Place the SAW flight on the right legal side
| Airport position: SAW | Performing airline | Rule to apply first |
|---|---|---|
| EU-area origin and SAW endpoint | Carrier shown for the service | EU261 normally applies from the European departure |
| Outbound SAW journey into covered Europe | Qualifying European airline | EU261 can apply because of the operator |
| European city reached from SAW | Local or other non-Carrier within EU261 inbound scope | Do not assume EU261; test the applicable local regime |
| Linked sectors on a ticket through SAW | Identify the sector causing the loss | Contract, direction and operator must be read together |
Treat every sector touching SAW as a real flight rather than a city-pair label. Applied to SAW, outbound and return legs are separate, and a partner code cannot convert one operator into another.
A route that passes the SAW territorial test still needs a compensable event. For SAW, separate the arrival threshold, notice period and extraordinary-circumstances evidence from the preliminary scope result.
Final destination versus separate tickets at SAW
Separate tickets between SAW and IST do not become one connection merely because a search engine presented them as a single journey. Ticket number sequence, PNR and baggage destination help separate a protected transfer at SAW from a passenger-created self-connection.
For a one-ticket journey through SAW, retain the scheduled endpoint time and record when a door opened there. When recording the SAW event, neither runway landing nor the first leg's departure delay supplies the complete comparison.
Turn the SAW event into evidence
Build the SAW record while information is still visible. For SAW, Airport displays can establish what passengers were told, but the airline's own notice is more useful for its asserted cause and replacement offer.
- In the SAW record, the written cancellation, denied-boarding or rerouting choice, plus proof of when it was communicated;
- a downloaded SAW e-ticket receipt showing passenger names, ticket numbers and who was due to operate each sector;
- boarding cards for both the planned SAW service and each substitute flight accepted later;
- timestamps for the first delay, cancellation message, new departure and final door opening on the booking through SAW;
- the first operational explanation, later updates and visible SAW status board before those records disappear;
- When recording the SAW event, a care-cost schedule listing date, supplier, item, currency and reason for each purchase made while stranded.
For SAW, keep care receipts separate from consequential losses such as prepaid hotels at the destination. The legal basis and evidence burden are not the same.
Four different remedies can follow at SAW
The familiar EUR 250/400/600 structure belongs to a covered EU261 journey. For an excluded SAW-origin flight, identify the local legal amount and currency before making a demand.
Keep three ledgers for SAW: the statutory amount, the unused ticket or replacement transport, and reasonable care expenses. A carrier's weather defence to the first does not automatically erase the others.
Before purchasing a costly substitute from SAW, ask the airline for rerouting in writing and preserve its refusal or silence. That sequence makes a later reimbursement demand much stronger.
A two-flight SAW thought experiment
Suppose a locally operated flight from SAW arrives four hours late in the EU. For the journey involving SAW, the delay length would satisfy one EU threshold, yet the non-European origin and operator can prevent EU261 from applying at all.
A family using Istanbul Sabiha Gökçen International Airport should run this analysis per passenger. On the documented SAW facts, infants without a separate fare, reward tickets and voluntary seat surrender may require additional examination.
The operating airline comes first at SAW
Send the first SAW demand to the operating airline, not automatically to the airport, booking platform or marketing carrier. For SAW, identify the flight, booking, passengers, final delay, remedy and evidence in separate paragraphs.
If the airline rejects the SAW case without a satisfactory factual explanation, consider the role of Türkiye Directorate General of Civil Aviation. In the SAW record, enforcement, alternative dispute resolution and a court claim are different routes, so check what outcome that body can actually order.
For the journey involving SAW, the airport coverage hub helps test another origin; the delay guide explains final arrival, the cancellation guide separates refund from rerouting and the compensation calculator applies once scope is established.
Status of the rules on 12 September 2026
As at 12 September 2026, existing passenger-rights rules still control the SAW examples below. When recording the SAW event, the Council's 2026 amendment is not backdated and does not apply until the specified period following publication has elapsed.
The practical response is to document the Istanbul Sabiha Gökçen International Airport event now and use the existing submission route promptly; an adopted reform does not pause time limits already running.
FAQ
Is a departure from SAW automatically covered by EU261?
No; the airport lies outside EU261's departure area. For the journey involving SAW, coverage may still arise through a qualifying European carrier, without replacing the local legal analysis.
Where should I send a claim concerning Istanbul Sabiha Gökçen International Airport?
For travel through SAW, name the airline that was due to perform the sector, even if another company sold the ticket. Preserve the SAW e-ticket line that proves this identity.
Can my ticketed endpoint matter more than the first SAW delay?
In this SAW claim, a common PNR, ticket sequence and through-checked baggage can help prove one journey, but inspect the full contract. With separate bookings, each SAW sector normally stands alone.
Can the airline reject everything by citing weather at SAW?
Under EU261 or UK261, the exceptional-circumstances defence concerns the lump sum. It does not automatically cancel the passenger's separate refund or assistance analysis.
Which documents strengthen a SAW claim?
Keep more than the mobile boarding pass. On the documented SAW facts, download the e-ticket receipt, preserve each sector coupon, photograph live airport information and record the final arrival.