ERA13LA095 · Cessna 150J
Bamert Aviation Cessna 150J · Accident: landing area overshoot
From Charlotte-Monroe Executive Airport (EQY) to Goose Creek Airport (28A)
Event
- NTSB case
- ERA13LA095
- 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
Cessna 150J
- Aircraft type
- Cessna 150
- 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
- N50757
- Operator
- Bamert Aviation
- Onboard fatalities
- Unknown
- Route
- From Charlotte-Monroe Executive Airport (EQY), Monroe, NCTo Goose Creek Airport (28A), Indian Trail, NC
- Aircraft age
- About 44 years (built 1968)
- 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
- Landing · flare/touchdown
- 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
- Landing area overshoot
- 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
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that, while returning to his home base airport, the airplane had an electrical power failure, and, subsequently, the flaps would not fully extend. The airplane was high and fast on short final approach, and it touched down about 300 to 400 feet from the departure end of the runway. The flight instructor was unable to stop the airplane, and it overran the runway, went down an embankment, and collided with trees.
A postaccident examination of the airplane revealed no evidence of an electrical power failure. The battery was checked with a battery meter, and the battery held a charge. Control continuity was established for all of the flight controls. The flaps were operated with battery power only, and full up and down travel was achieved. An examination of the brakes revealed that they operated normally. No other anomalies were noted with the airplane that would have precluded normal operation.
Probable cause
The flight instructor’s failure to maintain adequate glidepath and airspeed control during short final approach and the airplane’s improper touchdown point, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13LA095
- Event ID
- 20121221X05132
- Case number
- ERA13LA095
- 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: 1390d31e31b498b1aa97abf0f97f99e7350b44763b173bcf1058345230b51769; retrieved 2026-09-15T20:39:29.027Z.