N3276R Beech F33A accident

NTSB NYC02LA054 · 2002-01-26 · Lynchburg, VA · near W24

Docket — crew, injuries and powerplant

Summary

The airplane was taxied to the runway, and the pilot did not observe any abnormalities with the braking or steering system. The taxi route included two separate 90-degree turns and a 180-degree turn. As power was applied for takeoff, the pilot anticipated the tendency for the airplane to turn left by compensating with right rudder; however, "it did not produce the usual corrective action." The pilot then attempted to apply braking action to stop the turn, but the airplane departed the left side of the runway, about 75 feet from the point where the takeoff roll began, while the engine was still developing full power. The pilot aborted the takeoff, and the airplane proceeded into low-lying brush, before coming to rest upright. Examination of the airplane revealed the rudder pedals and brakes operated normally. According to the Federal Aviation Administration Airplane Flying Handbook, "In the event a takeoff is rejected, the power should be reduced to idle and maximum braking applied while maintaining directional control."

Full narrative

On January 26, 2002, about 0940 eastern standard time, a Beech F33A, N3276R, was substantially damaged while taking off from the Falwell Airport, Lynchburg, Virginia. The certificated commercial pilot and passenger were not injured. Visual meteorological conditions prevailed, and no flight plan was filed for the personal flight conducted under 14 CFR Part 91.

According to the pilot, he taxied the airplane from his hangar to runway 10, a 2,000-foot long, 50-foot wide, asphalt runway. The taxi route to the runway required two separate 90-degree turns, and a 180-degree turn onto the runway. The pilot did not observe any abnormalities with the steering system during the taxi. Prior to departure, the pre-takeoff check included assuring that the brakes were released, and the flight controls were operating normally. As power was applied, the pilot "anticipated the tendency for the airplane to turn left." As the airplane gained speed, it began to turn left. The pilot attempted to compensate for the turn with right rudder; however, "it did not produce the usual corrective action." The pilot then attempted to apply braking action to stop the turn, but the airplane departed the left side of the runway, while the engine was still developing full power. The pilot aborted the takeoff, and the airplane proceeded into low-lying brush, before coming to rest upright.

A Federal Aviation Administration (FAA) inspector examined the wreckage after the accident. The inspector verified flight control continuity and observed no abnormalities with the rudder pedals or brakes.

The inspector also observed that the airplane departed the side of the runway about 75 feet from the point where the takeoff roll began.

According to the FAA Airplane Flying Handbook, "In the event a takeoff is rejected, the power should be reduced to idle and maximum braking applied while maintaining directional control."

The recorded weather at a nearby airport, about the time of the accident, included winds from 160 degrees at 5 knots.

Probable cause

The pilot's failure to maintain directional control and delay in aborting the takeoff. The National Transportation Safety Board determined the probable cause of this accident.

Circumstances

Event type
Accident
Highest injury
None
Weather conditions
Visual Meteorological Cond
Light condition
Day
Sky condition
NONE
Ceiling (ft)
0
Visibility (sm)
10
Wind direction
160
Wind speed (kt)
5
Temperature (F)
37
Nearest airport
Lynchburg
Distance from field
0.0
Airport elevation
939

Aircraft

RegistrationMakeModelDamageFAR part
N3276R Beech F33A SUBS 091

Sequence of events

#OccurrencePhase
1 260 Cruise

Findings

Finding
24539 cause
24505 cause