NTSB investigations: Piper PA-32R-300
14 cases on aircraft the registry lists as Piper PA-32R-300, where the first occurrence was “In flight encounter with weather”. 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 |
|---|---|
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1989 | 4 |
| 1993 | 1 |
| 1994 | 2 |
| 1996 | 1 |
| 1997 | 1 |
| 1999 | 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 ('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\" = 240))
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" = 240))
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 NYC99LA073Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Richmond, VAThe pilot's inadequate preflight planning/preparation which resulted in flight into icing weather conditions. A factor related to the accident was restricted visibility through the icy windshield during landing.NTSB MIA97LA145Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Augusta, GAflight by the pilot into known adverse weather conditions, which resulted in a loss of aircraft control during the landing flare, and collision with the terrain. The adverse weather with nearby thunderstorm activity, crosswind, and gusts was a related factor.NTSB MIA96LA066Accident · Minor injuriesLimited investigationFinal reportPiper PA-32R-300 · Smithville, TNThe pilot's improper in-flight planning/decision, which resulted in a heavy load of airframe ice, an inability to maintain altitude, and a subsequent emergency landing. Factors relating to the accident were: the adverse weather (icing) condition, which was…NTSB SEA95FA031Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Grantsville, UTThe VFR pilot's attempt to continue the flight into instrument meteorological conditions, and his failure to maintain altitude/clearance with mountainous terrain.NTSB BFO94FA066Accident · 3 fatalField investigationFinal reportPiper PA-32R-300 · Salem, OHVFR flight by the pilot into instrument meteorological conditions (IMC), his loss of aircraft control due to spatial disorientation, and exceeding the design stress limits of the aircraft. Factors related to the accident were: darkness, the adverse weather…NTSB ATL93FA151Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Laurinburg, NCThe pilot's VFR flight into instrument meteorological conditions (IMC), failure to maintain control of the aircraft after becoming spatially disoriented, and inadvertently exceeding the design stress limits of the aircraft. Factors related to the accident…NTSB NYC90LA032Accident · Serious injuriesLimited investigationFinal reportPiper PA-32R-300 · Johnstown, PAFailure of the pilot to maintain proper airspeed and altitude on an ILS final approach, which allowed the aircraft to descend below the glide path and collide with approach lighting. Factors related to the accident were: darkness, adverse weather conditions,…NTSB LAX89LA313Accident · No injuriesLimited investigationFinal reportPiper PA-32R-300 · Mammoth Lakes, CAThe pilot's improper compensation for the existing wind condition and his failure to maintain airspeed. Factors that related to the accident were: the gusty & cross-winds and high density altitude.NTSB FTW89LA100Accident · No injuriesLimited investigationFinal reportPiper PA-32R · Stratford, TXImproper planning/decision by the pilot, and his inadequate compensation for wind conditions, which resulted in a loss of aircraft control. The wind condition was a related factor.NTSB NYC89FA099Accident · 2 fatalField investigationFinal reportPiper PA-32R-300 · Southbridge, MAPoor judgement of the pilot by flying while physically impaired by alcohol, and his continued VFR flight into instrument meteorological conditions (IMC). Related factors were: the pilot's inadequate preflight planning/preparation, dark night, adverse weather…NTSB SEA88FA031Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Lakeport, CAAlthough weather conditions were marginally VFR at his departure point, and the pilot had access to a vehicle which could have been used to drive to his dest, he departed novato, CA, enroute to Lakeport, CA, without obtaining a wx briefing nor filing a flt…NTSB ATL87FA007Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Nashville, TNThe flight was cleared for the localizer approach to rwy 31. The pilot reported the airport in sight. The flight descended into the cloud layer and crashed about 1000 feet short of the middle marker. The pilot did not report any aircraft problem. The approach…NTSB ATL85FA146Accident · 1 fatalField investigationFinal reportPiper PA-32R-300 · Dundee, MSPlt obtained three preflight wx briefings then filed IFR using an assumed name. Routine communications until 2117 CST when pilot reported in a cell and said he wanted to make a 180 degree turn. Cleared for right turn. Radar and comm contact with aircraft lost…NTSB ATL82FA047Accident · 4 fatalField investigationFinal reportPiper PA-32R-300 · Lambsburg, VAThe aircraft was on an air taxi flight to transport 2 prisoners and was to be operated on a VFR flight plan in VFR conditions only. Prior to takeoff, the pilot had obtained 12 weather briefing. In 2 of the briefings, VFR flight was not recommended. At about…