Pegasus Europe-SAW-onward itinerary: final-destination compensation
On a Europe-SAW-onward itinerary, EU261 can follow the protected one-booking journey to the final destination, subject to operating-carrier and case-law limits.
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:
For europe-SAW-onward itinerary, start with the complete ticket rather than one flight number. The decisive record for europe-SAW-onward itinerary combines direction, actual operator, booking structure, final timing, cause and the remedy already offered.
| First check for europe-SAW-onward itinerary | What to record |
|---|---|
| Territorial scope | departure airport and each ticketed destination |
| Responsible airline | the operated-by line, not only the PC marketing code |
| Triggering event | delay, cancellation, denied boarding or contractual change |
| Measured outcome | final arrival, notice date, unused travel or proven loss |
| Carrier explanation | exact wording, time, location and affected aircraft |
Which rules can apply to europe-SAW-onward itinerary
For europe-SAW-onward itinerary, Pegasus Hava Tasimaciligi A.S. is a Turkish carrier, not an EU or UK carrier. That carrier status makes direction central to europe-SAW-onward itinerary, ahead of website language, nationality or purchase currency.
| Flight pattern | Starting point for the legal test |
|---|---|
| EU or EEA airport to Turkiye, operated by Pegasus | EU261 can apply because the flight departs the protected territory |
| Turkiye to an EU or EEA airport, operated by Pegasus | EU261 normally does not apply merely because this is the return; examine SHY-YOLCU |
| UK airport to Turkiye, operated by Pegasus | UK261 can apply to the UK departure |
| Turkiye to the UK, operated by Pegasus | UK261 normally does not apply because Pegasus is not a UK carrier; examine Turkish rules |
| Domestic Turkiye or an international Pegasus flight to or from a Turkish airport | SHY-YOLCU can be relevant, subject to its event and procedure rules |
For europe-SAW-onward itinerary, EU261 uses EUR 250, EUR 400 and EUR 600 bands after coverage, timing and cause are established. Turkish rules for europe-SAW-onward itinerary use EUR 100 domestically and EUR 250, EUR 400 or EUR 600 internationally, converted at the Central Bank selling rate on payment day.
For europe-SAW-onward itinerary, the Turkish amendment published on 10 December 2024 added an express rule for final-arrival delays of at least three hours caused by technical or operational reasons. In a review of europe-SAW-onward itinerary, it directs the carrier to perform the duties in Articles 8 and 9; it did not turn every late flight anywhere in the world into a valid claim.
Where both systems appear relevant to europe-SAW-onward itinerary, record any payment already made and do not promise duplicate fixed awards for the same disruption.
Map every segment and operator before using final destination
An EU departure is the strongest entry point for a Pegasus claim. The ticket must then show whether SAW and the onward destination form one unit rather than a self-connection.
Codeshare can change the carrier responsible for the disrupted segment. A PC code on the itinerary is not enough when the ticket states that Iberia or flynas operates the flight.
If the itinerary ends in a third country, do not split the amount automatically at SAW. First establish the protected journey and the distance method that applies.
Worked example
A Madrid-SAW-onward itinerary on one booking arrives at the final destination more than three hours late. The analysis begins with the EU departure, then checks each operator and the causal connection.
For europe-SAW-onward itinerary, substitute the passenger's real airports, operators, timings and offers.
Compensation, refund, rerouting and care are separate
For europe-SAW-onward itinerary, fixed compensation addresses a qualifying disruption; it is not the ticket price. For europe-SAW-onward itinerary, reimbursement replaces unused transport, rerouting provides substitute travel, and care covers proportionate waiting needs.
| Remedy | Evidence that normally matters |
|---|---|
| Fixed compensation | route, operator, final timing, notice and cause |
| Ticket reimbursement | unused coupons, payment record and the passenger's election |
| Rerouting or replacement cost | alternatives offered, contact attempts, urgency and price |
| Meals, hotel and transfers | necessity, dates, itemised receipts and proof of payment |
For europe-SAW-onward itinerary, a family should calculate each eligible passenger separately and claim shared expenses once. Write one line for every remedy and show how the amount was derived.
Evidence checklist for europe-SAW-onward itinerary
- the Pegasus PNR and complete e-ticket, including every coupon.
- the operating carrier shown for each segment.
- original and revised departure and arrival times.
- boarding passes and replacement documents that apply.
- email, SMS and app notices with visible timestamps.
- the exact reason Pegasus gave, in its original language.
- proof of final arrival, including a transfer after diversion.
- itemised receipts and proof of payment for each expense.
- the submitted complaint, attachment list and case reference.
- authority documents for every passenger represented.
For europe-SAW-onward itinerary, download durable copies instead of keeping only links to a booking panel. Store original-language evidence for europe-SAW-onward itinerary and add a short explanation when an authority or court will not understand it.
Present the claim in a form Pegasus can answer
Open the europe-SAW-onward itinerary request with the date, route, PNR and operator. Follow with a chronology, governing rule, requested remedies and evidence for europe-SAW-onward itinerary.
Quote Pegasus's reason before responding. For europe-SAW-onward itinerary, ask precise questions about causation, save the Write to Us submission and retain its reference.
Choose the escalation route by subject
For an eligible Turkish issue involving europe-SAW-onward itinerary, complain to Pegasus first and then consider SHGM. Its scope for europe-SAW-onward itinerary covers boarding refusal, cancellation, delay and class placement, but excludes baggage and several ticketing disputes.
An EU or EEA departure involving europe-SAW-onward itinerary belongs with the competent authority, ADR body or court; a UK departure uses the corresponding UK route. Check whether that body awards money or only supervises compliance.
For a represented SHGM claim about europe-SAW-onward itinerary, follow its notarisation, apostille and wet-signature requirements rather than assuming an electronic mandate is enough.
Legal position checked on 29 August 2026
The assessment of europe-SAW-onward itinerary uses current EU261, UK261 where relevant, and SHY-YOLCU as amended on 10 December 2024. Relevant live Pegasus pages were checked on the same date.
The EU reform adopted in July 2026 is not yet applied to europe-SAW-onward itinerary. Its future nine-month submission and 30-day response rules for europe-SAW-onward itinerary are not current on 29 August 2026.
Routes, bundles and forms can change. Verify the operator, current Pegasus terms and competent procedure again when submitting europe-SAW-onward itinerary.
Mistakes that weaken the file
- treating both directions of a return booking as EU261-covered.
- naming Pegasus without checking who operated every segment.
- using departure delay when final arrival is decisive.
- accepting credit without retaining the voucher terms.
- combining ticket money, expenses and fixed compensation into one sum.
- missing a short baggage or procedural notice period.
- presenting the future EU reform as law already in force.
For europe-SAW-onward itinerary, a concise factual record is more persuasive than repeated messages with changing amounts or legal theories.
Related guides
FAQ about europe-SAW-onward itinerary
Does EU261 stop automatically at SAW?
Not on every one-booking journey; final-destination rules can extend the assessment beyond the connection point.
Are separate Pegasus bookings treated the same?
Usually not. Independent PNRs are assessed separately and can leave replacement and baggage-transfer risk with the traveller.
Does a Pegasus-operated return from Turkiye automatically fall under EU261 for europe-SAW-onward itinerary?
No. For europe-SAW-onward itinerary, a direct Pegasus return from Turkiye normally falls outside EU261 because Pegasus is not an EU carrier; Turkish rules may still apply.
Can expenses be claimed as well as a fixed award for europe-SAW-onward itinerary?
Potentially yes. For europe-SAW-onward itinerary, reasonable care or replacement costs have a different function from fixed compensation and must be proved separately.
Does the adopted EU reform already change europe-SAW-onward itinerary?
No on 29 August 2026. Use the current rules for europe-SAW-onward itinerary; the future nine-month submission and 30-day response provisions are not yet applied.