NTSB investigations: Piper PA-24-250
13 cases on aircraft the registry lists as Piper PA-24-250, where the first occurrence was “In flight collision with object”. 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 |
|---|---|
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1995 | 2 |
| 1997 | 1 |
| 1999 | 1 |
| 2000 | 1 |
| 2001 | 1 |
| 2004 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102404')
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\" = 220))
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 ('7102404')
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" = 220))
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 IAD04FA017Accident · 1 fatalField investigationFinal reportPiper PA-24-250 · North Lima, OHThe pilot's failure to maintain a safe altitude clearance from trees. Factors included the night lighting conditions and the pilot's diminished night vision capability.NTSB SEA01LA148Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Thompson Falls, MTThe pilot's inadequate compensation in gusting wind conditions during the landing flare. A tree was a factor.NTSB CHI01LA012Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Manhattan, KSthe inadequate soft field takeoff procedure by the pilot and his failure to abort the takeoff. Factors were the high grass on the runway, the pilots disregard for the runway conditions, his lack of total experience in the aircraft, the trees, and the pilots…NTSB CHI99FA223Accident · 2 fatalField investigationFinal reportPiper PA-24-250 · Fertile, MNthe inadvertent stall. Factors relating to this accident were the instructor pilot maneuvering the airplane at very low altitude and the trees.NTSB CHI98LA029Accident · 1 fatalLimited investigationFinal reportPiper PA-24-250 · Robinson, ILthe pilot's improper decision to continue flight into adverse weather conditions The low ceiling and the heavy rain were factors.NTSB FTW95LA387Accident · No injuriesLimited investigationFinal reportPiper PA-24-180 · Cibolo, TXThe pilot's improper planning/decision and failure to abort the takeoff, while there was sufficient runway remaining.NTSB SEA95LA086Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Anaconda, MTThe pilot's attempt to conduct visual flight into instrument meteorological conditions, and his failure to maintain clearance from terrain.NTSB LAX93LA342Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Hesperia, CAThe aircraft's encounter with a low level windshear and the pilot's inadequate compensation for the existing wind conditions.NTSB MIA92LA163Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Brooksville, FLThe pilot-in-command's failure to maintain alignment with the runway during landing. This resulted in an in-flight collision with a runway marker, collapse of the right main landing gear, and subsequent collision with terrain.NTSB CHI90LA165Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Millington, MIInadequate planning-decision, failure to obtain lift-off airspeed, and failure to perform an aborted takeoff. Factors related to the accident are the uphill sloping runway, soft turf, high grass, and complacency.NTSB MKC89FA156Accident · 3 fatalField investigationFinal reportPiper PA-24-250 · Medicine Lodge, KSThe pilot misjudged clearance above a house (residence) that he was buzzing and allowed the aircraft to collide with the attached antenna.NTSB NYC88LA137Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Blairstown, NJThe flight was on final for runway 7 following another airplane, when the pilot's attention was drawn to a glider maneuvering in the area. He yielded left to maintain a comfortable distance from the glider and failed to observe an antenna tower in his path.…NTSB LAX84LA399Accident · Serious injuriesLimited investigationFinal reportPiper PA-24-250 · Folsom, CAThe acft was observed flying down a river at a low altitude toward the main body of a lake. The acft impacted a 12 kv power line. The plt stated that he did not see the wires until an instant before impact.