B-757-300

The FAA database contains 310 filed wildlife-strike reports naming B-757-300 across 35 airports; damage was indicated in 7.7% and engine ingestion in 7.7%. These are report-level shares, not flight probabilities.

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

Filed reports3101990–export

Airports represented35distinct airport IDs

Damage indicated7.7%of filed reports

Engine ingestion7.7%of filed reports

Damage-indicated reports24FAA report field

Serious / destroyed5FAA S or D level

Effect on flight15effect supplied

Reported cost$62Kinflation-adjusted supplied values

02 / YEAR LOG

B-757-300: 2016–2025 reporting record

B-757-300 has 10 complete-year cohorts from 2016 through 2025, totaling 163 filed reports in the annual series.

201615 · 0.0% damage

20178 · 0.0% damage

20189 · 11.1% damage

201915 · 0.0% damage

20209 · 0.0% damage

202117 · 5.9% damage

202217 · 5.9% damage

202324 · 4.2% damage

202419 · 5.3% damage

202530 · 3.3% damage

04 / AIRPORT RECORDS

B-757-300: published airport records

B-757-300 has 11 published airport combinations representing 242 filed reports that met the publication threshold.

KMCOOrlando Intl40 reports · 15.0% damage KDENDenver Intl Airport33 reports · 3.0% damage KMSPMinneapolis-St Paul Intl/Wold-Chamberlain Arpt30 reports · 13.3% damage KSFOSan Francisco Intl Arpt22 reports · 0.0% damage KATLHartsfield - Jackson Atlanta Intl Arpt20 reports · 5.0% damage KDTWDetroit Metro Wayne County Arpt18 reports · 11.1% damage KEWRNewark Liberty Intl Arpt18 reports · 16.7% damage KLAXLos Angeles Intl17 reports · 5.9% damage PHNLDaniel K. Inouye International Airport16 reports · 6.2% damage KORDChicago O'Hare Intl Arpt15 reports · 0.0% damage KRSWSouthwest Florida Intl Arpt13 reports · 7.7% damage