Sector Split - EBG Ost
There are many options available to allow the splitting of Bremen's sector group East. In general, sector ownership is determined according to the definitions in the sectorfile. Dynamic splitting is not available in Euroscope/Topsky.
Sector combinations shall be decided to suit the traffic needs, workload and controller availability.
- In general, FLG + MAR should be the standard option for splitting the sector group. This split also reflects real-world sector combinations most of the time.
- For events in Berlin, FLG + MAR is the best way to balance traffic and reduce the controller's workload
- For events in Copenhagen, MAR + MRZ is recommended, but can also be changed to the FLG + MAR if traffic/workload allows.
- During the activity of the VPA North-East (military activity inside sector MRZ), it is recommended to split sector MAR and MRZ.
- All other sector splits can be beneficial when traffic load is imbalanced between the north and south (e.g. multiple event airports or shuttle events)
EDWW East Sectorization
The following article will only show the most common sector combinations.
You can view more sector combinations here: https://atciss.vatsim-germany.org/map
Top-down coverage EDDB: 1. FLG, 2. BOR, 3. MAR
1 Controller
| Sector MAR | Sector BOR |
| EDWW_MAR_CTR 136.050 | EDWW_BOR_CTR 123.225 |
| Sector MRZ | Sectors FLG |
| EDWW_MRZ_CTR 124.175 | EDWW_FLG_CTR 136.450 |
2 Controllers
3 Controllers
| Sectors BOR + FLG + MAR | Sectors FLG + MAR + MRZ |
| EDWW_BOR_CTR 123.225 | EDWW_FLG_CTR 136.450 |
| EDWW_FLG_CTR 136.450 | EDWW_MAR_CTR 136.050 |
| EDWW_MAR_CTR 136.050 | EDWW_MRZ_CTR 124.175 |
| Sectors BOR + FLG + MRZ | Sectors BOR + MAR + MRZ |
| EDWW_BOR_CTR 123.225 | EDWW_BOR_CTR 123.225 |
| EDWW_FLG_CTR 136.450 | EDWW_MAR_CTR 136.050 |
| EDWW_MRZ_CTR 124.175 | EDWW_MRZ_CTR 124.175 |
4 Controllers
| Sectors BOR + FLG + MAR + MRZ |
| EDWW_BOR_CTR 123.225 |
| EDWW_FLG_CTR 136.450 |
| EDWW_MAR_CTR 136.050 |
| EDWW_MRZ_CTR 124.175 |











