NTSB investigations: Piper PA-32-300
23 cases on aircraft the registry lists as Piper PA-32-300, where the first occurrence was “In flight collision with object”. 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 | 4 |
| 1984 | 1 |
| 1986 | 1 |
| 1987 | 2 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 1995 | 3 |
| 2000 | 3 |
| 2002 | 1 |
| 2003 | 1 |
| 2004 | 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 ('7103212')
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\" = 220))
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_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220))
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 NYC04CA205Accident · No injuriesData collectionFinal reportPiper PA32-300 · Montauk, NYThe pilot's failure to maintain altitude\clearance while landing. A factor in this accident was the gusty wind conditions.NTSB IAD03FA070Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Factoryville, PAThe pilot's improper in-flight decision to descend below the published minimum descent altitude while executing a non-precision approach in instrument meteorological conditions, which resulted in collision with trees. A factor was the fog.NTSB ANC02FA010Accident · 1 fatalField investigationFinal reportPiper PA-32 · Haines, AKThe pilot's continued VFR flight into instrument meteorological conditions, and subsequent collision with trees while in cruise flight. Factors in the accident were weather conditions consisting of freezing rain, mist, and low ceilings.NTSB NYC00FA247Accident · 4 fatalField investigationFinal reportPiper PA-32-300 · Apple Creek, OHThe pilot's premature liftoff and failure to attain a proper climb rate. Factors related to the accident were the over-gross weight conditions, and the low cloud ceilings.NTSB NYC00LA242Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Nantucket, MAThe pilot's failure to maintain the proper glide path to the runway. Factors related to the accident were the fog conditions and the pilot’s fatigue.NTSB SEA00LA162Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Birkenfeld, ORThe pilot's delayed go-around, which resulted in the aircraft not clearing the fence posts. A contributing factor was the fence posts.NTSB ATL96LA024Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Monroe, NCThe pilot's inadequate planning and failure to follow operating procedures resulted in his descent below the decision height while on final approach.NTSB MIA96LA026Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Fort Lauderdale, FLThe pilots failure to follow the visual approach slope indicator and maintain a proper glidepath during approach. Contributing to the accident was pilot fatigue.NTSB LAX96FA050Accident · 3 fatalField investigationFinal reportPiper PA-32-300 · Fullerton, CAthe pilot-in-command's failure to follow IFR procedures in that he descended below the minimum descent altitude and failed to execute a missed approach. Contributing to the accident was the pilot-in-command's self-induced pressure to get to work.NTSB FTW94LA100Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Albuquerque, NMThe CFI rated second pilot's failure to maintain the ILS glideslope. A factor was the dark night and lack of supervision.NTSB BFO93FA082Accident · 1 fatalField investigationFinal reportPiper PA-32-300 · Lyburn, WVFailure of the pilot to attain sufficient altitude to remain clear of rising terrain and objects. Factors related to the accident were darkness and rising terrain.NTSB MIA90LA160Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Plymouth, FLThe pilots decision to depart for his destination airport in the path of approaching thunderstorms resulting in the encounter with wind gusts during landing which exceeded his limitations.NTSB NYC90FA011Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Glastonbury, CTThe pilot-in-command's failure to maintain adequate altitude control during maneuvering flight. Contributing to the accident was the failure of the airplane's electrical system and the pilot's operation at night, without emergency lighting (flashlight).NTSB CHI88FA090Accident · 2 fatalField investigationFinal reportPiper PA-32-300 · Quincy, ILDescent below the dh by the pilot in command during an instrument approach into known adverse weather rather then proceeding to a suitable alternate destination.NTSB NYC88LA043Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-300 · Montoursville, PAAfter takeoff, the plt remained in the traffic pattern to practice takeoffs & landings. He made a touch-&-go, then rprtd on a right downwind for another landing. He acknowledged a clearance to continue, but moments later, an ELT signal began transmitting.…NTSB BFO88LA018Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Churchton, MDThe plt rprtd that after searching unsuccessfully for a wind sock & getting no reply on UNICOM freq, he made an apch to rwy 16. Later, he saw the wind sock about half way down the rwy near a building. Drg the apch, he noticed he was high & put the acft in a…NTSB SEA87LA040Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-300 · Gates, ORThe plt was attempting to land the aircraft at night on an unlit grass airstrip. Prior to reaching the airstrip the plt collided with an apple tree. Both wings were severed from the aircraft and it went inverted before striking the ground in a slightly nose…NTSB ANC84LA076Accident · No injuriesLimited investigationFinal reportPiper PA-32 · Nunavachak, AKThe plt of a Piper PA-32, N4143W, was taking off toward the west-northwest on a tidal beach at the same time that another plt was taxiing west onto the beach. The other plt was taxiing a high wing, Bellanca 7GCBC, N2677Z. The Bellanca was angling down onto…NTSB LAX83FA260Accident · 2 fatalField investigationFinal reportPiper PA-32 300C · Buckeye, AZThe acft collided with a utility pole about 36 ft AGL less than a mile north of a private dirt airstrip. The acft had departed scottsdale municipal arpt at about 0045. The accident occurred at about 0200 aproximately 4 miles west of Buckeye,AZ. A witness…NTSB LAX83FA185Accident · 6 fatalField investigationFinal reportPiper PA32-300 · Weaverville, CAThe acft was being flown to a uni-directional arpt with an instructor plt (CFI) in the right front seat & a student plt/prospective buyer in the left front seat. The rwy elevation was 2230 ft MSL at the south end & 2350 ft at the north end. North of the rwy,…NTSB LAX83LA165Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Gorman, CAEncountering clouds enroute the plt descended to fly through the teton pass. After confirming a VFR check point, he commenced a climb. Shortly thereafter the acft struck a powerline.NTSB ANC83LA055Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Pedro Bay, AKThe acft collided with trees during an attempted go-around after an aborted landing on a frozen lake. The pilot landed toward the village and found the braking action on the snow covered ice was non existent. A go-around was attempted but not enough altitude…NTSB ANC82DA080Accident · No injuriesFinal reportPiper PA-32 · Near Dillingham, AKThe pilot began taking off down slope in calm wind conditions with six passengers on board. Reportedly, the 1380 ft runway was mostly dry, but was muddy in places, except the last 100 ft contained standing water. The aircraft had barely lifted off prior to…