NTSB investigations: Piper PA-32-260
34 cases on aircraft the registry lists as Piper PA-32-260, where the first occurrence was “Loss of engine power”. 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 |
|---|---|
| 1983 | 3 |
| 1984 | 1 |
| 1986 | 2 |
| 1989 | 1 |
| 1990 | 1 |
| 1991 | 1 |
| 1992 | 3 |
| 1994 | 1 |
| 1995 | 2 |
| 1996 | 4 |
| 1997 | 2 |
| 1999 | 2 |
| 2000 | 1 |
| 2001 | 1 |
| 2002 | 2 |
| 2003 | 1 |
| 2004 | 2 |
| 2006 | 2 |
| 2007 | 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 ('7103206')
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\" = 350))
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 ('7103206')
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" = 350))
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 MIA08LA029Accident · Minor injuriesLimited investigationFinal reportPiper PA32-260 · Marathon, FLA loss of engine power for undetermined reasons.NTSB MIA06FA092Accident · Serious injuriesField investigationFinal reportPiper PA-32-260 · Dunnellon, FLThe loss of engine power as a result of fuel starvation due to a contaminated carburetor fuel inlet screen.NTSB CHI06LA072Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Jackson, MIthe blocked induction air filter due to ice accumulation which resulted in a loss of engine power. The pilot's improper weather evaluation, trees, snow, fog, and icing conditions were factors.NTSB ATL04LA175Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Kennesaw, GAThe loss of engine power for undetermined reasons.NTSB ATL04LA117Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · New Bern, NCThe pilot's inadequate pre-flight planning which resulted in a loss of engine power due to fuel exhaustion.NTSB NYC03LA116Accident · Minor injuriesLimited investigationFinal reportPiper PA32-260 · Huntington, WVThe pilot's failure to position the fuel selector to a tank with adequate fuel for the flight, which resulted in a power loss due to fuel starvation and the subsequent forced landing.NTSB ANC02LA095Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Red Devil, AKA partial loss of engine power for an undetermined reason during the initial climb after takeoff that resulted in a collision with trees. A contributing factor in the accident was rising terrain which was unsuitable for a forced landing.NTSB DEN02LA090Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Victor, COthe pilot's failure to refuel, resulting in fuel exhaustion and a subsequent loss of engine power. Contributing factors were the pilot's use of inappropriate medication, and the unsuitable terrain on which to make a forced landing.NTSB LAX02LA022Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Avalon, CAthe total loss of engine power during departure climb for undetermined reasons.NTSB LAX00LA247Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Chester, CAThe loss of engine power for undetermined reasons.NTSB MIA99LA099Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Atlantic Ocean (Atlantic Ocean)a loss of engine power for an undetermined reason, resulting in a forced landing in water, and subsequent sinking of the airplane.NTSB MIA99LA073Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Orlando, FLA loss of engine power due to an engine assembly overload for undetermined reasons. A related factor was the pilot exceeded the airplane's maximum allowable weight.NTSB CHI98LA037Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Lakeville, MNfuel starvation due a deteriorated grommet in an Adel clamp, and a loose mixture control cable.NTSB MIA97LA109Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Atlantic Ocean (Atlantic Ocean)loss of engine power for undetermined reason(s). A factor relating to the accident was: the pilot's poor in-flight planning/decision by flying at too low of an altitude to glide to shore for a forced landing.NTSB IAD97LA027Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Claverack, NYloss of engine power for undetermined reasons.NTSB CHI97LA012Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Mancelona, MIthe worn fuel system pump (actuator arm). A factor was the unsuitable terrain encountered by the pilot.NTSB NYC96LA171Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Coatsville, PAloss of engine power for undetermined reason(s). Factors relating to the accident were: darkness, and the lack of suitable landing areas.NTSB CHI96LA174Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Osage Beach, MOa partial loss of power for undetermined reasons.NTSB MIA95LA158Accident · 1 fatalLimited investigationFinal reportPiper PA-32-260 · Brooksville, FLA loss of engine power after takeoff for undetermined reasons. Contributing to the accident was the lack of suitable terrain for a forced landing.NTSB MIA95LA079Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Caribbean SeaA total loss of engine power for undetermined reasons.NTSB MIA94FA175Accident · 1 fatalField investigationFinal reportPiper PA-32-260 · Gulf Of MexicoLoss of engine power due to an undetermined reason. A factor related to the accident was: inadequate passenger briefing by the pilot.NTSB NYC92LA173Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Newburyport, MAThe loss of engine power for undetermined reasons.NTSB MIA92LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Randleman, NCThe failure of the pilot-in-command to switch the fuel selector to a tank with fuel, after the engine failed due to fuel starvation.NTSB BFO92LA107Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Norwalk, OHLoss of engine power due to undetermined reasons and the lack of suitable terrain for a forced landing.NTSB DEN91LA045Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Guymon, OKFuel starvation for undetermined reasons, and the pilot's delay in flaring the airplane. A factor was: the pilot's total lack of experience.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 ATL87FA012Accident · Serious injuriesField investigationFinal reportPiper PA-32-260 · Lawrenceville, GAAbout 20 min after takeoff, while cruising at 6500', the eng lost power. Rprtdly, the eng went to either idle or a wind-milling cond & the fuel pressure dropped to zero. The plt tried to restart the eng by using emerg procedures, but was unable. He initially…NTSB NYC86LA172Accident · Minor injuriesLimited investigationFinal reportPiper PA-32 · Block Island, RIThe eng lost partial power on the initial climb-out as the plt was taking off from rwy 28. He initiated a left turn back to the arpt, but the eng lost all power. Subsequently, the acft was landed in an area of brush & small trees near the west end of the…NTSB NYC84FNC07Accident · Minor injuriesFinal reportPiper PA-32-260 · Brunswick, METhe acft eng failed without warning at an alt of 2500 ft MSL. During the forced landing at nas Brunswick, the plt executed normal emergency procedures but was not successful in air-starting the acft. He stated that after having the 'abandoned field made' he…NTSB MKC84LA042Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Schuyler, NEWhile descending toward the planned destination, the eng began running rough & the plt attempted to improve the eng's performance by using carburetor heat. He made a localizer-only apch, but was unable to see the rwy at the min descent alt. A missed apch was…NTSB LAX84FA045Accident · 2 fatalField investigationFinal reportPiper PA-32-260 · Riverside, CAShortly after departure the plt radioed in that he had blown a rod 'or something' and was about two miles out on a right base leg. He then informed the tower that he was not going to make the runway after which the left wing contacted a power pole and the…NTSB MIA83LA070Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Culebra, PRThe flight had departed st. thomas, VI at 0900 on a VFR flight plan to roosevelt roads after discharging passengers in st. thomas. While enroute in cruise at 1800 MSL the engine failed. He turned toward the island of Culebra and when all efforts to restart…NTSB NYC83FA037Accident · 3 fatalField investigationFinal reportPiper PA-32-260 · Douglassville, PAAt aprx 1540 EST, the acft was dispatched to philadelphia, PA on a pax flt. After arriving, the plt remained there to pick up 4 other pax that were arriving at approx 2100 EST. At 2007, the plt received a partial wx brief & filed an IFR flt plan to rtn to…