Cessna 172N accident near Gila Bend, Arizona, March 17, 2013
On March 17, 2013 at about 6:50 pm local time, a Cessna 172N, registered N5802J, was substantially damaged in an accident during approach (VFR go-around) near Gila Bend, Arizona (Gila Bend Municipal airport). It was a personal flight under general aviation rules (Part 91). 1 person had minor injuries. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The student pilot's failure to maintain airplane control during an attempted go-around.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- March 17, 2013 · about 6:50 pm local time
- Place
- Gila Bend, Arizona · Gila Bend Municipal · map
- Type
- Accident
- Injuries
- 1 person had minor injuries.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 172N · all 172Ns on the register
- Registration
- N5802J · no longer on the register · serial 17273839
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The student pilot reported that while he was attempting to land the airplane, it drifted left, and he decided to execute a go-around. During the go-around, the airplane struck a tree located left of the runway then impacted the ground. Postaccident examination revealed substantial damage to the engine firewall and wings. The student 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
- Controlled flight into terrain or object (CFIT) during approach (VFR go-around) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Heading/course › Not attained/maintained
- cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Student pilot
- Environmental issues › Physical environment › Object/animal/substance › Tree(s) › Effect on operation
Dual student
- Certificate: student
- Ratings: single-engine land
- Flight time: 41 hours in all; 41 in this make and model; 34 in the last 90 days; 10 in the last 30 days; 4 as pilot in command
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: minor injuries
The aircraft
- Airframe total time: 16,114 hours
- Last inspection: annual inspection, February 7, 2013
- Maximum gross weight: 2,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming O-320 SERIES (piston); 0 hours total
The flight
- Departed from: TUS Tucson AZ at 5:15 pm
- Destination: E63 Gila Bend AZ
- Flight plan: VFR
- Runway 22, 5,200 ft by 75 ft
Weather at the time
- Light: daylight
- Wind: from 280° at 11 knots, gusting 15
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 82°F (28°C), dew point 27°F (-3°C)
- Altimeter: 29.87 inHg
- Observation at 6:55 pm from KGXF, 5 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.
Other NTSB records under N5802J the same tail number, which may have belonged to a different aircraft at the time
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.