Skip to content

Atlas / NTSB / ERA23LA229

NTSB CAROL · Event

Event ERA23LA229

2023-05-11 South Bethlehem, New York, United States Airport · 4B0 Serious 1 aircraft Status: Completed

Registry · N1596E

FAA Aircraft Registry record.

Make / Model

CESSNA 172N

Engine

LYCOMING O-360 SERIES (180 hp)

Seats / Engines

4 seats · 1 engine

Last airworthiness date

20021217

ADS-B equipped

Yes — Mode-S A0EECD

Registrant of record

TEAM 172-03 LLC

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot’s improper decision to attempt an intersection takeoff in a tailwind when the full runway in the opposite, headwind direction was available.

Factual narrative

On May 11, 2023, about 1420 eastern daylight time, a Cessna 172N, N1596E, was substantially damaged when it was involved in an accident near South Bethlehem, New York. The private pilot and one passenger suffered serious injuries, while a second passenger incurred minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that his injuries included a vertebrae fracture and concussion, and he could not recall the accident sequence. A pilot-rated witness reported that the airplane was attempting to take off from runway 19 at South Albany Airport (4B0), South Bethlehem, New York. Runway 19 was 2,853 ft-long, 60 ft-wide, and consisted of asphalt. About 15 minutes before the accident takeoff, another Cessna 172 performed a tailwind takeoff on runway 19 uneventfully; however, that airplane started its takeoff roll at the beginning of the runway. The accident airplane took off beginning at a runway intersection, with about 2,293 ft of runway remaining, in an approximate 9-kt tailwind, gusting to 13 or 14 kts. The accident airplane subsequently impacted a field near the departure end of runway 19 and came to rest upright. Examination of the wreckage by a Federal Aviation Administration inspector revealed substantial damage to the left wing and fuselage. The inspector observed the flaps in the retracted position and did not note evidence of any preimpact mechanical malfunctions. Following the wreckage recovery to a storage facility, recovery company personnel were able to rotate the propeller by hand, confirm powertrain continuity to the rear accessory section, and attain thumb compression on all cylinders. Review of weight and balance data for the airplane revealed that it had a useful load of 820 lbs. The reported occupant weights totaled about 740 lbs., leaving 80 lbs for fuel and baggage. The amount of fuel onboard and weight of the baggage was unknown. Review of performance data from a make and model pilot operating handbook revealed that, at maximum gross weight and in the reported wind and temperature conditions, the airplane required about 2,300 ft of runway to take off and clear a 50-ft obstacle. There were no performance data for any tailwind greater than 10 knots or any weight above the maximum gross weight. Due to his injuries, the pilot did not recall the accident. A pilot-rated witness reported seeing the airplane make an intersection takeoff from a 2,853-ft-long runway with a tailwind (9 kts, gusting to 13 or 14 kts). The intersection used resulted in only 2,293 ft of runway available. The accident airplane subsequently impacted a field near the departure end of the runway and came to rest upright. Postaccident examination of the wreckage did not reveal evidence of any preimpact mechanical malfunctions. Review of weight and balance data for the airplane revealed that it was loaded to within 80 pounds of its maximum gross weight before accounting for baggage and fuel (the quantities of which could not be determined). Review of performance data revealed that at maximum gross weight, in the reported wind and temperature conditions, the airplane required about 2,300 ft of runway to take off to clear a 50-ft obstacle. There were no performance data for tailwind conditions greater than 10 knots or any weight above the maximum gross weight. Based on the takeoff performance data, the pilot was likely attempting to operate the airplane in excess of its performance capabilities, which resulted in a subsequent collision with terrain when it was unable to climb. Instead of departing with a tailwind, and from an intersection with a reduced amount of runway remaining, had the pilot instead elected to depart in the opposite direction utilizing the full runway length, it is possible that the accident could have been avoided. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot
  • Environmental issues-Conditions/weather/phenomena-Wind-Tailwind-Decision related to condition
  • Aircraft-Aircraft oper/perf/capability-Aircraft capability-Takeoff distance-Capability exceeded

Verbatim from NTSB's published report. Source file NTSB_2023_ERA23LA229.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type. Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗