Event CEN23LA406

Factual narrative

The pilot reported that he had completed a charter flight and departed to pick up new passengers at an airport about 200 nautical miles away. While on approach to the destination airport, the previous passengers notified the pilot that they were ready to be picked up, so the pilot did not land and turned the airplane back toward the departure airport. The pilot climbed to 10,000 ft and noticed the airplane’s fuel burn was high, so he climbed to 16,000 ft. The pilot reported that “everything was routine until about a 3-mile final” to the runway, when the controller asked the pilot to slow to a final approach speed. An airplane was still on the runway, so the controller told the pilot to go around. The pilot told controllers twice that he had minimum fuel available. The pilot continued on a visual approach for the same runway when the right engine lost power followed by the left engine. He feathered both propellers and made a forced landing to a wooded area. The airplane sustained substantial damage to the fuselage, both wings, and the empennage. The pilot reported that there were no preimpact mechanical malfunctions or failures that would have precluded normal operation. The pilot later stated that he was “trying to do too much with too little” fuel and the accident was a result of poor fuel management. Although the controller directed the pilot to go around, the pilot should have recognized the criticality of the minimum fuel situation and landed the airplane. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

• — Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid management
• — Aircraft-Fluids/misc hardware-Fluids-Fuel-Fluid level
• — Personnel issues-Action/decision-Info processing/decision-Decision making/judgment-Pilot