Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

January 26, 2002 · Beech F33A · N3276R

Lynchburg, VA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
January 26, 2002
Injury Outcomes
No injuries (2 uninjured)
Location
Lynchburg, VA
Aircraft
Beech F33A
Tail Number
N3276R
Injuries
None
Aircraft Damage
Substantial
NTSB Number
NYC02LA054

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."

NTSB Probable Cause

The pilot's failure to maintain directional control and delay in aborting the takeoff.

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.

Flight

Event TypeAccident
Event Time09:40 EST
Nearest AirportLynchburg (0nm)
Runway28
Runway Length2900 ft
Runway Width50 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftBeech F33A
Tail NumberN3276R
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsContinental · IO-520 · Reciprocating · 285
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 81 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind160° @ 5 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point37 C / 25 C
Altimeter30.31 inHg
Observation Time09:45
Weather SourceWFAC

Appendix: Source Data