FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA161 · Cessna 172 C

18 Apr 2016 · Westmoreland, NY, United States

Cessna 172 C · Accident: loss of control in flight during takeoff

From Westmoreland, NY to Griffiss International Airport (RME)

Report a problem

Event

NTSB case
ERA16FA161
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
2 · 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 172 C

Aircraft type
Cessna 172
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
N1863Y
Operator
Unknown
Onboard fatalities
Unknown
Route
From Westmoreland, NYTo Griffiss International Airport (RME), Rome, NY
Aircraft age
About 54 years (built 1962)
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
Takeoff
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
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The private pilot was taking off for a personal flight from a private turf airstrip to return to his home base airport. He initiated takeoff with a 10° flap extension and about 1,130 ft of the 1,344 ft of usable runway remaining, despite a recommendation from the airstrip owner that he begin the takeoff from a point that would have provided an additional 200 feet of runway. After beginning the takeoff, and as the airplane approached the departure end of the runway, the aft fuselage bottom contacted the runway several times due to the pilot's control input, which likely slowed the airplane. Shortly after becoming airborne while in a nose-high attitude, the airplane entered an aerodynamic stall before colliding with a tree and then the ground. After coming to rest, all occupants were conscious and alert, but the rear seat occupant required assistance exiting the airplane. The pilot attempted to assist him from the wreckage, but an explosion occurred about that time. The pilot and rear seat occupant sustained burns and died 6 days and 1 day after the accident, respectively, due to their injuries from the fire.

Examination of the flight controls, engine, and engine accessories revealed no evidence of preimpact failure or malfunction that would have precluded normal operation. Extensive heat damage to the engine and engine accessories precluded an operational test of the engine. A sound spectrum analysis of a video recording of the takeoff provided by the airstrip owner revealed that the reduced engine rpm near rotation was attributed to the slow airspeed and not a loss of engine power.

The airplane was within weight and center of gravity limits. Takeoff performance data for the airplane indicated that, given the weather at the time of the accident, the distance required for the airplane to take off was about 786 ft and to clear a 50-ft obstacle was about 1,370 ft with no flaps on a hard surface runway. The chart did not contain figures for a soft, grass runway, which would increase the takeoff distance. Flaps at 10° would decrease the ground run by about 10% but would the advantage was lost to climb over a 50-ft obstacle. A speed study using the video showed that the average groundspeed between becoming airborne and the time of impact was about 47 knots, or 54 mph, which was the stall speed at gross weight and 0° bank angle. Even if the pilot had used the full usable runway distance, his decision to takeoff on this runway was poor given the performance capabilities of the airplane and the fact that the grass runway would likely have increased the takeoff and climb distance beyond that available. Further, it is likely that the pilot, when he noted that the airplane was nearing the end of the runway, increased the airplane's pitch, which resulted in the tail dragging, and lifted off the airplane with inadequate airspeed and exceeded the airplane's critical angle of attack, which resulted in an aerodynamic stall.

Probable cause

The pilot's decision to takeoff on the grass runway given the conditions at the time; his excessive aft control input during the takeoff roll, which resulted in the aft fuselage contacting the runway surface; and his failure to attain sufficient airspeed and exceedance of the airplane's critical angle of attack, which resulted in an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA161
Event ID
20160418X04320
Case number
ERA16FA161
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. 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: ef14f09f6d773f7b05992dee2903f9f8cc69916a798e742e32ba1012bd1db058; retrieved 2026-09-14T21:44:27.939Z.