ERA15LA334 · Beech B19
Beech B19 · Accident: loss of engine power (partial) during initial climb
From Dexter Regional Airport (1B0) to Dexter Regional Airport (1B0)
Event
- NTSB case
- ERA15LA334
- 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 B19
- Aircraft type
- Beechcraft 19
- 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
- N2013G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Dexter Regional Airport (1B0), Dexter, METo Dexter Regional Airport (1B0), Dexter, ME
- Aircraft age
- About 37 years (built 1978)
- 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
- Loss of engine power (partial)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot and flight instructor had flown for about 30 minutes before landing and conducting a subsequent takeoff. The instructor stated that, during the initial climb, the engine experienced a partial loss of power. He conducted a forced landing to a field during which the airplane impacted trees, resulting in substantial damage to the engine firewall, fuselage, and left wing. Examination of the engine revealed no evidence of any preimpact mechanical anomalies.
The flight instructor calculated that the total distance required to clear a 50-ft obstacle during the takeoff was 1,300 ft; however, postaccident calculations based on performance data in the airplane's flight manual indicated a required takeoff distance of about 1,700 ft. Given that there were 30-ft-tall trees located 50 ft beyond the departure end of the 1,250-ft-long turf runway, it is likely that the airplane had insufficient distance available for takeoff and initial climb to clear the trees.
Probable cause
The flight instructor’s inadequate preflight planning, which resulted in collision with trees and terrain during takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15LA334
- Event ID
- 20150902X33755
- Case number
- ERA15LA334
- 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: 84395cfa8388487bc3b78b88d25e046f475504a54c41a7ad7cc9d2e17326b572; retrieved 2026-09-16T02:44:34.504Z.