# NTSB investigations: Piper PA-30: In flight collision with object

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 ATL04FA027](https://openairdocs.org/ntsb/ATL04FA027.md): Piper PA-30 · Spartanburg, SC · Accident · 1 fatal · Field investigation · Final report · Oct 27, 2003 · N7799Y · Destroyed
  > The pilot's failure to follow IFR procedures and descent below the glide path, which resulted in an inflight collision with trees during an instrument approach. A factor was the pilot's impairment due to the sedating effects of medication.
- [NTSB CHI02LA219](https://openairdocs.org/ntsb/CHI02LA219.md): Piper PA-30 · Abilene, KS · Accident · No injuries · Limited investigation · Final report · Jul 29, 2002 · N90TC · Substantial damage
  > The pilot failed to achieve clearance over the trees and wires. Factors associated with the accident were the pilot failed to use all available runway, a downwind takeoff was performed, the tailwind, trees, and wires.
- [NTSB CHI01LA221](https://openairdocs.org/ntsb/CHI01LA221.md): Piper PA-30 · Bowman, ND · Accident · No injuries · Limited investigation · Final report · Jul 21, 2001 · N7382Y · Substantial damage
  > Altitude/clearance not obtained by the pilot during the initial climb. Factors relating to the accident were attaining the proper climb rate not being possible, the microburst, the dark night, and the tree.
- [NTSB ATL98LA074](https://openairdocs.org/ntsb/ATL98LA074.md): Piper PA-30 · Hendersonville, NC · Accident · Minor injuries · Limited investigation · Final report · May 8, 1998 · N7312Y · Substantial damage
  > The pilot's failure to attain the proper touchdown point and improper go-around procedures resulting in collision with wires, trees, and the ground. Factors were the pilot's lack of familiarity with the airplane and the short runway.
- [NTSB BFO94LA153](https://openairdocs.org/ntsb/BFO94LA153.md): Piper PA-30 · Wolfeboro, NH · Accident · No injuries · Limited investigation · Final report · Aug 27, 1994 · N8541Y · Substantial damage
  > The pilot's failure to maintain directional control during landing which resulted in inflight collission with trees.
- [NTSB LAX94FA047](https://openairdocs.org/ntsb/LAX94FA047.md): Piper PA-30 · Brea, CA · Accident · 1 fatal · Field investigation · Final report · Nov 15, 1993 · N8238Y · Destroyed
  > The pilot's choice of an inadequate cruise altitude over rolling hill terrain which resulted in an in-flight collision with helium balloons and an in-flight loss of control for undetermined reasons. A factor in the accident was the pilot's inadequate visual…
- [NTSB NYC93LA132](https://openairdocs.org/ntsb/NYC93LA132.md): Piper PA-30 · Mitchellville, MD · Accident · No injuries · Limited investigation · Final report · Jun 27, 1993 · N7563Y · Substantial damage
  > The failure of the pilot to maintain a proper glide path during the final approach, which resulted in the airplane striking a moving vehicle.
- [NTSB DEN93LA037](https://openairdocs.org/ntsb/DEN93LA037.md): Piper PA-30 · Eckert, CO · Accident · Serious injuries · Limited investigation · Final report · Apr 2, 1993 · N8210Y · Substantial damage
  > The pilot-in-command's failure to maintain adequate clearance from the truck during the landing. Factors which contributed to the accident were: the pilot's poor judgement in attempting the operation, and the driver's poor judgement in not vacating all…
- [NTSB MIA90IA072](https://openairdocs.org/ntsb/MIA90IA072.md): Piper PA-30 · Tallahassee, FL · Incident · No injuries · Incident investigation · Final report · Feb 19, 1990 · N7574Y · Minor damage
  > Proper glidepath not maintained.
- [NTSB ATL85LA257](https://openairdocs.org/ntsb/ATL85LA257.md): Piper PA-30 · Portland, TN · Accident · Minor injuries · Limited investigation · Final report · Aug 24, 1985 · N7369Y · Substantial damage
  > The plt made a visual aprch to the wrong airport & attempted to go-around. During the go-around the acft coll ided with trees on the departure end of the rwy.

## 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 ('7103002')
    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" = 220))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

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

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