FANDOM


Multiple realities
(covers information from several alternate timelines)
This article or section is incomplete This page is marked as lacking essential detail, and needs attention. Information regarding expansion requirements may be found on the article's talk page. Feel free to edit this page to assist with this expansion.

The following is a list of unnamed Alpha and Beta Quadrant sectors.

Sector patrolled by USS Enterprise Edit

This sector was being patrolled by the USS Enterprise in 2267 when it received an alleged subspace message from Starbase 11. The sector was untroubled, with no alien problems. (TOS: "The Menagerie, Part I")

Sector containing Murasaki 312 Edit

This sector contained the quasar-like formation Murasaki 312 and at least four star systems, including the system containing the planet Taurus II.

In 2267, the USS Enterprise traveled through this sector on its course to Makus III. During the starship's time in the sector, Murasaki 312 ionized the entire sector. (TOS: "The Galileo Seven")

Sector where the Enterprise discovered the Botany Bay Edit

This sector was where, in 2267, the USS Enterprise discovered the SS Botany Bay. For years prior to this discovery, there had been no flights into this sector by Earth ships. (TOS: "Space Seed")

According to the 4th edition of the Star Trek Encyclopedia, this sector was the Mutara sector (vol. 2, p. 60) or was adjacent to the Mutara sector (vol. 1, p. 98).

Sector containing Unit XY-75847 Edit

This sector was where, in 2267, Unit XY-75847 reported the sighting of a fleet of Klingon ships to Starfleet Command. This sector was located in the same quadrant as Organia. (TOS: "Errand of Mercy")

Sector containing System L-370 Edit

This Alpha or Beta quadrant sector contained several solar systems, including L-370 and L-374. (TOS: "The Doomsday Machine")

According to the revised edition of the Stellar Cartography: The Starfleet Reference Library ("History of the United Federation of Planets"), which shows where the USS Constellation was destroyed, this sector was located near Klingon space.

Sector containing Babel Edit

As the Enterprise was assigned to this sector in 2268, it was given the mission of transporting the delegates of Federation planets to a council on the planetoid Babel. (TOS: "Journey to Babel")

Sector containing Capella IV Edit

This sector contained the inhabited planet Capella IV.

In 2267, the Enterprise visited this sector on a mission to Capella IV. Prior to this mission, Klingons had been detected in the sector. The USS Carolina was registered as being in this sector. (TOS: "Friday's Child")

Sector containing Romulan Neutral Zone Edit

This sector, containing a section of the Romulan Neutral Zone, was where the Enterprise entered the Zone, on a direct course, to Starbase 10 in 2267. (TOS: "The Deadly Years")

Sector containing M24 Alpha system Edit

This sector, containing the M24 Alpha system, was where the Enterprise, in 2268, followed an ionization trail to the planet Triskelion in the named system, where she retrieved her landing party. The sector was described as being empty by Montgomery Scott. (TOS: "The Gamesters of Triskelion")

Sector containing Starbase 6 Edit

This sector, containing Starbase 6, was visited by the Enterprise in 2268. It was located near Sector 39J. At the time of the Enterprise's visit, there were no indications of magnetic storms in the sector. (TOS: "The Immunity Syndrome")

Sector containing System 892 Edit

This sector, containing System 892, was first charted by the Federation survey ship SS Beagle in 2262. Six years later, the USS Enterprise would investigate the disappearance of the Beagle in this sector. (TOS: "Bread and Circuses")

Sector containing Beta XII-A Edit

This Alpha Quadrant sector, containing the planet Beta XII-A, was where, in 2268, the USS Enterprise and Kang's battle cruiser were lured to the named planet by distress calls fabricated by the Beta XII-A entity. This sector was scanned by the Federation starship for other ships, with negative results. (TOS: "Day of the Dove"; DIS: "Magic to Make the Sanest Man Go Mad")

Sector containing Type 4 asteroids Edit

In 2270, the USS Enterprise was assigned to this sector for a routine geological survey of type 4 asteroids. Near the completion of this mission, the Enterprise was ambushed by Romulan battle cruisers. (TAS: "The Practical Joker")

Sector containing Dramian star system Edit

This sector, containing the Dramian star system, was where the USS Enterprise reported an aurora in 2270. (TAS: "Albatross")

Sector containing Quadrant 9 Edit

This sector, containing Quadrant 9 and a segment of the Neutral Zone, was the site of a historic battle. In 2364, the Talarian freighter Batris defeated the Klingon cruiser IKS T'Acog. (TNG: "Heart of Glory")

Sector affected by the Manheim Effect Edit

This sector was affected by the Manheim Effect in 2364. At the time of the incident, the USS Enterprise-D was in this sector, on a heading to Sarona VIII. (TNG: "We'll Always Have Paris")

Unexplored sector Edit

This sector, unexplored by the Federation as of 2364, was the target of a subspace message sent by the mother creature of parasitic beings from Earth, after their infiltration of Starfleet was foiled. (TNG: "Conspiracy")

Sector containing three systems Edit

This Beta Quadrant sector, containing a portion of the Romulan Neutral Zone, contained three systems which had a number of cultural similarities, indicating they were being influenced by the Iconians. (TNG: "Contagion")

Sector traversed by Enterprise Edit

In 2365, the USS Enterprise-D was traversing through this sector when the Ansel Adams was reported as missing from Shuttlebay 2. In its search for the missing shuttlecraft, the Enterprise did a sensor search of the sector, revealing no other shuttles or ships in the region. (TNG: "Q Who")

Sector containing Boradis system Edit

This sector, in Federation territory in the mid-24th century, contained the Boradis system as well as several Federation colonies. The first colony, an outpost, was established on Boradis III in 2331. As of 2365, there were four colonies in the Boradis system and nine outposts in other systems in the sector. (TNG: "Emissary")


Sector containing Galorndon Core Edit

This sector, containing the Federation planet Galorndon Core, was a region of space claimed by the Federation in the Beta Quadrant. In this sector, the Romulan Neutral Zone was located half a light year away from Galorndon Core. (TNG: "The Enemy", DIS: "Magic to Make the Sanest Man Go Mad")

Galorndon Core's location, and the location of this sector, in the Beta Quadrant was established by a star chart seen in the Star Trek: Discovery episode.

Sector containing Acamar system Edit

This sector, containing the Acamar system, was a region of space in the Beta Quadrant. In the mid-24th century, the Gatherers attacked Federation research facilities and disrupted Federation trade routes in this sector. (TNG: "The Vengeance Factor"; DIS: "Magic to Make the Sanest Man Go Mad")

Acamar system's location, and the location of this sector, in the Beta Quadrant was established by a star chart seen in the Star Trek: Discovery episode.

Sectors neighboring the Acamar system sector Edit

These sectors, neighboring the Acamar system sector, were invaded by the Gatherers in the mid-24th century, who attacked Federation outposts located there. (TNG: "The Vengeance Factor")

Federation sectors threatened by Nelvana III base Edit

In 2366, these sectors, numbering 15 in total, would be, according to Romulan logistics officer Setal, threatened by a base on Nelvana III. These sectors would be in "striking distance" of Romulan warbirds sent from this planet. During the incident at Nelvana III, in these sectors, outposts along the border of the Neutral Zone received warnings from Starfleet Command. (TNG: "The Defector")

Romulan sector Edit

This distant sector in Romulan territory was the assignment for the logistics officer Setal, who worked under Alidar Jarok. The region was mentioned in an interrogation led by William Riker of Setal in 2366. After Setal was revealed to be the admiral, Jarok stated that he was assigned, as its commander, to this sector after being censured for his outspokenness against the militant polcies of the Romulan High Command. (TNG: "The Defector")

This sector was only mentioned in dialogue.

Sector containing Bre'el IV Edit

In 2366, the Enterprise-D contacted all ships in this sector, requesting that they rendezvous with the Federation starship and join them in relief efforts, as the planet Bre'el IV was threatened with its asteroidal moon impacting the larger body. (TNG: "Deja Q")

Sector containing Tanuga system Edit

In 2366, the Enterprise-D was assigned to a mission in this sector. As the Tanuga system was located in this sector, the Federation starship paused its mission, dropping off William Riker and Geordi La Forge at the Tanuga IV research station so they could check on the progress of Doctor Nel Apgar's work on a Krieger wave converter. Before getting its officers back, the Enterprise-D concluded a study of a protostar cloud. (TNG: "A Matter of Perspective")

Sector containing Narendra III Edit

This sector, in the Beta Quadrant, contained the planet Narendra III. (TNG: "Yesterday's Enterprise"; DIS: "Magic to Make the Sanest Man Go Mad")

In 2346, the USS Enterprise-C received a distress call from the outpost on Narendra III. After scanning the sector for other Federation ships, with negative results, the Enterprise-C responded to the call. It entered into battle with Romulan warbirds, eventually being destroyed. Its sacrifice impressed the Klingons, who entered into a peaceful relationship with the Federation.

In 2366, the USS Enterprise-D was on a mission in this sector when a temporal rift, caused by the formation of a Kerr loop from superstring material, resulted in an alternate timeline in which the Federation was at war with the Klingon Empire.

In this new timeline, Starfleet monitor stations sent a message to the Enterprise-D informing the starship that Klingon battle cruisers were heading to this sector. The Federation starship protected its predecessor, the USS Enterprise-C, from the enemy vessels as the latter ship returned to the past, thereby restoring the timeline. (TNG: "Yesterday's Enterprise")

A star chart in the Star Trek: Discovery episode placed Narendra III's primary Narendra in the Beta Quadrant.

Sector containing Khitomer system Edit

This sector, in the Beta Quadrant, contained the Khitomer system.

In 2346, in the aftermath of the Khitomer Massacre, a sensor scan of the region by the USS Intrepid revealed that the attacking spacecraft, presumed to be Romulan warbirds, were no longer in the sector. (TNG: "Sins of the Father"; DIS: "Magic to Make the Sanest Man Go Mad")

A star chart in the Star Trek: Discovery episode placed Khitomer in the Beta Quadrant.

Sector containing Risa Edit

This sector, in the Alpha Quadrant, contained the planet Risa. (TNG: "Captain's Holiday"; DIS: "Magic to Make the Sanest Man Go Mad")

A star chart in the Star Trek: Discovery episode placed the primary of Risa in the Alpha Quadrant. This sector might be the same as Sector 25712, a sector associated with nearby Starbase 12.

Sector attacked by Nausicaans Edit

In this sector, Earth Cargo Service freighters were frequently attacked, over a time period lasting years, by Nausicaan pirates. Travis Mayweather knew about the sector and the repeated attacks within it. One of the freighters which was assaulted in this area was the ECS Fortunate, which consequently sustained heavy damage, in 2151. When Enterprise NX-01 arrived to investigate the aftermath of the battle, the starship's crew found no other ships in the region. Despite subsequent onslaughts by the Nausicaans, Matthew Ryan, who was temporarily in command of the Fortunate, refused Enterprise's help, which his commanding officer, Captain Jackson Keene, reasoned was due to Ryan and others who had grown up on the freighter feeling that they had some special claim to ownership of this particular stretch of space and who typically became jumpy when they saw another ship within ten light years. After Keene resumed command of the Fortunate, Enterprise departed from the area. (ENT: "Fortunate Son")

In the first draft script of "Fortunate Son", Captain Archer recommended setting up regular patrols in this sector, to protect the freighters. However, Admiral Forrest, doubtful that plan would work, replied that the sector was "pretty big." Later in the teleplay, a freighter called the Gallant (later renamed the ECS North Star) was said to have been destroyed by Nausicaans in the same sector, a few years beforehand. In the final edit of the episode, however, the word "sector" is only mentioned once, when Mayweather tells Archer that Nausicaan pirates had been "attacking freighters in this sector for years."

Sector containing ArkariaEdit

The sector containing Arkaria was notable for having several cultures with extremely similar etymological histories. (TNG: "Starship Mine")

Sector containing Taurean systemEdit

This sector contained the Taurean system. Earth vessels associated with the Federation had visited it for at least a century and a half before 2269. However, despite it long having been trafficked, Starfleet by 2269 still considered it an unfamiliar sector. Klingon and Romulan ships had visited the sector for some time as well, and ships from all three powers had disappeared in mysterious circumstances there. (TAS: "The Lorelei Signal")

Sector on edge of Federation spaceEdit

At the start of the Federation-Klingon War of 2256, part of this sector was at the edge of Federation space. It contained a binary system with an accretion disk. (DIS: "The Vulcan Hello")

Given the close (six light years) distance of the binary star to Gamma Hydra, this could be the Gamma Hydra sector.

Triona system sector Edit

This remote sector contained the Triona system. Its isolation led Beverly Crusher to speculate that Lieutenant Keith Rocha could have been absorbed by a coalescent organism while posted there. (TNG: "Aquiel")

Uncharted Necro Cloud sectorEdit

The "escape pod" on which Kalara arrived at Starbase Yorktown in 2263 was tracked to coordinates 210 mark 14, in a sector of an uncharted nebula, the Necro Cloud. The area was uncharted due to the nebula being too dense. The USS Enterprise subsequently managed to penetrate the area, finding the planet Altamid. (Star Trek Beyond)

Sector containing Amargosa starEdit

This sector contained the star Amargosa. In the late 24th century, the Federation research station Amargosa observatory observed the star from its location in the Amargosa system. In 2371, after receiving a distress call from the staton, the USS Enterprise-D came to the rescue of the station's scientists. Upon discovering two dead Romulans, the starship sent a message to Starfleet Command about a possible Romulan threat to the sector. Soon afterwards, Amargosa was destroyed by Doctor Soren, resulting in major effects throughtout the sector. These included an increase in gamma emissions and changes in the gravitional forces, necessitating any starship traveling through the sector performing minor course corrections. As the Nexus entered the sector, these changes would alter its course towards the Veridian system. (Star Trek Generations)

There was, as well, a change in the ambient magnetic fields; however, this change was not mentioned in the film.
Community content is available under CC-BY-NC unless otherwise noted.