NTSB investigations: Piper PA-24-260
9 cases on aircraft the registry lists as Piper PA-24-260, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1982 | 1 |
|---|---|
| 1986 | 1 |
| 1991 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 2002 | 1 |
| 2004 | 1 |
| 2006 | 2 |
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 ('7102406')
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\" = 130))
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 ('7102406')
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" = 130))
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 CHI07LA056Accident · No injuriesLimited investigationFinal reportPiper PA-24-260B · Belleville, ILThe failure of the torque link bolt which resulted in the right main landing gear strut scissors separating and becoming jammed in the wheel well. Contributing to the accident was the seized torque link bolt due to surface corrosion.NTSB LAX06LA114Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Rancho Murieta, CAan electrical fault in the nose gear limit switch circuit, which lead to an intermittent failure of the landing gear extension system. Also causal was the pilot's failure to fully complete the emergency gear extension procedure. A factor in the accident was…NTSB SEA04LA153Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Redmond, ORUnknown malfunction of the landing gear system for undetermined reasons that resulted in a gear collapse during landing.NTSB CHI02FA292Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Ankeny, IAThe pilot applied an excessive angle of bank and failed to maintain terrain clearance. An additonal factor was the pilot's attention being diverted.NTSB MIA94LA123Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Spring Hill, FLUnsuitable terrain encountered during a forced landing. Contributing to the accident was the fatigue failure of one of the propeller blade's pitch change knob.NTSB DEN93LA074Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Grand Junction, COFailure of the pilot in command to follow manual gear extension procedures. A factor was a total electrical failure.NTSB CHI91LA218Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Flint, MIPropeller pitch change mechanism sheared. Factors related to the accident were powerplant vibration and proper touchdown point not possible.NTSB MIA86LA159Accident · No injuriesLimited investigationFinal reportPiper PA-24-260 · Tallahassee, FLWhile in the traffic pattern the acft's electrical system failed due to internal failure of the alternator. The plt failed to extend the landing gear by the emergency gear extension handle and a gear up landing resulted.NTSB ATL83FA041Accident · 1 fatalField investigationFinal reportPiper PA-24-260 · Culpepper, VAAbout 16 min after takeoff the plt reported to ARTCC that he had lost the artificial horizon, gyro & vacuum pump. Radio & radar contact was lost shortly thereafter. Examination of the vacuum pump failed to reveal a pre-impact failure or malfunction. The acft…