NTSB investigations: Piper PA-32-300
43 cases on aircraft the registry lists as Piper PA-32-300, where the sequence of events included Collision with terr/obj (non-CFIT). 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
| 2008 | 2 |
|---|---|
| 2009 | 1 |
| 2010 | 1 |
| 2011 | 1 |
| 2012 | 4 |
| 2013 | 1 |
| 2014 | 3 |
| 2015 | 3 |
| 2016 | 3 |
| 2017 | 2 |
| 2018 | 9 |
| 2019 | 1 |
| 2020 | 2 |
| 2021 | 1 |
| 2022 | 4 |
| 2023 | 2 |
| 2024 | 2 |
| 2026 | 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.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103212')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s.\"tier2Number\" = '470' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE \"isDefiningEvent\")))
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 ('7103212')
AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '470' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
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 ERA26LA296Accident · Serious injuriesClass 3 · LimitedInvestigation openPiper PA32 · Dawsonville, GANTSB ERA24LA211Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32 · Apopka, FLA partial loss of engine power due to sticking exhaust valves. Contributing to the accident was maintenance personnel’s failure to use available engine data while troubleshooting a known engine issue and maintenance personnel’s failure to comply with…NTSB ERA24LA081Accident · No injuriesClass 4 · LimitedFinal reportPiper PA32 · Gordonville, PAThe pilot’s improper fuel management resulting in fuel starvation, a total loss of engine power, and subsequent off-airport forced landing.NTSB ERA24FA026Accident · 2 fatalClass 3 · FieldFinal reportPiper PA-32-300 · Marion, OHA descent and impact with terrain for undetermined reasons.NTSB CEN23LA415Accident · No injuriesClass 4 · LimitedFinal reportPiper PA-32-300 · Moberly, MOThe flight instructor’s inadequate fuel management that resulted in fuel starvation and a total loss of engine power during an approach for landing.NTSB CEN23LA012Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Paola, KSThe pilot’s improper positioning of the fuel selector, which resulted in fuel starvation and a loss of engine power during a departure climb.NTSB ERA22FA418Accident · 1 fatalClass 3 · FieldFinal reportPiper PA32 · Afton, VAA catastrophic engine failure due to oil starvation, which resulted in a total loss of engine power at night over mountainous terrain.NTSB WPR22LA204Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Snohomish, WAThe total loss of engine power during takeoff due to fuel starvation and the pilot’s improper fuel tank selection and inadequate preflight inspection.NTSB ERA22LA202Accident · No injuriesClass 4 · LimitedFinal reportPiper PA32 · Fountain Inn, SCThe pilot’s failure to obtain the proper touchdown point during landing, which resulted in a runway overrun and collision with a fence.NTSB WPR21LA326Accident · No injuriesClass 3 · LimitedFinal reportPiper PA-32-300 · Del Mar, CAThe partial loss of engine power for reasons that could not be determined, which resulted in a forced landing on an interstate highway and subsequent collision with vehicles.NTSB ANC20CA040Accident · No injuriesData collectionFinal reportPiper PA32 · Fairbanks, AKThe pilot's inadequate compensation for gusting crosswind conditions, which resulted in a loss of directional control, a runway excursion, and impact with a snowbank.NTSB CEN20CA074Accident · No injuriesData collectionFinal reportPiper PA32 · Kingfisher, OKThe pilot's improper continuation of a landing in which he landed too far down the runway at too high a speed, which resulted in a loss of directional control and a runway excursion.NTSB WPR19FA256Accident · 1 fatalClass 3 · FieldFinal reportPiper PA32 · La Grande, ORThe pilot’s decision to continue visual flight rules flight into instrument meteorological conditions, which resulted in spatial disorientation and a loss of control.NTSB ERA18LA265Accident · Minor injuriesLimited investigationFinal reportPiper PA32 · Bartow, FLA total loss of engine power after the separation of the No. 3 cylinder from the crankcase due to improper maintenance.NTSB CEN18LA378Accident · Serious injuriesLimited investigationFinal reportPiper PA32 · Hereford, TXThe pilot’s exceedance of the airplane’s critical angle of attack during takeoff, which resulted in an aerodynamic stall.NTSB CEN18LA377Accident · Serious injuriesLimited investigationFinal reportPiper PA32 · Roanoke, TXThe total loss of engine power for reasons that could not be determined based on the available evidence.NTSB WPR18LA203Accident · Serious injuriesClass 3 · LimitedFinal reportPiper PA32 · Avalon, CAThe pilot's delayed decision to conduct a go-around following an unstable landing approach and long landing.NTSB WPR18LA194Accident · No injuriesClass 3 · LimitedFinal reportPiper PA32 · Salisbury, NCA total loss of engine power due to fuel starvation for reasons that could not be determined based on the available information.NTSB GAA18CA368Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Columbia, SCThe pilot's failure to maintain directional control during landing.NTSB ERA18FA138Accident · 1 fatalField investigationFinal reportPiper PA32 · West Milford, NJAn in-flight fire and total loss of engine power after takeoff due to a loose fuel line. Contributing to the accident was the installation of an unapproved fuel line by unknown personnel.NTSB ERA18LA102Accident · No injuriesClass 3 · LimitedFinal reportPiper PA 32-300 · Pompano Beach, FLThe pilot’s exceedance of the airplane’s critical angle of attack during an aborted landing, which resulted in an aerodynamic stall, loss of control, and impact with terrain. Contributing to the accident was the pilot’s failure to maintain a proper approach…NTSB WPR18LA070Accident · No injuriesLimited investigationFinal reportPiper PA 32-300 · Reno, NVA total loss of engine power due to fuel starvation. Contributing to the accident was the failure of the pilot/owner to ensure that the airplane was airworthy before flight.NTSB WPR18LA051Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA 32-300 · Hinesville, GAA total loss of engine power due to the failure of a connecting rod.NTSB ERA18FA016Accident · 2 fatalField investigationFinal reportPiper PA 32 · Morrison, TNThe pilots' loss of control during a missed approach in night instrument meteorological conditions as a result of spatial disorientation.NTSB ERA17LA034Accident · No injuriesLimited investigationFinal reportPiper PA32 · Bartow, FLA total loss of engine power during approach for reasons that could not be determined because engine examinations did not reveal any evidence of mechanical malfunctions or failures that would have precluded normal operation.NTSB GAA16CA314Accident · No injuriesData collectionFinal reportPiper PA 32 · Lincoln Park, NJThe airplane struck a deer during the landing flare resulting in substantial damage.NTSB ERA16FA169Accident · 1 fatalField investigationFinal reportPiper PA32 · Boone, NCThe pilot's delayed decision to conduct a go-around following an unstabilized landing approach and his subsequent failure to maintain clearance from trees near the end of the runway.NTSB ERA16LA071Accident · Minor injuriesLimited investigationFinal reportPiper PA-32 · Brunswick, GAMaintenance personnel's failure to properly torque a No. 4 cylinder hold-down nut during engine overhaul, which resulted in the loosening of the nut and the subsequent failure of the studs and through bolts and separation of the cylinder.NTSB GAA15CA190Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Greensboro, NCThe pilot's decision to continue the approach after realizing the intended parameters were not attainable, resulting in a runway over-shoot, a loss of control on the ground and the consequent collision with trees.NTSB CEN15FA305Accident · 2 fatalField investigationFinal reportPiper PA 32-300 · Brazoria, TXThe student pilot's failure to arrest the descent in a timely manner and the flight instructor's failure to safely intervene in the routine training maneuver for reasons that could not be determined based on the information available.NTSB CEN14FA434Accident · 1 fatalField investigationFinal reportPiper PA 32-300 · Ardmore, OKThe partial loss of engine power for reasons that could not be determined because thermal damage to the engine prevented a complete examination.NTSB ERA14LA369Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Helena, ALA total loss of engine power for reasons that could not be determined due to postcrash fire damage.NTSB CEN14CA422Accident · No injuriesData collectionFinal reportPiper PA 32-300 · Warsaw, INThe pilot failed to maintain directional control during landing.NTSB ERA13LA148Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Sanford, NCThe installation of an incorrect length of cotter pin on the throttle linkage clevis pin by maintenance personnel at an undetermined time, which resulted in the pin coming loose and the loss of throttle control.NTSB ERA13CA079Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Easton, MDThe pilot's failure to maintain directional control while landing.NTSB WPR13LA045Accident · 1 fatalLimited investigationFinal reportPiper PA-32 · ObyanA partial loss of engine power shortly after takeoff for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation and the pilot’s failure to maintain airplane control during…NTSB ERA13FA055Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Jackson, MSThe pilot's inadequate preflight inspection, which resulted in his failure to note the water in the fuel tank due to condensation, which subsequently shut down the engine in flight. Contributing to the accident was the pilot's self-induced pressure to…NTSB ANC12LA058Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gustavus, AKThe fatigue failure of the engine crankshaft for reasons that could not be determined during postaccident metallurgical examination.NTSB ERA11CA365Accident · Serious injuriesData collectionFinal reportPiper PA-32-300 · Bridgeport, CTThe pilot's failure to maintain clearance from a blast fence on final approach to land.NTSB ERA10WA116Accident · 3 fatalForeign investigationPiper PA-32-300 · Bimini, Bahamas, BahamasOn January 17, 2010, at approximately 1545 eastern standard time, a Piper PA-32-300, N4219R, crashed approximately 500 yards northwest of the Bimini Bay Resort, North Bimini, Bahamas. The flight departed Lynden Pindling International Airport, Nassau, Bahamas…NTSB ANC09LA030Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Nunapitchuk, AKThe pilot's failure to maintain sufficient airspeed to avoid a stall during the landing approach.NTSB DEN08LA082Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Houston, TXLoss of engine power for reasons undetermined. Contributing to the accident was a lack of suitable terrain for a forced landing.NTSB MIA08CA039Accident · No injuriesData collectionFinal reportPiper PA-32-300 · Lapine, ALThe pilot's failure to attain the proper touchdown point.