- For other uses, see Vigilant.
Service history and disposition
On 53550.8, Captain Jean-Luc Picard of the USS Enterprise-E received a warning about an impending Borg attack on Starbase 612 from Captain Thaddius Deming of the USS Premonition, a ship from a possible future. The Enterprise altered course to investigate. (ST video game: Armada mission: "Premonitions")
Arriving on stardate 53551.3, the Enterprise-E found the USS Vigilant adrift near Starbase 612 following a surprise attack by the Borg Collective. Captain Picard had away teams transport to the Vigilant and the rest of the derelict fleet. The Vigilant returned to duty in time to ward off further Borg attacks and destroy their base in the sector. (ST video game: Armada mission: "Dark Omens")
Six months later, 2377, Starfleet suffered an attack by Gul Kentar's insurrectionist forces in the Pearl Nebula, and defended the galaxy during the Borg Invasion of 2377 and a Species 8472 incursion. The Vigilant was one of the ships involved in combat. (ST video game: Armada II)
|Facilities and starships assigned to Starbase 612|
|space stations||Mining Station Alpha • Starbase 312 • Starbase 612 • Tessen Prime Shipyard|
|starships||Protégé • Spitfire • Vigilant • Wolverine|
|Ships named Vigilant|
|Federation, Starfleet||USS Vigilant (Miranda-class) • USS Vigilant (Defiant-class) • USS Vigilant (NCC-94794, Vigilant-class escort prototype) • see also: Vigilant-class escort/scout|
|Klingon Empire, Klingon Defense Force||IKV Vigilance (F5-class bird-of-prey frigate)|
|Romulan Star Empire, Romulan Imperial Fleet||IRW Vigilance (D'deridex-class warbird)|
|Cardassian Union||CDS Vigilant (Keldon-class)|
No specific history or definitive final fate was established for this vessel in the Armada series as its name was selected for a destroyer by the Armada series game developers, and is placed randomly most times the ship appears.