FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08CA186 · Cessna 140A

16 Aug 2008 · Lowman, ID, United States

Cessna 140A · Accident: loss of control on ground during landing

From Idaho City US Forest Service Airport (U98) to Warm Springs Creek Airport (0U1)

Report a problem

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

Event

NTSB case
SEA08CA186
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 140A

Aircraft type
Cessna 140
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
N1161D
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From Idaho City US Forest Service Airport (U98), Idaho city, IDTo Warm Springs Creek Airport (0U1), Lowman, 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

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

NTSB narrative

After touching down on the grass/turf airstrip in a tailwheel equipped airplane, the pilot failed to maintain directional control. As the pilot was attempting to regain control of the airplane, it ground looped, resulting in the collapse of one of the main landing gear legs. In addition to the collapse of the landing gear leg, the accident sequence resulted in the bending of internal structure of the right wing. According to the pilot, there were no issues with the flight controls or the tail wheel steering system.

Probable cause

The pilot's failure to maintain directional control during the landing roll.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08CA186
Event ID
20080908X01412
Case number
SEA08CA186
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: e863158765d9756ebd2d49a18fcf49f7369c17564c91e024f7780a1ec5d44e06; retrieved 2026-09-15T10:10:43.248Z.