VATSIM Pilot Resource Center – Required Reading

To view this page ensure that Adobe Flash Player version 9.0.124 or greater is installed.

Please login or register to make a comment!

VATSIM Pilot Resource Center Required Reading for New Pilots FOR FLIGHT SIMULATOR USE ONLY Copyright © VATSIM.net. All rights reserved. VATSIM Pilot Resource Center 3 Required Reading By Mike Bevington This introductory course is considered minimum reading for new VATSIM members.

Please take the time to read and understand the information contained here. It is a summary of critical items found in VATSIM courses 101 through 121. For detailed information about online flying with VATSIM, I highly recommend you review the individual courses relative to your area of interest.

The VATSIM Pilot Resource Center (PRC) courses relevant to the content below are shown in (italics) . I. PILOT EXPECTATIONS VATSIM is a volunteer organization.

There are no fees or membership dues. The members are dedicated to participating in an ATC environment using real world procedures and practices to the greatest extent possible on a virtual flight simulation network. In order to remain a member in good standing of VATSIM, there are three sets of rules you need to follow: the VATSIM Code of Regulations, the Code of Conduct and the User Agreement.

The full and current text of each of these documents may be found on the VATSIM website ( http://vatsim.net ). - (102e) ... more. less.

Pilots are expected to maintain a current ISP based email address, keep informed of and comply with all VATSIM NOTAMs. They are expected to observe ATC regulations pertaining to the airspace through which they are flying and seek help using private messages, the local or regional web sites, or through email contact with the leadership of the airspace to which the specific regulations apply. Pilots should always be courteous to other pilots and controllers, and treat them with respect . Our primary reason for being here is the enjoyment of the hobby. Please keep that in mind at all times. Be cordial to other users, exercise patience, and stay cool. Take the time to express your gratitude to the controllers with a cThank you, job well done d when the occasion calls for it. That goes a long way in bringing a sense of accomplishment to the men and women who take the time to become highly proficient at providing the ATC services that make VATSIM incomparable. Log on to fly or observe, not to chat . New members are encouraged to observe how things operate on the network. This helps to learn both procedure and phraseology (a fancy word which describes how ATC and pilots communicate). Keep in mind that legitimate observation to learn will always be encouraged as it is a necessary practice to become comfortable with using and functioning within the VATSIM environment. It is only when you cross the line between legitimate observing and using VATSIM as a chat program that you will be in violation of this rule. - (102d & 102e) Pilots are expected to plan their flights up to, but not in excess of, their ability. If you don 9t have or know how to use VFR or IFR charts, say so in the Remarks section of the flightplan. Pilots are expected to PLAN their flights prior to logging onto VATSIM. Sitting on the ground for more than 30 minutes is not acceptable on VATSIM unless you are a new member trying to learn the flow of ATC communications. If that is the case, insert something like cNewbie observing ATC d in your flightplan so the controller or supervisor knows your intentions. II. MINIMUM REQUIREMENTS The following items are minimum expectations of VATSIM Pilots and are discussed in detail on the VATSIM Pilot Resource Center: " A basic understanding of piloting skills, and to safely perform all of the following: (101e) o Taxi o Take-off o Maintain an assigned altitude, heading, and airspeed o Navigate to and from an airfield in VFR flight, or navigate to and from navigation aids such as VORs when in IFR flight o Fly a basic traffic pattern o Land on an assigned runway " Understand the difference between VFR and IFR flight - (121c) " Although IFR skills are not required, learning to file and fly on an IFR flightplan greatly enhances the VATSIM experience later - (122c) " Understand valid altitudes for direction of flight - (102a) " Be familiar with the Pilots 9 Etiquette Guide - (102 & 121f) " Understand basic ATC phraseology - (111a) " Tune to different radio frequencies and effectively communicate with a controller - (FAQ & 121h) " Answer a private message (or chail d) from a controller or supervisor - (FAQ) " Follow instructions from VATSIM air traffic controllers - (111 & 121) " Ask questions or get clarifications if you do not understand - (102a & 121) " Set up the software required, join the network with your real name, choose a callsign, set the aircraft type, and be able to file a flightplan - (103, 121d, 122a) " Be courteous and respectful at all times - (101, 102, 121, 122) " Operate within the limits of the VATSIM Code of Conduct, User Agreement, and Code of Regulations - (102d & 102e) III. GETTING STARTED Once you have completed the following steps, you should be ready to log onto the VATSIM network: VATSIM ID and Password IP for the VATSIM server nearest you (see cHow do I see who is online? d in the VATSIM FAQ) - (104b & FAQ) Aircraft you have flown before and are familiar with its characteristics - (102a) Downloaded and properly installed all the required pilot software such as SquawkBox, FSInn, AVC, etc. - (103 & 104) Have a headset with a boom mic for AVC (Advanced Voice Client) Text Only pilots can disregard this step - (103a) Reviewed the Pilot Resource Center thoroughly to eliminate surprises Filed a flightplan at the VATSIM Flight Plan page or through the SquawkBox or FSInn Flight Plan screens. In the Remarks section put something like cFirst flight, request ATC assistance d - (122a) Preparation is part of flying. Before you start, you should have all the materials you need for the flight (charts/approach plates/etc.) easily at hand. Visit the website of the ATC sector or sectors you 9ll be flying. There is a wealth of information on airspace rules, preferred routes, sector boundaries and much more available on these websites. While many controllers will be happy to help you with procedures when traffic is slack, do not rely on this. Start your flight with a quick visit to the websites of the ATC sectors and you 9ll be on your way to a much more enjoyable flight! Squawk Standby preferably before connecting to VATSIM. After starting your connection software (FSInn or Squawkbox or xSquawkbox) but just before connecting to the VATSIM network, select c Squawk Standby d in the popup menu to place your transponder on standby. Then upon reaching the hold point for departure, unselect cSquawk Standby d to place your transponder in the normal mode (squawk mode Charlie). Some major airports may ask that you squawk normal in all movement areas. Check your local rules. This helps ATC by reducing the clutter appearing on the controller 9s radar screen. Connect with your aircraft positioned on a parking ramp or parking/gate area only . When connecting, a pilot should never be on a taxiway, or on a runway. If there is an aircraft on short final for the runway and suddenly another aircraft pops up on the same runway, a landing pilot will be quite displeased because they will be asked to go around. - (102a) Know your aircraft and how to control it. Although this may sound basic, it 9s an unfortunate reality that many new pilots initially find that their ability to control their aircraft is not as good as they thought it was. Obviously, this can be very disruptive. The network is not the best place to try out that hot new panel or airplane you 9ve never flown before. Remember that although c as real as it gets d may be the goal, sometimes technical and system realities get in the way. VATSIM is a global internet network with an extremely diverse membership. Different members may have dissimilar levels of connectivity, varying system capabilities and an indeterminate level of experience. Controllers and pilots, even the most experienced and knowledgeable, are often faced with having to sacrifice some realism in order to accommodate system realities. Understanding that in these situations, individual controllers and pilots may make different decisions about what is the least unrealistic way to proceed. Approaching the process with a relaxed , flexible and positive attitude will go a long way toward increasing your enjoyment of the network. IV. FIRST FLIGHT For your first flight on VATSIM, start small and work your way up. It is recommended that you carry out your first few flights at either smaller or less busy airfields where there is ATC. This will allow the controller much more time to help you, give advice, and talk you through any difficulties you may have. Starting your first flight at a major fly-in or extremely busy airfield is strongly discouraged. Traffic levels are usually very high with mainly experienced pilots. See VATSIM 122 for more information. - (102a & 122) Use proper radio phraseology. When using voice, a pilot should never jump right into a transmission immediately after connecting. Allow yourself enough time to get into the flow of the communications. Never overstep another transmission, when you do so, the controller cannot hear either transmission clearly. While text makes it easier to communicate (no need to wait, the controller can see several lines at once), there are certain rules of etiquette that govern this medium. Transmissions should never be conducted entirely capitalized, or entirely in lower case. All capital letters insinuate that the typist is yelling. In addition, a pilot should not be afraid to use shorthand when replying to ATC. - (111, 121, 122) File for and fly at the correct altitude for your direction of flight. Aircraft operating in the cruise segment of a flight are provided a generic separation based on their heading. Individual countries around the world may have different rules for this - so firstly check your local Division 9s web page for the actual altitudes for your flight. There is a general guide for valid altitudes in the VATSIM 102a lesson. - (102a) IFR Pilots should check their flightplans before requesting clearance. Many areas are not allowing GPS Direct flights, so plan to fly airways. If you want to use your GPS System, you can use it to guide you to various intersections and VORs along your route. Ensure that the proper aircraft is selected, proper altitude is entered, and that your departure and arrival airports are correct (often a pilot will file their intended route, but leave the airports from their last flight). Also, the IFR Pilot should at least possess the approach charts for the various approaches that they may require. For example, if I am on the ILS Approach to runway 16 in Calgary, and must declare a missed approach, I should be able to climb to 5500 without the controller telling me to do so. I know this procedure because it is written on my chart. The chart also gives localizer information, NDB and VOR frequencies, and runway lengths. During a busy shift, a controller would be burned out rather quickly if required to continuously repeat cLocalizer frequency 109.3 d, when the pilot should know that by reading the chart. - (121d, 122a, 122c) Some pilots enjoy flying VFR , that is, Visual Flight Rules. If you are going to fly VFR, you must do your homework. Know where you can and cannot fly, and keep well clear of Class Bravo airspace. Nothing annoys a controller more than having an aircraft draw a complete circle around the TRACON. Filing a flightplan is also of great benefit. Instead of forcing the controller to tie up the frequency finding out where you want to go, simply file a flightplan, for example, cSouth Shore Long Island to Verrazano Bridge, up VFR Corridor, GWB then KTEB d - (121d, 122a, 122b) Accepting a clearance from a controller is an absolute agreement to do what the controller has instructed you to do 3 If you don 9t understand ASK 3 DON 9T TRY TO FAKE IT!!: The instructions that a controller gives you can be likened to a contract 3 in reading the instructions back, you have agreed, dated, and signed the contract. - (102a & 121e) When the controller issues instructions, you should get in the habit of writing them down as he or she says them. This ensures that you do not forget a vital bit of information. When you read the instructions back, read exactly what you wrote. This serves as a final check for your instructions. If you do not understand something, do not read it back. Make sure that you 9ve contacted the appropriate controller before taxiing at an airport where tower services are being provided or before departing when no tower is available. When initially connecting to VATSIM, pilots should check the ATC List to connect to a controller. Use the ATC Directory menus in your connection software, the VATSIM cWho 9s On Line d page, or use ServInfo (link is in the FAQ document) to determine what controllers are on-line. Start with Clearance Delivery (xxx_DEL) for your location and tune to their frequency. Look for ATC staffing in this order: DELIVERY (xxx_DEL) GROUND (xxx_GND) TOWER (xxx_TWR) DEPARTURE (xxx_DEP) APPROACH (xxx_APP) CENTER (xxx_CTR) NOTE: Sometimes, the position callsign is listed in three sections (LAX_V_CTR). Further along these lines, the center section (_V_) may appear with other variations such as (_KND_), (_VS_), or (_V1_). From our viewpoint as a pilot, that is just added confirmation the position is cvoice d capable. All controllers should be assumed to be on voice unless their ATIS message when connecting to them says they are text only. Taxiing properly is part of the process 3 not optional. Part of the process may be having to wait your turn. If you feel the need to try to cut the line by taxiing across the grass or declaring a phony emergency 3 disconnect and come back when you have the time. - (102a) Nothing is more frustrating to a controller than sequencing a string of traffic, and sending them all into holds because someone decided to takeoff without contacting ATC. You should check when you first connect, before taxiing, and before takeoff. If there is no controller, you should announce your intentions over the Unicom (122.800) frequency. - (102a, 121, 122) While not being in contact with an active air traffic controller, pilots must monitor the UNICOM-frequency 122.800 . - (102a, 102d, 121, 122) V. AIRBORNE Pilots flying inside active (controlled) airspace must not leave the cockpit unattended at any time. If a pilot needs to leave the flight unattended for a few minutes, the pilot should request the planned absence with the active air traffic controller. Report your return to the cockpit to the controller. - (102d & 102e) Pilots flying outside of active (controlled) airspace are required to log off of the network if it is anticipated that they will be leaving the cockpit unattended for more than thirty (30) minutes . If you are found to be unresponsive for more than thirty minutes, you will be subject to immediate removal from the network. Repeat offenders will be subject to suspensions and/or expulsions. One thing to note is that staff is not always required to give you the full thirty minutes . If you fly into controlled airspace and are unresponsive, you can be removed immediately. The point to remember is that if you intend to be away from your computer for more than 30 minutes or you find yourself suddenly needing to leave, take a brief moment to disconnect from the network. - (102d & 102e) Aviate, Navigate, Communicate. This means that when ATC issues instructions, control the plane, start to carry out the instruction, THEN communicate with ATC in the form of a readback. When on voice, this is one seamless action. However, on text it is important to act promptly on the command, and then turn your attention to the readback. - (101a & 121h) When a controller gives you vectors, he/she is not picking arbitrary directions and numbers. He/She is, in fact, going through numerous calculations designed to keep all aircraft separated from one another. For example, I may be flying a heading of 010. There is traffic at my altitude at a bearing of 020. If the controller wants me to come to a new heading of 040, without altering speeds or altitudes, he/she may simply say cAmerican 602, turn right heading 040 d. It is vital that you, as the pilot, follow this instruction. If you do not, the controller will see flashing conflict lights pop up on the screen. If a controller directs you to perform an action that really makes no sense to you, i.e. directing you to turn left to 040 in the example above, without additional clarification that you are expected to circle 330 degrees, asking for confirmation on a left turn versus a right turn is most likely in order. - (102a & 121e) Pilots flying under the control of student controllers are kindly requested to be patient and fair to this new member of the ATC community! Disconnect from the network in the event of system or other problems that make you unable to fly properly. If you have an equipment failure that makes it impossible for you to safely fly or taxi your plane and you cannot take reasonable actions, explain this to the controller and then politely disconnect from the network until you can fly again. When you reconnect, do so at a reasonable place (e.g. not in the middle of a runway), not necessarily the place where you disconnected. - (102a) VI. PROHIBITED ACTIONS It is forbidden to have more than one connection to the VATSIM network at a time. If you wish to get information about your flight status, please use ServInfo or Whazzup. You can find links to them in the VATSIM 104 course. - (102d & 102e) Simulations of emergency situations are not forbidden on VATSIM. However, air traffic controllers have the right to deny the simulation of an emergency and pilots must stop the emergency if requested to do so. If the pilot is unable to stop the emergency, the pilot must log off the network. It is strictly forbidden to simulate hijacking-situations . - (102a & 102d) Never pause your simulator or use time acceleration except as authorized by ATC. If you need to pause your simulator or want to increase time acceleration (i.e. 4X), notify the controller with whom you are in communication. The controller may have you fly slightly off course to pause or increase the simulation rate so you do not disrupt the flow of traffic; a ground controller may have you taxi to a hanger area away from important taxiways. NEVER pause while taking off, landing, or flying an approach, even for a small amount of time. Even the pause to reload scenery can take long enough to cause problems. Be very selective about when you access Flight Simulator menus because that causes the aircraft to pause as well. Make sure 'pause on task switch ' is turned off in the flight simulator. - (102a) Don 9t chat with controllers or try to use text to cget attention d when the voice channel is busy. Harassing a controller who 9s already busy with traffic only makes things more difficult for all 3 a little patience goes a long way here. Also remember that if you are only using text (not voice capable) you have no idea how busy the controller is on voice! Please be patient. - (102a, 121f) Don 9t argue with other pilots or controllers on line. Be courteous, be patient, and stay cool. If you have a complaint, collect the details and email the relevant Conflicts Manager - (102e) VII. GETTING HELP Learning new skills takes time and study in order to be proficient. There are many resources available to the on-line pilot. You are encouraged to seek answers to questions by completing the courses within the VATSIM Pilot Resource Center. There are many areas of study covered, as well as a very handy FAQ. Other resources include: " Microsoft" Flight Simulator 2000, 2002, 2004 and FSX built-in flight training programs " VATSIM Home Page: http://vatsim.net " VATSIM Forums: http://forums.vatsim.net/ " VA forums: http://linksmanager.com/vatsimvas " The VATSIM Membership Department for email changes, ID or passwords issues " The VATSIM Support Forum for general support for VATSIM pilots These are great places to find answers but you should take a couple of steps before you post a question: 1. Read all the readme files that came with the software 2. Be sure to read the instructional material, including tutorials and FAQ, found here at the VATSIM Pilot Resource Center 3. Take a few minutes to look through recent posts in forums and newsgroups, search for answers before asking your question.

less