Claim Compensation for a Paris Charles de Gaulle Airport to Budapest Airport Flight

Marketing airline versus operator on this airport pair

A route page cannot decide the airline question without the ticket. For CDG to BUD, list each sector in order, then write the operator beside it. This prevents a claim from being sent to a marketing carrier that did not operate the affected flight.

Follow the protected itinerary to the final destination

Use the reservation reference to prove whether the journey from CDG to BUD was protected as one itinerary. Keep rebooking documents and any ground transfer inserted after disruption. Do not combine independent tickets into one legal journey merely because they were purchased for the same trip.

Measure arrival for the CDG–BUD case

The route file should explain where and when the passenger finally arrived. A cancellation followed by rerouting may use another airport or ground transport. Preserve that alternative path so the reviewer can calculate the impact without assuming the original BUD sector operated.

Waiting, hotel and replacement travel

Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to BUD by rerouting or abandon unused travel for reimbursement. Keep itemised receipts and the alternatives offered; the cause of disruption does not automatically eliminate every care duty.

Link the disruption event to the affected sector

A route-based claim is easier to review when the cause is placed on the timeline. State when it arose, which operator reported it and which part of the CDG–BUD itinerary it affected. Preserve later explanations if the initial message changes.

Route documents in travel order

• Complete booking showing CDG as departure and BUD or the final booked destination
• Operating carrier and flight number for every sector
• Boarding passes, check-in proof and replacement itinerary
• Scheduled and actual final-arrival times with sources
• Cancellation or delay notices and the reason given
• Care, hotel, transport and substitute-travel receipts

Keep original records and submit copies through the verified channel. Mark any item that comes from a third-party source.

A route-led request without unsupported assumptions

A strong route submission does not claim that a direct service always operates. It describes the actual ticket. State every sector, identify where the disruption occurred and explain how the passenger ultimately reached BUD or the final destination.

Route-specific fields before submission

• CDG departure: record the scheduled local time, terminal and check-in evidence at Paris Charles de Gaulle Airport.
• CDG operator: name the company that operated the disrupted sector leaving France.
• CDG notice: preserve the first delay or cancellation message and its timestamp.
• CDG assistance: list meals, hotel, transport or rerouting requested before the journey continued.
• CDG–BUD booking: state whether the airport pair sat on one reservation or separate tickets.
• CDG–BUD disruption: identify the affected sector, stated cause and replacement path.
• BUD destination: record whether Budapest Airport was the final booked destination or an intermediate point.
• BUD arrival: preserve the scheduled and actual arrival times and the source used for each.
• BUD expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
• France to Hungary review: verify the applicable regime and procedural deadline before escalation.

A completed CDG–BUD worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.

Confirm current operations before using route-specific facts

The catalogue stores this as an airport-pair legal reference and marks current service as unverified. It does not confirm a direct flight, distance band or operating airline. The page therefore remains protected from indexing until current service, distance and carriers are verified. The passenger should use the actual booking, not this route record, as evidence of travel.

Start with travel direction: CDG to BUD

Treat CDG–BUD as a journey frame rather than a live schedule. The passenger may have flown directly, connected elsewhere or held separate tickets. Preserve the ticket and identify the operator of each sector before applying route coverage or measuring the final-arrival impact.

How the eu departure and eu arrival interact

The CDG departure is catalogued in the EU/EEA framework. EU261 is therefore the primary route screen regardless of the operating airline's nationality, subject to the actual itinerary and legal conditions. The BUD arrival marker is eu; any UK element should be assessed separately rather than mixed into one unsupported conclusion.