NTSB investigations: Piper PA-23-250, SC
10 cases on aircraft the registry lists as Piper PA-23-250. 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
| 1967 | 1 |
|---|---|
| 1970 | 1 |
| 1973 | 1 |
| 1977 | 1 |
| 1982 | 1 |
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 2003 | 1 |
| 2009 | 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\" = 'SC' 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 ('7102308'))
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" = 'SC' 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 ('7102308'))
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 ERA10FA024Accident · 4 fatalField investigationFinal reportPiper PA-23-250 · Summerville, SCFlight into terrain for undetermined reasons.NTSB ATL04FA016Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Cordesville, SCThe pilot's failure to maintain adequate airspeed, which resulted in an inadvertent stall and subsequent uncontrolled descent into trees and the ground. A factor was physical impairment.NTSB ATL86FA026Accident · 1 fatalField investigationFinal reportPiper PA-23-250 · Chester, SCWitnesses at the accident site estimated the ground visibility to be 100 yds or less. The instrument rated plt on the 32 NM flt had not filed a flt plan even though he had obtained a wx briefing from fss. The acft collided with the steel cables atop steel…NTSB ATL84LA281Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Cheraw, SCAccording to the plt, after 100 to 150 ft of landing roll the right main landing gear collapsed.NTSB ATL84LA035Accident · No injuriesLimited investigationFinal reportPiper PA-23-250 · Greer, SCDuring the flt, hydraulic failure of the landing sys occurred & the aircrew were unable to get the gear locked in the down position. After orbiting for over an hour, a landing was made. During touchdown, the gear collapsed. An exam revealed that an aileron…NTSB ATL83FA067Accident · Minor injuriesField investigationFinal reportPiper PA-23-250 · Johns Isle, SCThe plt stated both engs lost power after takeoff & the acft ditched in the stono river. No preimpact failure and/or malfunction of either eng could be found. The plt did not hold any airman certificate.NTSB MIA77FLG19Accident · No injuriesClosedPiper PA-23 · Charleston, SCNTSB MIA73FLG43Accident · No injuriesClosedPiper PA-23 · Cameron, SCNTSB MIA71FLG03Accident · No injuriesClosedPiper PA-23 · Charleston, SCNTSB MIA68F0220Accident · Minor injuriesClosedPiper PA-23 · Aiken, SC