FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN25LA401 · CubCrafters CCK-2000 EX

7 Sept 2025 · Thompsonville, MI, United States

CubCrafters CCK-2000 EX · Accident: loss of engine power (total) on approach

From Thompsonville Airport (7Y2) to Thompsonville Airport (7Y2)

Report a problem

Event

NTSB case
CEN25LA401
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
0
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

CubCrafters CCK-2000 EX

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
N40DT
Operator
Unknown
Onboard fatalities
Unknown
Route
From Thompsonville Airport (7Y2), Thompsonville, MITo Thompsonville Airport (7Y2), Thompsonville, MI
Aircraft age
Built the same year (2025)
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
Approach · VFR pattern final
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)
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
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

Shortly into the local area flight with the experimental amateur-built airplane, the pilot noticed a flicker on the avionics display, but a low voltage warning never appeared. The pilot then looked at the engine monitoring display which indicated the alternator was not charging, and it showed 12.8 volts direct current (VDC) on the main battery. The pilot immediately started a climbing turn back to the departure airport. After reaching about 4,000 ft, he tried several methods to get the alternator working including cycling both the field and the main alternator circuit breakers several times. He checked the voltage for the ignition backup battery, which read 12.8 VDC. Since he had about a 15-minute flight back to the departure airport, he decided to save the ignition backup battery and run off the main battery until he received a low voltage warning. The airplane was on final approach when a low voltage warning appeared on the display. The pilot switched over to the ignition backup battery and watched as the voltage dropped from 12.8 VDC down to 0 VDC, and the engine sustained a total loss of engine power. The pilot reported that the ignition backup battery only lasted about one or two minutes before the voltage dropped to 0 VDC. While on short final, about 300 ft agl, the pilot performed a forced landing near trees and a grass field. The airplane came to rest nose down in the trees and sustained substantial damage to both wings and the wing struts. Postaccident engine examination revealed a fractured ring terminal for the 12-volt alternator. It is likely that the ring terminal fractured from vibrations while the engine was operating. It is also likely that there was too much tension and not enough relief on the wire that the ring terminal was connected during the installation to the alternator. The airplane’s engine was built to use a dual electronic ignition system that operated from the airplane’s electrical system, which included the main battery, the alternator to maintain the main battery’s charge, and the ignition backup battery. Once the ring terminal fractured, the ignition system relied completely on the main battery as the source of ignition power. Once the main battery power was depleted and the ignition backup battery power was depleted, the ignition system could not operate, and the engine sustained a total loss of power due to the lack of ignition. The airplane did not accumulate enough time to require its first annual inspection for the airframe and the engine. According to the airplane maintenance manual, the ignition backup battery is to be changed at each annual inspection. The pilot expressed concern that with the ignition backup battery that came with the kit, as it may take a builder some time to complete the building of the airplane, and that could easily go over a one-year timeline for example. The pilot would not have been able to detect the fractured ring terminal without removing the engine cowl, which is not normally part of the pilot’s preflight inspection.

Probable cause

A total loss of engine power due to a lack of ignition resulting from a fractured alternator ring terminal and the builder’s incorrect installation of the wire connecting to the alternator. Contributing to the total loss of engine power was the failure of the ignition backup battery.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN25LA401
Event ID
20250929201747
Case number
CEN25LA401
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, 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: 349d7b13fa07e456cadc40f42923289dbaeb153c84bd58d67ea963499e134507; retrieved 2026-09-16T20:23:59.933Z.