(covers information from several alternate timelines)
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
Sector where the Enterprise discovered the Botany Bay Edit
Sector containing Unit XY-75847 Edit
Sector containing System L-370 Edit
Sector containing Babel Edit
Sector containing Capella IV Edit
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
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
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
Sector in simulation Edit
This sector was mentioned in a scenario designed to test Cadet Thira Sidhu in the mid-23rd century. According to the scenario, the USS Bouman was in the sector when it was captured by Tholians. The USS Enterprise was in the same sector and attempted to intervene. (ST: "Ask Not")
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")
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")
Sectors neighboring the Acamar system sector Edit
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 Sublieutenant 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 command officer, to this sector after being censured for his outspokenness against the militant policies of the Romulan High Command. (TNG: "The Defector")
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
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")
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")
Sector containing Risa Edit
Sector containing Zeta Gelis star cluster Edit
Sector containing Starbase 133 Edit
This sector was the location for Starbase 133.
In 2367, in the reality created by Beverly Crusher, the Wellington was one of two Federation vessels in this sector; the other being the USS Enterprise-D. It reported no unusual readings after Wesley Crusher had performed warp field experiments aboard the Enterprise-D. (TNG: "Remember Me")
Sector containing Gamma Arigulon system Edit
This sector was the location for the Gamma Arigulon system.
In 2367, the starship LaSalle reported radiation anomalies from the Gamma Arigulon system. Later, as the USS Enterprise-D was investigating the system's star, the Federation starship was greeted by K'mpec's attack cruiser. This was a surprise as Starfleet had not mentioned the presence of Klingon vessels in the sector. (TNG: "Reunion")
Sector containing Gamelan system Edit
This sector was the location for the Gamelan system.
In 2367, the USS Enterprise-D entered this sector to help Gamelan V with a waste ship which was threatening the planet with increased radiation levels. The Enterprise successfully destroyed the waste ship. When the Enterprise received the distress signal, there were no other ships in the sector. (TNG: "Final Mission")
Sector where Enterprise-D rendezvous with the Devoras Edit
This sector was the location for a section of the Romulan Neutral Zone.
In 2367, according to a tactical projection by Data of Romulan deployments in this sector, the Romulan Star Empire placed their ships along the border with the idea that they were there to support a "policy of confrontation designed to test Federation defenses." There was a 90 percent probability that the empire would continue the policy into the near future.
Federation sectors threatened by Cuellar system science station Edit
In 2367, these sectors, numbering 3 in total, would be, according to Captain Benjamin Maxwell, threatened by the Cardassian science station, if it was a military transport station, in the Cuellar system. The Cardassisn could use the system as a jumping-off point into these sectors. (TNG: "The Wounded")
Sector containing Ventax II Edit
This sector was home to the planet Ventax II.
Sector containing Tagus III Edit
This sector was home to the planet Tagus III.
Sector containing Kriosian system Edit
Sector containing the Mar Oscura Nebula Edit
This sector was home to the Mar Oscura Nebula.
Klingon sectors Edit
These sectors were located in Klingon space.
In that year, prior to the Klingon Civil War, four squadron commanders assigned to these sectors were supportive of Kurn. After speaking with Kurn, three of the four squadron commanders agreed to back Gowron in the upcoming civil war, giving Gowron the strength to control these sectors. (TNG: "Redemption")
Over three weeks later, Gowron's forces launched attacks against the House of Duras' forces in three sectors, forcing the Duras family to send an urgent message to the Romulans saying that they were near defeat. (TNG: "Redemption II")
El-Adrel system sector Edit
This sector contained the El-Adrel system.
Solarion system sector Edit
This sector contained the Solarion system.
Lefler's parents' sector Edit
Sector containing Penthara IV Edit
This sector contained the inhabited planet Penthara IV.
Professor Berlinghoff Rasmussen said, in a conversation with Captain Jean-Luc Picard, that if he influenced events at Penthara IV, he might change the history of this sector. (TNG: "A Matter of Time")
Beta Quadrant sector Edit
This sector was located in the Beta Quadrant.
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")
Sector containing ArkariaEdit
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
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)