FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA16FA316 · Cessna A188 A

16 Sept 2016 · Alapaha, GA, United States

Cessna A188 A · Accident: loss of control in flight while maneuvering

From Berrien County Airport (4J2) to Berrien County Airport (4J2)

Report a problem

Event

NTSB case
ERA16FA316
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
1 · 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 A188 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
N3547Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Berrien County Airport (4J2), Nashville, GATo Berrien County Airport (4J2), Nashville, GA
Aircraft age
About 47 years (built 1969)
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
Destroyed

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 commercial pilot had completed one aerial application flight on the morning of the accident and planned to complete two additional flights. Using his trailer-based fuel tank, the pilot refueled the airplane to full, and his ground assistant added a mixture of chemicals and water to the airplane's hopper. The flight departed, and about 20 minutes later, two witnesses reported that they heard an airplane flying back and forth near their property until the engine noise went silent, which was followed by the sound of an impact. The accident site was in an open, plowed-dirt field that bordered the cotton field being sprayed.

Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures. The damage to the wings, fuselage, and empennage were consistent with the airplane having been in a left spin at ground impact. Although dirt was found in the throttle-body metering unit filter, there was no dirt or other debris found upstream or downstream within the fuel system. Therefore, it is unlikely that the dirt affected engine operation, as it was most likely introduced during the impact. Further, the propeller separated from the engine and exhibited chord-wise scratching and s-bending, all of which were consistent with the engine producing power at the time of impact. Postaccident examination of the pilot's fuel source revealed no contamination, and although a small sample was discolored, the pilot was aware of the discoloration, and would pump fuel through the hose until the color returned to a normal 100LL color.

It is likely that the pilot proceeded from his base airport directly to the cotton field, which was the smaller of the two fields he intended on spraying during the accident flight. This was contrary to what the pilot normally did, which was to spray larger fields first to lighten the load before proceeding to smaller fields. The airplane's flight manual cautioned that the use of very low airspeeds in combination with heavy loads "reduces the margin of safety." It is likely that, while maneuvering at a low altitude over the smaller field with a heavy load, the pilot failed to maintain adequate airspeed, and the airplane exceeded its critical angle-of-attack and entered an aerodynamic stall and spin.

The cetirizine identified during toxicology testing was likely well below the lower therapeutic limit, and it is unlikely to have had any effects on the pilot at the time of the accident. The carbon monoxide identified during toxicology testing was most likely from the postimpact fire, and, as a result, did not contribute to the accident.

Probable cause

The pilot's failure to maintain adequate airspeed while maneuvering at low altitude during aerial application operations, which resulted in the airplane exceeding its critical angle-of-attack and entering an aerodynamic stall and spin.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA16FA316
Event ID
20160916X12503
Case number
ERA16FA316
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: f16af4cbcf88c5446cf1bcc4434da1919c594be8eb8bed68d3114d171a4a019a; retrieved 2026-09-14T22:00:15.953Z.