- Date
- October 2, 2010, 15:38 local (22:38 UTC)
- Place
- Salem, OR
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N545DSCessna 172N
- Defining event
- Landing-landing roll: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report December 20, 2010
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- FAA/FSDO
- FAA report
- 20101002047409A
- Case key
- 77536
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 pilot's failure to maintain directional control during the landing roll.
Findings · 4
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, he planned to practice solo takeoffs and landings at the airplane's base airport. He reported that he made the initial takeoff on runway 34, and completed a right-hand circuit of the traffic pattern. On final approach, he increased the flap setting to 30 degrees. After main gear touchdown, the airplane began to drift to the left. The pilot reported that he attempted to correct the drift with rudder input, but there was "no effect," prior and subsequent to nose gear touchdown. The pilot determined that the brakes were functional, but he chose not to use them to assist with directional control, due to his concern about causing "the airplane to cartwheel." About 2,000 feet beyond the landing threshold, the airplane exited the left side of the runway, and struck a runway sign. The pilot was uninjured, but the airplane was substantially damaged. The pilot also reported that at the time of the accident, the winds were from 350 degrees at 3 knots. The automated weather observation taken about 18 minutes after the accident included winds from 340 degrees at 6 knots. The pilot stated that the preflight inspection, takeoff, and traffic pattern were normal, and he had no reason to believe the airplane malfunctioned. Post-accident examination of the airplane did not reveal any pre-accident mechanical anomalies, and a Federal Aviation Administration inspector stated that the rudder, nose wheel steering, and brake systems appeared to be functional. The pilot reported 44 total hours of flight experience in all aircraft. Approximately 17 hours had been accumulated in the make and model airplane involved in the accident. One hour was logged as pilot-in-command.
Factual narrative
According to the student pilot, he planned to practice solo takeoffs and landings at the airplane's base airport. He reported that he made the initial takeoff on runway 34, and completed a right-hand circuit of the traffic pattern. On final approach, he increased the flap setting to 30 degrees. After main gear touchdown, the airplane began to drift to the left. The pilot reported that he attempted to correct the drift with rudder input, but there was "no effect," prior and subsequent to nose gear touchdown. The pilot determined that the brakes were functional, but he chose not to use them to assist with directional control, due to his concern about causing "the airplane to cartwheel." About 2,000 feet beyond the landing threshold, the airplane exited the left side of the runway, and struck a runway sign. The pilot was uninjured, but the airplane was substantially damaged. The pilot also reported that at the time of the accident, the winds were from 350 degrees at 3 knots. The automated weather observation taken about 18 minutes after the accident included winds from 340 degrees at 6 knots. The pilot stated that the preflight inspection, takeoff, and traffic pattern were normal, and he had no reason to believe the airplane malfunctioned. Post-accident examination of the airplane did not reveal any pre-accident mechanical anomalies, and a Federal Aviation Administration inspector stated that the rudder, nose wheel steering, and brake systems appeared to be functional. The pilot reported 44 total hours of flight experience in all aircraft. Approximately 17 hours had been accumulated in the make and model airplane involved in the accident. One hour was logged as pilot-in-command.
Aircraft
- Registration
- N545DS
- Reported as
- Cessna 172N (N)
- Category
- Airplane
- Serial number
- 17373867
- Airframe hours
- 4,449
- Engine
- Lycoming O-320, 160 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Instructional · Part 91
- Operator
- Graham Aviation Services
- Registered owner
- Graham Aviation Services
- Airworthiness certificate
- Standard, Normal
- Last inspection
- 100 hour · July 24, 2010 · 60 hours before
- Departed
- SLE · Salem, OR
- Destination
- SLE · Salem, OR
- Flight plan
- Unknown
- Airport
- SLE · McNary Field, runway 34, 5,145 × 100 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
- Student pilot
- Age
- 33
- Injuries
- None
- Certificate
- Student
- Medical
- Class 3, With waivers/limitations
- Seat
- Left
- Flight hours
- 44 total · 17 in this make and model · 3 as pilot in command · 18 in the last 90 days · 7 in the last 30 days · 0 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 340° at 6 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 70 °F, dew point 48 °F
- Altimeter
- 29.95 inHg
- Observed at
- SLE
Docket · 6
The files NTSB released with the investigation on December 17, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 842 KB 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.