FANDOM


Kolarus III was the third planet in the Kolarin system, orbiting at a distance of 1.2 au about Kolarus Prime. It was located in Federation territory near the Romulan Neutral Zone.

The planet had a mass of 5.972 × 1024 kg and an O2/N2 atmosphere. Its surface was dominated by vast savannas and deserts with little surface water. It was inhabited by isolated pockets of Kolarans, an early industrial humanoid civilization.

In 2379, Shinzon planted the parts of the Soong-type android B-4 on Kolarus III as part of his plan to capture Jean-Luc Picard. The positronic emissions from B-4 drew the attention of the USS Enterprise-E, the first Federation starship to visit the planet. An Enterprise away team of Picard, Worf and Data collected the scattered parts, though they came under fire from the Kolarans. Their presence at Kolarus III meant that the Enterprise was the closest ship to Romulus when Shinzon made a peace overture to the Federation. (Star Trek Nemesis)

This planet was named after the Kalahari desert. (Star Trek: The Next Generation Companion, 3rd ed., p. 354)
During production on Star Trek Nemesis, Kolarus was represented by a filming location: a desert midway between El Mirage Dry Lake Bed in El Mirage, San Bernardino County, and Edwards Air Force Base, at the east side of Lancaster, off Avenue C between 235th and the San Bernardino County line, Lancaster, Los Angeles County. [1] (Star Trek: The Next Generation Companion, 3rd ed., p. 351) CGI sky replacement was thereafter done at Digital Domain. (Star Trek: The Next Generation Companion, 3rd ed., p. 351)}
The topographical map of an area of Kolarus III, which was used by Data for locating the components of B-4, was based on a map of the Hadley-Apennine region of Luna. This was the landing site for Apollo 15. (Star Trek Encyclopedia (4th ed., vol. 1, p. 435))

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.