CZECH AIRCRAFT WORKS SPOL SRO SPORTCRUISER near Santa Monica, CA — 2016-05-22
- Date
- 2016-05-22
- Location
- Santa Monica, CA, USA
- Airport
- SMO
- Aircraft
- CZECH AIRCRAFT WORKS SPOL SRO SPORTCRUISER
- Registration
- N1111X
- Category
- Airplane
- Highest injury
- None
- Fatalities
- 0
- Phase of flight
- Initial climb
Probable cause
A partial loss of engine power during takeoff due to vapor lock. Contributing to the accident was the student pilot's failure to notice that the engine had exceeded multiple temperature limits and that the fuel flow had become erratic during an extended ground hold, which led to the vapor lock.
Contributing factors
Contributing to the accident was the student pilot's failure to notice that the engine had exceeded multiple temperature limits and that the fuel flow had become erratic during an extended ground hold, which led to the vapor lock.
NTSB narrative
The student pilot had just completed two uneventful takeoffs and landings in the light-sport airplane. As he approached the runway's hold-short line to wait for the third takeoff clearance, a pilot from another aircraft in the traffic pattern declared an emergency. The student remained in the airplane with the engine running for about 20 minutes before receiving a takeoff clearance. Data from the airplane's engine monitor indicated that, while the airplane was waiting, multiple engine temperature limits were exceeded, and the fuel flow became erratic. The student did not notice the exceedances, and shortly after takeoff, the engine lost partial power, and the airplane began to descend. The student then initiated a 180° turn back toward the airport. The airplane landed long, and the student was unable to slow the airplane before it departed the elevated section of the runway and fell 10 ft. The airplane sustained substantial damage to the firewall and lower fuselage structure. The engine monitor data revealed that, during the first two previous takeoffs and landings, the fuel flow indications were normal. However, as stated previously, after the airplane had been holding short for about 20 minutes awaiting clearance for the next takeoff, multiple engine temperature limits were exceeded, and the fuel flow indications began to oscillate. Once the takeoff began, the fuel flow continued to oscillate, indicating that the fuel flow to the engine was experiencing intermittent interruptions, which was consistent with the fuel system experiencing vapor in the fuel lines (vapor lock). The vapor lock was likely caused by the engine bay becoming hot during the extended ground hold after the airplane had previously being flown for two flights, which resulted in heat-soaking of the fuel system. About 4 years before the accident, the engine manufacturer amended its engine installation manual to recommend the installation of a fuel return line, which was designed to prevent engine malfunctions caused by the formation of vapor in the fuel system. Examination of the airplane's fuel system revealed that a fuel return line had not been installed. The airplane manufacturer did not mandate the installation of a fuel return line until about 17 months after the accident, at which time, it issued a safety alert mandating the installation of the fuel line in accordance with the updated engine installation manual. Ten months later, the airplane manufacturer issued another alert, recommending updates to the Pilot's Operating Handbook by adding a warning that contained procedures to follow to limit the possibility of vapor lock. However, although the lack of a fuel return line could have contributed to the development of vapor lock, it more likely occurred because the student allowed the engine to overheat during the ground hold.
Analysis
- Primary failure mode
- Engine power loss
- First missed decision gate
- Pilot could have aborted takeoff due to high engine temperatures before takeoff.
NTSB coding
Evidence available
- FDR / data
- 14 docket documents
Docket documents14
- Cockpit Displays – Recorded Flight Data - Attachment 1 - Tabular Data (CSV)fdr
- Cockpit Displays – Recorded Flight Data - Specialist's Factual Reportfdr
- Evidence Control Formsform
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1form
- Release of Aircraft Wreckage, NTSB Form 6120.15form
- Fuel Flow Transducer Manufacturer Statementsinterview
- Pilot Interview Summaryinterview
- Santa Monica Flyers General Manager Interview Summary regarding Fuelinterview
- Czech Aircraft Works Safety Alertsother
- Maintenance Logbook Excerptsother
- Rotax 912 Series Engine Installation Manual Excerptsother
- Rotax and Czech Aircraft Works Operation Manual Excerptsother
- Fuel Analysis Reportreport
- NTSB Engine Examination Reportreport
Related mishaps
- CESSNA 172I
2024-11-14 · Los Angeles, CA
- CIRRUS DESIGN CORP SR22T
2024-06-23 · Boerne, TX
- CESSNA 172G
2024-05-16 · Lakeport, CA
- KJELSRUD GARY KITFOX
2024-05-10 · Powell, WY
- BEECH B24R
2024-04-22 · Lumberton Township, NJ
- CESSNA 177RG
2023-10-01 · Lake Placid, NY · 2 fatalities