CEN23LA273 · Berkut 540
Berkut 540 · Accident: loss of engine power (partial) en route
From The Eastern Iowa Airport (CID) to The Eastern Iowa Airport (CID)
Event
- NTSB case
- CEN23LA273
- 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
- Event fatalities
- Unknown
- 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
Berkut 540
- Aircraft type
- Berkut 540
- 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
- N567JS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From The Eastern Iowa Airport (CID), Cedar Rapids, IATo The Eastern Iowa Airport (CID), Cedar Rapids, IA
- Aircraft age
- Built the same year (2023)
- 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
- En route
- 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, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
According to the pilot, the accident occurred during his first flight of the experimental airplane. About 8 minutes after takeoff, upon reaching an altitude of about 3,250 ft mean sea level (msl), the airplane entered a gradual descent, and the pilot realized that the engine had lost partial power. He decided to return to the airport. He recalled the fuel pressure, fuel flow, and manifold pressure were within normal limits at that time. However, when the pilot activated the fuel boost pump, the engine lost all power. The airplane did not have sufficient altitude to reach the airport, and the pilot executed a forced landing to a road.
The airplane impacted a sign and trees adjacent to the road before coming to rest in a residential driveway. The pilot noted that when the airplane came to rest, he heard a “fast humming” sound and immediately switched off the ignition. Both wings separated from the fuselage, and both canards were damaged. Each of the four propeller blades were separated at the blade roots and fragmented.
A postaccident engine examination revealed several anomalies. The ignition harness leads corresponding to the Nos. 3 and 4 cylinder upper spark plugs were disconnected from the ignition module. In addition, the Nos. 1, 2, and 6 upper, and the No. 2 lower spark plug leads were loose and not fully connected at the ignition module. The ignition modules were tested and operated normally. The Nos. 1 and 2 cylinder spark plugs exhibited normal operating signatures; however, the remaining spark plugs exhibited sooty deposits.
Engine data retained by the onboard avionics revealed the engine speed remained stable until about 6 minutes after takeoff when it decreased about 200 rpm consistent with a partial loss of engine power. At that time, the No. 1 cylinder head temperature (CHT) and exhaust gas temperature (EGT) decreased dramatically. The No. 2 CHT and EGT remained low for most of the flight.
About 14 minutes after takeoff, the engine speed decreased further from approximately 2,500 rpm to about 1,200 rpm with corresponding decreases in the other engine parameters. Approximately 15 seconds after the reduction in engine power, the fuel pressure increased consistent with the pilot activating the electric fuel boost pump. About one minute after the reduction in engine power, the pilot touched down on the road during the forced landing, and six seconds later the engine speed and fuel flow increased abruptly and momentarily and then abruptly dropped to zero.
The sudden increase in engine speed after impact suggested the engine had not lost power completely, and the engine speed increased when the propeller blades fractured during the accident sequence, which removed the resistive torque from the engine.
The partial loss of engine power was likely due to the ignition system anomalies observed during the postrecovery examination.
Probable cause
A partial loss of engine power during the test flight due to multiple ignition system anomalies.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA273
- Event ID
- 20230703192503
- Case number
- CEN23LA273
- 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, cause areas. 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: 153ec70758dce418ed45d44801d76fc3db2511e143e93d5925ea4b4b7d9c77de; retrieved 2026-09-16T17:47:41.991Z.