Industry · Aviation
JUNE for Airlines: one decision per flight
One delayed flight can bring 180 claims. JUNE for Airlines links every passenger claim to its flight, including the claims still to come. Your legal team decides once per flight, and JUNE applies that decision to every claim that lands on it.
Trusted by legal teams at
The challenge
Each claim is small. The wave is not.
Claim portals make it easier than ever to file for compensation under EU261. When a flight is delayed or cancelled, the whole cabin is affected and many passengers miss their connections. A single flight can trigger dozens, sometimes hundreds, of near-identical claims.
For airlines this creates a costly dilemma: reviewing a small claim properly often costs more than paying it, while paying without review opens the door to duplicate payouts and abuse. And working out what actually happened on a flight has often meant querying customer service, booking and payment systems separately for every single case.
- 01 Reviewing a claim often costs more than the claim
- 02 Unreviewed payouts invite duplicates and abuse
- 03 Flight facts rebuilt case by case from separate systems
How JUNE runs it
From intake to resolution, step by step
- 01
The flight becomes the unit of work
Every flight is identified by flight number, date and departure airport. As soon as a claim comes in, JUNE links it to the right flight, and every further claim joins the same flight cluster automatically.
- 02
Decide once per flight
One Handling Instruction per flight – for example “do not contest” – applies to every linked claim, including claims filed weeks later. Passenger-specific checks remain possible at any point.
- 03
Defend in-house, with your panel firms
Automation lets your team handle more first-instance proceedings internally. External firms work in secure Collab Spaces on the same data – without email chains.
Key capabilities
- Flight clusters
- Handling Instructions
- Structured flight view
- Flight data from any source
- Delays, cancellations and denied boarding
- Panel firm collaboration
JUNE for Airlines in five instructions
Legal teams steer their strategy across flights, routes and legs instead of case by case. Five examples from day-to-day work:
- 01
“Set flight XY123 on 3 March to ‘do not contest’.”
One Handling Instruction is enough. Every claim already linked to the flight carries it, and so does every claim that arrives later. Whoever opens a case file sees right away which flight it belongs to and how the flight is being handled.
- 02
“Air traffic control strike on Friday. Create all affected flights now.”
Flights can be created before the first claim arrives. When the wave of claims comes in, every matching claim attaches to its flight automatically, and the strategy is already in place.
- 03
“What actually happened on this flight?”
Delays and delay codes, cancellations, passenger and boarding information, aircraft work orders and customer communications in one structured flight view. Whether a case can be defended becomes clear at a glance.
- 04
“Contest all claims for the delayed rotation between Munich and Barcelona.”
Handling Instructions can be set for several flights at once, so legal teams manage their strategy across flights, routes and legs.
- 05
“Show me everyone who has filed for this flight.”
Every claim linked to a flight appears in one list, with opposing party, court, case handler, status and claim amount.
Why teams choose JUNE
What makes the difference
In use at Europe’s airlines
JUNE is in use at the legal departments of airlines such as Lufthansa, Austrian Airlines, Discover and British Airways, and adapts to your processes and legal ecosystem.
View case studiesFlight data from any source
Your own systems and data interfaces, commercial flight data providers or manually maintained flight information: whatever the source, JUNE presents the data in one standardised flight view.
EU261 claims management
Compensation of €250–600, the reform under Regulation (EU) 2026/2202 – information within 96 hours after the end of the journey and payment or justified refusal within 30 days from 23 October 2027: how JUNE runs EU261 claims at scale.
EU261 in detailPress release: JUNE for Airlines
One delayed flight. 180 claims. One decision. Read the announcement with statements from founders Katja Nikolaus and Christian Häp.
Read the press releaseCustomer result
20 min
response time per case – previously days or weeks
- One Data Platform Lufthansa’s data platform plus JUNE as the legal workflow layer
- EU261 passenger lawsuits handled in a digital, data-driven process
“With JUNE, we’ve transformed our previously analog and largely paper-based handling of passenger claims into a digital, data-driven process. The platform provides us with the relevant information for each case in the shortest possible time and enables secure collaboration with our external law firms. What previously required time-consuming manual coordination, we now complete in just a few minutes with greater accuracy and full transparency across all teams.”
Enterprise-grade security
- ISO 27001 certified
- SOC 2 certified
- EU hosting data stays in the EU
- GDPR compliant processing
Related
Where else JUNE runs the process
Travel & transport
Rail, bus, ferry and tour operators automate passenger and disruption claims under EC 1371/2007 and EC 181/2011 with JUNE – from intake to resolution.
ExploreClaims handling
Industry-neutral claims automation: capture, validate and resolve high-volume claims with straight-through processing and full auditability in one platform.
ExploreLegal departments
Run high-volume and complex matters in one system, steer external counsel in secure Collab Spaces and report on your whole legal portfolio in real time.
ExploreSee JUNE run your aviation process
Bring a real workflow. We’ll show you how JUNE would take it from intake to resolution – and tell you honestly if it isn’t a fit.