VATSIM Code of Conduct Companion Document PDF

# VATSIM Code of Conduct Companion Document This document supplements the VATSIM Code of Conduct. It is intended to explain the rules in more detail and provide clarification on some of the Code of Conduct wording in plain English. It is important to note that this document is interpretation, not i...

# VATSIM Code of Conduct Companion Document This document supplements the VATSIM Code of Conduct. It is intended to explain the rules in more detail and provide clarification on some of the Code of Conduct wording in plain English. It is important to note that this document is interpretation, not itself the policy. The Code of Conduct is the governing document. ## Legend * Code of Conduct Text * Plain English Meaning ## WARNING Information contained in the document is intended for flight simulation purposes only. ## A. General Rules of Conduct **(a) - Account holders shall, at all times, be courteous and respectful to one another.** We expect everyone to be polite and respectful to allow everyone to enjoy the network. Foul language, rude behavior, and actions are intended to spoil someone's enjoyment will not be tolerated. **(b) - An account holder must provide truthful and unaltered information to VATSIM and/or staff members. Falsification of information and/or documentation is not permitted.** In cases where deliberate false information, statements, evidence, or documentation is submitted, the account holder may be subject to disciplinary action. You must be truthful in all communications with VATSIM and staff members. You may not provide false information. Any evidence, statements, or documentation sent to VATSIM must be original and must not be altered. Providing false information to VATSIM or its staff members is a violation of this Code of Conduct and may result in disciplinary action against you and your VATSIM account. **(a) - To use VATSIM, you must first register as an account holder of VATSIM. Only registered account holders in good standing may observe, fly as a pilot, and/or provide ATC as a controller.** **(b) - Only registered account holders in good standing may connect to VATSIM or a VATSIM service, except as a guest where applicable.** An account holder in good standing is someone not presently barred from participating in the VATSIM Network and is therefore permitted to log into VATSIM services. There are situations whereby a non-account holder (guest) may utilize some VATSIM services such as the public website and VATSIM mapping software which do not require an account login. **- Without exception, an account holder may not permit or knowingly allow their VATSIM account to be used by anyone else.** Your VATSIM account may only be used by you. You should not allow another person to utilize your VATSIM account. This includes reasonable expectations of account use. You must reasonably protect your account credentials. If you suspect your account may be compromised or accessible by another person, it is your responsibility as the account owner to change your password and/or seek support from the Membership Department as soon as possible to secure your account. Any actions taken by your account are attributable to you regardless of whether or not you took the actions. **(a) - During the registration process with VATSIM, you shall provide your real, full (e.g., first and last) name. Nicknames, callsigns or abbreviations are not permitted to be associated with an account holder's registered account. VATSIM reserves the right, in its discretion, to require proof of real name and proof of age from an account holder.** We require you to register with your real, full name on your account, not acronyms, nicknames or online handles. This information is not shared publicly by VATSIM. However, you are welcome to log in to the network using the information in the following section, which allows certain additional login name conventions should you not wish to log in using your real, full name. **(b) - Account holders shall connect to VATSIM using only one of the following name conventions (Note: an account holder may substitute their surname with the first initial of their surname):** * Their real, registered name (e.g., Joseph Smith, Joseph S.). * An appropriate shortening of their given name, followed by their surname (e.g., Joe Smith, Joe S.) * Their real given name. (e.g., Joseph) * An appropriate shortening of their given name (e.g., Joe) * Their VATSIM certificate ID number. This refers to connecting to our live network (e.g. as a pilot) or other VATSIM services. When connected you must use one of the formats listed above, without exception. Titles and post-nominals are not to be used. If the name you use to connect is not one of these formats, or does not match the information we hold on your account then you can expect to be told to change it. Some pilot clients allow you to optionally add a "home airfield" into your name. This is not mandatory and is perfectly acceptable to include a 3 or 4 letter airport code in this field. **(c) An account holder may append (new) to the end of their name until they are comfortable on the network to signify that they are a newer user (e.g. "Joe (new)").** It can be quite daunting to do your first few flights with ATC. We often suggest you put some reference to being "new" in your flight plan remarks so that other users are aware. Likewise you can put it in your name in this format (if you wish). Pilots in this situation are advised to prepare well for their flight, ensure they are familiar with their aircraft offline before connecting and consider performing first flights in quiet areas. We have a very active community on our forum and Discord who can provide help to the new user. While we do aim to help newer users to get comfortable, there are certain expectations of ability and preparation before you connect (see B8). The use of "(new)" and other indications of being new does not change the expectations of you. **- During your time as a VATSIM account holder, you shall provide and maintain a valid e-mail address. This means that you shall notify VATSIM* *of any changes to your e-mail address. Your e-mail address will not be shared outside the VATSIM organization without your express permission. Failure to maintain your e-mail address is grounds for immediate suspension of your VATSIM account, without notice. ** If your email account bounces back, your account will be deactivated. It can be difficult to reclaim your account if this happens, so we advise ensuring your email is up to date. **- An account holder may register for and hold only one VATSIM account.** Where multiple accounts are held by one user, we will close all but the first account. If you create multiple accounts, we may also suspend or close your primary account. Creating, or even attempting to create, an account to circumvent accounts that have been disabled for disciplinary or administrative reasons is considered a significant offense; users taking such actions are subject to significant disciplinary action, up to and including account termination. **- An account holder shall only use software approved by VATSIM to connect to, or interface with the network. Approved Software An account holder shall become familiar with the basic use of these programs prior to logging on to the VATSIM network.** Software connecting to the network refers to a pilot client or an ATC client. VATSIM only allows clients approved by the development team. You may not utilize any non-approved programs to connect to, communicate with, or otherwise interact with the VATSIM Network. Users are expected to familiarize themselves with the client they choose when logging on. For pilots, this should include: how to turn on the transponder, how to transmit voice and text messages over the ATC frequency, how to see online ATC and how to view and respond to private messages (as these are used by Supervisors to contact users). Air Traffic Controllers must have a higher level of familiarity and be able to competently control the position they are logging onto with the software they select. **- An account holder shall only make one connection to the VATSIM network during any given session, except as may be otherwise provided for in this Code of Conduct.** Account holders can only be connected as a pilot OR controller OR observer. You cannot have simultaneous connections to the network except as otherwise permitted in the Code of Conduct. Exceptions include providing an ATIS or using a towerview connection (clause C7). Other exceptions are only relevant to Supervisors & Administrators. **- Except as provided for in Section B3 of this Code of Conduct, account holders shall not leave their connections unattended. Account holders not actively participating in the network (i.e., connected as an observer) shall not log on for excessive periods of time.** When connected to the network, you are expected to be at your computer and able to respond promptly to messages (whether private or on the frequency). You must also be able to perform your role as a pilot or controller. Air Traffic Controllers are expected to be providing service to pilots and therefore need to be at their computer. Short essential breaks (e.g. to get a drink) are acceptable with ATC permission. Observers are welcome if learning or otherwise contributing, however VATSIM isn't intended as a background application. Observers are expected to be at their computer at all times actively observing and/or learning, and disconnect if not actively observing. Pilots are permitted some time away from their computer under certain conditions, which are detailed in clause B3. **- Account holders shall exercise patience and tolerance towards other account holders, especially where an account holder is less familiar with an area, or learning new skills. This does not relieve account holders from compliance with this Code of Conduct.** We expect users to connect in order to simulate aviation. We expect controllers to receive training appropriate to the position they are controlling and for pilots that can connect and control their simulator and interact appropriately with ATC. However, we don't expect perfection and where mistakes happen we expect a degree of tolerance to allow them to be corrected. Even if you are new, you must be able to follow the Code of Conduct. Being new does not mean you are exempt from sections of the Code of Conduct. Clause B8 details further information about pilot requirements. **- Account holders are prohibited from using any software, forums, newsgroups, social media streams, or mailing lists utilized by VATSIM and its officially recognized Regions, Divisions and their subdivisions to threaten, harass, stalk, or to otherwise violate the legal rights of others including expectations of privacy and publicity. This includes using the above resources to find, locate, or otherwise discover methods of contacting account holders for the purpose of threatening, harassing, stalking, or otherwise violating the legal rights of them.** **Further, account holders shall not publish, post, distribute, disseminate, or use any kind of defamatory, infringing, obscene, vulgar, profane, unlawful, or other similar types of communications, materials, or information. Individuals violating this rule are subject to the procedures set forth in Article I of the VATSIM.net Code of Regulations, which may result in removal from VATSIM and revocation of their account privileges.** We expect you to behave legally and not cause distress to other users through your interaction with them. This clause lists a series of actions that we consider non-exhaustive examples of unacceptable behavior that may be grounds for suspension or termination of your account. **- Account holders shall not connect to VATSIM with a callsign, or other identifier, that implies or designates a status they do not hold including, but not limited to, those reserved for, or generally used by, Founders, users of the Board of Governors, Supervisors, and/or any other network staff. Furthermore, account holders shall not state, imply, or otherwise communicate that they hold a status they do not.** Users are not permitted to claim they are a staff user, at any level, if they don't actually hold that position. Pretending to be a Supervisor or other staff user may result in your account being suspended. The following callsigns formats (non-inclusive) imply a staff position and must not be used (# here means any combination of letters and numbers): * VATSIM# - these callsigns imply status as a network Founder * VATGOV# - these callsigns imply a user of the Board of Governors * VAT# - implies a division staff user (e.g. VATEUD1 for the EUD Division Director) * #_SUP - implies a network Supervisor * #_ADM - an alternate callsign authorized only for those that hold the rating of network Administrator Other staff callsign formats exist that are not listed here. Users may not utilize a callsign that resembles a staff callsign **- Account holders shall only connect to VATSIM as an observer, a pilot, or an air traffic controller. No other connection is permitted. Fictional and/or unrealistic aircraft/vehicles are not authorized. Military, paramilitary or civilian government agency operations and/or activities must be authorized by an approved Special Operations Organization. Special Operations restrictions and procedures are defined in the Special Operations Policy.** VATSIM simulates aviation and aerial military/governmental operations only. We do not permit ground vehicles, spacecraft, drones (excluding unmanned aerial vehicles, e.g. Global Hawk restricted to vSOA operations only), boats that are not capable of flying in a manner as defined in the VATSIM Code of Conduct. Additionally, VATSIM specifically prohibits unrealistic and fictional aircraft from use on the network. VATSIM restricts certain flight operations to account holders who are active & trained members of an approved Special Operations Organization (VSOA) and operating under a vSOA approved operation. A list of restricted operations can be found on the VATSIM Special Operations, Policy & Procedure Manual. Some examples of flight types that require vSOA membership to perform include: * Air-to-air refueling * Low-level high speed flight * Intercepting, escorting * Air show activities * Search and Rescue & Firefighting * Flying unmanned aerial vehicles The full list can be found in Special Operations Policy. Some examples of flight types that do NOT require vSOA membership: * Flying a military jet at "slow" (e.g. subsonic) speeds down civil routes * Flying transport/cargo flights between military airfields * Flying a helicopter with a callsign such as "helimed" or "lifeguard" in the airspace that it may fly real-world, performing such duties. Note performing search and rescue operations falls under vSOA restricted category * Using a military callsign whilst on a civil route with a non-military aircraft * Flying agricultural (Ag) flights, such as agricultural aerial application **- Voice is the preferred method of communication on VATSIM. Account holders should use voice if able to do so but shall accommodate the use of text. Only unaltered speech is permitted to be transmitted.** Voice transmissions must be spoken in the pilot/controller's own voice. Voice morphers, music, shouting, or other disruptive noise is not permitted. We encourage users to utilize voice communications wherever possible, though text-only is available for interacting with controllers and on unicom where a pilot needs to. It will always be assumed on unicom that a pilot is monitoring voice and text, therefore a pilot unable to receive voice unicom should regularly make it clear on the unicom frequency that they are text-only. Controllers will always be required to provide services via text if requested by pilots and are not permitted to ignore, refuse, or otherwise reduce the priority of pilots communicating without voice. Pilots using text (especially on the ground) must be aware that in busy airspace a controller may be tackling large numbers of high priority tasks via voice before they are able to respond, in the same way that pilots on voice may need to wait for a gap in communications for the same reason. **- While connected to VATSIM, and when requested to do so, account holders shall respond to messages from, and comply with all instructions issued by VATSIM Administrators and/or VATSIM Supervisors.** Supervisors or Administrators will typically contact you via private message on the network. Supervisors will usually be logged on as #_SUP (e.g., ABC_SUP), though you can check the online Supervisor list here: https://stats.vatsim.net/who If you are contacted by a Supervisor or Administrator who is instructing you to do something, you are expected to do so and to reply promptly. They are present to assist users, enforce the rules and to protect the enjoyment of all users. You can call a Supervisor in any approved client by typing: wallop type your message here for why you need help In your message to the Supervisors (the text after ".wallop'), you should include information about what is wrong Example: ".wallop N123AB is cursing on ABC_CTR's frequency" **- All voice and text communications frequencies are for operational use only. Account holders shall not carry out private conversations over any communication channels, frequencies, or resources, with the exception of private text messages. The Guard VHF radio frequency (121.500) may be utilized in accordance with real world procedures. Pilots and air traffic controllers should monitor Guard if able.** Any frequency including unicom, whether voice or text is strictly for simulation purposes. Messages transmitted are expected to be related to your flight either to interact with ATC or to announce your intentions to other pilots. This rule does not prohibit brief pleasantries as is common in aviation. Accepted air-to-air frequencies, such as 122.75 in the US for fixed wing general aviation, are perfectly acceptable to be used for reasons such as coordinating formation flights, fly-ins, etc. General chit chat should be taken to other communication platforms such as private messages. These air-to-air frequencies do not replace unicom and should never impact ATC operations. The "Guard" frequency 121.5 is the international emergency frequency. It is designed for use to transmit distress messages and to get a hold of unresponsive pilots. As in the real world, the Guard frequency may be utilized on VATSIM in accordance with real-world procedures. Pilots are expected to monitor Guard on their second radio if they are able to do so. **- The re-creation of, or organization of events or activities recognizing or simulating real-world disasters, tragedies, or other such events, particularly those which resulted in loss of life, are not permitted.** VATSIM considers the re-creation of aviation disasters to be distasteful. Therefore, simulating a crash or simulating the flight of a crash is prohibited. Certain callsigns are prohibited and you will be restricted from logging into the network with these callsigns. These restricted callsigns include: * American Airlines 11 * American Airlines 77 * Malaysian Airlines 17 * Malaysian Airlines 370 * United Airlines 93 * United Airlines 175 As many airlines re-introduce the callsigns of former crashed aircraft, most callsigns are not prohibited. You should avoid intentionally using the callsign of a crashed aircraft in a similar area/route. VATSIM further does not permit flights in relation to current real-world conflict, disaster or war. Whether well-intentioned or not, users will be told to stop if conducting military flights in warzones or flying "relief missions" for real-world disasters. VSOAs may fly relief missions in accordance with vSOA policy (reference VSOA policy for further information). **- VATSIM welcomes account holders who wish to stream, record, or otherwise distribute their session for public viewing.** * (a) The online network conduct of the account holder during the stream/recording remains subject to this Code of Conduct. * (b) If a link to the stream/recording is provided either in their flight plan, or via another VATSIM operated medium, the entire stream/recorded session including informal mediums such as a stream chat are subject to this Code of Conduct. * (c) Account holders connected to the network who deliberately disrupt the stream/recording of another user are subject to immediate suspension from the network. * (d) VATSIM does not have the ability for its account holders to opt-out of being part of another account holder's stream/recording. We expect users streaming their VATSIM content to appropriately moderate it. Where you don't list your stream on VATSIM (i.e. it's not in your pilot remarks), you are free to moderate it in accordance with your own rules and the rules of the streaming service you are using. If however you advertise it in your flightplan, or otherwise via VATSIM (e.g. VATSIM Discord servers), you must ensure the content of your stream including your comments on informal medium such as stream chat does not break the Vatsim CoC. While streaming, you are still expected to follow all other sections of the Code of Conduct. You must prioritize your interaction on the VATSIM Network over your stream. It is not acceptable to become distracted by your stream and let your performance on the network slip. Where content of your stream violates the code of conduct, we may take action against your account. For the avoidance of doubt, this includes: * Ensuring your video and chat do not have rude/disrespectful content * Ensuring illegal activities are not allowed to be recommended (e.g. piracy) * Not encouraging or allowing others to break the rules * Not allowing viewers to harass other users ## B. Pilot Conduct **- A pilot shall not connect to the VATSIM Network on a runway or taxiway. When a pilot connects on the ground at the same location of another aircraft, the pilot connecting shall deconflict with the aircraft already occupying the location. If a pilot chooses to connect while airborne, said pilot shall ensure doing so does not cause disruption to other account holders. ** It is expected that you will start a connection to the network at a gate, or other designated parking area. When you connect on the ground, if you conflict with another aircraft, you are expected to move your aircraft to get out of the way of the pilot who is already there. Please note that it may take a few seconds for aircraft to appear in your simulator after you connect to the network. It is recommended to review the VATSIM Map before you connect to avoid these issues. Connecting on the runway or taxiway is not permitted, even if the airport is quiet. If you load up on the runway, you will be required to disconnect and reconnect at a suitable parking location (gate, ramp, etc). Exceptions may apply for gliders operating from gliderports, after the pilot verifies no conflict with others. Pilots should only need to connect airborne when they have been accidentally disconnected from their flight or needed to step away from their session as per section B3. When returning in such a case, the pilot is expected to review other aircraft & ATC online in the area in which they connect to ensure they will not cause any conflict when connecting, this may be accomplished with a VATSIM Map. If ATC is online, the pilot should first connect through their pilot client as an observer and coordinate with ATC. The pilot should be prepared to provide ATC their current position, altitude, direction of flight, and other pertinent information as requested. Commencing a flight and then connecting in the air to bypass ATC is never permitted. See section B12 for further information on traffic management initiatives. **- A pilot shall not pause while connected to the VATSIM Network except when operating under air traffic control, with the express permission of the controller. If the controller revokes the permission for any reason, the pilot shall un-pause immediately.** Pausing is often unexpected for those around you and it's challenging for you to know who you are going to affect. When under the control of ATC, if you pause for only a few seconds, traffic behind you rapidly catches up. In busy traffic environments, this will require the controller to take urgent action and then completely replan a sequence. Therefore, never pause with ATC unless they have explicitly permitted it. It's better to tell the controller your issue (e.g. ask for a hold or a turn away). Because it's impossible for you to know who you may affect, VATSIM doesn't permit pausing except in very limited circumstances. **(a) - Pilots shall monitor their flights at all times. It is the responsibility of the pilot to check for and make timely contact with appropriate air traffic controllers. This includes making prompt contact when requested to do so. Pilots shall be attentive to their aircraft and ATC and respond to instructions without delay.** If a controller is online covering the airspace you are in, it is your responsibility to make contact with them. You may leave your computer for brief periods of time to perform essential tasks, however if a controller appears while you are away, you need to be able to promptly return. Before going away, it is therefore important to look ahead for potential ATC you might need to contact. Always consider disconnecting temporarily if you're going away for longer than a few minutes and/or you won't be able to hear contact messages sent by ATC. While under control of ATC, you may not step away without the express permission of the controller. If a controller reasonably sends you a message and asks you to contact them, you need to do so promptly. It is your responsibility to do this, no matter the situation. This includes if you think you aren't yet in their airspace, or you believe they have misinterpreted your flight plan. While under ATC control, especially during critical phases of flight, you must minimize distractions and must refrain from watching media which may take your focus away from your flight. It is critical to maintain a constant watch over all aspects of your flight including but not limited to your aircraft and the ATC frequency. A controller should not need to issue you an instruction more than once. If you are constantly missing instructions from ATC, you must pay more attention. Controllers on VATSIM often work large amounts of airspace in a top-down fashion. As a pilot, you may not always hear all the traffic on frequency due to the large distances involved. A pilot who misses instructions from ATC adds a very high workload on an already busy controller and shows disrespect to the service they provide. **(b) - If it becomes necessary to leave a pilot connection unattended, the account holder should disconnect from the network. When operating under active air traffic control, a pilot may step away for a short period of time with express permission from air traffic control. Notwithstanding anything in this Code to the contrary, no pilot connection is permitted to be unattended for a period of longer than 30 minutes.** When operating under an active air traffic controller, you cannot step away without the controller's permission. You may only step away if the controller authorizes you to. These times away from the cockpit must be limited and short in duration. You are never permitted to be away from your keyboard for more than 30 minutes while connected to the network. This does not mean you are allotted 30 minutes away, as the requirement to contact ATC in B3(a) overrides this rule. If you are going to be away for longer than 30 minutes, whether there is ATC online or not, you must disconnect. **(a) - Pilots shall utilize a transponder when required by regulation and/or procedure. Air traffic control may approve operations without a transponder.** Airspace designations (as well as countries) and/or procedures may specify that a transponder is required in certain airspaces and not in others. You may simulate operations without a transponder, in a way that is realistic and in compliance with these rules unless you receive approval from ATC for a deviation from the rules. For example, if an airport chart or ATIS states to utilize a transponder in Mode C, you must follow that guidance and set your transponder to Mode C or receive approval from ATC for a deviation from the requirement. Pilots simulating operations without a transponder need to be knowledgeable of the rules and prepared to navigate accurately in the airspace they are flying. When simulating a transponder, if requested to turn a transponder on due to airspace infringement, the pilot should do so promptly. If they believe the controller to be incorrect, this should be handled politely and potentially after the fact, fed back via the relevant VACC/ARTCC/Division. We recommend less experienced users to always simulate having a transponder and have their transponder turned on when airborne and when operating on the ground at large airports. If you aren't sure whether you can operate without a transponder, ask ATC or leave your transponder on. Operating without a transponder intentionally to cause disruption will not be tolerated. Likewise, repeated airspace infringements whilst operating without a transponder are not reasonable. **(b) - A pilot should maintain a previously assigned squawk code unless otherwise directed by ATC or flight rules have changed. When not assigned a discrete squawk code, a pilot shall utilize a squawk code appropriate for their flight rules (IFR/VFR) and location.** When assigned a squawk code, you should utilize it. Maintain your last issued squawk code when released to advisory frequency. If your flight rules or flight type have changed since being issued a code, and you are on advisory frequency, you may consider changing your squawk code. If you have not been issued a squawk code for your current flight, you should select a squawk code that is appropriate for your flight rules & type. See below for examples, reference appropriate country publications for specifics & additional codes. All codes assume another specific squawk has not been assigned. | Code | Operation | Country | |---|---|---| | 1200 | VFR | USA, Canada, Australia | | 1201 | VFR in LAX SFRA | USA | | 1202 | VFR Glider Operations (not in contact with ATC) | USA | | 1255 | VFR Aircraft not in contact with an ATC facility while enroute to/from or within the designated fire fighting area(s). | USA | | 2000 | IFR | ICAO | | 4000 | VFR Military on VR route or requiring frequent/rapid changes in altitude | USA | | 7000 | VFR | ICAO (minus countries from 1200 code above) | | 7001 | VFR Sudden military climate out from low-level operations. | UK | | 7004 | VFR Aerobatics | UK | | Frequency Monitoring Code (FMC) - As Defined | VFR listening to specific frequency | UK | A civilian aircraft squawking VFR should not be flying in Class Alpha Airspace! *There may be certain local exemptions to this such as defined "Wave Windows" for gliders, if coordinated with ATC. Note that certain procedures may permit a pilot to change their squawk code without being instructed to do so. An example of this is oceanic flying. It's common that pilots are expected to squawk 2000 without ATC instruction a certain amount of time after entering oceanic airspace. In the North Atlantic airspace, this is generally expected 10 minutes after entering oceanic airspace. Refer to local procedures for specifics. **- Pilots flying through uncontrolled airspace shall monitor VHF radio frequency 122.800 or other designated advisory frequency until they come under air traffic control coverage. Where another pilot may benefit, or when in doubt, a pilot shall transmit their intentions on the designated advisory frequency.** Monitoring the advisory frequency (122.8 unless otherwise specified) when no ATC is online is mandatory. You should monitor both voice and text channels. Certain locations in the world publish specific advisory frequencies which must be used. See USA below. It is expected that you should make voice or text announcements to raise the awareness of other pilots in the area when flying. Examples of when you will likely need to make unicom transmissions include: * Pushing back when pushing back onto a taxiway * Before you enter a runway (stating the runway and airport) * Descending into busy airspace * Establishing an approach Further information on using advisory frequencies is available on the Pilot Learning Center. The more traffic in the area, the more transmissions you will likely need. Pilots should transmit even in situations where other traffic may not be present. Just because you have not seen/heard a transmission from another aircraft does not mean there are not others which may benefit. In many cases, pilots are expected to "transmit in the blind". Announcing on advisory is not the same as ATC clearance. There may be other pilots around and you should appropriately attempt to accommodate others. Therefore you should announce your action early so that people have time to reply if there is conflict. When operating around others, particularly when ATC is not online, it is especially important to be respectful of and patient with, others. Announcing your intentions does not give you any right to ignore or intentionally conflict with other traffic. None of this section implies that the concept of see and avoid is not critical. See and avoid is the primary method of separation in uncontrolled airspace. When you are in uncontrolled airspace or visual meteorological conditions (VMC), you are expected to visually look out for other traffic and follow the right-of-way rules. If another aircraft is not transmitting on frequency, you must still make all attempts to deconflict with other traffic. Even if you have not heard or seen a transmission from another aircraft, this does not mean that they have not made a transmission as they may have been out of range, or blocked by another aircraft. A tower controller, or a controller providing top-down service to an airport would normally designate the active runway(s). Where such a controller doesn't exist (e.g. "ground" controllers only, or no ATC), there is no official "active runway" and so any other information is considered a suggestion. However, where a suggestion (e.g. a ground controller's ATIS, published real-world information, etc.) is available and a pilot wishes to utilize a different runway, they should attempt to minimize the impact on other pilots by delaying their departure/landing if required. **VATUSA CTAF Trial** VATSIM United States Division began a CTAF (Common Traffic Advisory Frequency) trial on 1 March 2024. This trial replaces 122.800 frequency and utilizes real world CTAF for pilot traffic announcements and coordination. CTAF is the designated frequency when flying in the United States to make traffic calls. Other countries will roll out CTAF in the near future. For more information and how to determine the correct CTAF frequency, visit: https://vats.im/ctaf-trial **- No flight may declare itself to have priority over another. Pilots are permitted to declare in-flight emergencies only when under air traffic control. If, for any reason, air traffic control requests the pilot to terminate the emergency, then the pilot shall do so IMMEDIATELY or disconnect from the network. Pilots are not permitted to simulate any unlawful act including, but not limited to, declaring a hijack by any method, including entering a transponder code of 7500.** Emergencies are only permitted when under ATC control. ATC may choose whether or not to allow the emergency and if they choose to deny it, you must stop simulating an emergency or disconnect from the network. The controller you are with may be happy to accept an emergency, but future controllers are permitted to deny emergency status. Nothing in this section makes it a requirement to request permission in advance to simulate an emergency. Pilots may not give themselves priority handling, even if a real-world equivalent of their flight may automatically receive it (e.g. Air Force One, medical evacuations, etc.). ATC may, at its discretion, provide priority handling to an aircraft simulating certain operations (see A13 for restrictions on pilot operations). ATC cannot shut down airports or excessively delay other aircraft to provide this priority. **- Two or more pilots are permitted to fly in formation. If, for any reason, air traffic control instructs pilots to separate, the pilots shall immediately comply with the request or disconnect from the network.** This clause relates to both military-type formation flights (covered by the vSOA policy and clause A13) and non-military formation flights that may be flown by any user. All of the pilots in the formation must agree to be flying in formation. If a controller is online covering airspace the formation flight is in, they can instruct pilots to separate. This instruction cannot be refused. Pilots should be aware that this is most likely when flying formations that would be unrealistic real-world. **(a) A pilot must be familiar and proficient with the operation of their aircraft prior to connecting to the VATSIM network and shall comply with all agreed (read-back) air traffic control clearances or instructions. Where unable to do so, such as where operational safety is compromised (e.g. TCAS conflict resolution), air traffic control must be notified without delay. ** We recommend you fly offline a few times in a new aircraft before connecting to the network so that you are familiar with how to operate it. Where you are flying with ATC, they will expect you to have a basic proficiency level for the type of flight you are performing. This being said, VATSIM considers everyone to be learning, therefore if you receive a complex instruction you can't comply with, ask for something simpler. Don't accept a clearance you are unable to fly. If you receive an instruction from ATC and read it back, you are expected to comply. Intentionally disregarding is not acceptable except where you deem it likely to cause a crash (e.g. TCAS alerts), in which case you need to communicate this urgently to ATC. Accidentally not being able to comply multiple times strongly implies you do not have sufficient proficiency with your aircraft and is quite challenging for ATC to handle. **(b) - Pilots who are unfamiliar with an airspace shall educate themselves by first observing operations and/or studying procedures used in that location. A pilot is expected to undergo reasonable preparation for their intended flight and potential diversions. This includes basic familiarization with arrival/departure airports, departure/arrival procedures and their planned route. Pilots shall familiarize themselves with airspace structure to prevent infringement of controlled or restricted airspace. Pilots should select aircraft that are capable of utilizing intended airports.** A pilot flying into new airspace must spend time and effort on learning how to fly appropriately in the new airspace. Even experienced pilots may need to review training and other publications or training material to gain additional knowledge on flying in a new area. A pilot needs to prepare for any flight on the network. Ground clearances, direct routes, SIDs and STARS, approach procedures are all predictable parts of an IFR flight. A pilot is therefore expected to familiarize themselves with these so that they can follow ATC instructions. This doesn't require committing all information to memory, however having appropriate charts and looking up the procedures is expected. Even when flying VFR, you must still be familiar with the appropriate charts. Adherence to airspace is required, this includes but is not limited to: airspace class, restricted airspace, special use airspace, and published special flight rules areas. When in doubt about whether or not a restricted/special use airspace is active, contact ATC. There is a difference between making mistakes and being unprepared/unaware. Ignoring what ATC have said and just taxiing to the runway is not acceptable. Accidentally planning a route that is