Claim assessment record
- Entity
- Split Airport
- IATA
- SPU
- Country
- Croatia
- City
- Split
- Regime marker
- eu
- Catalogued
- 2026-07-19
This Split Airport guide converts airport evidence into a structured route-and-carrier claim assessment. Use the sections as a case file: identify the operator, prove the route and timing, document the cause and request a reasoned decision.
What this SPU guide does not verify
Terminals, handlers, airlines and routes at Split Airport can change. This record uses the catalogue location Split, Croatia, regime marker eu and code SPU; it is not a live flight-status or terminal service. Confirm the current operating carrier and official contact channel before sending personal data. No compensation or reimbursement outcome is guaranteed.
Turn the Split Airport record into a claim chronology
Build the request in route order: origin, Split Airport's role, operating carrier, disruption, replacement journey and final arrival. Attach the airport log behind that chronology. State the reason given and each remedy separately, so the airline can answer timing, expenses and compensation without treating the submission as an unexplained collection of screenshots.
Compare the replacement offered at Split Airport
Ask for the earliest reasonable route to the final booked destination, not merely the next flight from SPU to the same airport. Compare terminal changes, ground transfers and connection protection. If the passenger accepts reimbursement instead, record which sectors are unused and whether the journey has lost its purpose.
Hotel and transport around SPU
Even where compensation is uncertain, assistance can be relevant during a long wait at Split Airport. Request care first and document any refusal. When paying personally, preserve the receipt and choose a reasonable substitute rather than assuming that every cost incurred in Split will be reimbursed.
Airport information versus airline responsibility
The airport can explain gates, terminals, closures and local operations, but the operating airline is normally the starting point for care, rerouting, reimbursement and compensation. Preserve any Split Airport announcement because it may help explain the event, then direct the remedy request to the correct carrier unless a separate airport complaint is genuinely relevant.
Record the disruption while still at SPU
Use a timestamped note for Split Airport: scheduled event, actual event, announcement, airline response and passenger decision. Keep the airport evidence alongside the booking rather than as isolated photographs. This makes it clear how each image relates to delay, cancellation, rerouting or a missed connection.
Measure the connection impact at the final destination
Use Split Airport as the middle point in the chronology, not automatically as the place where the legal delay is measured. Preserve boarding passes for every sector and the replacement itinerary. This allows a reviewer to see whether the disruption at SPU affected a single through-journey or two unrelated bookings.
Carrier status matters on journeys ending at Split Airport
For a journey arriving at Split Airport, record the origin and operating carrier. An inbound EU/EEA assessment can depend on whether the operator has EU/EEA status, unless the journey was already covered from its departure point. Use the full itinerary and one-booking connection structure.
Coverage questions for a journey beginning at Split Airport
A journey departing from Split Airport is catalogued within the EU/EEA departure framework. Confirm the operating carrier and full booking, but carrier nationality is not normally the first barrier for an EU/EEA departure. Keep immediate care and travel remedies separate from the cause-based compensation assessment.
Use SPU as the airport evidence anchor
Split Airport uses IATA code SPU and serves Split, Croatia. The catalogue marks the airport regime as eu. That location marker helps organise the route test, but it does not replace the full itinerary, travel direction or operating-carrier identity. Record whether SPU was the original departure, final arrival or a connection point.
Verification and legal limitation
This page is general passenger-rights information, not legal advice, live flight data or a promise of payment. The structured record for Split Airport was last catalogued on 2026-07-19. Verify the current itinerary, operating carrier, official channel, law and procedural deadline before acting.
Care, reimbursement, rerouting, expenses and fixed compensation are separate questions. Eligibility and outcome depend on the complete facts and are not guaranteed.