CL-600

The FAA database contains 441 filed wildlife-strike reports naming CL-600 across 194 airports; damage was indicated in 10.4% and engine ingestion in 6.3%. These are report-level shares, not flight probabilities.

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

Filed reports4411990–export

Airports represented194distinct airport IDs

Damage indicated10.4%of filed reports

Engine ingestion6.3%of filed reports

Damage-indicated reports46FAA report field

Serious / destroyed14FAA S or D level

Effect on flight56effect supplied

Reported cost$5.2Minflation-adjusted supplied values

02 / YEAR LOG

CL-600: 2016–2025 reporting record

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

201617 · 5.9% damage

20176 · 16.7% damage

201819 · 5.3% damage

201915 · 0.0% damage

20209 · 22.2% damage

202123 · 0.0% damage

20229 · 22.2% damage

202313 · 7.7% damage

202423 · 4.3% damage

202516 · 0.0% damage

04 / AIRPORT RECORDS

CL-600: published airport records

CL-600 has 4 published airport combinations representing 66 filed reports that met the publication threshold.

KTEBTeterboro Airport19 reports · 15.8% damage KHPNWestchester County Arpt18 reports · 11.1% damage KMMUMorristown Municipal Arpt17 reports · 11.8% damage KGYYGary/Chicago Intl Arpt12 reports · 33.3% damage