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

Cessna 172 accident near Wilcox, Arizona, February 2, 2013

On February 2, 2013 at about 11:30 pm local time, a Cessna 172, registered N1421V, was substantially damaged in an accident during enroute near Wilcox, Arizona (Benson Municipal 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 loss of engine power for reasons that could not be determined because postaccident examination did not reveal any abnormalities that would have precluded normal operation.

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

What the record shows

Date
February 2, 2013 · about 11:30 pm local time
Place
Wilcox, Arizona · Benson Municipal Airport · map
Type
Accident
Injuries
No one was hurt; 3 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 M · all 172s on the register
Registration
N1421V · no longer on the register · serial 17263566
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot reported that during a cross-country flight, the engine lost power. Despite his efforts, the pilot was unable to restart the engine and initiated a forced landing in rough terrain. During the off airport landing, the airplane nosed over. Postaccident examination of the airframe fuel system and engine run revealed no evidence of mechanical malfunctions or failures 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

  1. Loss of engine power (total) during enroute defining event
  2. Nose over/nose down during landing (flare/touchdown)

The NTSB's findings

  • cause Not determined › Not determined › (general) › (general) › Unknown/Not determined
  • Environmental issues › Physical environment › Terrain › Rough terrain › Not specified

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 800 hours in all; 160 in this make and model; 17 in the last 90 days; 7 in the last 30 days; 800 as pilot in command
  • Last flight review: March 6, 2012
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 8,230 hours
  • Last inspection: annual inspection, September 3, 2012
  • Maximum gross weight: 2,200 lb
  • Seats: 4
  • Landing gear: retractable
  • Engine: Lycoming O-360 (piston); 0 hours total

The flight

  • Departed from: P13 Globe AZ at 10:00 pm
  • Destination: Benson AZ
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 140° at 4 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 66°F (19°C), dew point 21°F (-6°C)
  • Altimeter: 30.20 inHg
  • Observation at 10:00 pm from P13, 54 miles away

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers2

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.