NTSB investigations: Piper PA-31-350, 1999
11 cases on aircraft the registry lists as Piper PA-31-350. 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
| 1974 | 1 |
|---|---|
| 1975 | 5 |
| 1976 | 4 |
| 1977 | 3 |
| 1978 | 10 |
| 1979 | 7 |
| 1980 | 5 |
| 1981 | 9 |
| 1982 | 11 |
| 1983 | 9 |
| 1984 | 5 |
| 1985 | 8 |
| 1986 | 7 |
| 1987 | 7 |
| 1988 | 3 |
| 1989 | 9 |
| 1990 | 11 |
| 1991 | 9 |
| 1992 | 4 |
| 1993 | 6 |
| 1994 | 7 |
| 1995 | 9 |
| 1996 | 8 |
| 1997 | 9 |
| 1998 | 11 |
| 1999 | 11 |
| 2000 | 10 |
| 2001 | 7 |
| 2002 | 8 |
| 2003 | 3 |
| 2004 | 9 |
| 2005 | 5 |
| 2006 | 4 |
| 2007 | 8 |
| 2008 | 6 |
| 2009 | 3 |
| 2010 | 5 |
| 2011 | 7 |
| 2012 | 3 |
| 2013 | 3 |
| 2014 | 2 |
| 2015 | 6 |
| 2016 | 1 |
| 2017 | 2 |
| 2018 | 2 |
| 2019 | 3 |
| 2020 | 3 |
| 2021 | 4 |
| 2022 | 1 |
| 2023 | 4 |
| 2024 | 2 |
| 2025 | 2 |
| 2026 | 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 year(c.\"eventDate\") = 1999
AND 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'))
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 year(c."eventDate") = 1999
AND 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'))
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 LAX00LA043Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Scottsdale, AZThe pilot's failure to follow the manufacturer's published emergency procedures for engine loss of power resulting in a forced landing in an open construction area where the airplane collided with a berm. A related factor was the loss of engine power in the…NTSB CHI00LA029Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Romulus, MIthe inadvertent wheels-up landing by the pilot.NTSB LAX00FA014Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · North Las Vegas, NVThe failure of the pilot-in-command to maintain separation from terrain while operating under visual flight rules. Contributing factors were the improper issuance of a suggested heading by air traffic control personnel, inadequate flight progress monitoring…NTSB ANC00LA004Accident · No injuriesLimited investigationFinal reportPiper PA-31 · Soldotna, AKAn in-flight collision with a bird.NTSB DCA99MA088Accident · 10 fatalMajor investigationFinal reportPiper PA-31-350 · Volcano, HIthe pilot's decision to continue visual flight into instrument meteorological conditions (IMC) in an area of cloud-covered mountainous terrain. Contributing to the accident were the pilot's failure to properly navigate and his disregard for standard operating…NTSB MIA99FA263Accident · 2 fatalField investigationFinal reportPiper PA-31-350 · Moreland, GAThe pilot's failure to maintain the minimum descent altitude while executing a localizer approach. Contributing factors were low ceilings and dark night conditions as well as the trees.NTSB CHI99LA256Accident · Minor injuriesLimited investigationFinal reportPiper PA-31-350 · Salina, KSthe inadequate preflight inspection by the pilot. Factors to the accident were fuel exhaustion and the operation of the aircraft with known deficiencies in equipment by the pilot.NTSB ANC99FA074Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Tanana, AKUndetermined.NTSB ANC99LA045Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Chevak, AKThe pilot's inadequate in-flight planning/decision, and his failure to attain the proper touchdown point on the runway. Factors in the accident were a tail wind condition, and the presence of snow and ice on the runway surface.NTSB CHI99LA114Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Waterloo, IAthe pilot's failure to maintain directional control.NTSB ANC99LA020Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Anchorage, AKThe failure of the driver of a vehicle to maintain an adequate visual lookout.