CEN22FA433 · Airgyro AG915 SPARTAN
Airgyro AG915 SPARTAN · Accident: loss of control in flight en route
From Chan Gurney Municipal Airport (YKN) to an unrecorded destination
Event
- NTSB case
- CEN22FA433
- 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
- 1 · 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
Airgyro AG915 SPARTAN
- Aircraft type
- Airgyro AG915
- Category
- Gyroplane
- 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
- N499AG
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chan Gurney Municipal Airport (YKN), Yankton, SDTo not recorded
- Aircraft age
- Built the same year (2022)
- 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 control in flight
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Aircraft › Aircraft power plant
- Personnel issues › Experience/knowledge
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot built the experimental gyroplane and was in the process of achieving the required 40 flight test hours. The maintenance records showed that the gyroplane had accumulated 37.8 flight hours before the accident. The gyroplane departed from the airport and two witnesses observed black smoke emitting from the gyroplane while it was flying. Neither witness observed fire emitting from the gyroplane while in-flight. The gyroplane impacted a grass field. The wreckage, which was destroyed, sustained extensive thermal damage. Examination of the wreckage revealed that an in-flight fire had occurred. Several sections of the fuselage, empennage, and the main rotor mast were found a significant distance from the impact point. The sections exhibited signs of thermal damage that did not appear to be related to a postimpact fire. In addition to the thermal damage, there was also evidence of fluid consistent with oil on both the interior and exterior of several fuselage and empennage pieces. The fluid on the exterior surfaces appeared in airflow-driven patterns, indicating that the fluid leak occurred in flight. Evidence showed that the in-flight fire had originated from the compartment where the experimental engine was housed. Two aluminum valve covers (cylinders Nos.2 and 4) collocated on the engine were melted along the bottom edge of the covers with evidence of dripping and material flow. The flow direction of the melted areas indicated that the material was in an upright (in-flight position) at the time the material started to flow and is inconsistent with postimpact fire damage. The fire fuel source appeared to be leaking oil from the governor pad. The engine had oil coating over a large area of the exposed surfaces. Oil was found on several sections of the fuselage and the empennage, including sections located away from the area of impact and postimpact fire. A governor had not been installed on the governor pad and the governor flange cover was still in place. The still-installed governor pad was heavily coated in oil, with an area of coagulated oil directly beneath the pad. With the governor flange cover installed, oil leaked from the governor pad and likely ignited at the turbocharger exhaust duct. An in-flight fire occurred that produced the black smoke that the two witnesses observed. It is likely that the pilot lost control in flight with the engine fire, and subsequently impacted terrain.. Contributing to the accident was the improper build process by the pilot. The engine installation manual states that the governor flange cover is for engine transportation only and not for flight operations. Additionally, the governor flange cover must be replaced with a functional governor, or the engine is to be converted to a different version per a service document from the engine manufacturer. It is likely that the pilot did not fully reference and understand the engine installation manual and the service document during the build process, and thus flew the gyroplane with the governor flange cover installed, which eventually leaked oil and resulted in an in-flight fire.
Probable cause
A loss of control while an in-flight fire occurred, which resulted in an impact with terrain. Contributing to the accident was the pilot/builder’s improper engine build procedures.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22FA433
- Event ID
- 20220927106005
- Case number
- CEN22FA433
- 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: 454584b6dae028c27063b59e451c5f9380024139a46f67e599353c029bf59f10; retrieved 2026-09-15T07:51:51.521Z.