NTSB investigations: Piper PA-24
5 cases on aircraft the registry lists as Piper PA-24, where the first occurrence was “Overrun”. 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
| 1983 | 1 |
|---|---|
| 1985 | 1 |
| 1993 | 1 |
| 1998 | 2 |
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 ('7102402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 340))
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 ('7102402')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 340))
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 MIA98LA247Accident · No injuriesLimited investigationFinal reportPiper PA-24 · Centre, ALThe failure of the pilot to attain the proper touchdown point and his delay in initiating a go-around during a high and fast approach. A factor was the ditch.NTSB NYC98LA126Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Taunton, MAa delayed decision by the pilot to abort the takeoff, which resulted in an overrun. A factor was false reading from the airspeed indicator.NTSB CHI93LA122Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-180 · Lyons, WIThe pilot's use of an unsuitable runway.NTSB NYC85LA246Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Bayport, NYAccording to the CFI, the student raised the nose of the acft too early during takeoff. This resulted in the acft becoming airborne prematurely. The student was unable to climb out of ground effect and the decision to abort the takeoff was made. The acft…NTSB CHI83LA188Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Platteville, WIDuring arrival, the plt entered the traffic pattern to land on rwy 27 in x-wind conditions. The rwy was 2200 ft long & was wet from light rain. After making 2 go-arounds, a landing was made on the 3rd apch. The plt reported that the braking was poor to nil.…