Regulations and Policies: Difference between revisions

From New York ARTCC
(Created page with "= Virtual New York ARTCC General Policy = This document outlines the policies and procedures for the Virtual New York ARTCC as of December 2023, Revision F. == Section 1: General Provisions == ; Purpose : The purpose of this document is to provide clear guidelines and operating procedures for members of the Virtual New York ARTCC (ZNY). ; Scope : This document applies to all controllers operating within the ZNY airspace and is designed to ensure safe, efficient, and st...")
 
No edit summary
Line 1: Line 1:
= Virtual New York ARTCC General Policy =
=ARTCC ORGANIZATION=
This document outlines the policies and procedures for the Virtual New York ARTCC as of December 2023, Revision F.


== Section 1: General Provisions ==
==2.1 Internal Communication==
; Purpose
: The purpose of this document is to provide clear guidelines and operating procedures for members of the Virtual New York ARTCC (ZNY).


; Scope
a. All New York ARTCC members must maintain a working e-mail address for communication and keep their New York ARTCC profile updated to comply with the following:
: This document applies to all controllers operating within the ZNY airspace and is designed to ensure safe, efficient, and standardized operations.


== Section 2: Membership and Training Requirements ==
1. The e-mail address provided to the New York ARTCC must be the same as the one used for VATSIM and VATUSA profiles.
=== 2.1 Membership Criteria ===
* Controllers must be members of VATSIM and adhere to the VATSIM Code of Conduct.
* Controllers must complete an initial training session to be assigned to ZNY.


=== 2.2 Training Phases ===
2. We strongly discourage using legacy e-mail addresses such as AOL and Hotmail as these tend to be rejected by our server and flag e-mails from ZNY.
* The training phases are divided as follows:
** Phase 1: Ground Control and Clearance Delivery
** Phase 2: Local Control (Tower)
** Phase 3: TRACON Operations
** Phase 4: Enroute Center Operations


; Promotion Criteria
==2.2 Member Conduct==
: Promotions to higher control positions require successful completion of assessments at each training phase and approval from the Training Department.


== Section 3: Operational Procedures ==
===2.2.1 General===
=== 3.1 Position Relief Briefings ===
* Controllers assuming a position must complete a full position relief briefing with the outgoing controller.
* Briefings should include current traffic flow, pending aircraft, and any temporary restrictions.


=== 3.2 Standard Operating Procedures (SOPs) ===
a. Members and visitors must comply with VATSIM's Code of Conduct at all times while holding a membership with the New York ARTCC. In addition to the Code of Conduct, members must comply with the additional policies below.
* Each facility has specific SOPs detailing the procedures for handling arrivals, departures, and overflights.
* Controllers must familiarize themselves with the SOPs applicable to their assigned sector or facility.


; Position Combining/Decombining
b. The use of the New York ARTCC TeamSpeak Server (located at ts.nyartcc.org), the New York ARTCC Discord Server, and the New York ARTCC Forum is a privilege, not a right. Violation of either the New York ARTCC policies is grounds for disciplinary action.
: Combining or decombining positions must be coordinated with neighboring facilities and approved by a supervisor if available.


== Section 4: Communication Protocols ==
===2.2.2 TeamSpeak & Discord Server===
=== 4.1 Radio Communication ===
* Controllers are expected to maintain clear and concise radio communications.
* Phraseology must be ICAO-compliant and adapted to VATSIM standards where necessary.


=== 4.2 Text Communication ===
a. Use
* Text communication with pilots should mirror voice phraseology as closely as possible.
* All commands and responses in text must be entered in proper format to avoid misunderstandings.


; Frequency Management
1. Any member or visitor controlling the New York ARTCC airspace on the VATSIM Network is strongly encouraged to use TeamSpeak to better coordinate with other controllers. (Recommended)
: Ensure all frequencies are monitored, and changes in frequency are communicated to pilots and neighboring sectors.


== Section 5: Airspace and Sector Assignments ==
2. Hanging out and playing other games while in the New York ARTCC TeamSpeak is permitted, so long as it does not distract those controlling the VATSIM Network. If it does, you need to switch rooms or sign off immediately. (Mandatory)
; ZNY Airspace Overview
: The ZNY airspace covers a large portion of the northeastern United States, including New York, New Jersey, Pennsylvania, and portions of adjacent states.


; Sector Boundaries
3. Duplicate TeamSpeak privilege keys are not authorized. If you want to use TeamSpeak on multiple computers, we strongly recommend you create a MyTeamSpeak account and synchronize your TeamSpeak identity to the cloud. The account is free and will save you a lot of time. If you do not wish to do so, you need to copy the identity under "settings" and import it to the new computer. (Mandatory)
: Detailed maps and descriptions of sector boundaries are provided in Attachment 1. Controllers must be aware of these boundaries and coordinate with adjacent sectors when necessary.


== Section 6: Traffic Management Initiatives ==
b. Manners
=== 6.1 Flow Control ===
* Implement flow control measures when traffic density warrants, including metering and miles-in-trail restrictions.
* Coordination with adjacent ARTCCs is required for cross-border traffic management.


=== 6.2 Ground Delay Programs ===
1. All users shall always be courteous. No rude behavior, rude comments, or vulgar language will be tolerated if any member in the channel is offended by it. (Mandatory)
* When severe weather or congestion affects departures, ground delays may be issued. Controllers must notify affected aircraft and provide updated departure times when available.


== Section 7: Event Management ==
2. Harassment or abuse of any kind will not be tolerated. (Mandatory)
* During special events, ZNY may implement additional procedures to manage increased traffic volumes.
* Controllers assigned to event positions must attend the pre-event briefing and follow the event-specific SOPs.


== Section 8: Safety and Compliance ==
3. First offenses will be treated as a warning. Subsequent offenses will result in being kicked from the server and possible revocation of TeamSpeak privileges.
* Controllers are responsible for maintaining a high standard of safety and compliance with VATSIM and ZNY policies.
* Violations of procedures or unprofessional behavior may result in disciplinary action.


= Attachments and References =
c. Nicknames
* Attachment 1: ZNY Airspace Sector Boundaries
* Attachment 2: Training Phase Details
* Attachment 3: SOP Reference Guide
* Attachment 4: Communication Phraseology Reference


== Section 9: Controller Duties and Responsibilities ==
1. All members and visitors must use their first and last names as well as their operating initials on TeamSpeak and Discord. (Mandatory)
=== 9.1 General Responsibilities ===
* All controllers are responsible for maintaining situational awareness within their assigned airspace.
* Controllers should ensure all communications and interactions with pilots are professional and efficient.
* Adherence to ZNY policies and the VATSIM Code of Conduct is mandatory.


=== 9.2 Specific Position Responsibilities ===
2. Example: Andrew Heath (AJ)
* **Clearance Delivery (CD):**
** Issue IFR clearances to departing aircraft.
** Coordinate with Ground Control for pushback and taxi clearances.
* **Ground Control (GC):**
** Manage all ground movements within the airport, including taxiways, holding points, and intersections.
** Coordinate with Clearance Delivery for IFR releases and with Local Control for runway assignments.
* **Local Control (LC):**
** Provide takeoff and landing clearances.
** Monitor runway occupancy and coordinate closely with Ground Control to maintain safe runway operations.
* **Approach Control (TRACON):**
** Sequence arrivals and departures for efficient spacing and safe integration into enroute airspace.
** Coordinate with Tower and Center controllers for handoffs and altitude assignments.
* **Enroute Control (Center):**
** Manage aircraft within ZNY's enroute airspace, including climb, descent, and route adjustments.
** Coordinate with adjacent ARTCCs for boundary handoffs.


== Section 10: Weather Procedures ==
3. Changing nicknames, claiming certification you have not earned, or using aliases is not allowed. (Mandatory)
=== 10.1 Weather Updates ===
* Controllers are responsible for monitoring METARs and TAFs for their areas of operation.
* Significant weather changes (e.g., thunderstorms, low visibility) should be communicated to affected pilots and neighboring sectors.


=== 10.2 Severe Weather Avoidance ===
4. All members are limited to a maximum of 4 visible TeamSpeak tags unless otherwise allowed by the ATM or DATM.
* When weather conditions impact routes or approaches, controllers should issue vectors and altitudes to help pilots avoid severe weather.
* Traffic flow may be adjusted as necessary to accommodate weather diversions.


; Low Visibility Operations
d. Discussion Topics
: During low visibility conditions, ensure pilots have appropriate clearance and provide additional separation if necessary.


== Section 11: Incident Reporting ==
1. Politics, religion, and other potentially confrontational topics are permitted. Still, if any member or visitor asks you to change topics, you must comply or move your discussion to a different channel. (Mandatory)
* All incidents involving deviations from standard procedures or pilot complaints should be documented.
===1.3.2 Airspace Diagram===
* Controllers are expected to report incidents to ZNY leadership for further review and resolution.


=== 11.1 Incident Review Process ===
[[File:ZNY_Airspace_Diagram.png|center|frameless|700px]]
* Incidents are reviewed by the ZNY management team.
* Controllers involved may be required to provide a statement or attend a review session.


; Disciplinary Actions
=2. GENERAL POLICIES=
: Based on the severity of the incident, disciplinary actions may range from additional training to suspension of controlling privileges.


== Section 12: Training and Certification Standards ==
==2.1 Internal Communication==
=== 12.1 Initial Training Requirements ===
* New controllers must complete an introductory training session covering basic airspace knowledge, phraseology, and procedures.
* Successful completion of initial training qualifies controllers to operate Ground and Clearance Delivery positions.


=== 12.2 Certification Levels ===
a. All New York ARTCC members must maintain a working e-mail address for communication and keep their New York ARTCC profile updated to comply with the following:
* **Level 1 - Ground and Clearance Delivery:** Authorized to control Ground and Clearance Delivery positions.
* **Level 2 - Tower Control:** Authorized to control Ground, Clearance Delivery, and Local Control positions.
* **Level 3 - TRACON Control:** Authorized to control Ground, Clearance Delivery, Local, and Approach Control positions.
* **Level 4 - Center Control:** Authorized to control all ZNY positions, including Center.


; Recurrent Training
1. The e-mail address provided to the New York ARTCC must be the same as the one used for VATSIM and VATUSA profiles.
: Controllers are required to participate in recurrent training sessions at least annually to maintain proficiency and stay updated on procedural changes.


== Section 13: Technical Requirements ==
2. We strongly discourage using legacy e-mail addresses such as AOL and Hotmail as these tend to be rejected by our server and flag e-mails from ZNY.
=== 13.1 Software and Equipment ===
* Controllers must use approved software, such as EuroScope or VRC, configured for ZNY airspace.
* A stable internet connection and a high-quality headset are recommended for effective communication.


=== 13.2 System Updates ===
==2.2 Member Conduct==
* Controllers are responsible for keeping their software up-to-date to ensure compatibility with VATSIM and ZNY data files.
* Notices regarding required updates will be distributed by the ZNY technical team.


; Controller Information File (CIF)
===2.2.1 General===
: The CIF contains all necessary information on frequencies, sector files, and ZNY-specific configurations. Controllers are required to review and use the CIF as part of their setup.


== Section 14: Leave and Absence Policies ==
a. Members and visitors must comply with VATSIM's Code of Conduct at all times while holding a membership with the New York ARTCC. In addition to the Code of Conduct, members must comply with the additional policies below.
* Controllers must notify ZNY leadership if they plan to be inactive for an extended period.
* Controllers on approved leave retain their position and seniority but may require a requalification session upon return.


=== 14.1 Inactivity Policy ===
b. The use of the New York ARTCC TeamSpeak Server (located at ts.nyartcc.org), the New York ARTCC Discord Server, and the New York ARTCC Forum is a privilege, not a right. Violation of either the New York ARTCC policies is grounds for disciplinary action.
* Controllers who are inactive for more than 90 days without notification may lose their assigned position and certification level.
* Controllers returning from inactivity will undergo a proficiency check to assess current knowledge and skills.


== Section 15: Event Participation ==
===2.2.2 TeamSpeak & Discord Server===
* Controllers are encouraged to participate in official ZNY events to gain experience and support the network's community.
* Event-specific briefings are mandatory for controllers assigned to staff event positions.


=== 15.1 Event Scheduling and Assignment ===
a. Use
* ZNY events are scheduled regularly, with sign-up sheets available for controllers to volunteer for specific positions.
* Assignments are based on experience, certification level, and training completion.


; Priority Assignments
1. Any member or visitor controlling the New York ARTCC airspace on the VATSIM Network is strongly encouraged to use TeamSpeak to better coordinate with other controllers. (Recommended)
: Certified controllers with higher experience levels may be given priority for complex positions during events. All assignments are made at the discretion of ZNY event coordinators.


= Attachments =
2. Hanging out and playing other games while in the New York ARTCC TeamSpeak is permitted, so long as it does not distract those controlling the VATSIM Network. If it does, you need to switch rooms or sign off immediately. (Mandatory)
== Attachment 1: ZNY Airspace Sector Boundaries ==
* Detailed maps and boundary descriptions for each ZNY sector, including TRACON and Center boundaries.


== Attachment 2: Training Phase Details ==
3. Duplicate TeamSpeak privilege keys are not authorized. If you want to use TeamSpeak on multiple computers, we strongly recommend you create a MyTeamSpeak account and synchronize your TeamSpeak identity to the cloud. The account is free and will save you a lot of time. If you do not wish to do so, you need to copy the identity under "settings" and import it to the new computer. (Mandatory)
* Overview of each training phase, covering the skills and knowledge required to progress through certification levels.


== Attachment 3: SOP Reference Guide ==
b. Manners
* A comprehensive guide to Standard Operating Procedures for each ZNY facility and position.


== Attachment 4: Communication Phraseology Reference ==
1. All users shall always be courteous. No rude behavior, rude comments, or vulgar language will be tolerated if any member in the channel is offended by it. (Mandatory)
* Standard phraseology examples for clearance delivery, ground, tower, approach, and enroute positions.
* Detailed guidance on handling specific scenarios, such as emergency situations and weather diversions.


== Document Revision History ==
2. Harassment or abuse of any kind will not be tolerated. (Mandatory)
* **Revision F - December 2023:** Comprehensive update to membership criteria, operational procedures, event participation, and controller responsibilities.


© Copyright 2023 Virtual New York ARTCC (ZNY). All Rights Reserved.
3. First offenses will be treated as a warning. Subsequent offenses will result in being kicked from the server and possible revocation of TeamSpeak privileges.
 
c. Nicknames
 
1. All members and visitors must use their first and last names as well as their operating initials on TeamSpeak and Discord. (Mandatory)
 
2. Example: Andrew Heath (AJ)
 
3. Changing nicknames, claiming certification you have not earned, or using aliases is not allowed. (Mandatory)
 
4. All members are limited to a maximum of 4 visible TeamSpeak tags unless otherwise allowed by the ATM or DATM.
 
d. Discussion Topics
 
1. Politics, religion, and other potentially confrontational topics are permitted. Still, if any member or visitor asks you to change topics, you must comply or move your discussion to a different channel. (Mandatory)
 
==2.3 Activity and Leave of Absence Policies==
 
===2.3.1 Home Controller Activity Requirements===
 
a. Home controllers are required to meet the following minimum activity standards:
 
1. All controllers holding an S1 rating and above are required to log at least two (2) hours of controlling time on approved ZNY positions per month.
 
2. Controllers who fail to meet the activity requirement for a given month may have their ZNY TeamSpeak and Discord privileges suspended and may be subject to removal from ZNY after a period of inactivity.
 
===2.3.2 Visiting Controller Activity Requirements===
 
a. Visiting controllers are required to meet the following minimum activity standards:
 
1. Visiting controllers holding an S1 rating and above must log at least two (2) hours of controlling time on approved ZNY positions per month.
 
2. Failure to meet the activity requirement may result in a loss of ZNY TeamSpeak and Discord privileges and possible removal from ZNY as a visiting controller.
 
===2.3.3 Leave of Absence (LOA) Policy===
 
a. Any controller needing to take a break from controlling due to real-life commitments may request a Leave of Absence (LOA).
 
b. LOA requests should be submitted via the ZNY website with the following guidelines:
 
1. An LOA request can be granted for up to 90 days. Extensions beyond this period will require additional justification.
 
2. Controllers on LOA are exempt from meeting monthly activity requirements.
 
c. Controllers who remain on LOA status for more than 180 consecutive days without a valid reason may be removed from ZNY.
 
d. Controllers returning from LOA should notify the Training Department to facilitate a re-assessment if necessary.

Revision as of 05:45, 8 November 2024

ARTCC ORGANIZATION

2.1 Internal Communication

a. All New York ARTCC members must maintain a working e-mail address for communication and keep their New York ARTCC profile updated to comply with the following:

1. The e-mail address provided to the New York ARTCC must be the same as the one used for VATSIM and VATUSA profiles.

2. We strongly discourage using legacy e-mail addresses such as AOL and Hotmail as these tend to be rejected by our server and flag e-mails from ZNY.

2.2 Member Conduct

2.2.1 General

a. Members and visitors must comply with VATSIM's Code of Conduct at all times while holding a membership with the New York ARTCC. In addition to the Code of Conduct, members must comply with the additional policies below.

b. The use of the New York ARTCC TeamSpeak Server (located at ts.nyartcc.org), the New York ARTCC Discord Server, and the New York ARTCC Forum is a privilege, not a right. Violation of either the New York ARTCC policies is grounds for disciplinary action.

2.2.2 TeamSpeak & Discord Server

a. Use

1. Any member or visitor controlling the New York ARTCC airspace on the VATSIM Network is strongly encouraged to use TeamSpeak to better coordinate with other controllers. (Recommended)

2. Hanging out and playing other games while in the New York ARTCC TeamSpeak is permitted, so long as it does not distract those controlling the VATSIM Network. If it does, you need to switch rooms or sign off immediately. (Mandatory)

3. Duplicate TeamSpeak privilege keys are not authorized. If you want to use TeamSpeak on multiple computers, we strongly recommend you create a MyTeamSpeak account and synchronize your TeamSpeak identity to the cloud. The account is free and will save you a lot of time. If you do not wish to do so, you need to copy the identity under "settings" and import it to the new computer. (Mandatory)

b. Manners

1. All users shall always be courteous. No rude behavior, rude comments, or vulgar language will be tolerated if any member in the channel is offended by it. (Mandatory)

2. Harassment or abuse of any kind will not be tolerated. (Mandatory)

3. First offenses will be treated as a warning. Subsequent offenses will result in being kicked from the server and possible revocation of TeamSpeak privileges.

c. Nicknames

1. All members and visitors must use their first and last names as well as their operating initials on TeamSpeak and Discord. (Mandatory)

2. Example: Andrew Heath (AJ)

3. Changing nicknames, claiming certification you have not earned, or using aliases is not allowed. (Mandatory)

4. All members are limited to a maximum of 4 visible TeamSpeak tags unless otherwise allowed by the ATM or DATM.

d. Discussion Topics

1. Politics, religion, and other potentially confrontational topics are permitted. Still, if any member or visitor asks you to change topics, you must comply or move your discussion to a different channel. (Mandatory)

1.3.2 Airspace Diagram

File:ZNY Airspace Diagram.png

2. GENERAL POLICIES

2.1 Internal Communication

a. All New York ARTCC members must maintain a working e-mail address for communication and keep their New York ARTCC profile updated to comply with the following:

1. The e-mail address provided to the New York ARTCC must be the same as the one used for VATSIM and VATUSA profiles.

2. We strongly discourage using legacy e-mail addresses such as AOL and Hotmail as these tend to be rejected by our server and flag e-mails from ZNY.

2.2 Member Conduct

2.2.1 General

a. Members and visitors must comply with VATSIM's Code of Conduct at all times while holding a membership with the New York ARTCC. In addition to the Code of Conduct, members must comply with the additional policies below.

b. The use of the New York ARTCC TeamSpeak Server (located at ts.nyartcc.org), the New York ARTCC Discord Server, and the New York ARTCC Forum is a privilege, not a right. Violation of either the New York ARTCC policies is grounds for disciplinary action.

2.2.2 TeamSpeak & Discord Server

a. Use

1. Any member or visitor controlling the New York ARTCC airspace on the VATSIM Network is strongly encouraged to use TeamSpeak to better coordinate with other controllers. (Recommended)

2. Hanging out and playing other games while in the New York ARTCC TeamSpeak is permitted, so long as it does not distract those controlling the VATSIM Network. If it does, you need to switch rooms or sign off immediately. (Mandatory)

3. Duplicate TeamSpeak privilege keys are not authorized. If you want to use TeamSpeak on multiple computers, we strongly recommend you create a MyTeamSpeak account and synchronize your TeamSpeak identity to the cloud. The account is free and will save you a lot of time. If you do not wish to do so, you need to copy the identity under "settings" and import it to the new computer. (Mandatory)

b. Manners

1. All users shall always be courteous. No rude behavior, rude comments, or vulgar language will be tolerated if any member in the channel is offended by it. (Mandatory)

2. Harassment or abuse of any kind will not be tolerated. (Mandatory)

3. First offenses will be treated as a warning. Subsequent offenses will result in being kicked from the server and possible revocation of TeamSpeak privileges.

c. Nicknames

1. All members and visitors must use their first and last names as well as their operating initials on TeamSpeak and Discord. (Mandatory)

2. Example: Andrew Heath (AJ)

3. Changing nicknames, claiming certification you have not earned, or using aliases is not allowed. (Mandatory)

4. All members are limited to a maximum of 4 visible TeamSpeak tags unless otherwise allowed by the ATM or DATM.

d. Discussion Topics

1. Politics, religion, and other potentially confrontational topics are permitted. Still, if any member or visitor asks you to change topics, you must comply or move your discussion to a different channel. (Mandatory)

2.3 Activity and Leave of Absence Policies

2.3.1 Home Controller Activity Requirements

a. Home controllers are required to meet the following minimum activity standards:

1. All controllers holding an S1 rating and above are required to log at least two (2) hours of controlling time on approved ZNY positions per month.

2. Controllers who fail to meet the activity requirement for a given month may have their ZNY TeamSpeak and Discord privileges suspended and may be subject to removal from ZNY after a period of inactivity.

2.3.2 Visiting Controller Activity Requirements

a. Visiting controllers are required to meet the following minimum activity standards:

1. Visiting controllers holding an S1 rating and above must log at least two (2) hours of controlling time on approved ZNY positions per month.

2. Failure to meet the activity requirement may result in a loss of ZNY TeamSpeak and Discord privileges and possible removal from ZNY as a visiting controller.

2.3.3 Leave of Absence (LOA) Policy

a. Any controller needing to take a break from controlling due to real-life commitments may request a Leave of Absence (LOA).

b. LOA requests should be submitted via the ZNY website with the following guidelines:

1. An LOA request can be granted for up to 90 days. Extensions beyond this period will require additional justification.

2. Controllers on LOA are exempt from meeting monthly activity requirements.

c. Controllers who remain on LOA status for more than 180 consecutive days without a valid reason may be removed from ZNY.

d. Controllers returning from LOA should notify the Training Department to facilitate a re-assessment if necessary.