also known as: Nollie BS Bigspin

spin flatgroundstreet difficulty 6/10

Sign in to add this trick to your list.

roll 0° yaw 0° pitch 0° body 0°

Shown for a regular-footed rider riding nollie. Teal ring + arrow = the rider's facing direction; teal band = the tail; a dot is where a hand holds the board - bright yellow for the front hand, amber for the back one, which is the whole difference between a mute and an indy. Board and rider rotate independently - each follows its own component. Unlock the camera (top right) to drag the view around.

How it works

A bigspin popped from the nose that turns backside: the front foot snaps the nose and pushes it out in front of the toes and round, so the board wraps 360 degrees backside while the body turns 180 backside, landing fakie. Pushing a full turn from the nose while starting the body's turn makes the timing far tighter than the regular or fakie versions - the front foot must finish its push before the turning hips pull it off line. The frontside one, scooped behind, is the easier way round off the nose.

Step by step

  1. Roll in nollie position with the front foot deep in the nose pocket, shoulders slightly wound frontside.
  2. Snap the nose and push it out in front and round through a full backside turn.
  3. Release the shoulders backside and turn the body 180 as the board spins.
  4. Keep the hovering back foot above the deck's pivot through the wrap.
  5. Catch with both feet as rotations complete and land rolling fakie.

Body mechanics

Front footDelivers the nose pop and the full push round, then turns with the body to the catch.
Back footHovers level, tracking the spinning deck, and catches first.
ShouldersFrontside pre-wind, backside release synchronized to the nose snap.
ArmsCompact and quick; there is little hang time to correct.
GazeDown at the wrap, then over the shoulder to the fakie landing.

Delete this comment?

Discussion

Sign in to join the discussion.

No comments yet.

Something wrong with the Nollie Bigspin?

No account needed. Say what's wrong and, if you can, what it should be - a source helps a lot. If you know exactly what the fix is, proposing the edit directly gets it in faster.

What kind of problem?