CEN11LA460 · Ayres S2R600 G6
Swan Lake Flying Service Ayres S2R600 G6 · Accident: powerplant system/component malfunction/failure during initial climb
From Pine Bluff, AR to Pine Bluff, AR
Event
- NTSB case
- CEN11LA460
- 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
- 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
Ayres S2R600 G6
- Aircraft type
- Ayres S2
- 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
- N3101S
- Operator
- Swan Lake Flying Service
- Onboard fatalities
- Unknown
- Route
- From Pine Bluff, ARTo Pine Bluff, AR
- Aircraft age
- Not recorded
- 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 137: Agricultural
- 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
- Initial climb
- 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
- Powerplant system/component malfunction/failure
- 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
After the airplane sustained a complete loss of engine power during initial climb, the pilot performed an off-airport landing. Postaccident examination revealed that three teeth in the torque sensor spur gear separated after four of the five torque sensor mounting bolts became loose. The loose bolts caused the torque sensor housing to move radially away from the gear case, causing the teeth to overload and separate. Subsequently, the engine’s fuel pump and fuel control were no longer driven by the gears in the gear train, which were normally driven by the torque sensor spur gear, thus the engine was starved of fuel. Metallurgical examination showed that the bolts became loose because a bolt that was undersized and of the incorrect configuration had been installed. A maintenance record showed that the engine had previously been disassembled due to a torque sensor failure and an overhauled torque sensor had been reinstalled.
Probable cause
The use of an incorrect mounting bolt by maintenance persons to attach the engine torque sensor, which resulted in an internal failure of the torque sensor and subsequent loss of engine power due to fuel starvation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN11LA460
- Event ID
- 20110707X44030
- Case number
- CEN11LA460
- 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. 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: cbf2342561562d276c9ed61f8771ae2d539680442a653a2211eac8a803d9fc8b; retrieved 2026-09-15T16:25:17.437Z.