NTSB investigations: Lycoming IO-320 series, 2003
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
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\") = 2003
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") = 2003
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 IAD04CA006Accident · No injuriesData collectionFinal reportPiper PA-30 · Louisville, KYThe pilot's improper flare, which resulted a hard landing. A factor was the glare from the setting sun.NTSB ATL04LA052Accident · No injuriesLimited investigationFinal reportPiper PA-39 · Kissimmee, FLThe pilot's failure to maintain directional control which resulted in a collision with terrain and obstacles following a loss of right engine power.NTSB LAX04FA057Accident · 2 fatalField investigationFinal reportWing D-1 · Rosamond, CAThe flying pilot's failure to obtain/maintain control of the airplane during practice stalls, which resulted in the inadvertent entry into a spin.NTSB ATL04FA027Accident · 1 fatalField investigationFinal reportPiper PA-30 · Spartanburg, SCThe pilot's failure to follow IFR procedures and descent below the glide path, which resulted in an inflight collision with trees during an instrument approach. A factor was the pilot's impairment due to the sedating effects of medication.NTSB FTW03LA206Accident · No injuriesLimited investigationFinal reportBellanca 7KCAB · McKinney, TXThe pilot's failure to maintain airspeed resulting in an inadvertent stall during landing. A contributing factor was flaring too high.NTSB CHI03LA212Accident · No injuriesLimited investigationFinal reportCessna 172P · Pinckneyville, ILThe planned approach not maintained by the pilot and the delayed remedial action by the certified flight instructor. A contributing factor to the accident was the approach light.NTSB NYC03LA154Accident · Serious injuriesLimited investigationFinal reportWohlers Falco F.8L · Ashland, OHA loss of engine power due to the failure of the engine air intake duct tubing, which resulted in a total blockage of the induction inlet duct. A factor related to the accident was the inadequate 100-hour inspection by maintenance personnel. (This narrative…NTSB IAD03FA058Accident · 2 fatalField investigationFinal reportPiper PA-30 · NewPhiladelphia, OHThe pilot's mismanagement of the fuel, and his failure to maintain minimum controllable airspeed with one engine inoperative.NTSB ATL03FA125Accident · 2 fatalField investigationFinal reportBellanca 7KCAB · Dover, TNThe pilot continued VFR flight into adverse weather conditions including instrument meteorological conditions and turbulence in thunderstorms, which resulted in a loss of control in flight and subsequent collision with terrain.NTSB LAX03LA155Accident · No injuriesLimited investigationFinal reportMonaghan Glasair · Hayward, CAthe pilot's inadequate recovery from a bounced landing and his failure to maintain directional control, resulting in a ground loop.NTSB NYC03LA065Accident · No injuriesLimited investigationFinal reportCessna 172P · Linden, NJThe pilot's inadequate compensation for the crosswind and his failure to maintain directional control during landing. Factors in the accident were the crosswind and the snowbank.NTSB LAX03FA093Accident · 2 fatalField investigationFinal reportPiper PA-30 · Nipomo, CAthe flying pilot's failure to maintain an adequate airspeed that resulted in a stall/spin.NTSB DEN03LA037Accident · Minor injuriesLimited investigationFinal reportRothrock Cozy Mark IV · Erie, COThe pilot's failure to maintain aircraft control during landing. Contributing factors were the high crosswinds and the gusts.