- Date
- August 21, 1993, 12:25 local (16:25 UTC)
- Place
- London, OH
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N5653GCessna 172
- Weather
- Visual (VMC) · Day
- Status
- Completed · report June 30, 1994
- Report
- Approved by Office Director
- FAA report
- 19930821052759A
- Case key
- 38640
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 student pilot's failure to maintain directional control of the airplane after landing, and subsequent departure from the runway and collision with terrain.
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 student pilot had conducted three successful landings, and on the fourth landing and touchdown, he partially applied the right brake. The airplane veered to the right, but the pilot managed to straighten the airplane on the runway. He applied partial power to the engine and back pressure to the yoke. The airplane became airborne again and floated to the right. When the airplane touched down again it impacted a dirt embankment and the nose wheel strut broke off.
Factual narrative
On Saturday, August 21, 1993, at about 1225 eastern daylight time, a Cessna 172, N5653G, piloted by Mr. Eric Sounders, collided with the terrain during the landing roll at the Madison County Airport, London, Ohio. The airplane was substantially damaged. The pilot was not injured. Visual meteorological conditions prevailed at the time, and no flight plan had been filed. The flight was being conducted under 14 CFR 91.
According to the pilot's statement on the NTSB Form 6120.1/2:
...[I] had completed [3] touch-n-goes...I turned for final approach for runway 8. Winds were light and variable 6-8 knots at 040 degrees. Approached with 10 degrees flaps...throttle was decreased to idle once runway was made. Once contact with ground had began the aircraft did bump but...did not porpoise...I possibly applied right brake more than left...and a left to right wind gust I began to veer off runway to the right...once off the runway I was unable to control plane...
FAA Inspector, William Mazurek said:
...on the fourth landing, evidence indicates that the right brake was partially applied when he touched down, causing the aircraft to veer to the right...he managed to straighten the path of the aircraft somewhat. He either applied some power or had never completely gone to idle upon touchdown...he increased back pressure to lessen any potential damage to the nose wheel. The increased back pressure, partial power and terrain elevation that decreased caused the aircraft to become airborne again and float to the right. Upon touchdown and out of control, the pilot rolled through a swale and into a dirt embankment...broke off the nose wheel strut...slid one hundred feet in soft dirt... before coming to rest...
The student pilot had a total of 42 flight hours at the time of the accident.
Aircraft
- Registration
- N5653G
- Reported as
- Cessna 172
- Category
- Airplane
- Serial number
- 17271910
- Airframe hours
- 1,407
- Engine
- Lycoming O-320-H2AD, 160 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- Eric Richmond
- Registered owner
- Eric Richmond
- Airworthiness certificate
- Standard, Normal
- Last inspection
- Annual · August 20, 1993 · 3 hours before
- Departed
- 2I4 · Columbus, OH
- Destination
- UYF
- Airport
- UYF · Madison County, runway 8, 4,200 × 75 ft, asphalt
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 26
- Certificate
- Student
- Medical
- Class 3, Valid Medical--w/ waivers/lim
- Seat
- Left
- Flight hours
- 42 total · 42 in this make and model · 9 in the last 30 days
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 40° at 6 knots, gusting 8
- Visibility
- 7 statute miles
- Lowest ceiling
- None
- Temperature
- 73 °F, dew point 63 °F
- Altimeter
- 30.00 inHg
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.