ERA25LA011 · Saint Glasair II SFT
Saint Glasair II SFT · Accident: loss of engine power (partial) on approach
From Orange County Airport (OMH) to an unrecorded destination
Event
- NTSB case
- ERA25LA011
- 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
Saint Glasair II SFT
- Aircraft type
- Saint GLASAIR II SFT
- 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
- N952W
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Orange County Airport (OMH), Orange, VATo not recorded
- Aircraft age
- About 27 years (built 1997)
- 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 crosswind
- 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
During initial climb on a crosswind leg of the airport traffic pattern, the experimental amateur-built airplane exhibited a partial loss of engine power. The pilot attempted to glide the airplane to an upwind landing, but overshot the runway and landed in a field, resulting in substantial damage.
Postaccident examination of the wreckage revealed that a threaded coupler between the throttle rod end and throttle cable had loosened and disconnected the cable from the throttle arm. This allowed the arm to move toward idle position. Use of a throttle cable coupler was likely a custom installation, and was not provided by the kit manufacturer. The installation provided a means to adjust the throttle cable; however, it also proved to be a single point of failure as there was no means to secure the coupler, such as a cotter pin or safety wire.
Probable cause
The installation of a non-failsafe coupler that resulted in the separation of the throttle cable from the throttle arm and a subsequent partial loss of engine power.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA25LA011
- Event ID
- 20241015195308
- Case number
- ERA25LA011
- 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: 4172bc0f7d57f2a3494b517198a406cef5817713b94ae7b9d2c0150a23f61483; retrieved 2026-09-16T19:22:36.752Z.