# NTSB NYC97LA056: Cessna 150, N11438, Clarksville, MD, February 20, 1997

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: February 20, 1997, 16:45 local (21:45 UTC)
- Place: Clarksville, MD
- Coordinates: 39.200592, -76.939041 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=39.2006&lon=-76.9390&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report April 10, 1998
- Report: Approved by Office Director
- NTSB case key (mKey): 39329
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC97LA056
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/39329/pdf
- Page: https://openairdocs.org/ntsb/NYC97LA056

## Probable cause

The pilot's failure to maintain directional control and 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 - on ground/water, takeoff - roll/run
  - directional control - not maintained, pilot in command (cause)
  - aborted takeoff - not performed, pilot in command (cause)
  - ground loop/swerve - inadvertent, pilot in command
- On ground/water collision with object, takeoff - roll/run
  - object - tree(s)

## Analysis

The aircraft veered off the runway during the takeoff roll and collided with trees.  According to the pilot, 'we did a normal run up at the point half way up the hill on runway 13.  Everything looked okay, controls worked okay, carburetor heat and magnetos checked okay.  We taxied to the top of the hill and attempted to take off.  Within seconds after we started to roll on runway 13, the airplane veered to the left.  I applied full right rudder.  The airplane straightened out but it had gone too far left.  With the right pedal on the floor, the airplane had straightened out fairly close to a line of small pine trees on the left side of the runway. The airplane continued parallel to the trees for about 100 feet even though I continued full right rudder.  Finally, the airplane turned left into the trees.'  The pilot further stated that he 'should have pulled power immediately when [the] airplane went out of control.'

## Factual narrative

On February 20, 1997, about 1645 eastern standard time, a Cessna 150, N11438, was substantially damaged when it collided with trees during the takeoff roll at the Haysfield Airport, Clarksville, Maryland.  The certificated private pilot and passenger were not injured.  Visual meteorological conditions prevailed for the local flight.  There was no flight plan for the personal flight conducted under 14 CFR Part 91.

In a statement submitted by the pilot, he stated:

"We did a normal run up at the point half way up the hill on runway 13.  Everything looked okay, controls worked okay, carburetor heat and magnetos checked okay.  We taxied to the top of the hill and attempted to take off.  Within seconds after we started to roll on runway 13, the plane veered to the left.  I applied full right rudder.  The plane straightened out but it had gone too far left.  With the right peddle on the floor, the plane had straightened out fairly close to a line of small pine trees on the left side of the runway.  The plane continued parallel to the trees for about 100 feet even though I continued full right rudder.  Finally, the plane turned left into the trees."

The pilot further stated that he "should have pulled power immediately when [the] plane went out of control."

Examination of the wreckage by a Federal Aviation Administration Inspector did not disclose evidence of mechanical malfunction with the airplane, nor did the pilot report any.

In the NTSB Form 6120.1/2, the pilot reported that the winds were from 310 degrees at 12 knots, gusting to 16.

## Aircraft

- Registration: [N11438](https://openairdocs.org/deregistered/N11438-2017-07-13), registration cancelled 2017-07-13, S/N 15075421, built 1973 (OpenAirDocs)
- Reported make and model: Cessna 150
- Registry model: [Cessna 150L](https://openairdocs.org/model/cessna-150l) (registry code 2071826) (OpenAirDocs)
- Registry engine: [Continental 0-200 series](https://openairdocs.org/engine/continental-0-200-series) (registry code 17020, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 15075421
- Airframe hours: 4562
- Engines: Continental O-200 100 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: Tds Air Inc
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, November 22, 1996, 78 hours before
- Departed: MD24
- Airport: MD24, Haysfield, runway 13, 2,200 × 50 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 51; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 217 total, 72 in this make and model, 175 as pilot in command, 2 in the last 90 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: variable at 10 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 68 °F

## 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 19970220048079A](https://openairdocs.org/incident/19970220048079A), Feb 20, 1997: Cessna 150L, Clarksville, MD, Substantial damage. (-16) Pilot and passenger attempted takeoff on a grass runway with wind down the runway at 10-15 knots. (Aircraft at gross). Aircraft started to veer left,…

## Other investigations on N11438 (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 NYC76DFA33](https://openairdocs.org/ntsb/NYC76DFA33), Apr 18, 1976: Cessna 150 (N11438), Scotia, NY, substantial damage

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.
