WPR18LA158 · Rhoads Autogyro MTO Sport
Blue Sky Gyros Rhoads Autogyro MTO Sport · Accident: part(s) separation from aircraft during initial climb
From San Manuel Airport (E77) to San Manuel Airport (E77)
Event
- NTSB case
- WPR18LA158
- 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
Rhoads Autogyro MTO Sport
- Aircraft type
- Rhoads AUTOGYRO MTO SPORT
- 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
- N574BR
- Operator
- Blue Sky Gyros
- Onboard fatalities
- Unknown
- Route
- From San Manuel Airport (E77), San Manuel, AZTo San Manuel Airport (E77), San Manuel, AZ
- Aircraft age
- About 3 years (built 2015)
- 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
- 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
- Part(s) separation from aircraft
- 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 propeller/rotor
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that he and the student pilot were conducting a familiarization flight. After an uneventful takeoff and when the gyroplane was about 400 ft above ground level, she heard a “loud bang,” followed by severe vibrations and a total loss of engine power. She chose to initiate an emergency landing and turned right back toward the runway and landed uneventfully. During the landing roll, she saw that the gyroplane was on fire. The gyroplane came to a stop, and the fire was extinguished. Examination of the gyroplane revealed that the muffler, coolant line, and both carburetors were either fracture separated or shaken loose. One of the propeller blades and part of the propeller hub were missing, which likely resulted in an imbalance and subsequent severe vibrations and extensive vibration-related damage. One of the propeller blades had impacted a rotor blade. A fuel line was found damaged and open, which likely started the in-flight fire, and the fuselage and horizontal stabilizer exhibited substantial damage. Examination of the propeller and propeller hub components revealed no evidence that the propeller blade fractured before the hub failed. The propeller hub fractured due to fatigue cracking that initiated at a network of corrosion pits along the surface of the propeller blade root seat. The internal tube exhibited a rough surface texture and an approximate 45° slant orientation. Tube material adjacent to the tube fracture had thinned and exhibited deformation in multiple locations. The periphery of the angled root seat exhibited chatter marks on the root of the propeller blade. Based on the characteristics of the fracture surfaces and the chatter marks, it is likely that the fatigue cracks propagated due to high-cycle rotational and vibrational loads from normal propeller operation. Due to the nature of the high-cycle fatigue and the inability to determine the loads and rpms of the propeller during the accident flight, the investigation could not determine exactly when the fatigue cracking initiated. Examination of the corrosion pits found elements in them consistent with common salts. The tight fit of the blade roots against the hub seats could have led to crevice corrosion if moisture and salt had penetrated the area. In addition, contact with some composite components (such as carbon fiber) can create galvanic couples with aluminum, which will become susceptible to preferential corrosion. Based on the evidence, it is likely that the corrosion pitting along the propeller blade root seats led to the initial cracking, which was propagated by high-cycle fatigue. Further, it is likely that the propeller hub design was not adequate because it did account for the repetitive stresses that occur during normal operation.
Probable cause
The fracture of the propeller hub due to corrosion pitting along the propeller blade root seat, which led to cracking that was propagated due to high-cycle fatigue.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR18LA158
- Event ID
- 20180531X25340
- Case number
- WPR18LA158
- 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: 22079993a155c321dfdc5f2ddf797b635b687c18774d989340e01893a0e8cb0a; retrieved 2026-09-16T07:20:44.080Z.