Fandom

Wookieepedia

Attack on the Pica Rim Pipeline

135,485pages 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.

"Rescue workers have been working around the clock to reach some 4,000 passengers and workers who were trapped in a monorail traveling through the Pica Rim Pipeline alter a series of bombs ruptured a 4,000 kilometer section of the undersea transit tube."
―A Colonial News Nets report[src]

An attack on the Pica Rim Pipeline took place in 2 ABY on the planet Albrae-Don, during the Galactic Civil War. The terrorist group Justice Action Network bombed the Pica Rim Pipeline, a large underwater transportation system that lined the floors of the planet's oceans, in protest of the execution of its leader: Earnst Kamiel. A series of bombs ruptured and flooded a 4,000 kilometers section of the structure. Some 4,000 passengers were trapped in a monorail traveling through the Pipeline. Rescue workers were sent to save them but they were difficult to reach and the monorail was not designed to withstand the pressure of tons of water, making the passengers' situation critical.

AppearancesEdit

Notes and referencesEdit

  1. 1.0 1.1 SWAJsmall "Galaxywide NewsNets"—Star Wars Adventure Journal 10
  2. SWAJsmall "Galaxywide NewsNets"—Star Wars Adventure Journal 11
  3. The Essential Atlas states that the Battle of Yavin occurred in year 35, which is the zero point of the BBY/ABY year-notation system, so the difference between the calendar based on the Battle of Yavin and the Great ReSynchronization's year-notation system is thirty-five years. This date is derived from simple math based upon other confirmed dates.

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.