> ## Documentation Index
> Fetch the complete documentation index at: https://docs.canadava.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Flight Planning

> How to file flight plans on VATSIM using SimBrief, manual prefile, and in-client filing - including callsign format, equipment codes, and remarks

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

<Tabs>
  <Tab title="SimBrief (Recommended)">
    SimBrief is the easiest and most complete way to file a flight plan on VATSIM. It calculates your fuel, generates a full route, accounts for weather, and can prefile directly to the network.

    <Steps>
      <Step title="Go to SimBrief">
        Visit [simbrief.com](https://www.simbrief.com) and log in to your account. If you do not have one, registration is free.
      </Step>

      <Step title="Enter your flight details">
        Fill in your departure airport, arrival airport, alternate airport, and aircraft type. SimBrief will suggest routes based on real-world flight data.
      </Step>

      <Step title="Generate the OFP">
        Click **Generate Flight** to create your Operational Flight Plan (OFP). SimBrief calculates fuel requirements, optimal altitude, estimated flight time, and a detailed route with waypoints and airways.
      </Step>

      <Step title="Prefile to VATSIM">
        Scroll to the bottom of the generated OFP page. Under the **Prefile on a Network** section, click the **Prefile** button next to VATSIM. This automatically submits your flight plan to the VATSIM servers.
      </Step>
    </Steps>

    <Tip>
      If you have linked your SimBrief account through the [SimBrief integration](/essentials/simbrief-integration), your booked flight details will auto-populate when you generate a flight plan. This saves time and ensures your callsign, route, and aircraft type all match your booking.
    </Tip>

    SimBrief handles all the technical details - equipment codes, performance data, fuel calculations, and route optimization. For most pilots, this is the only flight planning tool you will ever need.

    <Tip>
      Once you have your route, you will need charts to fly the assigned SID and approach. See the [Charts and Plates](/vatsim/resources/charts) guide for free and paid chart sources.
    </Tip>
  </Tab>

  <Tab title="VATSIM Prefile">
    You can file a flight plan manually through the VATSIM member portal.

    <Steps>
      <Step title="Log in to the VATSIM portal">
        Go to [my.vatsim.net](https://my.vatsim.net) and sign in with your VATSIM credentials.
      </Step>

      <Step title="Navigate to the flight plan section">
        Find the flight plan filing area in your member dashboard.
      </Step>

      <Step title="Fill in all required fields">
        Enter your callsign, aircraft type, departure and arrival airports, route, cruise altitude, and other required information. See the flight plan fields table below for details on each field.
      </Step>

      <Step title="Submit the flight plan">
        Click Submit. Your flight plan will become active on the network when you connect with a matching callsign.
      </Step>
    </Steps>

    This method requires you to know your route, altitude, and equipment codes. It is useful when you want full manual control over your flight plan or when SimBrief is unavailable.
  </Tab>

  <Tab title="In-Client Filing">
    Some pilot clients allow you to file a flight plan directly from within the application.

    * **vPilot** includes a built-in flight plan form accessible from the main window
    * **xPilot** provides a flight plan dialog under the Flight Plan menu

    In-client filing is convenient for simple flights but offers less detail than SimBrief. You will need to enter your route, altitude, and other information manually. This method works well for short VFR flights or when you already know your route from a previous flight.
  </Tab>
</Tabs>

## Flight Plan Fields

| Field                | Description                                                  | Example              |
| -------------------- | ------------------------------------------------------------ | -------------------- |
| **Callsign**         | ICAO airline code + flight number, or GA registration        | ACA456               |
| **Aircraft Type**    | ICAO type designator for your aircraft                       | A320                 |
| **Equipment Suffix** | Navigation and communication capability code                 | /L                   |
| **Departure**        | ICAO code of your departure airport                          | CYYZ                 |
| **Arrival**          | ICAO code of your destination airport                        | CYUL                 |
| **Alternate**        | ICAO code of your backup airport in case of diversion        | CYOW                 |
| **Cruise Altitude**  | Your planned cruising altitude as a flight level or altitude | FL350                |
| **True Airspeed**    | Planned cruise speed in knots                                | 460                  |
| **Route**            | Waypoints and airways from departure to arrival              | DEDKI3 AVSEP DCT YOW |
| **Remarks**          | Additional information for ATC and the network               | RMK/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.

| Suffix | Equipment                | Typical Aircraft                                              |
| ------ | ------------------------ | ------------------------------------------------------------- |
| **/L** | ILS, VOR, GPS (RNAV)     | Most modern airliners (A320, 737, etc.)                       |
| **/G** | GPS only (RNAV)          | GPS-equipped GA and regional aircraft                         |
| **/R** | RNAV with RNP capability | Advanced airliners with RNP approach capability               |
| **/W** | RVSM-capable with RNAV   | Aircraft approved for Reduced Vertical Separation above FL290 |
| **/A** | DME, VOR only            | Older aircraft without GPS                                    |
| **/T** | DME, VOR, ILS            | Older aircraft with ILS but no GPS                            |

<Tip>
  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.
</Tip>

## 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:

| Remark                | Purpose                                                                                            |
| --------------------- | -------------------------------------------------------------------------------------------------- |
| **RMK/NEW TO VATSIM** | Tells controllers you are a new pilot. They will be extra patient and provide additional guidance. |
| **RMK/TCAS**          | Indicates 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/SIMBRIEF**      | Indicates the flight plan was generated by SimBrief. Informational only.                           |

You can combine multiple remarks. For example: `RMK/TCAS SIMBRIEF NEW TO VATSIM`

<Note>
  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.
</Note>

<Tip>
  For a more detailed guide on setting up SimBrief, see the [SimBrief Integration](/essentials/simbrief-integration) page.
</Tip>