Bunkai From Tekki/Naihanchi (Chul Gi) With Cross Reference To Wing Chun

Most Karate systems that evolved from the Okinawan style of Shuri Te tend to use big steps to capitalise on forward body momentum and inertia to transfer impact into the opponent. As a broad generalisation, this tends to distinguish them from the styles derived from Naha Te and most styles of Kung Fu which prefer the use of circular (or centrifugal) force for generating power.

However, the Tekki kata’s (called Naihanchi in some styles and Chul Gi in Korean) which are still present in many Shuri Te derived styles contradict this forward momentum method in that they are not very mobile and are far more “static”. Another characteristic of the Tekki kata’s is that they make more use of a punch with the palm facing up as opposed to the usual “cork-screw” punch where the fist ends up facing downwards and the arm is not fully extended.

Tekki is obviously a close quarters fighting kata. As such a number of its movements are quite close to Wing Chun Kung Fu which specialises in close quarters fighting. On the surface, Wing Chun and Tekki look quite different, but as usual Keith and I look below the surface and find some similarities which can be used by practitioners of either system.

Tekki / Naihanchi Kata Bunkai

___________________________________________________________________________________

4 UNIQUE EBOOKs

Multiply your effectiveness with more impact for less effort and where to hit for best effect.

Bonus: Historical look at Bassai Dai, one of Karate’s most pivotal katas

___________________________________________________________________________________

 

 

2 thoughts on “Bunkai From Tekki/Naihanchi (Chul Gi) With Cross Reference To Wing Chun

  1. Hi Niel
    Thanks for your kind words. We will certainly be working our way through most of them 🙂

  2. I love this! It is so insightful to have 2 different styles working together to provide bunkai! I hope you guys do something like this for every kata!

Leave a Reply

Your email address will not be published. Required fields are marked *