GAA16CA475 · Beech 200 UNDESIGNAT
Beech 200 UNDESIGNAT · Accident: loss of control on ground during landing
From Florida Keys Marathon International Airport (MTH) to Orlando Apopka Airport (X04)
Event
- NTSB case
- GAA16CA475
- 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
Beech 200 UNDESIGNAT
- 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
- N369CD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Orlando Apopka Airport (X04), Apopka, FL
- Aircraft age
- About 40 years (built 1976)
- 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 · aborted after 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 on ground
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of a multi-engine turboprop airplane reported that during the landing flare he encountered a crosswind gust, which pushed the airplane to the right of the runway centerline. The pilot further reported that he applied power to abort the landing, but the airplane touched down in the grass to the right of the runway. After the wheels touched down in the grass, he reported that the power added "caught up with the aircraft," but the airplane was rolling toward trees and hangars. Subsequently, the pilot pulled the power to idle, but the right wing impacted a tree and the right main landing gear and nose wheel collapsed. A post-crash fire ensued after the collision and the right wing sustained substantial damage.
The pilot reported no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
There was no record of the observed weather at the airport during the accident. An automated weather observing system about 14 nautical miles from the accident airport, near the time of the accident, recorded the wind variable at 5 knots.
Probable cause
The pilot's failure to maintain directional control during an attempted aborted landing in gusty crosswind conditions, which resulted in a runway excursion and an impact with a tree.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA475
- Event ID
- 20160912X53321
- Case number
- GAA16CA475
- 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: 825029a4b09de3de28a2215dc5628d95a0f8fcbbd2450cd2732f9de53634dd04; retrieved 2026-09-16T04:15:20.012Z.