SEA94LA223 · Cessna 320B
Cessna 320B · Accident: partial loss of engine power (non-mechanical) during takeoff
From an unrecorded airport to King County International Airport - Boeing Field (BFI)
Event
- NTSB case
- SEA94LA223
- 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 320B
- Aircraft type
- Cessna 320
- 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
- N9833L
- Operator
- Knoll, Ronald K. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo King County International Airport - Boeing Field (BFI), Seattle, 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
- Takeoff
- 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
- Partial 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 starvation
- 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
- Fluid, fuel › Starvation
- Pilot in command › Fuel tank selector position, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
In a written statement, the pilot reported that everything was normal for engine start and run-up. But, during the takeoff ground run, the left engine momentarily expereinced a partial loss of power and then regained full power again. The pilot continued the take off, but immediately after the airplane became airborne, the left engine again experienced a partial loss of power. The airplane yawed to the left, began to lose altitude and airspeed, and then began an uncommanded roll to the left. The pilot then reduced both throttles to idle as the aircraft descended into a pear orchard, where it impacted the ground in a nose down 'semi-level' attitude. During the post crash inspection, it was found that the left fuel selector was positioned in the 'off' quadrant, about half-way between the center of the quadrant and the edge of the 'left main' guadrant. The right fuel selector was positioned in the 'right main' quadrant.
Probable cause
The pilot's failure to insure that the fuel selector was in the proper position which resulted in fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA94LA223
- Event ID
- 20001206X02152
- Case number
- SEA94LA223
- 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: 56ab5cb293666960ca1fa74c89fb484488d76f18dc8e9c2ccedb7d68b2e1f72b; retrieved 2026-09-21T13:40:14.133Z.