FANDOM


Coronado
Coronado
The Coronado and two light ExoCarriers fighting the Neosapiens near Earth
Career


Faction Exofleet
Name Coronado
Class Light Exocarrier
Status Destroyed (Rebuilt)
Weapons and Defense
Armament
Fusion Torpedoes
Ships and Crew
Complement

HistoryEdit

The Coronado (†) was called into active duty in 2119 A.D. when the Homeworld Congress declared war on the Pirate Clans of Saturn. The Pirate Clans War was in response to Jonas Simbacca's Pirate Clan pillaging a civilian ore freighter, the Danube, which resulted in the death of one of its two crew members. In addition to the death of the Danube's crew member, an entire ExoFleet work crew was killed when a booby trap left by the pirates was accidentally triggered. The Coronado served in all engagements in the Pirate Clans War including the Battle of the Asteroid Belt and Battle of Enceladus.

The Pirate Clans War abruptly ended when the Neosapien Commonwealth surprise attacked and conquered the Homeworlds, violating their disarmament treaty they signed after the Neosapien Revolt of 2069 A.D. and the First Drej War of 2106 AD. In response, the Exofleet turned its full attention to freeing the Homeworlds from Neosapien oppression. The Coronado was destroyed in Exofleet’s first engagement of the Neosapien War, the Second Battle of Earth, in attempt to liberate the Homeworlds. It took several direct hits in its fusion torpedo tube from a Neosapien E-Frame, which ignited the rest of the armament in the Coronado and destroying it. The Coronado model of light ExoCarrier was never reintroduced during the ExoFleet-Pirate Clan Alliance fleet build-up, though there is one other light ExoCarrier with the Coronado model that served in the fleet until it was destroyed in the Third Battle of Earth. The Coronado was rebuilt after the war for the next war against the Drej.

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.