NTSB investigations: Piper PA-31-350
16 cases on aircraft the registry lists as Piper PA-31-350, 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 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1989 | 1 |
| 1990 | 3 |
| 1992 | 1 |
| 1994 | 2 |
| 1995 | 1 |
| 1998 | 1 |
| 2000 | 2 |
| 2004 | 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 ('7103110', '7103125')
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 ('7103110', '7103125')
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 ANC04LA059Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Goodnews, AKThe pilot's inadequate weather evaluation which resulted in an in-flight encounter with severe turbulence, and his exceedence of the design stress limits resulting in overstress of the wings. A factor contributing to the accident was the presence of…NTSB ANC04LA018Accident · Serious injuriesLimited investigationFinal reportPiper PA-31-350 · Koyukuk, AKThe pilot's continued flight into adverse weather conditions, and his failure to maintain clearance from terrain, which resulted in an in-flight collision with terrain. Factors associated with the accident were fog and whiteout weather conditions.NTSB ANC01LA027Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Deadhorse, AKThe pilot's continued VFR flight into instrument meteorological conditions. Factors associated with the accident were clouds, fog, dusk light conditions, and the pilot's self-induced pressure to complete the flight prior to nightfall.NTSB ATL00FA081Accident · 3 fatalField investigationFinal reportPiper PA-31-350 · Lumber City, GAPilot's failure to follow instrument procedures and descended below approach minimums and collided with trees. A factor was low clouds.NTSB ANC99LA014Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Point Lay, AKFailure of the pilot to maintain a proper glidepath. Factors associated with this accident were the airport not having a VASI system installed, and the lack of visual perception for the pilot.NTSB CHI95FA285Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Ardoch, NDthe pilot-in-command's continuing flight into adverse weather. Factors were the pilot-in-command's failure to obtain a weather observation and the adverse weather.NTSB BFO94LA102Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Oxford, CTThe pilot's inadvertent encounter with fog during landing.NTSB ATL94FA076Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Elizabethton, TNThe pilot's attempted VFR flight into IMC conditions, and his failure to maintain a proper altitude over mountainous terrain. Factors were the clouds and obscuration at the accident site.NTSB ANC92LA058Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Kotzebue, AKPilot factor in that the proper glidepath and altitude was not maintained. Factors to the accident were: inattentiveness and snow.NTSB MKC90LA108Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Dubuque, IAWeather evaluation misjudged resulting in uncontrolled descent by the pilot in command and aircraft control not maintained by the pilot in command.NTSB MKC90FA082Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Bois D'Arc, MOInadvertent flight by the pilot into instrument meteorological conditions (IMC), and his spatial disorientation, which resulted in loss of aircraft control. Factors related to the accident were: the pilot's inadequate weather evaluation, darkness, low…NTSB ANC90FA034Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Cold Bay, AKContinued VFR flight by the pilot into instrument meteorological conditions (IMC), and his failure to maintain adequate altitude (or clearance) from mountainous terrain. The adverse weather and terrain conditions were related factors.NTSB DEN89LA224Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Monument Valley, UTThe pilot's failure to adequately compensate for windshear.NTSB ANC85FA041Accident · No injuriesField investigationFinal reportPiper PA-31-350 · Savoonga, AKThe plt reported that during arrival, he overflew the arpt & made a right turn while watching the village. As he maneuvered, he encountered white-out conditions, turned too FAR & subsequently collided with rising terrain. The wx over the general area prior to…NTSB ATL85FA039Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Petros, TNThe flt departed ft. lauderdale, FL, on 8-2-84 at aprx 0815 EDT for cincinnati, OH. The acft wreckage was found on 11-17-84 on an up slope of big fodder stack mountain. The acft had contacted a 25 ft tall tree located 200 ft west of the main wreckage. The…NTSB SEA82DA017Accident · No injuriesFinal reportPiper PA-31-350 · Spokane, WAAfter arriving in the Spokane area, a full ILS was commenced. It was terminated about 200 ft above the decision height with a missed approach. The aircraft was vectored for a second ILS. During the last 400 ft of this approach, about 3/4 to one inch of mixed…