Piper PA28 accident near Tat Momoli, Arizona, August 29, 2018
On August 29, 2018 at about 1:40 am local time, a 1998 Piper PA28, registered N4139A, was substantially damaged in an accident during enroute (cruise) near Tat Momoli, Arizona. 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
A total loss of engine power due to a fatigue crack in the connecting rod bushing end.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- August 29, 2018 · about 1:40 am local time
- Place
- Tat Momoli, Arizona · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Piper PA28 181, built 1998 · all PA28s on the register
- Registration
- N4139A · no longer on the register · serial 2843115
- 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 the cross-country flight, the engine experienced a total loss of power. The pilot initiated a forced landing to a nearby road where, during the landing roll, the airplane impacted a barbed wire fence, resulting in substantial damage to the right wing. Postaccident examination revealed a large hole in the engine case at the No. 4 cylinder that exposed the crankshaft and connecting rod. The No. 4 cylinder was seized, and the connecting rod was fractured at the piston end. Further examination revealed that the connecting rod fractured from a fatigue crack in the bore on the piston end, which likely initiated at an internal corner of the bore. The fatigue crack progressed through most of the pin bore cross-section. Following the fracture of the connecting rod, the continued movement of the broken part led to subsequent overstress fractures and damage to nearby components, which resulted in catastrophic engine failure and a complete seizure of the engine. The cause of the fatigue crack initiation could not be determined, as both the initiation site (or sites) and the termination of the fatigue crack were destroyed by postfracture impact damage. The general location of the initiation, the internal corner of the pin bore, suggested the presence of concentrated stress in that location, which could have been the result of a material defect, such as a pore, inclusion, or corrosion pit that may have occurred when the connecting rod was rebushed. A crack initiation could also have been the result of improper sizing of the internal bushing, improper installation of the connecting rod, or use of the wrong parts. The engine was overhauled 42 flight hours before the accident.
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
- Powerplant sys/comp malf/fail during enroute (cruise) defining event
- Loss of engine power (total) during enroute (cruise)
- Collision during takeoff/land during landing (landing roll)
The NTSB's findings
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › Recip eng cyl section › Fatigue/wear/corrosion
- cause Aircraft › Aircraft power plant › Engine (reciprocating) › (general) › Failure
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 307 hours in all; 0 in this make and model
- Last flight review: October 28, 2016
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
The aircraft
- Airframe total time: 5,510.3 hours
- Last inspection: 100-hour inspection, March 1, 2018; 42 hours since
- Maximum gross weight: 2,558 lb
- Seats: 4
- Landing gear: fixed
- Engine: Lycoming Engines O-360-A4M (piston); 1,606 hours total
The flight
- Departed from: OLS Nogales AZ
- Destination: VNY Van Nuys CA
- Flight plan: none
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 360° at 5 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 99°F (37°C), dew point 52°F (11°C)
- Altimeter: 29.84 inHg
- Observation at 1:56 am, 14 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
10 documents, released by the NTSB on September 11, 2020. 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 | Materials Laboratory Factual Report | PDF, 13 pages | View Download |
| 2 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 3 | FAA Engine Examination Report | PDF, 3 pages | View Download |
| 4 | Examination Report, Piper Aircraft Company | PDF, 4 pages | View Download |
| 5 | Airframe Logbook | PDF, 4 pages | View Download |
| 6 | Engine Logbook | PDF, 1 page | View Download |
| 7 | Engine Overhaul Records Excerpts | PDF, 14 pages | View Download |
| 8 | Statement of Party Representatives to NTSB Investigation | PDF, 1 page | View Download |
| 9 | Release of Aircraft Wreckage, NTSB Form 6120.15 | PDF, 1 page | View Download |
| 10 | Accident Photographs | PDF, 5 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
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.
