- Date
- July 31, 2010, 11:12 local (15:12 UTC)
- Place
- Elk Creek, VA
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N172FLCessna 172N
- Defining event
- Landing-landing roll: Collision during takeoff/land
- Weather
- Instrument (IMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Eastern Region Aviation
- Parties
- FAA/FSDO
- FAA report
- 20100731039899A
- Case key
- 76819
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 continued visual flight into instrument meteorological conditions, which resulted in an off-airport landing.
Findings · 2
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
Analysis
According to the student pilot/owner, when he initially checked the weather 2 hours before takeoff, his intended route of flight was “cloudy,” but reporting visual meteorological conditions. After the student pilot and his passenger arrived at the airport, the student pilot checked the weather again and decided to fly southeast before proceeding direct to the destination through better weather conditions. After the student pilot took off, he requested flight following and informed an air traffic controller of his intended route of flight. The controller advised the student pilot of possible rain en route, and recommended that he modify his route of flight to proceed direct to his destination. The student pilot accepted the controller’s advice and found the first 45 minutes of flight to be “fine,” but the weather worsened. The student pilot flew into clouds "briefly" twice, but maneuvered the airplane back into visual conditions. He then asked air traffic control for advice, but all the suggestions “yielded no relief.” Shortly thereafter, the student pilot declared an emergency and decided to make an emergency landing to a field. The student pilot “dropped the plane down on the mains as firmly as possible, and [it] bounced and went airborne again.” The airplane traveled down the field, hit the top of a fence and continued up a hill, where it finally came to rest. The airplane incurred substantial damage to the forward section of the fuselage and the right wing root. The pilot did not report any mechanical anomalies with the airplane. The weather reported at an airport about 15 miles east, about the time of the accident, included broken clouds at 500 feet; broken clouds at 900 feet; overcast clouds at 1,400 feet; and light rain. The student pilot reported 170 hours of total flight time.
Factual narrative
According to the student pilot/owner, when he initially checked the weather 2 hours before takeoff, his intended route of flight was “cloudy,” but reporting visual meteorological conditions. After the student pilot and his passenger arrived at the airport, the student pilot checked the weather again and decided to fly southeast before proceeding direct to the destination through better weather conditions. After the student pilot took off, he requested flight following and informed an air traffic controller of his intended route of flight. The controller advised the student pilot of possible rain en route, and recommended that he modify his route of flight to proceed direct to his destination. The student pilot accepted the controller’s advice and found the first 45 minutes of flight to be “fine,” but the weather worsened. The student pilot flew into clouds "briefly" twice, but maneuvered the airplane back into visual conditions. He then asked air traffic control for advice, but all the suggestions “yielded no relief.” Shortly thereafter, the student pilot declared an emergency and decided to make an emergency landing to a field. The student pilot “dropped the plane down on the mains as firmly as possible, and [it] bounced and went airborne again.” The airplane traveled down the field, hit the top of a fence and continued up a hill where it finally came to rest. The airplane incurred substantial damage to the forward section of the fuselage and the right wing root. The pilot did not report any mechanical anomalies with the airplane. The weather reported at an airport about 15 miles east, about the time of the accident, included broken clouds at 500 feet; broken clouds at 900 feet; overcast clouds at 1,400 feet; and light rain. The student pilot reported 170 hours of total flight time.
Aircraft
- Registration
- N172FL
- Reported as
- Cessna 172N
- Category
- Airplane
- Serial number
- 17269187
- Engine
- Lycoming O-320 SERIES, 180 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Departed
- BCB · Blacksburg, VA
- Destination
- VPC · Cartersville, GA
- Airport
- NONE · None
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
- Student pilot
- Age
- 37
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3, Without waivers/limitations
- Seat
- Left
- Flight hours
- 170 total · 160 in this make and model · 7 in the last 90 days · 7 in the last 30 days · 4 in the last 24 hours
Weather
- Conditions
- Instrument (IMC) · Day
- Wind
- 150° at 7 knots
- Visibility
- 3 statute miles
- Lowest ceiling
- 500 ft broken
- Temperature
- 64 °F, dew point 64 °F
- Altimeter
- 30.05 inHg
- Observed at
- HLX, 15 nm away
Docket · 6
The files NTSB released with the investigation on September 5, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 4.4 MB in all.
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 N172FL · 1
Matched to the same aircraft by N-number and date.