FTW90DPA05 · Gyroflug SC01B160
Gyroflug SC01B160 · Accident: airframe, component or system failure on approach
Event
- NTSB case
- FTW90DPA05
- 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
Gyroflug SC01B160
- Aircraft type
- Gyroflug SC01
- 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
- N3412L
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- 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 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 base
- First occurrenceThe 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
- Airframe, component or system failure
- 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
- Other maintenance personnel › Maintenance, installation, improper
- Propeller system/accessories, blade › Separation
- Propeller system/accessories, prop blade retention › Failure, total
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE HAD BEEN MODIFIED TO BE FLOWN EITHER REMOTELY OR BY THE PILOT. TAKEOFF AND INITIAL CLIMB WERE PERFORMED BY REMOTE CONTROL AND CONTROL WAS TRANSFERRED TO THE PILOT TO POSITION FOR A REMOTE CONTROL LANDING. ANGLE OF BANK INCREASED PAST 90 DEGREES IN A NOSE HIGH ATTITUDE AT ABOUT 425 FEET AGL; THE PILOT TRANSMITTED THAT HE WAS 'GOING DOWN' SHORTLY BEFORE IMPACT. ONE OF THE THREE WOODEN PROPELLER BLADES SEPARATED FROM THE HUB AND WAS FOUND 1/4 MILE FROM THE MAIN WRECKAGE. THE BLADE WAS ATTACHED TO THE HUB PRIMARILY BY 5 LAG SCREWS. THREADS IN THE WOOD BUTT OF THE SEPARATED BLADE WERE STRIPPED. THE 5 SCREWS REMAINED IN PLACE. LAG SCREWS IN THE REMAINING 2 BLADES WERE FOUND UNDERTORQUED. SEVERAL DISCREPANCIES WERE NOTED REGARDING SPECIFICATIONS FOR PROPELLER BLADE ROOT AND SIZE, TOLERANCES, AND LAG SCREWS.
Probable cause
TOTAL PROPELLER BLADE RETENTION FAILURE, THE RESULTANT SEPARATION OF ONE PROPELLER BLADE, AND THE IMPROPER INSTALLATION OF THE PROPELLER BY UNKNOWN MAINTENANCE PERSONNEL.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW90DPA05
- Event ID
- 20001212X23406
- Case number
- FTW90DPA05
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: a19cf3d07353080ef266b9ebafa35cc2e47602e44bf2f336b3f5b3b0143b504c; retrieved 2026-09-21T02:35:33.024Z.