# NTSB SEA96LA127: Piper PA-34-200T, N67SA, Aurora, OR, June 14, 1996

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: June 14, 1996, 10:45 local (17:45 UTC)
- Place: Aurora, OR
- Coordinates: 45.230575, -122.800056 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=45.2306&lon=-122.8001&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 6 uninjured
- Status: Completed, report February 28, 1997
- Report: Approved by Office Director
- NTSB case key (mKey): 42398
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA96LA127
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/42398/pdf
- Page: https://openairdocs.org/ntsb/SEA96LA127

## Probable cause

inadvertent retraction of the landing gear by the pilot during landing.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Gear collapsed, landing
  - gear retraction - inadvertent, pilot in command (cause)

## Analysis

Immediately after touchdown, the right main and nose landing gear collapsed.  The airplane slid down the runway, causing substantial damage, and then the left landing gear collapsed.  No evidence was found by investigators of a mechanical malfunction.

## Factual narrative

On June 14, 1996, approximately 1045 Pacific daylight time, N67SA, a Piper PA-34-200T, sustained substantial damage when the landing gear collapsed after landing at Aurora Sate Airport, Aurora, Oregon.  The private pilot and his five passengers were uninjured.  Visual meteorological conditions prevailed at the time of the accident.  No flight plan was filed for the flight, which had originated at Bend, Oregon, about 0945.  There was no report of the ELT actuating.

The pilot stated that immediately after touchdown the right main and nose gear collapsed.  The aircraft slid down the runway and exited the runway to the right. The left landing gear collapsed and the aircraft stopped forward motion.

No evidence of a mechanical malfunction was found by investigators.

## Aircraft

- Registration: [N67SA](https://openairdocs.org/deregistered/N67SA-2002-12-20), registration cancelled 2002-12-20, S/N 34-7970358, built 1980 (OpenAirDocs)
- Reported make and model: Piper PA-34-200T
- Registry model: [Piper PA-34-200T](https://openairdocs.org/model/piper-pa-34-200t) (registry code 7103406) (OpenAirDocs)
- Registry engine: [Continental GTSI0-520-F-K](https://openairdocs.org/engine/continental-gtsi0-520-f-k) (registry code 17031, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 34-7970358
- Airframe hours: 2446
- Engines: Continental TSIO-360-EB 200 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Horizon Industries
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, January 31, 1996, 50 hours before
- Departed: S07, BEND, OR
- Destination: 3S2
- Airport: 3S2, Aurora, runway 17, 5,000 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 39; private; airplane ratings: multi-engine land, single-engine land; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 289 total, 21 in this make and model, 231 as pilot in command, 7 in the last 90 days, 6 in the last 30 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: calm
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 70 °F

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19960614038479A](https://openairdocs.org/incident/19960614038479A), Jun 14, 1996: Piper PA34200T, Aurora, OR, Substantial damage. Narrative: on June 14, 1996 at 1045 PDT, N67SA, PA-24-200T sustained minor damage when the right main and nose gear collapsed immediately after touchdown. No…

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

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