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

Beech A36 accident near Topock, Arizona, December 10, 2023

On December 10, 2023 at about 10:51 pm local time, a 1975 Beech A36, registered N4171S, was substantially damaged in an accident during enroute (climb to cruise) near Topock, Arizona. It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The failure of the No. 4 connecting rod due to oil starvation, which resulted in a loss of engine power, inflight fire, and a subsequent off-airport emergency landing on rough desert terrain. Contributing to the accident was the pilot’s decision to attempt a return to the airport when closer sites were available for a forced landing.

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

What the record shows

Date
December 10, 2023 · about 10:51 pm local time
Place
Topock, Arizona · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Beech A36, built 1975 · all A36s on the register
Registration
N4171S · registry record · serial E-667
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The pilot departed on a visual flight rules, cross-country flight. ADS-B data indicated that the airplane departed the runway and made a climbing turn. During the climb, the pilot contacted air traffic control for flight following, and shortly after reported that the engine was losing oil pressure and that he was returning to the departure airport. ADS-B data showed that the airplane made a 180° turn and the airplane’s altitude began to decrease. During the return, the airplane’s altitude and ground speed continued to decrease. The pilot informed the controller that he had configured the airplane’s engine power to idle. Shortly after, radio contact with the accident airplane was lost, but the controller asked the pilot of another aircraft operating in the area to assist. The pilot of the assisting aircraft transmitted a radio call to the controller that the accident airplane’s “engine is burning up.” The pilot of the assisting aircraft attempted to visually identify the distressed airplane, and moments later spotted heavy smoke emanating from wreckage. Postaccident examination of the engine revealed a hole in the top of the crankcase above the No. 4 cylinder, and the No. 4 connecting rod and piston pin had exited the crankcase. Disassembly of the engine revealed oil starvation near the rod cap area of the I-beam. The main bearings showed normal operational signatures and the crankcase and crankshaft oil passages were unobstructed and free of foreign objects or debris. The bearing end of the I-beam showed thermal discoloration that appeared white/light grey in color, with dark grey progression emanating from the trapezoidal contour into the I-beam and flanges. The No. 4 piston connecting rod cap and connecting rod bearings were fracture separated and remnants of each were found in the oil sump. One of the connecting rod cap bolts was found lodged between the camshaft and the crankcase. The associated connecting rod cap nut and the opposite side bolt and nut were not readily identifiable; however, metallic debris consistent with the bolt and nut were found in the oil sump. Since the No. 4 connecting rod received its lubrication from the unobstructed main bearing oil passage, it is likely that the oil starvation event occurred between the main bearing and the No. 4 connecting rod bearings and the connecting rod cap. Although there were potential off-airport emergency landing locations about 4 nautical miles (nm) to the north and to the south of the accident location, the pilot chose to attempt to return to the accident airport. While the pilot managed the inflight engine failure and inflight fire, the airplane’s altitude was not sufficient to return to the airport, resulting in an off-airport emergency landing, and the airplane impacted rough desert terrain. The pilot’s autopsy revealed that he had coronary artery disease and aortic plaque. His toxicology was positive for midazolam, ketamine, and norketamine. The pilot’s coronary artery disease and aortic plaque were associated with some increased risk of an impairing or incapacitating cardiovascular event. However, there was no indication that such an impairing event occurred before the crash. There is a high probability that both midazolam and ketamine were administered during the pilot’s post-crash treatment.

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. Powerplant sys/comp malf/fail during enroute (climb to cruise) defining event
  2. Loss of engine power (partial) during enroute (climb to cruise)
  3. Loss of engine power (total) during enroute
  4. Off-field or emergency landing during enroute

The NTSB's findings

  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng oil sys › Failure
  • Aircraft › Aircraft power plant › Engine (reciprocating) › Recip engine power section › Failure
  • Environmental issues › Physical environment › Terrain › Rough terrain › Contributed to outcome

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,152.5 hours in all; 1,152.5 in this make and model
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: unk
  • Injury: fatal

The aircraft

  • Airframe total time: 7,807 hours
  • Last inspection: annual inspection, November 1, 2023
  • Maximum gross weight: 3,600 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental IO-520-BA (10 (piston); 2,856 hours total
  • Fire on the ground

The flight

  • Departed from: A20 Bullhead City AZ at 10:33 pm
  • Destination: PRC Prescott AZ
  • Flight plan: none

Weather at the time

  • Light: daylight
  • Wind: from 350° at 15 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 9°F (-13°C)
  • Altimeter: 30.21 inHg
  • Observation at 2:56 pm from KEED, 10 miles away

Weather report (METAR): METAR KEED 102156Z AUTO 35015KT 10SM CLR 18/M13 A3021 RMK AO2 SLP217 T01831128=

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

12 documents, released by the NTSB on January 14, 2026. 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.

#DocumentWhat it is
1 Pilot Logbook Excerpts PDF, 4 pages · our copy View Download
2 Maintenance Log Excerpts PDF, 5 pages · our copy View Download
3 FAA ATC Accident Package Excerpt PDF, 3 pages · our copy View Download
4 Flight radar 24 ADS-B Overlay map file · our copy Download
5 Flight radar 24 ADS-B Track Data data file · our copy Download
6 FAA Kmz File ADS-B Data map file · our copy Download
7 FAA Excel File ADS-B Data data file · our copy Download
8 Wreckage and Impact Summary PDF, 9 pages · our copy View Download
9 Engine Examination Summary PDF, 15 pages · our copy View Download
10 Toxicological Report PDF, 1 page · our copy View Download
11 Statement of Party Representatives -textron Aviation PDF, 1 page · our copy View Download
12 Release of Aircraft Wreckage PDF, 2 pages · our copy View Download

The same 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.