Aeronautical Information

Charts and Aeronautical Information

Rules And Regulations - Israel Division (VATIL)

The rules detailed hereinafter are an addition to VATSIM regulations and code of conduct, which stays in effect (read VATSIM CODE OF CONDUCT) . The HEBREW version is available here!

  1. Acceptable callsigns
    1. VATIL staff members are allowed to use VATIL# call sign (# will be replaced by the staff position number as published). No other member will use a call sign of this sort.

    2. Controllers connecting to VATSIM network will use one of the call signs detailed in the call signs appendix, and:

      1. A mentoring or trainer ATC will add a “_M_” tag to his respective call sign.
      2. A non-staff member controller connecting for observation purposes only will ALWAYS use “_obs” suffix.
      3. An ATC will not connect using a valid ATC call sign unless he intends to control in this ATC position.
      4. The use of “FSS” suffix is strictly forbidden for all members.
    3. Pilots will use normal aviation call signs, preferably Israeli aviation call signs or registry numbers (4X + 3 letters – 4X-AIT for example).
  2. Communication
    1. Text is the primary communication method in VATSIM network. ATC or pilot refusing to use text will be suspended in accordance to VATSIM rules. It is recommended however to use voice communication when able.

    2. All communication will be handled in English; in case all pilots on channel are Hebrew speakers, the use of Hebrew is acceptable. All pilots and controllers are obliged to use English again whenever a foreign pilot joins or about to join the channel.

    3. On Hagav and Pluto channels communication will be in Hebrew; however should a non-Hebrew speaker will join the channel, all users should respect him and use communicate in English.

    4. Use of the Guard channel (121.5) is prohibited according to VATSIM policy – controllers are requested to refrain from using this channel.

  3. Emergencies
    1. Declaring an emergency under traffic is not welcomed, and pilots are requested to refrain from doing so especially during declared events.

    2. ATC may deny an emergency, particularly to prevent delays to other pilots or during heavy traffic periods. If an emergency is denied, the pilot is expected to resume normal flight or immediately log off the network.

    3. Simulating a hijack situation or even squawking the hijack transponder code is strictly prohibited in VATSIM. A pilot caught during such conduct is subject to disciplinary actions in accordance to VATSIM rules and regulations.

  4. Military Operation
    • According to VATSIM regulations, military operations shall be conducted only under VSOA guidelines.
    • Operation of military aircraft is allowed between any two airports according to standard flight rules. For clarification, any aircraft interception, and formation flight of military type aircraft, may suggest military training and should be conducted under VSOA guidelines.
    • Standard (non-military) operations of Israeli tactical aircraft shall avoid all adjoining FIRs and Gaza strip, except Nicosia.
    • VATSIM is a non-political network. All operations and exchanges shall maintain courteous and non-offensive nature, avoiding unfriendly gestures, call signs and reference to historical conflicts.
    • VSOA - approved organizations shall operate within the VATIL airspace according to the following guidelines:

    1. Aggressive flight and attack of targets and areas outside established firing ranges is prohibited.

    2. IFR Military traffic shall use the ATS route system and established military wing/ airbase ATC procedures.

    3. VFR Military traffic shall use the military Jet Route System and/or CVFR Route System, as applicable to aircraft category, and established military wing/airbase ATC procedures.

    4. Military flight training will be conducted in the established Military Operating Areas (MOAs), and Special Use Areas (SUAs) for range practice.

    5. ATS route traffic traversing MOAs has priority over military operations. When required, ongoing military operations shall upon ATC requirement, clear the subject routes within 2 minute notice.

    6. Military traffic has priority over use of MOAs including traversing ATS routes marked "BY ATC". Civil traffic clearance along ATS Route System segments marked "BY ATC" shall require prior ATC coordination.

    7. Cross country navigation outside MOAs and route systems, require prior approval.

  5. Controllers training
    1. The Divisional training director (VATIL3) will set the training regulations in VATIL, and will publish his intentions from time to time. His authority in this field is full and final.

    2. VATIL training department will prepare theoretical exams, which along with CPT’s will be mandatory for every ATC upgrade.

    3. All CPT will be held under the supervision of an Instructor (INS or INS+) whenever possible.

    4. An ATC holding a STU or STU+ rank will not man a CTR position.
    5. An ATC holding a STU rank will not man an APP position.
  6. Visiting controllers
    1. Visiting controllers (i.e. – non-VATIL members) wishing to control in the Israeli airspace will coordinate the details with VATIL3 prior to their operation.

    2. A visiting controller holding STU rank will man only GND or DEL positions.

    3. A visiting controller holding STU+ rank will man only TWR position or below.

    4. A visiting controller holding CTR rank will man only APP position or below.
  7. Conflict resolution

    1. To the extent possible, VATIL will not get involved in users’ conflicts or disputes of personal nature. However, when necessary, a complaint should be filed to the divisional conflict resolutions manger (DCRM).

    2. The DCRM is authorized to get involved in the conflict, suggest an action, use disciplinary actions, or any other act needed to resolve the situation in accordance to VATSIM rules.

 

All Rights Reserved To VATSIM Israel 2006-2007 ©