Memory Alpha

Captain's log, USS Enterprise (NCC-1701-D), 2367

42,246pages on
this wiki
Add New Page
Discuss0 Share

In 2367, numerous log entries were made on the captain's log for the USS Enterprise-D. (Star Trek: The Next Generation)

Entrants Edit

Entries Edit

Borg incident Edit

  • "Captain's Log, Stardate 44012.3. The Enterprise remains docked at McKinley Station, undergoing a major overhaul and refit following the Borg incident. I am confident that the ship and her crew will soon be ready to return to service." (TNG: "Family")

Diversion to Starbase 416 Edit

  • "Captain's Log, Stardate 44085.7. Due to a medical emergency we have been forced to cut short a two-day liberty on Ogus II and set course for Starbase 416. It seems a young man's practical joke has come dangerously close to a lethal conclusion."
  • "Captain's Log, Stardate 44091.1. We have been at Starbase 416 for three days. Young Willie Potts is responding well to treatment and has been returned to the Enterprise." (TNG: "Brothers")

Talarian Rescue Edit

  • "Captain's log, stardate 44143.7. We have moved into sector 21947 in response to a distress call from a Talarian observation craft. The alien vessel appears adrift, and our initial scans have detected a life-threatening radiation leak within its propulsion system."
  • "Captain's log, supplemental. We have completed an emergency evacuation of four Talarians and one Human. How this young man found himself in the company of these aliens remains a mystery."
  • "Captain's log, supplemental. Captain Endar's claim that Jeremiah Rossa is his son is clearly unacceptable. However, to avoid escalating tensions I have invited the Talarian leader to come aboard the Enterprise so that we may address the issue face-to-face." (TNG: "Suddenly Human")

Incident at Starbase 133 Edit

  • "Captain's log, stardate 44162.5. Two attempts to retrieve Dr. Crusher have failed. And now the Traveler – a mysterious visitor from our past – has reappeared."
  • "Captain's log, stardate 44162.8. At the direction of the Traveler, the Enterprise is returning to Starbase 133 and the precise position where the subspace bubble was formed." (TNG: "Remember Me")

Mission to Camus II Edit

  • "Captain's Log, Stardate 44215.2. The Enterprise has bypassed its scheduled archaeological survey of Camus II in response to a distress call from the Federation freighter Arcos which has assumed an emergency orbit around Turkana IV - birthplace of our late comrade, Tasha Yar."
  • "Captain's Log, Supplemental. We are in orbit above Turkana IV, an Earth colony that severed relations with the Federation nearly fifteen years ago. I'm concerned about sending an away team, but if we are to discover the fate of the two missing Federation crewmen I see no alternative."
  • "Captain's Log, Stardate 44225.3. Dr. Crusher has successfully removed Ishara's magnetic implant enabling the young woman to guide our rescue attempt. Without my intending it she has virtually become an active member of the crew." (TNG: "Legacy")

Encounter at Alpha Onias III Edit

  • "Captain's Log, Stardate 44286.5. The Enterprise is conducting a security survey of the Onias sector near the Neutral Zone. Despite our proximity to the Romulan territory, the mission has been quiet and uneventful." (TNG: "Future Imperfect")

Incident in the Gamma Arigulon system Edit

  • "Captain's Log, Stardate 44246.3. We're investigating radiation anomalies reported in the Gamma Arigulon system by the starship Lasalle. Preliminary readings are inconclusive."
  • "Captain's Log, supplemental. K'mpec, who ruled the Klingon Empire longer than anyone in history, is dead. We await the arrival of Duras and Gowron rivals for the leadership of the High Council." (TNG: "Reunion")

Mission to Pentarus V Edit

  • "Captain's Log, stardate 44307.3. I am preparing to leave by shuttlecraft for Pentarus V where I've been asked to mediate a dispute among the salenite miners, a contentious group unfortunately, prone to violence. But first, I must deal with a situation of a far more personal nature." (TNG: "Final Mission")

Disabled by quantum filamentEdit

  • "Captain's Log, Stardate 44356.9. Sensor diagnostics have been completed and indicate that all systems are normal. There remains no explanation for the images which appeared in our path."
  • "Captain's Log, Stardate 44359.5. What began as a curious inconvenience has turned into a serious threat. At current speed the two-dimensional beings and the Enterprise will be drawn into the cosmic string fragment in seven hours."
  • "Captain's Log, Supplemental. If our speed and course remain unchanged in one hour the Enterprise will be torn apart by the gravitational forces of the cosmic string fragment." (TNG: "The Loss")

Mission to Ventax II Edit

  • "Captain's Log, Stardate 44474.5. We have reached Ventax II and are attempting to contact the Federation science station, which at last report was under siege by an angry mob."
  • "Captain's Log, Supplemental. The claim this woman, who calls herself Ardra, has made upon my ship is clearly an empty threat. But she has further inspired my determination to expose her for the fraud she is." (TNG: "Devil's Due")

Supply run to the Guernica system Edit

  • "Captain's Log, Stardate 44614.6. We are approaching Starbase 313, where we will pick up a shipment of scientific equipment for transport to a Federation outpost in the Guernica system. During the journey, we will be hosting a special guest."
  • "Captain's log, supplemental. Since the newborn has attached itself to the hull, it has been making greater and greater demands on the ship's energy. But we have been able to stabilize our power systems temporarily." (TNG: "Galaxy's Child")

Search for the USS Brattain Edit

  • "Captain's Log, Stardate 44635.8. Four days have passed, but we have made little progress in solving the mystery of the Brattain. I have decided we should return to Starbase 220 and to that end, Commander La Forge is rigging the Brattain for towing."
  • "Captain's Log, Stardate 44639.9. We have now been adrift for a total of ten days. We have sent subspace distress calls, but because of our distant location, we cannot expect a response for at least another two weeks."

Sabotage of the Enterprise Edit

  • "Captain's Log, Stardate 44769.2. For some weeks we have had a Klingon exobiologist on board as part of a scientific exchange program. Unfortunately, we suspect that he was involved in a security breach and in the possible sabotage of our warp drive."
  • "Captain's Log, Supplemental. Retired Admiral Norah Satie whose investigation exposed the alien conspiracy against Starfleet Command three years ago, is arriving to assist in our inquiry."
  • "Captain's Log, Supplemental. Admiral Thomas Henry, who has worked closely with Norah Satie in the past, has arrived to observe the hearings." (TNG: "The Drumhead")

Mission to Kaelon II Edit

  • "Captain's log, stardate 44805.7. For generations, the people of Kaelon II have been working to revitalize their dying sun. The Federation has offered to assist in testing what may be a solution to this problem." (TNG: "Half a Life")

Peace mission to Peliar Zel Edit

  • "Captain's Log, Stardate 44824.4. Governor Leka and the representatives of the two moons are ready to transport on board. We have learned that they each have troops massed and are ready for combat if this final effort at peace is not successful." (TNG: "The Host")

Mission to Mar OscuraEdit

  • "Captain's Log, Stardate 44932.3. The Enterprise is preparing to enter the Mar Oscura, an unexplored dark matter nebula. Commander Data is modifying several of our photon torpedoes for an experiment designed to elicit more information about this unusual phenomenon."
  • "Captain's Log, supplemental. This series of unexplained events has now resulted in the death of a crewman, but it appears that Mr. Data may have an explanation." (TNG: "In Theory")

Mission to Qo'noSEdit

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.