The 7C2216 incident at Muan International Airport on 29 December 2024 killed 179 people. That number is the boundary condition for every conversation about bird-strike investment in 2026. This short note walks the asymmetry between detection investment and loss exposure on the civilian airport axis.
The asymmetry
ICAO Doc 9332 lays out the IBIS reporting framework. Compliance with the reporting layer is widespread. Operational response layers — habitat profiling, real-time detection, deterrence orchestration — are not required by the same instrument and are funded out of operator discretion.
A modern AVIX-class deployment runs on edge inference hardware costing roughly $30 K per coverage cone, including sensors, compute, and provisioning. The lifetime cost of a single bird-related airframe loss runs four orders of magnitude higher even before the human cost of fatalities is accounted.
Why the imbalance persists
Three reasons surface in operator interviews:
- Reporting compliance feels like coverage. It is not. IBIS reports describe events after the fact; they do not reduce the next event.
- Insurance treats bird strike as actuarial. The premium curve is smoothed across the global fleet; individual operator incentive to invest in detection is dulled by the cross-subsidy.
- Detection vendors sell into procurement, not safety. The buyer is procurement; the user is safety; the alignment between them is imperfect.
What changed in April 2026
The Lattice catalog adoption of platform_type: Animal changes one
specific input in this equation: it removes a schema-translation step
from any operator already on Lattice. The economics of adopting an
AVIX-class detection layer are now strictly easier than they were the
day before the catalog release.
Whether the procurement / safety alignment improves is a separate question. The schema layer is no longer the bottleneck.
—
Inquiries: ceo@uamkt.com