Europe → Türkiye
A SunExpress flight departing an EU airport can fall under EU261 even though SunExpress is not an EU carrier. The European departure is the key fact.
SunExpress claims often arise on direct leisure and visiting-friends-and-relatives routes between Türkiye and European airports. That makes the exact departure side of the journey especially important: the outbound and return legs of the same trip may not fall under the same compensation regime.
Treat each disrupted SunExpress flight as its own route first. Keep the booked origin, destination, actual arrival time and disruption notice. If you bought a package holiday or booked through an agency, also keep the airline booking details—the organizer's involvement does not replace the need to identify the affected operating flight.
A SunExpress passenger may fly from a European airport to a Turkish holiday or family destination and return on the reverse route days later. Even though both sectors belong to one trip in everyday terms, passenger-rights coverage should be checked sector by sector.
A qualifying long delay, cancellation or involuntary denied boarding may support compensation, but the departure jurisdiction, operating carrier, timing and cause remain central.
A SunExpress flight departing an EU airport can fall under EU261 even though SunExpress is not an EU carrier. The European departure is the key fact.
The return sector starting in Türkiye does not gain EU261 coverage merely because it lands in the EU. Turkish passenger-rights rules may instead be relevant.
A SunExpress flight starting in the United Kingdom should be checked separately under UK passenger-rights rules. Do not assume the EU test automatically applies to a UK-origin journey.
SunExpress flights can form part of a broader holiday booking. For flight-compensation analysis, it is still important to isolate the operating flight and the airline disruption from separate accommodation or package issues.
If a tour operator or agency arranged the trip, retain both the package confirmation and any SunExpress booking reference, flight number or boarding pass.
A hotel or transfer problem is not the same as a flight-compensation event. Focus the airline claim on the affected SunExpress sector and its passenger-rights consequences.
If the disrupted flight was replaced, keep the replacement flight details and actual arrival time. These facts help show the real impact of the airline disruption.
On a direct SunExpress flight, preserve the scheduled and actual arrival time. The arrival impact, route and reason for delay are more useful than departure delay alone.
Save when the cancellation was communicated and the alternative offered. A refund, replacement flight and possible compensation are related but distinct questions.
If you met the travel and check-in requirements but were involuntarily denied boarding, retain written confirmation and the details of any replacement journey.
A booking channel, tour operator or marketing arrangement does not itself identify the airline responsible under passenger-rights rules. Keep the flight number and any “operated by” information for the disrupted sector.
This also prevents a package booking from obscuring the core compensation question: which flight was disrupted, who operated it, where did it depart, and what was the arrival consequence?
We identify the exact disrupted outbound or return flight instead of treating a round trip as one undifferentiated journey.
We assess the departure jurisdiction, operating carrier and disruption against the passenger-rights framework that may apply.
We organize the airline booking, timings, notification and supporting evidence around the affected SunExpress flight.
Send the exact disrupted sector, booking details and arrival outcome. If your trip included both outbound and return SunExpress flights, identify which sector was affected so the correct route-based rules can be checked.