Thursday 14 January 2016

Jukendo Kata: Mokuju vs Tanken #3 銃剣道 形 (木銃と短剣)


  • Starting from 9 steps apart.
  • Ju takes a geidan aimed at Tans front knee
  • Tan covers with a twist of the forearm anticlockwise to cover over the top of the gun. At the same time leans a long way forward. The tanken blade is a long way to the horizontal at this point. Maybe 30 degrees off horizontal. The mokuju is almost in the centre of the blade length.
  • 3 steps in each
  • Tan pushes forward (seme) applying attacking pressure to the top of the gun
  • Ju evades with a step back and right, simultaneously lowering the barrel to and swinging the butt right up to his cheek to avoid the tanken.
  • Ju strikes nodo (throat)
  • Ju does hiki nuki zanshin (big step out followed by a lowering of body weight and a covering of Tan's wrist)
  • Return to chudan
  • Take a few steps back to middle point slowly moving back into kamae at the same time
  • Drop weapon point down releasing pressure on opponent, At this Tan's back hand goes down as well.
  • 5 steps back
  • Return to Chudan, Tan's back hand comes up to hold the (imaginary) bayonet scabbard

Important Points:
  • Timing of the seme by Tan. Tan walks in One, Two, Threeeeee, pressure. It is quite a huge push in but not so that balance is lost or any more steps are needed. There is a slight lowering of the tanken towards the mokuju
  • The nuki waza has the unusual lifting of the butt because Tan can push in so far due to the weight being forward. If Tan doesn't push in so far as to force this movement then it looks a bit silly.
What we did wrong ():
  • Overall speed is too fast. This one in particular was way too fast.
  • All in all when Ewa has the mokuju I can't see much big stuff wrong with it. Speed, balance and crispness but I think technically correct.
  • When I have the mokuju we don't return to centre, aside from that I think it is, as Sensei says "Almost Okay".
  • Still using naginata footwork when I have the mokuju and return to centre and therefore probably wrong.

No comments:

Post a Comment