Fandom

Wookieepedia

Auzituck anti-slaver gunship

134,554pages on
this wiki
Add New Page
Talk0 Share

The Appazanna Engineering Works Auzituck anti-slaver gunship was a Wookiee gunship used to battle slavers.[1] The interiors were made from wroshyr trees, with sap serving as glue.[3] One such vessel, serving as a freedom fighter against the Galactic Empire, was contracted to meet with the crew of the Ghost by Cikatro Vizago. But by the time it arrived, it had been raided by Trandoshan slavers and left adrift, and the crew had been sold to the Empire. Another gunship later rendezvoused with the Ghost to recover the Wookiee crew they had rescued.[4] The Wookiee bounty hunter Black Krrsantan also owned his own Auzituck gunship during the Galactic Civil War.[5]

Behind the scenesEdit

The Auzituck anti-slaver gunship first appeared in Star Wars Rebels: Spark of Rebellion, the one-hour premiere for the animated television series Star Wars Rebels. The name "Auzituck" dates back to the May 1973 rough draft of what ultimately became Star Wars: Episode IV A New Hope. In scene 135 of that script, which was set in the "Wookee [sic] camp," an early version of Chewbacca was greeted by his father, Auzituck, Chief of the Kaapauku tribe.[6]

The young readers book Star Wars Rebels: Head to Head, written by Pablo Hidalgo and featuring various match-ups from the series, placed a patrol gunship against an Imperial freighter, with the gunship damaging the freighter and escaping.

In the episode Peril on Kashyyyk of LEGO Star Wars: The Freemaker Adventures, Wookiees use the gunships to raid a Trandoshan prison camp.[7]

The ship, particularly the distinctive bubble cockpits, resembles the real-life Mi-24 Hind Helicopter, much like the LAAT.

AppearancesEdit

Non-canon appearancesEdit

SourcesEdit

Notes and referencesEdit

In other languages

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.