flydubai and Emirates codeshare: which airline is responsible
Short answer: The airline code that sold a sector is not necessarily the airline that operated it. flydubai's own partnership guidance distinguishes the marketing carrier from the carrier physically flying the aircraft, and its conditions say an FZ-coded service may be operated by another airline. For EU261 or UK261 fixed compensation, identify the operator of the disrupted original sector. Emirates and flydubai are both UAE carriers, so neither name creates European arrival-side coverage for a journey beginning in Dubai.
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:
Read four identifiers from the original booking
Record the website or agent, ticket issuer, marketing flight number and full operated by line. Then preserve the original boarding pass and disruption notice. A partnership can place FZ and EK references on the same itinerary, while the aircraft, check-in rules and baggage process belong to the operator.
Do this before accepting a change. The app may replace the original sector with a new airline, hiding who was due to perform the disrupted flight. An aircraft photograph is secondary evidence because livery, ownership and operation can differ. Ask for a written operator confirmation if the documents conflict.
Marketing and operation have different jobs
flydubai's official FAQ explains that a marketing carrier sells a service under its code while the operating carrier physically performs it. Its published example shows an FZ-marketed sector performed by Emirates. The conditions also warn that baggage, check-in, boarding, delay and cancellation provisions may differ on codeshare services.
For a fixed passenger-rights demand, address the actual operator of the affected sector. For ticket servicing or refund mechanics, the issuing airline or agent may still have a role. For a loyalty posting issue, the programme is another channel. State the requested remedy so each business is not asked to solve every part of the trip.
The operator also determines the inbound coverage test
A journey from an EU or UK airport can be covered regardless of whether flydubai or Emirates operates it because the departure limb applies. A journey from Dubai to the EU or UK is different. Both airlines are UAE carriers, so switching from FZ to EK does not supply EU or UK carrier status for the arrival limb.
If a European carrier actually operates an inbound codeshare, reassess coverage using that company. Do not infer status from the marketing number. On a multi-sector booking, place operator and territorial result beside each segment, then identify which event caused final delay.
The original disruption and replacement operation are separate
Suppose flydubai was due to operate the protected first flight but cancelled it and rebooked the passenger on Emirates. Emirates' successful replacement service does not become responsible for flydubai's original cancellation merely because it delivered the passenger late. The original operating carrier and event remain the focus of that compensation claim.
If the Emirates replacement suffers a new, independent disruption, create a second event row. Avoid double recovery for the same loss of time but investigate each operator's role and cause. Keep both boarding passes and all messages, including who arranged the rerouting.
Dubai connections need a segment-by-segment cause map
A first FZ-operated flight may arrive late and cause loss of an EK-operated onward sector. On one protected booking, final arrival can matter, but the claim must still explain which operator's event produced it. If the onward flight was independently cancelled, request reasons from both. One airline's weather explanation does not automatically cover the other's staffing decision.
Use a table with sector, marketing code, operator, schedule, event, cause and replacement. Attach through-ticket evidence. If the tickets were separate, preserve any agent protection and do not present the arrangement as one statutory journey without support.
Baggage is usually reported to the final operating carrier
flydubai directs passengers whose baggage is delayed or damaged on a partner flight to report it to the final carrier that operated the flight. At the arrival airport, obtain the PIR immediately and retain every tag. The carrier handling the baggage file may therefore differ from the operator responsible for an earlier flight delay.
Do not wait for the compensation dispute to settle before reporting baggage. Seven- and 21-day written time limits can run independently. Use the PIR reference in the baggage channel and the booking timeline in the flight channel. A missing suitcase does not extend the passenger's legal arrival time, though it can create a separate Montreal claim.
Name the legal entity and role in the demand
Open with: “The disrupted sector [route/date] was marketed as [code] and operated by [airline].” Attach the source. Then state the protected journey, event, final delay and amount. If authority is given to a representative, make sure it names the passenger, flight and correct carrier rather than only an informal partnership label.
When one party redirects the case, retain the message and submit a concise file to the indicated operator. If it appears wrong, ask the sender to confirm who controlled the flight and why. A documented conflict is useful in ADR or court; several generic contact forms without operator analysis are not.
Ticket stock does not settle physical operation
A ticket number prefix can identify the issuing carrier, while the flight code identifies marketing and the operated by field identifies physical performance. Keep all three. A refund may need the issuer even though fixed compensation goes to the operator. Do not use the card statement merchant as proof of who flew the sector.
If a travel agent supplies only a summary, request the passenger receipt and coupon history. Match the date and route because the same flight number can have different arrangements over time. The conclusion should rest on the passenger's actual service, not a partnership description copied from another season.
Related flydubai guides
FAQ: frequently asked questions about this flydubai situation
Does an FZ flight number mean flydubai operated the aircraft?
Not always. It can be a marketing code; check the full operated-by wording.
Does an EK code mean Emirates is responsible?
Only if Emirates was the actual operator of the disrupted sector or has a separate ticketing role relevant to the remedy.
Does Emirates operation make Dubai-to-EU covered?
Generally no. Emirates and flydubai are both UAE carriers; neither supplies EU arrival-side carrier status.
Who handles baggage after a partner itinerary?
Report immediately at arrival; flydubai says partner-flight baggage issues should be reported to the final operating carrier.
Who pays after flydubai rebooks me on Emirates?
The original disruption is assessed against its original operator; a new independent disruption may require separate analysis.
Official sources
Sources checked for flydubai and Emirates codeshare: which airline is responsible:
- EUR-Lex: Regulation (EC) No 261/2004
- UK Civil Aviation Authority: delays and cancellations
- flydubai disruptions policy
- flydubai disruptions and cancellations
- flydubai contact form
- flydubai conditions of carriage
- flydubai delayed or damaged baggage
- flydubai Emirates partnership FAQ
- European Commission: national enforcement bodies
- ICAO: Montreal Convention 1999