Starfleet Records. United Earth starships: Enterprise (NX-01). Brief cancellation and missions afterward: By March of 2152, ten months after launching, Enterprise had engaged in armed conflicts with more than a dozen species. That month, the ship's mission was canceled when one of its shuttlepods appeared to have ignited tetrazine gas within the atmosphere of Paraagan II, killing 3,600 innocent colonists. It was this event, along with the ship's actions at other planets including P'Jem and Tanda

Starfleet Records. United Earth starships: Enterprise (NX-01). Brief cancellation and missions afterward: Remembering some parts of: ENT: "Shockwave, Part II" Star Trek. Live the experience. | Starfleet Command

Starfleet Records. United Earth starships: Enterprise (NX-01). Early missions: The phase cannons were not installed until September 2151, while Enterprise battled an unknown enemy. Source: ENT: "Silent Enemy". Star Trek. Live the experience. | Starfleet Command

Starfleet Records. United Earth starships: Enterprise (NX-01). Missions afterward: The ship, heading towards a plasma eddy which gradually increased the turbulence felt aboard the craft, was successfully sabotaged by its crew, and the worsening shipboard conditions influenced the Takret Militia to withdraw. The vessel was in danger of being ripped in two by the plasma eddy when the craft finally veered away from it. Shortly thereafter, Enterprise managed to leave the storm earlier than expected,

Starfleet Records. United Earth starships: Enterprise (NX-01). The beginning of the mission. The historical significance of Enterprise was related in a drawing of the ship that hung in Archer's ready room; the image was part of a series of drawings depicting the historical lineage of ships called Enterprise. Source: Enterprises series. Star Trek. Live the experience. | Starfleet Command

Starfleet Records. United Earth starships: Enterprise (NX-01). Brief cancellation and missions afterward: Captain Archer was able to convince the Starfleet Command Council and the Vulcan High Command to allow Enterprise to continue, particularly after it was revealed that the accident had been triggered by the Suliban Cabal. Source: ENT: "Shockwave", "Shockwave, Part II". Star Trek. Live the experience. | Starfleet Command