ERA25LA064 · AMS Flight D O O CARAT A
AMS Flight D O O CARAT A · Accident: loss of engine power (total) en route
From Thomas Ridge Airport (3GA7) to Northeast Alabama Regional Airport (GAD)
Event
- NTSB case
- ERA25LA064
- 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
AMS Flight D O O CARAT A
- Aircraft type
- Ams Flight CARAT
- Category
- Glider
- 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
- N17GF
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Thomas Ridge Airport (3GA7), Rupert, GATo Northeast Alabama Regional Airport (GAD), Gadsden, AL
- Aircraft age
- About 17 years (built 2007)
- 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 (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 handling/service
- Personnel issues › Experience/knowledge
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot of the motor glider stated that about 1 hour after departure, the motor glider’s engine lost partial power and began to run rough. Shortly thereafter, the engine lost power completely and the pilot’s attempt to restore power was unsuccessful. He located a nearby private airport on his GPS and attempted to perform a forced landing to its turf runway. As he approached the runway, he observed cattle and a fence on the runway and realized it was not an actual airport but was unable to make any corrections due to altitude and airspeed. During the landing, the motor glider landed hard and came to rest inverted resulting in substantial damage to the fuselage. Postaccident examination of the motor glider’s engine revealed that the No. 4 cylinder intake valve had separated from its two keepers/safety wedges and had fractured into three sections. The valve face was located inside the cylinder, and the valve stem was deformed and found in the intake manifold. One valve keeper was found inside the valve cover and exhibited abrasion at its rotocap contact surface; the second keeper was not located. The intake rocker arm adjustment screw was backed off, and its corresponding jamb nut was found in the valve cover. The exhaust rocker arm adjustment screw for the No. 4 cylinder was also backed off, though its jamb nut remained in place. These conditions differed from those found on the remaining three cylinders. Abrasion marks on the intake and exhaust rocker arm adjustment areas were consistent with contact between the rocker arms and rotocaps during engine operation. The engine manufacturer’s maintenance publications required a minimum 1 mm clearance between the rocker arm and rotocap when the valve was fully depressed and specified that the clearance be visually inspected at intervals not exceeding 100 hours. The engine had accumulated 107.1 tachometer hours since the valves were last replaced and 54.9 hours since the most motor glider’s most recent condition inspection. Based on this information, the wear and damage observed during the postaccident examination of the engine likely the result of improper clearance between the rocker arm and rotocap, which resulted in unseating of the keepers and valve separation. Although the private use airport was charted, the local municipality had not approved the airport, and the airport had been erroneously activated; thus the airport should not have been charted. The airport owner later requested its deactivation, which became effective about 3 months after the accident.
Probable cause
Maintenance personnel’s failure to comply with the engine manufacturer’s guidance, which resulted in improper valvetrain clearances, unseating of the intake valve keepers, and a total loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA064
- Event ID
- 20241204199379
- Case number
- ERA25LA064
- 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: fbe0077d7f51287e036f69e4325b215d45e3e6dccc63067628e5f23581ab3bd8; retrieved 2026-09-16T19:31:17.846Z.