Skip to main content
A flight plan is your roadmap on the VATSIM network. It tells ATC where you are going, what route you intend to fly, what altitude you want, and what aircraft you are using. Without a flight plan, controllers cannot provide you with proper service - and for IFR flights, filing one is effectively mandatory.

Callsign Format

Your callsign on VATSIM follows the ICAO airline format: ICAO airline code + flight number (e.g., ACA456 for Air Canada flight 456) The ICAO code identifies the airline and the flight number identifies your specific flight. Controllers will address you using the airline telephony designator - for example, “Air Canada 456” for callsign ACA456. For general aviation flights, use a registration-style callsign such as C-GABC.

Filing Methods

Flight Plan Fields

FieldDescriptionExample
CallsignICAO airline code + flight number, or GA registrationACA456
Aircraft TypeICAO type designator for your aircraftA320
Equipment SuffixNavigation and communication capability code/L
DepartureICAO code of your departure airportCYYZ
ArrivalICAO code of your destination airportCYUL
AlternateICAO code of your backup airport in case of diversionCYOW
Cruise AltitudeYour planned cruising altitude as a flight level or altitudeFL350
True AirspeedPlanned cruise speed in knots460
RouteWaypoints and airways from departure to arrivalDEDKI3 AVSEP DCT YOW
RemarksAdditional information for ATC and the networkRMK/TCAS SIMBRIEF

Equipment Suffix Codes

The equipment suffix tells ATC what navigation equipment your aircraft has. This affects the types of approaches and routes ATC can assign to you.
SuffixEquipmentTypical Aircraft
/LILS, VOR, GPS (RNAV)Most modern airliners (A320, 737, etc.)
/GGPS only (RNAV)GPS-equipped GA and regional aircraft
/RRNAV with RNP capabilityAdvanced airliners with RNP approach capability
/WRVSM-capable with RNAVAircraft approved for Reduced Vertical Separation above FL290
/ADME, VOR onlyOlder aircraft without GPS
/TDME, VOR, ILSOlder aircraft with ILS but no GPS
If you are unsure which suffix to use, /L is the safe default for any modern airliner or aircraft with GPS and ILS capability. SimBrief will automatically select the correct suffix when you generate a flight plan.

Remarks Field Best Practices

The remarks field is where you add supplementary information that does not fit into the standard fields. Here are the most common entries:
RemarkPurpose
RMK/NEW TO VATSIMTells controllers you are a new pilot. They will be extra patient and provide additional guidance.
RMK/TCASIndicates your aircraft has a Traffic Collision Avoidance System. Standard for airliners.
V/Voice capable - you can communicate by voice (this is the default assumption).
T/Text only - you cannot use voice and will communicate via text messages.
R/Receive only - you can hear voice transmissions but will respond via text.
RMK/SIMBRIEFIndicates the flight plan was generated by SimBrief. Informational only.
You can combine multiple remarks. For example: RMK/TCAS SIMBRIEF NEW TO VATSIM
Your flight plan becomes active on the network when you connect with a matching callsign. If you change your callsign after filing, you will need to refile your flight plan with the new callsign. The system matches flight plans to connections by callsign.
For a more detailed guide on setting up SimBrief, see the SimBrief Integration page.