The quick version
- Plan your route, cruise altitude and fuel, usually in SimBrief or a similar tool.
- File the plan on the myVATSIM website, either by filling in the form yourself or by using SimBrief’s prefile link.
- Load your simulator at a parking spot, then connect with your pilot client using exactly the same callsign you filed.
- Call the controller for your clearance, or follow UNICOM procedures if no one is online.
The rest of this guide explains each step and each field so nothing on the form is a mystery.
Before you file: plan the flight
A flight plan is only as good as the planning behind it. Before filing, you should know:
- Departure and arrival airports (ICAO codes such as EGLL or KJFK).
- A valid route between them, ideally one that matches current airways and procedures.
- Cruise altitude or flight level, and cruise true airspeed.
- Estimated time en route and fuel on board.
- An alternate airport for IFR flights.
Most simmers generate this in SimBrief, which is free and produces a route, fuel figures and a full operational flight plan. Little Navmap is a popular free alternative, especially for VFR and general aviation. We compare the options in what’s the best flight planning app.
Make sure the navigation data in your simulator and planning tool is reasonably current, so that the route you file is one your aircraft can actually fly.
Where to file
myVATSIM web form
VATSIM provides a web-based flight plan form on myVATSIM. Log in with your VATSIM account, open the flight plan page, fill in the fields and submit. This is the method every pilot can use regardless of simulator or client.
Prefiling from SimBrief
If you plan in SimBrief, the dispatch page offers an option to prefile with VATSIM. It opens the myVATSIM form with most fields already filled in from your plan. Review everything, particularly the callsign and remarks, before submitting.
From your pilot client
Pilot clients such as vPilot and xPilot include a flight plan button. Depending on the client and version, it either sends you to the web form or lets you load a plan you have already filed. Either way, the plan ends up stored against your account on the network.
The flight plan fields explained
| Field | What to enter |
|---|---|
| Callsign | The callsign you will connect with, e.g. BAW123 for an airline-style flight or a registration like N172SP. It must match your connection. |
| Flight rules | IFR or VFR. |
| Aircraft type | The ICAO type designator, e.g. A320, B738, C172. |
| Equipment / capability | Codes describing your navigation and surveillance equipment. SimBrief fills these in; if filing by hand, use the codes your aircraft genuinely supports. |
| Departure and arrival | ICAO airport codes. |
| Alternate | An alternate airport for IFR flights. |
| Departure time | Estimated off-block or departure time in UTC (Zulu), not local time. |
| Cruise altitude | E.g. FL350 or 35000 for IFR; a sensible VFR altitude for VFR flights. |
| Cruise speed | True airspeed in knots, or a Mach number where the form allows it. |
| Route | The airways and waypoints between departure and arrival, e.g. DCT ABC UL9 XYZ. |
| Time en route / fuel | Estimated flight time and fuel endurance in hours and minutes. |
| Remarks | Free text for controllers. Note your voice capability and anything they should know. |
Voice capability. VATSIM traditionally uses tags in the remarks to tell controllers how you will communicate: /v/ for voice, /r/ for receive voice but reply by text, and /t/ for text only. Some forms set this with a dropdown instead.
New to the network? It is common and welcome to add a remark such as NEW TO VATSIM or FIRST FLIGHT. Controllers often slow down and explain more when they see it.
Filing a VFR flight plan
VFR flight plans are simpler. Set flight rules to VFR, enter a realistic VFR cruising altitude, and use the route field to describe where you intend to fly, such as visual reporting points or a short description of your route. Use the remarks to mention anything unusual, like pattern work or sightseeing.
VFR flights are welcome on VATSIM. Some regions have specific procedures for VFR traffic in controlled airspace, so it is worth checking the local division’s pilot pages for busier areas.
After filing: connecting and getting your clearance
Once the plan is filed, load your aircraft at a gate or parking spot (never on a runway or taxiway) and connect with your pilot client using the same callsign. Controllers will see your plan alongside your aircraft.
If a clearance delivery, ground or tower controller covers your airport, call them for your clearance. If only a higher-level controller is online, they may provide service for your departure airport too. If no one is online, monitor and announce on UNICOM. Our guide on connecting MSFS to VATSIM with vPilot covers the connection process, and VATSIM radio phraseology for beginners gives example calls for requesting and reading back a clearance.
Changing or cancelling a flight plan
If you need to change something before departure, you can usually edit and refile the plan through myVATSIM. If you are already talking to a controller, tell them about the change on frequency as well, because they may already be working with the original version. Once airborne, route or altitude changes should be requested from ATC rather than silently amended.
Common mistakes
- Callsign mismatch. If the callsign you connect with differs from the one you filed, controllers will not see your plan.
- Local time instead of UTC. All times on VATSIM are in UTC.
- Unflyable routes. A route copied from an old source may use airways or waypoints that no longer exist in your navigation data. Generate a fresh route when you can.
- Unrealistic altitudes. Check that your cruise level suits your direction of flight and your aircraft’s performance.
- Missing voice tag. Controllers may assume text-only if your capability is unclear.
- Connecting first, filing later without care. It works, but you may need to refresh the plan in your client before ATC sees it.
Is VATSIM real time?
Yes. VATSIM runs in real time: other pilots are flying at the same moment you are, and controllers are working live. Your filed departure time is an estimate in UTC, and leaving a little early or late is normal, but the network itself does not pause or speed up. For the same reason, you should not use simulation rate acceleration while connected, since it would put you out of step with everyone else.
Filing a flight plan costs nothing; neither does anything else on the network. See is VATSIM free for the full picture.