Piper PA-34-200T accident near Walden, Colorado, January 1, 2007
On January 1, 2007 at about 10:30 pm local time, a Piper PA-34-200T, registered N821GS, was substantially damaged in an accident near Walden, Colorado. It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot experiencing lateral flight control stiffness for undetermined reasons and the pilot's intentional wheels up landing. Factors were the snow covered and rough/uneven terrain.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- January 1, 2007 · about 10:30 pm local time
- Place
- Walden, Colorado · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-34-200T · all PA-34-200Ts on the register
- Registration
- N821GS · no longer on the register · serial 34-7770419
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was in cruise flight at 12,500 feet. The pilot told his wife that he was disengaging the autopilot to maneuver over the mountains. He then pressed the trim-disengage button on the control yoke. Shortly after, the airplane began rolling uncontrollably to the left and right. The pilot steadied the airplane with the rudder. He then began a 1/2 standard rate left turn. When he went to roll the airplane right, he said that the flight controls were difficult to manipulate. He attempted additional turns and found the problem continued. The pilot changed airspeed and found the problem increased with reduced airspeed. After that, he declared an emergency with air traffic control, began a descent, and proceeded to the nearest airport. The pilot said he was unable to locate the airport so he elected to perform a wheels up landing on a snow-covered field. During the landing, the airplane sustained substantial damage to the inboard left wing and the bottom left side of the forward fuselage. An examination of the airplane revealed no anomalies that could explain the stiff controls.
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
Crew member
- Certificate: private
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 100 hours in all; 50 in this make and model
- Injury: no injuries
The aircraft
- Landing gear: retractable
- Engine: Continental TSIO-360 (piston); 0 hours total
The flight
- Departed from: GXY Greeley CO
- Destination: RKS Rock Springs WY
- Flight plan: VFR
Weather at the time
- Light: daylight
- Wind: from 350° at 3 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 14°F (-10°C), dew point 7°F (-14°C)
- Altimeter: 30.12 inHg
- Observation at 3:53 pm from LAR
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 | |||
| Passengers | 3 |
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.
