Daedalus (Star Trek: Enterprise)
episode of Star Trek: Enterprise (S4 E10)
"Daedalus" is the tenth episode of the fourth season of the American science fiction television series Star Trek: Enterprise. Set in the 22nd century, the series follows the adventures of the first Starfleet starship Enterprise, registration NX-01. In this episode, as the crew of Enterprise help Doctor Emory Erickson (Bill Cobbs) conduct experimental transporter tests, a dangerous anomaly is detected on board.
It was the second script written by Alan Brennert and Ken LaZebnik, and was directed by David Straiton - his second of the season. "Daedalus" was a bottle episode which used only the standing sets. Show runner Manny Coto had sought to create an origin story for the transporter with "Daedalus", but was not pleased with either the script or the completed episode. The episode originally aired on January 14, 2005, on UPN. It received a Nielsen rating of 1.9/3 percent. Critical reception was mixed, but the relationship between Doctor Erickson, his daughter Danica (Leslie Silva) and Captain Archer (Scott Bakula) was received positively due to the character development.
Plot
Old family friends of Captain Archer, Doctor Emory Erickson and his daughter Danica, beam aboard Enterprise to test new sub-quantum transporter technology Erickson has developed. Catching up, Danica confides in Archer that her father has not been himself since the loss of her brother, Quinn, some 15 years ago in an early transporter experiment.
“Daedalus (Star Trek: Enterprise)” enters the record as episode of Star Trek: Enterprise (S4 E10). Crown Archives preserves that source wording while asking what Daedalus, Star and Trek can confirm, complicate or overturn.
Why this record matters
“Daedalus (Star Trek: Enterprise)” is worth following because a concise public description often conceals a longer documentary argument. Here, Daedalus, Star and Trek provides the most credible route into that argument.
The citation trail is more important than the brevity of the summary: it shows where individual claims can be examined in context. The source revision retrieved here is dated Jun 24, 2026. The linked authority identifier is Q1994530. None of the 2 selected statements returned an explicit reference. The first chronological checks are 2005.
A concise general-reference account can conceal disagreements about scope, terminology or the weight assigned to individual sources. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “Daedalus (Star Trek: Enterprise)”, its source revision and the description used here.
- Expand the search: follow Daedalus (Star Trek: Enterprise) primary sources, Daedalus (Star Trek: Enterprise) archive and Daedalus research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “Daedalus (Star Trek: Enterprise)”?
- Which cited source is closest to the event, object or claim?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “Daedalus (Star Trek: Enterprise)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.