B-747-1/200

The FAA database contains 235 filed wildlife-strike reports naming B-747-1/200 across 36 airports; damage was indicated in 28.9% and engine ingestion in 28.5%. These are report-level shares, not flight probabilities.

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

Filed reports2351990–export

Airports represented36distinct airport IDs

Damage indicated28.9%of filed reports

Engine ingestion28.5%of filed reports

Damage-indicated reports68FAA report field

Serious / destroyed37FAA S or D level

Effect on flight41effect supplied

Reported cost$15.8Minflation-adjusted supplied values

02 / YEAR LOG

B-747-1/200: 2016–2025 reporting record

B-747-1/200 has 2 complete-year cohorts from 2016 through 2025, totaling 2 filed reports in the annual series.

20221 · 0.0% damage

20241 · 0.0% damage

04 / AIRPORT RECORDS

B-747-1/200: published airport records

B-747-1/200 has 5 published airport combinations representing 166 filed reports that met the publication threshold.

KMWHGrant County International Airport72 reports · 12.5% damage KJFKJohn F Kennedy Intl47 reports · 46.8% damage PANCTed Stevens Anchorage Intl20 reports · 45.0% damage KSFOSan Francisco Intl Arpt14 reports · 14.3% damage KSDFMuhammad Ali International13 reports · 38.5% damage