No fatalities

Student Pilot Loses Directional Control on Landing, Strikes Runway Sign

Salem, OR, United States

On October 2, 2010, a CESSNA 172N N operated by Graham Aviation Services was involved in an aviation accident near Salem, OR. No fatalities were reported. Investigators recorded the probable cause as: The pilot's failure to maintain directional control during the landing roll. This summary draws on records from NTSB; 12 related events involving the same aircraft type or operator are linked below.

SourcesNTSBPrimary reportUpdated 2026-08-03Data APIEditorial standards

A student pilot lost directional control after landing, exiting the runway and striking a sign. The pilot, uninjured, reported brakes functional but unused due to cartwheel concern. Post-accident exam found no anomalies.

Incident Overview

A student pilot conducted solo takeoffs and landings at the airplane's base airport. The initial takeoff was on runway 34, followed by a right-hand traffic pattern. On final approach, the flap setting was increased to 30 degrees. After main gear touchdown, the airplane began drifting left. The pilot applied rudder input but reported no effect both before and after nose gear touchdown. Although the brakes were functional, the pilot chose not to use them due to concern that braking could cause the airplane to cartwheel. The airplane continued left, exiting the runway about 2,000 feet beyond the landing threshold, and struck a runway sign.

Pilot and Weather Information

The pilot reported winds from 350 degrees at 3 knots at the time of the accident. An automated weather observation taken approximately 18 minutes after the accident indicated winds from 340 degrees at 6 knots. The pilot stated that the preflight inspection, takeoff, and traffic pattern were normal, and no reason to suspect an airplane malfunction was noted.

Inspection and Findings

Post-accident examination of the airplane revealed no pre-accident mechanical anomalies. A Federal Aviation Administration inspector confirmed that the rudder, nose wheel steering, and brake systems appeared functional. The pilot reported a total of 44 hours of flight experience, with approximately 17 hours in the accident make and model, and one hour logged as pilot-in-command.

Outcome

The pilot was uninjured, but the airplane sustained substantial damage.

Contributing factors

Causes

Student pilotDirectional control — Not attained/maintained

Other contributing factors

Sign/marker

Frequently asked questions

What happened in the 2 Oct 2010 CESSNA 172N N accident near Salem, OR?

A student pilot lost directional control after landing, exiting the runway and striking a sign. The pilot, uninjured, reported brakes functional but unused due to cartwheel concern. Post-accident exam found no anomalies.

Were there any fatalities in the 2 Oct 2010 CESSNA 172N N accident?

No fatalities were recorded in this accident.

What aircraft was involved and where did it happen?

The accident on 2 Oct 2010 involved a CESSNA 172N N, operated by Graham Aviation Services, at Salem, OR.

What was the probable cause of the accident?

The pilot's failure to maintain directional control during the landing roll.