Tower

Hamburg Tower kümmertis sichresponsible umfor denall restlichenarriving Groundbereich,and welcherdeparting nichttraffic. vomThe Aprontop abgedecktlevel wirdof the airspace D controlzone is 2500ft MSL. Above this altitude, airspace C covers this area around Hamburg within responsibility of Hamburg East/West Approach.

Controlzone of Hamburg Airport - © openflightmaps.org

Finkenwerder: In the west side of the controlzone is the Airbus Airport Finkenwerder EDHI. Traffic to and from Finkenwerder can cause critical situations in Hamburg. The responsible radar controller will give information about traffic. It may be necessary to:

• clear VFR aircraft in the area
• hold back departures, in coordination with radar
  

Additionally, when EDHI_TWR is unstaffed the whole aerodrome or some procedures (D1,e.g. F,VFR Gfrom westlichEDDH U),for sowieone allentouch an-and undgo abfliegendenin IFR-Verkehr,EDHI) sobaldcan siebe aufdelegated demfrom ILSradar sindto beziehungsweiseHamburg am Rollhalt stehen.Tower. 

DelegationHamburg CTR, Boberg Sector: only active at 33 arrivals or 15 departures

Ham-Finkenwerder CTR: only active with traffic in EDHI - airspace is in responsibility of Finkenwerder Tower (or Hamburg East Approach top-down)

Runways

Hamburg has a dependent crossing runway system with two runways.

Preferred Runway Config: 23 arrival and 33 departure is preferred and is used as long as possible (5kt tailwind component, pilot reports). All other runway configurations decrease your efficiency, increase target spacing for arrivals and causes more congestions on the ground. 

Helper: EDDH Wind/Runway Chooser 

Specialties

Visual example

blue = landing traffic RWY 23, orange = traffic ready for departure RWY 33

RollbewegungenTurmdelegiert,so

Runway 33 blocked!	Runway am33 Parkplatzclear, dera Allgemeinentake-off Luftfahrtclearance sindcan anbe denissued

dass

Crossing einRunway zügigesWake ein/ausrollenTurbulence möglichSeparation

ist.

Due Festeto Parkpositionenthe werdenposition amof the runway cross and the distinct system of separated landing and departure runways, there are only two situations which need to be watched for crossing wake turbulence separation:

• 05 or 15 departure with a go-around on the other runway. Departure needs to be delayed anyway due to missed approached procedure leading to HAM VOR!
• 33 light type departures before the runway cross. Prefer to assign intersection D9/A6 at the runway cross
  
  

Area of Responsibility

Additionally in Euroscope: Ground View > Functions > Maps > AoR

Movement at GA nichtdelegated vergeben.to Tower (green area): Taxiing out of and into the general aviation parking area is delegated to tower to ensure a steady traffic flow. Parking positions are not assigned to arriving traffic. Outbound traffic should be handed off to tower when they report ready for pushback or taxi, whichever comes first. 

Der

Departures

Spacing: Departures shall be separated with a minimum of 3nm or wake turbulence separated, whichever is greater. When two aircrafts have the same SID the separation shall be increased to 5nm or wake turbulence separation whichever is greater. Different aircraft performances and climb speeds need to be taken into account.

Efficiency: Try to sequence departures with alternating SID directions (west/east). In case of two westbound departures (different SIDs) out of runway 33, more spacing (4-5nm) is preferred but not mandatory, as all aircrafts fly the same route until ELSOB.

As there are distinct  landing and departure runways, use lineups constantly to issue take-off clearances as soon as possible.

Arrivals

Approaches: By default, the ILS Approach is used for all arrivals, except runway 33 or coordinated otherwise.

Runway 23 (very often): The target spacing is only 3nm on runway 23. In high traffic situations pilots need to vacate as soon as possible. Most of the time the phrase "taxi left via D1, hold short of runway 33" is used.

Runway 15 (regularly): The first exit is E4 to the left. Depending on the spacing on the final and planed parking position, long rollouts might be instructed to vacate left via D6 or right via D9.

Runway 05 (some times): Same as runway 23 pilots should vacate as soon as possible and be guided onto D1. In this case to have enough time for departures out of runway 33 before the next arrival is on short final.

Runway 33 (only at very strong winds): This RNP only approach is being avoided as long as possible as its path is directly above Hamburg city. All arriving traffic will taxi via E1 to hold short of runway 23 within the responsibility of the tower.

One of your primary objectives with arrivals is to keep the runways useable. Unfortunately some vPilots will hold before the holding line blocking the runway, unless you keep them rolling. Issue taxi instructions as soon as possible.

Handover to apron will take place as early as possible, at the latest when reaching the boundary of responsibility.

Missed Approaches: For all published approaches, the missed approaches will be as published, except coordinated otherwise. In case of a missed approach, the responsible radar station HAME (Hamburg East) or its top-down Center shall be informed via Topsky or verbally. Missed approaches as published all lead to the HAM VOR. Departures might need a delay until the situation is clear.

Efficiency

Reduced Runway Separation (RRS): Reduced Runway Separation can be applied on both runways for all categories.

Sequencing traffic: Keep up clearances and rolling instructions. A good sequence on default config (23/33) looks like:

• Landing Clearance runway 23
• Lineup runway 33
• Cross D1 traffic at runway 33 and send to East Apron
• Takeoff Clearance runway 33
• Taxi arrival on D1 hold short runway 33
  
  

VFR

Hamburg offers several options for traffic under VFR. There are published holding patterns north and south of runway 05/23 and east of runway 15/33.

kümmertsich-

VRP	NAV
N1	East abeam Kisdorf/Henstedt-Ulzburg
N2	Large roundabout at federal street B432
D	Highway junction A1 and A24
S1	Highway junction A7 and A261
S2	Bridge Köhlbrandt "Köhle"
W1	Marina/Yachthafen Hamburg, River Elbe
W2	Highway junction A7 and A23
C	Highway exit A23 Pinneberg-Nord, Radio Tower

auch

VRPs wennW2 es+ N2: these reporting points are pretty close to the runways. Be careful and respect the current runway config. Possible landing, departing and go-around traffic.

Finkenwerder: Good coordination between tower and approach is needed in seinemcase Luftraumof liegttraffic -at nicht um den AirbuswerksflughafenEDHI Finkenwerder. Dies ist Aufgabe des darüber liegendem Radarlotsen. Ein Tiefanflug in Finkenwerder soll mit dem Approach koordiniert werden, um unnötige Frequenzwechsel zu vermeiden.

Die Rollbahneinmündung E4 ist für Flugzeuge mit ICAO code lettre E oder kleiner zulässig (vgl. A1 und B1 am APR 1).

Depatures müssen durch den Tower angemessen vorgestaffelt werden. Wenn zwei Luftfahrezeuge auf der gleichen SID fliegen, muss der Abstand mindestens 5nm betragen, idealerweise wird die Lücke mit einer anderen Depature (andere SID) gefüllt.

VFR - Tower (EDDH_VFR_TWR)

InTower, East Apron, and Delivery need to be online before the VFR Tower can be staffed. 
Usually only staffed at the Hamburg bestehtHarbor dieFestival Möglichkeit,and einenthe VFR-TowerOverload zuReal-life öffnen. Hierzu sind die geltenden Besetzungsregeln zu beachten.
In der Realität hat dieser die Möglichkeit mittels Radar präzise Verkehrsinformationen zu geben und den VFR-Verkehrsfluss effizient zu gestalten. In seinen Aufgabenbereich fallen alle VFR Flüge im Bereich der Kontrollzone so auch Ein-/ Aus-/ und Durchflüge. Platzrundenflüge und Pistenfreigaben bleiben im Zuständigkeitsbereich des normalen Towers. Damit Verkehrsinformationen mit exakten und verifizierten Höhenangaben gegeben werden können, darf der R_TWR Squawks zuweisen und die Squawkvergabe für abfliegenden Verkehr aus Hamburg an Apron/Tower delegieren. Abflüge werden nach dem Start durch den Tower an den Radar-Tower übergeben. Für Übergaben von Anflügen nach Hamburg können individuelle Absprachen getroffen werden, jedoch empfiehlt sich für bestimmte Pistenkonfigurationen die Außenalster als visueller Referenzpunkt im Süden des Flughafens.
Die effiziente Abwicklung des Verkehrs kann nur durch gute Kooperation und Koordination zwischen Tower und Radar-Tower gewährleistet werden.

HubschrauberEvent.

Auf dem Gelände des Flughafens sind die beiden Polizeihubschrauber der Polizei Hamburg stationiert. Die Station befindet sich am östlichen Ende des Vorfeldes 5 . Starts und Landungen werden aufgrund der baulichen Gegebenheiten mit direkten Ab- und Anflügen von bzw. zur Plattform durchgeführt. Ca. 6 km südöstlich des Platzes innerhalb der Kontrollzone befindet sich das Bundeswehrkrankenhaus, hier ist der Christoph 29 stationiert. Innerhalb des Sektors Boberg befindet sich das Unfallklinikum der Berufsgenossenschaft, hier ist der Christoph 50 (Hansa) beheimatet. Auch sind im näheren Umfeld des Flughafens mehrere Krankenhäuser die zum Teil überregionale Bedeutung haben und daher auch von externen Rettungshubschraubern angeflogen werden.

In reality the Hamburg VFR Tower is a station to provide precise traffic information using radar coverage and to organize the VFR traffic flow efficiently. Its area of responsibility includes all VFR flights in the area of the control zone, as well as entry/exit/through flights. Traffic circuits and runway clearances remain the responsibility of the normal EDDH_TWR.

In order to provide traffic information with exact and verified altitude information, the EDDH_VFR_TWR may assign squawks and delegate the squawk assignment for departing traffic from Hamburg to Apron/Tower. Departures are handed over to the radar tower after takeoff. Individual arrangements can be made for handovers of approaches to Hamburg but for certain runway configurations the Outer Alster is recommended as a visual reference point in the south of the airport.

The efficient handling of traffic can only be guaranteed through good cooperation and coordination between the tower and the radar tower.

Helicopters

Departures directly from the parking position are not permitted. All helicopter traffic needs to air-taxi from and to the helipad, except helicopters based at the police station.

Helipad West: Main arrival/departure point for helicopters in Hamburg. 

Helipad East: Helipad East between B1 and B3 is not used that often or is closed via NOTAMS. Prefer using Helipad West. 

Police helicopters: The police helicopters are based at Hamburg Airport east of apron 5 (H Pol1 / H Pol 2), Callsign "Libelle". These helipads are not reachable via air-taxi and can only be used for direct arrival/departures. Pilots will communicate directly with the tower.

Rescue helicopters: There are no rescue helicopters located at the airport but within the area of the tower control zone. In EuroScope werdenthe diesurounding Klinikenhospitals undwith Krankenhäuserhelicopter innerhalbplatforms derare Kontrollzonedisplayed wieas:

folgt

• AKA = Asklepios Klinik Altona
• AKE = Schön Klinik Eilbek (ehm. Asklepios Klinik Eilbek)
• AKH = Asklepios Klinik Nord (Heidberg)
• BWK = Bundeswehrkrankenhaus - StandortStation of CHX29 (ehm. SAR71 = CS/MEDEVAC+REG)
• KWS = Kath. Kinderkrankenhaus Wilhelmstift
• STG = Asklepios Klinik St. Georg
• UKB = BG Unfallklinikum Boberg - StandortStation of CHX50 (Hansa)
• UKE = Universitätsklinikum Eppendorf

Low Visibility Operations (LVO)

When the weather condition requires low visibility operations the use shall be announced in the ATIS. At runway 23 the CAT II / CAT III needs to be used.

use &lvp in the ATIS maker URL or "LOW VIS OPS" flag in the NOTAM menu of vATIS

During low visibility operations, the departure and arrival spacing is increased. Delays may be issued earlier than in normal conditions.  Additionally, under low visibility operations runway 33 or 23 shall be used for departures and 23 for arrivals.