CEN12FA058 · Cessna 337G
Lamp Ministry Cessna 337G · Accident: loss of engine power (partial) during initial climb
From San Luis Valley Regional Airport/Bergman Field (ALS) to Salida Airport - Harriet Alexander Field (ANK)
Event
- NTSB case
- CEN12FA058
- 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
- 1 · 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 337G
- Aircraft type
- Cessna 337
- 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
- N337LC
- Operator
- Lamp Ministry
- Onboard fatalities
- Unknown
- Route
- From San Luis Valley Regional Airport/Bergman Field (ALS), Alamosa, COTo Salida Airport - Harriet Alexander Field (ANK), Salida, CO
- Aircraft age
- About 35 years (built 1976)
- 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
- Initial climb
- 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 (partial)
- 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
One witness reported that the pilot started both engines before takeoff and that both the front and rear engines were running for about 5 minutes before he started to taxi the airplane. Another witness reported seeing the airplane flying just after takeoff at a low altitude and then hearing the engine shut off before the airplane went out of sight behind a stand of trees. Another witness reported seeing the airplane flying at a low altitude when it suddenly lost altitude and nose dived toward the ground.
The twin-engine airplane's fuselage had two engines in tandem, one engine in front of the cabin and one engine behind the cabin. The airplane had retractable landing gear and a belly-attached cargo pod. Examinations of the rear engine's propeller blade assembly showed evidence that it was not producing power at impact. The front engine's propeller blade assembly showed evidence that it was producing power at impact. Examinations of the fuel distribution system revealed that the front engine fuel selector handle was set to the left tank. The front engine fuel selector valve was found between the "left tank" and "off" positions. The rear engine fuel selector handle and valve were found in the "off" position; therefore, the rear engine was most likely starved of available fuel, which is consistent with the physical and witness evidence of a loss of power to the rear engine. Further, given the witness statement that both engines were running before departure, it is likely that the fuel selector was inadvertently moved to the "off" position during, or shortly after, takeoff.
Detailed examinations of the airframe components and teardowns of both engines did not reveal any preexisting mechanical anomalies that would have contributed to the accident. The Pilot's Operating Handbook (POH) noted that the airplane's single-engine climb rate is reduced 15 feet per minute (fpm) with the belly cargo pod attached and 240 fpm when the gear is in transit. The actual weight of the airplane at the time of the accident could not be determined due to a lack of fuel and airplane empty weight information. A weight of 4,000 pounds, the lightest weight shown in the POH, was used for airplane performance calculations, which showed that, at the time of the accident, the airplane's single-engine climb rate with the belly cargo pod attached was about 99 fpm. Given that the main landing gear were likely in transit, the climb rate could have been reduced by as much as 240 fpm. In this condition, the airplane would not have been able to climb and the pilot would not have been able to maintain level flight.
Probable cause
The loss of power to the rear engine due to fuel starvation during takeoff, which resulted from the fuel selector valve being inadvertently moved to the “off” position, and resulted in the airplane’s inability to climb.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN12FA058
- Event ID
- 20111111X12732
- Case number
- CEN12FA058
- 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: 769108df2f59a7a3d6a4fad8e4b5b01db7a879e7e65a23bfff187baea67c3552; retrieved 2026-09-13T21:58:15.983Z.