For OCC and operations leadership

Your OCC stops being
the evidence archive.

Months after a disruption, an authority asks for the NOTAMs, the slot messages, the delay codes and the duty manager's notes — and the request lands on your desk. Cura pulls every one of those sources over an API the moment the request arrives, drafts the response in the authority's own structure and files it. Nobody in operations is asked for anything.

Book a Demo See how it works arrow_downward
checkReceived cachedIn Progress
mark_email_unread Authority request arrives Authority
checkCollected cachedPulling
storage Evidence collected Cura
Weather, NOTAMs, CTOT, delay codes, booking — pulled in parallel
checkDrafted cachedDrafting
edit_note Response drafted AI agent
Cause categorised, delay attributed minute by minute
checkFiled cachedIn Review
how_to_reg Approved and filed Claims

Every escalation ends the same way: someone in operations digging through March.

A national authority writes to the airline eleven weeks after the flight. Legal cannot answer it without you — so the request becomes a favour, then a chase, then a deadline.

NOTAM archives Screenshots of METARs Duty manager notes Delay code disputes Slot messages 20 working days A deadline you didn't set
The change

The request never reaches your team.

Same escalation, same authority, same deadline — a completely different week for the people running the operation.

Today

Evidence is assembled by memory, months late.

  • scheduleLegal emails OCC asking what happened on a flight from three months ago.
  • folder_offNOTAMs, CTOTs and weather have to be reconstructed from whatever was saved on the day.
  • person_searchThe duty manager who worked that shift may not be the one answering.
  • gavelThin evidence means paying claims the airline should have defended.
With Cura

Evidence is sealed at the moment of the disruption.

  • boltEvery source is fetched over an API the moment the request lands — in parallel, in minutes.
  • lock_clockWeather, minima and NOTAMs are stamped at the time of the disruption, not recalled later.
  • notifications_offNo one in OCC is interrupted. The read-only API is wired up once, at onboarding.
  • shieldThe airline defends what it can defend, on the record, with a checksum per document.
How it works

Data in. Filed package out.

When a passenger escalates to the authority or to court, this is every source that goes into the file, who supplies it, and what happens next. Every source is fetched over an API — the only thing anyone at the airline does is approve the response for sending.

Stage one

Intake and collection

A request arrives with a reply deadline. Cura reads it and matches it to the claim — or opens one, if the passenger never claimed with the airline and went straight to the authority. Then every evidence source is pulled at once over an API. Nothing here is a request to a person, and nothing waits on one; the connections below are set up once, at onboarding.

checkReceived cachedIn Progress
mark_email_unread Request arrives Authority
checkMatched cachedIn Progress
smart_toy Read and matched AI
  • Claim found — matched to the case on file
  • No claim — new case is opened
checkCollected cachedIn Progress
storage Evidence collected Cura
Pulled in parallel, gaps flagged
Cura has it

Weather, minima, NOTAMs, flight details

Held continuously and stamped at the time of the disruption, so the record does not depend on anyone remembering to save it on the day.

Cura, via granted access

Slot messages, CTOT, Eurocontrol messages

Retrieved on your behalf. This is what turns "ATC delay" from an assertion into something the authority can check.

From your API

Booking, check-in, delay codes, ops notes

A read-only API into your systems, wired up once. After that it is pulled automatically on every case and any gap is flagged rather than filled with an assumption.

Stage two

Draft, approve, close

The agent writes the response in the authority's structure and hands the handler one screen. Approving it for sending is the only human step on this page — before it and after it, everything runs on its own.

checkDrafted cachedDrafting
edit_note Response drafted AI agent
  • Cause categorised and the delay attributed minute by minute
  • Each requested item answered in turn, in the authority's structure
  • Annexes indexed, with source and integrity check
  • Defend-or-settle recommendation for the handler
checkFiled cachedIn Review
how_to_reg Approved and filed Airline → Cura
Read and press send — the only human step. Cura files it and stores the receipt.
checkRecorded cachedAwaiting
gavel Ruling recorded Cura
Outcome and reasoning captured — and fed back, so every ruling sharpens the drafting agent and the defend-or-settle recommendation
In practice

What they ask for, and what goes back

A real request lists its items and expects each one answered. The package mirrors that list item for item, so the case handler on the other side can tick their way down it.

Request for documentation — case ref. EU-2026-04178
From
passengerrights@authority.example
To
claims@airline.example
Date
12 March 2026 · reply due 11 April

Dear Sir or Madam,

We have received a complaint concerning the diversion and subsequent delay of the above flight. In order to properly progress with this matter, we kindly request that you provide the following documentation:

  1. All relevant slot messages, including the original CTOT, any revised CTOTs, and related NOTAMs
  2. All NOTAMs valid at the relevant time for the route, departure airport, destination airport, and alternate/diversion airport
  3. All relevant Eurocontrol messages, communications, or network management notifications that influenced the CTOT allocation, delay, or diversion decision
  4. Any other operational messages, weather reports, or internal communications that may be material to understanding the cause and handling of the diversion and delay

Please note that a failure to reply within the period stated above may lead us to determine the matter on the basis of the information already before us.

Yours faithfully,
Case Officer, Passenger Rights Unit
arrow_forward
Re: Request for documentation — case ref. EU-2026-04178
From
claims@airline.example
To
passengerrights@authority.example
Date
14 March 2026 · 28 days before the deadline

Dear Case Officer,

Further to your request of 12 March, please find our response to each item below, in the order set out in your letter. The supporting documents are attached as Annexes A to D.

  1. Slot messages and CTOT historyOriginal CTOT, both revisions and the related NOTAM — Annex A
  2. NOTAMs valid at the relevant timeRoute, departure, destination and alternate aerodrome — Annex B
  3. Eurocontrol and network management messagesThe regulation that set the CTOT, with the message log — Annex C
  4. Operational messages and weather reportsMETAR and TAF, approach minima and the diversion decision trail — Annex D

The cause has been categorised and the delay attributed minute by minute in the covering note at Annex A. We remain at your disposal should any further material be required.

Yours faithfully,
Claims Team, Airline Claims
descriptionAnnex A descriptionAnnex B descriptionAnnex C descriptionAnnex D
lock Each annex indexed with its source and a checksum — sha256:8f3c…a91d
Learning

It gets better with every case.

Three signals feed back into the drafting agent — two from day one, one when the rulings land.

Edit diffs

boltDay one

Every paragraph an agent rewrites. Eight rewrites in ten is a template problem — fixed the same day.

Overrides

boltDay one

Every time an agent pays against a defend call, with the reason. Expert judgement, months before the verdicts.

Rulings

hourglass_topGround truth

Parsed argument by argument: dismissed in 11 of 14 cases resting on an operations log alone.

functions Counting, not training. Rates you can inspect, trace to real cases and defend in a dispute — not a model nobody can explain to a regulator.

See it run on one of your own flights.

Book a Demo