Claim Compensation for a London Gatwick Airport to Split Airport Flight

Define the LGW–SPU itinerary

The useful route fact is direction: departure at LGW and booked destination SPU. Verify whether those points belong to one protected booking, whether another airport was used after rerouting and which carrier operated the disrupted sector. The catalogue deliberately avoids claiming current service frequency.

Coverage screen for LGW to SPU

The LGW departure is catalogued in the UK framework, so UK261 is the primary route screen. The SPU arrival marker is eu. If the journey reaches the EU/EEA, EU coverage should be considered from the real route and operating carrier, not assumed merely because the destination is European.

Identify every operating carrier on the LGW–SPU journey

Do not choose the respondent solely from the logo on the confirmation. Match the flight designator and operating-carrier line for the sector that failed. If rerouting introduced a different airline, preserve both the original and replacement operators so the chronology remains clear.

Follow the protected itinerary to the final destination

Use the reservation reference to prove whether the journey from LGW to SPU 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 LGW–SPU case

Create a time line with scheduled departure from LGW, disruption notice, replacement departure and actual final arrival. State whether the time comes from the airline, airport, boarding record or another source. Avoid rounding a threshold from memory.

Waiting, hotel and replacement travel

For a long wait after leaving or before leaving LGW, document what assistance was requested and provided. If an overnight stay or reasonable replacement became necessary, preserve the airline response and cost. A claim should list care expenses separately from the compensation request.

Link the disruption event to the affected sector

Ask which sector was affected, what event occurred and how it prevented the planned journey. A broad label such as weather or operational reasons does not by itself show the causal link. Keep notices for both LGW and SPU, because conditions at another airport or on an earlier aircraft rotation may also be cited.

Evidence pack for LGW to SPU

• Complete booking showing LGW as departure and SPU 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.

From itinerary summary to airline response

Use one paragraph for eligibility facts and a separate table for money requested. This prevents reimbursement, care expenses and fixed compensation from being combined into an unexplained total. Verify the relevant deadline and escalation forum for the jurisdiction before proceeding.

Complete the London Gatwick Airport to Split Airport route record

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

A completed LGW–SPU 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.