SEA82DA094 · Piper PA-28-180
Toledo Flying Club Piper PA-28-180 · Accident: loss of engine power on approach
From Bremerton National Airport (PWT) to Grand Forks International Airport (GFK)
Event
- NTSB case
- SEA82DA094
- 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
Piper PA-28-180
- Aircraft type
- Piper PA-28
- 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
- N9544J
- Operator
- Toledo Flying Club
- Onboard fatalities
- Unknown
- Route
- From Bremerton National Airport (PWT), Bremerton, WATo Grand Forks International Airport (GFK), Grand Forks, ND
- 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 · VFR pattern final
- 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
- Loss of engine power
- 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
- Miscellaneous › Undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT BEFORE LANDING, HE TURNED THE FUEL BOOST "ON", APPLIED CARBURETOR HEAT, AND SET THE POWER AT ROUGHLY 1500 RPM. HE REPORTED THAT THE MIXTURE HAD BEEN IN THE FULL RICH POSITION DURING THE ENTIRE FLIGHT. HE ENCOUNTERED A CROSSWIND ON FINAL APPROACH AND ATTEMPTED A POWER CORRECTION. HOWEVER, THERE WAS NO ENGINE RESPONSE. SUBSEQUENTLY, THE AIRCRAFT WAS SUBSTANTIALLY DAMAGED DURING A FORCED LANDING OFF OF THE AIRPORT. NO RESTART WAS ATTEMPTED. AN INVESTIGATION REVEALED NO PRECRASH MALFUNCTION OR FAILURE OF THE AIRCRAFT OR ENGINE. HOWEVER, IT WAS NOTED THAT THE MAJORITY OF THE PILOT'S FLIGHT EXPERIENCE WAS IN A CESSNA 172. ALSO, IT WAS NOTED THAT THE MIXTURE CONTROL IN PIPER PA-28, N9544J, WAS SIMILAR TO THE CARBURETOR HEAT CONTROL IN MANY CESSNA 172 AIRCRAFT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record SEA82DA094
- Event ID
- 20020917X04101
- Case number
- SEA82DA094
- 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 1982-06-24.
- API snapshot SHA-256: 8b3de4035a174a8b3a5a5935f75259a46fe86cf80717e88560671191a2dabbf3; retrieved 2026-09-24T02:49:43.202Z.