Fatal NTSB investigations: Lycoming TI0-540 series, OK
7 cases on aircraft whose registry engine model is Lycoming TI0-540 series. 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
| 1969 | 1 |
|---|---|
| 1976 | 1 |
| 1982 | 1 |
| 1999 | 1 |
| 2008 | 1 |
| 2009 | 1 |
| 2014 | 1 |
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.\"eventStateOrRegion\" = 'OK' AND c.\"eventCountry\" = 'USA'
AND c.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533'))
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."eventStateOrRegion" = 'OK' AND c."eventCountry" = 'USA'
AND c."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41533'))
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 CEN14FA434Accident · 1 fatalField investigationFinal reportPiper PA 32-300 · Ardmore, OKThe partial loss of engine power for reasons that could not be determined because thermal damage to the engine prevented a complete examination.NTSB CEN09FA562Accident · 5 fatalField investigationFinal reportPiper PA-32R-300 · Tulsa, OKThe non-instrument-rated pilot’s decision to attempt flight in instrument meteorological conditions, which resulted in spatial disorientation and an in-flight collision with a radio tower guy wire.NTSB DFW08FA056Accident · 1 fatalField investigationFinal reportAero Commander 500B · Tulsa, OKThe pilot's loss of control due to spatial disorientation and the pilot exceeding the design/stress limits of the aircraft. Factors contributing to the accident were the pilot's reported gyro problem, the dark night conditions , and prevailing instrument…NTSB FTW99FA199Accident · 2 fatalField investigationFinal reportSmith, Ted Aerostar Aerostar 601P · Bethany, OKThe pilot's failure to maintain the minimum controllable airspeed. A factor was the disconnected rubber interconnect boot, which resulted in the partial loss of left engine power.NTSB FTW83FPM04Accident · 2 fatalFinal reportPiper PA23-250 · 8 Miles Se Bris, OKThe acft departed at 2220 with a planned enroute stop at holdenville, OK. 55 minutes later the acft crashed approximately 8.5 miles from its original departure point. Witnesses describe the wx as very bad due to heavy rain & fog.NTSB FTW76AF069Accident · 2 fatalClosedPiper PA-24 · Alva, OKNTSB FTW69A0059Accident · 2 fatalClosedPiper PA-24 · Clayton, OK