Cologne Bonn Airport Compensation Claim
Delayed, cancelled, denied boarding or rerouted at Cologne Bonn Airport? Keep the booking, operating carrier, airline notices, replacement itinerary and actual arrival at the ticketed destination.
CGN serves both Cologne and Bonn in Germany’s Rhine region. Departures begin at an EU airport. For disruption analysis, keep the exact operating flight and booking structure clear—especially if your onward journey uses a separate ticket or a replacement changes the airport.
When can a Cologne Bonn compensation claim arise?
A qualifying long delay, cancellation or denied boarding can create an EU261 compensation question, but payment is not automatic. Final-destination delay, cancellation notice timing, denied-boarding circumstances and the disruption cause still need to be assessed.
Keep the operating airline distinct from a booking or marketing brand, and preserve the full itinerary when the affected CGN flight belongs to one protected journey.
Direction, operating carrier and itinerary structure matter
Departing CGN
A Cologne Bonn departure starts at an EU airport, subject to EU261’s other conditions, exclusions and disruption facts.
Arriving CGN
For journeys starting outside the EU, preserve origin, operating airline and route before territorial scope is assessed.
Booking structure
Keep one protected itinerary distinct from separately purchased onward travel when documenting consequences.
CGN can be the start, end or disruption point of a Rhine-region trip
The airport serves two major nearby cities, so record the ticketed airport rather than only the city you were travelling to. If disruption changes the airport or ground-transfer plan, preserve what the airline actually offered and your actual arrival.
Direct flight
Keep scheduled and actual arrival plus every delay, cancellation and replacement-flight notice.
Cologne or Bonn
Your city destination does not replace the airport record. Keep CGN and any airline-arranged surface transfer distinct.
Separate onward ticket
Keep separately purchased onward travel distinct from the disrupted CGN booking.
For protected connections, preserve final-destination arrival
If the CGN flight is one segment of a single protected itinerary, keep the complete booking, replacement segments and actual arrival at the final ticketed destination. If you built the onward journey from separate tickets, keep those contracts distinct.
Connection evidence
- Complete booking or PNR
- Original segment times
- Replacement segment details
- Operating carrier for each affected flight
- Actual final-destination arrival
Record the replacement journey actually offered
A CGN cancellation may result in a later direct flight, a different routing or a substitute airport. Keep the alternatives actually offered by the airline, replacement operating carriers, any relevant surface transport and actual arrival at the intended destination.
Evidence for a strong CGN file
Journey evidence
- Booking confirmation and ticket
- Boarding passes and check-in proof
- Original and replacement itinerary
- Ticketed and replacement airports
- Actual final-destination arrival
Disruption evidence
- Delay or cancellation notices
- Airline’s stated disruption reason
- Rerouting, refund and care offers
- Reasonable itemised expense receipts
- Messages and transfer instructions
Related compensation guides
Cologne Bonn Airport compensation FAQ
Does EU261 apply to flights departing Cologne Bonn?
Does Cologne Bonn Airport itself pay flight compensation?
What if my CGN flight was part of a connection?
What if the replacement uses another airport?
Check your Cologne Bonn disruption
Keep the booking, operating carrier, itinerary structure, replacement journey, disruption reason and actual-arrival evidence together.
