CEN17LA096 · Cook Smith Aviation Repli
Cook Smith Aviation Repli · Accident: loss of engine power (total) while maneuvering
From Aero Valley Airport (52F) to Aero Valley Airport (52F)
Event
- NTSB case
- CEN17LA096
- 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
Cook Smith Aviation Repli
- Aircraft type
- Cook SMITH AVIATION REPLI
- 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
- N712AZ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Aero Valley Airport (52F), Roanoke, TXTo Aero Valley Airport (52F), Roanoke, TX
- Aircraft age
- About 9 years (built 2008)
- 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 · low-altitude flying
- 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 (total)
- 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
- Tree(s)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The private pilot reported that he departed in the experimental, amateur-built airplane with 10 gallons of fuel in the left fuel tank and 15 gallons of fuel in the right fuel tank. He had flown for about 15 minutes in straight and level flight, then he conducted a simulated forced landing to a wheat field. During the recovery from the practice maneuver, he turned off the carburetor heat, applied full engine power, and raised the nose to a steep pitch attitude of about 35° to 40° nose up. He stated that the engine experienced a total loss of power in the climb about 200 to 500 ft above ground level. He pushed the control stick full forward to maintain airspeed and chose to land straight ahead. The engine started to "sputter" and regain power about the time that the airplane struck the trees, which resulted in substantial damage to the wings and fuselage.
Examination of the accident site revealed that no fuel was present; however, the airplane's fuel system was largely compromised by impact damage. There were no apparent fuel stains on the fabric-covered wings. Based on the temperature and dew point about the time of the accident, the conditions were not favorable for carburetor icing at any power setting. The engine was installed on an engine test stand and operated through a range of engine power settings between 1,200 to 2,700 rpm, and at idle. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or failures that would have precluded normal operation.
The airplane had a 180-hp engine installed that was not equipped with an engine-driven fuel pump or electric fuel boost pump. The airplane's gravity feed fuel system had 24-gallon fuel tanks installed in each overhead wing, but there was no fuel header tank installed. Leading edge slats were installed along the entire span of the right and left wings, which allowed the airplane to be flown at a very high nose-up pitch attitude.
It was possible for the airplane to climb at a very steep angle, which could put the carburetor higher than the wing tanks. With inadequate fuel pressure to deliver fuel to the carburetor, it is possible that a gravity feed fuel system might experience a disruption of fuel flow in high nose-up pitch attitudes; given the lack of any mechanical anomalies with the engine, it is likely that the loss of power was the result of a disruption of fuel flow during the climb.
Probable cause
A total loss of engine power due to fuel starvation as the result of a disruption in fuel flow.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA096
- Event ID
- 20170201X00517
- Case number
- CEN17LA096
- 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, 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: af4b003c587022c45a0cd630db34ebdea3b6c66d02269ee5c3ebcdec63e187e0; retrieved 2026-09-16T04:59:15.600Z.