# NTSB investigations: Piper PA-32R-300: In flight collision with terrain/water

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB LAX04FA102](https://openairdocs.org/ntsb/LAX04FA102.md): Piper PA-32R-300 · Big Pine, CA · Accident · 1 fatal · Field investigation · Final report · Jan 21, 2004 · N8701E · Destroyed
  > failure of the pilot to maintain clearance with mountainous terrain for undetermined reasons.
- [NTSB ANC99FA130](https://openairdocs.org/ntsb/ANC99FA130.md): Piper PA-32R-300 · Bettles, AK · Accident · 1 fatal · Field investigation · Final report · Sep 3, 1999 · N9166K · Destroyed
  > The pilot's continued flight into known adverse weather conditions. Factors in the accident were low ceilings and snow.
- [NTSB NYC97LA073](https://openairdocs.org/ntsb/NYC97LA073.md): Piper PA-32R-300 · Lumberton, NJ · Accident · No injuries · Limited investigation · Final report · Apr 14, 1997 · N29M · Substantial damage
  > The pilot's delay in initiating remedial action to arrest an excessive descent rate during a go-around. A crosswind condition was a contributing factor.
- [NTSB ANC95FA101](https://openairdocs.org/ntsb/ANC95FA101.md): Piper PA-32R-300 · Haines, AK · Accident · 6 fatal · Field investigation · Final report · Jul 7, 1995 · N6281J · Destroyed
  > The pilot's failure to maintain an adequate altitude above and clearance from the surrounding terrain. A factor related to the accident was the pilot's improper decision to conduct the maneuver in such close proximity to the rising terrain.
- [NTSB FTW95FA112](https://openairdocs.org/ntsb/FTW95FA112.md): Piper PA-32R-300 · Conroe, TX · Accident · 5 fatal · Field investigation · Final report · Feb 10, 1995 · N5373F · Destroyed
  > The pilot's failure to follow published IFR procedures. Factors were the weather conditions, the dark night, and the pilot's failure to activate the approach lighting system.
- [NTSB SEA94FA040](https://openairdocs.org/ntsb/SEA94FA040.md): Piper PA-32R-300 · Spokane, WA · Accident · 1 fatal · Field investigation · Final report · Dec 15, 1993 · N999VP · Destroyed
  > The pilot's failure to maintain proper alignment with the instrument landing system approach course. The pilot's failure to perform a missed approach was a factor.
- [NTSB CHI94FA048](https://openairdocs.org/ntsb/CHI94FA048.md): Piper PA-32R-300 · Antigo, WI · Accident · 2 fatal · Field investigation · Final report · Dec 10, 1993 · N550BC · Substantial damage
  > the failure of the pilot in command to maintain proper altitude.
- [NTSB ANC93FA134](https://openairdocs.org/ntsb/ANC93FA134.md): Piper PA-32R-300 · Atigun Pass, AK · Accident · 1 fatal · Field investigation · Final report · Aug 4, 1993 · N477JC · Destroyed
  > The pilot-in-command's intentional VFR flight into instrument meteorological conditions and his unfamiliarity with the geographical area. Factors were the rain and fog.
- [NTSB SEA92LA173](https://openairdocs.org/ntsb/SEA92LA173.md): Piper PA-32R-300 · Farmington, UT · Accident · Minor injuries · Limited investigation · Final report · Aug 4, 1992 · N7091C · Destroyed
  > The pilot's poor inflight decision. Factors include downdrafts and a box canyon.
- [NTSB NYC91LA167](https://openairdocs.org/ntsb/NYC91LA167.md): Piper PA-32R-300 · Rhinebeck, NY · Accident · No injuries · Limited investigation · Final report · Jul 2, 1991 · N5002F · Substantial damage
  > The pilot did not calculated the airplane's performance data to insure that he had enough runway to clear an obstacle at the end of the field, which resulted in the airplane's landing gear striking high hedges, subsequently the pilot elected to land in a…
- [NTSB LAX91FA124](https://openairdocs.org/ntsb/LAX91FA124.md): Piper PA-32R-300 · Palm Springs, CA · Accident · 1 fatal · Field investigation · Final report · Mar 8, 1991 · N711PE · Destroyed
  > Incapacitation of the pilot due to inadequate sleep.
- [NTSB CHI90FA236](https://openairdocs.org/ntsb/CHI90FA236.md): Piper PA-32R-300 · Watertown, WI · Accident · 7 fatal · Field investigation · Final report · Aug 19, 1990 · N4070Q · Destroyed
  > Initiation of VFR flight into adverse weather and instrument meteorologial conditions. Factors which contributed to the accident were the adverse weather conditions and the pilot's self-induced pressure to maintain currency.
- [NTSB NYC87FA188](https://openairdocs.org/ntsb/NYC87FA188.md): Piper PA-32R-300 · Tannersville, NY · Accident · 2 fatal · Field investigation · Final report · Jun 26, 1987 · N7146C · Destroyed
  > While on a VFR air taxi cargo flight, the aircraft collided with trees on the east side of high peak mountain, elevation 3,655 feet. The accident site elevation was 3080 feet. A witness said it was heavy overcast, not raining and the clouds were not below the…
- [NTSB DEN85FA153](https://openairdocs.org/ntsb/DEN85FA153.md): Piper PA-32R-300 · Melstone, MT · Accident · 1 fatal · Field investigation · Final report · Jun 9, 1985 · N75063 · Substantial damage
  > The acft was observed in a left turn in a steep dive until it passed out of view behind a hill. The investigation revealed no evidence of airframe or engine malfunction or failure piror to the crash. Medical findings revealed the plt, sole occupant, had 90…
- [NTSB MIA83IA239](https://openairdocs.org/ntsb/MIA83IA239.md): Piper PA-32R-300 · Orlando, FL · Incident · No injuries · Incident investigation · Final report · Sep 25, 1983 · N301WA · Minor damage
  > Acft made an intentional gear up landing after both normal & emergency procedures failed to lower the gear. It was determined that the hydraulic pump motor had failed. Normal & emergency systems were interdependent. The emergency gear diaphragm was blocked by…
- [NTSB ATL82FLT04](https://openairdocs.org/ntsb/ATL82FLT04.md): Piper PA-32R-300 · Iuka, MS · Accident · 3 fatal · Final report · May 11, 1982 · N444ME · Destroyed
  > The aircraft crashed during a pass across the airport. A witness was parked, facing east, in the runup area for runway 18. According to him, the the aircraft took off about 6 minutes earlier, made a traffic pattern, and crashed behind and to his right. The…

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```sql
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" = 230))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb?model=7103213&occurrence=230

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.