TTX – 3/4

When the parties concerned, on the basis of known intelligence, agree to a course of action.

- direct negotiation and agreement for individual flights
- standing agreements made in accordance with local procedures (= letters of agreements)
- use of permanent procedures agreed between national aviation authorities
- electronically

letter of agreement!

- standard clearance (by CLD, variations need coordination), AND
- tower keeps APP informed of departure sequence and runway in use, AND
- assigned SID must be displayed to ADC, APP and ACC sector

- unless prior coordination, aircraft must NOT be permitted to cross airspace of other unit

- responsible for initiating coordination is controller of transferring unit

- transferring unit controller must comply with conditions of accepting controller

Not enough time to transmit FPL data

- prior coordination needed!
- boundary estimate based on estimate time of departure

- at an agreed reporting point
- on an estimate for a boundary
- at or passing an agreed level
- acft is in climb/descent to a previously agreed level
(transferring controller has ensured that standard separation exists)

When flight has reached the position or level agreed between the units.

= without systematic use of bi-directional speech facilities, if:

- detailed conditions are specified in local procedures
- successive aircraft are separated when transferred and separation is maintained or increased
- bi-directional speech facilities are available at all times

So that instructions which become effective later can already be issued now.

Don't alter existing clearances without approval.

Immediately after accepting ATCO has agreed to assume control.

- normally silent handover
conditions: descending to FL130, own navigation within 5 NM of correct route

- 20 NM separation for subsequent arrivals (same performance, no catch up)

- OMEGA APPROACH must inform SWISS RADAR immediately if holding at FRI/HOC at or above FL 130

- APP may change heading by maximum 45° either side prior TMA boundary

coordination needed!
responsible for doing coordination to C is B!

only accept if:
- satisfied with transfer conditions
- traffic permits
- workload permits

sufficient time of analysis needed

explicitly state that you accept the transfer

movement data
control data

- information concerning missed approaches
- information about aircraft that constitute essential local traffic to acft under control of APP unit
- acft performing (or requesting to) unusual procedures which will affect management by APP unit

- information concerning missed approaches
- essential local traffic to acft under control of APP unit
- arrival and departure times for IFR flights (OMEGA: departure times for IFR)
- first acft in approach sequence is in communication with and sighted by ADC unit and reasonable assurance that landing can be completed
- information relating to overdue or unreported aircraft
 

- aircraft approaching to land (if neccessary request landing clearance)
- acft cleared to visual holdint points
- acft routing through traffic circuit
- estimated time + proposed level of arriving acft over aerodrome, at least 15 min prio estimated arrival
- statement that acft has been cleared to contact ADC and controll shall be assumed by that unit
- anticipated delay to departures due to congestion

prior to departure, according to local procedures

specified by APP in case of conflicts

APP unit (if not specified otherwise)

As soon as possible after acft is airborne and no conflict exists with aerodrome traffic under your control.

For the safe and efficient use of airport runways and movement areas.

coordination displays
verbal means
flight progress strips
other reading information

Local procedures! if:

- all control and relevant flight plan data are transmitted by other means
- radar or vertical separation exists
- reasonable assurance that separation will be maintained or increased
- bi-directional speech facilities exist to permit verbal communication

Apron Management Service

- limits of areas of responsibility described in local procedures
- inform AMS of any unusual situation which may affect handling of ground traffic
- coordinate to prevent conflicts (aircraft, vehicles) at the limits of area of responsibility

Approach control
to organise approach/departure sequences and advise best time for chance

Area control (advised through APP)
to issue alternate inbound routes and coordinate new departure routes with adjacent sectors

Adjacent aerodromes
potential conflicts of traffic circuits and/or arrival/departure routescan be coordinated

Pilots
so that they receive sufficient warning / time to re-plan and adjust FPL

- approach control
- aircraft under your control
- aerodrome fire service
- contractors working on the aerodrome who will be affected by the change
- other agencies according to loca instructions

1. Advise OMEGA Approach of impending runway chance
2. Inform Approach of LAST departure from current runway (+last arrival)
3. Inform Approach of FIRST departure from new runway (+first arrival)
4. Advise Approach of new IFR departure sequence
5. Request new IFR departure clearance (SID)
6. Advise airborne traffic of impending runway change
7. Reposition inbound and circuit traffic for new runway
8. Inform all pilots of new landing sequence
9. Advise traffic on ground of new runway
10. Reposition all traffic on ground to new runway