Controlling Techniques?

[F18bkr]

What are your controlling techniques for certain airports? What's your
style? How often do you use waypoints as opposed to directions?

[Roy Ryland]

With this game, a lot of times when a fix (NAVAID) is directly opposite the airports duty runway,  I will clear the aircraft to that fix.  That way he'll be lining up with the runway heading and then just clear him to land.   RRR         -------Original Message-------

--   You received this message because you are subscribed to the Google Groups "ATC-SIM" group. To post to this group, send email to atc...@googlegroups.com. To unsubscribe from this group, send email to atc-sim+u...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/atc-sim?hl=en.       ____________________________________________________________     No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.717 / Virus Database: 270.14.113/2573 - Release Date: 12/18/09 01:35:00

[Evan]

I mostly play at Newark/KEWR, and try to stick to real procedures as
close as is possible in this sim. I keep arrivals anywhere from 5-7k
feet and try and route them all up the left of the screen (when
landing south on 22L) I generally give them a general heading to get
to the west side of the airspace, and then usually give them a fix to
the MM NDB when they're pretty parallel to the runway, and then to
PATRN -> TEB, as the real approach roughly goes. Seems to work pretty
well, the only thing I wish we had was designated departure/arrival
runways (praying for it one day! =P)!! Departures generally fly runway
heading until I can figure out where they're headed, and when they
won't conflict, but usually departures to the north will get a pretty
quick right turn to 040, and be far enough away from arrivals to their
left.

[ion_de_la_raion]

In real life I use direct to a waypoint which is 11 miles from touch
down.
If I have more than 5 aircrafts on approach then speed limit,
vectoring and descend steps is the way I do it.

But here I don't have the waypoints to do that so I have to vector
them.

For departures: FL100 direct to exit point
The most simple and efficient spacing method for departing on paralel
runways is for the first aircraft to turn left/right and the next one
to remain on rwy heading until 3000ft then direct to fix

[Tinto]

In an effort to keep violations down, I play by a set of self made
restrictions (but often reflecting actual procedure)
I always use vectors for arrivals - only exception would be directing
to a fix for arrival holding (almost never). They are all set to
handoff altitude + 1 or above as soon as they are on screen (ATL =
6000 or above). Departures are always cleared to minimum handoff
altitude and rarely instructed to climb beyond (ATL = 5000). This
way, there is always vertical separation until it's time to descend
for approach. Departures are given direct clearance to handoff
waypoint, unless the waypoint is too close, in which case i use a dog
leg or expedite climb. I spend about 20% of time working departures
(mainly just clearance) and focus on arrivals.

I figured out minimum approach separation for any combination of ac
type and added a bit - and always aim for this approach spacing. Also
found minimum separations for departures (already holding) for combos,
with clearance based on altitude of the preceeding. Eg, with two
737s, the follower can takeoff when the preceeding is at field+400ft
to maintain vertical separation after takeoff, but i use field+500ft,
since this also assures lateral separation. When ATR42 following 737:
field+1000ft, when 737 following ATR42: field+2500ft etc.

All arrivals set to 200kts when established on localiser, unless need
to adjust for spacing.