# NTSB CEN25LA401: CubCrafters CCK-2000, N40DT, Thompsonville, MI, September 7, 2025 - Type: NTSB accident investigation - Classification: Accident · No injuries · Class 3 · Limited · Final report - Date: September 7, 2025, 09:32 local (13:32 UTC) - Place: Thompsonville, MI - Coordinates: 44.50488, -85.959834 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.5049&lon=-85.9598&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report August 19, 2026 - Report: Approved by Office Director - Investigation class: Class 3 - NTSB office: Central Region - Parties: Lycoming Engines, FAA Grand Rapids FSDO - NTSB case key (mKey): 201747 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN25LA401 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/201747/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=201747 - Page: https://openairdocs.org/ntsb/CEN25LA401 ## 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Electrical power system: battery/charger](https://openairdocs.org/ntsb-findings/01022432): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/01022432/cases.md?model=05641A0), [All aircraft, 37 cases](https://openairdocs.org/ntsb-findings/01022432/cases.md) - [Electrical power system: dC generator-alternator](https://openairdocs.org/ntsb-findings/01022434): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/01022434/cases.md?model=05641A0), [All aircraft, 5 cases](https://openairdocs.org/ntsb-findings/01022434/cases.md) - [Electrical power system: dC power distribution system](https://openairdocs.org/ntsb-findings/01022460): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/01022460/cases.md?model=05641A0), [All aircraft, 13 cases](https://openairdocs.org/ntsb-findings/01022460/cases.md) - [Engine (reciprocating)](https://openairdocs.org/ntsb-findings/01058500): Aircraft › Aircraft power plant · Failure (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/01058500/cases.md?model=05641A0), [All aircraft, 497 cases](https://openairdocs.org/ntsb-findings/01058500/cases.md) - [Electrical power system: electrical pwr sys wiring](https://openairdocs.org/ntsb-findings/01022497): Aircraft › Aircraft systems · Failure (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/01022497/cases.md?model=05641A0), [All aircraft, 44 cases](https://openairdocs.org/ntsb-findings/01022497/cases.md) - [Maintenance: installation](https://openairdocs.org/ntsb-findings/02062035): Personnel issues › Task performance · Owner/builder (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/02062035/cases.md?model=05641A0), [All aircraft, 371 cases](https://openairdocs.org/ntsb-findings/02062035/cases.md) - [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Owner/builder (probable cause); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=05641A0), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Enroute-cruise: Electrical system malf/failure](https://openairdocs.org/ntsb-events/332); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/332/sequence.md?model=05641A0), [All aircraft, 182 cases](https://openairdocs.org/ntsb-events/332/sequence.md) - [Enroute-cruise: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/060/sequence.md?model=05641A0), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Approach-VFR pattern final: Loss of engine power (total)](https://openairdocs.org/ntsb-events/341) (defining event); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/341/sequence.md?model=05641A0), [All aircraft, 3,820 cases](https://openairdocs.org/ntsb-events/341/sequence.md) - [Landing: Off-field or emergency landing](https://openairdocs.org/ntsb-events/440); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/440/sequence.md?model=05641A0), [All aircraft, 3,365 cases](https://openairdocs.org/ntsb-events/440/sequence.md) - [Landing: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=05641A0), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Post-impact: Evacuation](https://openairdocs.org/ntsb-events/460); cases with it: [David Terhaar CCK-2000, 1 case](https://openairdocs.org/ntsb-events/460/sequence.md?model=05641A0), [All aircraft, 103 cases](https://openairdocs.org/ntsb-events/460/sequence.md) ## Analysis 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 normallypart of the pilot’s preflight inspection. ## Factual narrative On September 7, 2025, about 0932 eastern daylight time, a CubCrafters CCK-2000 EX airplane, N40DT, sustained substantial damage when it was involved in an accident near Thompsonville, Michigan. The private pilot and the passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The experimental airplane, known as a Carbon Cub, which the pilot built from a kit, departed from the Thompsonville Airport (7Y2), Thompsonville, Michigan, about 0917. Shortly into the local area flight, the pilot noticed a flicker on the Garmin G3X Touch 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 7Y2. 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 7Y2, 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 Garmin G3X Touch display. The pilot switched over to the ignition backup battery, he 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 noticed that the ignition backup battery was faulty, and it only lasted about one or two minutes. While on short final, about 300 ft agl, the pilot performed a forced landing near trees and a grass field. During the forced landing, the airplane came to rest nose down in the trees. The pilot and the passenger were able to egress from the airplane. The airplane sustained substantial damage to both wings and the wing struts. Postaccident examination of the engine revealed a fractured ring terminal for the Denso 021080-0760 12-volt alternator. The ring terminal, a 10 AWG (American Wire Guage), was found fractured in place. The pilot reported that the fractured ring terminal is from a harness, which does not have a part number, came with the kit he purchased (see figure 1). Figure 1 – View of the fractured ring terminal in the red circle (courtesy of the pilot). The pilot reported that the ring terminal likely fractured from vibrations while the engine was operating and that it is possible that there might have been too much tension on the wire and ring terminal. The pilot additionally reported that he did not have any previous issues with the alternator, including during the build process. The 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 theignition backup battery. The engine, which was equipped with a dual electronic ignition system (Light Speed Engineering 1.334-D-H-22 Dual Plasma III), does not have magnetos installed. The 12-volt ignition backup battery that failed, a Power Sonic PS-1221S (that has a CubCrafters part number of SP91001-201), had a decal on it that stated “received 03/14/2023.” The ignition backup battery also came with the kit that he purchased and was installed during the build process. A review of the historical FAA airworthiness records showed that a conformity inspection was performed by an FAA aviation safety inspector on the airplane on July 7, 2025, and that a FAA special airworthiness certificate was issued for the airplane on the same date. The airplane did not accumulate enough time to require its first annual inspection for the airframe and the engine. According to the CubCrafters CCK-2000 airplane maintenance manual, the ignition backup battery is to be changed at each annual inspection. The pilot expressed concern 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. The pilot reported he believed the ignition backup battery failed because it was old. For the Garmin G3X Touch display, the pilot reported the following voltage settings were programed from the airplane: 10.0-10.8 Volts – Red Range + Alert 10.8-11.5 Volts – Yellow Range + Alert 11.5-12.6 Volts – Yellow Range 12.6-15.8 Volts – Green Range 15.0-15.8 Volts – Yellow Range + Alert 15.8-16.0 Volts – Red Range + Alert For the area where the ring terminal fractured by the alternator, it is not visible during a preflight inspection to a pilot, as the engine cowl covers it. ## Aircraft - Registration: [N40DT](https://openairdocs.org/aircraft/N40DT), registered now, S/N CCK-2000-0115, built 2025 (OpenAirDocs) - Reported make and model: CubCrafters CCK-2000 (EX) - Registry model: [David Terhaar CCK-2000](https://openairdocs.org/model/david-terhaar-cck-2000) (registry code 05641A0) (OpenAirDocs) - Registry engine: [Lycoming CC363I](https://openairdocs.org/engine/lycoming-cc363i) (registry code 41465, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: CCK-2000-0115 - Year built: 2025 - Airframe hours: 41 - Engines: CubCrafters CC363i 186 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Condition, July 7, 2025, 41 hours before - Departed: 7Y2, Thompsonville, MI - Destination: 7Y2, Thompsonville, MI - Equipment: Electronic primary flight display, Data recorder ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 53; injuries: none; private; airplane ratings: single-engine land, single-engine sea; medical: class 3, with waivers/limitations; last flight review March 8, 2025; seat: front; restraint: 3-point; flight hours: 1,150 total, 215 in this make and model, 1,150 as pilot in command, 48 in the last 90 days, 22 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 9 knots, gusting 14 - Visibility: 10 statute miles - Lowest ceiling: 3,400 ft overcast - Temperature: 52 °F, dew point 48 °F - Altimeter: 29.90 inHg - Observed at: KFKS, 14 nm away - METAR: KFKS 061315Z AUTO 27009G14KT 250V310 10SM -DZ SCT020 SCT028 OVC034 11/09 A2990 RMK AO2 T01120087 ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20250907013519A](https://openairdocs.org/incident/20250907013519A), Sep 7, 2025: N/A CCK-2000, Thompsonville, MI, Substantial damage. On 09/07/2025 at approximately 1020 eastern standard time, [privacy data omitted] an experimental-homebuilt carbon cub CCK-2000 aircraft, registered to and… ## Docket (9 files) The files NTSB released with the investigation on August 19, 2026, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=201747. 7.2 MB in all. - Pilot/operator aircraft accident report, NTSB form 6120.1 (item 1, PDF, 10 pages, 1.6 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19547554&FileExtension=pdf&FileName=N40DT%20NTSB%20Form%206120_1_Redacted-Rel.pdf - Investigation photographs (item 2, PDF, 9 pages, 1.9 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19573736&FileExtension=pdf&FileName=Investigation%20Photographs-Rel.pdf - Pilot - email statement (item 3, PDF, 2 pages, 259 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19548630&FileExtension=pdf&FileName=CEN25LA401%20Pilot%20Statement_Redacted-Rel.pdf - Pilot - interview (item 4, PDF, 3 pages, 73 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19572704&FileExtension=pdf&FileName=CEN25LA401%20Pilot%20MOR-Rel.pdf - N40DT - ADS-B data (microsoft excel file) (item 5, XLSX, 2.7 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19649085&FileExtension=xlsx&FileName=20250907_A4AAA5_599821069_ADSB-Rel.xlsx - N40DT - ADS-B data (google earth pro file) (item 6, KMZ, 98 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19647873&FileExtension=kmz&FileName=20250907_A4AAA5_599821069-Rel.kmz - Cubcrafters - record of conversation (item 7, PDF, 2 pages, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19649992&FileExtension=pdf&FileName=CEN25LA401%20CubCrafters%20MOR-Rel.pdf - Cubcrafters - CCK-2000 poh/afm excerpt (item 8, PDF, 1 page, 226 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19551945&FileExtension=pdf&FileName=CubCrafters%20CCK-2000%20-%20POH_%20AFM%20Excerpt-Rel.pdf - Statement of party representatives to NTSB investigation - Lycoming engines (item 9, PDF, 1 page, 205 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=19547544&FileExtension=pdf&FileName=NTSB%20Party%20Form%20N40DT%20CEN25LA401_Redacted-Rel.pdf From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.