FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08LA083 · Cessna 180

26 Feb 2008 · Moab, UT, United States

Cessna 180 · Accident: loss of control on ground during landing

From Canyonlands Regional Airport (KCNY) to Canyonlands Regional Airport (KCNY)

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
SEA08LA083
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 180

Aircraft type
Cessna 180
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
N1732C
Operator
Unknown
Onboard fatalities
Unknown
Route Narrative disagrees
From Canyonlands Regional Airport (KCNY), MOab, UTTo Canyonlands Regional Airport (KCNY)
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 · flare/touchdown
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

During one of a series of three-point landings in a tail wheel-equipped airplane, the airplane bounced and then veered to the right during the flare/touchdown phase of the landing sequence. The pilot was unable to keep it from going further to the right, and as it continued to veer to the right of the runway heading, the left main gear leg collapsed, resulting in damage to the fuselage structure. There were no malfunctions or anomalies in the airplane's flight control or tail wheel steering systems. The pilot said that he felt he needed more extensive training in the Cessna 180 and that he should not have attempted a three-point landing in that model airplane until he had completed that training.

Probable cause

The pilot's failure to maintain directional control of the tail wheel-equipped airplane during the flare/touchdown phase of a three-point landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA083
Event ID
20080403X00424
Case number
SEA08LA083
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: 6a8fd89df80a9a9507aa01d1a8809c7b339ed082a1500736357add049d6d20aa; retrieved 2026-09-15T09:29:18.449Z.