Direct answer: before an airline, OTA, tour operator or travel-ops assistant **auto-sends** a delay or cancellation message that mentions passenger options, care, refunds, re-routing or compensation under **UK Reg (EU) No 261/2004** (UK261), the product must already know — from operational systems, not from model improvisation — (1) whether UK261 is in scope for that flight, (2) whether the event is a delay vs cancellation vs denied boarding, (3) which **care** thresholds apply, (4) which **choice** (refund / re-route earliest / re-route later) must be offered on cancellation, and (5) whether any **compensation** wording is allowed given extraordinary-circumstances rules and notice windows. If those facts are missing, the assistant may draft internal ops notes — it must not invent rights language to the passenger.
That is the operator question Kaize is answering here. We are a UK AI product studio for travel and hospitality. Disruption messaging sits in the same class as other confirmation stacks we write about: the model is not the source of legal truth. UK261 obligations live in the booking and ops systems; AI is a delivery and drafting layer that must be gated.
Primary evidence is first-party UK Civil Aviation Authority material: the CAA passenger pages on delays and cancellations, the CAA Guidance to Industry – 9 September 2026 on the NATS flight-planning disruption of 8 September 2026, and the CAA newsroom statement on passenger compensation following that NATS disruption. Assimilated UK261 text (including the Article 14 duty to inform passengers of their rights) is on legislation.gov.uk. No invented claim volumes, no fictional airline outcomes, no invented GSC or GEO metrics.
Why this is distinct from AI rebooking controls
Kaize already covered what AI may **prepare** versus what humans must **confirm** when tour operators rebuild itineraries after disruption — see AI rebooking for UK tour operators. This article is adjacent but different: it is about the **rights notice and options language** that goes out in SMS, app push, email or chatbot when a flight is delayed or cancelled under UK261. Rebooking inventory logic is one stack. Passenger-rights disclosure and care/refund/re-route choice is another. Collapsing them into one “disruption AI” prompt is how operators ship confident-sounding messages that misstate compensation or bury the refund choice.
When UK261 is in scope — and when the assistant must stay silent
Per the CAA cancellations guidance, UK law passenger rights under UK261 apply when the flight is either departing from a UK airport on any airline; arriving in the UK on a UK or EU airline; or arriving in the EU on a UK airline. The CAA’s September 2026 industry guidance restates that Assimilated Regulation 261/2004 applies to all flights departing from the UK, and to flights arriving into the UK on UK and EU carriers — and that **different rights may apply** to passengers arriving on flights to the UK operated by non-EU carriers (for example some US-carrier arrivals).
An AI notifier that cannot resolve carrier nationality, departure airport country and arrival airport country from the PNR/flight record must not assert “you are entitled to UK261 compensation” or even “your UK261 rights are…”. It can say the airline will confirm applicable rights, or route to a human — it must not fill gaps with plausible law.
Care obligations the message must not invent
For **delays**, the CAA states passengers are entitled to care after scheduled departure delay of at least two hours (flights under 1,500km), three hours (1,500–3,500km), or four hours (over 3,500km). Care includes food and drink based on delay length, two phone calls or emails, and overnight accommodation plus transport when delayed overnight — **regardless of the reason for the delay**. For **cancellations**, airlines must provide care and assistance while passengers wait: reasonable food and drink, a means to communicate, accommodation if re-routed the next day, and transport to/from that accommodation (or home).
The CAA is also clear that if the airline cannot arrange care during major disruption, passengers may make reasonable arrangements themselves and claim costs back — keeping receipts, avoiding luxury spend. Automated messages that imply “no help is available” without pointing to that path, or that invent voucher amounts the airline has not authorised, fail the control stack.
Cancellation choice: refund vs re-route — not a model preference
On cancellation in UK261 scope, the airline must let the passenger **choose** between: (1) a refund for unused ticket parts (with return-to-origin rules for some transfer cases), or (2) an alternative flight — as soon as possible after the cancelled flight, **or** at a later date that suits the passenger. The CAA’s September 2026 industry guidance repeats that obligation and notes that “re-routing at the earliest opportunity” is fact-specific in major disruption — but the **choice** itself is not optional marketing copy.
What the assistant may draft: a message that surfaces the three options the ops system has already authorised for that booking state, with deep links or agent handoff. What it must not do: pick the commercially convenient option for the airline, hide the refund path, or invent “earliest opportunity” flights that are not actually bookable in the inventory system.
Compensation wording: thresholds, notice windows, extraordinary circumstances
Compensation is **not** automatic. For long delays, the CAA explains passengers may claim fixed-sum compensation if they arrive more than three hours late at the destination airport, subject to extraordinary circumstances. For cancellations, entitlement depends on notice period and the timings of the alternative flight offered — with tables for seven-to-fourteen days’ notice and less-than-seven-days’ notice on the CAA cancellations page. Amounts are distance-based (examples on CAA pages include £220 / £350 / £520 bands).
Extraordinary circumstances matter. After the **8 September 2026 NATS flight-planning outage**, the CAA’s 9 September guidance to industry said delays and cancellations on 8 September caused by that technical issue — and delays/cancellations **directly caused by knock-on effects** — are **likely** extraordinary circumstances, so passengers are **unlikely** to be entitled to compensation in those circumstances. The same note says that interpretation is **illustrative guidance**, not determinative of every case, and passengers may still try to claim. Care and the refund/re-route choice still apply.
That is exactly why compensation language must be a gated component: an assistant that auto-promises “you will receive £520” after an ATC outage, or that auto-denies all claims forever because “CAA said extraordinary circumstances,” is inventing a determination the CAA itself labelled non-determinative. Safe patterns: state care and choice obligations; link to the airline claims process; quote CAA guidance as guidance where the ops policy team has mapped the incident code; never let the model adjudicate extraordinary circumstances from free text.
Article 14 — informing passengers of their rights
UK261 Article 14 requires the operating air carrier to inform passengers of their rights — including a written notice setting out compensation and assistance rules when boarding is denied or a flight is cancelled, and an equivalent notice for delays of at least two hours. The CAA’s NATS guidance explicitly reminds airlines to keep passengers informed **and advise them of their rights**. An AI channel that sends only “sorry for the inconvenience” without rights information is not a complete disruption stack — but inventing rights text without the legal/ops map is worse than a thin apology.
What the assistant may draft vs what must stay human- or system-owned
What the assistant may draft
- **After** flight-event, UK261-scope, care-threshold and option-set components return ALLOW: clear passenger messages that restate the authorised care steps and the refund/re-route choices the booking system exposes.
- Internal ops summaries: which passengers are past care thresholds, which cancellations still lack a recorded passenger choice, which incident codes map to “compensation guidance: unlikely / case-by-case.”
- Links to CAA passenger pages and the airline’s own claims ADR/PACT paths — as static approved URLs, not model-invented procedures.
- Drafts for human agents that highlight missing PNR fields (carrier nationality, connection type, self-transfer vs single ticket) before any rights assertion.
What must stay system-owned or human-confirmed
- Whether UK261 applies to this specific flight leg.
- Whether the event is delay, cancellation or denied boarding in the airline’s source-of-truth ops feed.
- Authorised care offers (vouchers, hotels) and inventory for re-routing.
- Any fixed-sum compensation eligibility determination, including extraordinary-circumstances classification for a named incident.
- ATOL / package overlays when the flight sits inside a package — do not collapse package rules into UK261-only copy; see also Kaize’s package travel booking-journey and ATOL disclosure articles.
Product controls (not prompt tips)
Kaize point of view
After events like the 8 September 2026 NATS outage, the commercial pressure to “just send something” is enormous. The CAA’s own industry note still puts care, information and the refund/re-route choice at the centre — while treating compensation under extraordinary circumstances as guidance, not a chatbot verdict. Travel companies that want AI in disruption channels should implement UK261 as **deterministic product components** on top of flight and booking systems, then let models draft within those envelopes. That is how Kaize builds travel AI: connect the real stack, put gates where law and ops truth live, and keep generative language away from inventing passenger rights. For the adjacent rebooking problem (what may be prepared vs confirmed), see our AI rebooking controls. For why ungated assistants fail in live ops, see what usually breaks in production.
FAQ
Can an AI tell passengers they will not get compensation after an ATC outage?
Not as a hard determination invented by the model. The CAA’s September 2026 NATS guidance says compensation is **unlikely** for delays/cancellations caused by that outage and direct knock-ons, labels that view as guidance, and notes passengers may still claim. Messages should follow a compliance-approved incident policy and still cover care and cancellation choice.
Does care still apply when extraordinary circumstances apply?
Yes. CAA delay guidance states care is due regardless of the reason for the delay. The NATS industry note likewise reminds airlines to look after passengers with meals, refreshments and hotel accommodation proportionate to delay length.
Is this the same as package-travel or ATOL AI disclosure?
No. UK261 is an operating-carrier passenger-rights regime for covered flights. Packages and ATOL-protected sales add separate disclosure and organiser duties. Do not let one AI template satisfy both without separate gates.
What should tour operators who sell flight-inclusive packages watch?
Keep UK261 flight-leg messaging aligned with the airline/operating-carrier facts, and keep package organiser communications on their own rules. Where your assistant speaks to the traveller, label which legal stack the message is executing — and block sends when the booking type is ambiguous.