Fatal NTSB investigations: Continental I0-470 series, 1983
9 cases on aircraft whose registry engine model is Continental I0-470 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 | 4 |
|---|---|
| 1966 | 2 |
| 1967 | 3 |
| 1968 | 2 |
| 1969 | 5 |
| 1970 | 3 |
| 1971 | 2 |
| 1972 | 5 |
| 1973 | 1 |
| 1974 | 2 |
| 1975 | 3 |
| 1976 | 3 |
| 1977 | 1 |
| 1978 | 10 |
| 1979 | 8 |
| 1980 | 9 |
| 1981 | 10 |
| 1982 | 6 |
| 1983 | 9 |
| 1984 | 8 |
| 1985 | 5 |
| 1986 | 6 |
| 1987 | 8 |
| 1988 | 4 |
| 1989 | 3 |
| 1990 | 1 |
| 1991 | 2 |
| 1992 | 5 |
| 1993 | 5 |
| 1994 | 8 |
| 1995 | 3 |
| 1996 | 3 |
| 1997 | 2 |
| 1998 | 1 |
| 1999 | 2 |
| 2000 | 5 |
| 2001 | 8 |
| 2002 | 6 |
| 2003 | 7 |
| 2004 | 5 |
| 2005 | 9 |
| 2006 | 7 |
| 2007 | 5 |
| 2008 | 4 |
| 2009 | 5 |
| 2010 | 8 |
| 2011 | 3 |
| 2012 | 3 |
| 2013 | 5 |
| 2014 | 3 |
| 2015 | 6 |
| 2016 | 4 |
| 2017 | 3 |
| 2018 | 6 |
| 2019 | 3 |
| 2020 | 4 |
| 2021 | 3 |
| 2022 | 6 |
| 2023 | 4 |
| 2024 | 4 |
| 2025 | 8 |
| 2026 | 3 |
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\") = 1983
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 ('17027'))
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") = 1983
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 ('17027'))
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 FTW84FA045Accident · 2 fatalField investigationFinal reportCessna 310L · Bartlesville, OKThe acft was observed at 300-500 ft on a downwind leg over the brightly lighted city. After passing the city the acft entered a very dark & hilly area immediately north of the city. He then made a left turn onto base leg & remained over unlighted & hilly…NTSB LAX84FA012Accident · 2 fatalField investigationFinal reportCessna 210-5 (205) · Schurz, NVThe acft was on a crosscountry flight in VFR conditions. The non-instrument rated pilot encountered instrument conditions at night and lost control of the acft in flight. The post crash investigation revealed evidence of an inflight structural failure due to…NTSB MKC83FA128Accident · 4 fatalField investigationFinal reportBeech J35 · Knoxville, IAThe acft was observed to lift off the rwy aft abt a 900 ft ground roll. The lndg gear began to retract as it lifted off, and it began an immediate left turn overflying the airport hangars. It was further observed with the wings aligned with the ground in a 90…NTSB LAX83FA279Accident · 2 fatalField investigationFinal reportBeech 95-B55 · Van Nuys, CAThe acft crashed in a residential area after a loss of control by the plt. The acft was climbing through an overcast in IFR conditions and last reported 'four' in response to a request for altitude. This was the last radio transmission received from the flt.…NTSB ATL83FA129Accident · 2 fatalField investigationFinal reportBeech K35 · Birmingham, ALThe acft collided with trees and terrain during a practice localizer approach at night to rwy 23 at Birmingham municipalarpt. The weather was VMC and the pilot was not instrument rated. On approaching Birmingham from tri-cities, NC the pilot asked for a…NTSB FTW83FA142Accident · 1 fatalField investigationFinal reportCessna 210-5 · Orange Grove, TXThe plt was believed to have departed hebbronville muni arpt at about 0500 CST. When the acft failed to arrive at its destination, a search was initiated. The wreckage was found where it crashed in an area of mesquite trees & brush, about halfway between the…NTSB LAX83FA350Accident · 5 fatalField investigationFinal reportBeech N35 · Mount Shasta, CAThe acft flew into mt reddy at about 9000 ft level. The clouds were as low as 5000 and the mountain tops were obscured. The plts in flt wx briefing contained the advice that VFR flt along his route was not recommended because the mt tops were obscured in…NTSB NYC83FA054Accident · 4 fatalField investigationFinal reportCessna 310R · Atlantic City, NJThe flt proceeded routinely from chicago to Atlantic City. Communications and procedures all seemed routine and normal and at 1901 local control at Atlantic City informed the pilot that he was one mile out and should be picking up the 'rabbit' momentarily. At…NTSB SEA83LA209Accident · 2 fatalLimited investigationFinal reportBellanca 14-19-3 · Goldendale, WAThe pilot's inadequate preflight and in-flight planning, which resulted in flight into adverse weather conditions and clearance from trees not maintained. Factors contributing to the accident included the clouds, low ceilings, and turbulence.