Within 48 hours of the Houthi strikes on Saudi airports, the reinsurers behind local aviation insurers moved, according to market brokers, to cancel AVN52E and AVN52G war liability from Oct. 19 and to cut hull war notice from seven days to 24 hours. Cancellation is the tool of a market that cannot see its exposure.
A month earlier, Lloyd's CFO had described its £1.4bn Iran conflict estimate as "heavily based on exposures and estimates as opposed to really hard numbers." The peril was known. The data was not — and so the risk was underpriced: a Grey Rhino.
Why the response was blunt
Saudi airlines bought cover from a licensed local insurer, which ceded up to 100% to international reinsurers, largely in London. Lessors and lenders sit above, setting minimum limits and reinsurer quality in each lease. Every link held part of the big picture: the reinsurer an annual fleet schedule, the insurer policy PDFs, the lessor covenants in legal documents. Nobody holds where aircraft are parked tonight or how many people were in each terminal. With a partial picture, the safe answer was to cut exposure and renegotiate.
The result was 24-hour notice.
Five data gaps that stood out
Whether an organization builds, buys or partners, a few principles tend to separate what works from what stalls:
- Aircraft location. What the chain holds: annual fleet schedule and agreed values. What is needed: value on the ground by airport and by hour, from schedules and ADS-B flight tracking. What it unlocks: caps per airport instead of fleet-wide withdrawal.
- Passenger and terminal exposure. What the chain holds: terminal values, if declared at all. What is needed: footfall by terminal and time of day. What it unlocks: liability priced to the real casualty risk.
- Policy wordings. What the chain holds: PDFs at each link in the chain. What is needed: clause-level data on AVN52, notice periods and event definitions. What it unlocks: knowing which contracts respond before the dispute.
- Lease covenants. What the chain holds: legal documents held by lessors. What is needed: minimum limits and reinsurer rating rules held as data. What it unlocks: early warning of covenant breaches.
- Threat. What the chain holds today: headlines and broker notes. What is needed: scenarios built on range, interception rates and target patterns. What it unlocks: pricing by scenario, not by panic.
What it costs not to know
- Capacity. Withdrawn capacity comes back at a higher price, and good and bad risks are priced alike because nobody can tell them apart.
- Credit. Without lease data, nobody knows which aircraft breach minimums until the lessor's letter arrives.
- Claims. Whether a week of strikes is one event or six, and whether passengers in a terminal were "embarking" under Day v TWA (1975), will be argued from documents, not data.
- Capital. Reserves set on estimates tie up capital that could support new business.
Lessons learned
- Make data a condition of capacity. Price exposure data quality into the rate, as property catastrophe reinsurance did with location-level schedules.
- Set one data standard across the chain. One exposure record from airline to retrocession, aligned to ACORD standards, entered once rather than re-keyed at every step.
- Monitor accumulation live, not annually. Combine schedules, flight tracking, seat-booking and airport data — historical footfall by terminal-gate to show value on the ground by airport and by hour.
- Digitize wordings before the dispute. Turn AVN48B, AVN52, notice and event-definition clauses into structured data so the market knows which contracts respond.
- Build a 72-hour playbook. After an event on a known peril, produce an exposure report within 72 hours with options to reprice, cap or sub-limit, not just cancel.
How the market can close the gap
The gap is not a technology gap. Insurers, reinsurers, brokers and lessors already have systems. What is lacking is a joined-up view across firms that do not share data. That makes it a market problem first. Who builds the capability matters less than whether the chain agrees what to share, in what format and with whom. Some will build it in-house, some will buy it, and some will pool it through a market body. The steps are the same in each case:
- Diagnose. Pick one program and measure what better data would change: capacity retained, price spread between airports and capital held against estimates.
- Agree. Settle a common exposure standard, data rights and residency rules before building anything. Sensitive data, such as live terminal occupancy, stays in-country.
- Build. Start with what needs no outside cooperation, such as aircraft location from schedules and tracking, and clause data from wordings. Add footfall and covenant data as access is agreed.
- Govern. Run the shared data under neutral rules, so each party sees what it needs and no more, and test it against the 72-hour standard after each event.
The wider question to answer
Saudi Arabia is one example, and not the only one. Any country building its economy around aviation hubs, tourism or global events needs airports that are insurable, not just open. With Expo 2030 and the 2034 FIFA World Cup ahead, Saudi Arabia just faces the question sooner than most.
Governments may still need to back the most extreme war losses, wherever they happen. That backing will be smaller and cheaper if the market can measure what sits beneath it.
The next event, wherever it happens, will test one thing: whether the chain can show reinsurers its exposure within 72 hours. If it can, capacity will be repriced. If it cannot, capacity must be withdrawn.
