NYC96LA095

NTSB accident investigation · Piper PA-28-R200 · Forks Township, PA · May 1, 1996

Accident · Serious injuriesLimited investigationFinal report
Date
May 1, 1996, 13:30 local (17:30 UTC)
Place
Forks Township, PA
Injuries
2 serious
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N5030SPiper PA-28-R200
Weather
Visual (VMC) · Day
Status
Completed · report November 25, 1996
Report
Approved by Office Director
FAA report
19960501009139A
Case key
39172

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 flight instructor's misjudgment of distance and altitude, and delay in performing remedial action.

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.

UndershootApproach - vfr pattern - base leg/base to final
Emergency procedure - simulatedPilot in command(cfi)
Distance/altitude - misjudgedPilot in command(cfi)Cause
Remedial action - delayedPilot in command(cfi)Cause
In flight collision with objectApproach - vfr pattern - base leg/base to final
Object - utility pole

Analysis

The certified flight instructor (CFI) and the private pilot, her husband, had flown a previous flight that day and practiced maneuvers at altitude. After a refueling stop, they departed for another training flight. The private pilot performed two practice power off landings from the downwind to runway 18. During a third practice forced landing, with the landing gear extended, the CFI took over the controls. When the airplane developed a high sink rate during the turn to final, the CFI realized that the airplane was low and slow. The CFI stated that she advanced the throttle, but the engine did not respond. The airplane's right wing struck a 25-foot-high pole at the edge of an open field, about 12 feet above the ground and 900 feet from the approach end on the runway. The private pilot stated that during the approach he thought that they were getting 'too slow and too low,' and when full power was applied the engine response 'sounded strange.' Examination of the wreckage revealed no preimpact failure of the airframe or engine.

Factual narrative

On May 1, 1996, at 1330 eastern daylight time, a Piper PA-28-R200, N5030S, was substantially damaged during a simulated forced landing to the Easton Airport, Forks Township, Pennsylvania. The flight instructor and private pilot received serious injuries. Visual meteorological conditions prevailed for the local training flight that departed Easton, about 1300. No flight plan had been filed for the flight conducted under 14 CFR Part 91.

In the NTSB Form 6120.1/2, the certified flight instructor (CFI) stated that she and the private pilot, her husband, had flown a previous flight that day and practiced maneuvers at altitude. The airplane was then landed, refueled, and they departed for another training flight. During the second training flight the private pilot performed two practice power off landings from the down wind. The CFI further stated:

"...He started this maneuver on a very wide down wind to 18. The third time, I took the airplane, kept it in closer to the runway and pulled the power back. On the turn to final, the airplane suddenly developed a fast sink rate. I gave immediate full throttle (gear was down, checklist for landing complete.) There was a slight sputter of the engine...Full throttle and nothing happened. Sink rate not arrested. Saw the pole and tried not to hit it with fuselage..."

A Federal Aviation Administration (FAA) Inspector interviewed the CFI and private pilot the day after the accident. In the FAA Inspector's summary of the interview, the CFI stated that during the turn to final, she realized that she was low and slow and advanced the throttle to full power and that the engine response "did not seem right." The private pilot stated that during the approach he thought that they were getting "too slow and too low," and when full power was applied the engine response "sounded strange."

Several witnesses observed the airplane flying low before impact. One witness stated:

"...I saw a plane through the trees which appeared to be flying at an extremely low altitude in relation to the airport. As I came into the clearing I noticed my suspicion was correct. The plane was dangerously low and I clearly witnessed the plane's right wing smash into the telephone pole..."

The airplane's right wing struck a 25 foot high pole, about 12 feet above the ground, 900 feet from the approach end of the runway.

Examination of the wreckage by FAA Inspectors revealed no pre-impact failure of the airframe or engine. One FAA Inspector's report stated:

"...The propeller was damaged by impact and showed leading edge damage and rotation marks on the forward face of the propeller blades...No malfunction of the engine was evident or could be duplicated..."

Aircraft

Registration
N5030S
Reported as
Piper PA-28-R200
Category
Airplane
Serial number
28R20035776
Airframe hours
3,627
Engine
Lycoming IO-360-C1C, 200 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Dorothy & James Regan
Airworthiness certificate
Standard, Normal
Last inspection
Annual · March 15, 1996 · 6 hours before
Departed
N43
Airport
N43 · Easton, runway 18, 1,953 × 50 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
64
Certificates
Commercial, Flight instructor
Airplane ratings
Single-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--w/ waivers/lim
Seat
Right
Flight hours
1,282 total · 956 in this make and model · 1,066 as pilot in command · 8 in the last 90 days · 8 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
190° at 10 knots
Visibility
10 statute miles
Lowest ceiling
None
Temperature
63 °F, dew point 37 °F
Altimeter
29.00 inHg
Observed at
ABE, 11 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.

Other investigations on N5030S · 1

Matched to the same aircraft by N-number and date.