VATSIM Code of Conduct Quiz

VATSIM Code of Conduct Companion Document

• This document clarifies the rules outlined in the VATSIM Code of Conduct.

• It's an interpretation, not the governing document itself.

• Information is intended for flight simulation purposes only.

General Rules of Conduct

• A1(a): Account holders must be courteous and respectful. Foul language and disruptive behavior are prohibited.

• A1(b): Account holders must provide truthful and unaltered information. Deliberate false information is a violation and may result in disciplinary action.

• A2(a): Registration is required to use VATSIM, only registered account holders can fly or control.

• A2(b): Only registered account holders can access VATSIM services, except for guests who may use the public website or mapping software.

• A3: Each account holder is responsible for their account and can't let anyone else use it.

• A4(a): Registration requires using the account holder's real full name; nicknames, callsigns, and abbreviations aren't permitted.

• A4(b): Account holders connect with one of the listed name conventions:

  • Real registered name (full name)
  • Shortened given name, followed by surname
  • Real given name
  • Shortened given name
  • VATSIM certificate ID number

• A4(c): New users can append "(new)" to their names.

• A5: A valid email address is required and must be kept up-to-date.

• A6: Each account holder can only have one VATSIM account.

• A7: Use only software approved by VATSIM to connect.

• A8: An account holder can only have one connection at a time (but exceptions do exist)

• A9: Account holders must not leave their account unattended for extended periods while connected to the network.

• A10: Patience and tolerance are expected towards other users. Mistakes and learning are part of the process.

• A11: Account Holders cannot harass, stalk or threaten other users on VATSIM resources

• A12: Avoid using callsigns that imply a status that you don't have. Incorrectly representing yourself as staff is not permitted.

• A13: Connections are limited to observers, pilots, or controllers. Only authorized military, paramilitary, or civilian government agency operations are allowed.

• A14: Voice communication is preferred but text is acceptable. Only unaltered speech is permitted.

• A15: Respond to communications from VATSIM administrators and supervisors appropriately.

• A16: Text and voice communications are for flight operation use only.

• A17: Simulation of disasters is not permitted. Certain callsigns are prohibited.

• A18: Streaming of your sessions is permitted if guidelines are followed.

• A19: When streaming, follow all other Code of Conduct sections.

• A20: (This one has been split and merged) Pilots must follow correct procedure in connecting to and departing from airports and taxiways; connecting to a runway or taxiway isn't permitted.

• A21: Pilots and controllers must follow correct procedures. Pilots must monitor their flights at all times and be prepared for emergency situations.

Pilot Conduct

• B1: Connecting to VATSIM on taxiways or runways is prohibited.

• B2: Pausing in flight is generally not permitted.

• B3: Pilots need to maintain appropriate contact with ATC and be prepared for their route instructions.

• B4: Use transponder when required. Incorrect use/lack of transponder is not tolerated or acceptable.

• B5: Monitoring appropriate frequencies for advisory announcements; ensure you are aware of other pilots in the area.

• B6: An emergency flight can only be declared if you are under ATC control.

• B7: Formation flying is permitted (with specific conditions)

• B8: Pilots must ensure proficiency before flying.

• B9: Limit use of time acceleration/deceleration to only specific instances, be mindful of safety implications.

• B10: Use of IFR flight plans are mandatory.

• B11: Shared cockpits are permitted with specific constraints.

• B12: Traffic management initiatives may be implemented during high-traffic periods.

• B13: Real-world weather parameters are expected during flight simulations

• B14: Accurate IFR procedures and navigational data are required.

Controller Conduct

• C1: Controllers should familiarize themselves with the relevant airspace.

• C2: Controllers must comply with local rules and procedures.

• C3: Observers using a designated callsign suffix ("_OBS").

• C4: Use of correct callsigns for specific controller positions.

• C5: Positions are occupied on a first-come, first-served basis.

• C6: Only approved positions are handled by appropriate controllers.

• C7: (Sub section a) Controllers should have the appropriate infrastructure to provide airport voice services to airports that have them.

• C8: (This one split and merged) Controller actions must confirm with the GRP, TVCP, and local policy, controllers must act with respect to others.

Test your understanding of the VATSIM Code of Conduct with this quiz. It covers general rules of conduct and the responsibilities of account holders within the VATSIM community. This is essential for anyone looking to participate in flight simulation activities.