RARRRRRR! This article should be wookified to fit within the style of Wookieepedia. Please follow the guidelines in the Manual of Style and How to edit a page.

The title of this article is conjectural. Although this article is based on canonical information, the actual name of this subject is pure conjecture.

Previous Duel on Cloud City[1] Occupation of Bespin[1] Battle of Dathomir Battle of Dubrillion Next Mission to Ord Mantell Skirmish at the Rebel Rendezvous path Conflict Galactic Civil War[1] Date 3 ABY[1] Place Rebel Fleet Rendezvous path[1] Outcome Rebel victory, The Rebel fleet altered their course as a precaution[1] Combatants Rebel Alliance[1] Galactic Empire[1] Commanders Commander Wedge Antilles[1] General Crix Madine[1] Leia Organa Strength Rogue Squadron[1] 6 T-65 X-wing starfighters[1] 1 Imperial Strike Cruiser[1] 9 TIE/In starfighters Casualties All Imperials destroyed[1] [Source]

The Skirmish at the Rebel Rendezvous path, fought in 3 ABY, was a brief conflict between the Rebels and the Empire that occurred when the Rebel Fleet were following the path to the Rebel Rendezvous point.

PreludeEdit

Shortly after the disasterous results of the Battle of Hoth, the Rebel Fleet was to move towards the rendezvous point to regroup. In addition, they also were travelling to Tatooine so they could commence a rescue mission for Han Solo after he was captured at Bespin.

SpottedEdit

While travelling to the rendezvous point, the Rebel Fleet picked up a ship approaching that might be hostile, a ship they suspected was of Imperial origin. Suspecting that the size of their fleet made a big enough blip on the scanners to have one find them by chance, the fleet diverted to intercept. Because Luke Skywalker was still recovering from his injuries at Bespin, Wedge Antilles was placed in command of Rogue Squadron. Shortly thereafter, the Rebel fleet confirmed that the ship is an Imperial Strike Cruiser, and thus Rogue Squadron was deployed to intercept and destroy the cruiser so it won't give away their position. The Strike Cruiser then deployed a squadron of nine TIE fighters to deal with Rogue Squadron so it could communicate to the Executor about spotting the Rebel fleet. However, the Rebel Fleet managed to jam the signal preventing the message from being sent. Rogue Squadron then managed to get into a dogfight with the TIE Squadron, to which Rogue Three ended up having his engine knocked out by a TIE before the latter was destroyed by Rogue Two. Eventually, the Imperial Strike Cruiser tried to make a break for it, and also diverted power to their rear shields in order to ensure that they aren't attacked from behind. However, Rogue Five exploited the fact that it had relatively little shielding on the front by firing at the front, destroying the Imperial Strike Cruiser.

AftermathEdit

Although the Rebel Fleet was successful in eliminating the Strike Cruiser, they ended up altering their course as a precaution in case it did successfully transfer its sighting of the Rebel Fleet to the rest of the Imperial fleet. This suspicion was confirmed when Darth Vader reported to Palpatine and told him that he received a report on a possible sighting of the Rebel Fleet, although the Emperor told Vader that it would have to wait, as he wants Vader to conclude shipping arrangements with Prince Xizor.

AppearancesEdit

• Shadows of the Empire 1 (First appearance)

SourcesEdit

• C-3PO: Tales of the Golden Droid

Notes and referencesEdit