It really isn't as big of an issue as you want it to be. A simple mistake was made. It wasn't caught until sometime later. It happens.
No, it wouldn't. Not even remotely.It would be the biggest mistake on Riker's career...
It's very easily a mistake."Mistake", my ass. Riker is pointing out physical facts, not pulling them out of fallible memory or anything.
Hmh? Which line of "TATV" would this be? This one?The indication that one still exists is there via Troi, but she doesn't remember which one it was...
That doesn't sound like it - Kirk's ship didn't have Archer's ships aboard, either in plural or singular. What Troi is talking about is the Spock-style viewing hood... And she has only seen it in a photograph! It's a feature apparently found on many classes of ship, and unrelated to their names or registry numbers, too.Troi: "I remember seeing one of these in a photograph."
Riker: "Kirk's ship had them, I think."
Timo Saloniemi
Clearly referring to the NX-01 itself.TROI: Have you met with Commander Tucker?
RIKER: No, I haven't made it to Engineering yet. Have you spent any time on the NX-01?
TROI: I've never run the programme.
RIKER: What about the ship itself?
TROI: I think I went when I was a little girl, but I get all those museum ships mixed up.
No, it wouldn't. Not even remotely.
Nope, it's just a simple case of not being familiar with the hull registry of one ship. Nothing more.The incident that proves Riker cannot read, and will base his arguments on what he has "read" nevertheless, won't damage Riker's career? I guess not, in a Starfleet where all other officers are illiterate as well.No, it wouldn't. Not even remotely.![]()
I know you certainly have been more focused on arguing with me than actually thinking about the scene in question. Riker simply read a fake registry number that wasn't correct and didn't know that it incorrect at the time. Very simple.How can "not being able to read the registry in front of your eyes" be perverted into "not being familiar with" or other such nonsense? You certainly haven't been watching the same pair of episodes at all...
Correction, he reads Yamato on the ship's hull after reading the registry.Riker sees NCC-1305-E and from this deduces it is the Yamato.
Having a ship that new with a low registry number and a higher suffix than Enterprise suggests she was based on an originally an older design than a Constitution, maybe. But considering that there are Constitution-class ships with lower registry numbers than 1701, and even lower than 1305, it is possible that Yamato was one of the Constitution-class.
(A question would be, was the second Defiant-class USS Defiant renumbered to fit the lost Defiant or did she retain her number from when she was USS San Paulo? The effects shots of course were reused from the older ship, so one cannot tell what they actually did from the show.)
(A question would be, was the second Defiant-class USS Defiant renumbered to fit the lost Defiant or did she retain her number from when she was USS San Paulo? The effects shots of course were reused from the older ship, so one cannot tell what they actually did from the show.)
The DS9 writers wanted the new Defiant to have the registry NCC-74205-A but of course that wasn't possible due to it being seen exclusively in stock footage we only ever saw the NX-74205 registry on it.
In the novels, it still keeps the NX-74205 registry. Logically speaking, it should have kept the Sao Paulo's original registry, but that's beside the point.
(A question would be, was the second Defiant-class USS Defiant renumbered to fit the lost Defiant or did she retain her number from when she was USS San Paulo? The effects shots of course were reused from the older ship, so one cannot tell what they actually did from the show.)
The DS9 writers wanted the new Defiant to have the registry NCC-74205-A but of course that wasn't possible due to it being seen exclusively in stock footage we only ever saw the NX-74205 registry on it.
In the novels, it still keeps the NX-74205 registry. Logically speaking, it should have kept the Sao Paulo's original registry, but that's beside the point.
I thought it was explained in the novels that it was to keep a cloaking device on loan from the Romulans for a ship defined specifically as "USS Defiant NX-74205"?
Never underestimate lawyers, even in the 24th-Century.The DS9 writers wanted the new Defiant to have the registry NCC-74205-A but of course that wasn't possible due to it being seen exclusively in stock footage we only ever saw the NX-74205 registry on it.
In the novels, it still keeps the NX-74205 registry. Logically speaking, it should have kept the Sao Paulo's original registry, but that's beside the point.
I thought it was explained in the novels that it was to keep a cloaking device on loan from the Romulans for a ship defined specifically as "USS Defiant NX-74205"?
No, no reason was ever given in the novels for why the ship kept the same registry. I remember back in the day, someone from Pocket Books said the only reason they kept the same registry was because they were staying consistent with what was on screen.
Besides, why would the Romulans even care what registry the ship would have?
Never underestimate lawyers, even in the 24th-Century.I thought it was explained in the novels that it was to keep a cloaking device on loan from the Romulans for a ship defined specifically as "USS Defiant NX-74205"?
No, no reason was ever given in the novels for why the ship kept the same registry. I remember back in the day, someone from Pocket Books said the only reason they kept the same registry was because they were staying consistent with what was on screen.
Besides, why would the Romulans even care what registry the ship would have?
FEDERATION LAWYER: We'd like the replacement for the Defiant to have a cloaking device too.
ROMULAN LAWYER: No. Our exact agreement was for a cloaking device to be used only aboard the U.S.S. Defiant, NX-74205. It does not cover any other ship in your Starfleet.
FEDERATION LAWYER: Fine. If that's the way you want to play it...
We use essential cookies to make this site work, and optional cookies to enhance your experience.