CONTROLLER DEVELOPMENT

Ask questions of the training staff and fellow controllers. Also training FAQs

Moderator: ZSE Administrative Staff

Locked
Peter Armstrong
ZSE Controller
ZSE Controller
Posts: 392
Joined: Fri Dec 11, 2015 8:05 am

CONTROLLER DEVELOPMENT

Post by Peter Armstrong » Sun Apr 22, 2018 3:25 am

CONTROLLER DEVELOPMENT

Controller development can come in many forms. The traditional form is for an INS to teach and the Student to learn. However, controller development has changed and is continually changing, as is all forms of training and development in the real world that we live in. Even VATSIM has changed. We now have INS/Mentors and Unofficial Monitors. And, with the adage of sweatbox and all the tools within our programmes such as VRC , we now have an opportunity to embrace a host of training tools including Feedback (whether it be positive or negative) but, I believe that the negative should be constructive and not destructive.

With this in mind – and without pointing a finger at any individual Student of ATC – I would like to suggest that we all can observe and notice any mistakes or bad habits that we may witness. And in so doing, we can highlight such occurrences on this Forum for the benefit of all. Not forgetting that we may also compliment each other and recognize good practice. One other area of our training which we all forget is – being current! It can be a little confusing when we believe that our training – which may have happened lots of years ago – is now no longer valid (current). I would also suggest that this Forum can help seasoned controllers to be brought up to date with current practices.

The most important outcome of our training is that we can all use the exact same phraseology/terminology – we can all be in sync with the VATSIM interpretation of FAA regulations and, when that happens, our pilots can most probably predict what we are about to say which will give them confidence and enjoyment – and that’s what the best outcome of all this is – enjoyment.

This Forum can then become an “arm” of our training regime where observers can post their observations and – others can also observe the observers! So – caveat emptor you keen observers.

Peter
Happy controlling/flying :beer:
Valor Morghulis
Valor Dohaeris
Caveat Lector

Peter Armstrong
ZSE Controller
ZSE Controller
Posts: 392
Joined: Fri Dec 11, 2015 8:05 am

Re: CONTROLLER DEVELOPMENT

Post by Peter Armstrong » Mon Apr 23, 2018 2:35 am

Phrase “say altitude passing”. If, as a Dep controller, you have cleared the A/C (DEL/GND/TWR) for take-off and, that A/C is the only A/C within 150nm of the airport, do you need to use this phrase?
Happy controlling/flying :beer:
Valor Morghulis
Valor Dohaeris
Caveat Lector

Peter Armstrong
ZSE Controller
ZSE Controller
Posts: 392
Joined: Fri Dec 11, 2015 8:05 am

Re: CONTROLLER DEVELOPMENT

Post by Peter Armstrong » Tue Apr 24, 2018 11:03 am

VARIATIONS OF DEPARTURE/RADAR CONTACTS?

“radar contact”

Climb and maintain xxxx
Climb via the sid (Atome2) KSEA
Climb via the sid except maintain xxxx
Climb and maintain xxxx, cleared direct XYZ
Climb and maintain xxxx, fly hdg 123 direct XYZ
Climb and maintain xxxx, clrd dct XYZ to join ABC(airway)
Climb and maintain xxxx, fly hdg 123 direct XYZ to join ABC
Climb and maintain xxxx, fly hdg 123 direct XYZ when able
Happy controlling/flying :beer:
Valor Morghulis
Valor Dohaeris
Caveat Lector

Peter Armstrong
ZSE Controller
ZSE Controller
Posts: 392
Joined: Fri Dec 11, 2015 8:05 am

Re: CONTROLLER DEVELOPMENT

Post by Peter Armstrong » Wed Apr 25, 2018 3:10 am

Communications with pilots

I suppose that when communicating with pilots you have to be accurate, precise and deliberate. However, sometimes we hear “uhms” and “Arrhs” even “please” – “descend and maintain 4000 please”. Plus loads of other verbiage and verbosity.

Also, we should be brief. If we use separate instructions:-
• Cross point at 6000
• Depart point heading 165
• Descend and maintain 4000
We are introducing much more communication interruptions than is required. Could be a problem if busy with other traffic.

It would be much cleaner to use:-
• Cross point at 6000
• Depart point heading 165, then descend and maintain 4000
Or, some other integrated message to suit the occasion.

There are many more such example instances that could be quoted here but, suffice it to say, be precise, accurate, deliberate and brief and most of all – follow the FAA/VATSIM/VATUSA guidelines on these matters.
Happy controlling/flying :beer:
Valor Morghulis
Valor Dohaeris
Caveat Lector

Austin Wilkins
ZSE Controller
ZSE Controller
Posts: 34
Joined: Thu Aug 18, 2011 3:42 pm

Re: CONTROLLER DEVELOPMENT

Post by Austin Wilkins » Sat Apr 28, 2018 1:17 pm

Peter Armstrong wrote:
Mon Apr 23, 2018 2:35 am
Phrase “say altitude passing”. If, as a Dep controller, you have cleared the A/C (DEL/GND/TWR) for take-off and, that A/C is the only A/C within 150nm of the airport, do you need to use this phrase?
Unless you are not watching the aircraft depart from the airfield, and you do not radar identify them within the 1NM radius with a ROLLING CALL around the airfield, you must positively identify them, and the easiest way to do this is via altitude verification. This is a VATSIMism that is commonly misconcepted. One must ALWAYS identify the a/c within one mile or you have to either verify with altitude, an IDENT, squawk standby, then mode C, etc. Please refer to this video - http://media.aero.und.edu/avit.und.edu/a-v/atcpc01.mp4

Working top-down does not mean we can take short cuts
Austin Wilkins | VATUSA13
Deputy Training Director | http://vatusa.net
VATSIM Network Supervisor | http://vatsim.net
Former: ZSE_TA, HCF_DATM

Locked