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

Beech A200 accident near Salt Lake City, Utah, July 21, 2008

On July 21, 2008 at about 8:30 pm local time, a Beech A200, registered N11, was substantially damaged in an accident during initial climb near Salt Lake City, Utah (Salt Lake City International airport). It was a public-use flight (federal) 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 failure of the landing gear motor (worn components) resulting in the partial collapse of the landing gear during landing. Contributing to the accident was the flight crew not following emergency checklist procedures to attempt a manual gear extension.

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

What the record shows

Date
July 21, 2008 · about 8:30 pm local time · cases in 2008
Place
Salt Lake City, Utah · Salt Lake City International · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech A200 · all A200s on the register
Registration
N11 · registry record · serial BD-1
Damage
Substantial damage
Flight
Public-use flight (federal) · general aviation rules (Part 91)

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

The instructor pilot stated that after takeoff and while conducting flight maneuvers, he noticed an unsafe gear indication. The three green lights were extinguished; however, the red "gear transit" light was illuminated. The landing gear visually appeared to be down. The instructor pilot recycled the landing gear, which continued to fail to lock in the extended position. The pilot returned to the airport and executed a low approach over the runway where tower personnel advised them that the landing gear appeared to be down. The crew decided to attempt a landing with the unsafe landing gear indication. After touchdown, the main landing gear partially collapsed, while the nose gear remained extended. A previous incident similar to the accident occurred 14 weeks before. During that event, the flight crew manually extended the gear per the prescribed procedures and made a successful landing. During the accident event, the flight crew did not attempt to manually lower the landing gear as directed in the (checklist). Post accident inspection of the landing gear motor and relay system found that there were worn and chipped sprocket teeth, one of the sprocket shafts was not square with the gear, and at least one of the hanger bearings was worn.

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. Electrical system malf/failure during initial climb defining event
  2. Landing gear collapse during landing (flare/touchdown)

The NTSB's findings

  • cause Aircraft › Aircraft systems › Landing gear system › (general) › Fatigue/wear/corrosion other cases naming the landing gear
  • factor Personnel issues › Action/decision › Action › Lack of action › Flight crew
  • factor Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot

Pilot (unmanned)

  • Certificate: airline transport pilot, flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 3,750 hours in all; 64 in this make and model; 73 in the last 90 days; 3,137 as pilot in command; 2,200 on instruments
  • Last flight review: June 1, 2008
  • Medical certificate: Class 2
  • Seat: rgt
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane multi-engine; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Medical certificate: Class 2
  • Injury: no injuries

The aircraft

  • Last inspection: approved inspection programme
  • Maximum gross weight: 12,500 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney PT6A-41 (turboprop); 0 hours total
  • Engine 2: Pratt & Whitney PT6A (turboprop); 0 hours total
  • Operator: Federal Aviation Administration

The flight

  • Departed from: KSLC Salt Lake City UT
  • Runway 35, 9,596 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 030° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 15,000 ft
  • Temperature: 82°F (28°C), dew point 52°F (11°C)
  • Altimeter: 30.05 inHg
  • Observation at 8:53 pm from SLC

Injuries

FatalSeriousMinorNone
Flight crew2

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

5 documents, released by the NTSB on October 27, 2009. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/LAX08GA239.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.