Fatal NTSB investigations: Continental TSIO-520 series, 1983
10 cases on aircraft whose registry engine model is Continental TSIO-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
| 1968 | 1 |
|---|---|
| 1972 | 1 |
| 1973 | 1 |
| 1974 | 1 |
| 1976 | 2 |
| 1977 | 2 |
| 1978 | 10 |
| 1979 | 10 |
| 1980 | 11 |
| 1981 | 11 |
| 1982 | 13 |
| 1983 | 10 |
| 1984 | 9 |
| 1985 | 10 |
| 1986 | 11 |
| 1987 | 9 |
| 1988 | 10 |
| 1989 | 2 |
| 1990 | 3 |
| 1991 | 9 |
| 1992 | 5 |
| 1993 | 4 |
| 1994 | 8 |
| 1995 | 6 |
| 1996 | 4 |
| 1997 | 8 |
| 1998 | 4 |
| 1999 | 4 |
| 2000 | 4 |
| 2001 | 11 |
| 2002 | 12 |
| 2003 | 20 |
| 2004 | 13 |
| 2005 | 10 |
| 2006 | 16 |
| 2007 | 11 |
| 2008 | 8 |
| 2009 | 3 |
| 2010 | 13 |
| 2011 | 8 |
| 2012 | 9 |
| 2013 | 9 |
| 2014 | 6 |
| 2015 | 3 |
| 2016 | 7 |
| 2017 | 9 |
| 2018 | 7 |
| 2019 | 4 |
| 2020 | 8 |
| 2021 | 7 |
| 2022 | 3 |
| 2023 | 6 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 1 |
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 ('17040'))
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 ('17040'))
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 CHI84FA053Accident · 3 fatalField investigationFinal reportCessna T210M · White Lk Twnshp, MIAt about 1600, the acft was taken out of a heated hangar & parked on the ramp for refueling. It remained outside until the plt took off at about 1740 EST. During that time, snow was falling & the temp dropped from 34 to 31 deg. The plt initially contacted the…NTSB ATL84MA052Accident · 4 fatalMajor investigationFinal reportBeech 58TC · Knoxville, TNDuring arrival, the plt checked in with Knoxville apch control & stated that he was proceeding to the downtown arpt for landing. At that time, the wx at mcghee-tyson arpt (aprx 10 mi ssw) was clear with 7 mi visibility. About 10 min later, the plt reported…NTSB ATL84FA038Accident · 5 fatalField investigationFinal reportCessna T210M · Banner Elk, NCBefore takeoff, the plt obtained wx for ashville & hickory, NC & for the tri-city arpt, all of which were 30 to 54 mi from Banner Elk, NC. At that time, he told the briefer that there were clouds at Banner Elk, but he thought he could get out all right. The…NTSB LAX84LA044Accident · 1 fatalLimited investigationFinal reportCessna TU206G · Reno, NVThe pilot's body was found under the front of the acft by the propeller. All cockpit controls were in the start positionand the acft was not chocked or tied down. The payroll checks the pilot was to deliver were found in the acft.NTSB LAX83FA444Accident · 1 fatalField investigationFinal reportCessna T210M · Santa Ana, CAAfter landing at night, the plt taxied to a non-illuminated ramp area & stopped to deplane the passenger, who held a student plt certificate. The purpose of the passenger deplaning in that area was for her to obtain a vehicle & meet the plt at the acft's…NTSB LAX83FA348Accident · 2 fatalField investigationFinal reportCessna T210N · Watsonville, CAThe plt, who was a contractor, was scheduled to attend a heavy equip't auction in sacramento to begin a 1000. Witnesses heard normal eng sounds as the acft departed rwy 19 & turned to a left downwind departure turn. The acft was observed proceeding on a NE…NTSB NYC83FA126Accident · 4 fatalField investigationFinal reportBeech B36TC · Farmingdale, NYThe acft collided with a powerline static wire during an instrument landing approach. The private plt was instrument rated and had received a weather briefing and filed an IFR flt plan. He commented to the briefer that 'it doesn't sound too good' and that he…NTSB LAX83FA166Accident · 3 fatalField investigationFinal reportBeech A36TC · Sedona, AZDuring preflt briefings, the plt was briefed to expect deteriorating wx conditions with associated flt precautions for mountain obscurement, icing & moderate turbulence. The wx briefings were complete, except due to an inoperative circuit, the 0654 prescott &…NTSB DEN83FA059Accident · 4 fatalField investigationFinal reportCessna 340A · Aspen, COPrior to departure the flt was given an IFR clearance which began at herls intersection (16 mi nne) & to cross herls at or above 16,000 ft MSL. Departure arpt field elev is 7,793 ft. flts are required to proceed VFR to the initial fix of the IFR clearance.…NTSB FTW83FA108Accident · 1 fatalField investigationFinal reportBeech A36TC · Addison, TXThe non-instrument rated, student plt used another person's name while filing an instrument flt plan. When he contacted ground control for departure, he was advised that the arpt had just become IFR. After some confusion concerning canceling & filing flt…