FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA128 · Beech 95-B55

22 Feb 2014 · LaGrange, GA, United States

Executive Aircraft Storage Beech 95-B55 · Accident: loss of control in flight on approach

From LaGrange Callaway Airport (LGC) to LaGrange Callaway Airport (LGC)

Report a problem

Event

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

Beech 95-B55

Aircraft type
Beechcraft 55
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
N36638
Onboard fatalities
Unknown
Route
From LaGrange Callaway Airport (LGC), LaGrange, GATo LaGrange Callaway Airport (LGC), LaGrange, GA
Aircraft age
About 34 years (built 1980)
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
Approach · VFR go-around
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 control in flight
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 › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

The accident airplane was inbound to the airport, conducting an instrument approach in visual meteorological conditions, when the pilot announced its position over the airport's common traffic advisory frequency (CTAF). Witnesses described the accident airplane's approach as fast and stated that the airplane never touched down. The accident airplane's engines then rapidly accelerated to full power before the airplane pitched up into a steep climb, banked left, rolled inverted, and struck the ground in a nearly vertical nose-down attitude, about 3,600 feet down the 5,599-foot-long runway. Throughout the morning of the accident, glider operations were being conducted on an intersecting runway. As the accident airplane floated down the runway, witnesses observed a tow plane accelerating down the intersecting runway with a glider in tow; The tow plane pilot then announced over the CTAF, "abort abort abort." The glider was then released from the tow plane and landed undamaged on the runway prior to the intersection of the two runways, while the tow plane crossed over the intersecting runway before taxiing back to the ramp.

Examination of the wreckage revealed no preimpact mechanical anomalies. According to witnesses on the airport, neither the glider nor tow plane appeared to be in immediate conflict with the accident airplane just before the accident; they stated that the accident pilot could have safely continued the landing. Additionally, the three pilots onboard the accident airplane had flown into the airport earlier in the day and were aware of the glider operations being conducted on the other runway. However, the accident pilot's observed reaction, as evidenced by the sudden application of full engine power followed by the airplane's abrupt increase in both pitch attitude and bank angle, suggest that he may have been surprised by the appearance of the glider and tow plane in his field of vision and perceived an imminent collision.

The FAA airport manual contained advisories for glider operations at the accident airport. Examination of the airport rules and regulations, published on the airport website, revealed that a local notice to airmen (NOTAM) was required to be filed prior to the conduct of glider operations. Additionally, a "spotter" was prescribed to be used during glider operations, positioned in a location from which the entire length of the intersecting runway could be viewed, in order to avoid conflicts with other aircraft. According to the airport rules and regulations, the tow plane and glider were prohibited from taking off without approval from the spotter. On the day of the accident, no NOTAM had been filed regarding the day's glider operations, nor was a spotter being used. Interviews with the glider operator revealed a widespread lack of knowledge regarding these published rules. Furthermore, while airport management was aware of the rules with regard to glider operations, there was no method in place to ensure compliance with the published risk management practices.

Probable cause

The pilot's overreaction to a perceived conflict with a tow plane and glider on an intersecting runway, which resulted in a loss of control during an attempted aborted landing. Contributing to the accident was the failure of the glider tow operator to follow and the airport operator to ensure compliance with published airport rules and regulations for glider tow operations.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA128
Event ID
20140222X51922
Case number
ERA14FA128
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: cbbf28eea9925ae1711cf2a2cc46c230ecaa3fb2900dcc8dc74b5bd7150794c4; retrieved 2026-09-14T16:10:57.530Z.