Fandom

Wookieepedia

Battle of Celanon

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

The Battle of Celanon was a conflict between the Galactic Empire and New Republic in 13 ABY at Celanon. Under the command of Admiral Gilad Pellaeon, the Imperial forces had been pushed back in an attempt to contain an invasion of Imperial space. During the battle, Pellaeon lost his command ship, the Star Dreadnought Reaper.

BackgroundEdit

Following the New Republic victory against Moff Getelles of the Antemeridian sector, the New Republic pushed through the neutral Borderland Regions toward the Hydian Way, border of the Imperial Space. The Moffs of the Imperial Remnant, fearing the shift of power in the region, ordered Admiral Gilad Pellaeon to move his forces across the Hydian Way.[1] Torn away from his campaign against the planet Adumar, Pellaeon brought his forces into the fight against the New Republic.[2] The losses he inflicted on the New Republic were substantial, but Pellaeon was pushed back.[1]

The battleEdit

At Celanon, he once again engaged New Republic forces. He was not able to secure a victory, however, and lost his command ship, the Star Dreadnought Reaper.[1]

AftermathEdit

In the wake of Celanon, the New Republic refrained from pushing its advantage and halted the invasion. The New Republic had increased its power in the Borderland Regions, but the Empire didn't have lost territory. This battle was followed by four years relatively peaceful between the two factions.[1]

SourcesEdit

Notes and referencesEdit

Galactic Civil War
(2 BBY19 ABY)
The Post-Reborn Empire (11 ABY14 ABY)

Adumar and the Nam Chorios crisis – 13 ABY

Borderland Regions campaign
(13 ABY)

Lucazec · Barison · Arda · Quell · Celanon

Restored Empire crisis – 13 ABY

Related topics and articles

New Republic · Imperial Remnant

  [Source]

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.