WPR22LA036 · Cubcrafters CC11-160
Cubcrafters CC11-160 · Accident: collision during takeoff/landing
Event
- NTSB case
- WPR22LA036
- 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
- Event fatalities
- Unknown
- 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
Cubcrafters CC11-160
- Aircraft type
- Cubcrafters CC11
- 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
- N2YQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 8 years (built 2013)
- 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
- Collision during takeoff/landing
- 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 the tailwheel equipped airplane reported that, he was performing practice touch-and-go takeoffs and landings on a narrow dirt airstrip. The pilot made two uneventful short-field landings and after touchdown on the third landing, while on the landing roll, the airplane began to veer to the right. The pilot added brake pressure to realign the airplane back to the center of the airstrip and away from the adjacent v-ditch. Despite the pilot’s efforts, the airplane slid into the v-ditch and nosed over coming to rest inverted. The wing strut and rudder were substantially damaged. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s failure to maintain directional control during the landing roll, which resulted in the airplane veering into a ditch and nosing over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22LA036
- Event ID
- 20211118104259
- Case number
- WPR22LA036
- 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, cause areas. 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: 2a9a7778792efc3ba73b9f799c9ac375016290746606c05461340a42e1740ab9; retrieved 2026-09-16T14:45:10.299Z.