# NTSB FTW97LA008: Cessna 172M, N172JF, Tuttle, OK, October 5, 1996

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: October 5, 1996, 09:30 local (14:30 UTC)
- Place: Tuttle, OK
- Coordinates: 35.290206, -97.749481 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=35.2902&lon=-97.7495&mi=10
- Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report April 3, 1997
- Report: Approved by Office Director
- NTSB case key (mKey): 20084
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW97LA008
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/20084/pdf
- Page: https://openairdocs.org/ntsb/FTW97LA008

## Probable cause

failure of the pilot to maintain directional control during takeoff roll, which resulted in a ground swerve.  Factors relating to the accident were: tall grass along the edges of the runway, and the proximity of the fence, fence posts, and trees.

## 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
  - terrain condition - high vegetation (contributing factor)
  - directional control - not maintained, pilot in command (cause)
  - ground loop/swerve - inadvertent, pilot in command (cause)
- On ground/water collision with object, takeoff - roll/run
  - object - fence (contributing factor)
  - object - fence post (contributing factor)
  - object - tree(s) (contributing factor)

## Analysis

While approaching to landing at a private airstrip, the airplane's spinner impacted a transmission line; however, the pilot managed to land without further incident. After landing and clearing the 2,300 foot sod airstrip, the pilot checked the airplane for damage. He found only incidental damage to the propeller spinner. After inspecting the engine and completing a full engine runup, the pilot elected to depart the airstrip to the south. The pilot stated that as the airplane approached rotation speed during an up slope takeoff roll, it started to veer to the left, and he was unable to maintain directional control with opposite rudder. Subsequently, the airplane veered off the left side of the strip and impacted fence posts and trees. Witnesses stated that the grass along the edges of the runway was 'long enough to drag a wheel down.'  Post-recovery examination of the airframe confirmed flight control continuity to the rudder, elevators and ailerons. Additionally, no anomalies were found with the nose wheel steering mechanism or brake system.

## Factual narrative

On October 5, 1996, at 0930 central daylight time, a Cessna 172M, N172JF, was substantially damaged following a loss of control while on takeoff roll from a private airstrip near Tuttle, Oklahoma.  The airplane, owned and operated by a private owner, was being operated under Tittle 14 CFR Part 91.  The private pilot and the 3 passengers were not injured.  Visual meteorological conditions prevailed for the local personal flight for which a flight plan was not filed.  The flight departed from the Wiley Post Airport, near Bethany, Oklahoma, at approximately 0830.

According to the pilot, the rented airplane had been "cruising at about 1,200 feet AGL in the local area for about an hour when the engine began to run rough."  After circling the field, the pilot elected to execute a precautionary landing at the Thompson private airstrip near Tuttle, Oklahoma, where an ultralight fly-in was underway.  The pilot added that while landing to the south, the airplane's spinner impacted a power line; however, he managed to land without further incident.

After landing and clearing the 2,300 foot sod runway, the pilot checked the airplane for damage.  He only found incidental damage to the propeller spinner.  After inspecting the engine and completing a full engine runup, the pilot concluded that the rough running engine was "probably the result of carburetor icing" and he elected to depart the airstrip to the south and return to the Wiley Post Airport.  The airstrip has a slight up slope when taking off to the south.

The pilot stated that as the airplane approached rotation speed during the takeoff roll, the aircraft started to veer to the left and he was unable to maintain directional control "after applying full opposite rudder."  Subsequently, the airplane veered off the left side of the runway impacting fence posts and trees.  On the enclosed pilot/operator report, the pilot reported that the winds at the time of the accident were from 180 degrees at 12 knots.

Examination of the airplane by the FAA inspector at the accident site revealed that the left main landing gear separated from the airframe, the left lift strut was bent and the outer portion of the left wing sustained structural damage.  Post-recovery examination of the airframe by the operator and the FAA inspector confirmed flight control continuity to the rudder, elevators, ailerons.  Additionally, no anomalies were found with the nose wheel steering mechanism or brake system.

Witnesses at the airstrip provided the following information.  The pilot attempted to take off with the wing flaps in the retracted (up) position.  One witness stated that "in his opinion, the airplane assumed an exaggerated nose high attitude early during the takeoff roll and the pilot might have tried to pull the airplane off the ground prior to attaining flying speed."  An ultralight pilot stated that the grass along the edges of the airstrip was "long enough to drag the wheel down."

An estimate of the weight of the airplane at the time of the accident places the airplane within its limits.  The person who last refueled the airplane stated that both fuel tanks had been topped off to within a 1.5 inches from the top of the filler neck.

## Aircraft

- Registration: [N172JF](https://openairdocs.org/deregistered/N172JF-2001-08-27), registration cancelled 2001-08-27, S/N 17267410 (OpenAirDocs)
- Reported make and model: Cessna 172M
- Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs)
- Category: Airplane
- Serial number: 17267410
- Airframe hours: 3445
- Engines: Lycoming O-320-E2D 150 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: W.L. Frank
- Registered owner: Gregg A. Frank
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, October 2, 1996, 15 hours before
- Departed: 53OK
- Destination: PWA, BETHANY, OK
- Airport: 53OK, Thompson Field, runway 18, 2,300 × 50 ft, grass/turf

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 47; private; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 129 total, 29 in this make and model, 80 as pilot in command, 1 in the last 90 days, 1 in the last 24 hours

## Weather

- Conditions: Visual (VMC), Day
- Wind: 170° at 7 knots
- Visibility: 3 statute miles
- Lowest ceiling: none
- Temperature: 61 °F, dew point 61 °F
- Altimeter: 30.00 inHg
- Observed at: OKC, 12 nm away

## 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 19961005030929A](https://openairdocs.org/incident/19961005030929A), Oct 5, 1996: Cessna 172M, Tuttle, OK, Substantial damage. Rough engine landed sod strip. Checked out. Veered off alignment on takeoff into trees. Full flaps early liftoff. (-23) pilot stated he took off for a pleasure…

## Other investigations on N172JF (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 FTW99FA006](https://openairdocs.org/ntsb/FTW99FA006), Oct 11, 1998: Cessna 172M (N172JF), Oklahoma City, OK, destroyed, 1 fatal. Probable cause: Suicide.

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.
