CEN20LA173 · Titan TITAN TORNADO S Undesignat
Titan TITAN TORNADO S Undesignat · Accident: flight control system malfunction/failure en route
From Haskell Airport (2K9) to Haskell Airport (2K9)
Event
- NTSB case
- CEN20LA173
- 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
- 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
Titan TITAN TORNADO S Undesignat
- Aircraft type
- Titan TORNADO
- 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
- N318WH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Haskell Airport (2K9), Haskell, OKTo Haskell Airport (2K9), Haskell, OK
- Aircraft age
- About 5 years (built 2015)
- 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
- En route · climb to cruise
- 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 structures
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot departed on a flight in a kit-built airplane to test the winglets he had recently installed on the airplane’s stabilator, which were intended to eliminate the airplane’s uncommanded yaw. The flight was the airplane's first winglet test flight away from the airport traffic pattern and at a higher altitude. The student stated that during the flight, he decreased the pitch attitude to level off at 2,000 ft above ground level and the airplane suddenly vibrated aggressively and it "felt like the tail was thumping." He decreased the engine power, but the thumping and vibrating continued, so the pilot pitched the airplane down for an off-field emergency landing. Before he was able to land, the airplane rolled inverted and descended into the trees, resulting in the separation of the right wing. Postaccident examination revealed that the stabilator control horn had fractured due to overstress and separated from the push-pull tube. According to an airplane kit manufacturer engineer, winglets added to the stabilator produce flutter. Based on the evidence, it is likely that the winglets led the stabilator to flutter, which overstressed the stabilator control horn and resulted in the control horn’s failure.
Probable cause
The student pilot/builder’s addition of winglets to the stabilator, which resulted in flutter and overstress failure of the stabilator control horn.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20LA173
- Event ID
- 20200509X11853
- Case number
- CEN20LA173
- 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: 5fd72578defb0048ad84810ec5baf4fc1b3eef4e2972abb6c52bf3da9ff3d33f; retrieved 2026-09-16T11:34:23.927Z.