Cessna 185 accident near Fort Thomas, Arizona, October 22, 2010
On October 22, 2010 at about 8:50 pm local time, a Cessna 185, registered N5011X, was substantially damaged in an accident during landing (landing roll) near Fort Thomas, Arizona (Regeneration airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The airplane's encounter with a dust devil during landing rollout, which resulted in the pilot not being able to maintain directional control.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 22, 2010 · about 8:50 pm local time · cases in 2010
- Place
- Fort Thomas, Arizona · Regeneration · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 185 · all 185s on the register
- Registration
- N5011X · registry record · serial 185-0033
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot stated that after flying for about 10 minutes he made a normal traffic pattern approach and touched down on the runway. The initial rollout was without incident; however, seconds after lowering the tailwheel onto the runway surface, the airplane encountered a sudden gust of wind from the right, which was akin to a dust devil, or strong whirlwind. At this point in time, the pilot had minimal rudder authority. Despite his efforts to maintain directional control, the airplane's left wingtip contacted the runway and the airplane rolled off the runway and into a berm. During the accident sequence the outboard portion of the left wing was bent and the right wing strut was bent. The pilot indicated that he had no warning of the presence of the dust devil swirl of air. No weather reporting services are available at the airport from which the pilot took off and landed. The pilot reported that the windsock had indicated that the wind speed was between 5 and 7 knots. The pilot reported no preimpact mechanical malfunctions or failures with the airplane 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
- Other weather encounter during landing (landing roll)
- Runway excursion during landing (landing roll) defining event
- Collision with terrain or object (not controlled flight into terrain) during landing (landing roll)
The NTSB's findings
- cause Environmental issues › Conditions/weather/phenomena › Wind › Dust devil/whirlwind › Effect on operation
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Attain/maintain not possible
Pilot
- Certificate: commercial pilot
- Ratings: single-engine land; single-engine sea; instrument: airplane
- Flight time: 1,107 hours in all; 28 in this make and model; 17 in the last 90 days; 11 in the last 30 days; 954 as pilot in command
- Last flight review: August 30, 2010
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,675 hours
- Last inspection: annual inspection, July 1, 2010; 14 hours since
- Maximum gross weight: 3,525 lb
- Seats: 4
- Landing gear: fixed
- Engine: Cont Motor IO-520-D (piston); 0 hours total
The flight
- Departed from: 5AZ9 Fort Thomas AZ at 8:40 pm
- Destination: 5AZ9 Fort Thomas AZ
- Flight plan: none
- Runway 17, 3,000 ft by 50 ft
Weather at the time
- Light: daylight
- Visibility: 10 statute miles
- Sky: a few clouds at 8,000 ft
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
1 document, released by the NTSB on November 22, 2010. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Other NTSB records under N5011X the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N5011X on the register today · the tail number may have moved to another aircraft since
- Cessna 185 Skywagon 228 registered today · the model family and its accident history
- Cessna 72,677 aircraft on the register
- Engine: Cont Motor IO-520-D 95 aircraft carry this series today · as the NTSB recorded it
- Regeneration Airport · nearest airport
- Accidents and incidents in Arizona 2,985 since 1982 · 466 in the last ten years
- Arizona 8,435 aircraft registered
- Other NTSB records under N5011X 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/WPR11CA024.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.
