FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA099 · Cubcrafters Inc CC11 160

11 Jan 2018 · Spanish Fork, UT, United States

Rocket Aviation Cubcrafters Inc CC11 160 · Accident: abrupt maneuver during landing

From Spanish Fork Municipal Airport/Woodhouse Field (SPK) to Spanish Fork Municipal Airport/Woodhouse Field (SPK)

Report a problem

Event

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

Cubcrafters Inc 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
N5923C
Onboard fatalities
Unknown
Route
From Spanish Fork Municipal Airport/Woodhouse Field (SPK), Spanish Fork, UTTo Spanish Fork Municipal Airport/Woodhouse Field (SPK), Spanish Fork, UT
Aircraft age
About 5 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
Abrupt maneuver
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 › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

According to the pilot of the tailwheel-equipped airplane, he was practicing touch-and-go takeoffs and landings on the turf adjacent to the paved runway. During the landing roll, he applied the brakes too aggressively and the airplane nosed over.

The airplane sustained substantial damage to the right-wing strut, the rudder and vertical stabilizer.

The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Probable cause

The pilot’s incorrect brake application during the landing roll, resulting in a nose over.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA099
Event ID
20180111X60741
Case number
GAA18CA099
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: 091db4beb7b124c595a2e129af6f5d6f5d7f80b43707cb3d8555ef9698bae4dc; retrieved 2026-09-16T06:16:53.986Z.