Beech F33A accident near Mobile, Arizona, May 13, 2012
On May 13, 2012 at about 9:30 pm local time, a Beech F33A, registered N5521A, was substantially damaged in an accident during takeoff near Mobile, Arizona (Mobile Airport). It was an instructional 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 failure to maintain directional control during takeoff.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- May 13, 2012 · about 9:30 pm local time
- Place
- Mobile, Arizona · Mobile Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Beech F33A · all F33As on the register
- Registration
- N5521A · no longer on the register · serial CE-1338
- Damage
- Substantial damage
- Flight
- Instructional flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot stated that he applied takeoff power, and the airplane accelerated along the centerline of the runway. As the airplane accelerated through about 50 to 55 knots, it suddenly yawed to the left. Despite the student pilot's control inputs, the airplane continued to the left and exited the runway. Examination of the airplane's flight control system and nose wheel steering system revealed no mechanical failures or malfunctions that would have precluded normal operation.
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 takeoff
- Runway excursion during takeoff defining event
- Collision with terrain or object (not controlled flight into terrain) during takeoff
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
Pilot
- Certificate: student
- Flight time: 29 hours in all; 29 in this make and model; 29 in the last 90 days; 29 in the last 30 days; 2 as pilot in command
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 23,536 hours
- Last inspection: approved inspection programme, April 22, 2012; 51 hours since
- Maximum gross weight: 3,200 lb
- Seats: 5
- Landing gear: fixed
- Engine: Cont Motor IO-520-BB65 (piston); 0 hours total
- Operator: Airline Training Center Arizona INC
The flight
- Departed from: GYR Goodyear AZ at 8:09 pm
- Destination: GYR Goodyear AZ
- Runway 09, 4,500 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 250° at 10 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 15,000 ft
- Temperature: 102°F (39°C), dew point 30°F (-1°C)
- Altimeter: 29.87 inHg
- Observation at 9:37 pm from GYR, 19 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 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.
