**Before staffing this airport for the first time:** Obtain a successful grade at the self-enrollment Moodle course: **[EDDW - Bremen Tower](https://moodle.vatsim-germany.org/course/view.php?id=76).**
### Bremen ATC Stations| **Station** | **Station ID** | **Login** | **Frequency** | **Remark** |
| **ATIS** | ADW | EDDW\_ATIS | 132.380 | -- |
| **Ground** | DWG | EDDW\_GND | 121.755 | -- |
| **Tower** | DWT | EDDW\_TWR | 120.330 | -- |
| **Sector Friesland** | FRI | EDDW\_APP | 124.800 | -- |
| **Departures/hour** | **Arrivals/hour** | **Global/hour** |
| 18 | 18 | 30 |
Datalink Clearances (DCL/PDC) are not available at EDDW.
During 27-Ops, Bremen Ground shall use the Z-SIDs by default (where available). All L-SIDs shall only be used on explicit pilot's request only. The initial climb for all departure routes is 4000 ft.
**The use of SOFED departure routes shall be terminated in case ED-R 202A, ED-R 202B or ED-R 202E (known as TRA Weser) are active.** **In this case, traffic via SOFED shall be re-routed via OKWEL N125 ITMIZ (then flight-planned route).** EDWW sector FRI will inform Bremen Ground about the activation and deactivation of TRA Weser. By default, ED-R 202 is to be considered as deactivated.
#### Special Procedure - SOFED SIDs Beginning on March 20, 2025, the SOFED SIDs are no longer connected to airway N125 due to changes to the ATS routes. Nevertheless, SOFED SIDs will still be used for departures to the west. Traffic intending to use SOFED SIDs is requested to file "ABDIM DCT ITMIZ N125 ..." as the initial segment of the F-Plan route. Traffic will then be instructed to follow a SOFED SID and to then join ITMIZ when reaching ABDIM located on the SID. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/inkscape-owgoufmqnj.png)To avoid confusion, Bremen Ground is requested to inform the pilot about this procedure when giving IFR clearance: "... via SOFED2M departure, after ABDIM direct ITMIZ flight planned route ...". It is important to have a closer look at the F-Plan before giving IFR clearance to aircraft requesting to use SOFED SIDs.
It is to be expected that some pilots will file flight plans with the first waypoint "SOFED" instead of "ABDIM". This will still be considered as valid and Bremen Ground may clear SOFED SIDs nonetheless. In this case no coordination with Bremen Radar is required. #### Vectored Departures and Local IFR Vectored departures and local IFR are subject to individual coordination with the station responsible for EDWW sector FRI (Friesland). This sector will inform Bremen Ground about the planned departure routing. #### VFR traffic Departing VFR traffic will call Bremen Ground initially. Bremen Ground shall create an F-Plan when necessary and inform Bremen Tower about the intentions of the VFR traffic.**Runway 23 shall only be used on the explicit pilot's request and only for VFR departures of up to 5700 kg MTOM requesting to leave the CTR via SIERRA, WHISKEY, or NOVEMBER.**
**Jet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow a published IFR departure route under VFR conditions.** In this case, Bremen Ground shall coordinate the departure routing with Bremen Tower. Bremen Ground will then inform the pilot about the expected departure routing.
### Ground Movements #### Parking Positions Bremen Ground shall use the arrival stand planned by the Groundradar Plugin. On request by the pilot, this stand may be changed. All stands are limited to a maximum wingspan of 36 m. Stands 12A and 18A may be used by heavy aircraft (wingspan up to 52 m). General Aviation traffic shall be parked at the General Aviation Apron next to taxi lane R if the aircraft's wingspan is below 24 m. Larger General Aviation traffic shall park at stands 12-17. Apron 3 shall be used for traffic of company Atlas Air Service (ATL, callsign "Air Bremen"). Additionally, this apron may be assigned at the pilot's request only. #### Taxiway Intersections**As a general rule, departing IFR traffic shall be cleared to Intersection A (RWY 09) or Intersection F (RWY 27) by Bremen Ground.** Intersection C (RWY 09) or D/E (RWY 27) may be used on the pilot's request only. **For noise abatement reasons, pilots of propeller and turbo-prop aeroplanes of more than 2000 kg MTOM will, as a rule, be cleared by Bremen Ground to use intersection E for take-off RWY 27 instead of intersection F.** The pilot shall inform Bremen ground in case intersection F is required due to performance reasons.
Departing VFR traffic using runway 23 shall be cleared to intersection D holding at the holding point of runway 27. Unless otherwise requested, departing VFR traffic from runway 09 shall use intersection C. VFR traffic departing from runway 27 shall be guided via intersection D.**VFR traffic requesting to depart from runway 09 to leave the CTR via WHISKEY shall be guided to runway intersection A only.** The use of other intersections is prohibited!
Whenever possible, departing traffic should be transferred to Bremen Tower when joining taxiway F.**For noise abatement reasons, taxi clearances for aircraft taxiing via intersection F to take off from RWY 27 will be issued only up to the CAT II/III holding position.**
#### Taxiway Restrictions| **TAXIWAYS** | **RESTRICTIONS** | **NOTES** |
| **K** | Max. wingspan < 24 m | --- |
| **L** | Max. Wingspan < 31 m | --- |
| **H, D, E, S** | Max. wingspan < 36 m | --- |
| **G** | Max. wingspan < 52 m | Between TWY C and position 12 inclusively |
| **N** | Max. Wingspan < 52 m | --- |
| **R** | Max. ICAO code letter B | Max. wingspan < 24 m |
| **F1, F2** | Use only permitted for Airbus factory traffic | Callsign BGA |
| **Max Spannweite** | **A/C Types** |
| < 30m | AT72 / CRJX / DH8D / RJ1H / etc. |
| < 36m | B739 / A321 / BCS3 / E195 / etc. |
| < 52m | B753 / B763 / A306 / etc. |
| < 65m | A333 / A346 / A35K / B744 / B77W / B78X / etc. |
| < 80m | A124 / A388 / B748 / etc. |
| > 80m | A225 |
| Movements | Beluga (A3ST) | Beluga XL (A337) |
| Departure from RWY 09 | Taxi via F, C, N and A | Taxi via F to intersection C, backtrack required |
| Departure from RWY 27 | Taxi via F | |
| Arrival from RWY 09 | ||
| Arrival from RWY 27 | Taxi via A, N, C and F | Backtrack required, taxi via C and F |
The Beluga XL requires a backtrack from intersection C, as this aircraft exceeds the wingspan limit at taxiway N.
#### Low Visibility Procedures When low visibility conditions exist, Bremen Ground shall only use Intersection A (RWY 09) and Intersection F (RWY 27) for departing traffic. This traffic is to be cleared to the CAT II/III holding points only. ### Helicopter Traffic At Bremen airport, the rescue helicopter "Christoph Weser" (Christoph 55, CHX55) is stationed. Departure and arrival are performed on the takeoff and landing platform "Yankee" between taxiways H, C and F.As a general rule, rescue helicopters will contact Bremen Tower directly. Bremen Tower shall inform Bremen Ground about any helicopter arrival or departure. **The use of the taxiways triangle F-C-H is prohibited during every takeoff and landing at Yankee!**
# Tower Bremen Tower is responsible for all movements on the runways and traffic flying inside the Bremen CTR. ### Control Zone [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2022-10/eddw-ctr.png) Bremen CTR reaches from the ground to an altitude of 2500 ft MSL. Bremen Radar (sector Friesland) is responsible for movements inside Bremen airspace class D (non-CTR). ### Runways Runway 09/27 is the only available runway for IFR and landing VFR traffic. The runway direction shall be based on the current wind situation at the aerodrome. #### Runway 23 Runway 23 can be used during the daytime and if the wind conditions permit. This runway shall only be used on the explicit pilot's request and only for VFR departures of up to 5700 kg MTOM requesting to leave the CTR via SIERRA, WHISKEY, or NOVEMBER. #### Beluga Special Runway Both runway thresholds are connected to runway extensions increasing the TORA by roughly 300 m. These paved RWY extensions in front of the respective thresholds shall only be used as special take-off runways for Beluga and Beluga XL aircraft (A3ST and A337). ### Reduced Runway Separation (RRS) Bremen Airport (EDDW) is approved to apply the following reduced runway separation minima during day only:| **Runway** | CAT 1 following a departing CAT 1 or 2 | CAT 2 following a departing CAT 1 or 2 | CAT 1 to 3 following a departing CAT 3 |
| RWY 09/27 | 600 m | 1500 m | --- |
**The Beluga XL (A337) requires a backtrack from intersection C to depart from RWY 09 as this aircraft exceeds the wingspan limit at taxiway N.**
#### Departure Releases Departures do not have to be released by EDWW (Bremen Radar) unless: - EDWW explicitly restricts departures by time, SID or until further notice - Departures out of the non-operational runway config - The first departure after a runway change - The first departure after an unplanned missed approach ### Arriving Traffic After landing, Bremen Tower shall issue the initial taxi clearance via F (RWY 09) or A (RWY 27) and transfer the aircraft to Bremen Ground.For jet aircraft with an MTOM of more than 20 t, landing on runway 27, Bremen Tower shall instruct the pilot to vacate via taxiway A before issuing the landing clearance. **After coordination with Bremen Ground, this traffic may also be approved to vacate via C. **
Traffic landing on runway 09 with a wingspan of more than 36 m shall be instructed to vacate the runway via taxiway F before issuing the landing clearance.**The Beluga XL (A337) requires a backtrack from RWY 27 to leave via taxiway C as this aircraft exceeds the wingspan limit at taxiway N.** The pilot shall be informed about these procedures before issuing the landing clearance. The backtrack is performed at the designated Beluga Special Runway.
### VFR Traffic Traffic requesting traffic circuit flights may preferably be cleared for the southern downwind due to noise abatement reasons. Still, using the northern downwind is not prohibited per se.SIERRA 2 is only to be used for inbound traffic. Departing traffic shall proceed to SIERRA 1 directly.
#### Departing VFR Traffic Departing VFR traffic will contact Bremen Ground initially. Bremen Ground will inform Bremen Tower about the intentions of the departing VFR traffic.**In general, runway 27 is the preferred runway for VFR departures. Runway 23 should be used on the explicit pilot's request only!**
Traffic requesting to depart from runway 09 to leave the CTR via WHISKEY shall only take off from runway intersection A.
**Departures from runway 23 to leave the CTR via NOVEMBER shall only initiate the right turn after departure after explicit instruction from Bremen Tower.** Bremen Tower shall make sure that no conflict with arriving or departing traffic via runway 09/27 exists before issuing the right turn.
##### VFR departure for Jets and Aircraft with a MTOM of more than 5700 kg**Jet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow a published IFR departure route under VFR conditions.** In this case, Bremen Ground shall coordinate the departure routing with Bremen Tower.
Despite Bremen Ground previously issuing the expected departure procedure to the pilot, Bremen Tower shall also instruct the departure procedure before takeoff clearance.
The departure routes may be issued for IFR traffic, except the following maximum altitudes after departure shall be used:| Maximum Altitude | RWY 09 | RWY 27 |
| Maximum 2000 ft or below | SOFED, WIMCI, NIE | OKWEL, NIE, GESTO, OTEXE, WSN, OKWEL |
| Maximum 1500 ft or below | OKWEL, GESTO, WSN | SOFED |
The departure routing shall be assigned depending on the requested or filed waypoint from the pilot. **If requested by the pilot, Bremen Tower may coordinate an entry into airspace class D (non-CTR) with Bremen Radar to enable a climb above the mentioned altitudes.**
#### Arriving VFR Traffic Arriving traffic shall be guided via the published CTR entry procedures.**Jet aircraft or any aircraft with an MTOM of more than 5700 kg shall only enter the CTR via a published IFR approach (e.g. ILS).** This traffic shall contact Bremen Radar to join the published approach. Bremen Tower will not provide vectoring service for such traffic.
#### Rescue Helicopter Traffic ##### Christoph 55 The rescue helicopter Christoph Weser (CHX55) is stationed at Bremen airport. It usually parks in front of the DRF hangar (Hangar K). Departures and arrivals will be performed via the takeoff and landing platform between taxiways H, C and F. **This platform shall only be used for rescue helicopter traffic.** The platform may also be called "Yankee" unofficially. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/drf-helipad.png)**For departure, Bremen Tower will be contacted directly. In all cases, Bremen Tower shall inform Bremen Ground about any movement via the takeoff and landing platform** (arrivals and departures).
**It is important to note that the platform "Yankee" is not to be considered a helipad.** It functions as a takeoff and landing platform comparable to other hospitals in the CTR. **Therefore, no takeoff and landing clearance shall be given!** Traffic will depart and land at its own discretion.
**Examples:** > *"Christoph 55, cross Hotel, wind 100 degress 5 knots, takeoff Yankee own discretion, proceed direct \[...\]."* > > *"Christoph 55, wind 100 degress 5 knots, land Yankee own discretion, cross Hotel, approved to leave on ground."***The use of the taxiways triangle F-C-H is prohibited during every takeoff and landing at Yankee!**
##### Other Rescue Traffic Within Bremen CTR, three hospitals with helipads exist. Rescue helicopter Christoph 6 (CHX06) is stationed at "Klinikum Links der Weser" which may also be called "Pad Zulu" unofficially. Bremen Tower shall announce the current wind situation at EDDW whenever a rescue helicopter reports approaching the destination. A map with all hospitals can be toggled with ALT + H in the Euroscope package. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/euroscope-jk5etzeoir.png) ### Low Visibility Procedures (LVP) When the weather condition requires low visibility operations the use shall be announced in the ATIS. Additionally, Bremen Tower shall inform Bremen Ground and Bremen Radar about the beginning and termination of Low Visibility Procedures.use ***&lvp*** in the ATIS maker URL or "LOW VIS OPS" flag in the NOTAM menu of vATIS
**When low-visibility conditions exist, Bremen Tower shall instruct arriving traffic to vacate via taxiway F (RWY 09) or taxiway A (RWY 27) before issuing the landing clearance.** The use of intersection departures is prohibited during low-visibility operations.
# Arrival ## Sectorization and Airspace ### Sector Friesland [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-02/fri.png) Sector Friesland is part of EDWW sector group [Nord-B (EBG Nord-B)](https://knowledgebase.vatsim-germany.org/books/edww-bremen-radar/page/overview-ebg-nord-b).| **Station** | **Station ID** | **Frequency** | **Login** |
| Friesland | FRI | 124.800 | EDDW\_APP |
Note: Unless otherwise coordinated, traffic has to exactly proceed on the listed routes. Shortcuts through the TRA are not allowed.
Sector FRI shall inform Bremen Ground/Tower about the activity of TRA Weser. During the activity of ED-R 202A, 202B or 202E all SOFED departures shall not be used. Traffic shall be routed via OKWEL N125 ITMIZ instead.
[](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-10/tra-wesrer.png) ### TRA Friesland Within the northern part of sector FRI, parts of TRA Friesland may be active from FL80-FL245. Traffic is generally not approved to cross ED-R 201A and ED-R201C. Traffic may cross ED-R 201B on the following priority routes (see box below):Note: Unless otherwise coordinated, traffic has to exactly proceed on the listed routes. Shortcuts through the TRA are not allowed.
| **Runway** | **Available Approach Types** | **Intercept Altitude** |
| 09/27 | ILS Z, LOC Z, RNP, VOR | 3000 ft |
| ILS Y | 1700 ft (as published) |
| **Conditions** | **Target Spacing** |
| Normal Operations | 6 NM (\*) |
| After coordination with Tower | 3 NM |
| During Low Visibility Conditions | 10 NM |
(\*) Behind a Beluga XL (A337) landing on runway 27, Bremen Radar shall increase the target spacing as a backtrack is required to vacate the runway via taxiway C due to wing span limitation. The normal Beluga (A3ST) is not affected from this.
## Departing Traffic from EDDW Departing traffic from EDDW shall automatically switch frequency from Tower to EDWW. Traffic transferred to EDWW ACC sectors according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). Often traffic may be coordinated on a higher flight level with sector ALR, EID or EMS to avoid unnecessary level-offs. #### Special Procedure - SOFED SIDs Beginning on March 20, 2025, the SOFED SIDs are no longer connected to airway N125 due to changes to the ATS routes. Nevertheless, SOFED SIDs will still be used for departures to the west. Traffic intending to use SOFED SIDs is requested to file "ABDIM DCT ITMIZ N125 ..." as the initial segment of the F-Plan route. Traffic will then be instructed to follow a SOFED SID and to then join ITMIZ when reaching ABDIM located on the SID. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-03/inkscape-owgoufmqnj.png)It is to be expected that some pilots will file flight plans with the first waypoint "SOFED" instead of "ABDIM". This will still be considered as valid and Bremen Ground may clear SOFED SIDs nonetheless. Additionally, traffic may not follow the short cut to ITMIZ as instructed by Bremen Ground. It is highly recommended to coordinate shortcuts with sector Ems and Eider, especially when the route looks invalid.
## VFR Traffic ### VFR DeparturesJet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow a published IFR departure route under VFR conditions.
By default, the Bremen Tower will instruct the aircraft to stay clear of airspace class D (non-CTR). Nevertheless, coordination may be required between Bremen Tower and Bremen Radar in case the pilots request further climb. In this case, Bremen Radar shall issue the approval to enter airspace D (non-CTR) to Bremen Tower directly. ### VFR ArrivalsJet aircraft or any aircraft with an MTOM of more than 5700 kg shall follow published IFR arrival routes under VFR conditions.
In this case, the arriving VFR traffic shall contact Bremen Radar latest 25 NM before approaching EDDW. Bremen Radar shall provide service for a practice approach VFR (e.g. via an ILS approach). An entry via published VFR arrival routes into the CTR is not possible. ## Emden (EDWE) Emden (EDWE) is an uncontrolled aerodrome located about 19 NM southwest of ETNT. Due to published IFR procedures, limited service has to be provided for IFR traffic: - Approach clearance - IFR clearance**When online, Wittmund Radar (ETNT\_APP) will take over all responsibilities for IFR traffic from/to Emden.** In this case, traffic shall be coordinated individually between Bremen Radar and Wittmund Radar. **Bremen Radar shall transfer arriving traffic early enough before reaching IAF for Wittmund Radar to clear the approach.**
### Approach Types There is one published approach type available at EDWE:| **Runway** | **Available Approach Types** | **IAF** | **Altitude at IAF** |
| 07/25 | **RNP Z** | **SUQIF** | **4000 ft** |
| RNP Y (HEL) | JUIST | 3000 ft |
**The RNP Y is only available for helicopter traffic.** This approach is primarily used by helicopter traffic approaching from oil rigs located in the North Sea during IMC. This approach shall only be cleared when requested by the helicopter pilot.
As traffic will leave controlled airspace during the approach, traffic must proceed via the published approach procedures only! Arriving traffic shall be instructed to switch to Emden Information or 122.800 before reaching FAF.
### Departing Traffic Departing traffic will request the IFR clearance on the ground. Traffic will depart at its discretion and shall be instructed to report when airborne. Departing traffic from EDWE shall be offered to switch frequency for taxi and departure to properly communicate with other (VFR) traffic at Emden. Departing traffic shall be transferred according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc).JUIST departures are only available for helicopter traffic. In general, traffic shall only depart via published departure procedures.
### Emden Block Clearance Area To keep sufficient distance from EHGG APP for traffic on the published approach procedure for runway 07 at EDWE, the airspace within the "Emden Block Clearance Area" is permanently delegated from Eelde Approach to Bremen Radar/Wittmund Radar: [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2025-02/msedge-d9o3j30tuw.png) ## Wilhelmshaven (EDWI) Wilhelmshaven Jadeweser Airport (EDWI) is an uncontrolled aerodrome located about 14 NM southeast of ETNT. Due to published IFR procedures, limited service has to be provided for IFR traffic: - Approach clearance - IFR clearance**When online, Wittmund Radar (ETNT\_APP) will take over all responsibilities for IFR traffic from/to Wilhelmshaven.** In this case, traffic shall be coordinated individually between Bremen Radar and Wittmund Radar. **Bremen Radar shall transfer arriving traffic early enough before reaching IAF for Wittmund Radar to clear the approach.**
### Approach Types There is one published approach type available at EDWI:| **Runway** | **Available Approach Types** | **IAF** | **Altitude at IAF** |
| 02/20 | RNP | REVLA | 4000 ft |
As traffic will leave controlled airspace during the approach, traffic must proceed via the published approach procedures only! Arriving traffic shall be instructed to switch to Wilhelmshaven Information or 122.800 before reaching FAF.
### Departing Traffic Departing traffic will request the IFR clearance on the ground. Traffic will depart at its discretion and shall be instructed to report when airborne. Departing traffic from EDWI shall be offered to switch frequency for taxi and departures to properly communicate with other (VFR) traffic at Wilhelmshaven. Departing traffic shall be transferred according to [LOP EDWW](https://knowledgebase.vatsim-germany.org/books/bremen-fir-edww/page/lop-bremen-acc). ## Groningen (EHGG) IFR traffic may approach EHGG via sector Friesland. Inbound traffic shall be transferred at FL70 to EHGG APP. Outbound traffic from EHGG will be cleared to FL60 from EHGG APP.