| [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-11/mafimage.png) | [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2023-11/oIaimage.png) |
| **Runway 33 blocked!** | **Runway 33 clear, a take-off clearance can be issued** |
**Movement at GA delegated 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.
### Departures **General Departure-Release:** 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 - Departures using OID or vectored departure **Auto-Handoff:** Hamburg has an auto-handoff to the departure frequency when passing 2000ft, as stated in the charts. A short "bye bye" at the end of the take-off clearance can help vPilots to get the hint. **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, left/right in relation of the runway track. In case of two westbound departures (different SIDs) out of runway 33, more spacing (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 A6 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 In case of an unplanned missed approach, the Tower controller shall inform Hamburg East Approach immediately. Traffic will be handed over to Hamburg East Approach after coordination.The next departure is always subject to release, if not coordinated otherwise ([Departure Release](https://knowledgebase.vatsim-germany.org/books/coordination/page/departure-release)).
### Efficiency **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 ### Reduced Runway Separation (RRS) Hamburg Airport (EDDH) is approved to apply the following reduced runway separation minima during day and night:| **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 05/23 | 600 m | 1500 m | 2400 m |
| RWY 15/33 | 600 m | 1500 m | 2400 m |
| **VRP** | **NAV** |
|---|---|
| **N1** | East abeam Kisdorf/Henstedt-Ulzburg |
| **N2** | Large roundabout at federal street B432 |
| **D** | Highway junction A1 and A24 |
| **T1** | Bridge of federal street B75 leading above the railway tracks |
| **T2** | Track harp the cargo rail station Hamburg Süd (Veddel beim Spreehafen) |
| **H** | Marina/Yachthafen Hamburg, River Elbe |
| **P1** | Highway exit A23 Pinneberg-Nord, Radio Tower |
| **P2** | Highway junction A7 and A23 |
Tower, East Apron, and Delivery need to be online before the VFR Tower can be staffed. Usually only staffed at the Hamburg Harbor Festival and the Overload Real-life Event.
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 the surrounding hospitals with helicopter platforms are marked as square with an x inside. The names can be activated with ALT-H. [](https://knowledgebase.vatsim-germany.org/uploads/images/gallery/2024-05/helipads-eddh.png) ### Low Visibility Operations (LVO) At Hamburg, the following runway configurations are allowed during LVO: - Departures 33\*, Arrivals 23 (preferred configuration) - Departures 23, Arrivals 23 (alternative configuration) Single Runway Operations during LVO requires a larger spacing between arriving traffic. Therefore 33 Departures, 23 Arrivals is the preferred runway configurations whenever RVR and wind permit.\* Note: Runway 33 can only used for departing traffic if the RVR is not less than 150 m.
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.