Cessna 170B accident near Mobile, Arizona, November 28, 2002
On November 28, 2002 at about 3:30 pm local time, a Cessna 170B, registered N4465B, was substantially damaged in an accident near Mobile, Arizona (Private Strip 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 improper compensation for the crosswind conditions at touchdown and failure to maintain proper alignment of the tail wheel equipped airplane during landing, which resulted in a ground loop. The crosswind was a contributory factor.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- November 28, 2002 · about 3:30 pm local time
- Place
- Mobile, Arizona · Private Strip · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 170B · all 170Bs on the register
- Registration
- N4465B · registry record · serial 26809
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane ground looped and nosed over while the pilot was performing touch-and-go practice takeoffs and landings at an abandoned gravel airstrip. While on approach, the pilot configured the airplane in a crab to the right, in an effort to counteract the right-quartering crosswind. On final approach, about 15 feet above ground level, the crosswind diminished. The airplane touched down on the runway surface while still in the right crab, with the right main landing gear making contact first. The airplane veered to the left, off the edge of the runway and the main landing gear impacted a dirt berm, resulting in a nose over. The airplane came to rest inverted. The pilot reported no pre impact mechanical malfunctions or failures with the airplane.
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
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 180 hours in all; 37 in this make and model
- Last flight review: November 27, 2002
- Medical certificate: Class 3 (valid medical--w/ waivers/lim.)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,751.7 hours
- Last inspection: annual inspection, September 10, 2002; 2.1 hours since
- Maximum gross weight: 2,200 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-300-A (piston); 0 hours total
The flight
- Departed from: GYR Goodyear AZ at 2:30 pm
- Destination: Mobile AZ
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 070° at 15 knots
- Visibility: 10 statute miles
- Sky: a few clouds at 16,000 ft
- Temperature: 66°F (19°C), dew point 34°F (1°C)
- Altimeter: 30.20 inHg
- Observation at 4:56 pm from PHX, 30 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| 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.