NTSB investigations: Piper PA-38-112, NE
7 cases on aircraft the registry lists as Piper PA-38-112. 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
| 1981 | 1 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1993 | 1 |
| 1996 | 1 |
| 1998 | 1 |
| 2001 | 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\" = 'NE' 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 ('7103812'))
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" = 'NE' 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 ('7103812'))
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 CHI02LA048Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · O'Neill, NEThe inadequate preflight planning by the pilot resulting in the exhaustion of the fuel supply, and the pilot not maintaining directional control during the forced landing. A factor was the unsuitable landing area selected by the pilot, and the ditch.NTSB CHI98LA140Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Omaha, NEThe fatigue failure of the crankshaft which resulted from a spun bearing and the low altitude at which the loss of engine power occurred. A factor in the accident was the embankment on which the airplane was landed.NTSB CHI96LA298Accident · No injuriesLimited investigationFinal reportPiper PA-38 · Fairbury, NEinadequate airspeed and an inadvertant stall during the initial takeoff climb. Factors associated with the accident were the rough terrain used for takeoff and the ditch at the departure end on the field.NTSB CHI93FA133Accident · 1 fatalField investigationFinal reportPiper PA-38-112 · Plattsmouth, NEThe pilot-in-command (CFI)'s failure to maintain airspeed.NTSB MKC84LA286Accident · No injuriesLimited investigationFinal reportPiper PA-38-112 · Beatrice, NEDuring the flare an uncontrolled rate of descent developed resulting in a touchdown short of the rwy threshold. The mainldg gear struck the 5 inch exposed rwy lip. Density alt was aprx 4,200 ft.NTSB MKC83LA169Accident · No injuriesLimited investigationFinal reportPiper PA-38 · North Platte, NEThe pilot had been flying for about 1 hour in the local area and was returning from the practice area at 1100 feet AGL. In preparation for landing he advanced the mixture to full rich and the engine lost power. He tried emerg procedures but the engine did not…NTSB MKC81DCJ34Accident · No injuriesClosedPiper PA-38 · Kearney, NE