CL-300

The FAA database contains 669 filed wildlife-strike reports naming CL-300 across 250 airports; damage was indicated in 10.0% and engine ingestion in 4.6%. These are report-level shares, not flight probabilities.

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

Filed reports6691990–export

Airports represented250distinct airport IDs

Damage indicated10.0%of filed reports

Engine ingestion4.6%of filed reports

Damage-indicated reports67FAA report field

Serious / destroyed10FAA S or D level

Effect on flight67effect supplied

Reported cost$4.4Minflation-adjusted supplied values

02 / YEAR LOG

CL-300: 2016–2025 reporting record

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

201637 · 8.1% damage

201761 · 13.1% damage

201844 · 11.4% damage

201950 · 12.0% damage

202030 · 6.7% damage

202157 · 7.0% damage

202240 · 2.5% damage

202359 · 6.8% damage

202434 · 8.8% damage

202549 · 6.1% damage

04 / AIRPORT RECORDS

CL-300: published airport records

CL-300 has 5 published airport combinations representing 115 filed reports that met the publication threshold.

KTEBTeterboro Airport48 reports · 8.3% damage KMMUMorristown Municipal Arpt19 reports · 5.3% damage KLUKCincinnati Muni Arpt-Lunken Field19 reports · 5.3% damage KAPCNapa County Arpt16 reports · 0.0% damage KBEDLaurence G Hanscom Field Arpt13 reports · 15.4% damage