vZME Memphis ARTCC
Home Roster
Pilots
Feedback Flight Status Flying in vZME FSX Scenery Links Virtual Airlines
Policies
Privacy Policy Training Field Policy Training Procedures ZME ZFW LOA ZME ZHU LOA ZME ZID LOA ZME ZKC LOA ZME ZTL LOA
Staff
Members
About Us
Login/Join
SSO Login Manual Login Join

Airport Weather

FieldTypeWindAltimeter
KMEM VFR Calm 30.07
KJAN VFR 340@7 30.05
KLIT VFR Calm 30.06
KBNA VFR 360@7G15 30.07
KFSM VFR 030@4 30.03
KHSV VFR 020@11 30.05

Online

Online

Top Controllers

This Week

Name Hours
Scott Cash2.10
Clemens Martin1.56
Cole Ferraro1.18

This Month

Name Hours
Cole Ferraro1.18

Flying in vZME

Arriving Aircraft

  • Please brief for arrival. Review your instrument procedures and become familiar with them while in flight or before flight.
  • Comply with all crossing restrictions on your instrument procedures. If you're unable to comply with a crossing restriction, please promptly notify ATC.
  • If operating text- or receive-only, please navigate first before reading back ATC instructions. Navigation should take first priority. Abbreviated replies for acknowledgment of ATC instructions are encouraged.
  • Please have and brief for the precision approach (ILS) regardless of weather conditions or type of approach in use. If arriving from the northeast or southeast, brief for runway 36R or 18L (depending on landing direction), if inbound from the northwest or southwest, brief for the 36L or 18R approach.
  • Please obtain ATIS information prior to contacting the approach controller. When you are handed off from the center controller to the approach controller, you are not expected to switch right away. Go ahead and obtain the ATIS information quickly and then when you contact the approach controller, advise him you have the letter.
  • Verify integrity of your route of flight via current FAA aeronautical charts and procedures. Don't trust online route generators! If you do notice a discrepancy, notify ATC.
  • If you do not understand an instruction or clearance, please tell ATC you're unable to comply and ask the controller to clarify. Remember, pilots and controllers work as a team.
  • In the event of an accidental or inadvertent disconnect from the VATSIM network, please be cautious about reconnecting to the network.


Departing Aircraft

  • If no amendment was made to your proposed flight plan, readback of only the beacon code is encouraged.
  • At KMEM the following departures are only valid between 0200 - 0600 central time. AUTMN, BINKY, GENEH, GMBUD, GRRIZ, HOTRD, NIKEI, OLEMS. you likly be re-routed if you do file one these.
  • At KMEM the ELVIS departure, please do not file the following transition fixes: NFIVE, EFOUR, STREE, SFOUR, WFOUR, and WFIVE as you will be re-assigned a transition fix. These are only valid between 0200 - 0600 central time.
  • Please brief your departure procedures. This is especially critical as we will be utilizing simultaneous parallel departures. On RNAV departure procedures, verify your first RNAV waypoint. If the local controller notifies you of an incorrect RNAV waypoint in the takeoff clearance, do not takeoff and notify ATC of the discrepancy.
  • If you do not understand an ATC instruction or clearance, please notify ATC that you are unable to comply and ask for clarification. Remember, pilots and controllers work as a team.
  • Please notify ground controller that you have the current ATIS information prior to taxi.
  • In the event of an accidental or inadvertent disconnect from the VATSIM network, please be cautious about reconnecting to the network.
For entertainment purposes only. Do not use for real world purposes. Part of the VATSIM Network.