FANDOM


Z-95 Headhunter

Content approaching. Star Wars: Dark Times—Fire Carrier–class.

Parts of this article have been identified as no longer being up to date.

Please update the article to reflect recent events, and remove this template when finished.

Onkya was a Mon Calamari Jedi youngling who served the Jedi Order and escaped Order 66 with K'Kruhk and Chase Piru.

BiographyEdit

Clone WarsEdit

Onkya was a Mon Calamari who was a member of the Soaring Hawkbat Clan. The clan was stationed a the Bogden Jedi Training Facility on Bogden 3. They were awaiting transport back to the Coruscant Jedi Temple, which had been delayed due to the battle there. When masters K'Kruhk and Sian Jeisel arrived with their clone troopers, Order 66 was issued. Several of the younglings were killed as Du Mahn defended them. K'Kruhk and Piru ultimately escaped with half a dozen younglings to parts unknown. Two months afterwards, Onkya was living with the group of younglings in exile under the tutelage of K'Kruhk.

Great Jedi PurgeEdit

Onkya was present when Lumbra and his men came to the youngling's camp. When they noticed that the broken ship had a piece that they needed, Lumbra proceeded to take it. As he approached the ship, fellow youngling, Seddwia, jumped at him saying that it was their ship and to leave it alone. Lumbra grabbed Seddwia by the arm and pulled her away, starting a conflict. Chase Piru jumped to her rescue, but was shot and believed dead. When Lumbra realized they were Jedi younglings, they were chained up and on their way to be turned into the Empire.

The younglings were freed by K'Kruhk who gave in to un-Jedi like behavior briefly. With the help of Chase Piru, he shot down Lumbra's men with arrows. Lumbra and his shipmate, Callow, died at the hands of K'Kruhk's lightsaber.

AppearancesEdit

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.