NTSB investigations: Piper PA-32-260, VA
19 cases on aircraft the registry lists as Piper PA-32-260. 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 |
|---|---|
| 1968 | 1 |
| 1969 | 2 |
| 1974 | 1 |
| 1975 | 1 |
| 1977 | 1 |
| 1978 | 2 |
| 1987 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 1 |
| 1994 | 1 |
| 1995 | 2 |
| 2015 | 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.\"eventStateOrRegion\" = 'VA' 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 ('7103206'))
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" = 'VA' 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 ('7103206'))
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 ERA16LA022Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Bluemont, VAA total loss of engine power as a result of the separation of the No. 5 connecting rod for reasons that could not be determined based on the available information.NTSB NYC95LA130Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Ashland, VAa loss of engine power due to a subsurface fatigue crack in the crankshaft which led to failure of the crankshaft.NTSB NYC95FA068Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Suffolk, VAThe pilot's inadequate preflight and improper in-flight planning/decision, which resulted in fuel exhaustion. Darkness was a factor related to the improper planning/decision-making for the emergency landing.NTSB BFO94FA144Accident · 5 fatalField investigationFinal reportPiper PA-32-260 · Front Royal, VAThe pilot's failure to maintain adequate clearance, his improper in-flight decision and his inadvertent flight into instrument meteorological conditions (IMC) which resulted in in-flight collision with terrain. The high terrain and weather conditions were…NTSB NYC93FA012Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Pulaski, VAThe improper decision by the non-instrument-rated pilot to continue VFR flight into known instrument meteorological conditions resulting in spatial disorientation and loss of control of the airplane. Factors which contributed to the accident were the actions…NTSB BFO91LA032Accident · No injuriesLimited investigationFinal reportPiper PA32-260 · Roanoke, VAThe pilot's failure to maintain terrain clearance on a night visual approach.NTSB BFO90LA030Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Dungannon, VAThe pilot's improper planning/decision, which resulted in fuel starvation and loss of engine power, and failure of the pilot to maintain directional control of the aircraft during the emergency landing. Factors related to the accident were: the adverse…NTSB BFO89FA028Accident · 3 fatalField investigationFinal reportPiper PA-32-260B · Richmond, VAEngine lost power because of induction icing. Contributing factors are conditions conduvice to induction icing and unsuitable terrain.NTSB BFO88FA008Accident · 3 fatalField investigationFinal reportPiper PA-32-260B · Willis, VAThe acft was on a night IFR flight at 7000 ft MSL in IMC when the plt reported the directional gyro was inoperative. The acft was outbound from the pulaski VOR on V45 headed southeast. The plt further reported the turn&bank and the mag compass were operative.…NTSB BFO87LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Roanoke, VARoanoke tower cleared the aircraft for landing and the pilot pulled the power to idle. The pilot did not realize the engine had quit until he applied power on short final and the engine did not respond. The aircraft struck short of runway 33. The pilot stated…NTSB IAD79FA014Accident · No injuriesClosedPiper PA-32 · South Boston, VANTSB IAD78FA081Accident · No injuriesClosedPiper PA-32 · Severn, VANTSB IAD77FIA26Accident · No injuriesClosedPiper PA-32 · Harrisonburg, VANTSB IAD76FID14Accident · Minor injuriesClosedPiper PA-32 · South Boston, VANTSB IAD74AI057Accident · 1 fatalClosedPiper PA-32 · Luray, VANTSB IAD70F0089Accident · No injuriesClosedPiper PA-32 · Norfolk, VANTSB DIA69F0171Accident · No injuriesClosedPiper PA-32 · New Kent, VANTSB DIA68D0197Accident · No injuriesClosedPiper PA-32 · Rural Retreat, VANTSB DIA67D0113Accident · No injuriesClosedPiper PA-32 · Lynchburg, VA