WPR18LA181 · Cessna 172S S
Cessna 172S S · Accident: loss of engine power (total) while maneuvering
From Phoenix Deer Valley Airport (DVT) to Phoenix Deer Valley Airport (DVT)
Event
- NTSB case
- WPR18LA181
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172S S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N154ME
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo Phoenix Deer Valley Airport (DVT), Phoenix, AZ
- Aircraft age
- About 18 years (built 2000)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Maneuvering
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of engine power (total)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While maneuvering during a local instructional flight, the engine began running rough, and the instructor decided to return to the airport. The engine subsequently lost total power and the propeller stopped rotating. The instructor performed a forced landing to a clearing where the airplane nosed over, resulting in substantial damage. Examination of the engine revealed that the crankshaft was fractured at the No. 4 connecting rod journal. The fracture surface was flat and crack arrest lines were consistent with a fatigue fracture which initiated subsurface. No flaws or embedded particles were observed at the site of the fatigue initiation. The engine was overhauled about 3 years before the accident and had accumulated 2,798 hours of operation since the overhaul.
Probable cause
A total loss of engine power due to crankshaft failure as the result of a subsurface fatigue crack.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA181
- Event ID
- 20180626X55142
- Case number
- WPR18LA181
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: aadb3f13bf3fe1bc925852ffef193cb8dd3c10dc8dfa83b04a502e2678f75069; retrieved 2026-09-16T07:41:02.698Z.