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

# Your First Connection

> Complete walkthrough for your first flight on VATSIM - choosing an airport, connecting to the network, communicating with ATC, and completing your flight

export const Checklist = ({title, items, icon}) => {
  const [checked, setChecked] = useState(Object.fromEntries(items.map((_, i) => [i, false])));
  const toggle = i => setChecked(prev => ({
    ...prev,
    [i]: !prev[i]
  }));
  const done = Object.values(checked).filter(Boolean).length;
  return <div className="vatsim-checklist">
      <div className="vatsim-checklist-header">
        <div className="vatsim-checklist-title">
          {icon && <span className="vatsim-checklist-icon">{icon}</span>}
          <span>{title}</span>
        </div>
        <span className="vatsim-checklist-count">{done}/{items.length}</span>
      </div>
      <div className="vatsim-checklist-items">
        {items.map((item, i) => <button key={i} className={`vatsim-checklist-item ${checked[i] ? 'checked' : ''}`} onClick={() => toggle(i)}>
            <span className="vatsim-check-box">
              {checked[i] && <span className="vatsim-check-mark">✓</span>}
            </span>
            <span className="vatsim-check-label">{item}</span>
          </button>)}
      </div>
    </div>;
};

export const RadioExchange = ({exchanges, title}) => <div className="radio-exchange">
    {title && <div className="radio-exchange-title">{title}</div>}
    <div className="radio-exchange-body">
      {exchanges.map((ex, i) => <div key={i} className={`radio-line radio-line-${ex.from?.toLowerCase()}`}>
          <span className="radio-tag">{ex.from}</span>
          <span className="radio-msg">{ex.msg}</span>
        </div>)}
    </div>
  </div>;

Your first flight on VATSIM is a milestone. It can feel intimidating at first - talking to real controllers, sharing the airspace with other pilots, and following procedures you may have only read about. But the VATSIM community is welcoming to new members, and with a bit of preparation, your first connection will go smoothly.

This page walks you through every step, from choosing an airport to shutting down at the gate.

## Pre-Connection Checklist

Before you connect to the network, make sure you have everything ready. Preparation is the single most important thing you can do to ensure a good first experience.

<Checklist
  title="Pre-Connection Checklist"
  items={[
"VATSIM account created and P0 orientation completed",
"Pilot client installed and configured",
"Audio device tested and push-to-talk key assigned",
"Flight plan filed via SimBrief or VATSIM prefile",
"Aircraft loaded at a gate (never on a runway or taxiway)",
"Departure and arrival airport charts available"
]}
/>

## Step-by-Step: Your First Flight

<Steps>
  <Step title="Choose a quiet airport">
    For your very first VATSIM flight, avoid the busiest airports on the network. Hubs like EGLL (Heathrow), KJFK (New York JFK), and KLAX (Los Angeles) often have heavy traffic and fast-paced ATC that can overwhelm a new pilot.

    Instead, pick a smaller regional airport or fly during off-peak hours (early morning or late at night in the airport's local time). Use [SimAware](https://simaware.ca) or [VATSpy](https://vatspy.rosscarlson.dev) to check current traffic levels and see which controllers are online.

    Good options for Canadian operations include airports like CYOW (Ottawa), CYHZ (Halifax), or CYWG (Winnipeg) during quieter periods.
  </Step>

  <Step title="File your flight plan">
    ATC needs your flight plan to provide service. The easiest way to file one is through [SimBrief](https://www.simbrief.com):

    1. Enter your departure and arrival airports and aircraft type
    2. Generate the Operational Flight Plan (OFP)
    3. Scroll to the bottom and click **Prefile** next to VATSIM

    Alternatively, you can file directly at [my.vatsim.net](https://my.vatsim.net) under the flight plan section. For your first flight, keep the route simple - a short domestic flight of 1-2 hours is ideal.

    <Tip>
      Add **"RMK/NEW TO VATSIM"** in your flight plan remarks. Controllers will see this note and will be extra patient and helpful with you.
    </Tip>
  </Step>

  <Step title="Load your aircraft at the gate">
    In your flight simulator, spawn at a gate or parking stand at your departure airport. You can start cold and dark (all systems off) or in a ready-for-pushback state, depending on your preference and familiarity with the aircraft.

    <Warning>
      **Never connect to VATSIM while positioned on a runway or active taxiway.** Always start at a gate or parking spot. Appearing suddenly on a runway could conflict with pilots who are landing or departing.
    </Warning>
  </Step>

  <Step title="Connect to the network">
    Open your pilot client (vPilot, xPilot, or Swift) and enter the following:

    * **VATSIM CID** - your numeric ID from registration
    * **Password** - your VATSIM account password
    * **Callsign** - your airline code and flight number (e.g., ACA456) or a general aviation registration (e.g., C-GABC)
    * **Server** - select the server closest to your location for the best connection quality

    Click Connect. Your aircraft is now visible on the network.
  </Step>

  <Step title="Check the ATIS">
    Before contacting any controller, tune to the <Tooltip tip="Automatic Terminal Information Service - a recorded broadcast with current airport conditions">ATIS</Tooltip> frequency to get the current airport information. The ATIS tells you:

    * Active runway(s)
    * Current weather conditions (wind, visibility, altimeter setting)
    * Any special procedures or NOTAMs
    * The current ATIS letter identifier (Alpha, Bravo, Charlie, etc.)

    Note the ATIS letter - you will need to confirm you have the current information when you first contact ATC.
  </Step>

  <Step title="Contact ATC or use UNICOM">
    Check your pilot client to see which ATC positions are online at your airport.

    **If ATC is online:**

    * For IFR flights, contact **Delivery** (callsign ending in \_DEL) to receive your IFR clearance
    * If there is no Delivery, contact **Ground** (callsign ending in \_GND)
    * If only Tower is online, contact **Tower** (callsign ending in \_TWR) - they will handle everything

    Remember that VATSIM uses **top-down coverage**: if only a Center controller is online, they handle all positions below them including Tower and Ground.

    **If no ATC is online:**
    Announce your intentions on <Tooltip tip="The common traffic advisory frequency used when no ATC is online">UNICOM</Tooltip> frequency **122.800 MHz**. No one will respond, but other pilots in the area can hear you and plan accordingly.
  </Step>

  <Step title="Taxi, takeoff, and depart">
    Follow ATC instructions for taxi and takeoff. If no ATC is online, announce your movements on UNICOM and use your best judgment for runway selection based on the wind.

    During departure, follow your filed route. If ATC has given you a SID (Standard Instrument Departure), follow it. If you are unsure about an instruction, ask the controller to clarify.
  </Step>

  <Step title="En route">
    Once airborne and established on your route, the workload drops significantly. If a Center controller is online covering your route, they may have already been handed your information from the departure controller. If not, check in with them on their frequency.

    If no en-route ATC is online, simply fly your route and monitor UNICOM (122.800).
  </Step>

  <Step title="Arrival and approach">
    As you approach your destination, check what ATC is available. If Approach control is online, they will vector you for the arrival and hand you off to Tower for landing. If only Tower is online, contact them when you are approximately 15-20 nautical miles out.

    If no ATC is online, announce your intentions on UNICOM and plan your own approach to the active runway.
  </Step>

  <Step title="Landing and taxi to gate">
    After landing, exit the runway promptly. If Ground control is online, contact them for taxi instructions to your gate. If no ATC is online, announce your taxi on UNICOM and proceed to a gate or parking spot.
  </Step>

  <Step title="Disconnect">
    Once you are parked at your gate with engines shut down, you can disconnect from the network through your pilot client. Congratulations - you have completed your first VATSIM flight.
  </Step>
</Steps>

## Radio Examples

Here are examples of what communication sounds like on VATSIM. Do not worry about memorizing these - they will become natural with practice.

<RadioExchange
  title="UNICOM Departure (No ATC Online)"
  exchanges={[
{ from: "PILOT", msg: "Toronto Pearson traffic, Air Canada 456, taxiing to runway 05 via Alpha, UNICOM." },
{ from: "PILOT", msg: "Toronto Pearson traffic, Air Canada 456, departing runway 05, UNICOM." }
]}
/>

<RadioExchange
  title="Contacting Ground"
  exchanges={[
{ from: "PILOT", msg: "Toronto Ground, Air Canada 456, at gate Charlie 32, ready to taxi with information Bravo." },
{ from: "ATC", msg: "Air Canada 456, Toronto Ground, taxi to runway 05 via Alpha, hold short runway 06L." },
{ from: "PILOT", msg: "Taxi to runway 05 via Alpha, hold short 06L, Air Canada 456." }
]}
/>

## Tips for New Pilots

<Tip>
  If you get confused or miss an instruction, it is perfectly fine to ask ATC to **"say again."** Controllers are accustomed to helping new pilots and will happily repeat themselves. You can also ask them to **"speak slower"** if they are going too fast.
</Tip>

<Tip>
  Your first few flights do not need to be perfect. The VATSIM community is welcoming and everyone started as a beginner. Focus on learning one thing at a time - maybe taxi procedures on your first flight, then IFR clearances on the next, and so on.
</Tip>

<Info>
  If you ever feel overwhelmed during a flight, remember that you can always use **text communication** as a fallback. Type your messages in the pilot client and ATC will respond. This gives you more time to think about what to say.
</Info>

## Next Steps

Now that you have completed your first connection, build on your experience by learning proper radio phraseology and understanding how different ATC positions work together.

<CardGroup cols={2}>
  <Card title="Radio Phraseology" icon="message" href="/vatsim/communication/radio-phraseology">
    Standard calls and readbacks for every phase of flight
  </Card>

  <Card title="ATC Interaction" icon="tower-control" href="/vatsim/communication/atc-interaction">
    ATC positions, handoffs, squawk codes, and scenario walkthroughs
  </Card>
</CardGroup>