Kakita Himatsu 
Born: Unknown 
Died: 1166, Month of the Boar [1]

Kakita Himatsu was a scout bushi and bloodspeaker of the Crane Clan.

Blood Hunt Edit

In 1166 Iuchiban forced his servants to action, driving them to self-destructive acts of chaos. Himatsu began to hear his master's voice in his mind, and hardly endured without being noticed by his fellow Cranes. Himatsu was north of the Spine of the World Mountains hunting his bloodspeaker brethren, alongside with Daidoji Kitagi and Daidoji Akimasa. There they discovered a newly formed passage between realms. [2]

Maigo no Musha Edit

Akimasa returned to ask for reinforcements to secure the passage, and to study it, while Himatsu and Kitagi guarded it. Kitagi's father had died in Oblivion's Gate, and wished to enter into the passage to see what had been the fate of his father. Himatsu readily joined him, and once they had into it, the Heartless voice in his mind disappeared. Himatsu decided not to leave this place, which granted him freedom from his master commands. [2]

Death Edit

They were found by the realm's guardian, Sanzo, who explained they were at Maigo no Musha, the Realm of the Twarthed Destiny. Their presence weakened the boundaries of the realm, requesting them to leave, but Himatsu drew his sword, empowered with maho and threatened Sanzo. From the darkness appeared a shadow, which quickly overcame and fatally wounded Himatsu. He was an alternative Daidoji Uji, the Iron Crane, which had arrived from a nightmare world. All them left Maigo no Musha, and Uji's shadow had been careful to deadly wound Himatsu, but he did not die quickly. [2]


  1. Four Winds, p. 122
  2. 2.0 2.1 2.2 Flight from Darkness, by Shawn Carman

Crane This Crane Clan related article is a stub. That means that it has been started, but is incomplete. You can help by adding to the information here.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.