Stays on this device
Your input, progress, and letters are in browser storage. Original photos and PDFs are in IndexedDB.
Your input, progress, and letters are in browser storage. Original photos and PDFs are in IndexedDB.
An address or flight lookup sends only the search details. An AI feature sends only the required text, file, or a limited part of your form. You choose this for photos and messages; in a few situations, a comparison with a fixed list of tips starts automatically.
There is no account. Vluchtclaimhulp does not write your form content, files, or AI answers to application logs.
Plausible counts general visits and fixed action categories without cookies, never your claim text, flight, airline, amount, or case ID.
This deletes only photos, screenshots, PDFs, and receipts on this device. Airports, names, IBAN, text fields, progress, and letters remain.
For a photo or message, you see in advance that AI will be used and can enter the data manually. The automatic tip check starts only after several saved messages, denied boarding with a saved message, or a difference between the ticketed and operating airline; this check cannot be switched off.
A selected step sends only the chosen file or text. The automatic check uses part of the form and up to four message excerpts of 300 characters each, without your name, address, bank account number, or flight number. OpenRouter forwards this to the model provider. Zero retention is not guaranteed, and processing may take place outside the EEA.
You can correct copied or classified text. The automatic check selects only an existing tip and a visible label; fixed conditions remove a tip that does not fit. The browser keeps the shortened comparison and result for up to 24 hours.
The tool sends only the data needed for its AI features to OpenRouter and a model provider. Vluchtclaimhulp does not keep that content in a central claims database; your own progress does stay locally on this device.
Explanation reviewed on 31 July 2026 against the European Commission's final guidelines.
Vluchtclaimhulp uses AI as an input and comparison aid. The tool does not assist a judicial authority and does not make a decision with legal effect. In our assessment, its current design therefore does not fall within the categories in Annex III of the AI Act. The transparency rules in Article 50 remain relevant.
Check every reference in the letter before sending. The letter is assembled from fixed legal templates and the checked sources below; AI does not write or select the citations. Errors remain possible, and you are the one submitting it.
Passengers on a flight with an arrival delay of three hours or more are entitled to the same flat-rate compensation as passengers on a cancelled flight (Article 7).
Confirms and reinforces Sturgeon: passengers on a flight with an arrival delay of three hours or more are entitled to flat-rate compensation. The Court explicitly holds that Article 7 of Regulation 261/2004 is compatible with the Montreal Convention and with the principle of legal certainty.
On connecting flights the relevant delay is measured at the FINAL DESTINATION, not at a connection. An arrival delay of three hours or more at the final destination gives rise to compensation even if the first flight departed on time or the connection was reached on time.
The 'distance' under Article 7 of Regulation 261/2004 is the great-circle distance between the original point of departure and the final destination. Connections do not count toward the distance band. This prevents a carrier from influencing the band by choosing a routing detour.
A technical problem on an aircraft arising during maintenance or due to defective maintenance does not constitute 'extraordinary circumstances': it is part of an air carrier's normal operations. Only problems beyond that (e.g. a hidden manufacturing defect announced by the manufacturer) may fall outside this scope.
An unexpected technical fault that does not result from defective maintenance and was not detected during scheduled maintenance is not an extraordinary circumstance if the fault arises from the regular functioning of the aircraft. Confirms and reinforces Wallentin-Hermann.
A collision between an aircraft and a bird constitutes an 'extraordinary circumstance'. The carrier remains required to show it took all reasonable measures to limit the consequences. Delay attributable to an avoidable additional inspection does not count as a consequence of the extraordinary circumstance.
A 'wildcat strike' by a carrier's own staff in response to a surprise restructuring announcement does NOT fall within 'extraordinary circumstances': such labour unrest is inherent to the carrier's normal operations and within its actual control. The concept of 'extraordinary circumstances' must be interpreted strictly.
Failure of the airport's fuel-supply system can be an extraordinary circumstance when that system is operated by the airport and therefore lies outside the carrier's actual control. Operational system failures that do fall within the carrier's control are not.
An unexpected, previously-unseen technical fault on a new aircraft type — where the manufacturer subsequently acknowledges a hidden design defect affecting all aircraft of that type and impacting flight safety — falls within 'extraordinary circumstances'. This is an exception to Wallentin-Hermann/Van der Lans and applies only to manufacturer-acknowledged hidden design defects.
The 'reasonable measures' test requires the carrier to build buffer time into its planning and operations so that, given foreseeable disruptions, it can still depart on time. A carrier with no schedule margin cannot simply rely on extraordinary circumstances — the minimum necessary preparation is part of normal operations.
A screw or other foreign object debris (FOD) on the runway that damages an aircraft tyre is an extraordinary circumstance. This differs explicitly from technical faults arising from the normal functioning of the aircraft: the cause of damage lies outside the carrier's control and responsibility.
The sudden and unexpected death of a co-pilot shortly before scheduled departure, requiring the flight to be cancelled, is NOT an extraordinary circumstance. Though tragic and unforeseeable, the general event 'unexpected loss of a crew member' is part of the carrier's normal operations and within its actual control — comparable to the Krüsemann reasoning on staff unrest.
A lightning strike on an aircraft during the previous flight, requiring a mandatory safety inspection and resulting delay, falls within 'extraordinary circumstances'. A lightning strike is not inherent in the normal operation of aviation activity and lies outside the carrier's actual control. The carrier must still demonstrate it took all reasonable replacement / re-routing measures.