OpenAirDocs.org

NTSB investigations: Piper PA-28R-180

13 cases on aircraft the registry lists as Piper PA-28R-180, where the first occurrence was “In flight collision with terrain/water”. 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

19822026

Where

Open the map

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 c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102809')
      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\" = 230))
  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 MIA06LA015Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Opa-Locka, FLThe failure of the pilot-in-command/CFI to maintain control of the airplane and his inattentiveness to the altitude while troubleshooting the landing gear system resulting in the in-flight collision with terrain.Nov 6, 2005 · N4652J · Substantial damageNTSB IAD02FA024Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Milford, CTThe pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.Dec 30, 2001 · N7427J · Substantial damageNTSB IAD01FA053Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Afton, VAThe pilot's loss of consciousness due to a medical condition, which resulted in his failure to maintain control of the airplane and subsequent impact with rising terrain.Apr 30, 2001 · N7680J · DestroyedNTSB CHI01FA043Accident · 4 fatalField investigationFinal reportPiper PA-28R-180 · Danville, ILThe pilot's failure to maintain altitude/clearance during the instrument approach. Factors were the low ceilings, the pilot's failure to maintain proper alignment and glidepath during the approach, his lack of recent instrument experience, and his failure to…Nov 27, 2000 · N4541J · DestroyedNTSB IAD97LA120Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-180 · Danbury, CTThe pilot's improper planning/decision to not use actual occupant weights and compute takeoff data, which resulted in an overweight takeoff towards rising terrain.Sep 18, 1997 · N3102R · DestroyedNTSB LAX95LA060Accident · 1 fatalLimited investigationFinal reportPiper PA-28R-180 · Searchlight, NVthe pilot's intentional continued flight into instrument meteorological conditions in mountainous terrain.Dec 24, 1994 · N3836T · DestroyedNTSB LAX95FA044Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Groveland, CAthe failure of the pilot to maintain adequate terrain clearance during a nighttime descent into the airport over an unlighted mountainous area. Contributing to the accident was the pilot's distraction by attempting to make several cellular telephone calls…Dec 6, 1994 · N4510J · DestroyedNTSB LAX94FA125Accident · 1 fatalField investigationFinal reportPiper PA-28R-180 · Lake Tahoe, CAThe pilot's impairment of judgment and performance due to drugs, which led to his failure to follow the recommended departure procedure, and his failure to maintain sufficient altitude/clearance from rising mountainous terrain. Factors related to the accident…Feb 13, 1994 · N3775T · DestroyedNTSB SEA91FA026Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Salt Lake City, UTThe pilot's intentional buzzing of uninhabited island in the great Salt lake and his misjudging the timing of a pull-up maneuver to clear rising terrain of a ridgeline.Nov 30, 1990 · N4678J · DestroyedNTSB LAX90LA014Accident · No injuriesLimited investigationFinal reportPiper PA-28R-180 · Bishop, CAThe pilot's neglect in failure to ensure adequate clearance was available to pass the parked refueling vehicle. The refueling vehicle parking position on an active taxiway was a factor in the accident.Oct 28, 1989 · N7594J · Substantial damageNTSB CHI84FA073Accident · 2 fatalField investigationFinal reportPiper PA-28R-180 · Traverse City, MIPrior to the flt, the plt made a phone call to a relative who lived near the southeast side of long lake & said he would 'pass over in about 10 min.' After he took off, the acft was observed in a low pass over the southeast corner of the lake. The acft then…Jan 1, 1984 · N3776T · DestroyedNTSB CHI83LA190Accident · No injuriesLimited investigationFinal reportPiper PA-28R · Havana, ILThe aircraft collided with the ground during an attempted go around when the pilot stated that he did not see but two ofthe landing gear lights on. The approach was to runway 9 in a crosswind from 170 degrees at 18 KTS with gusts to 24 KTS the pilot described…Apr 26, 1983 · N7670J · DestroyedNTSB LAX82FUQ10Accident · Serious injuriesFinal reportPiper PA-28R-180 · Captinteria, CAThe pilot reported that he had some head congestion and had experienced ear discomfort on the first leg of the flight. He elected to fly the second leg of the flight in a canyon that he thought would allow passage through the mountains at low altitude.…Mar 8, 1982 · N7497J · Destroyed