Isawa Hibana 
Isawa Hibana 
Born: Unknown 
Parents: Isawa Miko

Isawa Hibana was a fire shugenja of the Phoenix Clan. Her mother was Isawa Miko. [1]

Colonies Edit

In 1199 Hibana and Ikoma Yamahatsu took the nun Aranai into custody and brought her back to the Second City. Aranai had killed the Defender of the Second City Asako Karachu in a duel, suffering the disparagement of an entire city. Hibana wished to know what really happened in the duel, and entrusted Asako Ifukube for the task, [2] while Yamahatsu appointed Ikoma Ayumi. [3]

Prodigy Edit

Isawa Hibana 2

Isawa Hibana

Hibana returned to mainland Rokugan, assigned to Toshi Ranbo. In 1200 in the Ichidou District she performed a magical display that amazed all the witnesses, including Master of Water Asako Miyabi and Master of Fire Isawa Koiso. [4] An Acolyte of Fire, Hibana backed Master of Fire Isawa Koiso in her endeavors against the Unicorn aggression, and she was convinced the Phoenix would excise the spiritual threat within the Moto family. Hibana was also aware that the Dragon knew something that concerned them greatly. [5]

Rise of Jigoku Edit

In 1200 in the Month of the Dog, Hibana, Hida Tadama, Tsuruchi Kinuyo, Daidoji Sakuzou, Ikoma Masaru, Tonbo Inuyama, Kuni Sango and Shosuro Yoshiyuki found evidences of an impeding Spider attack near Cold Wind City. The village was evacuated before the Battle of the Second Seal began. [6]

External Links Edit

Sources Conflict
The sources relating to this article are in conflict with each other.
2013 Kote Results page claims Isawa Hinata took Aranai hostage, so most probably Hibana was a typo in the fiction. Oni no Pikachu (talk) 18:26, September 11, 2014 (UTC)


Phoenix This Phoenix 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.