NTSB investigations: Piper PA-28-140
9 cases on aircraft the registry lists as Piper PA-28-140, where NTSB found Descent/approach/glide path. 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
| 2008 | 1 |
|---|---|
| 2009 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2015 | 1 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 1 |
Where
Latest 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102802')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f.\"findingCode\", '01062040')))
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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102802')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_findings.parquet' f WHERE f.case_mkey = x.case_mkey AND f.aircrafts_position = x.position AND starts_with(f."findingCode", '01062040')))
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 ERA18LA096Accident · Serious injuriesLimited investigationFinal reportPiper PA 28 · Edgewater, FLThe flight instructor's failure to maintain the appropriate glidepath to the runway, which resulted in a collision with trees and terrain during final approach.NTSB GAA17CA322Accident · No injuriesData collectionFinal reportPiper PA28 · Gilbert, SCThe pilot's improper glidepath in variable wind conditions, which resulted in the airplane impacting terrain short of the runway threshold.NTSB CEN17FA139Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Stonewall, TXThe pilot's failure to attain a proper touchdown point following a loss of engine power and his inability to stop the airplane on the short, soft runway. Contributing to the accident was the inadequate maintenance of the airplane by the owner and the mechanic…NTSB CEN16LA097Accident · No injuriesLimited investigationFinal reportPiper PA 28-140 · Sturtevant, WIThe pilot's failure to maintain a proper glidepath during a landing at dusk, which resulted in impact with a moving ground vehicle. Contributing to the accident was the inoperative precision approach path indicator.NTSB GAA16CA077Accident · No injuriesData collectionFinal reportPiper PA 28 · California, MDThe student pilot's descent below the prescribed final approach path at night, and flight instructor's failure to correct the student pilot's descent, which resulted in a collision with trees and impact with the ground.NTSB WPR13CA273Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Coolin, IDThe pilot’s failure to maintain an adequate glide path, which led to a runway excursion and collision with objects.NTSB WPR12LA087Accident · No injuriesLimited investigationFinal reportPiper PA-28-140 · Chehalis, WAThe pilot did not correctly manage his glide profile during a simulated engine-out forced landing. Contributing to the accident was the pilot's decision not to add additional engine power, which resulted in a runway undershoot.NTSB CEN09CA453Accident · No injuriesData collectionFinal reportPiper PA28 · Malvern, ARThe pilot's failure to maintain adequate airspeed during the approach to landing.NTSB ERA09FA116Accident · 1 fatalField investigationFinal reportPiper PA-28-140 · Pittstown, NJThe pilot's failure to maintain an adequate clearance from trees during the night landing approach and the flight instructor's inadequate remedial action.