Fatal NTSB investigations: Continental IO-520 series, 2006
16 cases on aircraft whose registry engine model is Continental IO-520 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 | 1 |
|---|---|
| 1966 | 3 |
| 1967 | 1 |
| 1968 | 4 |
| 1969 | 4 |
| 1970 | 2 |
| 1972 | 5 |
| 1973 | 1 |
| 1974 | 1 |
| 1975 | 3 |
| 1976 | 9 |
| 1977 | 6 |
| 1978 | 17 |
| 1979 | 30 |
| 1980 | 15 |
| 1981 | 15 |
| 1982 | 22 |
| 1983 | 21 |
| 1984 | 13 |
| 1985 | 7 |
| 1986 | 13 |
| 1987 | 5 |
| 1988 | 18 |
| 1989 | 9 |
| 1990 | 9 |
| 1991 | 11 |
| 1992 | 9 |
| 1993 | 9 |
| 1994 | 6 |
| 1995 | 12 |
| 1996 | 11 |
| 1997 | 9 |
| 1998 | 12 |
| 1999 | 13 |
| 2000 | 8 |
| 2001 | 19 |
| 2002 | 17 |
| 2003 | 20 |
| 2004 | 21 |
| 2005 | 26 |
| 2006 | 16 |
| 2007 | 18 |
| 2008 | 15 |
| 2009 | 10 |
| 2010 | 14 |
| 2011 | 22 |
| 2012 | 9 |
| 2013 | 6 |
| 2014 | 14 |
| 2015 | 11 |
| 2016 | 8 |
| 2017 | 6 |
| 2018 | 10 |
| 2019 | 16 |
| 2020 | 13 |
| 2021 | 10 |
| 2022 | 6 |
| 2023 | 4 |
| 2024 | 7 |
| 2025 | 6 |
| 2026 | 8 |
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.\"highestInjuryLevel\" = 'Fatal'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17032'))
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."highestInjuryLevel" = 'Fatal'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17032'))
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 CHI07FA045Accident · 4 fatalField investigationFinal reportBeech A36 · Chattanooga, TNThe pilot's reported spatial disorientation which lead to not maintaining altitude/clearance from terrain and not obtaining/maintaining a proper climb rate during the missed approach. Factors were the night, the clouds encountered on approach, and trees.NTSB DFW07FA039Accident · 3 fatalField investigationFinal reportBellanca 17-30A · Jay, OKThe loss of engine power for undetermined reasons and the pilot's improper decision to extend the landing gear for the water landing. Contributing factors were the prevailing night conditions and the lack of suitable terrain for the forced landing.NTSB NYC07FA042Accident · 2 fatalField investigationFinal reportCessna 210K · Edgewater, MDThe pilot's failure to maintain the proper altitude/clearance will on approach, which resulted in an in-flight collision with trees. Contributing to the accident was the night-light conditions, an obstruction light that was not illuminated, and trees that had…NTSB NYC06FA230Accident · 1 fatalField investigationFinal reportBeech S35 · Lake City, FLA loss of control during an unintentional takeoff for an undetermined reason.NTSB ATL06FA129Accident · 3 fatalField investigationFinal reportBeech F-33A · Alabaster, ALThe pilot's failure to maintain airspeed while maneuvering toward an emergency landing area following the total loss of engine power shortly after takeoff resulting in an inadvertent stall, uncontrolled descent, and collision with the ground, and a fence. A…NTSB DFW06LA195Accident · 1 fatalLimited investigationFinal reportCessna A188B · Sumrall, MSThe pilot's failure to maintain airspeed which resulted in an inadvertent stall. Contributing factors were the partial loss of engine power and the low altitude.NTSB MIA06LA122Accident · 1 fatalLimited investigationFinal reportCessna 320E · Wimauma, FLPilot's inadequate preflight planning and exceeding the weight and balance limitations of the airplane.NTSB CHI06LA175Accident · 1 fatalLimited investigationFinal reportCessna A185E · Clear Lake, MNThe pilot's misjudged flare that resulted in a hard landing and subsequent nose over. A factor to the accident was the grass runway that the forward landing gear dug into during the hard landing, resulting in the amphibian airplane nosing over.NTSB CHI06FA152Accident · 1 fatalField investigationFinal reportBeech B36TC · Gregory, MIThe non-mechanical loss of engine power for undetermined reasons during cruise flight and the unsuitable terrain the pilot selected for the forced landing. A factor was the tree that was impacted during the forced landing. An additional factor was the…NTSB CHI06FA141Accident · 1 fatalField investigationFinal reportCessna 210N · Ft. Thomas, KYThe pilot failed to maintain altitude/clearance with trees while attempting to return to the airport.NTSB CHI06FA117Accident · 5 fatalField investigationFinal reportCessna U206G · Bloomington, INThe pilot's continued descent below decision height and not maintaining adequate altitude/clearance from the trees while on approach. Factors were the the night lighting conditions, and the mist.NTSB LAX06FA130Accident · 2 fatalField investigationFinal reportBeech F33A · Kingman, AZThe noninstrument rated pilot's cruise flight into instrument meteorological conditions, and his failure to maintain control of the airplane, which resulted in an uncontrolled descent, and an in-flight collision with terrain. Factors associated with the…NTSB LAX06FA129Accident · 2 fatalField investigationFinal reportBeech A36 · Santa Monica, CAThe failure of an aviation maintenance technician to properly torque and cotter pin the number 2 connecting rod bolts at their attach point to the crankshaft, which resulted in the separation of the connecting rod in flight, and complete power loss.NTSB CHI06FA090Accident · 2 fatalField investigationFinal reportBeech J35 · Holland, MIA lossof engine power due to fuel starvation as a result of the pilot's improper fuel system management and failure to select a tank containing fuel. A factor was the dark night conditions.NTSB LAX06FA099Accident · 1 fatalField investigationFinal reportBeechcraft F33A · Buckeye, AZThe student pilot's failure to maintain aircraft control for undetermined reasons.NTSB NYC06FA048Accident · 2 fatalField investigationFinal reportBeech D55 · Dawson, GAThe pilot's failure to maintain sufficient airspeed to preclude a stall, which resulted in an inadvertent stall and loss of control while circling to land. Factors associated with the accident were the pilot's inadequate in-flight planning and weather…