Final NTSB investigations: GE CF6-80C2B6F
7 cases on aircraft whose registry engine model is GE CF6-80C2B6F. 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
| 2015 | 1 |
|---|---|
| 2017 | 1 |
| 2018 | 1 |
| 2019 | 1 |
| 2020 | 1 |
| 2023 | 2 |
Where
Open the mapLatest 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 c.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30109'))
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.
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 c."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30109'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB ENG24FA003Incident · No injuriesClass 3 · FieldFinal reportBoeing 767-300F · Memphis, TNA high-pressure fuel leak from a gap in the bolted flange interface between the main fuel pump’s fuel crossover supply tube and the hydromechanical unit idler adapter pad, which resulted in the crossover tube flange bolts partially pulling out and allowing…NTSB DCA23FA149Incident · No injuriesClass 1 · FieldFinal reportBoeing 737-79P · Austin, TXthe local controller’s incorrect assumption that the Southwest Airlines (SWA) airplane would depart from the runway before the Federal Express airplane arrived on the same runway, which resulted in a loss of separation between both airplanes. Contributing to…NTSB DCA20LA138Accident · Serious injuriesClass 3 · LimitedFinal reportBoeing 767 · Los Angeles, CAThe left main landing gear’s failure to extend due to the separation of the brake rod retaining hardware from the aft inboard wheel for reasons that could not be determined based on the available evidence.NTSB DCA19MA086Accident · 3 fatalClass 1 · MajorFinal reportBoeing 767 · Trinity Bay, TXThe inappropriate response by the first officer as the pilot flying to an inadvertent activation of the go-around mode, which led to his spatial disorientation and nose-down control inputs that placed the airplane in a steep descent from which the crew did…NTSB DCA18CA252Accident · No injuriesClass 4 · Data collectionFinal reportBoeing 767 · Portsmouth, NHan improper landing flare technique and the lack of the appropriate bounced landing recovery procedure.NTSB DCA18CA007Accident · Serious injuriesData collectionFinal reportBoeing 767 328 · Honolulu, HIan inadvertent encounter of clear air turbulence.NTSB OPS15IA017Incident · No injuriesIncident investigationFinal reportBoeing 767 34AF · Miami, FLThe controller's issuance of a landing clearance to an arriving aircraft while another aircraft was in position on the same runway. Contributing to the incident was the controller's non-compliance with traffic advisory procedures, and insufficient…