- Date
- September 25, 1998, 17:25 local (21:25 UTC)
- Place
- Reidsville, NC
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Approach
- Aircraft
- N152DDCessna 152
- Weather
- Visual (VMC) · Day
- Status
- Completed · report November 17, 1999
- Report
- Approved by Office Director
- FAA report
- 19980925033649A
- Case key
- 44093
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 NTSB’s determination of the probable cause, and any contributing factors.
The pilot's delay in the initiation of a go-around, and his failure to maintain obstacle (tree) clearance.
Analysis
The pilot circled the airport twice, and then he entered the traffic pattern for a landing. He realized that he was landing long so he aborted the landing and initiated a go around. During the go around, the aircraft's tail section struck the top of a tree, 300 yards from the edge of the runway. According to an FAA inspector, the pilot was attempting to land at an unfamiliar grass strip.
Factual narrative
On September 25, 1998, about 1725 eastern daylight time, a Cessna 152, N152DD, registered to a private owner, crashed near Reidsville, North Carolina, while on a Title 14 CFR Part 91 personal flight. Visual meteorological conditions were reported and no flight plan was filed. The airplane was substantially damaged. The private-rated pilot reported no injuries. The flight had originated from Burlington, North Carolina, about 1615.
The pilot stated he flew to Warfield, circled two times and then entered the pattern for a landing. The pilot then stated he, "...made a long approach to the landing field but as soon as I realized that the paved surface was not long enough and buildings and an aircraft were at the end of the runway and having not touched down yet, I attempted to abort the landing and make a go around." After clearing the aircraft, buildings, and power lines, the pilot stated "...the aircraft tail section struck the top of a tree which threw me into the tree and suddenly the flight was terminated."
The FAA inspector reported that the pilot was "attempting to land at an unfamiliar grass strip." He made two passes over the field and on the third approach he "overshot" the runway. Just before touchdown the pilot realized he was "too far down the runway for a safe landing." The pilot attempted a go around, applied power to the engine, and climbed over trees at the edge of the runway. According to the FAA inspector, "...the 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."
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.
Aircraft
- Registration
- N152DD
- Reported as
- Cessna 152
- Category
- Airplane
- Serial number
- 15284870
- Engine
- Lycoming O-235-L2C, 110 horsepower, reciprocating
- Damage
- Substantial damage
- Fire
- Unknown
- Flight
- Personal · Part 91
- Operator
- Garland Forbes
- Registered owner
- H&H Propeller Service
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · September 1, 1998 · 7 hours before
- Departed
- BUY · Burlington, NC
- Destination
- 6A5 · NC
- Airport
- 6A5 · Warfield, runway 35, 2,550 × 150 ft, concrete
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
- 62
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 218 total · 108 in this make and model · 173 as pilot in command · 6 in the last 90 days · 1 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- Calm
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 81 °F, dew point 64 °F
- Altimeter
- 30.00 inHg
- Observed at
- GSO, 20 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.