Piper PA-32-300 accident near Prescott Valley, Arizona, October 31, 2024
On October 31, 2024 at about 11:20 pm local time, a 1969 Piper PA-32-300, registered N154DC, was substantially damaged in an accident during enroute near Prescott Valley, Arizona (Prescott Rgnl/Ernest A Love Fl airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
Separation of the No. 3 engine cylinder due to a loss of torque on the cylinder base nuts, which resulted in a loss of engine power and in-flight fire. Contributing to the accident was maintenance personnel’s failure to ensure the engine case and cylinder base nuts were properly torqued during the most recent annual inspection.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 31, 2024 · about 11:20 pm local time · cases in 2024
- Place
- Prescott Valley, Arizona · Prescott Rgnl/Ernest A Love Fl · cases near this airport · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA-32-300, built 1969 · all PA-32-300s on the register
- Registration
- N154DC · registry record · serial 32-40599
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot was conducting a local flight to try to replicate a fuel mixture leaning problem he experienced on the previous flight. The pilot experienced the leaning issues again and recognized unusual exhaust gas temperature (EGT) and fuel flow readings during the flight, so he elected to return to the airport. During the return to the airport the pilot heard two loud “booms” before the engine lost total power. Shortly after, smoke and flames appeared inside the cabin near the forward right floorboard. The pilot successfully extinguished the fire and performed a forced landing to an open field. The forward right area of the fuselage was substantially damaged. Examination of the engine revealed the No. 3 cylinder had separated from the engine case; the No. 3 connecting rod had fractured and mechanical damage was found to the engine case, camshaft, and crankshaft. Five of the eight No. 3 cylinder base nuts were not located. The examination revealed signs of fretting between both engine case halves, as well as on each of the six cylinder’s hold-down plates, consistent with a loss of torque of the engine case nuts and bolts and the cylinder base nuts. No other pre-impact anomalies were noted with the engine. Damage to the engine was consistent with the No. 3 cylinder base nuts losing their torque and the nuts coming off the studs, which enabled the cylinder barrel to come off the cylinder piston, resulting in mechanical damage to the studs, No. 3 connecting rod, engine case, camshaft, and crankshaft. The damage resulted in a fire originating in the engine compartment. Although the investigation did not determine why there was a loss of torque of the engine case nuts and bolts or the cylinder base nuts, the engine had operated about 72 hours since undergoing an annual inspection. FAA guidance for an annual inspection includes an inspection for visual evidence of excessive oil, fuel, or hydraulic leaks, and sources of such leaks, and directs inspection of engine studs and nuts for improper torquing. Accordingly, any improperly torqued engine studs or nuts should have been identified by the annual inspection.
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
- Loss of engine power (total) during enroute defining event
- Off-field or emergency landing during enroute
- Fire/smoke (non-impact) during enroute
The NTSB's findings
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Failure other cases naming the engine
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Attain/maintain not possible
- Personnel issues › Task performance › Inspection › Scheduled/routine inspection › Maintenance personnel
- Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Incorrect service/maintenance other cases naming the engine
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 208 as pilot in command
- Last flight review: November 17, 2023
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 4,624 hours
- Last inspection: annual inspection, June 27, 2024; 72 hours since
- Seats: 6
- Landing gear: fixed
- Engine: Lycoming TI0-540 SER (piston); 1,169 hours total
The flight
- Departed from: PRC Prescott AZ
- Flight plan: none
Weather at the time
- Light: daylight
- Wind: from 180° at 8 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 61°F (16°C), dew point 9°F (-13°C)
- Altimeter: 24.95 inHg
- Observation at 4:53 pm from PRC, 7 miles away
Weather report (METAR): 4:53 PM 61 °F 9 °F 13 % S 8 mph 0 mph 24.95 in 0.0 in Fair
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 6 pictures from the NTSB's docket, as the NTSB released them
Photograph 1 – Airplane Wreckage on Scene
Photograph 2 – Damage to Airplane
Photograph 3 – Cockpit Damage
Photograph 4 – Engine Damage
Photograph 5 - Internal view of left and right engine case halves, highlighting fretting to forward section of each case half
Photograph 6 - Photos showing fretting to each cylinder hold down plateThe NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on December 10, 2025. 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 Written Statement | PDF, 5 pages | View Download |
| 2 | Record of Conversation - Pilot | PDF, 1 page | View Download |
| 3 | Incident Occurrence Sheet | PDF, 1 page | View Download |
| 4 | Wreckage Examination Report | PDF, 13 pages | View Download |
| 5 | Maintenance Records - Engine | PDF, 2 pages | View Download |
| 6 | Photos | PDF, 7 pages · our copy | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Connections how this case links to the rest of the register
- N154DC on the register today · the tail number may have moved to another aircraft since
- Piper PA-32 Cherokee Six, Lance and Saratoga 3,916 registered today · the model family and its accident history
- Piper 44,840 aircraft on the register
- Engine: Lycoming TI0-540 SER 5,075 aircraft carry this series today · as the NTSB recorded it
- Prescott Rgnl/Ernest A Love Field · nearest airport
- Accidents and incidents in Arizona 2,985 since 1982 · 466 in the last ten years
- Arizona 8,433 aircraft registered
The whole map of how records connect · these connections as data: /graph/accident/WPR25LA030.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.
