NTSB investigations: Continental TSIO-360 series, 1982
16 cases on aircraft whose registry engine model is Continental TSIO-360 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 |
|---|---|
| 1967 | 1 |
| 1971 | 1 |
| 1974 | 1 |
| 1975 | 2 |
| 1976 | 2 |
| 1977 | 5 |
| 1978 | 18 |
| 1979 | 9 |
| 1980 | 20 |
| 1981 | 14 |
| 1982 | 16 |
| 1983 | 18 |
| 1984 | 15 |
| 1985 | 18 |
| 1986 | 8 |
| 1987 | 11 |
| 1988 | 14 |
| 1989 | 8 |
| 1990 | 8 |
| 1991 | 10 |
| 1992 | 6 |
| 1993 | 7 |
| 1994 | 7 |
| 1995 | 8 |
| 1996 | 6 |
| 1997 | 12 |
| 1998 | 9 |
| 1999 | 12 |
| 2000 | 6 |
| 2001 | 13 |
| 2002 | 13 |
| 2003 | 16 |
| 2004 | 11 |
| 2005 | 10 |
| 2006 | 11 |
| 2007 | 14 |
| 2008 | 12 |
| 2009 | 6 |
| 2010 | 7 |
| 2011 | 9 |
| 2012 | 10 |
| 2013 | 7 |
| 2014 | 11 |
| 2015 | 7 |
| 2016 | 5 |
| 2017 | 9 |
| 2018 | 8 |
| 2019 | 3 |
| 2020 | 7 |
| 2021 | 4 |
| 2022 | 7 |
| 2023 | 11 |
| 2024 | 10 |
| 2025 | 4 |
| 2026 | 2 |
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\") = 1982
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17019', '17023'))
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") = 1982
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('17019', '17023'))
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 LAX83LVD02Accident · No injuriesFinal reportCessna 172 · Gualala, CACessna 172, N29150, & Piper PA-28, N8465Y, were both departing from a pvt, unctld arpt at the same time, but from opposite drctns on the same rwy. Th rwy was crowned in the center which prevented line-of-sight to acft on opposite ends. Each plt stated that he…NTSB DEN82DA202Accident · No injuriesFinal reportPiper PA-34 · Langdon, NDCabin door came open in flight and pilot made a precautionary landing. During roll-out nose gear collapsed as aircraft weight settled on it since it had not fully extended.NTSB ATL82DA253Accident · No injuriesFinal reportPiper PA-34 · Campbellsville, KYWhile taxiing to a hangar the left wheel went off the taxiway causing the left gear to collapse.NTSB ANC82DAG60Accident · 3 fatalFinal reportPiper PA-28R · Dillingham, AKPilot collided with mountainous terrain at the 1400 foot level. He proposed flight on V-452 which does not exist in that area. V-462 would have been appropriate but his position did not coincide with that route. He was on a VFR flight plan. Twilight ended…NTSB FTW82DA311Accident · No injuriesFinal reportPiper PA-34-200T · Eagle Pass, TXThe pilot stated that he overflew the ranch strip and looked it over before landing. He stated that he touched down on the first 200 ft of the 2200 ft, asphalt runway, but each time the brakes were applied, the wheels would lock and skid due to loose gravel…NTSB SEA83FA196Accident · 1 fatalField investigationFinal reportMooney M-20 · Sandy, ORThe acft crashed into rising terrain in marginal weather conditions. No flt plan had been filed. The acft crashed 25 miles from the takeoff point on 6/12/82 and was missing until 9/9/83. The pilot had received a weather briefing from portland fss indicating…NTSB FTW82DA194Accident · No injuriesFinal reportPiper PA-28-236 · Clayton, NMThe pilot reported that during flight, the engine lost power. He tried to land on a nearby airport. However, unexpectedly strong winds were encountered and he made a forced landing in a pastured when he saw he could not reach the airport. During the landing,…NTSB LAX82DA176Accident · No injuriesFinal reportPiper PA-28-201T · Van Nuys, CADuring flight at about 1500 ft, the engine suddenly lost power and the propeller stopped turning. The pilot attempted a restart, but the starter would not turn the propeller. The pilot maneuvered to make a forced landing at the Van Nuys airport. The aircraft…NTSB FTW82FQD10Accident · 4 fatalFinal reportMooney M20K · Van Horn, TXN99996 departed riverside, CA on a flight to nacogdoches, TX the aircraft made a refueling stop in deming, NM, the last known en route position. The left seat pilot held a pvt certificate, the right seat pilot was a former FAA designated pilot examiner.…NTSB CHI82DA120Accident · No injuriesFinal reportPiper PA-34 · Gaylord, MIDuring a night visual approach the aircraft landed about 90 ft short of the runway. The aircraft slid across the ground onto the runway pavement and swerved to the right striking a runway light and ending up on a snowbank.NTSB DEN82DA055Accident · No injuriesFinal reportPiper PA-28R-201T · Longmont, COThe pilot reported that he made a normal approach and touched down in the landing zone as defined by the VASI. However, during the landing roll, the right brake was inoperative. He was unable to stop on the remaining runway while rolling straight ahead. About…NTSB FTW82FQA13Accident · Serious injuriesFinal reportPiper PA-28RT-201T · Toadlena, NMThe non-instrument rated pilot in Piper PA-28RT, N29665, was using a call sign, N1104X, which was the registration number of a destroyed PA-32. He was cleared to climb to FL200, but as he continued, his speech became slurred. He acknowledged an artc…NTSB LAX82FA074Accident · 1 fatalField investigationFinal reportPiper PA-34 · Near Sonoma, CAThe pilot proceeded VFR toward a private strip after an instrument approach to napa county airport. The visibility was not good and the aircraft collided with a hillside while en route. About 5 mi north, the weather at the napa county airport was 500 ft…NTSB LAX82IA062Incident · No injuriesIncident investigationFinal reportPiper PA-28R-201T · Truckee, CADuring the landing roll the aircraft veered sharply to the left and struck a snowbank, collapsing the nose and left main landing gear. Inspection of the runway revealed the presence of several large ice chunks adhering to the runway surface.NTSB MIA82FA038Accident · No injuriesField investigationFinal reportPiper PA-34-200T · Newport Richey, FLThe pilot departed orlando, Florida on a VFR flight to tampa, Florida. At about 1534 EST, the pilot contacted tampa approach control for VFR flight following. Approach control reported radar contact, and at the same time, issued an advisory, "traffic at…NTSB FTW82FPJ11Accident · No injuriesFinal reportPiper PA-28R-201T · Watonga, OKThe pilot stated that the engine lost oil pressure and shortly thereafter quit. During the forced landing the pilot veered the aircraft off the highway he had elected to land on due to oncoming traffic. The aircraft sustained substantial damages due to the…