Major NTSB investigations: Lycoming TI0-540 series
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
| 1980 | 1 |
|---|---|
| 1981 | 1 |
| 1984 | 1 |
| 1986 | 1 |
| 2000 | 1 |
| 2008 | 1 |
| 2009 | 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.board_report_url IS NOT NULL OR c.\"investigationClass\" = 'Class 1' OR c.\"caseType\" = 'Major - Launch')
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.board_report_url IS NOT NULL OR c."investigationClass" = 'Class 1' OR c."caseType" = 'Major - Launch')
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 ERA09MA447Accident · 9 fatalClass 1 · MajorFinal reportPiper PA-32R-300 · Hoboken, NJ(1) the inherent limitations of the see-and-avoid concept, which made it difficult for the airplane pilot to see the helicopter until the final seconds before the collision, and (2) the Teterboro Airport local controller’s nonpertinent telephone conversation,…NTSB ANC08MA038Accident · 6 fatalMajor investigationFinal reportPiper PA-31-350 · Kodiak, AKThe failure of company maintenance personnel to ensure that the airplane's nose baggage door latching mechanism was properly configured and maintained, resulting in an inadvertent opening of the nose baggage door in flight. Contributing to the accident were…NTSB DCA00MA080Accident · 11 fatalMajor investigationFinal reportPiper PA-31 Navajo · Burlington Twp., NJthe failure of the pilots of the two airplanes to see and avoid each other and maintain proper airspace separation during visual flight rules flight.NTSB ATL86MA087Accident · 1 fatalMajor investigationFinal reportPiper PA-32-300 · Andalusia, ALThe accident flt was to be the last in a series of flt tests. This flt was for the purpose of determining the landing characteristics of the acft with a combination speed/stol kit installed. When the FAA flt test plt failed to return from the mission a search…NTSB ATL84MA208Accident · 5 fatalMajor investigationFinal reportPiper PA-32-300 · Canton, GAThe acft with a student plt at the controls had an in-flt breakup during a night x-country flt. During a preflt wx briefing, he was advised that VFR flt was not recommended. The plt terminated the conversation before the briefing was completed. While in flt,…NTSB DCA82AA007Accident · 4 fatalClosedPiper PA-31 · Durango, CONTSB FTW80AA057Accident · 7 fatalClosedPiper PA-31 · Houston, TX