NTSB investigations: Lycoming IO-320 series, 2011
13 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
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\") = 2011
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") = 2011
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 ERA12LA100Accident · No injuriesLimited investigationFinal reportSigmon Harvey E Vans RV 6 · Abingdon, VAThe failure of the Pitts pilot to see and avoid the RV-6 that had landed ahead. Contributing to the accident was the Pitts pilot's inability to hear the RV-6 pilot's radio calls due to the lack of a radio in the Pitts.NTSB CEN11CA662Accident · No injuriesData collectionFinal reportPiper PA-30 · Saguache, COThe pilot's failure to maintain airplane control during the aborted takeoff.NTSB ERA11LA438Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · St. Petersburg, FLThe pilot's improper rotation during takeoff, resulting in a stall and subsequent collision with the ground.NTSB WPR11CA329Accident · No injuriesData collectionFinal reportBellanca 7KCAB · Albany, ORThe pilot's inadequate preflight inspection and failure to ensure the fuel cap was secured after refueling, which resulted in a total loss of engine power due to fuel exhaustion.NTSB ERA11CA396Accident · No injuriesData collectionFinal reportPiper PA-30 · Plant City, FLThe failure of a screw in the nose landing gear aligner assembly for undetermined reasons, which prevented the landing gear from fully extending.NTSB ERA11CA385Accident · No injuriesData collectionFinal reportCessna 172P · Baltimore, MDThe student pilot's failure to maintain aircraft control following a bounced landing.NTSB CEN11FA434Accident · 1 fatalField investigationFinal reportSchaffer Gary W Lancair · Yukon, OKThe pilot's use of an excessive bank angle while in the airport traffic pattern, which resulted in an accelerated stall. Contributing to the accident were the pilot’s lack of experience in the airplane and the pilot’s distracted attention to the rough running…NTSB ERA11FA348Accident · 3 fatalField investigationFinal reportPiper PA-28-140 · Guntersville, ALThe pilot's excessive pitch attitude, which resulted in an aerodynamic stall during the takeoff initial climb. Contributing to the accident was the pilot’s failure to comply with weight and balance limitations.NTSB CEN11LA364Accident · Minor injuriesLimited investigationFinal reportPiper PA30 · Phillipsburg, OHThe pilot’s failure to maintain directional control during takeoff following a loss of left engine power for undetermined reasons.NTSB ERA11CA248Accident · No injuriesData collectionFinal reportWalker J C Lancair 320 · Baltimore, MDThe pilot's improper recovery from a bounced landing.NTSB CEN11CA288Accident · No injuriesData collectionFinal reportPiper PA-30 · Austin, TXThe pilot’s loss of directional control during landing which resulted in a runway excursion.NTSB CEN11LA262Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Ruidoso, NMThe left engine's intermittent loss of power during initial climb for undetermined reasons. Contributing to the accident was the high density altitude at the time of the accident.NTSB WPR11LA113Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Big Bear City, CAThe pilot’s failure to maintain the minimum single-engine control speed while on final approach for landing. Contributing to the accident was the pilot's decision to fly with a known deficiency in one engine and a loss of power in that engine for reasons that…