The U.S. aircraft register, updated daily
Accidents · NTSB CEN11CA677 · Final report

Piper PA-22-108 accident near Monte Vista, Colorado, September 4, 2011

On September 4, 2011 at about 11:08 pm local time, a Piper PA-22-108, registered N5934Z, was substantially damaged in an accident during landing (flare/touchdown) near Monte Vista, Colorado (Monte Vista Municipal airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's loss of control while landing, which resulted in a ground loop.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 4, 2011 · about 11:08 pm local time
Place
Monte Vista, Colorado · Monte Vista Municipal · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Piper PA-22-108 · all PA-22-108s on the register
Registration
N5934Z · registry record · serial 22-9804
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The student pilot stated that he thought that a gust of wind caught the tailwheel-equipped airplane just before touchdown, resulting in the right main landing gear wheel hitting the runway hard, which drove the wheel hub up into the strut. The airplane ground looped and nosed over, sustaining substantial damage to the right wing. After the accident, the pilot stated that, if he had recognized the wind gust sooner, he could have initiated a go-around. He also reported that, if he had known that the wheel hub broke during touchdown, he would have increased the throttle to keep the front of the airplane elevated.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Abnormal runway contact during landing (flare/touchdown) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › (general) › (general) › Pilot
  • cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
  • Environmental issues › Conditions/weather/phenomena › Wind › Gusts › Effect on operation

Pilot

  • Certificate: student
  • Ratings: single-engine land
  • Flight time: 132 hours in all; 32 in this make and model; 8 in the last 90 days; 8 in the last 30 days
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 3,360 hours
  • Last inspection: annual inspection, September 20, 2011
  • Maximum gross weight: 1,950 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming 0-235 SERIES (piston); 0 hours total

The flight

  • Departed from: MVI Monte Vista CO
  • Destination: MVI Monte Vista CO
  • Flight plan: not recorded
  • Runway 20

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.