Cross-border airport guide · BSL / MLH

Basel–Mulhouse Airport Compensation Claim

Delayed, cancelled, denied boarding or rerouted at EuroAirport Basel–Mulhouse? Keep the ticketed airport, airport code shown on your booking, operating carrier, airline notices, replacement itinerary and actual final arrival.

This airport serves a cross-border region around Basel, Mulhouse and Freiburg, but the physical airport is in France. For passenger-rights analysis, do not infer the legal framework from the city name alone: preserve the actual airport, route direction and operating carrier.

✓ France-based airport✓ EU261 departures✓ BSL / MLH records✓ Cross-border journeys
Basel Mulhouse Airport compensation claim

When can a Basel–Mulhouse 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.

Because the airport serves several nearby countries and cities, retain the exact airport shown on the booking rather than describing the trip only as “Basel,” “Mulhouse” or “Freiburg.”

The airport’s physical location matters more than the city label

FR

Departing the airport

The airport is physically in France, so departures begin at an EU airport, subject to EU261’s other conditions and exceptions.

IN

Arriving from outside the EU

For an inbound journey starting outside the EU, preserve origin and operating carrier before territorial scope is assessed.

PNR

One booking or separate tickets

Keep a protected itinerary distinct from separately purchased onward travel when documenting consequences.

Keep the airport code exactly as it appears in your travel record

EuroAirport is commonly associated with Basel–Mulhouse and may appear with different commercial city/airport coding in travel systems. For a disruption file, the safest record is the booking itself: preserve the airport name/code printed there, flight number and operating airline.

Record these identifiers

  • Airport name and code on the ticket
  • Flight number and date
  • Operating carrier
  • Origin and ticketed destination
  • Replacement itinerary, if any

Cross-border ground travel can become part of the practical disruption

Passengers may continue by road or rail toward Switzerland, France or Germany after landing. That ground journey does not by itself redefine the flight’s airport. If rerouting changes where you land, preserve airline transfer instructions and the actual arrival at your intended destination.

CH

Basel-side travel

Keep the booked airport distinct from your later ground journey into Switzerland.

FR

Mulhouse-side travel

Preserve any airline-arranged replacement transport if disruption changes the practical arrival plan.

DE

Germany-bound travel

If you continue toward Germany separately, keep those onward arrangements distinct from the flight booking unless protected together.

Document a substitute airport or changed surface transfer precisely

A cancellation can lead to a later flight, a different routing or a substitute airport. Keep the alternatives actually offered by the airline, the replacement airport, any surface transfer, replacement operating carriers and actual arrival. This is especially useful where the original trip already spans a cross-border region.

Evidence for a strong Basel–Mulhouse file

Journey evidence

  • Booking confirmation and ticket
  • Airport code exactly as booked
  • Boarding passes and check-in proof
  • Original and replacement itinerary
  • Actual final-destination arrival

Disruption evidence

  • Delay or cancellation notices
  • Airline’s stated disruption reason
  • Rerouting, refund and care offers
  • Transfer instructions and receipts
  • Reasonable itemised expenses

Related compensation guides

Basel–Mulhouse Airport compensation FAQ

Is Basel–Mulhouse Airport in Switzerland or France?
The airport is physically located in France, although it serves a cross-border region including Basel in Switzerland. Keep the actual airport and booking details for the legal assessment.
Does EU261 apply to departures from Basel–Mulhouse?
Because the airport is physically in France, departures start at an EU airport, subject to EU261’s other conditions and exceptions.
Why should I keep the airport code from my ticket?
Travel systems can present this cross-border airport using different city/airport coding. The booking record helps identify the exact disrupted flight and airport without relying on a city label.
Does the airport itself pay flight compensation?
Flight-compensation assessment normally concerns the operating airline rather than the airport.

Check your Basel–Mulhouse disruption

Keep the exact airport record, operating carrier, route direction, replacement journey, transfer instructions, disruption reason and actual-arrival evidence together.