Fandom

Wookieepedia

Unidentified Rebel scanner operator

135,091pages on
this wiki
Add New Page
Talk0 Share
Queicon

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.


"Incoming starship."
―The scanner operator when the Tyrant is approaching the Champion[src]

An individual was serving as a scanner operator and technician in the fleet of the Alliance to Restore the Republic during the Galactic Civil War, a conflict between the Alliance and the Galactic Empire. During the Battle of Hoth between the Empire and Alliance on and above the planet Hoth[1] in the year 3 ABY,[2] the individual was serving onboard the Mon Calamari cruiser Champion. As the Champion was about to leave Hoth, the scanner operator picked up an incoming starship on sensors. The starship was further identified by three other technicians as the Imperial I-class Star Destroyer Tyrant. The captain of the Tyrant, Xamuel Lennox, ordered the Captain of the Champion to hand over Rebellion General Crix Madine, who had been recently rescued from the Tyrant by Rebel commandos. The Champion's captain refused to comply, starting a battle in which the Champion was eventually able to escape to hyperspace and reach the Rebel's rendezvous point.[1]

Behind the scenesEdit

The Rebel scanner operator briefly appeared in the mission text of the third scenario of the light side campaign from The Price of Victory, which was released in 2010 as the eighth set of the Star Wars Galaxies Trading Card Game.[1]

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 SWGTCGsmall Star Wars Galaxies Trading Card GameThe Price of Victory (Light Side scenario campaign)
  2. The New Essential Chronology places the events of the Battle of Hoth in 3 ABY.

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.