ERA24FA209 · Rockwell International 690A
Rockwell International 690A · Accident: loss of control in flight en route
From Washington Manassas Harry P. Davis Field (HEF) to Georgetown County Airport (GGE)
Event
- NTSB case
- ERA24FA209
- 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
- 2 · 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
- Instrument Meteorological Cond
Rockwell International 690A
- Aircraft type
- Rockwell 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
- N690BM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Washington Manassas Harry P. Davis Field (HEF), Manassas, VATo Georgetown County Airport (GGE), Georgetown, SC
- Aircraft age
- About 49 years (built 1975)
- 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
- En route · cruise
- 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
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was in cruise flight at 20,000 ft on an instrument flight rules (IFR) cross-country flight when the pilot reversed course. When an air traffic controller queried the pilot, he replied, “we have lost…we need to climb.” The controller then asked the pilot, “what is your issue?” and the pilot responded, “we have lost autopilot.” There were no further communications received from the pilot and radar contact with the airplane was lost shortly thereafter. A witness who saw the airplane as it descended toward ground impact described that it was on fire. The wreckage of the airplane was heavily fragmented and scattered amongst a wooded area, with a debris path over 3 miles long. The left wing, left engine, left propeller, and empennage were heavily burnt and found at the main wreckage site. The right wing was separated at the wing root and was found 1/4-mile north of the main wreckage. The right wing was fire damaged, and the right engine and right propeller were not located. The vertical and horizontal stabilizers were found about 3/4-mile north of the main wreckage. All fractures exhibited overstress features consistent with an in-flight breakup. Mapping of the wreckage indicated that the tail components likely separated first, followed by the right wing. This structural failure resulted in the horizontal and vertical stabilizers deforming and subsequently separating from the airplane. The lack of heat damage indicated that this separation occurred before the fire and that the inflight fire observed by the witness was likely a result of the inflight breakup. No evidence of any mechanical malfunctions or failures that would have preceded the inflight breakup was found during the postaccident wreckage examination. Review of data provided by a preflight planning application vendor revealed that before the accident flight, the pilot filed an IFR flight plan and received a weather briefing. The briefing included an AIRMET for moderate icing with the freezing level between 9,000 and 13,000 ft, with tops at 24,000 ft, which included a portion of the intended route of flight. This AIRMET was active at the time of the accident. Satellite imagery of the accident area and upper air sounding model data depicted cloudy, instrument meteorological conditions across the region from the surface to above 30,000 ft. Upper air data and computer modeling also identified the potential for some icing as the airplane climbed above 11,000 ft, and it is possible that some trace icing could have accumulated on the airplane’s structure during this time. Weather radar reflectivity values indicated that along the final portion of the accident flight path, the potential for an encounter with more significant structural airframe icing was greater, though the severity of that icing could not be definitively quantified. The airplane was equipped with de-ice boots on the leading edges of the wings, horizontal stabilizer, and vertical stabilizer. Most of the components of the airplane’s de-ice system were destroyed during the accident sequence and could not be examined. Review of maintenance logbooks did not reveal evidence of any anomalies or preexisting discrepancies that would have precluded normal operation of the de-ice system before the accident flight. The pilot’s statement to air traffic control that he had “lost the autopilot,” shortly before radar contact with the airplane was lost and the airplane broke up in flight, suggest that he may have been experiencing difficulty controlling the airplane, either with or without the aid of the autopilot. The airplane’s pilot’s operating handbook contained an airworthiness directive (AD) that explicitly warned pilots who encountered certain types of structural icing in flight not to utilize the autopilot, as it could mask tactile cues indicative of adverse changes in the airplane’s handling characteristics. Given this information, it is likely that the pilot’s loss of control that ultimately resulted in the airplane’s inflight breakup was preceded by an accumulation of structural ice that altered the airplane’s handling characteristics in a way that the pilot had not anticipated and was unable to recover from.
Probable cause
The pilot’s loss of control following an encounter with structural icing, which resulted in an inflight breakup of the airplane.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24FA209
- Event ID
- 20240505194204
- Case number
- ERA24FA209
- 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, cause areas. 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: 84fc43782b0b6ab61e60d51081879a129a866196550ef2d65ecdd679de7bd975; retrieved 2026-09-15T08:13:31.265Z.