1
News / Re: VATUSA 3 Retirement and New Training Director
« on: February 27, 2019, 10:00:36 AM »
+1 and +1!
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
2
The Control Room Floor / Re: Squawk Readback Correct
« on: February 16, 2019, 02:43:02 AM »
I have also heard “squawk readback correct” in real-world. I’d suggest this is not a VATSIM-ism, but is rather a natural variation that can be permitted to persist. In fact, some variability in phraseology contributes to immersion.
We’ve got bigger fish to fry in training more generally. For instance, I’m focused more on ensuring our students appreciate the difference between “Cleared to” and “Cleared direct”!
Also...... unable end of world. Say intentions.
We’ve got bigger fish to fry in training more generally. For instance, I’m focused more on ensuring our students appreciate the difference between “Cleared to” and “Cleared direct”!
Also...... unable end of world. Say intentions.
3
General Discussion / Re: VATSIM Testing new CODEC
« on: January 22, 2019, 02:41:54 PM »
“I heard ....Be..... Mas....... One-Niner.... but transmission faint and broken. Say again?”
4
The Control Room Floor / Re: Visual Separation and You: Dos and Don'ts
« on: January 06, 2019, 12:48:06 PM »
A question for the experts: I’ve heard on occasion in real-world, tower ask if a second departure has visual on a rolling first departure (typically same wake class). Once acknowledge, the second departure is given “maintain vis sep from that a/c, cleared for takeoff”). I’ve always assumed that is done where they don’t have diverging headings for the two a/c but expect they will turn-out in different directions once with Departure, so the vis sep allows a quicker launch for second a/c. From this thread, I’m not clear whether this is a correct interpretation of what is happening, though. Maybe the first a/c was VFR.
Thoughts?
Frank
Thoughts?
Frank
5
News / Re: ZLA has a New Training Administrator!
« on: December 18, 2018, 08:54:39 PM »
Welcome aboard! Drinks service starts after we climb through 10,000.
6
Events / Re: Events: Tell us your thoughts!
« on: September 14, 2018, 06:59:29 AM »
I've always been delighted to see a mix of commercial jet traffic with local GA traffic. My perverse joy arises by having VFR or slow-mover IFR traffic (both at the primary airport and the satellites) integrated with the usual stream of jets.
Any event that encourages that sort of thing that gets my vote!
Frank
Any event that encourages that sort of thing that gets my vote!
Frank
7
News / Re: VATUSA Deputy Training Director
« on: September 04, 2018, 01:13:57 PM »
Well deserved. Looking forward to working with you.
8
News / Re: Seattle has a new Training Administrator!
« on: August 30, 2018, 01:06:46 PM »
Thanks for the good wishes and support. I’m inheriting an easier job because of the hard work and dedication of my predecessors, so I can only hope not to screw things up too badly for as long as I’m allowed to stay!
Best advice received so far: “Just remember, having a staff position at VATSIM ARTCC Management is like making love to a gorilla..... you don’t stop when YOU get tired..... you stop when the GORILLA gets tired......”. I’m still trying to figure that out, but it sounds ominous. Any other advice gratefully received!
Keep those dots apart.
Frank
Best advice received so far: “Just remember, having a staff position at VATSIM ARTCC Management is like making love to a gorilla..... you don’t stop when YOU get tired..... you stop when the GORILLA gets tired......”. I’m still trying to figure that out, but it sounds ominous. Any other advice gratefully received!
Keep those dots apart.
Frank
9
The Control Room Floor / Re: There are two types of controllers...
« on: May 22, 2018, 09:43:55 AM »
Just a suggestion..... some of the choices in the thread seem to be to be on either end of the spectrum (too verbose or strictly 7110.65). That strikes me as a false choice, at least some of the time.
What I often consider is deploying phraseology that may reveal which flavor of pilot I might be dealing with. So.... for the original example Shane gave in his original post, I might try: "DAL2168 Heavy, Minneapolis ground, runway 30L, taxi via A; runway 17 available on request". So far as I know, this is compliant with 7110.65 (or pretty darn near it!).
A pilot in the "less experienced" category, will either ignore it or possibly ask a question (sometimes in chat to avoid being embarrassed by asking) affording a learning opportunity. A "hardcore realism" pilot can take the hint and make the request, which would lead to a 7110.65-compliant exchange about the amended routing etc. which an experienced pilot will be grateful for as well as it increases immersion.
I deploy this strategy in other circumstances as well. For instance, in low traffic situations, I know Portland Departure in real-world often gives direct to the fix on the SID that precedes the transition (e.g. "direct MINNE" for the MINNE5, or "direct CHISM" for the CASCD2). For new VATSIM pilots, giving them this as they climb out can result in confusion, or (worse) accepting the short cut but not actually flying it. So, again, I may say (or ask Tower to say before h/o) "DAL2168 Heavy, runway 16L, cleared for takeoff, [expect direct CHISM, or direct CHISM available on request with Departure]." See what sort of reaction I get and deal accordingly.
I find this strikes a decent balance between the various interests and considerations discussed in this thread. I've received a reasonable amount of feedback both from experienced and new pilots alike that makes me believe this approach is appreciated by both types from a "customer service" perspective as well.
Frank
What I often consider is deploying phraseology that may reveal which flavor of pilot I might be dealing with. So.... for the original example Shane gave in his original post, I might try: "DAL2168 Heavy, Minneapolis ground, runway 30L, taxi via A; runway 17 available on request". So far as I know, this is compliant with 7110.65 (or pretty darn near it!).
A pilot in the "less experienced" category, will either ignore it or possibly ask a question (sometimes in chat to avoid being embarrassed by asking) affording a learning opportunity. A "hardcore realism" pilot can take the hint and make the request, which would lead to a 7110.65-compliant exchange about the amended routing etc. which an experienced pilot will be grateful for as well as it increases immersion.
I deploy this strategy in other circumstances as well. For instance, in low traffic situations, I know Portland Departure in real-world often gives direct to the fix on the SID that precedes the transition (e.g. "direct MINNE" for the MINNE5, or "direct CHISM" for the CASCD2). For new VATSIM pilots, giving them this as they climb out can result in confusion, or (worse) accepting the short cut but not actually flying it. So, again, I may say (or ask Tower to say before h/o) "DAL2168 Heavy, runway 16L, cleared for takeoff, [expect direct CHISM, or direct CHISM available on request with Departure]." See what sort of reaction I get and deal accordingly.
I find this strikes a decent balance between the various interests and considerations discussed in this thread. I've received a reasonable amount of feedback both from experienced and new pilots alike that makes me believe this approach is appreciated by both types from a "customer service" perspective as well.
Frank
10
The Control Room Floor / Re: 7110.65 Change to 3-7-2: Taxi and Ground Movement Operations
« on: March 22, 2018, 04:13:53 PM »
For what it is worth, my home field in St Augustine (KSGJ) has a pair of runways that nearly intersect just where you would exit the ramp to cross and get to a taxiway to the main runway. http://155.178.201.160/d-tpp/1803/00692AD.PDF
I've heard frequently from Ground: "Runway 31, taxi via D4 D B, hold short of the approach end of runway 2" and then "cross runways 2 and 6, [continue taxi]". Consistent with Brad's explanation.
Frank
I've heard frequently from Ground: "Runway 31, taxi via D4 D B, hold short of the approach end of runway 2" and then "cross runways 2 and 6, [continue taxi]". Consistent with Brad's explanation.
Frank
11
The Control Room Floor / Re: 7110.65 Change to 3-7-2: Taxi and Ground Movement Operations
« on: March 18, 2018, 06:30:42 AM »
It would be helpful for VATUSA to give a blanket waiver to allow any ARTCC that wishes to permit controllers to authorise multiple runway crossings (where centrelines are 1300’ or less) to conduct ground operations in that way. IRL, my home field is St Augustine (KSGJ) and the cab controllers complain periodically about having to authorise crossings for the two small runways that cross the main taxiway because they are 25 feet too far apart for the multiple crossing instruction! Now they’ll have to say “cross 6, hold short of 2..... cross 2, continue on Bravo.....”..... MOAR WORDS INDEED!
Perhaps one of the VATUSA folks can sort this so ARTCCs can train accordingly?
Frank
Perhaps one of the VATUSA folks can sort this so ARTCCs can train accordingly?
Frank
12
News / Re: New ZMP ATM
« on: July 04, 2016, 10:06:33 AM »
Congratulations! ZMP couldn't be in better hands.
Frank
Frank
Pages: [1]