NTSB investigations: Continental GTSIO-520-C, 1983
9 cases on aircraft whose registry engine model is Continental GTSIO-520-C. 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
| 1966 | 2 |
|---|---|
| 1967 | 9 |
| 1968 | 5 |
| 1969 | 11 |
| 1970 | 10 |
| 1971 | 9 |
| 1972 | 11 |
| 1973 | 5 |
| 1974 | 10 |
| 1975 | 9 |
| 1976 | 8 |
| 1977 | 7 |
| 1978 | 12 |
| 1979 | 11 |
| 1980 | 10 |
| 1981 | 13 |
| 1982 | 12 |
| 1983 | 9 |
| 1984 | 1 |
| 1985 | 7 |
| 1986 | 5 |
| 1987 | 9 |
| 1988 | 9 |
| 1989 | 5 |
| 1990 | 6 |
| 1991 | 7 |
| 1992 | 2 |
| 1993 | 3 |
| 1994 | 5 |
| 1995 | 7 |
| 1996 | 2 |
| 1998 | 6 |
| 1999 | 7 |
| 2000 | 3 |
| 2001 | 2 |
| 2002 | 6 |
| 2003 | 6 |
| 2004 | 8 |
| 2005 | 4 |
| 2006 | 8 |
| 2007 | 4 |
| 2008 | 4 |
| 2009 | 5 |
| 2010 | 3 |
| 2011 | 1 |
| 2012 | 4 |
| 2013 | 1 |
| 2014 | 3 |
| 2015 | 2 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 3 |
| 2021 | 3 |
| 2022 | 3 |
| 2023 | 3 |
| 2024 | 3 |
| 2025 | 1 |
| 2026 | 3 |
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\") = 1983
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17035'))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17035'))
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 LAX84LA069Accident · No injuriesLimited investigationFinal reportCessna TU206E · Red Rock, AZThe acft taxied into a ditch after landing on a road at night. After the acft came to rest it was apparently intentionally burned. Sob & injuries are presumed. The landing site was marked by the placement of white cloths along the edges of the road. The acft…NTSB DEN84FA004Accident · No injuriesField investigationFinal reportCessna 421C · Center, COThe acft collided with a dirt bank after a left engine overspeed and loss of directional control during takeoff. The plthad already aborted one takeoff due to overboost and a sticking wastegate. The problem seemed corrected after work and lubrication by a…NTSB ATL83LA373Accident · No injuriesLimited investigationFinal reportCessna 401A · Monroe, NCThe left landing gear collapsed on the acft as it was being taxied into the ramp. After turning left into the hub area the landing gear horn sounded and the left gear collapsed, according to the plt. A flt instructor who witnessed the accident said the ACFT'3…NTSB FTW83LA412Accident · No injuriesLimited investigationFinal reportCessna 421C · Port Lavaca, TXThe acft collided with a fence and bushes during takeoff. The rwy was shell and turf construction 2300 ft long. The plt figured the takeoff distance from a chart using dry hard surfaced level rwy. The acceleration seemed slow according to a witness and the…NTSB DEN83FA193Accident · 1 fatalField investigationFinal reportCessna 421A · West Jordan, UTInvestigation revealed that the plt aborted two takeoff attempts due to a 'roughness' in one eng. Not able to duplicate the roughness during subsequent ground checks, the plt departed. At an alt of 300 AGL the left eng began to surge and the right eng,…NTSB LAX83IA345Incident · No injuriesIncident investigationFinal reportCessna 411 · Huntington Bch., CAPilot inadvertantly landed with gear up due to the distraction of making a short field landing.NTSB LAX83LA259Accident · No injuriesLimited investigationFinal reportCessna 421B · Buckeye, AZThe plt had made 3 night landings at the strip during the past 6 mths. The procedure that had been used for lighting thestrip was to place a vehicle at the west end with the headlights facing east down the centerline of the strip. However, on the night of the…NTSB DEN83LA081Accident · No injuriesLimited investigationFinal reportCessna 421C · Gunnison, COThe plt began taking off on rwy 06 with a wind from 190 deg at 8 KTS. He stated that max power & RPM were obtained. He noted that he obtained 39 inches of manifold pressure & 2235 RPM at 100 KTS IAS. Reportedly, the acft rotated properly, but began to vibrate…NTSB ATL83LA120Accident · No injuriesLimited investigationFinal reportCessna 421 · Dayton, TNThe Cessna 421 collided with trees during the landing approach while on a corporate flight. The weather was IMC at the accident site and the acft was on an IFR flight plan. The acft was substantially damaged but the pilot was not injured. The acft contacted…