Feeder into Helsinki
Record the scheduled and actual arrival of the first sector and the connection shown in the original booking.
A Finnair claim can hinge on a Helsinki connection rather than only the delay of one flight. If a European feeder and an onward long-haul or Nordic flight were sold on one protected itinerary, preserve the missed connection, replacement sectors and the time you ultimately reached the original final destination.
Finnair is an EU carrier, so EU261 can be relevant to qualifying EU departures and qualifying Finnair-operated inbound flights from outside the EU. On codeshare or partner itineraries, confirm the airline that actually operated the disrupted sector before assigning responsibility.
A qualifying long arrival delay, cancellation or involuntary denied boarding may support compensation. For a protected connection, the effect at the final destination can matter, so keep every flight in the original booking and the replacement journey.
If you bought the onward ticket separately, keep both bookings but distinguish that self-built connection from a through itinerary protected under one reservation.
Record the scheduled and actual arrival of the first sector and the connection shown in the original booking.
Keep the flight you missed, including its operator, destination and scheduled departure.
For one protected itinerary, document when the replacement journey reached the original final destination.
A qualifying flight leaving an EU airport can fall within EU261 when the regulation's other conditions are met.
A qualifying inbound flight may also be covered when Finnair actually operates it because Finnair is an EU carrier.
Where multiple sectors form one protected itinerary, preserve the whole booking so the final-destination impact can be assessed.
Codeshare and partner itineraries can carry a Finnair marketing code even when another airline operates the aircraft. Keep the “operated by” information from your itinerary or boarding pass.
The actual operator, route and booking structure should be reviewed together. This is especially important when the disrupted sector is only one part of a longer Helsinki connection.
Save the original Helsinki connection and the endpoint shown on the ticket before any rebooking.
Keep every replacement flight and operator, including rerouting that bypasses Helsinki or uses a partner airline.
Document the actual arrival at the original final destination on a protected itinerary, not just arrival at an intermediate airport.
We identify the affected sector, Helsinki connection and whether the flights formed one protected booking.
We review the route, actual operating carrier and passenger-rights framework relevant to the disrupted flight.
For a protected connection, we organize the missed sector, rerouting and arrival at the original final destination.
Send the complete booking, operating-carrier details, disruption messages and replacement itinerary. If Helsinki was a protected connection, include the missed onward sector and your actual arrival at the original final destination.