French bee codeshare: identify the operating carrier
Short answer: French bee is an EU carrier. For the issue “French bee codeshare: identify the”: EU261 can cover departures from the EU and French bee-operated journeys from a non-EU airport to the EU. In a claim about “French bee codeshare: identify the”: Check the operating carrier, final arrival and cause before asking for 250, 400 or 600 EUR.
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:
What is specific to this case
Read every segment's ‘operated by’ field. In a claim about “French bee codeshare: identify the”: A group brand, codeshare number or loyalty programme can point to a different company from the legal operator that must answer the disruption claim.
In a claim about “French bee codeshare: identify the”: For Europe and the United Kingdom, verify code BF, the words ‘operated by’ and the legal entity before claiming. A group name or sales channel does not replace the operating-carrier test.
Decision in two minutes
| Check | Meaning |
|---|---|
| Coverage | Protection may apply after checking the operator |
| Final arrival | At least three hours at the final destination |
| Cause | The airline must prove an extraordinary defence |
| Amount | 250, 400 or 600 EUR per passenger |
When the protection applies
For "French bee codeshare: identify the", start with the departure airport, then identify the airline that actually operated the affected sector, and only then classify the disruption. French bee is an EU carrier. In a claim about “French bee codeshare: identify the”: EU261 can cover departures from the EU and French bee-operated journeys from a non-EU airport to the EU. When assessing “French bee codeshare: identify the”: Nationality, residence and the currency used to buy the ticket do not change this territorial test. For the issue “French bee codeshare: identify the”: Keep the complete itinerary because the marketing flight number on the first segment can give an incomplete picture.
The decisive issue
In "French bee codeshare: identify the", delay is normally measured at the final destination on a single reservation. In a claim about “French bee codeshare: identify the”: The relevant time is generally when at least one aircraft door opens, not touchdown or arrival at the parking stand. When assessing “French bee codeshare: identify the”: A final delay of three hours or more can trigger fixed compensation unless the carrier proves an extraordinary event and shows that reasonable measures could not have prevented the result.
Compensation, care and reimbursement
A cancellation connected with "French bee codeshare: identify the" creates separate rights: reimbursement or rerouting, care while waiting, and fixed compensation where its conditions are met. When assessing “French bee codeshare: identify the”: Notice given less than fourteen days before departure matters, but the departure and arrival times of the replacement itinerary must also be compared with the original schedule before any conclusion is reached.
Operating carrier and one booking
For "French bee codeshare: identify the", EU261 compensation is generally 250, 400 or 600 EUR according to the legally relevant distance. A low fare does not reduce the fixed amount. In a claim about “French bee codeshare: identify the”: Each eligible passenger on a family booking is assessed separately, while hotel, meals, transfers and replacement transport should be listed as distinct documented expenses rather than folded into the fixed payment.
Evidence that supports the claim
A marketing code does not identify the debtor in "French bee codeshare: identify the". Check the words "operated by" on the booking confirmation, e-ticket and boarding pass. When assessing “French bee codeshare: identify the”: The operating carrier answers the EU261 claim for the disrupted sector, although the travel agent, loyalty programme or selling airline may still be relevant to a separate ticket refund or ancillary-service issue.
What to do on the travel day
A strong file for "French bee codeshare: identify the" contains the PNR, e-ticket, original and replacement boarding passes, all airline notices, airport-screen photographs and the actual arrival time. Add a short chronology. For the issue “French bee codeshare: identify the”: Receipts should show the date, amount, currency and service purchased, because a card statement alone rarely explains why an expense was necessary and proportionate.
How to submit a complete claim
At the airport, do not leave "French bee codeshare: identify the" as an oral conversation. Ask for the cause, the offered alternative and care in writing. If no assistance is provided, reasonable and necessary expenses may be recoverable. When assessing “French bee codeshare: identify the”: Photograph a closed service desk, keep screenshots of the app and avoid luxury choices when a suitable practical option remains available.
Mistakes that weaken a claim
A claim about "French bee codeshare: identify the" should separate fixed compensation, the ticket price and out-of-pocket costs. In a claim about “French bee codeshare: identify the”: State the origin, final destination, operating carrier, scheduled arrival, actual arrival and legal basis. When assessing “French bee codeshare: identify the”: A compact amount table and a numbered attachment list are easier to assess than a long narrative that does not say precisely what is being requested.
Example involving several passengers
The phrase "operational reasons" does not resolve "French bee codeshare: identify the". When assessing “French bee codeshare: identify the”: The airline must identify the event, connect it to the delay or cancellation and explain the reasonable measures taken. For the issue “French bee codeshare: identify the”: Weather, air traffic control and security can be extraordinary; ordinary technical problems, aircraft rotation and a shortage of the carrier's own crew often belong to normal operational risk.
Deadlines and current law
In the "French bee codeshare: identify the" example, two adults and one child travel on one booking through Paris-Orly (ORY). For the issue “French bee codeshare: identify the”: If all three arrive four hours late in an eligible case, fixed compensation is assessed for each passenger. In a claim about “French bee codeshare: identify the”: One adult paid the hotel bill, so that invoice is claimed once as an expense instead of being artificially multiplied by three.
The rules relevant to "French bee codeshare: identify the" were checked on 1 September 2026. In a claim about “French bee codeshare: identify the”: The reform adopted in July 2026 is not yet applicable, so its future nine-month notification period and 30-day response period are not current deadlines. When assessing “French bee codeshare: identify the”: National limitation periods and the competent enforcement or dispute body still require a separate route-specific check.
The local rule outside EU261
In a claim about “French bee codeshare: identify the”: Outside EU261 or UK261, the ticket contract and the law at the place of departure may still provide rerouting, care, refund or complaint rights, but they do not automatically create the European fixed payment. When assessing “French bee codeshare: identify the”: For French bee, also check DGAC / Médiation Tourisme Voyage and keep that route separate from European fixed compensation.
Practical claim review
Review point 1 for "French bee codeshare: identify the": connect origin and final destination to a dated document and note exactly what it proves. In a claim about “French bee codeshare: identify the”: The file will remain understandable if French bee later changes the stated cause or a partner takes over the response.
Review point 2 for "French bee codeshare: identify the": connect operating carrier to a dated document and note exactly what it proves. When assessing “French bee codeshare: identify the”: The file will remain understandable if French bee later changes the stated cause or a partner takes over the response.
Review point 3 for "French bee codeshare: identify the": connect notice date to a dated document and note exactly what it proves. For the issue “French bee codeshare: identify the”: The file will remain understandable if French bee later changes the stated cause or a partner takes over the response.
Review point 4 for "French bee codeshare: identify the": connect actual arrival to a dated document and note exactly what it proves. In a claim about “French bee codeshare: identify the”: The file will remain understandable if French bee later changes the stated cause or a partner takes over the response.
Evidence
- Save the itinerary and PNR.
- identify the operating carrier.
- calculate scheduled and actual arrival.
- record the disruption and notice date.
- request the cause and supporting evidence.
- separate compensation from expenses.
- number every attachment.
- submit the claim and retain proof of receipt.
Claim steps
- Save the itinerary and PNR.
- identify the operating carrier.
- calculate scheduled and actual arrival.
- record the disruption and notice date.
- request the cause and supporting evidence.
- separate compensation from expenses.
Related guides
FAQ
Does EU261 apply automatically?
No. For French bee codeshare: identify the, check the departure point and operating carrier first.
Is 600 EUR always payable?
No. For French bee codeshare: identify the, distance, final delay, cause and replacement transport all matter.
Is weather enough to reject the claim?
Not without specific evidence. For French bee codeshare: identify the, care and rerouting remain separate rights.
How is a family booking calculated?
For French bee codeshare: identify the, any fixed amount is assessed for each eligible passenger.
Must I accept a voucher?
No. For French bee codeshare: identify the, money cannot be replaced by a voucher without informed agreement.