Sometimes pilots do not do what you want them to do. There are several common pilot errors we see on the network, and so we've included a series of alias commands to help orient pilots in the right direction and provide information about the error in a productive way while also minimizing your own need to deal with the issue. Use these commands with the problem aircraft selected.
.newpilot .msg $aircraft Hello, welcome to VATSIM! We're glad to have you flying with us. It seems you may be having an issue flying on the network. When you get a moment, we recommend you head to the VATSIM Pilot Resource Center (https://my.vatsim.net/learn) to learn more about flying on the network and to our website (https://laartcc.org) to find charts, or learn about local information such as our TEC routes.
.newpilotbusy .msg $aircraft Hello, welcome to VATSIM! We're glad to have you flying with us. It seems you may be having an issue flying on the network. I'm too busy at the moment to help, so I recommend you head to the VATSIM Pilot Resource Center (https://my.vatsim.net/learn) to learn more about flying on the network and to our website (https://laartcc.org) to find charts, or learn about local information such as our TEC routes.
.wrongcallsign .msg $aircraft Hello, it appears you are not using the correct ICAO callsign for your airline. The correct callsign should be $uc($1). When you have a moment, please log back in with the correct callsign.
.badairlinecs .msg $aircraft Hello, it appears you are using an invalid callsign. When operating as an air carrier, you should file and connect as the 3 letter ICAO code and flight number (e.x. AAL123). When you have a moment, please log back in and file with the correct callsign.
.badnovembercs .msg $aircraft Hello, it appears you are using an invalid general aviation callsign. Please connect and/or file using 5 letters in the alphabet if operating under an international callsign (e.x. DEHBG) or a valid November-type callsign (e.x. N12345). Formatting instructions for a valid november callsign can be found at https://www.faa.gov/licenses_certificates/aircraft_certification/aircraft_registry/forming_nnumber
.rwylogin .msg $aircraft Hello, it appears you have logged in while on an active runway. You may be preventing other aircraft from using the runway. Please disconnect, move your aircraft to a parking area, and reconnect. Do not slew your aircraft while still connected. Thank you.
.twylogin .msg $aircraft Hello, it appears you have logged in while on a taxiway. You may be blocking other aircraft from moving. Please disconnect, move your aircraft to a parking area, and reconnect. Do not slew your aircraft while still connected. Thank you.
.charts .msg $aircraft Charts for your airport can be found at skyvector.com/airport/$1 . We recommend having charts on board to avoid improperly flying procedures you have been assigned by ATC.
.stepping Please be mindful of stepping on other aircraft. When the frequency is busy everyone is delayed when transmissions need to be repeated. Please listen for your callsign and respond in a timely manner. If you hear a transmission for another aircraft, wait until there is sufficient frequency time for you to make a request. If you are on the ground or requesting a clearance you can expect delays. Multiple attempts to request a clearance only delay everyone further. Thank you.
.xplane .msg $aircraft Hello, it appears as though your simulation rate is slower than 1x. This is a known issue in X-Plane, which reduces the simulation rate whenever framerate drops below 20 fps. This causes issues for controllers attempting to merge you in with other traffic. To solve the problem, we recommend lowering your graphics settings and/or installing the free autospeed plugin (http://forums.x-plane.org/index.php?/files/file/26517-autospeed/). For now, if you are unable to maintain a normal simulation rate, please disconnect from the network. Thank you.
.vectorsid The departure procedure on which you were cleared contains a vector segment, which specifies a heading to fly until given further instructions by ATC. It appears that instead of following the published procedure, you turned before receiving ATC instructions. In the future, please familiarize yourself with the charted procedure prior to departure. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.sidtransition Hello, it appears that you've flown directly from the ending of the common route on your departure to the transition fix. Please note that there are additional fixes between the ending of the common route and the transition. In the future, when programming your FMC, please ensure that you have selected the appropriate transition for your departure.
.rightorcka.msg $aircraft After the first waypoint, the ORCKA departure procedure contains a vector segment, which specifies a heading to fly (236 from runways 25L/R or 251 from runways 24L/R) until given further instructions by ATC. These will almost always include a left turn to the KLIPR waypoint to resume the departure. It appears that you instead turned right without receiving any ATC instructions, which put you close to the Santa Monica Mountains and directly in the path of Los Angeles arrivals from the north. In the future, please familiarize yourself with the charted procedure prior to departure. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.leftorcka .msg $aircraft After the first waypoint, the ORCKA departure procedure contains a vector segment, which specifies a heading to fly (236 from runways 25L/R or 251 from runways 24L/R) until given further instructions by ATC. These are called "Vector Segments" and are often displayed in the FMC as "VECTOR" or "DISCONTINUITY." You MUST leave them in place. In the future, please familiarize yourself with the charted procedure prior to departure. You can review our article about this procedure, here: https://laartcc.org/article/left-turn-orcka. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.roppr It appears you have not complied with the altitude restriction at ROPPR (at or below 7,000). The "climb via SID" instruction requires you to comply with all charted altitude restrictions. The restriction here is critical because at this location, arriving aircraft cross overhead at 8,000. In the future, please familiarize yourself with the charted procedure and verify that all altitude restrictions are correctly programmed in the FMS prior to departure. It is also a good idea to set the altitude selector on the autopilot to 7,000 until after ROPPR. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.vectorstar The arrival procedure on which you were cleared ends with a vector segment, which specifies a heading to fly until given further instructions by ATC. It appears that instead of following the published procedure, you turned before receiving ATC instructions. In the future, please familiarize yourself with the charted procedure prior to beginning the arrival. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.startransition Hello, it appears that you've flown directly to a fix on your arrival procedure that is a part of the common routing. Please note that the arrival you are flying has published transitions. If you were routed via one by ATC or as part of your original filed flight plan, be sure to select the appropriate arrival transition in your FMC.
.apptransition .msg $aircraft Hello, it appears that you've flown directly to a fix on your approach procedure without first flying the assigned transition. Be sure to select the appropriate arrival transition in your FMC going forward.
.dcthunda .msg $aircraft It appears as though you have flown direct to HUNDA after passing CRCUS (if you are on the ANJLL arrival) or SEAVU (if you are on the HLYWD or SEAVU arrival). Please note that after being cleared for an approach from either of these arrivals, you should select and fly the appropriate transition onto the approach. Both CRCUS and SEAVU should be listed as approach transitions in the FMC of the aircraft you are flying. A helpful arrival helper card can be found at https://laartcc.org/uploads/downloads/KLAX_ANJLL_HLYWD_Arrival_Briefing_Card.png. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.dctmerce .msg $aircraft It appears as though you have flown direct to MERCE after passing CRCUS (if you are on the ANJLL arrival) or SEAVU (if you are on the HLYWD or SEAVU arrival). Please note that after being cleared for an approach from either of these arrivals, you should select and fly the appropriate transition onto the approach. Both CRCUS and SEAVU should be listed as approach transitions in the FMC of the aircraft you are flying. A helpful arrival helper card can be found at https://laartcc.org/uploads/downloads/KLAX_ANJLL_HLYWD_Arrival_Briefing_Card.png. Charts can be found at https://skyvector.com, https://www.airnav.com, or https://laartcc.org. Thank you.
.berbn .msg $aircraft Hello, it appears you have either gone direct HUXAR or have not selected the BERBN transition on the ILS Y 26L approach. Please note that after being cleared for an approach from BERBN, you must select and fly the appropriate transition onto the approach. BERBN should be listed as the ONLY transition listed in the FMC for the ILS Y 26L approach. The following reference are quick animated tutorials on how to successfully load the transition. | Boeing: https://gyazo.com/f5c8dff0d8968763b77e4e5b5e2f2bb2 | Removing the vector segment (ONLY AFTER CLEARED FOR THE APPROACH): https://gyazo.com/e10eb60911f009dafddb0291a26b98df | Airbus: https://gyazo.com/c82ddc81f1d57857be9b6265e4035be8