NTSB investigations: Piper PA-28R-200, 1986
15 cases on aircraft the registry lists as Piper PA-28R-200. 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
| 1969 | 5 |
|---|---|
| 1970 | 10 |
| 1971 | 11 |
| 1972 | 27 |
| 1973 | 37 |
| 1974 | 39 |
| 1975 | 39 |
| 1976 | 44 |
| 1977 | 50 |
| 1978 | 41 |
| 1979 | 25 |
| 1980 | 27 |
| 1981 | 25 |
| 1982 | 15 |
| 1983 | 20 |
| 1984 | 13 |
| 1985 | 11 |
| 1986 | 15 |
| 1987 | 15 |
| 1988 | 17 |
| 1989 | 15 |
| 1990 | 11 |
| 1991 | 14 |
| 1992 | 17 |
| 1993 | 13 |
| 1994 | 18 |
| 1995 | 8 |
| 1996 | 8 |
| 1997 | 18 |
| 1998 | 12 |
| 1999 | 9 |
| 2000 | 10 |
| 2001 | 6 |
| 2002 | 9 |
| 2003 | 11 |
| 2004 | 6 |
| 2005 | 7 |
| 2006 | 5 |
| 2007 | 7 |
| 2008 | 4 |
| 2009 | 8 |
| 2010 | 7 |
| 2011 | 3 |
| 2012 | 7 |
| 2013 | 5 |
| 2014 | 2 |
| 2015 | 10 |
| 2016 | 9 |
| 2017 | 11 |
| 2018 | 5 |
| 2019 | 8 |
| 2020 | 4 |
| 2021 | 5 |
| 2022 | 2 |
| 2023 | 3 |
| 2024 | 5 |
| 2025 | 5 |
| 2026 | 1 |
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\") = 1986
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
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") = 1986
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
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 CHI87FA048Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · N. Manitou Isl., MIThe plt had recvd an unfavorable wx brief that included a SIGMET on flt icing. Enroute during flt over a large body of water he experienced power loss and was at too low a altitude to glide to shore. The plt attempted to ld on a island but crashed in a lake.NTSB FTW87FA029Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Petersburg, TXAcft impacted in a 95 deg nose down attitude following a loss of control in IMC conditions while the non-instrument rated pvt plt was being vectored to the final app crs. Plt had filed IFR and had experienced difficulties thru out the flt. As he was given…NTSB CHI87LA022Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-200 · South Bend, INDuring cruise at 7000' MSL, the plt assumed that he was having an electrical failure because he had not heard any ARTCC transmissions, fuel gauges were indicating low fuel, ammeter reading was zero, and landing gear would not cycle. He shut off all electrical…NTSB BFO87FA004Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Mount Pleasant, MDThe acft was on the second apch attempt for ILS rwy 23 when the accident occurred- on the first attempt the pilot flew outbound instead of inbound on the localizer course. For the second attempt the pilot was cleared for a full apch for ILS rwy 23; which…NTSB MIA87LA005Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-200 · Lakeland, FLThe plt stated the acft lost power and he was unable to make it to the arpt. The acft crashed in a field about 3/4 of a mile from the Lakeland arpt. Post crash examination of the eng revealed a complete failure of both magnetos, resulting in the loss of power…NTSB FTW86LA157Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Afton, OKThe pilot stated he was making a precautionary landing at night due to engine roughness and impacted electrical transmission wires. Investigation failed to disclose any reason for the reported engine roughness.NTSB MIA86LA209Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Marathon, FLFlight experienced loss of engine oil and subsequent seizing of the engine at which time the aircraft was ditched in the gulf of Mexico. Post crash examination of the engine revealed the oil line from the propeller govenor to the engine nose case had failed…NTSB SEA86LA170Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Royal City, WAThe plt was landing the acft on rwy 27, toward the sun. With the sun in her eyes, she did not see a 300 lb calf on the rwy. The acft struck & killed the calf & was substantially damaged.NTSB BFO86FID09Accident · No injuriesFinal reportPiper PA-28R-200 · Montpelier Sta., VAThe acft collided with 2 fences during an off arpt forced landing after a pwr loss. Post acc eng inspection showed internal failure of the eng. #2 connecting rod bolt failed in fatigue through 40 percent of the diameter. The remainder failed in tension. The…NTSB MKC86LA135Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Mammoth Spring, ARThe pilot stated that the aircraft had plenty of oil prior to departure and that the flight was proceeding normally when, suddenly, the oil pressure dropped to zero. While subsequently heading for a nearby airport, the engine lost power and seized, forcing an…NTSB NYC86LA105Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Westhampton Bch, NYThe instrument instructional flight returned to the airport late at night and successfully completed two instrument approaches with missed approaches. The pilots had been advised of a low layer of fog on the airport. On the third and final approach, after…NTSB BFO86FA023Accident · Minor injuriesField investigationFinal reportPiper PA-28R-200 · Camp Springs, MDDuring a flt to prepare the student for a CFI check ride, both the student and the CFI could not obtain a green light confirming the nose gear was down and locked. After numerous attempts to assure it was down and locked the acft was landed at andrews afb.…NTSB MIA86LA118Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Umatilla, FLThe plt reported that he flared the acft too high while landing. The acft stalled too soon and a hard landing resulted.NTSB ATL86LA089Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Hanceville, ALWhile enroute to birmingham the pilot experienced a complete power failure when no. 2 cylinder separated from the engine assembly. The pilot attempted to make an emergency landing on interstate 65 near Hanceville, AL, and the aircraftcollided with an…NTSB DEN86LA065Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Sterling, COAccording to the plt, during the checkride for his commercial plt certificate, the flt examiner gave him a simulated electrical failure & turned the landing lights off. The plt stated that during the night landing flare, he lost visual reference with the rwy…