NTSB investigations: Bombardier CL-600-2B19, 2007

6 cases on aircraft the registry lists as Bombardier CL-600-2B19. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

20002026
NTSB investigations: Bombardier CL-600-2B19, 2007 per year, 2000–2026: 64 cases
20004
20012
20023
20034
20043
20054
20063
20076
20084
20093
20108
20115
20123
20131
20162
20173
20181
20211
20222
20252

Latest cases

Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
  FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE year(c.\"eventDate\") = 2007
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('1390008'))
  ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

NTSB CHI08LA051Accident · Serious injuriesLimited investigationFinal reportBombardier CL-600-2B19 · Chicago, ILThe tug driver's failure to yield the right-of-way to the airplane prior to crossing the active taxiway as required by airport procedures, and his subsequent failure to maintain clearance with the airplane. A contributing factor was the presence of the tug on…Dec 17, 2007 · N918SW · Substantial damageNTSB DCA08FA018Accident · No injuriesField investigationFinal reportBombardier CL600-2B19 · Providence, RIthe captain’s attempt to salvage the landing from an instrument approach which exceeded stabilized approach criteria, resulting in a high sink rate, likely stall, and hard landing which exceeded the structural limitations of the airplane. Contributing to the…Dec 16, 2007 · N470ZW · Substantial damageNTSB OPS08IA002Incident · No injuriesIncident investigationFinal reportBombardier CRJ1 · Baltimore, MDThe probable cause of this incident is local controller's failure of maintaining awareness of the situation and failing to provide the appropriate separation between the two aircraft operating on intersecting runways. Providing separation between aircraft is…Dec 3, 2007 · N781CA · 2 aircraft · No damageNTSB LAX07IA191Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B19 · Phoenix, AZAn out of rig/jammed door. Contributing to the incident was the operator's inadequate maintenance program and the airframe manufacturer's inadequate response to the issue.Jun 13, 2007 · N7264V · No damageNTSB DCA07FA037Accident · No injuriesClass 1 · FieldFinal reportBombardier CL-600-2B19 · Traverse City, MIThe pilots' decision to land at Cherry Capital Airport (TVC), Traverse City, Michigan, without performing a landing distance assessment, which was required by company policy because of runway contamination initially reported by TVC ground operations personnel…Apr 12, 2007 · N8905F · Substantial damageNTSB DEN07IA055Incident · No injuriesIncident investigationFinal reportBombardier CL-600-2B19 · Cripple Creek, COA fatigue fracture, which resulted in the separation of the No.1 engine fan disk. Contributing factors in the accident were the operators' maintenance personnel lack of training to be able to detect arc-out damage on the fan disk, and the fan disk…Jan 25, 2007 · N17337 · Minor damage