NTSB investigations: Piper PA-22-150, 1984
15 cases on aircraft the registry lists as Piper PA-22-150. 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 | 114 |
|---|---|
| 1965 | 108 |
| 1966 | 96 |
| 1967 | 78 |
| 1968 | 69 |
| 1969 | 55 |
| 1970 | 52 |
| 1971 | 47 |
| 1972 | 35 |
| 1973 | 32 |
| 1974 | 21 |
| 1975 | 27 |
| 1976 | 40 |
| 1977 | 33 |
| 1978 | 31 |
| 1979 | 28 |
| 1980 | 19 |
| 1981 | 17 |
| 1982 | 12 |
| 1983 | 20 |
| 1984 | 15 |
| 1985 | 12 |
| 1986 | 20 |
| 1987 | 14 |
| 1988 | 17 |
| 1989 | 18 |
| 1990 | 12 |
| 1991 | 18 |
| 1992 | 15 |
| 1993 | 8 |
| 1994 | 11 |
| 1995 | 7 |
| 1996 | 10 |
| 1997 | 10 |
| 1998 | 10 |
| 1999 | 9 |
| 2000 | 9 |
| 2001 | 10 |
| 2002 | 5 |
| 2003 | 6 |
| 2004 | 5 |
| 2005 | 11 |
| 2006 | 7 |
| 2007 | 7 |
| 2008 | 7 |
| 2009 | 7 |
| 2010 | 7 |
| 2011 | 6 |
| 2012 | 8 |
| 2013 | 3 |
| 2014 | 3 |
| 2015 | 2 |
| 2016 | 2 |
| 2017 | 8 |
| 2018 | 4 |
| 2019 | 12 |
| 2020 | 7 |
| 2021 | 5 |
| 2022 | 9 |
| 2023 | 4 |
| 2024 | 8 |
| 2025 | 5 |
| 2026 | 7 |
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\") = 1984
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102210'))
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") = 1984
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102210'))
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 ANC85LA018Accident · No injuriesLimited investigationFinal reportPiper PA-22 · Minchumina, AKThe acft made a hard landing on a frozen lake during a precautionary landing. The plt said that cargo on board had shifted in flt and he also had a loss of 15 mph in airspeed. Thinking it might be an icing problem, the plt made the unscheduled landing. No ice…NTSB CHI84LA370Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Lake City, MIAccording to the plt, at about 30 ft AGL after takeoff the eng RPM began to decrease. The acft flew into a tree adjacent to a road near the end of the rwy. A visual inspection of the engine revealed no mechanical malfunctions. The property owner reported that…NTSB SEA84LA213Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-150 · Shoshone, IDThe plt attempted takeoff from a wet alfalfa field. High vegetation and soft terrain prevented proper acceleration to lift off speed. The nosewheel struck an embankment and the aircraft nosed over.NTSB DEN84LA267Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Aurora, COPlt stated that following a hard landing, directional control was lost. Acft departed runway and collided with dirt berm.NTSB FTW84LA370Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-150 · Tahlequah, OKLaw enforcement officers responding to the acft accident found the acft inverted beyond the south end of the runway. Plt stated he and his passengers had been drinking beer and decided to go flying. Plt's statements to officers are not clear on exact events…NTSB ANC84FA131Accident · No injuriesField investigationFinal reportPiper PA-22 · Delta Junction, AKThe acft was damaged in an off arpt landing after the engine lost power. The plt stated the acft was operating on automotive fuel without the required supplemental type certificate. The acft was operating without the required annual inspection and the tbo had…NTSB CHI84LA322Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Findlay, OHDuring the initial takeoff climb at an alt of aprx 1400 ft MSL the engine quit. Attempts to regain power failed. The acft nosed over during a forced landing in a corn field. Post accident investigation of the engine revealed a broken carburetor heat linkage…NTSB NYC84LA250Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · E. Hanover, NJThe acft made a forced landing shortly after takeoff when the engine lost power. At about 400 ft AGL the engine sputtered and stopped. The fuel tanks were switched by the plt and the engine made a slight pwr gain and quit again. A landing was made in a marshy…NTSB FTW84FA288Accident · 1 fatalField investigationFinal reportPiper PA-22-150 · Quinlan, TXSeveral witnesses stated the acft 'buzzed them below tree-top level' before the accident. Witnesses also stated that the engine 'sounded like it cut out.' The acft impacted the ground in a steep left bank. Post accident inspection revealed no evidence of any…NTSB FTW84LA245Accident · Minor injuriesLimited investigationFinal reportPiper PA-22-150 · Tallulah, LAThe acft caught fire shortly after takeoff and the plt landed in a wheat field. The nosewheel dug into the soft field and the acft nosed over. This acft has been the subject of recommendations on worn and deteriorated fuel lines. The pltsdescription of his…NTSB LAX84LA290Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Phoenix, AZThe plt had just purchased the acft & had flown it only 3 hrs. The purpose of this flt was to ferry it to deer valley for a paint job. He reported that when he landed, the wind was from 150 deg at 6 gusting 12 KTS. During the landing, the nose wheel touched…NTSB SEA84LA095Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Davenport, WADuring the landing roll the brakes were applied with no effect. The acft went off the end of the rwy into a ditch and nosed over. Examination of the acft showed the brake system low on fluid and the master cylinder diaphragm ruptured.NTSB NYC84LA128Accident · No injuriesLimited investigationFinal reportPiper PA-22-150 · Factoryville, PAPlt stated that he inadvertently allowed the acft to drift left during the landing roll when he reached for the hand brake. The left main and nose gears contacted a snow bank and the acft nosed over.NTSB DEN84LA090Accident · Serious injuriesLimited investigationFinal reportPiper PA-22-150 · Laramie, WYThe plt stated that when he was 10 miles southeast with airport lights in sight, a convair plt reported inbound on an IFR clearance to land. Not wanting to possibly cause the convair plt to make a missed approach he elected to make a turn. In the turn, he…NTSB ATL84FLT02Accident · Serious injuriesFinal reportPiper PA-22-150 · Memphis, TNThe acft struck a powerline and crashed 1.5 mi south of Memphis airport while on a ILS localizer app to rwy 36R. The wx at the time of acc was ceiling 200 ft, visibility 3/4 mile with fog. The acft was equipped with a VOR localizer, but no glide sloop…