| ATC Callsign: | Rotterdam Tower |
| ATC Code: | EHRD_TWR |
| FRA Requirement: | AS2 |
| Frequency: | 118.205 |
| Airspace class: | C |
Rotterdam Tower is responsible for traffic on the aprons, runway and in the EHRD Control Zone. It is Rotterdam Tower's responsibility to safely, but expeditious, manage the flow of traffic: aircraft taxing to and from the runway, aircraft landing and taking off, aircraft entering, leaving or transiting through the CTR. Rotterdam Tower will also cover the responsibilities of Rotterdam Delivery in his absence.
Tower is responsible for the usage of the runway, only one aircraft shall be cleared to use the runway at any time, only exemption is a line up behind a just departed or landed aircraft. The runway is considered to be clear when a airborne aircraft has passed either the runway end or runway sides or if a aircraft on the ground has passed a holding point line completely.
Before allowing an aircraft to enter the runway (for takeoff or lineup) tower shall:
There is no traffic on short final that will not be able to land due to the aircraft entering the runway. If so an arrival shall if possible be delayed (vfr circuit/extend downwind), if this is not possible the aircraft shall not be allowed on the runway.
Before issuing a departure clearance (takeoff clearance) tower shall:
Check if the runway is clear
Check if wake turbulence is no factor (this includes a previous touch and go, they are an arrival AND departure)
Issue any additional instructions
If required for safety Tower is allowed to revoke a takeoff clearance or have the pilot abort his takeoff. This can either be done by:
If the aircraft is not yet moving, cancellation of the takeoff clearance
If the aircraft is moving the abortion of the takeoff roll.
NOTE:
Keep in mind that if the pilot has passed his V1 speed (point of no return) he can not abort his takeoff.
Arriving traffic (IFR) is handed to the tower controller either established on ILS/VOR/NDB final or with the runway in sight for a visual approach.
Tower shall on initial contact with the arrival:
if possible issue a landing clearance
else tell the pilot to continue his approach and give him the number in sequence for landing (number 1 is the aircraft closest to but not yet passed the runway threshold, traffic on the runway does not add to this number)
Before issuing a landing clearance tower shall check that:
The runway is clear
Tower has the authority to revoke a landing clearance, he can either do this by:
Canceling the landing clearance, this will have the arrival continue his approach and could be used to have an other aircraft make a touch and go or departure in front of the arrival.
Issue a go around instruction, in this case the approach has to be aborted and the aircraft shall continue on the published missed approach or follow instructions of the tower.
VFR traffic will normally follow published VFR routes. Tower is allowed to deviate from this if traffic permits by agreeing on a different route with the pilot, if no satisfactory route can be agreed on VFR shall follow the published routes.
With the CTR class C Tower is responsible to separate IFR from VFR and vice versa, VFR flights have to separate themselves if traffic information is given to both VFR flights.
VFR flights en-route and in the circuit can be delayed by giving an orbit, either at a reporting point or at a point in the circuit.
VFR circuit traffic could also be delayed by extending there up or downwind leg, if the tower decides to extend he is responsible for turning the aircraft back to crosswind or base, and from there the VFR flight shall continue his circuit. The tower may clear the VFR flight to turn base behind an arriving aircraft when the VFR traffic has the other arrival in sight, if applicable the VFR flight has to be warned about wake turbulence.
If a circuit trainer gets to close to a preceding aircraft he can be cleared for a stop and go in stead of a touch and go, in this case tower informs the pilot this will be a touch and go and clears him to land, if spacing is sufficient tower issues a takeoff clearance.
Traffic in an orbit is unable to see other traffic, make sure there is sufficient space between multiple orbiting flights.
Do not let your circuit get to big! Every mile a flight has to extend he has to fly back.
NOTE:
VFR circuit traffic either on touch or stop and go is considered an arrival and departure, therefore has to have sufficient wake turbulence separation with a preceding departure!
Tower may hand this responsibility to the pilot by informing him of the heavier traffic ahead and issuing a clearance regarding that traffic and his wake.
At Rotterdam runway 24 is preferred, with winds at or below 06kts runway 24 is to be used. With higer winds the runway that has the most headwind shall be used.
If Schiphol has runway 06 or 36R for landing Rotterdam shall use runway 06 for landing.
Tower is responsible for all ground traffic and hands out taxi clearances, a taxi clearance consists of:
Taxi to … (location)
(runway if the location is a holding point)
via (taxi route)
At Rotterdam taxiways shall be used as follows:
Taxiway N is for arrivals using rwy 06 and departures using rwy 24
Taxiway Y is for arrivals using rwy 24 and departures using rwy 06
Rotterdam has the following arrival and departure routes for VFR:
H- arrivals at 1500ft, departures at 1000ft
R- 1500ft
M- 1000ft
* Waterweg Arrival - 1500ft or at ATC discretion - Routing: HOTEL-WEST ABEAM MAASLUIS-EUROMAST-PAPA
Rotterdam has two VFR circuits, one at 1000ft for arrivals and one at 500ft for circuit training flights. The 500ft circuit has two published holdings named A and B.
All circuits at Rotterdam are located at the northwest side of the airfield
Departures should be transferred to (in order of writing) as soon as practicable but at latest when passing 2000ft:
All runways:
ARNEM, ANDIK and LUNIX to EHAM_W_APP, EHAA_CTR or UNICOM.
this traffic is NOT transferred to EHRD_APP
Runway 06:
All other SID's to EHRD_APP, EHAA_SW_CTR, EHAA_CTR or UNICOM
Runway 24:
All other SID's to EHRD_APP, EHAA_SW_CTR, EHAA_CTR or UNICOM
Pilot
ATC
VFR Flight to Eelde, Startup issued by Rotterdam delivery.
| Rotterdam Tower, PHABC, Cessna 172, at Lima, VFR to Eelde, information A, Request Taxi. |
| PHABC, Taxi Holdingpoint runway 24 (via V) |
| Taxi Holdingpoint runway 24 (via V), PHABC |
| PHABC at holdingpoint runway 24 ready for departure |
| PHABC Wind 230 degreed 05 Knots Hotel departure,runway 24 cleared for takeoff |
| Hotel departure, runway 24 cleared for takeoff, PHABC |
The Departure given in this example is for illustration purposes only, all departures and arrivals VFR can be found on the Rotterdam Quickview.
A conditional lineup clearance,
| PHABC, behind the landing Boeing 737 line up runway 24 behind |
| Behind the landing Boeing 737 line up runway 24 behind, PHABC |
| PHABC, correct |
VFR Flight to Rotterdam approaching ROMEO.
| Rotterdam Tower, PHNSC, Robin DR 400, request to enter your CTR via ROMEO, for landing, received info A |
| PHNSC, Rotterdam Tower, Info A is correct, cleared to enter CTR via ROMEO Arrival, runway 24, QNH1013 |
| ROMEO arrival, runway 24, QNH1013, PHNSC |
- When overhead Visual Reporting Point (VRP) OSCAR: | |
| PHNSC is overhead OSCAR |
| PHNSC, roger, report PAPA |
| PHNSC, after PAPA, cleared to cross in the middle, 1000 feet, report right downwind |
| Cleared to cross in the middle, 1000ft, wilco, PHNSC |
