CEN11CA059 · Hawker MK-20 Sea Fury
Cinima Sixteen Hawker MK-20 Sea Fury · Accident: loss of control on ground during landing
From Marion County Regional Airport (FLP) to Stephens County Airport (BKD)
Narrative check · The NTSB narrative appears to contradict this record's location, departure or destination and operator. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN11CA059
- 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
Hawker MK-20 Sea Fury
- Aircraft type
- Hawker MK-20
- 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
- C-FGAT
- Operator
- Cinima Sixteen Possible conflict
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Marion County Regional Airport (FLP), Flippin, ARTo Stephens County Airport (BKD), Breakenridge, TX
- Aircraft age
- Not recorded
- 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 · landing roll
- 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
- 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
- Personnel issues › Action/decision
- 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 pilot reported that prior to the accident flight and after the last annual inspection, the airplane had displayed poor (soft) braking qualities. This substandard braking capability required the pilot to pump the brakes to adequately decelerate on the ground. The pilot departed for a cross-country flight and did not lock the tailwheel. During landing at the destination airport, he was unable to maintain control of the airplane. The airplane ground looped counterclockwise, resulting in right landing gear collapsing and the right wing sustaining substantial damage. A postaccident examination of the airplane revealed the wheel brakes were improperly adjusted.
Probable cause
The improperly adjusted brakes and the pilot's failure to lock the tailwheel, resulting in a loss of directional control. Contributing to the accident was the pilot's decision to continue flying the airplane with a known brake deficiency.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11CA059
- Event ID
- 20101108X91241
- Case number
- CEN11CA059
- 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. 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: 17fb1fdccb42d0fc30b2f6892020611f3dfed553c652b887932d48d594c6e077; retrieved 2026-09-15T15:32:58.290Z.