- Date
- June 15, 1996, 16:30 local (23:30 UTC)
- Place
- Hillsboro, OR
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N6554PPiper PA-24-250
- Weather
- Visual (VMC) · Day
- Status
- Completed · report February 28, 1997
- Report
- Approved by Office Director
- FAA report
- 19960615014199A
- Case key
- 42396
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
Probable cause
the pilot's inadequate compensation for wind conditions, and his failure to attain a proper touchdown point for landing. A factor relating to the accident was: upsloping terrain short of the threshold.
Sequence of events
NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.
Analysis
The pilot reported that during an approach to land, he initiated his flare over a river. He reported the aircraft 'encountered a severe downdraft' and that 'elevator back pressure failed to stop (the) rapid descent.' The accompanying flight instructor reported the pilot's approach angle 'was a little bit high' and that he observed the pilot 'slamming back on the control wheel just before touchdown.' The aircraft's right main landing gear impacted rapidly upsloping terrain just short of the runway threshold; both main gear collapsed shortly thereafter. The aircraft then skidded down the runway approximately 750 feet on the nose wheel and collapsed main gear.
Factual narrative
On June 15, 1996, approximately 1630 hours Pacific daylight time, a Piper PA-24-250, N6554P, registered to and being flown by a private pilot, accompanied by a flight instructor, was substantially damaged during an undershoot and subsequent main landing gear collapse while landing at the Stark's Twin Oaks airstrip, Hillsboro, Oregon. Both occupants were uninjured. Visual meteorological conditions existed at the time and no flight plan was in effect. The flight, which was instructional (a biannual flight review), was to have been operated under 14CFR91, and originated from the McMinnville airport, McMinnville, Oregon, shortly before the accident.
The pilot reported that he "started (his) flare over (the) river, encountered (a) severe downdraft" and that "elevator back pressure failed to stop (the) rapid descent." The aircraft's right main landing gear impacted rapidly upsloping terrain just short of the threshold of runway 02. Both main gear then collapsed and the aircraft skidded down the runway approximately 750 feet on the nose wheel and collapsed main gear.
The flight instructor was interviewed by an FAA inspector and reported that during the approach "the approach angle was little bit high" and that he observed the pilot "slamming back on the control wheel just before touchdown and during the flare."
Aircraft
- Registration
- N6554P
- Reported as
- Piper PA-24-250
- Category
- Airplane
- Serial number
- 24-1676
- Airframe hours
- 2,606
- Engine
- Lycoming O-540-A1C5, 250 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Registered owner
- Honeycutt, George, F.
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · June 22, 1995 · 2 hours before
- Departed
- MMV · Mcminnville, OR
- Destination
- 7S3
- Airport
- 4S3 · Stark'S Twin Oaks Airpark, runway 2, 2,465 × 25 ft, asphalt
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 53
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 325 total · 195 in this make and model · 236 as pilot in command
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 290° at 13 knots
- Visibility
- 50 statute miles
- Lowest ceiling
- None
- Temperature
- 70 °F, dew point 48 °F
- Altimeter
- 30.00 inHg
- Observed at
- HIO, 6 nm away
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.