NTSB investigations: Piper PA-32R-300
18 cases on aircraft the registry lists as Piper PA-32R-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
| 1984 | 2 |
|---|---|
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 2 |
| 1991 | 2 |
| 1993 | 2 |
| 1994 | 1 |
| 1995 | 1 |
| 2001 | 1 |
| 2002 | 2 |
| 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 ('7103213')
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 ('7103213')
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 NYC07LA027Accident · 1 fatalLimited investigationFinal reportPiper PA-32R-300 · Williamsburg, VAThe pilot's improper decision to depart into adverse weather conditions. Contributing was the gusty wind conditions.NTSB ATL06FA038Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Camden, ALThe pilots failure to maintain altitude and clearance during a visual descent which resulting in an in-flight collision with trees and the ground for undetermined reasons.NTSB ANC02LA117Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Manley Hot Spgs, AKA bird strike during takeoff, which resulted in substantial damage to the right wing.NTSB MIA02FA067Accident · 1 fatalField investigationFinal reportPiper PA32R-300 · Broadway, NCThe pilot's inadequate visual lookout and his failure to maintain obstacle clearance.NTSB FTW01LA158Accident · 1 fatalLimited investigationFinal reportPiper PA-32R-300 · Belle Chase, LAthe pilot's failure to maintain clearance with a utility pole while maneuvering. Contributing factors were the pilot's impairment due to alcohol intoxication and the night light conditions.NTSB FTW95FA363Accident · Serious injuriesField investigationFinal reportPiper PA-32R-300 · Wichita Falls, TXthe pilot's failure to maintain airspeed while diverting attention to an open cargo door. A factor was the pilot's inadequate preflight inspection.NTSB BFO94LA113Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Seven Springs, PAThe pilot's failure to attain adequate airspeed and his premature liftoff which resulted in a stall mush and collision with trees.NTSB CHI94FA018Accident · 5 fatalField investigationFinal reportPiper PA-32R-300 · Atkinson, NEthe instrument rated commercial pilot's failure to maintain adequate clearance from terrain/obstructions during the initial climb after takeoff. Related factors are the weather conditions (fog) and the pilot's failure to maintain the proper rate of climb.NTSB FTW93LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · El Dorado, ARThe pilot's failure to maintain clearance. A factor was the dark night.NTSB NYC92LA027Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R · Caldwell, NJThe pilot allowed the airplane to get too low on final approach during a night visual landing. Factors in the accident were: the pilot improperly planned the approach, dark night and a lack of flight experience in night operations.NTSB ATL91LA140Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Boone, NCThe pilot's failure to follow the manufacturer's procedures related to takeoff performance. Factors in the accident were: the high density altitude, the high obstructions, and the pilot's lack of expereince with takeoff operations at high density altitude.NTSB LAX90LA108Accident · No injuriesLimited investigationFinal reportPiper PA-32-R-300 · Sacramento, CAAn inadvertent collision with a large bird during the hours of darkness while in the landing pattern.NTSB NYC90FA051Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Great Barrngton, MAFailure of the pilot to maintain proper altitude and clearance from trees while departing from the airport. Factors related to the accident were: the pilot's inadequate preflight planning/preparation, his allowing the aircraft weight and balance to be…NTSB DEN90LA010Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Albuquerque, NMImproper planning/decision by the pilot. Factors related to the accident were: the pilot's lack of familiarity with the aircraft, his failure to use the recommended flap extension, his failure to maintain an airspeed above the automatic gear extension speed…NTSB MIA88FA083Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Pembroke Park, FLThe non-instrument rated private pilot obtained a weather briefing that indicated the weather would be deteriorating to IMC, but he attempted a flight anyway. During the flight, he became disoriented and penetrated 2 control zones and then struck an antenna…NTSB MIA87LA206Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Hastings, FLThe plt stated that he had just lifted from the 2300 ft wet grass strip, where he estimated the grass to be about 6 in to 1 ft high, when he sustained a partial power loss. The acft struck an embankment at the end of the rwy & sheared the gear. Air temp in…NTSB MIA85FA066Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Homestead, FLWhile cruising northerly at a low altitude during a dark night, the acft struck a row of trees appx 50 ft tall about 8 ft from the tops, it then hit a large tree at about 6 ft AGL, 670 ft from the initial impact point, & came to rest in a dirt road. An exam…NTSB CHI84LA094Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Greenville, ILThe plt received a weather briefing the night before the accident and did not have it updated on the day of the accident. The acft was descended below the mda during the approach in fog and collided with high tension lines.