Eelde Tower

Position Information

ATC CallsignEelde Tower
ATC CodeEHGG_TWR
FRA RequirementAS2
Frequency118.700
Airspace classC

Area of Responsibility

Eelde Tower is responsible for traffic on the aprons, runway and in the EHGG Control Zone. It is Eelde 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. Eelde Tower will also cover the responsibilities of Eelde Delivery in his absence


General Procedures

Runway usage

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.

Departures

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

Cancellation of a takeoff clearance.

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.
    Keep in mind that if the pilot has passed his V1 speed (point of no return) he cannot abort his takeoff.

Arrivals

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

Cancellation of a landing clearance:

Tower has the authority to revoke a landing clearance, he can either do this by:

  • Cancelling 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

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.

Remarks on delay techniques:

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

Local Procedures

Runway selection

At Eelde runway 23 is preferred, with winds at or below 06kts runway 23 is to be used. With higher winds the runway that has the most headwind shall be used.

Ground movement

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)

A crossing or taxi via a runway clearance shall be issued when the traffic is no conflict for any other traffic on or approaching the runway.

  • If the pilot did not request the crossing/taxi: Cross runway 05/23 at (intersection) or Taxi via runway 01/19 to (position)

  • If the pilot has requested the crossing/taxi: Crossing runway 05/23 at (intersection) approved or Taxi via runway 01/19 to (position) approved

 

Circuit and VFR routes

Eelde has the following arrival and departure route for VFR:

  • X and U (departure) at 1000ft

  • Y and R (arrival) at 1500ft

Eelde has three VFR circuits for runway 05/23, one at 1000ft north/west of the runway for light aircraft at ATC discretion only, one normal circuit at 1000ft south/east of the runway for light aircraft and a big circuit at 1500ft south/east of the runway for other aircraft .


Handovers

Departures should be transferred to (in order of writing) as soon as practicable but at latests when passing 2000ft:

  • EHGG_APP

  • EHAA_E_CTR,

  • EHAA_W_CTR

  • UNICOM

R/T Examples

Pilot ATC

VFR Flight to Rotterdam, Startup issued by Eelde delivery.

Eelde Tower, PHABC, Cessna 172, VFR to Rotterdam, information A, Request Taxi.

PHABC, Taxi Holdingpoint runway 23

Taxi Holdingpoint runway 23, PHABC

PHABC at holdingpoint runway 23 ready for departure

PHABC Wind 230 degreed 05 Knots X-ray departure, runway 23 cleared for takeoff

X-ray departure, runway 23 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 Eelde Quickview.

A conditional lineup clearance,

PHABC, behind the landing Boeing 737 line up runway 23 behind

Behind the landing Boeing 737 line up runway 23 behind, PHABC

PHABC, correct

VFR Flight From Rotterdam to Eelde approaching Romeo.

Eelde Tower, PHABC, Cessna 172, Approaching Romeo 1500ft, information A

PHABC, Squawk 0060

Squawk 0060, PHABC

PHABC, Cleared Romeo arrival runway 23 QNH1013 information A correct

Cleared Romeo arrival runway 23 QNH1013, PHABC