In 2014, the Songdo and Yeongjong tidal flats were inscribed on the Ramsar Convention list. That single administrative act reframed every bird-strike conversation around Incheon — and, by extension, every discussion about what an Animal-class entity in the Lattice catalog should be allowed to carry.
This note walks the chain from the RAMSAR designation through the East
Asian-Australasian Flyway (EAAF) to the design parameter we ship today:
disposition: NEUTRAL by default, escalation only when doctrine
demands it.
The flyway pinch point
The EAAF stretches from Siberia to Australia, narrowing across the Yellow Sea. The Korean tidal flats are the principal stopover for ~50 million migratory birds per year. That is not optional habitat — it is the geological feature their navigation depends on.
A civilian airport sitting in the middle of that pinch point inherits the flyway's ecology whether the operator chose it or not. Muan, Incheon Gimpo, Busan — every Korean airport reads the same map.
What "kill-based deterrence" assumes
The simplest bird-strike abatement strategy is to remove the birds. Acoustic harassment, falconry, lethal control — all variations on a single doctrine: no birds at the airport. Effective when the airport sits in a low-density habitat. Wrong-shaped solution when the airport sits in the EAAF stopover loop.
A RAMSAR-protected site cannot legally tolerate a strategy that kills the migratory population. The wetland's protected status is not a soft preference; it is a treaty obligation.
Why NEUTRAL is doctrinal
When AVIX-AI publishes an Animal-class entity to the Lattice catalog,
the default disposition is NEUTRAL. That is not a UI choice — it is a
statement about what the operator should do: detect, track, predict
trajectory, and steer the aircraft, not the birds.
A bird is not a target. It is a feature of the airspace. The catalog schema reflects that.
We escalate only on doctrine: a _uamkt_extensions:doctrine_ref tag
points to ICAO Doc 9332 § 4.6 which authorises specific behavioural
deterrence (non-lethal) in defined contexts. The escalation lives in
the entity payload, not in vendor opinion.
ESG as a design parameter
It is fashionable to treat ESG as a constraint that good engineering has to survive. We treat it as a design parameter that good engineering consumes. The Animal-class disposition default and the doctrine-tagged escalation pattern are the parameter applied to software.
The result is that an AVIX-AI deployment at Incheon is, by construction, compatible with the airport's RAMSAR obligations. Compliance is not bolted on — it is the API.
—
Inquiries: ceo@uamkt.com
Primary reference: Ramsar Convention Secretariat (2014). Site 2197: Songdo Tidal Flat.