Piper PA-22-150 accident near Anchorage, Alaska, May 29, 2010
On May 29, 2010 at about 5:45 am local time, a Piper PA-22-150, registered N5844D, was substantially damaged in an accident during landing (landing roll) near Anchorage, Alaska (Bold Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain directional control during the landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 29, 2010 · about 5:45 am local time
- Place
- Anchorage, Alaska · Bold Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-22-150 · all PA-22-150s on the register
- Registration
- N5844D · no longer on the register · serial 22-4523
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was landing on runway 14 when the accident occurred. He stated that during the landing, the airplane veered to the left and the left wing tip struck a tree. The airplane rotated to the left, and the right main landing gear collapsed. The right wing and horizontal stabilizer impacted the ground, resulting in substantial damage. The pilot verified that there were no mechanical anomalies with the airplane prior to the accident.
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
- Loss of control on ground during landing (landing roll) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 130 hours in all; 18 in this make and model; 5 in the last 90 days; 5 in the last 30 days; 87 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Injury: no injuries
The aircraft
- Airframe total time: 2,376 hours
- Last inspection: annual inspection, July 1, 2009
- Maximum gross weight: 2,000 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: MRI Anchorage AK
- Destination: A13 Anchorage AK
- Flight plan: none
- Runway 14, 1,000 ft by 15 ft
Weather at the time
- Light: daylight
- Wind: from 140° at 7 knots
- Visibility: 10 statute miles
- Sky: broken clouds at 11,000 ft
- Temperature: 63°F (17°C), dew point 36°F (2°C)
- Altimeter: 30.03 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
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.