TRAMON
General
TRAMON (short for TRA monitor) is a position used to monitor traffic performing manoeuvres within a restricted area (e.g. TRA). This position is a special working position and does not involve tactical control services. In contrast to the tactical control service of Loneship and Sunrsie, TRAMON is staffed by civil ATCOs.
Positions
TRAMON can be staffed on Vatsim as ETXX_TRA_CTR (130.510)
Tasks
When staffed, TRAMON has the following tasks:
- Activation and deactivation of TRA, as coordinated with the airspace users
- Coordination of TRA opening and closure with the relevant ATC positions
- Clearance to enter or exit a TRA, in coordination with the relevant ATC positions
- Information for traffic within a TRA when the required distance to the area boundary is about to be lost
- Coordination with the relevant ATC positions when traffic within the TRA cannot maintain the required distance to the area boundary
- Traffic information about other traffic inside or crossing the TRA (as far as possible)
- Takes over further tasks such as tanker missions (AAR) and formation splits or formation join-ups
In some cases, TRAMON can also take departing traffic from a military airfield directly, if this traffic requests to enter the TRA directly after departure. This needs to be coordinated with the relevant ATC positions.
TRAMON will not perform any Fighter Control (FC). For this, the stations Loneship (ETXX_LS_CTR) and Sunrise (ETXX_SR_CTR) shall be used, which require a Tier 2 endorsement to be staffed. When Loneship or Sunrise are online, they will perform the TRAMON tasks for the area.
Distances to TRA Boundary
- TRA:
- laterally 2.5 NM (If agreed with ATC, TRA traffic does not need to maintain distance to boundary, ATC shall apply 5 NM)
- vertically 1000 ft below FL290, 2000 ft above FL290 (500 ft if division level in between to FLs, e.g. FL245)
- MVPA:
- Traffic inside MVPA does not need to maintain distance to the boundary; ATC will apply 5 NM and 1000 ft or 2000 ft
Examples
Example 1 - TRA Entry
This example describes a situation where the IFR cancellation is performed by the ATC sector after coordination with TRAMON. The IFR is cancelled before entering the TRA.
Example: (🎧 = EDWW, 📡 = TRAMON)
🎧: "TRAMON, Müritz."
📡: "Go ahead!
🎧: "Radar Handover, SNAKE, 23 NM, west TAGOB, FL210, for TRA operations."
📡: "Identified, TRA operations approved inbound TAGOB, squawk 7415."
🎧: "Consider!"
The ATC sector will then issue the clearance to enter the TRA to SNAKE on frequency.
Example: (🎧 = EDWW, 👨🏻✈️ = Pilot)
🎧: "SNAKE, report flight conditions."
👨🏻✈️: "SNAKE, VMC"
🎧: "SNAKE, IFR cancelled 1235, cleared to operate BASIC1A, 1B, 1C, 1D, FL100 up to FL320, squawk 7315, contact MONITOR <frequency>."
Example 2 - TRA Entry
This example describes a situation where the IFR cancellation is performed by TRAMON. In this case traffic TRAMON will state the entry conditions before traffic is cleared into the TRA.
Example: (🎧 = EDWW, 📡 = TRAMON)
🎧: "TRAMON, Müritz."
📡: "Go ahead!
🎧: "Radar Handover, MMF41, 28 NM, south KUBAB, FL260, for air to air refuelling JANIN anchor."
📡: "Identified, Heading 350, descend to FL220, squawk 7432."
🎧: "Consider!"
TRAMON will then issue the IFR cancellation.
Example: (📡 = TRAMON, 👨🏻✈️ = Pilot)
👨🏻✈️: "TRAMON, hello, MMF41, heading 350, FL220"
📡: "MMF41, identified, report flight conditions."
👨🏻✈️: "MMF41, VMC"
📡: "MFF41, IFR cancelled 1235, cleared to operate BASIC1A, 1B, 1C, 1D, 1E, FL100 up to FL320, enter JANIN anchor FL220."
Example 3 - TRA Exit
TRA exits can be performed in several ways. Either the traffic requests to leave the TRA VFR into airspace E, or traffic can leave IFR. When leaving IFR, TRAMON coordinates the IFR clearance with the relevant ATC sector or issues a frequency change to the ATC sector (free call).
The following example describes a situation where TRAMON coordinates an IFR clearance with the ATC sector.
Example: (🎧 = EDWW, 📡 = TRAMON)
📡: "Müritz, TRAMON."
🎧: "Go ahead!
📡: "Radar Handover, SNAKE, squawking 7315, position 15 NM east of LAG, FL185, request IFR clearance to ETNS."
🎧: "Identified, cleared to ETNS via direct SWG, FL180, squawk 1132, IFR starts now."
📡: "<readback>"
TRAMON will then issue the IFR clearance to the pilot and transfers the aircraft to the next ATC sector.
Example 4 - TRA crossing with millitary jet aircraft
TRA transits of military IFR jet traffic through an active TRA are often generally approved by TRAMON. TRAMON shall be informed about the crossing traffic in due time.
In general TRA traffic will not be separated to other military jets crossing the TRA (inter-military risk).
Example: (🎧 = EDWW, 📡 = TRAMON)
🎧: "TRAMON, Müritz."
📡: "Go ahead!"
🎧: "Information on TRA crosser, THUNDR1, 2 ship tornado formation 10 miles west of MASOR, FL200, on course to LAG."
Usually, the crossing traffic stays on the frequency of the ATC sector. For these flights a traffic information shall be given, when entering the area.
Example: (🎧 = EDWW, 👨🏻✈️ = Pilot)
🎧: "THUNDR1, you are entering active TRA, traffic information, single Eurofighter, bearing 035, distance 37 NM, indicated FL200."
👨🏻✈️: "TUNDER1, roger, looking out"
TRAMON shall also issue traffic information for traffic inside the TRA as far as possible.
The same procedure shall be applied for civil traffic crossing TRAs on TRA priority airways. Important to note: This traffic needs to be separated to traffic within the TRA (see example 5).
Example 5 - TRA crossing with civil or military transport aircraft
In general, TRAMON shall not approve any TRA crossing for civil or military transport aircraft except for:
- Flights for which an emergency has been declared
- SAR flights
- Medical flights
- Flights avioding dangerous WX phenomena
Traffic crossing the TRA (except military jet aircraft) are required to be separated to traffic inside the TRA. In this case, TRAMON will usually adjust the lowest/highest available level for the TRA usage or block certain TRA sectors until the crossing traffic as passed. Remember that traffic in the TRA is still VFR. Additionally, TRAMON shall issue traffic information about the TRA crosser as far as possible.
Example: (🎧 = EDWW, 📡 = TRAMON)
🎧: "TRAMON, Müritz."
📡: "Go ahead!"
🎧: "Approval request for TRA crossing, due to weather, EJU34BA, A320, 10 NM north of ARGAD on heading 170, FL250, for approx. 25 NM."
📡: "Approved!"
The ATC sector shall then coordinate the further routing with TRAMON once the aircraft is clear of weather again.
Example: (📡 = TRAMON, 👨🏻✈️ = Pilot)
📡: "SNAKE, lowest usable FL260 due to stranger, bearing 025, range 15 NM, FL250, track south."
👨🏻✈️: "SNAKE, copy, lowest FL260"