FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA257 · Piper PA 28R-201

16 Jul 2016 · Esperance, NY, United States

Piper PA 28R-201 · Accident: collision during takeoff/landing during initial climb

From Hogan Airport (NY05) to Tweed New Haven Airport (HVN)

Report a problem

Event

NTSB case
ERA16FA257
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
3 · 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

Piper PA 28R-201

Aircraft type
Piper PA-28
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
N2241Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Hogan Airport (NY05), Esperance, NYTo Tweed New Haven Airport (HVN), New Haven, CT
Aircraft age
About 39 years (built 1977)
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
Collision during takeoff/landing
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 › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The private pilot and three passengers departed in the airplane from a 3,000-ft-long runway with a density altitude of about 3,000 ft and a light wind. Surveillance video showed that the airplane did not use the entire length of the runway for takeoff; the pilot began his takeoff roll where the paved section of the part turf/part asphalt runway began, resulting in 2,400 ft of available runway. During the ground roll, the nose of the airplane lifted off and then settled back onto the runway, and the airplane became airborne at 1,500 ft. Witnesses described the takeoff and initial climb as "slow" and "sluggish." The wings rocked, and the airplane climbed to about 100 ft in a continuous left turn before descending into trees 1,000 ft left of the runway centerline.

Examination of the airplane and its engine revealed no evidence of preimpact mechanical malfunction or anomaly. An estimate of the airplane's takeoff weight indicated that it was about 66 lbs over the maximum allowable takeoff weight of 2,750 pounds. Review of performance charts revealed that the takeoff ground roll distance for the airplane at the maximum allowable gross weight was about 2,180 ft. Review of radar data showed that from rotation to the final radar target, the airplane's groundspeed (which was about the same as its airspeed given the light wind) varied between 61 and 67 knots, which was about the airplane's calculated stall speed of 60 knots. Further, the witness observations were consistent with the pilot failing to attain sufficient airspeed, which resulted in the airplane's wing exceeding its critical angle of attack and an aerodynamic stall.

It is likely that the pilot lifted off prematurely at a speed lower than normal and was unable to accelerate or climb the airplane once it exited ground effect. A premature liftoff and a climb attempt at a speed significantly below best angle of climb speed (78 knots) placed the airplane in a situation where the power required for level flight was very near or exceeded the available power. To recover from this situation the pilot needed to lower the airplane's nose in order to accelerate the airplane to obtain a positive rate of climb. However, such an action is counterintuitive when low to the ground and requires accurate problem recognition, knowledge of the correct solution, and sufficient terrain clearance to accomplish.

Probable cause

The pilot's inadequate preflight weight and balance and performance planning, which resulted in the airplane being over gross weight. Also causal were the pilot's decision not to use the entire runway for takeoff, his premature liftoff, and his failure to attain adequate airspeed, which resulted in the airplane exceeding its critical angle of attack and an aerodynamic stall.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA257
Event ID
20160716X21535
Case number
ERA16FA257
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. 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: e8c6184105402e4eab59ea6c87f66c935ed69f6606f64b6c1937981ab4ad77c5; retrieved 2026-09-14T21:54:27.312Z.