FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA20LA288 · Cessna 170 Undesignat

13 Aug 2020 · Ardmore, TN, United States

Cessna 170 Undesignat · Accident during initial climb

From Ardmore, TN (no airport) to Moontown Airport (3M5)

Report a problem

Event

NTSB case
ERA20LA288
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 170 Undesignat

Aircraft type
Cessna 170
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N3962V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Ardmore, TN (no airport)To Moontown Airport (3M5), Huntsville, AL
Aircraft age
About 73 years (built 1947)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Initial climb
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot, a passenger, and a dog were departing from a grass field. The pilot had purchased the airplane about 5 days before and this was the first time he had operated from the field. He reported that, after takeoff, there was “inadequate thrust” to climb, and he performed a forced landing to a pasture, during which the airplane sustained substantial damage. Postaccident examination of the airplane revealed that the wing flaps were in the retracted position. Examination of the engine revealed a partial fracture just aft of the propeller flange. The fracture was visibly twisted, and the fracture face displayed a 45° angle to the longitudinal axis of the crankshaft. This was indicative of an overload type of failure consistent with the impact, and that the engine was producing power during the accident sequence. The right magneto was also damaged during the impact, which precluded functional testing. Overall, the examination of the engine did not reveal evidence of any preimpact failures or malfunctions that would have precluded normal operation. The pilot believed that the field was about 2,000 ft long; however, review of satellite images indicated that the field was only about 1,230 ft long and sloped uphill. Obstacles existed along the departure path in the form of a driveway, trees, and buildings. Review of the airplane owner’s manual indicated that, for shortest takeoff the wing flaps should be in the “full down” (30°) position. It also noted that for unusually short field takeoffs, the application of wing flaps should occur just before the airplane is ready to leave the ground, and the flaps should not be retracted until an altitude of at least 100 ft above the highest obstacle. The density altitude around the time of the accident was about 3,224 ft. Under such conditions, the pilot would have experienced a takeoff distance about 34% longer than normal and an approximate 26% reduction in rate of climb. Review of performance information contained in the airplane owner’s manual revealed that, under similar atmospheric conditions, at maximum gross weight with the flaps retracted, the airplane would have required a takeoff ground roll distance of about 880 ft; however, this information was valid for a level, hard-surfaced runway. The distance to clear a 50-ft obstacle was about 2,200 ft. No performance information was published for operations off turf/grass surfaces, which provide more rolling resistance (drag) than paved surfaces. Based on the available information, it is likely that the airplane’s takeoff and climb performance was reduced due to the elevated density altitude conditions and the additional drag provided by the grass. Additionally, the pilot did not use the short-field takeoff technique prescribed by the owner’s manual. Had the pilot more thoroughly familiarized himself with the constraints of the area he was attempting to take off from, as well as the information provided in the owner’s manual, he likely would have realized that departing from the field under the accident circumstances provided little margin for a successful takeoff and climbout.

Probable cause

The pilot’s inadequate preflight planning and his decision to depart from a constrained, grass-covered field in elevated-density altitude conditions, which resulted in reduced takeoff and climb performance and a subsequent forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA20LA288
Event ID
20200818X01327
Case number
ERA20LA288
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: cc281c0b3a20e9d8dc46fdeadc7571a1d54814f53d66c28b56858fe2a8d1a6d8; retrieved 2026-09-16T12:40:47.792Z.