A-310

The FAA database contains 568 filed wildlife-strike reports naming A-310 across 72 airports; damage was indicated in 4.9% and engine ingestion in 3.5%. These are report-level shares, not flight probabilities.

Source: FAA National Wildlife Strike Database · Named-subject cohort · Snapshot September 16, 2026

Filed reports5681990–export

Airports represented72distinct airport IDs

Damage indicated4.9%of filed reports

Engine ingestion3.5%of filed reports

Damage-indicated reports28FAA report field

Serious / destroyed11FAA S or D level

Effect on flight5effect supplied

Reported cost$14.5Minflation-adjusted supplied values

02 / YEAR LOG

A-310: 2016–2025 reporting record

A-310 has 6 complete-year cohorts from 2016 through 2025, totaling 26 filed reports in the annual series.

201611 · 0.0% damage

20173 · 0.0% damage

20183 · 0.0% damage

20197 · 0.0% damage

20201 · 0.0% damage

20221 · 0.0% damage

04 / AIRPORT RECORDS

A-310: published airport records

A-310 has 5 published airport combinations representing 355 filed reports that met the publication threshold.

KMEMMemphis Intl227 reports · 6.6% damage KINDIndianapolis Intl Arpt69 reports · 0.0% damage KEWRNewark Liberty Intl Arpt27 reports · 7.4% damage KSATSan Antonio Intl17 reports · 0.0% damage KAFWFort Worth Alliance15 reports · 0.0% damage