Departure from the EU
Brussels Airlines flights departing an EU airport can fall within EU261 when the regulation's other conditions are met.
Brussels Airlines claims often combine two very different journey patterns: short European sectors and longer trips connecting through Brussels. A disruption at Brussels Airport can therefore affect a protected onward journey far more than the first flight's delay suggests.
Brussels Airlines is an EU carrier, so EU261 is central to many of its operated flights, including qualifying inbound journeys from outside the EU. On Lufthansa Group and codeshare itineraries, the actual operator of the disrupted sector still needs to be identified.
A qualifying long arrival delay, cancellation or involuntary denied boarding may support compensation. When a short European flight feeds a longer Brussels connection on one booking, the claim should not be reduced to the delay on the first sector alone.
Preserve the full ticket, the original final destination and every replacement sector. This makes it possible to distinguish a protected connection from separately booked travel and to identify which operating carrier caused the disruption.
Brussels Airlines flights departing an EU airport can fall within EU261 when the regulation's other conditions are met.
Because Brussels Airlines is an EU carrier, a Brussels Airlines-operated flight arriving in the EU from outside the EU can also fall within EU261 when the remaining conditions are satisfied.
On a codeshare or group itinerary, check who actually operated the affected flight. The SN marketing code alone does not settle the operating-carrier question.
If both sectors are on one protected booking, save the complete itinerary. A modest inbound delay can become a much larger delay at the ticketed final destination.
Keep every replacement flight and routing change. A new journey through another hub or with another carrier is part of the disruption record.
A separately purchased flight after Brussels should not automatically be treated as a protected Brussels Airlines connection. Preserve both bookings.
Brussels Airlines tickets can sit inside wider Lufthansa Group and codeshare itineraries. A sector marketed with an SN flight number can still require an operating-carrier check before responsibility is assessed.
For the flight that was delayed or cancelled, record the “operated by” carrier from the itinerary or boarding pass. This is especially important when a feeder, onward flight or replacement segment was performed by another airline.
The first itinerary establishes the connection structure and destination purchased before the disruption.
Save new flight numbers, operators and boarding passes, including rerouting through a different hub.
Record when you reached the original ticketed destination. For a protected connection this can be central to the delay assessment.
We map the European feeder, Brussels connection and original final destination instead of isolating one flight.
We identify the operating airline of the disrupted sector and assess which passenger-rights framework may apply.
On protected connections, we organize the case around the actual arrival at the original endpoint and the available disruption evidence.
Send the complete itinerary, the operating carrier of the disrupted sector and any replacement flights. If a Brussels connection was missed, include the actual arrival time at the original final destination.