CEN20LA352 · Beech 200 B200
Beech 200 B200 · Accident: loss of control in flight during takeoff
From Chicago Rockford International Airport (RFD) to Dupage Airport (DPA)
Event
- NTSB case
- CEN20LA352
- 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
- 1 · 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
Beech 200 B200
- Aircraft type
- Beechcraft 200
- 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
- N198DM
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chicago Rockford International Airport (RFD), Rockford, ILTo Dupage Airport (DPA), West Chicago, IL
- Aircraft age
- About 36 years (built 1984)
- 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
- Takeoff
- 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
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot departed on a positioning flight in the twin-engine airplane. Videos recorded by multiple airport-based cameras showed the airplane take off from runway 19. Shortly after liftoff, the airplane started turning left, and the airplane developed a large left bank angle as it was turning. The airplane departed the runway to the left and impacted the ground. During the impact sequence, an explosion occurred, and there was a postimpact fire. An airplane performance study showed that during the takeoff, a nose-left sideslip, a left side force, and a left roll occurred, consistent with the loss or reduction in thrust of the left engine. The sideslip was reduced, likely due to inputting rudder to balance the side force, and the airplane briefly rolled right possibly due to an overcorrection in rudder. The airplane pitched up and was able to begin climbing again; however, it continued to lose speed. The sideslip then reversed, and the airplane rolled left again before impacting the ground. The study indicated that before rotating and lifting off, the airplane accelerated to a groundspeed of 98 knots (kts) and an airspeed of 105 kts, which was about 19 kts above the published minimum control speed for the airplane. Therefore, the airplane had achieved sufficient airspeed for the pilot to maintain control despite a loss or reduction in left engine thrust provided he made the appropriate control inputs. The sideslip force calculations indicated that there was a partially successful attempt to maneuver the airplane back to level flight when the airplane rolled back right, but it was not maintained. The right rudder input would need to be held until the thrust asymmetry was corrected. Teardown examinations of the engines and propellers found no evidence of preimpact failure. Both engines exhibited evidence of operation at impact. Damage to the propeller blades and hubs indicated that neither propeller was feathered at impact. The predominant left propeller blade bending and twisting was aft and toward low pitch. The predominant right propeller blade bending and twisting was forward in the thrust direction and toward high pitch. Analysis of the propeller internal witness marks and the blade damage found that the right engine was producing more power than the left engine at initial impact. Based on the available evidence, it could not be determined why the left propeller was not feathered at impact, even though the autofeather system was armed. The rudder trim knob was found 4 units to the left; the aileron trim knob was found 6 units to the right; and the rudder boost switch was found in the OFF position. The before engine starting checklist in the pilot’s operating handbook for the airplane specified that the rudder and aileron trim be set and that the rudder boost switch be on. Therefore, the postaccident positions of the rudder trim knob, aileron trim knob, and rudder boost switch likely indicate the pilot did not follow the before engine starting checklist. With the rudder boost switch not being on, it could not be determined based on the available evidence, what role that system may have had with the pilot attempting to maintain control of the airplane during the asymmetric thrust sequence. Although the pilot’s previous history of significant coronary artery disease and the scar in his left ventricle placed him at increased risk of an acute cardiac event, whether such an event occurred at the time of the accident could not be determined from the available information. Absent evidence of an engine malfunction, the investigation considered whether the left engine’s thrust reduction was the result of a malfunction in the throttle control system or an uncommanded throttle movement due to an insufficient friction setting of the airplane’s power lever friction locks. However, heavy fire and impact damage to the throttle control system components, including the power quadrant and cockpit control lever friction components, precluded determining the position of the throttle levers at the time of the loss of thrust or the friction setting during the accident flight. Thus, the reason for the reduction in left engine thrust could not be determined.
Probable cause
The pilot’s failure to maintain airplane control following a reduction of thrust in the left engine during takeoff. The reason for the reduction in thrust could not be determined based on the available evidence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA352
- Event ID
- 20200820X85853
- Case number
- CEN20LA352
- 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, 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: fbc8cfb78d2e709e3b64b2316f2648885dc57a83b0405b688a19dfb3c761d86e; retrieved 2026-09-15T07:18:27.346Z.