FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19LA043 · Aero Commander 690 C

12 Nov 2018 · Myrtle Beach, SC, United States

Aero Commander 690 C · Accident: turbulence encounter on approach

From CBE · Cumberland, MD to Myrtle Beach International Airport (MYR)

Report a problem

Event

NTSB case
ERA19LA043
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
0
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

Aero Commander 690 C

Aircraft type
Aero Commander 690
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
N840JC
Operator
Unknown
Onboard fatalities
Unknown
Route
From CBE · Cumberland, MDTo Myrtle Beach International Airport (MYR), Myrtle Beach, SC
Aircraft age
About 37 years (built 1981)
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 · IFR final approach
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
Turbulence encounter
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

  • Environmental issues › Conditions/weather/phenomena

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

NTSB narrative

The pilot was approaching the airport to land in instrument meteorological conditions when he encountered heavy turbulence. He continued the approach and the airplane started to descend rapidly. Although he added full power in an attempt to climb, the airplane continued to descend until it collided with the Atlantic Ocean. The forward portion of the fuselage, which included the cockpit separated from the airplane. The pilot did not report any anomalies with the airplane before the accident. Review of weather information for the area of the airport about the time of the accident revealed light to moderate precipitation with a high potential for moderate turbulence and low-level wind shear below about 2,000 ft. Radar imagery did not reveal signatures typically associated with microburst activity. Based on the available information, it is likely that the pilot encountered low-level windshear and turbulence during the approach, which resulted in a loss of airplane control.

Probable cause

An encounter with low-level windshear and turbulence during the landing approach, which resulted in a loss of airplane control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19LA043
Event ID
20181112X51649
Case number
ERA19LA043
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: d83297d99dd0cede11d31f09aad1fda9846d45cd60c24c2e2b56015408aa420c; retrieved 2026-09-16T08:25:48.445Z.