Corendon Airlines compensation claim form and evidence
Short answer: A useful filing identifies the law, operator, timeline and each requested sum before attaching numbered evidence; this finding on legal test controls the analysis of the claim submission for Corendon Airlines. A Corendon flight starting in Britain is assessed under UK261 and one starting in the EU under EU261, regardless of which Corendon company operates it; this finding on outbound direction controls the analysis of the claim submission for Corendon Airlines; for a third-country return, the exact group company operating the sector can change the EU261 result.
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:
A Corendon submission should identify the operating company before the passenger selects a contact channel. Copy the disrupted sector, operator code, direction, final arrival and requested remedy into a local draft, then attach the documents that prove each point. Send flight compensation to the relevant XC, CD, XR or actual substitute operator and address package-performance issues separately to the organiser. Retaining both acknowledgements avoids losing the first submission date when a shared brand portal redirects the case internally.
Draft offline so the portal does not dictate the legal theory
Before opening the Corendon Airlines channel, assemble PNR, tickets, operated-by wording, original plan, changed plan, notice, final arrival and receipts. Decide whether the request concerns a lump sum, repayment, rerouting, care or Montreal loss. Corendon's post-flight portal accepts delay, schedule change, cancellation, involuntary denied boarding and baggage files; select the operating company and preserve the submitted record; this finding on submission route controls the analysis of the claim submission for Corendon Airlines. Write locally and redact unnecessary identity or card material, because an expired session can destroy the only version and a narrow dropdown can otherwise turn a legal demand into general feedback.
Compress the event into six verifiable statements
For a package flight departing Britain and shown as operated by XC, start with service, date, route and operator. Follow with the promised timing, the first change and its notification, the solution offered, the actual final result and the reason given. End with separate amounts and numbered enclosures. Handler and passenger can then read matter 866 in chronological order. A reply that addresses only ticket repayment remains visibly incomplete if the fixed redress or care rows are still open.
Treat proof of submission as part of the evidence
Save populated fields and the attachment list before pressing send. Retain the acknowledgement, reference and automated email afterwards. If additional material appears, send a dated supplement quoting the existing reference instead of opening competing duplicates. Secure bank fields are preferable to ordinary correspondence. Any later regulator, ADR body or court should see exactly what Corendon Airlines received and when, not a fresh recollection prepared after rejection.
Submission pack for Corendon reference 866
- Select the correct XC, CD or XR company before entering the event.
- Prepare a local copy of the original plan and every later itinerary.
- Reduce the chronology to dated statements that another reader can verify.
- Give compensation, fare, care and baggage their own requested amounts.
- Number each enclosure and state the proposition it supports.
- Use secure fields for bank details and redact unrelated identity data.
- Capture all populated portal fields before the final click.
- Archive the acknowledgement, case reference and attachment list together.
Send a focused request and choose escalation
Corendon's post-flight channel asks the passenger to choose a group operator and event category. Before opening it, use an EU-bound holiday return operated by Dutch code CD to verify XC, CD or XR from the original document; a later replacement may display a different company. Save the completed fields and every attachment name before transmission.
Matter 866 should contain a short chronology followed by a remedy table. State a personal statutory amount for each eligible passenger, one actual value for each shared expense and a separate transport or baggage request where relevant. The portal confirmation becomes the final enclosure. If a response addresses only one row, the passenger can point to the exact unresolved request without recreating the entire history.
The filing procedure is stated as at 10 September 2026 (Corendon Airlines; file 866). The reform's future nine-month notification period has deferred application and is not presented here as an existing deadline (Corendon Airlines; matter 866).
The attachment index for Corendon case 866 should use stable names such as 01-booking, 02-notice and 03-arrival. Refer to those numbers in the narrative. A decision maker can then move from each assertion to its proof without guessing which screenshot or receipt the passenger meant. Keep original file metadata where possible and export dynamic app screens before they change. For a group request, add a passenger schedule linking each name to ticket, requested amount and any authority to act. End the saved pack with the exact portal category and Corendon entity selected. Verify that every uploaded page remains readable.
Prepare the submission outside the carrier portal and treat the upload receipt as records (Corendon Airlines; file 866). The opening paragraph should give service, date, itinerary, original operator, disruption, final result, legal basis and requested remedy (Corendon Airlines; matter 866). Follow it with a traveller table, a separate expense ledger and numbered enclosures (Corendon Airlines; record 866). Open every attachment, verify names and readability, and remove sensitive material that is not needed for the request (Corendon Airlines; case chronology 866). Before pressing send, capture the selected category and populated fields; afterwards retain the acknowledgement, reference and exact attachment list (Corendon Airlines; file 866). A later document should supplement that reference, not create a rival version whose date and contents are harder to prove (Corendon Airlines; matter 866).
Name the missing record, responsible company and next action in the closing sentence (Corendon Airlines; file 866). Reconcile the balance with every payment already received, label any estimate and retain the dated calculation used (Corendon Airlines; matter 866). The result remains actionable without turning an unresolved condition into certainty (Corendon Airlines; record 866).
Related Corendon Airlines guides
FAQ: Questions passengers ask about the claim submission
Which operator should I select in Corendon's portal?
Corendon Airlines: Choose the company shown as operating the disrupted sector, using the original record rather than the best-known group name.
How should several expenses be entered?
Corendon Airlines: Use separate rows with date, payer, purpose, currency, value and enclosure number instead of an unsupported total.
Can one form include several passengers?
Corendon Airlines: Often yes, but name each person and keep ticket-linked amounts distinct; authority may be needed for other adults.
What if the portal sends no copy?
Corendon Airlines: Save screenshots or a PDF before submission and retain the confirmation page, email and generated reference afterwards.
Should I open a second Corendon case?
Corendon Airlines: Usually supplement the existing reference. Duplicate cases can separate the chronology from its evidence unless support instructs otherwise.
Official sources
Sources checked for Corendon Airlines compensation claim form and evidence: