ERA17FA038 · Quad City CHALLENGER II
Juguetes Quad City CHALLENGER II · Accident: aircraft structural failure while maneuvering
From Skinners Wholesale Nursery Airport (16FD) to Skinners Wholesale Nursery Airport (16FD)
Event
- NTSB case
- ERA17FA038
- 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
- 2 · 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
Quad City CHALLENGER II
- Aircraft type
- Quad City CHALLENGER
- 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
- N327SH
- Operator
- Juguetes
- Onboard fatalities
- Unknown
- Route
- From Skinners Wholesale Nursery Airport (16FD), Crescent City, FLTo Skinners Wholesale Nursery Airport (16FD), Crescent City, FL
- Aircraft age
- About 8 years (built 2008)
- 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
- Maneuvering · low-altitude flying
- 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
- Aircraft structural 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
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft structures
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot and flight instructor were conducting an instructional flight in an experimental amateur-built airplane about 3/4 mile east of the departure airport in light winds with no adverse weather nearby. The investigation could not determine which of the pilots was flying the airplane at the time of the accident. One witness reported hearing the engine noise decrease before seeing the airplane descend and then abruptly pitch up and hearing the engine noise increase. He then heard a loud sound and saw a wing separate from the fuselage. Subsequently, the airplane entered an uncontrolled descent and impacted trees and terrain. Another witness reported seeing the airplane flying overhead and hearing the engine running. He also saw a parachute trailing behind the airplane while it was descending.
Examination of the wreckage revealed that both the forward and aft right wing "Rony" attachment brackets had failed. The brackets were separated from the root tube and the root tube was fractured on all four sides at the aft wing attachment bracket mounting holes. All the attachment brackets and root tube fracture surfaces were consistent with overload failure and showed no evidence of preexisting damage, cracks, or corrosion. Examination of the engine revealed no evidence of any preimpact mechanical failures or malfunctions that would have precluded normal operation. Although the ballistic recovery airframe parachute system was found deployed, the airplane impacted tress before the parachute could inflate.
The airplane had been involved in a hard landing about 1 week before the accident. Two days before the accident, the student, who had previously been an airplane mechanic in the U.S. Navy, replaced a steel cable between the two landing gear legs, which had been broken during the hard landing. However, no evidence was found indicating that the hard landing or the repairs contributed to the failure of the right wing attachment brackets and subsequent wing separation.
Although the toxicology testing of specimens from the flight instructor detected hydrocodone in the liver, the investigation could not determine whether the flight instructor's use of hydrocodone before the flight contributed to the accident. Although ethanol was detected in the student's muscle, it was not detected in the liver, and no n-propanol was detected in the liver, which is consistent with postmortem production of ethanol.
Given the witness's statement and the wreckage evidence, it is likely the airplane was pitched up abruptly following a descent, which resulted in the in-flight separation of the right wing and the subsequent uncontrolled descent.
Probable cause
An abrupt pitch-up maneuver following a descent, which resulted in the in-flight separation of the right wing due to the overload failure of both the forward and aft right wing attachment brackets.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA17FA038
- Event ID
- 20161109X11027
- Case number
- ERA17FA038
- 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: 0c6e1de6164f6849efd42d825d4143a452848b39e2fc67bae42c25178987059f; retrieved 2026-09-14T22:02:08.899Z.