This rule is the most restrictive and conservative method of IFR separation by a radar facility overhead a Class D facility.

That being said, let this serve as a reminder of how IFR operations work at Class D airports:

Class D control towers can separate IFR operations within their airspace by visual separation as long as standard IFR separation exists prior to and after the application of visual separation.

However, in real life Letters of Agreement are sometimes much more restrictive than this based on what type of facility overlies the airport and what radar equipment is in use by them. Because of this, the rest is a review of the most restrictive/conservative method of IFR separation in the Class D tower environment.

Class D towers must report to the radar facility overhead (i.e. DEN_APP when working APA_TWR) when an IFR arrival lands.

   - Ex. "Denver Approach, Centennial Tower." "Denver Approach." "N123 has landed." "ZY" "MM"

This tells the radar facility that they may clear the next IFR arrival for approach into the airport, or issue a departure release to an IFR departure who is waiting.

That is also why we must obtain an IFR release for all IFR departures. Ex. "Denver Approach, Centennial Tower." "Denver Approach." "Request release N123 to Grand Junction." (Include the runway number if more than one is in use at your airport as advised to the radar facility and within the ATIS). "N123 is released." "JW" "DM" (The release may include a heading to fly, or an amended initial altitude. If not, it is the tower's discretion to assign a heading if a pilot nav SID is not being flown).

If the radar facility has an IFR arrival inbound that is established on an Instrument Approach Procedure (IAP) they may issue "N123, hold for release" or "N123, expect departure clearance 0130 Zulu". It is the radar facility's job to call the tower back to issue the release when able; generally when the tower calls to advise the previous IFR arrival has landed.

Tower provided visual separation:

   - If the radar facility sees fit, based on the weather and traffic situation, they can delegate responsibility for utilizing visual separation between two specific IFR operations to the tower. Ex. "Visual separation approved between N123 and N456, N456 released at your discretion."

Voila! Advise if you have questions.

ZY

Hello members,

Firstly, this is an honest discussion. Please be honest and reasonable in your replies, I welcome all opinions that are posted in good faith.

Recently, being a visitor at several ARTCCs and frequenter of each ARTCC's Teamspeak servers, I've noticed unfriendly "discussion" among members and staff/senior staff regarding other ARTCCs and VATSIM members.

Behavior and conversations I've observed have ranged from friendly and acceptable banter and discussion (of which I have no concern for and contribute to members feeling welcome), to outrightly unacceptable and unfriendly talk about other ARTCCs and VATSIM members. It's disappointing to me that a network where people are supposed to be able to enjoy learning about aviation in an acceptable environment are subject to this kind of degrading speech and atmosphere in Teamspeak channels. When senior staff are cussing out other ARTCC staff members, and talk of "coup de'tats" of other ARTCCs come up I start to get worried about our priorities and principles as VATSIM members, but that's another discussion.

Teamspeak servers are, in my understanding, owned and operated/monitored by the ARTCCs themselves, but I've noticed a VATUSA-wide ordeal here that ARTCCs alone will have difficulty combating, especially because senior staff members are contributing to this fiasco.  

People leave ARTCCs, or VATSIM as a whole because of this kind of behavior; let's keep each other accountable.

Likely some people don't see this the way I do of course. I understand that because ARTCCs manage their Teamspeak servers they can choose to allow anything they see fit to happen on them, but I am not interested in the faux-legalities of the issue, I'm interested in discussing the moral obligation I believe we have as VATSIM members to, "at all times, be courteous and respectful to one another." If you participate in these kind of discussions, please be reminded that you are likely driving people away from VATSIM by making it appear crude and unwelcoming.

Please discuss.

Cheers
ZY

P.S. Let's discuss staff positions and the implications associated with your behavior provided you become a staff member as well.