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.


Messages - Brian Clark

Pages: [1]
1
The Control Room Floor / Houston Holding Points
« on: August 06, 2010, 04:00:08 AM »
I'm a bit of a noobie here but that doesn't stop me from having a slight bit of an opinion (typical right?)

As much as realism, study depth, etc. are good things, VATSIM ATC (like real ATC) is ultimately a practical service with a purpose. Real ATC concluded that HPs were a good idea because they evaluated what their requirements and resources were and synthesized.

REAL ATC
Resources: Well-trained controllers, well-trained pilots, accessible dissemination methods, ramp controllers, cooperative personnel
Requirements: High traffic volume

VATSIM ATC
Resources: Amateur* controllers, amateur pilots, limited dissemination methods, no ramp controllers, sometimes non-cooperative personnel
Requirements: Low traffic volume

*No offense, I know VATSIM ATC training approaches the rigor of real world ATC training in most ways.

If you put the real FAA, airlines, airports, etc. into the "VATSIM world" in terms of resources and requirements, they would not come to the same conclusions that they have in the real world. The cost-benefit ratio is out of whack. The fundamentals of ground control probably best serve the situation while remaining emotionally satisfying to VATSIM's mission.

The best way to implement HPs (I think, at least initially) is to make agreements with select VAs who promise to ensure their pilots are HP certified. Only "Class 1" VAs, and their  pilots, as shown in the flight plan comments, would be able to be given such hold points. Similarly only select airports should require higher-than-standard knowledge from their controllers for HP ops. OAK_GND might not be a HP ops position while SFO_GND is.

2
The Control Room Floor / "Position And Hold" Change Expected Soon
« on: August 05, 2010, 01:11:40 AM »
The thing about radio phraseology is that it's very keyword (proword) based. Prowords best when you have a small dictionary and very set reactions associated with each proword.

"Hold" as in "Hold short" "land and hold short" "holding pattern" are already well-established concepts that use a very consistent definition. "Position and hold" is likewise consistent with the other uses of the word "hold." It would be unnecessarily expanding the dictionary to describe a very "hold-like" concept to use "wait" as the keyword. Unless it is their express intent to differentiate the "line up and wait" command from the "hold short runway X-Y" command, as in, there has been a problem with those being mixed up, then it is a poor idea to dilute the proword dictionary.

If you're really going to go through all the effort to change something in aviation, do it because it's a good idea in its own right, not because "those guys do it over there."

Pages: [1]