The Feynman was a Federation type 7 shuttlecraft that was in service with Starfleet in the mid-24th century, attached to the USS Enterprise-D. It was shuttlecraft 05.

In 2367, Lieutenant Commander Geordi La Forge and Lieutenant Reginald Barclay piloted this shuttle to investigate a Cytherian probe disrupting the operation of the Argus Array. The probe sent a beam to the shuttle which knocked Barclay unconscious and later caused his IQ to increase exponentially. (TNG: "The Nth Degree")

In 2369, Captain Jean-Luc Picard, Doctor Beverly Crusher, and Lieutenant Worf flew the Feynman to a trading outpost near the border of the Cardassian Union in order to secure passage to Celtris III aboard DaiMon Solok's Ferengi vessel. (TNG: "Chain of Command, Part I")

Appendices Edit

Background information Edit

The Star Trek Encyclopedia (3rd ed., p. 153) stated the shuttlecraft "was named for Dr. Richard Feynman (1918-1988), noted Nobel physicist and bongo player." The Encyclopedia further stated that "the name was misspelled as Feyman on the shuttle's exterior because of a mistake made in the art department."

It was also mispronounced in the episode as FAIN-man, when the correct pronunciation is FINE-man.

Its interior was represented by that of a type 6 shuttlecraft in "Chain of Command, Part I". The fate of the Feynman was not known, as both Crusher and Worf were retrieved by Will Riker in another shuttlecraft. According to a deleted scene from "Chain of Command, Part II", the Feynman was recovered by the Enterprise. This shuttle was seen in a shuttlebay. It had the exterior shell of a type 6 shuttlecraft and the name was spelled as "Feyman". [1]

The Star Trek: The Next Generation Companion identified the shuttle used in the episode TNG: "The Nth Degree" as the Feynman.

External link Edit

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.