LAX07CA182 · Cessna 340A
Cessna 340A · Accident: total loss of engine power (non-mechanical) on approach
From Stellar Airpark (KP19) to Stellar Airpark (KP19)
Event
- NTSB case
- LAX07CA182
- 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
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
- N8688K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Stellar Airpark (KP19), Chandler, AZTo Stellar Airpark (KP19), Chandler, AZ
- 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 downwind
- 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 starvation
- 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 › Starvation
- Pilot in command › Fuel management, inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
While on downwind the airplane experienced a loss of engine power and collided with houses and other obstacles during a forced landing on a residential neighborhood street. The pilot stated that he took off to troubleshoot a landing gear anomaly. He departed the airport area to the south. He cycled the landing gear and upon getting questionable indications in the cockpit of gear position he requested another aircraft confirm his landing gear configuration. Once he got the confirmation that all three wheels were down he proceeded back to the airport. About 2 miles away and approximately 1,800 feet agl the right engine began to lose power. He troubleshot the engine by attempting a restart, cycling the fuel pump off then on, and selected the right auxiliary fuel tank. The right engine did regain some power. He had lost some altitude during the process of troubleshooting the engine. He raised the landing gear to reduce drag, and entered right hand traffic for runway 17. At this point the left engine lost power, the airplane turned left, and he entered a descent to help maintain airspeed. He put the left propeller in feather, and switched to a new fuel tank, but the engine did not regain power. He did not have any altitude to exchange for airspeed and steered the airplane towards a clear residential street. The airplane impacted the roofs of at least two houses before colliding with the street. The pilot egressed through the rear of the airplane. An FAA inspector that examined the airplane wreckage stated that there was very little evidence of fuel onboard the airplane. The pilot stated that the left engine had failed due to fuel starvation and that he had fuel onboard but it was not in the right places.
Probable cause
fuel starvation due to the pilot's failure to adequately manage and monitor his fuel supply.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX07CA182
- Event ID
- 20070705X00889
- Case number
- LAX07CA182
- 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: 3210ecf497b634d5524a0f16f49b00bc8b332a90c98cb4f273f4ae3fc422f8a5; retrieved 2026-09-22T03:47:29.845Z.