Tower

Bremen Tower is responsible for all arrivingmovements on the runways and departingtraffic flying inside the Bremen CTR.

Control Zone

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 toprunway leveldirection ofshall be based on the airspacecurrent Dwind controlsituation zone is 2500ft MSL. Above this altitude airspace D (Non-CTR) coversat the areaaerodrome. within responsibility of Bremen Radar. An extra D airspace area west and east of the CTR is at 1500ft MSL. West of the field is the uncontrolled airfield EDWQ Ganderkesee in the final of runway 09.

Runway and Airport

23

Runway 27 is preferred up to 5 knots tailwind component.

Runway 23 can be used during the daytime and if the wind conditions permit. This runway shall only be used for VFR departures duringof daytime.up to 5700 kg MTOM requesting to leave the CTR via SIERRA, WHISKEY, or NOVEMBER.

Beluga Special Runway 05 does not exist.

Runway 27/09 has two additional specialBoth runway thresholds are connected to runway extensions increasing the TORA by roughly 300 m. These paved RWY extensions in front of each of the thresholds.respective IRLthresholds these canshall only be used foras special take-off byrunways for Beluga aircraft,and butBeluga onXL VATSIMaircraft we(A3ST allowand everyA337).

pilot

Departing whoTraffic

requests

Departing IFR traffic will automatically switch to usethe ondeparture offrequency thesestated extensionin viathe ATIS when airborne. 

The Beluga XL (A337) requires a backtrack from intersection C to dodepart so.from RWY 09 as this aircraft exceeds the wingspan limit at taxiway N.

Departures

Departure Releases

General Departure-Release: Departures do not have to be released by EDWW (Bremen Radar) except:unless:

• when EDWW explicitly restricts departures by time, SID or until further notice
• Departures out of athe non-activeoperational runway
   config
• The first departure after a runway change
  
• The first departure after an unplanned missed approach
  

Arriving Traffic

Auto-Handoff:After landing, Bremen hasTower 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 auto-handoffMTOM of more than 20 t, landing on runway 27, Bremen Tower shall instruct the pilot to thevacate departurevia frequencytaxiway immediatelyA afterbefore take-off, as stated inissuing the charts.
landing clearance. 

Spacing:Traffic Departureslanding shallon berunway separated09 with a minimumwingspan of 3more nmthan or36 wake turbulence separated, whichever is greater. When two aircrafts have the same SID waypoint (e.g. WRB) the separation shall be increased to 5 nm or wake turbulence separation whichever is greater. 

VFR above 5.700 kg MTOM: Departure via SID instead of visual reporting points.

Arrivals

Beside normal handoff procedures, arrivals on runway 27m 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 shall only be cleared to use the southern downwind due to noise abatement procedures.

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 whileinitially. taxiingBremen on taxiway A.

One of your primary objectives with arrivals is to keep the runways useable. Unfortunately some vPilotsGround will hold before the holding line blocking the runway, unless you keep them rolling. Issue taxi instructions as soon as possible or advice to hold behind the holding line while giving a handoff to Ground.

Missed Approaches

In case of an unplanned missed approach, the Tower controller shall inform Bremen RadarTower about the intentions of the departing VFR traffic. 

When runway 23 is active (Friesland)daytime immediately.only, winds permitting), VFR departures of up to 5700 kg MTOM requesting to leave the CTR via SIERRA, WHISKEY or NOVEMBER are assigned runway 23. Traffic will be handed overrequesting to depart from runway 27 is subject to prior approval from Bremen RadarTower. (Friesland)

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 coordination.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. 

Special VFR departure

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 nextdeparture routes may be issued for IFR traffic, except the following maximum altitudes after departure isshall alwaysbe subject to release, if not coordinated otherwise (Departure Release). 

VFR

Bremen offers three routes in and out of the CTR with two published holding patterns in the north and south of the field and a maximum altitude of 2000ft MSL. Traffic circuits are usually issued in the south of the field to prevent overflying inhabited areas.used:

2500ftorbelow

Maximum Altitude	RWY 09	RWY 27
VRP	Maximum	N	W	S1	S2	SOFED, BASUM, ERLAD, NIE	BASUM, ERLAD, NIE, GESTO, OTEXE, WSN
NAVMaximum 1500 ft or below	HarbourOTEXE, areaGESTO, Bremen CityWSN	South of Delmenhorst, A1 Highway Exit	Gessel, South of Bremen, Federal Road and Railway crossing	South of the field, A1 Highway Exit SOFED

SierraThe Route:departure S2routing 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 helipad between taxiways H, C and F. This helipad shall only be used for incomingrescue VFRhelicopter traffic. OutboundThe aircrafthelipad shouldmay proceedalso directlybe tocalled S1"Pad afterYankee" departure.
unofficially. 

Flights to EDWQ Ganderkesee directly west out of the control zone should not climb higher than 1500ft because of the D airspace west of the CTR. 

Helicopters

Helipad Yankee: only used for CHX55, other helicopters shall use the runway.

PoliceFor departure, Bremen Tower will be contacted directly. For arrivals, Bremen Tower will directly issue taxi clearance to the parking position. In all cases, Bremen Tower shall inform Bremen Ground about any movement via the helipad. The use of taxiway H during movement between the helipad and the DRF hangar is prohibited. 

Examples:

"Christoph 55, air taxi to Helipad, wind 100 degress 5 knots, cleared for takeoff helipad." 

"Christoph 55, after landing air taxi to parking, wind 100 degress 5 knots, cleared to land helipad." 

Other Rescue helicopters:Traffic

Within

Bremen
• KMCTR, =three Klinikumhospitals Bremen-Mitte
with
• SKHhelipads =exist. KlinikumRescue Delmenhorst
helicopter
• ZLWChristoph =6 Helipad(CHX06) "Z"is stationed at "Klinikum LinksLinks der Weser
  
  
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. 

Low Visibility OperationsProcedures (LVO)
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

DuringWhen low low-visibility operations,conditions exist, Bremen Tower shall instruct arriving traffic to vacate via taxiway F (RWY 09) or taxiway A (RWY 27) before issuing the departurelanding andclearance. arrivalThe spacinguse of intersection departures is increased.prohibited Delaysduring maylow-visibility be issued earlier than in normal conditions.operations.