The USS Seine was a Federation Starfleet Danube-class runabout active in the late 24th century.


In the early 2380s decade, it was assigned to the starship USS Aventine.

In the year 2381, while the Aventine was investigating the wreck of the NX-class Columbia, the Caeliar Arithon killed Crewman Ylacam while he was logged in for maintenance. Arithon remained hidden aboard the Seine and used its microtorpedoes to blow out the shuttlebay and open a subspace tunnel by emitting a soliton wave. The Seine and Aventine passed through the tunnel to supernova remnant FGC-SR37-758 near the center of the Azure Nebula where Arithon hoped to find Erigol. However, the planet had been destroyed some time prior, and Arithon perished aboard the runabout. The Aventine received a distress call from the USS Enterprise-E and tractored in the runabout before departing. (ST - Destiny novel: Gods of Night)

The escape attempt was later investigated by Geordi La Forge to determine how to open and utilize the subspace tunnels; logs indicated that the runabout had emitted a triquantum wave from its deflector dish, something the Enterprise was not setup to do at the time. However, working with engineers from the Aventine, both ships were able to be equipped with similar capabilities. (ST - Destiny novel: Mere Mortals)


Danube-class runabouts
Federation, Starfleet AmazonBrahmaputraCamDanubeElestanEuphratesGanderGangesGeneseeGlyrhondHolanaHudsonHudson (2375) • InwoodIrrawaddyMarquandMattinglyMekongMississippiMissouriNCC-70310NCC-73918NileOrinocoPlatteRio GrandeRubiconSeineShenandoahSt. LawrenceSungariTecyrTiberVolgaYangtzee KiangYoljaYukonZambesi Ufp-emblem Starfleet Command logo
Terran Empire, Starfleet
(mirror universe)
DelawareHydaspesRunaboutVistula TerranEmpire
USS Aventine auxiliary craft
Ufp-emblem KangKolothKorMeuseUSS Seine Starfleet Command logo

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.