FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08LA068 · Bellanca 17-30A

2 Feb 2008 · Mukilteo, WA, United States

Bellanca 17-30A · Accident: loss of engine power (total) on approach

From Seattle Paine Field International Airport (KPAE) to Seattle Paine Field International Airport (KPAE)

Report a problem

Event

NTSB case
SEA08LA068
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

Bellanca 17-30A

Aircraft type
Bellanca 17
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
N8794V
Operator
Unknown
Onboard fatalities
Unknown
Route
From Seattle Paine Field International Airport (KPAE), Mukilteo, WATo Seattle Paine Field International Airport (KPAE)
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
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)
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
Wire
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
  • Not determined › Not determined

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

NTSB narrative

While the pilot was on short-final for a touch-and-go landing, the airplane's engine lost all power. Because he was at such a low altitude, he did not have time to go through a complete restart procedure, so after switching fuel tanks, he aligned the airplane to land on a paved road that was under his approach path. While attempting to land on that road, the airplane clipped a power line and descended into the surface of the road. An inspection of the engine, fuel system, and air induction system did not reveal any system or component anomaly that would have prevented the engine from producing rated horsepower. Both the fuel tank that was selected prior to the power loss, and the fuel tank that was selected after the power loss contained sufficient fuel to maintain operation of the engine. Fuel was also found in the fuel manifold valve. The reason for the loss of power was not determined.

Probable cause

Loss of engine power while on final approach for undetermined reasons. Contributing to the accident was a power line.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA068
Event ID
20080211X00167
Case number
SEA08LA068
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. 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: d053fd9e24c5633c9ce4c0d3003f5dfc77ced58d2268dec40ca786d3fa19522e; retrieved 2026-09-15T09:21:39.145Z.