Fandom

The Youtube Poop Wiki

Gwonam's X-wing

2,441pages on
this wiki
Add New Page
Comments0 Share
Gwonam's X-wing

Gwonam's T-65 X-wing.

Gwonam's X-wing was a Rebel starfighter that Gwonam purchased for personal use.

BackgroundEdit

The starfighter is an Incom T-65 X-wing Space Superiority Starfighter that was purchased on eBay by Gwonam for about 149,000 credits. It was bought used from an unknown seller.

UseEdit

After its delivery to Hyrule Castle, the X-wing was taken by King Harkinian for a joyride. Harkinian flew the starfighter into direct combat with a Star Destroyer and eventually made an impossibly accurate hyperspace jump into the Death Star's access port. Inside the Death Star, Harkinian was chased by a squadron of TIEs, forcing him to begin evasive maneuvers. In such cramped space, he banged the ship several times against the wall. Miraculously enough, it didn't cause any damage to the X-wing.

Later, the X-wing was 'borrowed' by Gwonam's twin brother Namowg as a means of transportation from an unknown planet to the planet where Hyrule Castle is located.

Final FlightEdit

A few months after the events of The Return, Harkinian takes the X-wing on an escapade yet again, this time to aid Lucy Wild against Gru and his minions on the island of Dorikai. Partway through the flight to the island, Gwonam teleports Harkinian out of the cockpit and back to the castle, angry that Harkinian stole his prized fighter a second time. Gwonam's R3 unit R3-Z17 was attached to the fighter's astromech droid socket. However, due to the R3's faulty wiring, it was not able to pilot the ship back to Hyrule Castle. The X-wing fell out of orbit and crashed into the planet, destroying R3-Z17 in the process.

Harkinian in the Death Star

Harkinian being chased by two TIE Fighters inside the Death Star.

Namowg in Gwonam's X-wing

Namowg in Gwonam's X-wing.

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.