NTSB investigations: Piper PA-28-181, OK
6 cases on aircraft the registry lists as Piper PA-28-181. 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 |
|---|---|
| 1982 | 1 |
| 1985 | 2 |
| 1987 | 1 |
| 1998 | 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\" = 'OK' 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 ('7102807', '7102832'))
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" = 'OK' 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 ('7102807', '7102832'))
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 FTW98LA322Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Fairview, OKLoss of engine power due to fuel exhaustion as a result of the pilot's failure to refuel. A factor was the lack of suitable terrain for the forced landing.NTSB FTW87FA168Accident · Serious injuriesField investigationFinal reportPiper PA-28-181 · Jenks, OKAlthough it was determined that the engine failed due to fuel exhaustion, the exact sequence of events that led to this event was not determined. The pilot reported that the aircraft was out of fuel over the radio and no fuel was found in the aircraft. There…NTSB FTW85LA255Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Tahlequah, OKThe plt stated the acft was in flt slightly more than three hrs after it was refueled, before fuel exhaustion occurred. The acft reportedly was leaned during the flt. Post accident examination revealed no evidence of any fuel system leaks. Reason for the fuel…NTSB FTW85LA133Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Bartlesville, OKAfter one uneventful full-stop landing the plt re-entered the pattern for a second landing. The plt truned to final at about 500 ft AGL and 65-70 KTS with the rwy lights in sight. Shortly thereafter, according to the plt, the landing light illuminated two…NTSB FTW82FPJ18Accident · Serious injuriesFinal reportPiper 28-181 · Oklahoma City, OKThe pilot had difficulty locating the airport at his destination. He touched down at a point more than halfway down the 3000 foot runway and realizing he would be unable to stop the aircraft, attempted a go-around. The main landing gear struck a roadside…NTSB FTW81FPJ36Accident · No injuriesClosedPiper PA-28 · Blanchard, OK