# Accident 20160917018729A: Alex Michael Bantum/Tercel USA TERCEL-GYROPLANE, Blairstown, NJ, September 17, 2016

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: September 17, 2016, 11:45 local time
- Place: Blairstown, NJ
- Airport: Blairstown
- Damage: Substantial damage
- Phase of flight: Takeoff: Departure Roll
- Operating rules: General operating rules (Part 91)
- Location: 40.9711° N, 74.9975° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=40.9711&lon=-74.9975&mi=10
- Aircraft: N528WM, registered now (https://openairdocs.org/aircraft/N528WM) (OpenAirDocs)
- Registry model: Alex Michael Bantum/Tercel USA TERCEL-GYROPLANE (registry code 05633NF, https://openairdocs.org/model/alex-michael-bantum-tercel-usa-tercel-gyroplane) (OpenAirDocs)
- Registry engine: Rotax 912UL series (registry code 55571, https://openairdocs.org/engine/rotax-912ul-series) (OpenAirDocs)
- Reported make and model: ALEX MICHAEL BANTUM/TERCEL USA TERCEL-GYROPLANE
- Reported engine: ROTAX 912UL
- People aboard: 1
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Private pilot
- Pilot flight hours: 118 total, 20 in this make and model, 10 in the last 90 days
- NTSB investigation: [NTSB GAA16CA499](https://openairdocs.org/ntsb/GAA16CA499) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20160917018729A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

THE PILOT STATED THAT HE POSITIONED THE AIRCRAFT ON RUNWAY 25 TO PRACTICE TAKE-OFF AND LANDINGS AND ENGAGED THE BREAKS.  HE BROUGHT THE STICK VERTICAL AND THEN GRADUALLY ENGAGED THE PRE-ROTATOR AND BROUGHT THE ROTOR RPM TO 180.  AT THAT POINT HE DISENGAGED THE PRE-ROTATOR, RELEASED THE BREAK, AND WENT FULL THROTTLE.  THE PILOT STATED THAT THIS IS WHERE HE MADE THE MISTAKE BY NOT BRINGING THE STICK ALL THE BACK OR FULL AFT.  AS A RESULT THE AIRCRAFT ACCELERATED BUT THE ROTOR RPM STARTED TO DECREASE AS THE STICK WAS NOT BACK.  AS AIRCRAFT PICKED UP SPEED, THE PILOT STARTED TO BRING THE STICK BACK, BUT THE ROTOR HAD SLOWED DOWN.  THE RESULT WAS LIFT DIFFERENTIAL BETWEEN THE ADVANCING AND RETREATING BLADES WHICH INDUCED BLADE FLAP.  THE PILOT STATED THAT THE STICK BECAME UNCONTROLLABLE AND THE AIRCRAFT DEPARTED THE LEFT SIDE OF THE RUNWAY ONTO THE GRASS.  THE PILOT CUT THE POWER TO IDLE AS LEFT LANDING GEAR AND THE NOSE GEAR CAME OFF AND THE ROTOR HIT THE GROUND.

THE AIRCRAFT CAME TO A STOP INTACT AND UPRIGHT, RESTING ON CHIN BUBBLE. THE LEFT GEAR LEG BENT AFT SLIGHTLY.  THERE IS FUSELAGE AND CLAMP DEFORMATION AT LEFT GEAR MOUNT SADDLE AND THE WHEEL ASSEMBLY BROKEN OFF AT AXLE. NOSE GEAR MOUNT STRUCTURE WAS TORN OUT, NOSE TUBE SWUNG AFT THROUGH BELLY SKIN, AND THE NOSE WHEEL IS MISSING. BOTH ROTOR BLADES EXHIBIT LEADING EDGE DAMAGE AT TIP AND OVERLOAD "S" BENDING. ROTOR BLADE YOKES EXHIBIT SCORING FROM ADJACENT STRUCTURE. ROTOR GIMBAL BELLCRANK ATTACHMENT BOLTS (2 OF 3) FAILED IN OVERLOAD.  THE LEFT GIMBAL CONTROL ROD NOW DISPLACED FROM CENTER OF FUSELAGE CLEARANCE HOLE TO BEYOND EDGE INDICATING DAMAGE TO ROTOR MAST SUPPORT STRUCTURE (DISPLACED RIGHT).  THE STICK CONTROLS CONTINUOUS AND CORRECT TO ROTOR GIMBAL BELLCRANK. RUDDER AND ENGINE CONTROLS CONTINUOUS AND CORRECT. BRAKE SYSTEM IS COMPROMISED BY DAMAGE TO LEFT GEAR.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB GAA16CA499](https://openairdocs.org/ntsb/GAA16CA499), Sep 17, 2016: Alex Michael Bantum/Tercel USA TERCEL-GYROPLANE (N528WM), Blairstown, NJ, substantial damage. Probable cause: The student pilot’s incorrect takeoff procedure, which resulted in a loss of main rotor rpm and the subsequent loss of directional control and runway excursion.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.