# NTSB investigations: Piper PA-32-301: In flight encounter with weather

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 FTW03FA016](https://openairdocs.org/ntsb/FTW03FA016.md): Piper PA-32-301 · Paron, AR · Accident · 6 fatal · Field investigation · Final report · Oct 20, 2002 · N4353Y · Destroyed
  > The pilot's failure to maintain altitude/clearance from terrain. Contributing factors were the low ceiling, the pilot's decision to fly in known adverse weather conditions, and his lack of an instrument rating.
- [NTSB ANC96LA027](https://openairdocs.org/ntsb/ANC96LA027.md): Piper PA-32-301 · Nome, AK · Accident · Minor injuries · Limited investigation · Final report · Mar 2, 1996 · N8374T · Substantial damage
  > the pilot's continued VFR flight into instrument meteorological conditions and his failure to maintain adequate altitude/clearance from terrain. Low ceilings and snow covered terrain were factors in the accident.
- [NTSB MIA96FA048](https://openairdocs.org/ntsb/MIA96FA048.md): Piper PA-32-301 · Memphis, TN · Accident · 2 fatal · Field investigation · Final report · Dec 19, 1995 · N8349Z · Destroyed
  > the pilot's continued flight into known forecast icing conditions which resulted in the aircraft developing an ice buildup, and the pilot's failure to maintain control of the aircraft. The icing conditions was a factor.
- [NTSB ANC95FA090](https://openairdocs.org/ntsb/ANC95FA090.md): Piper PA-32-301 · Kodiak, AK · Accident · 4 fatal · Field investigation · Final report · Jul 1, 1995 · N8385G · Destroyed
  > The pilot's attempt to fly VFR into IMC conditions and his failure to maintain clearance from terrain. Factors include fog and low ceilings.
- [NTSB MKC90LA040](https://openairdocs.org/ntsb/MKC90LA040.md): Piper PA-32-301 · Norfolk, NE · Accident · No injuries · Limited investigation · Final report · Dec 29, 1989 · N8157R · Substantial damage
  > Inproper in-flight planning/decision by the pilot and his delay in diverting to an alternate airport, which resulted in fuel exhaustion due to an inadequate supply of fuel. Factors related to the accident were: the adverse weather conditions, the pilot's lack…
- [NTSB SEA89FA143](https://openairdocs.org/ntsb/SEA89FA143.md): Piper PA-32-301 · Haines, AK · Accident · 2 fatal · Field investigation · Final report · Jul 30, 1989 · N8257V · Destroyed
  > Improper in-flight planning and decision by the pilot, which resulted in inadvertent flight into instrument meteorological conditions (IMC). The weather conditions and terrain were related factors.
- [NTSB ANC88LA032](https://openairdocs.org/ntsb/ANC88LA032.md): Piper PA-32-300 · Kipnuk, AK · Accident · No injuries · Limited investigation · Final report · Feb 23, 1988 · N8429N · Substantial damage
  > The pilot stated that during the initial climbout from the airport he encountered a complete whiteout condition. The pilot then elected to land on the frozen lake and during the rollout the aircraft struck a snowbank.
- [NTSB CHI87FA057](https://openairdocs.org/ntsb/CHI87FA057.md): Piper PA-32-301 · Wheeling, IL · Accident · No injuries · Field investigation · Final report · Dec 29, 1986 · N8281Y · Substantial damage
  > The pilot attempted flight although pirep's for icing had been issued during weather briefing from fss and aircraft was not equipped for icing conditions. Shortly after takeoff, pilot reported to ATC problems with aircraft flight instruments and then reported…
- [NTSB NYC85LA128](https://openairdocs.org/ntsb/NYC85LA128.md): Piper PA-32R-301 · Ellington, CT · Accident · No injuries · Limited investigation · Final report · May 19, 1985 · N300UM · Substantial damage
  > The acft colldied with a stump during a landing attempt at Ellington arpt. The acft had touched dwn about 25 ft short of the rwy. The left aileron was damaged but the acft made a go-around & returned to westover air base & landed. According to the plt,…

## 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 ('7103207')
    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
```

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

---
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.