NTSB investigations: Piper PA-28-161, MD
7 cases on aircraft the registry lists as Piper PA-28-161. 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
| 1984 | 1 |
|---|---|
| 1986 | 1 |
| 1990 | 1 |
| 1999 | 1 |
| 2019 | 1 |
| 2021 | 1 |
| 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 c.\"eventStateOrRegion\" = 'MD' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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 c."eventStateOrRegion" = 'MD' AND c."eventCountry" = 'USA'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102803', '7102834'))
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 ERA26LA262Accident · No injuriesClass 4 · LimitedInvestigation openPiper PA-28-161 · Easton, MDNTSB ERA21LA267Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA-28-161 · Easton, MDA total loss of engine power for reasons that could not be determined.NTSB ERA19TA195Accident · No injuriesClass 3Final reportPiper PA28 · Westminster, MDThe pilot's failure to maintain directional control during recovery from a bounced landing, which resulted in a runway excursion.NTSB NYC00LA041Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Annapolis, MDThe pilot's failure to adequately adjust engine power to compensate for the winds on final approach.NTSB BFO90LA056Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Chester, MDThe pilot's misidentification of a road for the runway. Factors were sunglare and the pilot's unfamiliarity with the airport, and inadequate visual lookout.NTSB BFO86LA017Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Elkton, MDThe acft experienced a loss of pwr during cruise. The student plt reported that carb heat was applied after the initial pwr loss without any change in RPM. He subsequently applied full throttle, but the acft was unable to maintain altitude and a forced ldg…NTSB NYC84FIG01Accident · Minor injuriesFinal reportPiper PA-28-161 · Gathersburg, MDWhile on a second attempt to intercept the LOC on the ILS 23 apch at frederick, MD, the plt reported a low fuel condition to baltimore ATC. At this time ATC suggested the plt fly to either baltimore (34 miles se) or to dulles (25 miles sw) for an apch. A…