Casualties unknown

2007-12-01: Cessna 172N (N259ER) — Washington Flying Club — Gaithersburg, MD

Gaithersburg, MD, US

On December 1, 2007, a Cessna 172N (registration N259ER) operated by Washington Flying Club was involved in an aviation accident near Gaithersburg, MD. Investigators recorded the probable cause as: The student pilot's failure to maintain aircraft control during an attempted touch-and-go. Contributing to the accident was the instructor's delay in taking remedial action, and the presence of trees in proximity to the side of the runway. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive; 10 related events involving the same aircraft type or operator are linked below.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 1781061362Data APIEditorial standards

A student pilot and CFI lost control during takeoff, striking a treeline 80 feet from the runway. The CFI was unable to prevent the impact despite verbal and physical intervention.

Accident Sequence

A student pilot with 12 hours of flight time and a certificated flight instructor (CFI) were conducting their first flight together. The student had completed one takeoff, traffic pattern circuit, and landing. Following the CFI's instruction, the student initiated another takeoff. After lift off, the airplane began to veer to the left. Despite verbal commands from the CFI, the drift and turn continued. The CFI then attempted to physically intervene on the flight controls but was initially resisted by the student. Recognizing that they could not avoid a treeline located 80 feet from the runway edge, the CFI leveled the wings and attempted to shut down the engine. The airplane impacted the trees approximately 10 feet above ground level.

Post-Accident Observations

The surface weather observation reported winds of 5 knots. Subsequent to the accident, the CFI stated that he normally emphasized transfer of control in preflight briefings, but he did not discuss that with this student.

Airport Information

The accident was the fifth one in 24 years that involved the same treeline. While the treeline was coincident with the runway proximity limit specified in the advisory circular for airport design, the airport's 2002 improvement plan prescribed an increase in the distance between the treeline and the runway edge. As of July 2009, the treeline had not been relocated.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20081003X17816. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.