FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA94FA154 · Cessna 172

21 Jun 1994 · Port Angeles, WA, United States

Cessna 172 · Accident: total loss of engine power (mechanical failure) en route

From an unrecorded airport to Bowerman Airport (HQM)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's fatalities. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
SEA94FA154
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
1 · all aircraft and ground Possible conflict
Ground fatalities
0
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 172

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
N8025B
Operator
Brown, Charles E. · private individual
Onboard fatalities
Unknown
Route
From not recordedTo Bowerman Airport (HQM), Hoquiam, WA
Aircraft age
Not recorded
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
En route · cruise
First occurrenceThe 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
Total loss of engine power (mechanical failure)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Engine assembly, connecting rod › Failure, total
  • Fluid, oil › Lack of

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE STUDENT PILOT REPORTED THAT DURING A CROSS COUNTRY FLIGHT, THE ENGINE LOST POWER AND THAT THERE WAS AN INDICATION OF A LOSS OF OIL PRESSURE. DURING THE FORCED LANDING, THE AIRPLANE COLLIDED WITH ROUGH TERRAIN. DURING AN ENGINE INSPECTION, IT WAS FOUND THAT THE NUMBER SIX CONNECTING ROD BROKE DUE TO AN UNDETERMINED OIL EXHAUSTION/STARVATION OCCURRENCE.

Probable cause

LACK OF OIL AND CONNECTING ROD FAILURE. A FACTOR TO THE ACCIDENT WAS ROUGH/UNEVEN TERRAIN.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA94FA154
Event ID
20001206X01610
Case number
SEA94FA154
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: bbe3955cd8f98de40acf5f0068a5fb49f8d66140189d930ec21687b972815c57; retrieved 2026-09-21T00:06:32.132Z.