Why Airport-Surface Data Challenges Runway Excursion Loss Severity Assumptions

Runway excursions are the most frequent aviation accident type, yet reinsurance pricing for overruns and veer-offs still relies on broad severity averages that ignore the one variable most predictive of outcomes: the airport surface itself. Runway length, friction coefficient, grooving, and runway end safety area dimensions at each airport an airline operates into determine whether an excursion becomes a repairable incident or a total hull loss. Airport-surface data lets reinsurers stop assuming severity and start measuring it.

Why do runway excursions dominate aviation frequency but remain poorly differentiated by severity?

Runway excursions dominate aviation frequency and remain poorly differentiated by severity because historical claims data lumps all overruns and veer-offs together, treating a minor landing-gear excursion at a long, flat, well-grooved runway the same as a total hull loss at a short strip with a 60-meter RESA and a ravine beyond it. The claims record does not distinguish, so the pricing model cannot either.

The numbers are well known across the industry: runway excursions account for a large share of all aviation hull losses annually, making them the single most frequent accident category for commercial aviation. Yet the severity distribution within that category is extraordinarily wide. Some excursions produce little more than a tow and a tire change. Others destroy airframes, injure passengers, and trigger liability claims that run into hundreds of millions of dollars. The difference between those outcomes often comes down to the airport surface: how much runway was available, what the friction was at the time of the event, and what sat beyond the threshold.

The reinsurance industry has sophisticated tools for differentiating catastrophe risk by location in property lines, but aviation underwriting has not yet systematically incorporated airport-level surface data into its severity assumptions. A cedent's portfolio of operated airports is the aviation equivalent of a property portfolio's geocoded locations, and the data exists to score each airport for excursion severity. It simply has not been connected to the treaty pricing process.

What goes wrong when runway excursion severity is priced from averages?

Runway excursion severity priced from averages fails in five ways: RESA dimensions ignored so all overruns look the same, friction data at the time of event discarded, runway grooving and drainage unaccounted, terrain beyond RESA absent from the model, and airport-level frequency patterns invisible because claims are pooled by airline not by airport.

These are the failure modes that keep aviation reinsurance pricing anchored to historical averages even when forward-looking airport data offers a sharper tool. Each one erodes the accuracy of treaty pricing and the quality of the underwriting conversation.

1. Why does ignoring RESA dimensions flatten severity?

Ignoring RESA dimensions flattens severity because the model treats an overrun at an airport with a 240-meter engineered materials arresting system as identical to an overrun at an airport with a 60-meter grass strip ending at a drainage ditch. The historical claims data does not preserve the RESA variable, so the model cannot learn from it.

RESA length and composition are publicly reported for most commercial airports through ICAO and national regulator publications. An engineered materials arresting system (EMAS) can stop an overrunning aircraft within the RESA with minimal damage, while a short grass RESA followed by terrain drop-off produces catastrophic outcomes. Yet the aviation treaty underwriter pricing a portfolio of airline risks rarely has airport-level RESA data joined to the cedent's schedule of operations. The result is severity loaded for the worst case across every airport in the portfolio, which penalizes airlines operating into well-equipped airports and subsidizes those operating into marginal ones.

2. How does friction data at the time of event get lost?

Friction data at the time of event gets lost because claims adjusters focus on aircraft systems and crew actions, not on the surface the aircraft was trying to stop on. Runway condition reports from the hour of the event exist in airport logs, but they rarely make it into the claims file or the reinsurance notification.

A runway with a freshly measured friction coefficient of 0.25 under standing water is fundamentally different from the same runway dry with a friction coefficient of 0.70. The aircraft's certified landing distance multiplies by a factor that can turn a legal landing into an overrun regardless of crew performance. When the claim arrives coded as "runway excursion, crew error" without surface-condition data, the reinsurance claims tracking system records a crew-error loss that reinforces the average, when the real story was a surface-condition loss that airport data would have revealed.

3. What does ignoring grooving and drainage hide?

Ignoring grooving and drainage hides the single most effective runway-surface intervention for reducing excursion risk in wet conditions. A grooved runway channels water away from the tire contact patch, maintaining friction that a smooth runway loses as soon as standing water appears. The difference in available braking between a grooved and ungrooved runway under heavy rain is larger than most crew-performance variables.

Airport infrastructure data shows which runways are grooved, which have porous friction course overlays, and which have documented drainage problems that produce ponding. This data is captured in airport master plans and pavement management records. It is not captured in aviation reinsurance submissions. An airline operating a fleet of aircraft types with known braking characteristics into airports with poor drainage and ungrooved runways carries a systematically higher excursion severity risk than its claims history alone might suggest, and airport data is what exposes that difference.

4. How does terrain beyond RESA stay absent from the model?

Terrain beyond RESA stays absent from the model because aviation reinsurance pricing aggregates claims by airline and aircraft type, not by the physical environment each aircraft operates into. A runway ending at a flat, cleared field presents a different overrun outcome than a runway ending at a steep embankment, a body of water, an airport perimeter road, or a built-up area.

This is the fatal-outcome variable. The total hull losses among runway excursions disproportionately involve terrain or obstacles beyond the runway end. Airport charts, satellite imagery, and terrain databases describe exactly what sits beyond each runway threshold, and that description can be converted into a terrain-severity score per runway end. The reinsurer who applies that score across a cedent's route network can price excursion severity at a granularity the competition cannot match, because the competition is still pricing from historical claims averages that bury the terrain variable entirely.

5. Why do airport-level frequency patterns stay invisible in pooled claims data?

Airport-level frequency patterns stay invisible because aviation claims are reported and tracked by airline, not by airport. An airline that experiences three excursions in five years at the same poorly equipped regional airport generates claims that appear as three unrelated events in the loss run, when airport-level analysis would show a concentration that demands a different underwriting response.

Pooling claims by airline is administratively convenient but analytically destructive for excursion risk. The airport, not the airline, is the primary severity driver, and frequency concentrations at specific airports signal hazard that the airline's operating procedures cannot fully mitigate. A treaty data quality checker that re-indexed claims by airport as well as airline would surface concentrations that current loss runs hide, and those concentrations would drive better underwriting questions and sharper pricing.

Replace severity averages with airport-level data using Insurnest's aviation reinsurance technology

Talk to Our Specialists

Visit Insurnest to learn how we help aviation reinsurers integrate runway condition, RESA, friction, and terrain data into treaty pricing and portfolio management.

What do airline risk managers actually expect from reinsurers on runway excursion data?

Airline risk managers expect reinsurers to understand the airports their aircraft operate into at least as well as they do, to differentiate pricing based on the airport-surface investments the airline has already made or avoided, and to use runway data as a shared language for risk improvement rather than a backward-looking claims audit.

Claire is the risk manager at a regional airline operating a fleet of narrowbody aircraft into a mix of major hub airports and smaller regional strips across Southeast Asia. Her airline has invested in brake-to-vacate software, regularly trains crews on contaminated-runway procedures, and participates in the IATA runway safety program. But she operates three daily sectors into an airport with a 1,800-meter runway, a 60-meter RESA terminating at a riverbank, no grooving, and friction reporting that is updated monthly at best.

Last renewal, her reinsurer asked about fleet age, hull values, and crew training hours. Nobody asked about the airports. The treaty was priced as if every runway her aircraft touched was Munich or Singapore, and the reinsurer's severity model assigned an average excursion cost that Claire knows is wrong for her worst runway. She carries the exposure exposure not because the reinsurer priced it but because the reinsurer never measured it.

She wants a different conversation. She wants her reinsurer to understand that her airline's excursion risk is not one risk but thirty risks, one per airport, and that her investments in real-time landing-performance tools and crew training are targeted at the airports where the data says severity is highest. She wants the reinsurer to see that differentiation and reflect it in pricing, so the airlines that invest in operating safely into difficult airports are rewarded rather than pooled with those that do not. The following asks are what she would put to her reinsurance partners if the conversation were about data rather than history.

• Airport-by-airport RESA scoring. "Show me you know which of my airports have arresting systems, which have full RESAs, and which have grass strips ending at hazards, because that is where my severity lives." The runway end, not the crew, is the primary severity driver.
• Friction reporting quality by airport. "Tell me which airports you rate as having reliable, current friction data and which you flag as having data gaps, because those gaps are where my risk is unmeasured." An airport that reports friction weekly is not the same as one that reports monthly or not at all.
• Runway length margin analysis. "For each of my aircraft types and each airport, show me the margin between runway available and runway required under wet and contaminated conditions, because that margin is my safety buffer." A 200-meter margin is comfortable; a 50-meter margin on a wet ungrooved runway is not.
• Terrain and obstacle data beyond runway ends. "Map what sits beyond every runway threshold I operate into, so we both know which overruns become recoverable incidents and which become hull losses." Terrain is the variable that determines whether an excursion is a claim or a catastrophe.
• Grooving and surface-treatment status. "Identify which of my destination runways are grooved, which have porous friction overlays, and which are smooth asphalt, because the difference in wet-weather braking is material to my loss experience." Surface treatment is the cheapest severity reduction per runway and should affect pricing.
• Excursion frequency normalization by airport movements. "Show me my excursion frequency per ten thousand movements at each airport, not just my total count, so we can see whether a cluster of incidents at one airfield is a trend or just a busy schedule." Frequency without exposure denominator is meaningless.
• Contaminated-runway landing distance data from the flight data monitoring program. "Let me share what my flight data says about actual landing distances versus planned distances on contaminated runways, because that shows you my crews are managing the risk." Flight data validates procedure; claims data only validates failure.
• Airport infrastructure investment tracking. "Notice when an airport in my network gets an EMAS, a RESA extension, or a grooving program, because that reduces my severity exposure and should be reflected in your pricing view." Airport improvement is a direct severity reduction that static claims data cannot capture.
• Peer benchmarking by airport type. "Compare my excursion experience to other operators at the same airports, because that tells you whether my performance is driven by the airport or by my operation." The same airport produces different excursion rates for different airlines, and that difference is the operational credit the reinsurer should price.
• Scenario-based excursion severity modeling by airport. "Run an overrun scenario at each of my destination airports with current runway-condition data and tell me the expected hull and liability severity range, so we can agree what the worst case actually looks like." A catastrophe scenario built from airport data replaces assumed severity with measured severity.

The real expectation is that the reinsurer brings airport intelligence to the table, not just claims intelligence, and that the treaty price reflects the airports the airline actually operates into rather than an industry average that includes airports the airline has never visited.

How can aviation reinsurers build airport-surface data into excursion pricing?

Aviation reinsurers can build airport-surface data into excursion pricing by ingesting runway-dimension and RESA data for their cedents' destination airports, integrating friction-reporting quality scores, overlaying terrain and obstacle data beyond runway thresholds, normalizing excursion claims by airport movement counts, joining flight data monitoring outputs to airport-condition variables, and constructing airport-level severity scores that feed directly into treaty pricing models.

The data is not hidden. ICAO, national aviation authorities, airport operators, and commercial data providers all publish runway characteristics that can be joined to an airline's schedule of operations. The following capabilities describe how that data flows into the reinsurance underwriting process.

1. How does runway-dimension and RESA ingestion work at portfolio scale?

Runway-dimension and RESA ingestion at portfolio scale works by cross-referencing the cedent's list of regularly served airports against a database of runway physical characteristics, producing a per-airport score that captures runway length, width, RESA length, RESA composition, and arresting-system presence. The score feeds into the treaty pricing model as a severity modifier.

This is a data-join exercise, not a modeling exercise. Every commercial airport has published runway data. The technical work is linking the cedent's airport list to the runway database, keeping the linkage current as routes change, and converting the physical dimensions into a severity score that the underwriting model can consume. Once built, the score updates automatically when an airport commissions a RESA extension or an EMAS, and the pricing view stays current without manual refresh.

2. What does friction-reporting quality scoring add?

Friction-reporting quality scoring adds a data-currency dimension to the physical runway score. An airport with a long, grooved runway that reports friction twice a year may be riskier in practice than a shorter runway that reports friction daily and publishes the results in real time. Quality scoring captures reporting frequency, measurement method, and data publication practice.

The Global Reporting Format for runway surface conditions, adopted by ICAO, standardizes how runway condition is reported internationally. The data exists; the question is how consistently each airport produces and publishes it. An airport with a strong friction-reporting program gives the operator and the reinsurer visibility into surface condition at the time of each operation. An airport with a weak program leaves both the crew and the reinsurer operating blind, and the pricing should reflect that difference.

3. Why does terrain and obstacle mapping change the severity conversation?

Terrain and obstacle mapping changes the severity conversation because it converts the question "what happens if an aircraft overruns at this airport?" from a guess into a data-supported answer. A runway ending at a flat, obstruction-free overrun area is a different severity proposition than a runway ending at a perimeter fence, a road, a building, or a drop-off.

Satellite imagery and terrain-elevation data make this mapping straightforward. Each runway end gets a terrain-severity classification from benign to extreme. The classification joins the RESA score to produce a composite runway-end severity rating. For a cedent whose worst runway end is the most frequently served, the rating flags a concentration of severity that the claims history may not yet have revealed but that the physical environment makes inevitable.

4. How does normalizing excursion claims by airport movements reveal hidden concentrations?

Normalizing excursion claims by airport movements reveals hidden concentrations by dividing the excursion count at each airport by the number of movements the cedent operates there, producing a per-airport excursion rate that exposes whether the airline's excursion experience is evenly distributed or concentrated at specific airfields.

An airline might have five excursions over five years that appear as a flat frequency pattern across the portfolio. Normalized by movements, four of the five might occur at one airport where the airline operates only 5% of its movements, producing a rate forty times higher than at the rest of the network. That concentration is actionable. The reinsurer can ask why that airport produces excursions, whether the ceded reinsurance team is aware of the pattern, and what the airline is doing about it. Unnormalized claims data hides that question entirely.

5. What does joining flight data to airport-condition variables enable?

Joining flight data to airport-condition variables enables the reinsurer to see what actually happened on approaches and landings at the airports that matter, not just what the claims record says about the ones that went wrong. Flight data monitoring programs capture actual landing distances, braking action, and touchdown points. Joined to airport condition data at the time of each landing, they show whether the airline is operating with adequate margins.

This is the positive side of the data relationship. Claims data only captures failures. Flight data captures the operational reality: the 9,999 landings that succeeded for every one that overran. When the reinsurer can see that the airline consistently lands within the first third of the runway on contaminated surfaces and stops with margin to spare, the conversation about the one excursion is contextualized. The airline can demonstrate risk control, not just assert it, and the treaty pricing can reflect demonstrated performance alongside historical loss experience.

6. How do airport-level severity scores feed into treaty pricing?

Airport-level severity scores feed into treaty pricing by attaching a severity factor to each airport the cedent serves, weighting those factors by the proportion of operations at each airport, and producing a portfolio-level excursion severity index that replaces the industry-wide severity average currently used in most aviation reinsurance pricing models.

The mechanics are arithmetic. If an airline operates 70% of its movements into airports scoring low on the excursion-severity index and 30% into airports scoring high, the portfolio-weighted severity is lower than the industry average. If the reverse is true, the weighted severity is higher. The pricing model captures that difference and produces a treaty price that reflects the airline's actual operating environment. As the reinsurance market cycle shifts, the airlines with the better airport profiles earn the sharper pricing because their severity is demonstrably lower, not because they told a better story at renewal.

Build airport-surface data into your aviation treaty pricing with Insurnest's reinsurance analytics

Talk to Our Specialists

Visit Insurnest to see how we deliver runway-dimension scoring, friction-quality assessment, terrain mapping, and airport-level severity indices for aviation reinsurance underwriting.

What does an ideal airport-data-driven excursion pricing model look like?

An ideal airport-data-driven excursion pricing model assigns every airport the cedent serves a composite severity score built from runway dimensions, RESA length and composition, friction-reporting quality, surface treatment, and terrain beyond the threshold, weights those scores by the proportion of movements at each airport, and produces a portfolio-level severity index that replaces the industry average in treaty pricing.

Imagine Claire again, now with a reinsurer who has built this model. At the renewal meeting, the conversation opens with a map. Each airport her airline serves is plotted with a color code: green for low excursion severity, amber for moderate, red for high. The map shows that 12% of her movements concentrate at three red-coded airports, including the riverbank strip with the 60-meter RESA. The reinsurer's model prices excursion severity at those airports differently from her green-coded hub airports, and the portfolio-weighted severity index is specific to her operation, not an industry blend.

Claire shares her flight data monitoring output: actual landing distances on contaminated runways versus required, by airport, over the past twelve months. The data shows her crews consistently landing within margins the model recognizes as conservative. The reinsurer adjusts the severity score for those airports downward based on demonstrated performance, and the treaty price reflects the adjustment.

The conversation then turns to the red airports. The reinsurer asks what operational changes, crew training investments, or fleet deployment adjustments Claire plans for those airfields. Claire describes a brake-to-vacate rollout targeting the three red airports and a crew-procedure update for the contaminated-runway case. The reinsurer notes these as mitigants and agrees to review the severity scores at mid-term when the operational data shows the results. The treaty is priced on data both sides can see, and the price moves when the data moves. The reinsurance renewal has become a risk-management conversation, not a claims-history negotiation.

Price aviation excursion severity from airport data, not industry averages, with Insurnest

Talk to Our Specialists

Visit Insurnest to learn how we help aviation reinsurers and cedents build airport-level severity models, integrate flight data, and replace assumed severity with measured exposure.

Conclusion

Runway excursions will remain the most frequent aviation accident type for the foreseeable future, but treating all excursions as having the same severity because the claims record averages them together is a choice, not a necessity. Airport-surface data, runway dimensions, RESA, friction, grooving, terrain, and movement-normalized frequency, can replace assumed severity with measured severity in aviation reinsurance pricing.

For aviation treaty underwriters, the opportunity is to differentiate risk at a granularity the market currently ignores. An airline operating into airports with long, grooved runways, full RESAs, and real-time friction reporting does not carry the same excursion severity as an airline operating into short, ungrooved runways with minimal overrun areas and sparse condition data. The data to prove that difference exists; it simply has not been connected to the underwriting process.

For airline risk managers and ceded reinsurance teams, the opportunity is to earn pricing credit for the airport-surface awareness they already have and the operational investments they have already made. When the reinsurer can see the airport data, the conversation moves from defending a claims history to demonstrating risk control, and the treaty price moves with it. The airports are the exposure. The data is available. The only question is who prices it first.

Frequently asked questions

What is a runway excursion in aviation?

A runway excursion is any event where an aircraft departs the runway surface during takeoff or landing, either by overrunning the end or veering off the side.

What airport-surface data matters for runway excursion severity?

The key data points are runway friction coefficients under wet and contaminated conditions, runway surface condition reporting codes (RWYCC), runway end safety area (RESA) dimensions and composition, runway length available versus required for the aircraft

How does RESA length affect reinsurance loss severity?

RESA is the cleared, graded area beyond the runway end designed to decelerate an overrunning aircraft. A 90-meter RESA versus a 240-meter RESA can be the difference between an aircraft stopping with repairable damage and

Why do reinsurers assume runway excursion severity rather than measuring it?

Most aviation reinsurance pricing relies on historical loss averages rather than forward-looking airport-specific data. A total hull loss from an overrun at one airport is treated as representative of overrun severity at all airports, even

What role does runway friction data play in excursion claims?

Runway friction directly determines braking effectiveness. A contaminated runway with poor friction reporting can mean an aircraft touches down within the normal zone but cannot stop, while a well-maintained grooved runway with current friction measurements

Can reinsurers use runway condition data to differentiate pricing between airports?

Yes. An airline operating primarily into airports with long runways, full RESAs, grooved surfaces, and current friction-reporting programs presents a different excursion severity profile than one operating into short runways with minimal overrun areas.

How do runway excursions interact with aviation hull and liability treaties?

A runway excursion can trigger both hull and liability claims. Hull damage from the excursion itself, ranging from landing-gear collapse to total constructive loss, falls under the hull cover.

What should aviation reinsurers ask cedents about runway excursion exposure?

Reinsurers should ask for the list of airports the airline regularly operates into, runway dimensions and RESA data for those airports, the airline's contaminated-runway landing procedures, whether the fleet uses brake-to-vacate or similar landing-performance tools,

About the author

Hitul Mistry is the Founder of Insurnest, an InsurTech company that engineers end-to-end technology exclusively for the insurance industry serving carriers, TPAs, MGAs, brokers, and reinsurers across India, the UAE, and the US. With more than a decade of insurance domain experience, he has built systems spanning underwriting automation, AI-powered underwriting intelligence, claims management, rating and quoting, broking and agency platforms, and reinsurance automation across Health/GMC, Group Life, Motor, P&C, and Reinsurance. Insurnest doesn't adapt generic software to insurance; it builds from the workflow up.

Connect with Hitul on LinkedIn.