SEA83LA067 · Cessna 150G
Cessna 150G · Accident: total loss of engine power (non-mechanical) on approach
From Hogan's Corner Airport (5WA8) to Bremerton National Airport (PWT)
Event
- NTSB case
- SEA83LA067
- 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
- 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 150G
- Aircraft type
- Cessna 150
- 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
- N3355J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hogan's Corner Airport (5WA8), Ocean Shores, WATo Bremerton National Airport (PWT), BREWERTON, 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
- Approach
- 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 (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel exhaustion
- 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
- Fluid, fuel › Exhaustion
- Pilot in command › Fuel supply, not maintained
- Pilot in command › In-flight planning/decision, improper
- Pilot in command › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRCRAFT COLLIDED WITH A TREE STUMP DURING A FORCED LANDING AFTER THE ENGINE QUIT DURING ENTRY INTO THE TRAFFIC PATTERN. WHEN THE ENGINE STOPPED THE PILOT FELT HE COULD NOT MAKE THE AIRPORT AND CHOSE A FIELD TO LAND IN TO AVOID TREES ON THE FINAL APPROACH TO THE AIRPORT. DURING THE LANDING ROLLOUT, THE ACFT HIT A TREE STUMP AND NOSED OVER. INVESTIGATION SHOWED THE RIGHT FUEL TANK WAS EMPTY AND THE LEFT TANK CONTAINED ABOUT ONE GALLON OF FUEL. THE PILOT SAID HE THOUGHT THE ACFT HAD LONG RANGE FUEL TANKS. THOSE TANKS PROVIDE ABOUT 12 MORE GALLONS OF FUEL. THEY WERE NOT INSTALLED IN THIS ACFT. THE ACCIDENT ACFT HAD FLOWN ABOUT 4 HOURS AFTER IT WAS RETURNED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA83LA067
- Event ID
- 20001214X42568
- Case number
- SEA83LA067
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1983-03-21.
- API snapshot SHA-256: 5950f4c8761dbaa2f715db9a2148f086eb2f7c7d1e79f467f28c9b2f30cc2d58; retrieved 2026-09-21T17:59:44.095Z.