19980925033649A

Accident · Substantial damage

FAA accident report · Cessna 152 · Reidville, NC · September 25, 1998

Date
September 25, 1998 · 17:25 local
Place
Reidville, NC
Airport
Warf Airport
Phase of flight
Go Round (Aborted VFR)
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N152DD
NTSB investigation
NTSBMIA98LA256
Reported as
Cessna 152
Reported engine
Lycoming O235L2C
People aboard
1
Fatal injuries
0
Pilot’s flight hours
208 total108 in this make and model6 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

Pilot attempted to land CE-152-152 at an unfamiliar gras strip, after 2 passes around airport. Pilot overshot appraoch end of runway. Pilot realized before touching down he was too FAR down runway for a safe landing. Pilot attempted a go around, powered the aircraft and climbed over trees located at edge of runway. Pilot stalled the aircraft due to high angle of attack and full flaps. Aircraft came in contact with tree 300 yards from edge of runway. No injuries to pilot were reported. (.4) the pilot stated he circled two times and then entered the pattern for a landing, made a long approach to landing but realized that the paved surface was not long enough. During his approach he noticed buildings and an aircraft on landing roll at the other end of the runway. He attempted to abort the landing and go around. During the go around the aircraft's tail section struck the top of a tree. According to the FAA inspector, the pilot was attempting to land at an unfamiliar grass strip. On the third approach he `overshot' the runway. The pilot noticed his position on the approach and decided he was too FAR down the runway for a safe landing. The FAA inspector reported the pilot `stalled' the aircraft because he was in a `...high angle of attack with full flaps and this caused aircraft to come in contact with a tree 300 yards from edge of runway.'

As the FAA filed it

PILOT ATTEMPTED TO LAND CE-152-152 AT AN UNFAMILIAR GRAS STRIP, AFTER 2 PASSES AROUND AIRPORT. PILOT OVERSHOT APPRAOCH END OF RUNWAY. PILOT REALIZED BEFORE TOUCHING DOWN HE WAS TOO FAR DOWN RUNWAY FOR A SAFE LANDING. PILOT ATTEMPTED A GO AROUND, POWERED THE AIRCRAFT AND CLIMBED OVER TREES LOCATED AT EDGE OF RUNWAY. PILOT STALLED THE AIRCRAFT DUE TO HIGH ANGLE OF ATTACK AND FULL FLAPS. AIRCRAFT CAME IN CONTACT WITH TREE 300 YARDS FROM EDGE OF RUNWAY. NO INJURIES TO PILOT WERE REPORTED. (.4) THE PILOT STATED HE CIRCLED TWO TIMES AND THEN ENTERED THE PATTERN FOR A LANDING, MADE A LONG APPROACH TO LANDING BUT REALIZED THAT THE PAVED SURFACE WAS NOT LONG ENOUGH. DURING HIS APPROACH HE NOTICED BUILDINGS AND AN AIRCRAFT ON LANDING ROLL AT THE OTHER END OF THE RUNWAY. HE ATTEMPTED TO ABORT THE LANDING AND GO AROUND. DURING THE GO AROUND THE AIRCRAFT'S TAIL SECTION STRUCK THE TOP OF A TREE. ACCORDING TO THE FAA INSPECTOR, THE PILOT WAS ATTEMPTING TO LAND AT AN UNFAMILIAR GRASS STRIP. ON THE THIRD APPROACH HE `OVERSHOT' THE RUNWAY. THE PILOT NOTICED HIS POSITION ON THE APPROACH AND DECIDED HE WAS TOO FAR DOWN THE RUNWAY FOR A SAFE LANDING. THE FAA INSPECTOR REPORTED THE PILOT `STALLED' THE AIRCRAFT BECAUSE HE WAS IN A `...HIGH ANGLE OF ATTACK WITH FULL FLAPS AND THIS CAUSED AIRCRAFT TO COME IN CONTACT WITH A TREE 300 YARDS FROM EDGE OF RUNWAY.'

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.