FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR10CA291 · Cessna 188B

13 Jun 2010 · Blackfoot, ID, United States

Vector Disease Control Cessna 188B · Accident: loss of control on ground during landing

From Mccarley Field (KU02) to Mccarley Field (KU02)

Report a problem

Event

NTSB case
WPR10CA291
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 188B

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
N9357K
Onboard fatalities
Unknown
Route
From Mccarley Field (KU02), Blackfoot, IDTo Mccarley Field (KU02), Blackfoot, ID
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 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
Loss of control on ground
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
  • Aircraft › Aircraft systems

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

NTSB narrative

The pilot stated that he was returning from an aerial application practice flight, in a tailwheel-equipped airplane, to practice wheel only touch-and-go takeoffs and landings. The first four landings were uneventful. During the fifth and final landing, the airplane touched down and bounced approximately one foot into the air. The airplane stabilized and the main wheels touched down for a second time. As the tail wheel touched down approximately two-thirds down the runway, it started to shimmy “violently” and the airplane veered to the left. The pilot corrected the airplane back to the right. The intensity of the shimmy increased and despite the pilot’s control inputs, the airplane exited the right side of the runway and ground looped. The airplane’s left wing was substantially damaged. Post-accident examination of the tail wheel assembly revealed wear on the locking mechanism. Additionally, “snake-like” skid marks were found on the runway that appeared to be the result of a tail wheel shimmy.

Probable cause

A loss of directional control during the landing roll as a result of a worn tail wheel locking mechanism.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR10CA291
Event ID
20100614X33726
Case number
WPR10CA291
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2010-06-14.
  • API snapshot SHA-256: 64587ef815b0cc50b5a6c68718adff8290d30de43ea741f1b2a9aee718898275; retrieved 2026-09-15T14:26:58.441Z.