Aero Air Beech 200 B200 accident
Beech 200 B200 · Accident: loss of control in flight during takeoff
From Tom Madsen (Dutch Harbor) Airport (DUT) to Adak, AK
Event
- NTSB case
- ANC20LA015
- 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
- Charter & commuter
- 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
- N547LM
- Operator
- Aero Air
- Onboard fatalities
- Unknown
- Route
- From Tom Madsen (Dutch Harbor) Airport (DUT), Dutch Harbor, AKTo Adak, AK
- Aircraft age
- About 22 years (built 1998)
- 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 135: Air Taxi & Commuter
- 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
- 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
According to the pilot, when the airplane’s airspeed reached about 90 knots during the takeoff roll, he applied back pressure to the control yoke to initiate the takeoff and noted a brief positive rate of climb followed by a sinking sensation. The airspeed rapidly decayed, and the stall warning horn sounded. To correct for the decaying airspeed, he lowered the nose then pulled back on the airplane’s control yoke and leveled the wings just before impacting the ocean.
The pilot stated there were no preaccident mechanical malfunctions or anomalies that would have precluded normal operation. Wind about the time of the accident was recorded as 110º downwind of the airplane at 15 knots gusting to 28 knots. The passengers recalled that the pilot’s preflight briefing mentioned the downwind takeoff but included no discussion of the potential effect of the wind conditions on the takeoff. The airplane’s estimated gross weight at the time of the accident was about 769.6 pounds over its approved maximum gross weight, and the airplane’s estimated center of gravity was about 8.24 inches beyond the approved aft limit at its maximum gross weight. It is likely that the pilot’s decision to takeoff downwind and operate the airplane over the maximum gross weight with an aft center of gravity led to the aerodynamic stall during takeoff and loss of control. Downwind takeoffs result in higher groundspeeds and increase takeoff distance. While excessive aircraft weight increases the takeoff distance and stability, and an aft center of gravity decreases controllability. Several instances of the operator’s noncompliance with its operational procedures and risk mitigations were discovered during the investigation, including two overweight flights, inaccurate and missing information on aircraft flight logs, and the accident pilot’s failure to complete a flight risk assessment for the accident flight. The operator had a safety management system (SMS) in place at the time of the accident that required active monitoring of its systems and processes to ensure compliance with internal and external requirements. However, the discrepancies noted with several flights, including the accident flight, indicate that the operator’s SMS program was inadequate to actively monitor, identify, and mitigate hazards and deficiencies.
Probable cause
The pilot’s improper decision to takeoff downwind and to load the airplane beyond its allowable gross weight and center of gravity limits, which resulted in an aerodynamic stall and loss of control. Contributing to the accident was the inadequacy of the operator’s safety management system to actively monitor, identify, and mitigate hazards and deficiencies.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ANC20LA015
- Event ID
- 20200117X71039
- Case number
- ANC20LA015
- 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: 681ae6329bcf18f232917ed4ad90ee04195a2a8231ded7be146147eea3e15589; retrieved 2026-09-16T10:57:33.193Z.