Claim assessment record
- Entity
- MAN to LIS journey rights
- From
- MAN
- To
- LIS
- Catalogued
- 2026-07-19
This guide builds a route-led claim assessment for Manchester Airport (MAN) to Lisbon Airport (LIS) without inventing live service data. The page begins with eligibility facts and chronology, then builds the evidence, remedy and response-review stages.
Do not use departure delay as the only time figure
The route file should explain where and when the passenger finally arrived. A cancellation followed by rerouting may use another airport or ground transport. Preserve that alternative path so the reviewer can calculate the impact without assuming the original LIS sector operated.
Waiting, hotel and replacement travel
Ask the operating airline for meals, accommodation and transport when the relevant waiting conditions arise. Decide separately whether to continue to LIS by rerouting or abandon unused travel for reimbursement. Keep itemised receipts and the alternatives offered; the cause of disruption does not automatically eliminate every care duty.
Link the disruption event to the affected sector
A route-based claim is easier to review when the cause is placed on the timeline. State when it arose, which operator reported it and which part of the MAN–LIS itinerary it affected. Preserve later explanations if the initial message changes.
What proves this airport-pair case
- Complete booking showing MAN as departure and LIS 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
Add a one-line description to each attachment. The aim is a navigable evidence pack, not an unlabelled archive.
Present the MAN–LIS case
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.
A MAN–LIS case worksheet
- MAN departure: record the scheduled local time, terminal and check-in evidence at Manchester Airport.
- MAN operator: name the company that operated the disrupted sector leaving United Kingdom.
- MAN notice: preserve the first delay or cancellation message and its timestamp.
- MAN assistance: list meals, hotel, transport or rerouting requested before the journey continued.
- MAN–LIS booking: state whether the airport pair sat on one reservation or separate tickets.
- MAN–LIS disruption: identify the affected sector, stated cause and replacement path.
- LIS destination: record whether Lisbon Airport was the final booked destination or an intermediate point.
- LIS arrival: preserve the scheduled and actual arrival times and the source used for each.
- LIS expenses: connect each receipt to the wait, overnight stay, ground transfer or substitute journey.
- United Kingdom to Portugal review: verify the applicable regime and procedural deadline before escalation.
A completed MAN–LIS worksheet gives the respondent a route-specific chronology and prevents generic assertions from replacing the booking, operator, timing and cause evidence.
Why this MAN–LIS page remains a legal reference
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.
Do not assume an airport pair is a verified nonstop service
The useful route fact is direction: departure at MAN and booked destination LIS. 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.
How the uk departure and eu arrival interact
The MAN departure is catalogued in the UK framework, so UK261 is the primary route screen. The LIS 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 MAN–LIS journey
Record the operating carrier for each sector. A booking platform may show one brand while another airline operates the aircraft. On a connecting MAN–LIS journey, the disrupted sector and the carrier status can affect coverage. Keep flight numbers, boarding passes, code-share wording and every replacement itinerary.
Separate tickets change the MAN connection risk
The booking structure determines which final arrival matters. If LIS is only an intermediate point on one reservation, use the actual final booked destination. If the passenger held separate tickets, explain that fact and assess each contract rather than assuming through-journey protection.
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 MAN to LIS journey rights 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.