View Single Post
  #25  
Old May 8th 04, 10:02 PM
Steven P. McNicoll
external usenet poster
 
Posts: n/a
Default


wrote in message
...

Almost... Even *with* conflicting IFR traffic if you are not in
their airspace, VFR traffic is under no obligation to accept being
moved. No obligation to even be in communication with them at
all. If there's a conlict, the controller's last resort is to move the
IFR traffic and rely on "see and avoid" in VMC.


No, not "almost", what I wrote is exactly correct. The outer area
associated with Class C airspace is nonregulatory airspace surrounding
designated Class C airspace airports wherein ATC provides separation and
sequencing for all IFR and participating VFR aircraft. The outer area
extends outward 20 miles from the primary Class C airspace airport and
extends from the lower limits of radar/radio coverage up to the ceiling of
the approach control's delegated airspace, excluding the Class C airspace
proper. The same service is provided in the outer area as in the charted
Class C airspace, the only difference is participation is voluntary for VFR
aircraft in the outer area. If you elected to contact approach you
volunteered to participate. And, yes, ATC can move VFR traffic to provide
required separation from IFR traffic. If you're not in contact with ATC,
then you've obviously not volunteered to participate and no separation
mimima applies, so ATC will not move the IFR aircraft to resolve a conflict,
just issue a traffic advisory.