Pegasus codeshare and operating carrier: Iberia, flynas and PC tickets
The airline that actually operated the disrupted segment normally faces the EU261 claim; a PC flight number or Pegasus-issued ticket does not settle that question.
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 codeshare and operating carrier, start with the complete ticket rather than one flight number. The decisive record for codeshare and operating carrier combines direction, actual operator, booking structure, final timing, cause and the remedy already offered.
| First check for codeshare and operating carrier | 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 codeshare and operating carrier
For codeshare and operating carrier, Pegasus Hava Tasimaciligi A.S. is a Turkish carrier, not an EU or UK carrier. That carrier status makes direction central to codeshare and operating carrier, 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 codeshare and operating carrier, EU261 uses EUR 250, EUR 400 and EUR 600 bands after coverage, timing and cause are established. Turkish rules for codeshare and operating carrier use EUR 100 domestically and EUR 250, EUR 400 or EUR 600 internationally, converted at the Central Bank selling rate on payment day.
For codeshare and operating carrier, 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 codeshare and operating carrier, 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 codeshare and operating carrier, record any payment already made and do not promise duplicate fixed awards for the same disruption.
Read the operated-by line segment by segment
Pegasus and Iberia announced a codeshare in October 2025, including Iberia-operated destinations beyond Madrid. The operating airline remains visible in the booking documents.
Pegasus has also sold flynas-operated Saudi services. A website or ticketing relationship cannot be treated as proof that Pegasus controlled the disrupted aircraft.
Send the flight-operation claim to the actual operator while directing ticket-money or seller issues to the contractual party that holds them. Preserve both carrier codes.
Worked example
A PC-marketed segment beyond Madrid is listed as operated by Iberia and is cancelled. The operating-carrier test points to Iberia for EU261 operation liability, while the seller may still handle ticket servicing.
For codeshare and operating carrier, substitute the passenger's real airports, operators, timings and offers.
Compensation, refund, rerouting and care are separate
For codeshare and operating carrier, fixed compensation addresses a qualifying disruption; it is not the ticket price. For codeshare and operating carrier, 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 codeshare and operating carrier, 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 codeshare and operating carrier
- 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 codeshare and operating carrier, download durable copies instead of keeping only links to a booking panel. Store original-language evidence for codeshare and operating carrier 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 codeshare and operating carrier request with the date, route, PNR and operator. Follow with a chronology, governing rule, requested remedies and evidence for codeshare and operating carrier.
Quote Pegasus's reason before responding. For codeshare and operating carrier, 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 codeshare and operating carrier, complain to Pegasus first and then consider SHGM. Its scope for codeshare and operating carrier covers boarding refusal, cancellation, delay and class placement, but excludes baggage and several ticketing disputes.
An EU or EEA departure involving codeshare and operating carrier 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 codeshare and operating carrier, 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 codeshare and operating carrier 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 codeshare and operating carrier. Its future nine-month submission and 30-day response rules for codeshare and operating carrier 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 codeshare and operating carrier.
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 codeshare and operating carrier, a concise factual record is more persuasive than repeated messages with changing amounts or legal theories.
Related guides
FAQ about codeshare and operating carrier
Does a PC number always mean Pegasus is liable?
No. Codeshare documents can carry a PC marketing code while another airline operates the aircraft.
Can I claim from both the marketing and operating airline?
Allocate each request by function: flight-operation liability usually follows the operator, while ticket servicing can remain with the seller.
Does a Pegasus-operated return from Turkiye automatically fall under EU261 for codeshare and operating carrier?
No. For codeshare and operating carrier, 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 codeshare and operating carrier?
Potentially yes. For codeshare and operating carrier, reasonable care or replacement costs have a different function from fixed compensation and must be proved separately.
Does the adopted EU reform already change codeshare and operating carrier?
No on 29 August 2026. Use the current rules for codeshare and operating carrier; the future nine-month submission and 30-day response provisions are not yet applied.