Journey structure
Origin, destination and relevant segment facts are kept distinct so the system does not invent an itinerary.
Missed connection
Missed a connection? The whole journey can matter more than one flight segment.
A connection problem can involve multiple segments, carriers and arrival consequences. AeroDue keeps the journey structure explicit and suppresses conclusions that require facts you have not confirmed.
Check this journeyWhat AeroDue checks
Arrival impact
Where supported rules depend on the final journey outcome, the required facts are requested explicitly.
Other disruption rights
Care, expenses or other supported entitlements can remain visible independently from compensation.
What the result keeps clear
No invented connections
Unknown booking or itinerary relationships are not assumed.
Rule-level provenance
Supported conclusions show the legal rule and sources used.
External next step
A provider is offered only when its configured capability fits the case.
The page describes the problem at a safe generic level. Eligibility and any monetary value are decided only by the supported Rights Engine rules for the confirmed journey facts.
Check this journey
Describe the missed connection and let AeroDue check the supported journey-level passenger-rights rules without guessing missing itinerary facts.
Check this journey →