NTSB investigations: Piper PA-31-350, 2008

6 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

19742026
NTSB investigations: Piper PA-31-350, 2008 per year, 1974–2026: 302 cases
19741
19755
19764
19773
197810
19797
19805
19819
198211
19839
19845
19858
19867
19877
19883
19899
199011
19919
19924
19936
19947
19959
19968
19979
199811
199911
200010
20017
20028
20033
20049
20055
20064
20078
20086
20093
20105
20117
20123
20133
20142
20156
20161
20172
20182
20193
20203
20214
20221
20234
20242
20252
20261

Latest 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\") = 2008
    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.

NTSB WPR09LA013Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Portland, ORAn in-flight engine fire due to the fatigue fracture of an exhaust pipe that resulted from a failure of the pipe's slip joint.Oct 14, 2008 · N3BT · Substantial damageNTSB WPR09LA014Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Fresno, CAThe pilot misjudged the flare resulting in a hard landing.Sep 29, 2008 · N27996 · Substantial damageNTSB LAX08FA286Accident · 1 fatalField investigationFinal reportPiper PA-31-350 · Las Vegas, NVA loss of power in the right engine due to an in-flight fuel-fed fire in the right engine compartment that, while the exact origin could not be determined, was likely related to the right engine-driven fuel pump, its fuel supply line, or fitting. Contributing…Aug 28, 2008 · N212HB · Substantial damageNTSB ANC08LA097Accident · Serious injuriesLimited investigationFinal reportPiper PA-31-350 · Aniak, AKA partial loss of engine power during takeoff due to a failure of the left engine's turbocharger as a result of the failure of a turbine shaft bearing. Contributing to the accident was unsuitable terrain for a forced landing.Aug 4, 2008 · N40YR · Substantial damageNTSB LAX08LA080Accident · No injuriesLimited investigationFinal reportPiper PA-31-350 · Portland, ORThe failure of company maintenance personnel to install the upper pivot bolt through the pivot hole in the upper end of the landing gear actuating rod, and the company maintenance inspector's inadequate inspection of the work performed.Mar 20, 2008 · N4098A · Substantial damageNTSB ANC08MA038Accident · 6 fatalMajor investigationFinal reportPiper PA-31-350 · Kodiak, AKThe failure of company maintenance personnel to ensure that the airplane's nose baggage door latching mechanism was properly configured and maintained, resulting in an inadvertent opening of the nose baggage door in flight. Contributing to the accident were…Jan 5, 2008 · N509FN · Substantial damage