FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13LA370 · Beech C23

20 Aug 2013 · Bingham, ME, United States

Beech C23 · Accident: aerodynamic stall/spin during initial climb

From Gadabout Gaddis Airport (ME08) to Augusta State Airport (AUG)

Report a problem

Event

NTSB case
ERA13LA370
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

Beech C23

Aircraft type
Beechcraft 23
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
N243RG
Operator
Unknown
Onboard fatalities
Unknown
Route
From Gadabout Gaddis Airport (ME08), Bingham, METo Augusta State Airport (AUG), Augusta, ME
Aircraft age
About 34 years (built 1979)
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
Aerodynamic stall/spin
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Tree(s)
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

  • Aircraft › Aircraft oper/perf/capability
  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Task performance

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

NTSB narrative

The airplane had arrived at the departure airport earlier in the day. Witnesses, including the passenger, stated that it took multiple attempts for the pilot to land on the turf runway upon arrival; however, the pilot reported that "it was a non-event going in." The airplane subsequently took off from the 2,000-ft-long, turf-covered runway that had trees near its departure end. The pilot reported that, during takeoff, the airspeed indicator did not appear to be working, so he "tapped it" with his fingers. He estimated that the airplane was traveling about 60 to 70 mph at that time. He pulled back on the control wheel, and, when the airplane reached about 20 ft above ground level, the stall warning activated. He then pushed forward on the control wheel to gain airspeed and turned the airplane slightly upriver. The right wing then contacted trees, and the airplane subsequently impacted the river nose first. Examination of the wreckage did not reveal any evidence of preimpact failures or malfunctions of the airplane or engine that would have precluded normal operation.

At the time of the accident, the temperature was about 80 degrees F, and the calculated density altitude was about 3,218 ft, which would have decreased the airplane's climb rate by about 30 percent. Further, according to the airplane flight manual, about 2,300 ft of turf runway would have been needed to clear a 50-ft obstacle. Therefore, due to the extended required ground roll and the degraded climb performance, the airplane was likely not able to attain a sufficient climb rate to clear the trees at the end of the runway.

Probable cause

The pilot's inadequate preflight planning, which resulted in his attempt to take off from a short, turf runway in high-density altitude conditions under which the airplane was unable to attain a positive climb rate to clear trees.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13LA370
Event ID
20130822X11459
Case number
ERA13LA370
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: 9a34d87c4a8485d48918ba5fe929c872de08739e187808c4418ca1e069586345; retrieved 2026-09-15T22:35:14.688Z.