NTSB investigations: Lycoming IO-320 series, 2001
11 cases on aircraft whose registry engine model is Lycoming IO-320 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
| 1964 | 17 |
|---|---|
| 1965 | 21 |
| 1966 | 34 |
| 1967 | 35 |
| 1968 | 25 |
| 1969 | 20 |
| 1970 | 33 |
| 1971 | 28 |
| 1972 | 34 |
| 1973 | 32 |
| 1974 | 27 |
| 1975 | 21 |
| 1976 | 20 |
| 1977 | 19 |
| 1978 | 36 |
| 1979 | 19 |
| 1980 | 22 |
| 1981 | 17 |
| 1982 | 17 |
| 1983 | 13 |
| 1984 | 18 |
| 1985 | 12 |
| 1986 | 15 |
| 1987 | 18 |
| 1988 | 10 |
| 1989 | 11 |
| 1990 | 9 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 5 |
| 1994 | 3 |
| 1995 | 5 |
| 1996 | 10 |
| 1997 | 5 |
| 1998 | 6 |
| 1999 | 9 |
| 2000 | 11 |
| 2001 | 11 |
| 2002 | 13 |
| 2003 | 13 |
| 2004 | 10 |
| 2005 | 8 |
| 2006 | 12 |
| 2007 | 15 |
| 2008 | 10 |
| 2009 | 13 |
| 2010 | 10 |
| 2011 | 13 |
| 2012 | 7 |
| 2013 | 10 |
| 2014 | 10 |
| 2015 | 7 |
| 2016 | 4 |
| 2017 | 8 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 10 |
| 2021 | 9 |
| 2022 | 10 |
| 2023 | 9 |
| 2024 | 5 |
| 2025 | 6 |
| 2026 | 6 |
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 year(c.\"eventDate\") = 2001
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509'))
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") = 2001
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41509'))
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 FTW02LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Ozona, TXThe loss of engine power due to fuel exhaustion resulting from the pilot's failure to refuel the airplane. Contributing factors were the lack of suitable terrain for the forced landing and the dark night conditions.NTSB MIA02LA003Accident · Minor injuriesLimited investigationFinal reportPiper PA-30B-160 · Clarksville, TNThe failure of the CFI/check pilot to insure Vmc was maintained during a go-around following a simulated failed engine approach, resulting in an in-flight loss of control, uncontrolled descent, and collision with the terrain. A factor in the accident was the…NTSB SEA01FA175Accident · 1 fatalField investigationFinal reportPiper PA-30 · McCall, IDThe pilot's failure to maintain adequate airspeed following a loss of power on the left engine, resulting in loss of aircraft control. Factors included a loss of power on the left engine for undetermined reasons, and the pilot's failure to properly configure…NTSB IAD01LA106Accident · Serious injuriesLimited investigationFinal reportDigimas Starduster Too · Watertown, CTthe student pilot's inattention while maneuvering at low altitude, which resulted in collision with trees. A factor in the accident was the student pilot's intentional low-altitude maneuvering.NTSB ANC01LA124Accident · No injuriesLimited investigationFinal reportPiper PA-18-135 · Palmer, AKThe pilot's excessive use of brakes during the landing roll.NTSB CHI01LA221Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Bowman, NDAltitude/clearance not obtained by the pilot during the initial climb. Factors relating to the accident were attaining the proper climb rate not being possible, the microburst, the dark night, and the tree.NTSB FTW01LA123Accident · No injuriesLimited investigationFinal reportCessna 172P · Pleasanton, TXthe student pilot's failure to maintain directional control during the landing flare/touchdown. Contributory factors were the gusty wind and the student pilot's lack of total flight experience.NTSB NYC01LA111Accident · Minor injuriesLimited investigationFinal reportKnab-Douglas Jurca MJ5 Sirocco · G. Barrington, MAThe pilot's failure to obtain the proper touchdown point, which resulted in an overrun. A factor in this accident was the gusty wind condition.NTSB FTW01LA082Accident · Serious injuriesLimited investigationFinal reportChampion 7KCAB · Ragley, LAthe loose clamp (Nicopress fitting) on the elevator control cable due to inadequate quality control during the cable's manufacturing, which allowed the cable to disconnect and restricted the pilot's control of the airplane during landing.NTSB CHI01LA096Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Appleton, WIThe misjudged glidepath and the intentional engine shutdown by the pilot. Factors were the false indication of the landing gear down light and the approach light.NTSB MIA01FA072Accident · 1 fatalField investigationFinal reportPiper PA-30 · Ponce, PRThe pilot's decision to attempt flight with known deficiencies in the airplanes right engine, his failure to feather the right propeller after the engine failed , his failure to retract the landing gear following the engine failure, and his failure to…