FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA96LA159 · Cessna A188B

16 Jul 1996 · Pullman, WA, United States

Cessna A188B · Accident: in flight collision with terrain/water while maneuvering

From Pullman-Moscow Regional Airport (PUW) to an unrecorded destination

Report a problem

Event

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

Cessna A188B

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
N9336R
Operator
Unknown
Onboard fatalities
Unknown
Route
From Pullman-Moscow Regional Airport (PUW), Pullman, WATo not recorded
Aircraft age
Not recorded
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 · aerial application
First occurrenceThe 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
In flight collision with terrain/water
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

  • Pilot in command › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot stated that he was spraying a field to the north and south with a light wind from the northwest and wind shear from different directions. He reported that as he was spraying south toward a small ridge, the airplane suddenly settled. The airplane collided with terrain, just below the top of a ridge, then it bounced and became airborne. The pilot tried to recover; however, the engine was no longer responding. The airplane then stalled and again collided with the terrain, flat on its belly. The pilot reported that there was no mechanical failure or malfunction with the airplane at the time of the accident.

Probable cause

failure of the pilot to maintain terrain clearance during a swath run. Factors relating to the accident were: unfavorable (variable) wind conditions, low airspeed, and uneven terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA96LA159
Event ID
20001208X06375
Case number
SEA96LA159
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 66012590c20fbd836ad3d3283e9dfc15a7929ab1e2f0d52b13e97d87b2004bb4; retrieved 2026-09-21T12:37:41.524Z.