FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN19LA219 · Fisher Flying Products Super Koala

6 Jul 2019 · Hazen, ND, United States

Fisher Flying Products Super Koala · Accident: flight control system malfunction/failure during takeoff

From Mercer County Regional Airport (HZE) to Mercer County Regional Airport (HZE)

Report a problem

Event

NTSB case
CEN19LA219
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

Fisher Flying Products Super Koala

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
N220FF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Mercer County Regional Airport (HZE), Hazen, NDTo Mercer County Regional Airport (HZE), Hazen, ND
Aircraft age
About 11 years (built 2008)
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
Flight control system malfunction/failure
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
  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane owner and a mechanic had reassembled the airplane's wings and re-rigged the flight controls; the pilot had subsequently been having trouble with aileron control during test flights. The accident flight was the fourth test flight of the day to diagnose and fix the issue. During takeoff, the airplane "quickly" became airborne and began to roll to the left about 15 ft above the ground. The pilot applied full right aileron; however, the airplane continued to roll left and descend, and the airplane impacted the ground in a left-wing-low attitude, resulting in substantial damage to the left wing spar, bottom fuselage, cowling, engine, landing gear, and firewall. Postaccident examination of the airplane revealed improper rigging of the ailerons. The improper rigging and improper aileron cable tensions most likely resulted in a loss of aileron control during takeoff.

Probable cause

The airplane owner's and mechanic's improper rigging and cable tension of the aileron control system, which resulted in a loss of control during takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN19LA219
Event ID
20190712X22529
Case number
CEN19LA219
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: 138c8cc827ec374749579af9f3422e61aa137bc185808400095a0603d06e1bb3; retrieved 2026-09-16T09:24:18.244Z.