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 standardized operations.

Section 2: Membership and Training Requirements

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

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: Promotions to higher control positions require successful completion of assessments at each training phase and approval from the Training Department.

Section 3: Operational Procedures

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)

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: Combining or decombining positions must be coordinated with neighboring facilities and approved by a supervisor if available.

Section 4: Communication Protocols

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

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: Ensure all frequencies are monitored, and changes in frequency are communicated to pilots and neighboring sectors.

Section 5: Airspace and Sector Assignments

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: 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

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

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

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

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

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

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

**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

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

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: During low visibility conditions, ensure pilots have appropriate clearance and provide additional separation if necessary.

Section 11: Incident Reporting

All incidents involving deviations from standard procedures or pilot complaints should be documented.
Controllers are expected to report incidents to ZNY leadership for further review and resolution.

11.1 Incident Review Process

Incidents are reviewed by the ZNY management team.
Controllers involved may be required to provide a statement or attend a review session.

Disciplinary Actions: 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

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

**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: 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

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

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): 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

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

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

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

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: 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

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

Overview of each training phase, covering the skills and knowledge required to progress through certification levels.

Attachment 3: SOP Reference Guide

A comprehensive guide to Standard Operating Procedures for each ZNY facility and position.

Attachment 4: Communication Phraseology Reference

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

**Revision F - December 2023:** Comprehensive update to membership criteria, operational procedures, event participation, and controller responsibilities.