WPR12LA256 · Ayres S2R-G6
Sky Aviation Ayres S2R-G6 · Accident: powerplant system/component malfunction/failure en route
From Riverton, WY to Central Wyoming Regional Airport (RIW)
Event
- NTSB case
- WPR12LA256
- 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 S2R-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
- N70WY
- Operator
- Sky Aviation
- Onboard fatalities
- Unknown
- Route
- From Riverton, WYTo Central Wyoming Regional Airport (RIW), Riverton, WY
- 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
- 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
- Powerplant system/component malfunction/failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Not determined › Not determined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, shortly after departure, he observed the torque and temperature gauges move to extremely high values. The engine did not respond to speed or power lever inputs; however, the pilot reported that the linkage and amount of travel of the controls felt normal. The pilot diverted to a nearby airport and, when the airplane was lined up for landing on the runway, he shut down the engine. The pilot reported that, during the final descent, the airplane encountered a downdraft and collided with a light. Subsequently, the pilot was unable to maintain the airplane on an adequate descent glidepath, and it touched down in the dirt short of the runway.
Postaccident examination of the engine revealed no mechanical anomalies that would have precluded normal operation. Examination of the fuel control unit revealed several anomalies within the unit; however, none of those anomalies would have resulted in the reported engine overspeed condition.
Probable cause
An engine overspeed shortly after takeoff for reasons that could not be determined because postaccident examination revealed no mechanical malfunctions or failures that would have precluded normal operation.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR12LA256
- Event ID
- 20120611X14110
- Case number
- WPR12LA256
- 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. 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: df8a54a4b87681867a574d085d253cfd06e860de011479492b88c55854343b8d; retrieved 2026-09-15T18:27:08.147Z.