WPR16FA115 · Czech Aircraft Works Spol SRO SPORTCRUISER
Santa Monica Flyers Czech Aircraft Works Spol SRO SPORTCRUISER · Accident: loss of engine power (partial) during takeoff
From Santa Monica Municipal Airport (SMO) to Santa Monica Municipal Airport (SMO)
Event
- NTSB case
- WPR16FA115
- 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
Czech Aircraft Works Spol SRO SPORTCRUISER
- Aircraft type
- Czech Aircraft Works SPORTCRUISER
- 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
- N1111X
- Operator
- Santa Monica Flyers
- Onboard fatalities
- Unknown
- Route
- From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Santa Monica Municipal Airport (SMO), Santa Monica, CA
- Aircraft age
- About 8 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
- Takeoff
- 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
- Substantial
Cause areas
- Aircraft › Aircraft power plant
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
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.
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.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR16FA115
- Event ID
- 20160522X34523
- Case number
- WPR16FA115
- 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: e91dc61033032229c34adac3fff7dd2eeb6311c81aa17c6351fcb0871ad0edb0; retrieved 2026-09-16T03:25:03.477Z.