FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA16CA027 · Cessna A188A A

24 Oct 2015 · Elberta, UT, United States

Rooster Aviation Cessna A188A A · Accident: loss of control in flight while maneuvering

From U77 · Spanish Fork, UT to U77 · Spanish Fork, UT

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's damage. Values are shown as recorded, not corrected; compare with the narrative.

Event

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

Cessna A188A A

Aircraft type
Cessna 188
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
N4401Q
Onboard fatalities
Unknown
Route
From U77 · Spanish Fork, UTTo U77 · Spanish Fork, UT
Aircraft age
About 45 years (built 1970)
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 137: Agricultural
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
Maneuvering · low-altitude flying
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 in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial Narrative disagrees

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • 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 during an aerial application flight in rolling hills in a canyon, the canyon wind forced the airplane to the ground. The airplane impacted terrain, the pilot egressed from the cockpit without further incident, and a postcrash fire occurred. The airplane was destroyed in the postcrash fire.

The pilot reported there were no pre-impact mechanical failures or malfunctions with the airframe or engine that would have precluded normal operation.

Probable cause

The pilot's failure to compensate for wind while maneuvering at a low altitude, resulting in a collision with terrain and a postcrash fire.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA16CA027
Event ID
20151026X02502
Case number
GAA16CA027
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: 23634226dfb498d0cc7d657e203280b1ba860f0227c5959825c2e7eafe75ec35; retrieved 2026-09-16T02:55:17.598Z.