SEA04FA006 · Cessna 340A
Cessna 340A · Accident: loss of control in flight while maneuvering
From Red Bluff Municipal Airport (RBL) to Charlotte Amalie Harbor Seaplane Base (SPB)
Event
- NTSB case
- SEA04FA006
- 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
- 2 · 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
Cessna 340A
- Aircraft type
- Cessna 340
- 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
- N340P
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Red Bluff Municipal Airport (RBL), Red Bluff, CATo Charlotte Amalie Harbor Seaplane Base (SPB)
- 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
- Maneuvering
- 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 control in flight
- 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
- Stall
- 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
- Pilot in command › Airspeed, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Witnesses first observed the aircraft on final approach for landing, with the engine(s) making a backfiring sound. While the aircraft was on short final, another aircraft pulled onto the runway and initiated its takeoff roll. The accident aircraft was observed to initiate a go-around, but did not appear to be gaining altitude and was at what the witnesses thought was a slow airspeed. About mid-field, the accident aircraft made an approximate 45 degree turn from runway heading. Within 1/4 mile from the runway, the aircraft lost altitude. The witness stated that the aircraft was about 80 feet agl when the aircraft stalled, rolled inverted (left wing down) and collided with the flat open terrain in a nose low attitude. A post-crash fire subsequently consumed the wreckage. During the post-crash inspection of the engines, it was found that both engines displayed signs of operating at a lean mixture setting. The left engine pistons and spark plugs displayed a more serious lean condition than the right side and displayed the early signs of detonation on the piston heads. No other mechanical failure or malfunction was noted to either the engines or airframe.
Probable cause
The pilot's failure to maintain airspeed while maneuvering. An inadvertent stall, the pilot's failure to follow engine operation procedures and engine detonation were factors.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record SEA04FA006
- Event ID
- 20031103X01852
- Case number
- SEA04FA006
- 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, coordinates. 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: 8fd23aec3df4cb01e375b4ebf1747a7929cafe20827911ef7762afcec0d13ec0; retrieved 2026-09-20T18:53:00.350Z.