ERA14LA312 · Raytheon Aircraft Company C90A
Becs Raytheon Aircraft Company C90A · Accident: loss of control in flight during landing
From Frederick W. Smith International Airport (MEM) to Houston Municipal Airport (M44)
Event
- NTSB case
- ERA14LA312
- 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
Raytheon Aircraft Company C90A
- Aircraft type
- Beechcraft 90
- 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
- N800MK
- Operator
- Becs
- Onboard fatalities
- Unknown
- Route
- From Frederick W. Smith International Airport (MEM), Memphis, TNTo Houston Municipal Airport (M44), Houston, MS
- Aircraft age
- About 18 years (built 1996)
- 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
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he was at the controls during the approach and landing. He stated that, just before touchdown, the right wing "rose severely" and that the copilot called out "windshear" and "go around." As he applied power, the airplane rolled left again, so he retarded the throttles. The airplane subsequently settled into the grass to the left side of the runway and then struck a ditch, spun around, and came to rest upright. The airplane was substantially damaged due to the impact and a postaccident fire. The copilot reported that it felt like the wind was trying to "lift the tail and cartwheel them over."
The airport did not have weather reporting capability; however, surrounding airports reported light wind with no gusts, and no windshear was reported. A review of weather radar and geostationary weather satellite data for the accident region did not identify any convective or gust-front activity, and a review of National Weather Service data did not identify the presence of, or conditions conducive to, ground-level windshear for the accident region at the time of the accident.
A review of the cockpit voice recorder (CVR) transcript revealed that, although the copilot called out "go around," he did not mention windshear or any other weather phenomena at any time during the approach or accident sequence. Based on the conversation between the pilots recorded on the CVR, the approach was probably unstable for a period of time before landing. The CVR transcript also revealed that the more experienced copilot provided a significant amount of "coaching" during the approach; however, it could not be determined what effect this might have had on the pilot's performance.
Probable cause
The pilot’s failure to maintain a stabilized approach and his subsequent failure to maintain airplane control during the landing flare, which resulted in touchdown off the side of the runway and collision with a ditch.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14LA312
- Event ID
- 20140625X34015
- Case number
- ERA14LA312
- 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: f65a650947acef787c2dd6eb31e8684f1ca803fb265ba3a818a81f30b27e1365; retrieved 2026-09-16T00:29:08.263Z.