NTSB investigations: Lycoming IO-320 series, 2007
15 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\") = 2007
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") = 2007
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 SEA08LA048Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Bridger, MTThe landing gear collapsed during landing for undetermined reasons.NTSB NYC08FA054Accident · 2 fatalField investigationFinal reportPiper PA-30 · Parkland, FLBoth pilots' failure to see and avoid the other airplane. Contributing to the accident were the erroneous readouts from the Cessna's altitude encoder.NTSB CHI08CA036Accident · No injuriesData collectionFinal reportPiper PA-30 · Lonoke, ARThe pilot's misjudgment of the landing flare resulting in a hard landing.NTSB MIA07LA152Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Milton, FLThe failure of the pilot to attain the proper touchdown point during the precautionary landing resulting in the on-ground collision with fence posts.NTSB NYC07CA216Accident · No injuriesData collectionFinal reportPiper PA28-161 · William-Sodus, NYThe pilot's improper flare at touchdown, which resulted in a hard landing.NTSB DEN07LA160Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Lawrence, KSTotal failure of the landing gear retraction/extension assembly. Contributing factors in this accident were worn parts in the landing gear retraction/extension assembly, and mechanical binding of the extension assembly.NTSB DEN07WA147Accident · 2 fatalForeign investigationPiper PA-39 · Vannes, FranceNTSB MIA07FA117Accident · 2 fatalField investigationFinal reportPiper PA-30 · Nichols, FLFailure of the flight crew to maintain minimal controllable airspeed following a total loss of power in the right engine.NTSB SEA07LA190Accident · Serious injuriesLimited investigationFinal reportChampion 7KCAB · Orangeburg, SCThe pilot's failure to maintain airspeed during go-around which resulted in a stall. The tailwind was a factor.NTSB DEN07CA103Accident · No injuriesData collectionFinal reportPiper PA-30 · Highgate, VTThe pilot's failure to maintain airspeed on approach resulting in the stall and subsequent impact with terrain.NTSB ANC07CA030Accident · No injuriesData collectionFinal reportPiper PA-22 · Soldotna, AKThe pilot's failure to compensate for a crosswind during the landing roll, which resulted in a loss of control, an encounter with a muddy berm, and a nose over. A factor in the accident was a crosswind.NTSB NYC07FA091Accident · 3 fatalField investigationFinal reportPiper PA-30 · Trappe, MDThe pilot's improper decision to fly into an area of thunderstorms, which resulted in a loss of aircraft control and subsequent in-flight breakup. Contributing to the accident was the thunderstorm.NTSB LAX07LA108Accident · Minor injuriesLimited investigationFinal reportPiper PA-30 · Paris, IDa loss of power in the right engine for undetermined reasons.NTSB SEA07LA059Accident · Minor injuriesLimited investigationFinal reportBarnhart RV-6 · Auburn, WAA loss of engine power due to the obstruction of the engine's air inlet by a fabricated neoprene seal, and inadequate maintenance by unknown maintenance personnel. A contributing factor was the lack of suitable terrain for a forced landing.NTSB DFW07LA075Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Lubbock, TXThe pilot's improper landing flare. A contributing factor was the prevailing tailwind.