NTSB investigations: AiResearch TPE331 series, 2006
7 cases on aircraft whose registry engine model is AiResearch TPE331 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
| 1966 | 1 |
|---|---|
| 1968 | 1 |
| 1970 | 1 |
| 1976 | 2 |
| 1978 | 3 |
| 1979 | 1 |
| 1980 | 2 |
| 1981 | 6 |
| 1982 | 4 |
| 1983 | 2 |
| 1984 | 6 |
| 1985 | 7 |
| 1986 | 2 |
| 1987 | 2 |
| 1988 | 3 |
| 1989 | 3 |
| 1990 | 5 |
| 1991 | 3 |
| 1992 | 5 |
| 1993 | 6 |
| 1994 | 2 |
| 1995 | 7 |
| 1996 | 7 |
| 1997 | 2 |
| 1998 | 3 |
| 1999 | 7 |
| 2000 | 6 |
| 2001 | 6 |
| 2002 | 6 |
| 2003 | 11 |
| 2004 | 10 |
| 2005 | 10 |
| 2006 | 7 |
| 2007 | 8 |
| 2008 | 6 |
| 2009 | 7 |
| 2010 | 2 |
| 2011 | 4 |
| 2012 | 4 |
| 2014 | 1 |
| 2015 | 2 |
| 2016 | 6 |
| 2017 | 2 |
| 2018 | 4 |
| 2019 | 3 |
| 2020 | 3 |
| 2021 | 5 |
| 2022 | 3 |
| 2023 | 2 |
| 2024 | 5 |
| 2025 | 3 |
| 2026 | 4 |
Where
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\") = 2006
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('01514', '01517'))
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 year(c."eventDate") = 2006
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('01514', '01517'))
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 DEN06MA119Accident · 1 fatalMajor investigationFinal reportMitsubishi MU-2B-35 · Argyle, FLthe pilot's inadvertent flight into thunderstorm activity that resulted in the loss of control, design limits of the airplane being exceeded and subsequent in-flight breakup. A contributing factor was the failure of air traffic control to use available radar…NTSB NYC06MA208Accident · 2 fatalMajor investigationFinal reportMitsubishi MU-2B-40 · Bunnell, FLThe pilot's inadvertent encounter with thunderstorms.NTSB CHI06LA244Accident · Minor injuriesLimited investigationFinal reportFairchild SA227-AC · Grain Valley, MOthe pilot not maintaining clearance from the fence. Contributing factors were the pilot's fatigue and the fence.NTSB ATL06LA119Accident · No injuriesLimited investigationFinal reportAyres S2R · Doerun, GAThe loss of engine power for an underdetermined reason, resulting in a forced landing, an on ground collision with trees, and a post crash fire.NTSB ANC06FAMS1Accident · 3 fatalMissing aircraftFinal reportAero Commander 690A · Anchorage, AKUndetermined; the airplane and its occupants are missing.NTSB MIA06FA120Accident · 1 fatalField investigationFinal reportMitsubishi MU-2B-60 · Fort Pierce, FLthe pilot’s loss of aircraft control during the initial climb which was precipitated by the sudden loss of thrust and increase in drag from the right engine, and the pilot’s failure to adhere to the published emergency procedures regarding the position of the…NTSB DEN06IA056Incident · No injuriesIncident investigationFinal reportSwearingen SA226TC · Denver, COthe failure of the elevator down cable due to an improperly routed cable by unknown maintenance personnel. A contributing factor was the improper inspection of the elevator cable by the operator's maintenance personnel.