# Accident 20020126002449A: Beech F33A, Lynchburg, VA, January 26, 2002

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 26, 2002, 09:40 local time
- Place: Lynchburg, VA
- Airport: Falwell Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 37.3778° N, 79.1222° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=37.3778&lon=-79.1222&mi=10
- Aircraft: N3276R, a cancelled registration (https://openairdocs.org/deregistered/N3276R-2023-07-01) (OpenAirDocs)
- Registry model: Beech F33A (registry code 1151425, https://openairdocs.org/model/beech-f33a) (OpenAirDocs)
- Reported make and model: BEECH F33A
- NTSB investigation: [NTSB NYC02LA054](https://openairdocs.org/ntsb/NYC02LA054) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20020126002449A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) APPROXIMATELY 9:40 A.M., THE PILOT INITIATED THE TAKEOFF ROLL ON RUNWAY 10 WHEN THE BEECHCRAFT, BE-33-F33A AIRCRAFT 3276R, VEERED LEFT AFTER POWER WAS APPLIED. THE AIRCRAFT EXITED THE RUNWAY, CROSSED THE TAXIWAY, AND WENT THROUGH SOME SHRUBBERY BEFORE IT STRUCK A TREE. THE RIGHT LANDING GEAR COLLAPSED, THE NOSE GEAR WAS TORN OFF, AND THE PROPELLER BLADES HAVE TRIPLE CURLS, WHICH INDICATES SIGNIFICANT POWER. THE WINGS ALSO HAVE SUBSTANTIAL DAMAGE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB NYC02LA054](https://openairdocs.org/ntsb/NYC02LA054), Jan 26, 2002: Beech F33A (N3276R), Lynchburg, VA, substantial damage. Probable cause: The pilot's failure to maintain directional control and delay in aborting the takeoff.

## Other reports on N3276R (1)

Matched to the same aircraft by N-number and date.

- [Incident 20200101003149I](https://openairdocs.org/incident/20200101003149I), Jan 1, 2020: Beech F33A (N3276R), Michigan City, IN, Minor damage. The pilot of N3276R was unable to get the landing gear down and locked. As a result, the pilot made an intentional gear up landing. (The pilot was in…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.