Know what is on the ground at every airport

Aviation accumulation is about the moment aircraft are together: parked at a hub, in a hangar, on the apron.

Exposure management for aviation means knowing how much fleet value and liability sits at each airport, and what one event there could do.

Every aircraft that was there when the weather arrived.

An international airport on a bay, photographed from orbitPhoto: NASA
Illustrative
USD 460m

hull value parked at one hub, three operators.

8 aircraft, 3 operators, 1 apron

A hail cell is moving over a hub. How much hull value is parked inside it?

In the air, a fleet accumulates nowhere. On the ground it accumulates at the one place every operator needs to be at the same hour: the hub.

The question is never the value of one aircraft. It is the value of every aircraft that happened to be there when the weather arrived.

Airline A and Airline B

Different operators, different policies, one apron.

A lessor's aircraft

Owned by one party, flown by another, parked at the same gate row.

Airport operator liability

Written separately, but concentrated at the same airport.

One airfield, one weather event

One airport, walked from the air to the hangar.

A fleet in flight accumulates nowhere

The hull value sits on the policy and the aircraft, and exposure to a ground event is close to nothing while it is aloft.

RUNWAYAPRONTERMINALHANGARIN FLIGHT · NO GROUND EXPOSURETHREE POLICIES · ONE APRONONE ROOF · THREE AIRCRAFTILLUSTRATIVE HAIL BANDILLUSTRATIVE
On the apron
0 aircraft
0
In the hangar
0 aircraft
0
hull value at this airport
0USD m
Illustrative

One fleet book, three ways to read it.

A fleet schedule is the same rows whichever way you cut it. The accumulation only shows when you cut it by the place an event would hit.

Hub 1 holds 770 of 1,310 USD m, 59% of the book: three operators, one runway.

Hub 1770 USD m
Hub 2290 USD m
Hub 3250 USD m
Airline AAirline BLessor CIllustrative · fictional values

A fleet schedule lands where every other schedule does.

Aviation schedules map into the same screens through ConfigHub: aircraft, operator and airport in place of building, construction and zip.

Every item has a value and a place

The Policy tab holds a schedule with a value, an address and coordinates, then plots every item on the map.

  • Import, integrate or enter
  • The demo schedule is property locations, not aircraft
Policy · schedule
ExposureHub Policy tab: a schedule of 1,000 locations with a map of the Massachusetts portfolio
1
2
3

ExposureHUB demo environment · sample data

The hubs that matter, on one map.

Aviation schedules map into the platform through ConfigHub and then use the same Insight analytics, dashboards and scenarios as the rest of the portfolio.

Public Ebix material names a dedicated module only for Energy. For aviation, the platform is the same configurable, multi-line one, set up with your own schedules.

Major hub airports and long-haul routes

Ask the book what is on the ground.

The questions a team asks of this book. Move across them to see what in the platform answers each.

How much hull value do we have at this airport right now?

Accumulation by airport, from the geocoded fleet schedule.

Which hubs are exposed to the same peril?

What is our largest single-airport accumulation?

How does a major hub event land on our fleet and liability book?

Weather, ground motion and what is parked there.

For each peril: how it reaches this class, and what you look at on the map.
Windstorm and hail

A convective storm over a hub reaches every parked aircraft on the apron and in open stands at once. Hail damage does not care which policy an aircraft sits on.

A hail or wind band over the airfield, with apron and hangar values inside it.

Earthquake at hub airports

A hub in a seismic region concentrates hangar, terminal and apron values behind one ground motion. Fleets that never fly the same route still meet here.

Airport accumulation by quake zone, then operators inside the footprint.

Flood

Airfields are flat and often near water. Standing water reaches ground equipment, hangars and low stands before it reaches anything else.

Flood zones across the airfield; hangar and apron values by location.

Fire and ground incidents

A hangar or a fuel incident can involve several aircraft, several owners and the airport operator's liability together.

Hangar-level totals and the operators and lessors named in them.

How the rollout runs: one class first, then the template.

The pattern comes from a fast-growing specialty MGA customer: agree which teams are in scope, hold workshops with each, go live with one class and reuse that template. It now runs seven classes of business. Aviation follows the same road.
One fleet book goes live
  • Fleet and airport schedules mapped through ConfigHub
  • Airports, hangars and aprons geocoded
  • Accumulation by airport and operator
The template travels
  • Each further aviation team is brought on with the same template
  • Workshops with each team to agree what it needs
Phase 2
Within three months of go-live
  • Hail, wind and flood footprints for the main hubs
  • Liability schedule for airport operators and ground handlers
  • Exports for carriers and capacity providers
Longer term
Integrity and resilience
  • Lessor and multi-entity clients on the same template
  • Third-party model and data feeds
0teams in the fact-finding workshops
~0exposure management stakeholders
0classes live after a staggered go-live

From an Ebix Europe customer story. The three groupings (go-live, three months after, longer term) and the one-class-first approach are the customer's; what sits in each column for aviation shows how a rollout would be scoped.

Modules involved, and the classes beside it.

The same configurable, multi-line platform runs every class. Energy is the one class with a dedicated module.

See Aviation on ExposureHUB.

Book a walk-through built around your aviation schedule and the questions your team asks of it.