# NTSB NYC01LA038: Cessna 172K, N79054, Hagerstown, MD, November 17, 2000

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: November 17, 2000, 09:58 local (14:58 UTC)
- Place: Hagerstown, MD
- Coordinates: 39.629661, -77.710334 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.6297&lon=-77.7103&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report July 17, 2001
- Report: Approved by Office Director
- NTSB case key (mKey): 50638
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC01LA038
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/50638/pdf
- Page: https://openairdocs.org/ntsb/NYC01LA038

## Probable cause

The pilot's failure to remove the gust lock from the control column before takeoff, and his failure to abort the takeoff.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - in flight, takeoff - initial climb
  - removal of control/gust lock(s) - not removed, pilot in command (cause)
  - aborted takeoff - not performed, pilot in command (cause)
- In flight collision with terrain/water, descent - uncontrolled

## Analysis

During the takeoff roll, the pilot realized the control wheel lock was still connected to the control wheel and he attempted to remove it with both hands.  The airplane then rotated on its own, climbed to about 20 feet and 'crashed straight down' onto the runway.  The landing gear nose tire burst, the nose landing gear collapsed, and the airplane proceeded off the departure end of the runway.  According to the airplane's operating handbook, the second item on the PREFLIGHT INSPECTION checklist is to remove the control wheel lock.  Additionally, the third item on the BEFORE TAKEOFF checklist requires that the flight controls are 'free and correct.'  The pilot stated that he did not perform a run-up inspection on the airplane.

## Factual narrative

On November 17, 2000, at 0958 Eastern Standard Time, a Cessna 172K, N79054, was substantially damaged during takeoff at the Hagerstown Airport (HGR), Hagerstown, Maryland.  The certificated private pilot and three passengers were not injured.  Visual meteorological conditions prevailed and no flight plan was filed for the personal local flight conducted under 14 CFR Part 91.

According to the pilot, the purpose of the flight was to introduce several passengers to the Young Eagles Program.  He performed a pre-flight inspection, and explained to the passengers the function of each component as he checked it.  He then taxied the airplane to Runway 27 and applied full power for takeoff.  The trim tab was set in the "up" position, and the airplane rotated on its own at the end of the takeoff roll.  The pilot received "no elevator response" from the airplane during the climb, and then noticed the control wheel lock was still connected to the control yoke.   The airplane then "crashed back down on the runway," the nose landing gear tire "blew," the nose gear collapsed, and the airplane slid to a stop on its nose.

The pilot stated that he did not perform a run-up inspection because he had just flown in from another airport, and intended to immediately depart again.

According to the passenger seated in the right front seat, the pilot taxied to the runway and applied full throttle for takeoff.  During the takeoff roll, the pilot attempted to remove a pin from the control wheel with one hand.  About halfway down the length of the runway, the pilot used both hands to attempt to remove the pin, as the airplane lifted off the ground.  The airplane climbed to about 20 feet and "crashed straight down" onto the runway.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed the burst nose landing gear tire, and damage to the airplane's propeller, firewall, and belly.

According to the Cessna 152 Pilot's Operating Handbook, the second item on the PREFLIGHT INSPECTION checklist is to remove the control wheel lock.  Additionally, the second item on the BEFORE TAKEOFF checklist is to "check for free and correct movement" of the flight controls.

## Aircraft

- Registration: [N79054](https://openairdocs.org/aircraft/N79054), registered now, S/N 17257846, built 1969 (OpenAirDocs)
- Reported make and model: Cessna 172K
- Registry model: [Cessna 172K](https://openairdocs.org/model/cessna-172k) (registry code 2072430) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17257846
- Airframe hours: 6700
- Engines: Lycoming O-320 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Donald Myers
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, October 4, 2000, 11 hours before
- Departed: HGR
- Airport: HGR, Hagerstown Regional, runway 27, 5,461 × 150 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 66; private; airplane ratings: single-engine land; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 1,043 total, 887 in this make and model, 996 as pilot in command, 24 in the last 90 days, 7 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 280° at 11 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 46 °F, dew point 37 °F
- Altimeter: 29.00 inHg
- Observed at: HGR

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20001117038959A](https://openairdocs.org/incident/20001117038959A), Nov 17, 2000: Cessna 172K, Hagerstown, MD, No damage. (-23) On takeoff the nose wheel tire blew, the takeoff was aborted. The a/c rocked up on the nose landing gear collapsing the gear and damaging the firewall…

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.

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