<section id="1.1-introduction">
<h1><a class="header-anchor" href="#1.1-introduction"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1.1 Introduction</h1>
<section class="reference"></section>
<section id="1.1.1">
<h3><a class="header-anchor" href="#1.1.1">1.1.1</a></h3>
<section class="reference">
<p>Welcome to the Infinite Flight Air Traffic Controller (IFATC) Manual. It is designed to help new entrants and current Controllers with IFATC procedures, as well as cover the fundamental principles associated with all controlling facilities on Infinite Flight. <strong class="red">All Controllers are expected to familiarize themselves with this manual and continue to do so during their time with IFATC.</strong></p>
</section>
</section>
<section id="1.1.2">
<h3><a class="header-anchor" href="#1.1.2">1.1.2</a></h3>
<section class="reference">
<p>The <a href="/guide" class="documentation-content-link">Infinite Flight User Guide</a>, <a href="https://community.infiniteflight.com/" class="documentation-content-link">IFC Forum</a> and <a href="https://www.faa.gov/regulations_policies/orders_notices/index.cfm/go/document.current/documentnumber/7110.65" class="documentation-content-link">FAA 7110.65</a> are additional tools that Controllers <strong class="red">should</strong> utilize. In addition, a Controller directory, stats and the home of recruitment &amp; training can all be found at <a href="https://www.if-atc.com" class="documentation-content-link">https://www.if-atc.com</a>.</p>
</section>
</section>
<section id="1.1.3">
<h3><a class="header-anchor" href="#1.1.3">1.1.3</a></h3>
<section class="reference">
<p>Feedback is an essential part in the development &amp; upkeep of the ATC Manual and can be submitted using the <a href="https://docs.google.com/forms/d/e/1FAIpQLSewldULDy_GDkPRhZ8sVyyNYTvn5rdYsUpsH-6v2st7xRPI2Q/viewform" class="documentation-content-link">Report Form</a>. Please ensure that you have checked the <a href="https://docs.google.com/spreadsheets/d/1AfYV50T3Wn25nMPsaxEE1Jj50UTDyjPsma0d80CU0RY/edit?usp=sharing" class="documentation-content-link">Feedback Status Spreadsheet</a> <strong class="red">BEFORE</strong> submitting a new report to avoid duplicates (you can also check the progress of any reports that you have made using this). Any questions <strong class="red">should</strong> be sent to the Technical Writer (@RAH) via the IFC or the IFATC Discord.</p>
</section>
</section>
<section id="1.1.4">
<h3><a class="header-anchor" href="#1.1.4">1.1.4</a></h3>
<section class="reference">
<p>A site designed by one of our Controllers and dedicated to help with controlling can be found at <a href="https://www.ifatc.org/" class="documentation-content-link">https://www.ifatc.org/</a>. The features are extensive and updated regularly, thus are not covered within this manual but Controllers <strong class="red">should</strong> utilize the tools this site offers.</p>
</section>
</section>
<section id="1.1.5">
<h3><a class="header-anchor" href="#1.1.5">1.1.5</a></h3>
<section class="reference">
<p>All abbreviations contained within this manual are listed below with their associated definition:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Abbreviation</th>
<th>Definition</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Abbreviation">AAL</td>
<td data-label="Definition">Above Aerodrome Level</td>
</tr>
<tr>
<td data-label="Abbreviation">AGL</td>
<td data-label="Definition">Above Ground Level</td>
</tr>
<tr>
<td data-label="Abbreviation">Alt</td>
<td data-label="Definition">Altitude</td>
</tr>
<tr>
<td data-label="Abbreviation">ATC</td>
<td data-label="Definition">Air Traffic Control</td>
</tr>
<tr>
<td data-label="Abbreviation">ATIS</td>
<td data-label="Definition">Automatic Terminal Information Service</td>
</tr>
<tr>
<td data-label="Abbreviation">DM</td>
<td data-label="Definition">Direct Message</td>
</tr>
<tr>
<td data-label="Abbreviation">FAA</td>
<td data-label="Definition">Federal Aviation Administration</td>
</tr>
<tr>
<td data-label="Abbreviation">FF</td>
<td data-label="Definition">Flight Following</td>
</tr>
<tr>
<td data-label="Abbreviation">FNF</td>
<td data-label="Definition">Friday Night Flight</td>
</tr>
<tr>
<td data-label="Abbreviation">FPL</td>
<td data-label="Definition">Flight Plan</td>
</tr>
<tr>
<td data-label="Abbreviation">Ft</td>
<td data-label="Definition">Feet</td>
</tr>
<tr>
<td data-label="Abbreviation">GMT</td>
<td data-label="Definition">Greenwich Mean Time</td>
</tr>
<tr>
<td data-label="Abbreviation">GPS</td>
<td data-label="Definition">Global Positioning System</td>
</tr>
<tr>
<td data-label="Abbreviation">GA</td>
<td data-label="Definition">General Aviation</td>
</tr>
<tr>
<td data-label="Abbreviation">G/A</td>
<td data-label="Definition">Go-Around</td>
</tr>
<tr>
<td data-label="Abbreviation">GS</td>
<td data-label="Definition">Groundspeed</td>
</tr>
<tr>
<td data-label="Abbreviation">G/S</td>
<td data-label="Definition">Glideslope</td>
</tr>
<tr>
<td data-label="Abbreviation">HWC</td>
<td data-label="Definition">Headwind Component</td>
</tr>
<tr>
<td data-label="Abbreviation">KIAS</td>
<td data-label="Definition">Knots Indicated Airspeed</td>
</tr>
<tr>
<td data-label="Abbreviation">IAS</td>
<td data-label="Definition">Indicated  Airspeed</td>
</tr>
<tr>
<td data-label="Abbreviation">ICAO</td>
<td data-label="Definition">International Civil Aviation Organization</td>
</tr>
<tr>
<td data-label="Abbreviation">IFATC</td>
<td data-label="Definition">Infinite Flight Air Traffic Controllers</td>
</tr>
<tr>
<td data-label="Abbreviation">IF</td>
<td data-label="Definition">Infinite Flight</td>
</tr>
<tr>
<td data-label="Abbreviation">IFC</td>
<td data-label="Definition">Infinite Flight Community</td>
</tr>
<tr>
<td data-label="Abbreviation">IFFG</td>
<td data-label="Definition">Infinite Flight Fan Group</td>
</tr>
<tr>
<td data-label="Abbreviation">IFR</td>
<td data-label="Definition">Instrument Flight Rules</td>
</tr>
<tr>
<td data-label="Abbreviation">ILS</td>
<td data-label="Definition">Instrument Landing System</td>
</tr>
<tr>
<td data-label="Abbreviation">IRL</td>
<td data-label="Definition">In Real Life</td>
</tr>
<tr>
<td data-label="Abbreviation">Kts</td>
<td data-label="Definition">Knots</td>
</tr>
<tr>
<td data-label="Abbreviation">LLC</td>
<td data-label="Definition">Limited Liability Company</td>
</tr>
<tr>
<td data-label="Abbreviation">LOC</td>
<td data-label="Definition">Localizer</td>
</tr>
<tr>
<td data-label="Abbreviation">LUAW</td>
<td data-label="Definition">Line Up And Wait</td>
</tr>
<tr>
<td data-label="Abbreviation">METAR</td>
<td data-label="Definition">Meteorological Aerodrome Report</td>
</tr>
<tr>
<td data-label="Abbreviation">MSA</td>
<td data-label="Definition">Minimum Sector Altitude</td>
</tr>
<tr>
<td data-label="Abbreviation">Nm</td>
<td data-label="Definition">Nautical Mile</td>
</tr>
<tr>
<td data-label="Abbreviation">NOTAMS</td>
<td data-label="Definition">Notification to Airmen</td>
</tr>
<tr>
<td data-label="Abbreviation">RET</td>
<td data-label="Definition">Rapid Exit Taxiway</td>
</tr>
<tr>
<td data-label="Abbreviation">RV</td>
<td data-label="Definition">Radar Vectors</td>
</tr>
<tr>
<td data-label="Abbreviation">RWY</td>
<td data-label="Definition">Runway</td>
</tr>
<tr>
<td data-label="Abbreviation">SID</td>
<td data-label="Definition">Standard Instrument Departure</td>
</tr>
<tr>
<td data-label="Abbreviation">STAR</td>
<td data-label="Definition">Standard Terminal Arrival Route</td>
</tr>
<tr>
<td data-label="Abbreviation">TAF</td>
<td data-label="Definition">Terminal Aerodrome Forecast</td>
</tr>
<tr>
<td data-label="Abbreviation">TOD</td>
<td data-label="Definition">Top of Descent</td>
</tr>
<tr>
<td data-label="Abbreviation">TWC</td>
<td data-label="Definition">Tailwind Component</td>
</tr>
<tr>
<td data-label="Abbreviation">UFN</td>
<td data-label="Definition">Until Further Notice</td>
</tr>
<tr>
<td data-label="Abbreviation">UTC</td>
<td data-label="Definition">Coordinated Universal Time</td>
</tr>
<tr>
<td data-label="Abbreviation">VARB</td>
<td data-label="Definition">Virtual Airline Regulatory Board</td>
</tr>
<tr>
<td data-label="Abbreviation">VC</td>
<td data-label="Definition">Voice Channel</td>
</tr>
<tr>
<td data-label="Abbreviation">VFR</td>
<td data-label="Definition">Visual Flight Rules</td>
</tr>
<tr>
<td data-label="Abbreviation">VIS</td>
<td data-label="Definition">Visual</td>
</tr>
<tr>
<td data-label="Abbreviation">VMC</td>
<td data-label="Definition">Visual Meteorological Conditions</td>
</tr>
<tr>
<td data-label="Abbreviation">VNAV</td>
<td data-label="Definition">Vertical Navigation</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


1.1 Introduction
1.1.1
Welcome to the Infinite Flight Air Traffic Controller (IFATC) Manual. It is designed to help new entrants and current Controllers with IFATC procedures, as well as cover the fundamental principles associated with all controlling facilities on Infinite Flight. All Controllers are expected to familiarize themselves with this manual and continue to do so during their time with IFATC.{.red}
1.1.2
The Infinite Flight User Guide, IFC Forum and FAA 7110.65 are additional tools that Controllers should{.red} utilize. In addition, a Controller directory, stats and the home of recruitment & training can all be found at https://www.if-atc.com.
1.1.3
Feedback is an essential part in the development & upkeep of the ATC Manual and can be submitted using the Report Form. Please ensure that you have checked the Feedback Status Spreadsheet BEFORE{.red} submitting a new report to avoid duplicates (you can also check the progress of any reports that you have made using this). Any questions should{.red} be sent to the Technical Writer (@RAH) via the IFC or the IFATC Discord.
1.1.4
A site designed by one of our Controllers and dedicated to help with controlling can be found at https://www.ifatc.org/. The features are extensive and updated regularly, thus are not covered within this manual but Controllers should{.red} utilize the tools this site offers.
1.1.5
All abbreviations contained within this manual are listed below with their associated definition:
| Abbreviation | Definition                                |
| ------------ | ----------------------------------------- |
| AAL          | Above Aerodrome Level                     |
| AGL          | Above Ground Level                        |
| Alt          | Altitude                                  |
| ATC          | Air Traffic Control                       |
| ATIS         | Automatic Terminal Information Service    |
| DM           | Direct Message                            |
| FAA          | Federal Aviation Administration           |
| FF           | Flight Following                          |
| FNF          | Friday Night Flight                       |
| FPL          | Flight Plan                               |
| Ft           | Feet                                      |
| GMT          | Greenwich Mean Time                       |
| GPS          | Global Positioning System                 |
| GA           | General Aviation                          |
| G/A          | Go-Around                                 |
| GS           | Groundspeed                               |
| G/S          | Glideslope                                |
| HWC          | Headwind Component                        |
| KIAS         | Knots Indicated Airspeed                  |
| IAS          | Indicated  Airspeed                       |
| ICAO         | International Civil Aviation Organization |
| IFATC        | Infinite Flight Air Traffic Controllers   |
| IF           | Infinite Flight                           |
| IFC          | Infinite Flight Community                 |
| IFFG         | Infinite Flight Fan Group                 |
| IFR          | Instrument Flight Rules                   |
| ILS          | Instrument Landing System                 |
| IRL          | In Real Life                              |
| Kts          | Knots                                     |
| LLC          | Limited Liability Company                 |
| LOC          | Localizer                                 |
| LUAW         | Line Up And Wait                          |
| METAR        | Meteorological Aerodrome Report           |
| MSA          | Minimum Sector Altitude                   |
| Nm           | Nautical Mile                             |
| NOTAMS       | Notification to Airmen                    |
| RET          | Rapid Exit Taxiway                        |
| RV           | Radar Vectors                             |
| RWY          | Runway                                    |
| SID          | Standard Instrument Departure             |
| STAR         | Standard Terminal Arrival Route           |
| TAF          | Terminal Aerodrome Forecast               |
| TOD          | Top of Descent                            |
| TWC          | Tailwind Component                        |
| UFN          | Until Further Notice                      |
| UTC          | Coordinated Universal Time                |
| VARB         | Virtual Airline Regulatory Board          |
| VC           | Voice Channel                             |
| VFR          | Visual Flight Rules                       |
| VIS          | Visual                                    |
| VMC          | Visual Meteorological Conditions          |
| VNAV         | Vertical Navigation                       |

1.1 Introduction

<section id="1a.1-discord-communication-guidelines">
<h1><a class="header-anchor" href="#1a.1-discord-communication-guidelines"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.1  Discord Communication Guidelines</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Infinite Flight app related issues can be discussed within the IFATC Discord Channels for advice; however, for official support, the <a href="https://community.infiniteflight.com/c/support/17" class="documentation-content-link">IFC Forum</a> <strong class="red">must</strong> be used. Preferential support is not provided to IFATC.</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="general">
<h2><a class="header-anchor" href="#general"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> General</h2>
<section class="reference"></section>
<section id="1a.1.1">
<h3><a class="header-anchor" href="#1a.1.1">1A.1.1</a></h3>
<section class="reference">
<p>Discord is a messenger app for teams to make work simpler, more pleasant and more productive. More information on how this app works can be found <a href="https://support.discord.com/hc/en-us" class="documentation-content-link">here</a>.</p>
</section>
</section>
<section id="1a.1.2">
<h3><a class="header-anchor" href="#1a.1.2">1A.1.2</a></h3>
<section class="reference">
<p>Group chats are authorized as long as they do not diminish effectiveness of primary channels. Controllers are encouraged to utilize group messages for specific interest groups amongst Controllers. Discord rules will be enforced if an issue is brought to the attention of a Supervisor or above.</p>
</section>
</section>
<section id="1a.1.3">
<h3><a class="header-anchor" href="#1a.1.3">1A.1.3</a></h3>
<section class="reference">
<p>The channels and their use is outlined in the table below:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th style="text-align:left">Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#announcements</td>
<td data-label="Purpose">Official Infinite Flight updates (such as new blog update, new version of the ATC Manual, Beta information etc) to be made in this channel by the ATC Manager, Staff and Moderators only. Controllers <strong class="red">must not</strong> reply to any material posted in this channel so that all Controllers can be reached effectively.</td>
</tr>
<tr>
<td data-label="Channel">#botcommands</td>
<td data-label="Purpose">All bot commands <strong class="red">should</strong> only be used in this channel. <em>!command</em> can be typed in this channel to bring up a list of available commands for use <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.1-discord-communication-guidelines#1a.1.4" class="documentation-content-link">1A.1.4</a> below)</em></td>
</tr>
<tr>
<td data-label="Channel">#controllers</td>
<td data-label="Purpose">All normal Controller communications to occur in this channel. This channel <strong class="red">should not</strong> be used unless <strong class="red">ACTIVELY</strong> controlling.</td>
</tr>
<tr>
<td data-label="Channel">#controlling[1-5]</td>
<td data-label="Purpose">Voice Channels specifically available for Controllers that are <strong>ACTIVELY</strong> controlling <em>(for further guidance see <a href="/guide/atc-manual/1a.-new-entrants/1a.1-discord-communication-guidelines#1a.1.5" class="documentation-content-link">1A.1.5</a> and <a href="/guide/atc-manual/1a.-new-entrants/1a.2-general-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em></td>
</tr>
<tr>
<td data-label="Channel">#discussions</td>
<td data-label="Purpose">This is a channel for active Controllers to engage in discussion regarding IFATC, ATC, Infinite Flight, and Aviation. Controllers that are <strong>CURRENTLY</strong> open <strong class="red">should not</strong> be conversing in this channel unless operationally critical.</td>
</tr>
<tr>
<td data-label="Channel">#flights</td>
<td data-label="Purpose">This channel will be used for Controllers to coordinate group flights together. All coordination <strong class="red">should</strong> remain in this channel.</td>
</tr>
<tr>
<td data-label="Channel">#ifatceg</td>
<td data-label="Purpose">This channel contains news, tips and more brought to you by the IFATC Education Group</td>
</tr>
<tr>
<td data-label="Channel">#infinite-flight-rules</td>
<td data-label="Purpose">Highlights where to find the rules of the IFATC Discord server.</td>
</tr>
<tr>
<td data-label="Channel">#offtopic</td>
<td data-label="Purpose">This is a channel to discuss things unrelated to IFATC or Infinite Flight. All conversations <strong class="red">should</strong> remain appropriate. <em>#offtopic</em> is a privilege and all members are subject to removal at any time if misused. This is for active members only.</td>
</tr>
<tr>
<td data-label="Channel">#readonly</td>
<td data-label="Purpose">Day to day posts (such as housekeeping, schedule releases, FNF specific procedures etc) to be made in this channel by the ATC Manager, Staff and Moderators only. Controllers <strong class="red">must not</strong> reply to any material posted in this channel so that all Controllers can be reached effectively.</td>
</tr>
<tr>
<td data-label="Channel">#role-assignments</td>
<td data-label="Purpose">Within this channel is a &quot;notification opt in&quot; menu - Controllers can react with the corresponding emoji to opt in and when the mentioned phrase is used, the Controller will receive a notification*.</td>
</tr>
<tr>
<td data-label="Channel">#screenshots</td>
<td data-label="Purpose">This is a place to share Infinite Flight screenshots in moderation. No other simulator, games, or off-topic content <strong class="red">must</strong> be shared and all screenshots <strong class="red">should</strong> be of a high quality.</td>
</tr>
<tr>
<td data-label="Channel">#training-time</td>
<td data-label="Purpose">Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in.</td>
</tr>
<tr>
<td data-label="Channel">#training-time[1-3]</td>
<td data-label="Purpose">All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
</tbody>
</table>
<p>*Controllers <strong class="red">should</strong> utilise the <em>#discussions</em> channel and fellow Controllers before using the <em>@sup</em> tag unless discretion is required or the topic is of a sensitive nature. This encourages an open dialogue that other Controllers can benefit from witnessing and/or taking part in. Violation appeals require an Appeals Team member or IFC Moderator <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> below)</em></p>
</section>
</section>
</section>
<section id="bot-commands">
<h2><a class="header-anchor" href="#bot-commands"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Bot Commands</h2>
<section class="reference"></section>
<section id="1a.1.4">
<h3><a class="header-anchor" href="#1a.1.4">1A.1.4</a></h3>
<section class="reference">
<p>Below are some of the commands that can be used in the <em>#botcommands</em> channel:</p>
<p><strong>/approve</strong> - shows recruits that need their application approved (for use by Moderators ONLY)</p>
<p><strong>/atc</strong> – shows all open frequencies</p>
<p><strong>/atis[icao]</strong> – shows current ATIS message for that particular airport</p>
<p><strong>!commands</strong> - provides a list of all available commands that can be used</p>
<p><strong>%chart[icao]</strong> - gives you the latest charts of the chosen airport</p>
<p><strong>/checkride</strong> - shows Supervisors who is currently in the Check Ride phase</p>
<p><strong>!feedbackstatus</strong> - check the status any feedback provided for the ATC Manual</p>
<p><strong>/find [search phrase]</strong> – this can be used to find a member of IFATC within Discord</p>
<p><strong>/gmt</strong> – provides the current (local) time in GMT</p>
<p><strong>%icao[icao]</strong> - gives you general information about the chosen airport</p>
<p><strong>!lightaircraft</strong> - &quot;light&quot; aircraft for the purposes of Infinite Flight listed</p>
<p><strong>!manual</strong> - generates a link to the latest version of the ATC Manual</p>
<p><strong>!manualfeedback</strong> - generates a link to the Feedback Form for the ATC Manual</p>
<p><strong>%metar[icao]</strong> - gives you the live METAR of the chosen airport</p>
<p><strong>/mystats</strong> – search for your IFATC statistics</p>
<p><strong>/reference</strong> – provides quick IFATC references, rules and the ATC Manual</p>
<p><strong>/schedule</strong> - shows a list of scheduled training/testing sessions in the next 48 hours</p>
<p><strong>%taf[icao]</strong> - gives you the TAF of the chosen airport</p>
</section>
</section>
</section>
<section id="voice-channels">
<h2><a class="header-anchor" href="#voice-channels"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Voice Channels</h2>
<section class="reference"></section>
<section id="1a.1.5">
<h3><a class="header-anchor" href="#1a.1.5">1A.1.5</a></h3>
<section class="reference">
<p>The use of Voice Channels (VC's) <strong class="red">must</strong> only be used in accordance with the Discord and Discord Voice Channel rules <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.2-general-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em>. Controllers who are operating an airport independently without assistance <strong class="red">should not</strong> claim a VC unless:</p>
<ul>
<li>the control positions are split (e.g. passing Ground control to another member whilst still operating Tower)</li>
<li>a Radar Controller opens at the airport</li>
<li>and/or all facility Controllers opt to communicate via a VC in <em>#controllers</em></li>
</ul>
<p>The use of VC's is <strong class="red">not required</strong> and is at the sole discretion of the IFATC member (there may be select events where the use of VC's is required to guarantee operational efficiency - if this is the case, Controllers that do not wish to use voice may have to control elsewhere).</p>
<p>Controllers who wish to observe others in a VC for educational purposes may <strong class="red">ONLY</strong> do so if <strong class="red">ALL</strong> operational Controllers in the VC have given consent. Observers <strong class="red">must not</strong> distract from the active ATC operation and <strong class="red">should</strong> remain muted.</p>
<p>Below are some useful tips for VC's:</p>
<ul>
<li>You can see how many members currently occupy a VC at any time by noting the [00/08] channel count!</li>
<li>Selecting &quot;Mute&quot; means no one can hear you</li>
<li>Selecting &quot;Deafen&quot; means you don't hear anyone else</li>
<li>Always double check your sound settings (i.e. Input = Mic and Output = Speaker)</li>
<li>Connecting to a VC will act much like a phone call and can run in the background while controlling</li>
</ul>
</section>
</section>
</section>


1A.1  Discord Communication Guidelines
Tip
: Infinite Flight app related issues can be discussed within the IFATC Discord Channels for advice; however, for official support, the IFC Forum must{.red} be used. Preferential support is not provided to IFATC.
General
1A.1.1
Discord is a messenger app for teams to make work simpler, more pleasant and more productive. More information on how this app works can be found here.
1A.1.2
Group chats are authorized as long as they do not diminish effectiveness of primary channels. Controllers are encouraged to utilize group messages for specific interest groups amongst Controllers. Discord rules will be enforced if an issue is brought to the attention of a Supervisor or above.
1A.1.3
 The channels and their use is outlined in the table below:
| Channel                | Purpose                                                      |
| ---------------------- | :----------------------------------------------------------- |
| #announcements         | Official Infinite Flight updates (such as new blog update, new version of the ATC Manual, Beta information etc) to be made in this channel by the ATC Manager, Staff and Moderators only. Controllers must not{.red} reply to any material posted in this channel so that all Controllers can be reached effectively. |
| #botcommands           | All bot commands should{.red} only be used in this channel. !command can be typed in this channel to bring up a list of available commands for use (see 1A.1.4 below) |
| #controllers           | All normal Controller communications to occur in this channel. This channel should not{.red} be used unless ACTIVELY{.red} controlling. |
| #controlling1-5]      | Voice Channels specifically available for Controllers that are ACTIVELY controlling (for further guidance see [1A.1.5 and 1A.2.1 below) |
| #discussions           | This is a channel for active Controllers to engage in discussion regarding IFATC, ATC, Infinite Flight, and Aviation. Controllers that are CURRENTLY open should not{.red} be conversing in this channel unless operationally critical. |
| #flights               | This channel will be used for Controllers to coordinate group flights together. All coordination should{.red} remain in this channel. |
| #ifatceg               | This channel contains news, tips and more brought to you by the IFATC Education Group |
| #infinite-flight-rules | Highlights where to find the rules of the IFATC Discord server. |
| #offtopic              | This is a channel to discuss things unrelated to IFATC or Infinite Flight. All conversations should{.red} remain appropriate. #offtopic is a privilege and all members are subject to removal at any time if misused. This is for active members only. |
| #readonly              | Day to day posts (such as housekeeping, schedule releases, FNF specific procedures etc) to be made in this channel by the ATC Manager, Staff and Moderators only. Controllers must not{.red} reply to any material posted in this channel so that all Controllers can be reached effectively. |
| #role-assignments      | Within this channel is a "notification opt in" menu - Controllers can react with the corresponding emoji to opt in and when the mentioned phrase is used, the Controller will receive a notification*. |
| #screenshots           | This is a place to share Infinite Flight screenshots in moderation. No other simulator, games, or off-topic content must{.red} be shared and all screenshots should{.red} be of a high quality. |
| #training-time         | Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in. |
| #training-time[1-3]    | All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel must{.red} be used at any one time). |
Controllers should{.red} utilise the #discussions* channel and fellow Controllers before using the @sup tag unless discretion is required or the topic is of a sensitive nature. This encourages an open dialogue that other Controllers can benefit from witnessing and/or taking part in. Violation appeals require an Appeals Team member or IFC Moderator (see 1A.3.1 below)
Bot Commands
1A.1.4
Below are some of the commands that can be used in the #botcommands channel:
/approve - shows recruits that need their application approved (for use by Moderators ONLY)
/atc – shows all open frequencies
/atis[icao] – shows current ATIS message for that particular airport
!commands - provides a list of all available commands that can be used
%chart[icao] - gives you the latest charts of the chosen airport
/checkride - shows Supervisors who is currently in the Check Ride phase
!feedbackstatus - check the status any feedback provided for the ATC Manual
/find [search phrase] – this can be used to find a member of IFATC within Discord
/gmt – provides the current (local) time in GMT
%icao[icao] - gives you general information about the chosen airport
!lightaircraft - "light" aircraft for the purposes of Infinite Flight listed
!manual - generates a link to the latest version of the ATC Manual
!manualfeedback - generates a link to the Feedback Form for the ATC Manual
%metar[icao] - gives you the live METAR of the chosen airport
/mystats – search for your IFATC statistics
/reference – provides quick IFATC references, rules and the ATC Manual
/schedule - shows a list of scheduled training/testing sessions in the next 48 hours
%taf[icao] - gives you the TAF of the chosen airport
Voice Channels
1A.1.5
The use of Voice Channels (VC's) must{.red} only be used in accordance with the Discord and Discord Voice Channel rules (see 1A.2.1 below). Controllers who are operating an airport independently without assistance should not{.red} claim a VC unless:
the control positions are split (e.g. passing Ground control to another member whilst still operating Tower)
a Radar Controller opens at the airport
and/or all facility Controllers opt to communicate via a VC in #controllers
The use of VC's is not required{.red} and is at the sole discretion of the IFATC member (there may be select events where the use of VC's is required to guarantee operational efficiency - if this is the case, Controllers that do not wish to use voice may have to control elsewhere).
Controllers who wish to observe others in a VC for educational purposes may ONLY{.red} do so if ALL{.red} operational Controllers in the VC have given consent. Observers must not{.red} distract from the active ATC operation and should{.red} remain muted.
Below are some useful tips for VC's:
You can see how many members currently occupy a VC at any time by noting the [00/08] channel count!
Selecting "Mute" means no one can hear you
Selecting "Deafen" means you don't hear anyone else
Always double check your sound settings (i.e. Input = Mic and Output = Speaker)
Connecting to a VC will act much like a phone call and can run in the background while controlling

1A.1 Discord Communication Guidelines

<section id="1a.2-general-rules">
<h1><a class="header-anchor" href="#1a.2-general-rules"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.2  General Rules</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>All Controllers <strong class="red">must</strong> ensure that their Discord Nickname is either the same as their IFC Username or real name - this means that Controllers can be found easily if required <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.2-general-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="1a.2.1">
<h3><a class="header-anchor" href="#1a.2.1">1A.2.1</a></h3>
<section class="reference">
<p>The following rules <strong class="red">must</strong> be followed at all times:</p>
</section>
</section>
<section id="controlling">
<h2><a class="header-anchor" href="#controlling"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Controlling</h2>
<section class="reference">
<ul>
<li>All Controllers <strong class="red">must</strong> announce in <em>#controllers</em> when opening/closing any frequency on the Expert Server. When closing, a <strong class="red">MINIMUM</strong> of 5 minutes warning and the last ATIS letter used <strong class="red">must</strong> be provided</li>
<li>Controllers <strong class="red">must</strong> control within the bounds* of the ATC Schedule posted every week on the IFC and in <em>#readonly</em> on Discord. The only exception to this is when Controllers are not qualified to do so as per the rank structure <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> below)</em>, in which case a sensible alternative can be selected</li>
<li>Unless otherwise specified in the ATC Schedule, the &quot;region change&quot; occurs at 0600Z (Controllers that are open during a region change <strong class="red">must</strong> still meet the minimum controlling times before closing - <em>see <a href="/guide/atc-manual/1a.-new-entrants/1a.5-activity-requirements#1a.5.2" class="documentation-content-link">1A.5.2</a> below</em>). Controllers <strong class="red">must not</strong> open airports in the new region before the region changeover time unless it is within 30 minutes of changeover, there are no active frequencies open <strong class="red">AND</strong> no traffic exists in the <strong class="red">CURRENT</strong> region. In addition, Controllers are expected to show courtesy to other Controllers by sharing where possible, and opening the frequencies before announcing in <em>#controllers</em> - Controllers <strong class="red">must not</strong> purposely wait for the region changeover time and then post that they are 'open' in <em>#controllers</em> in an attempt to be 'first'</li>
<li>Opening frequencies is on a first come, first serve basis within <em>#controllers</em>. Therefore Controllers <strong class="red">should not</strong> reserve frequencies privately or not open in anticipation of a particular frequency becoming available. This does not apply to certain events where frequency allocation may be authorized</li>
<li>Controllers <strong class="red">must not</strong> control on the Training Server <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.4" class="documentation-content-link">7.5.4</a> below for exceptions)</em></li>
<li>Controllers <strong class="red">must not</strong> act as a Controller and as a pilot simultaneously on separate devices, violating Infinite Flight’s Terms &amp; Agreement</li>
<li>Standards of controlling are closely monitored – <strong class="red">Controllers are expected to control within their means,  prioritizing quality over quantity</strong> <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3-rank-structure" class="documentation-content-link">1A.3</a> below)</em></li>
</ul>
<p>*The &quot;bounds of the ATC Schedule&quot; is defined as the colored region that is highlighted for that day and/or time period. In addition, Controllers <strong class="red">should</strong> prioritize the opening of featured airports first, however all airports within the region are available</p>
</section>
</section>
<section id="discord">
<h2><a class="header-anchor" href="#discord"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Discord</h2>
<section class="reference">
<ul>
<li>All Controllers <strong class="red">must</strong> <a href="/guide/getting-started/home-user-interface/user-profile#linking-community-forum-account" class="documentation-content-link">link</a> their Community Forum Account <strong class="red">BEFORE</strong> controlling</li>
<li>Controllers <strong class="red">must</strong> ensure that their Discord Nickname is either the same as their IFC Username or real name</li>
<li>Controllers <strong class="red">must not</strong> share any IFATC material or conversations (including audio) contained within the IFATC Discord externally (unless prior approval has been granted)</li>
<li>Controllers <strong class="red">must</strong> be respectful to other users and practice common courtesies</li>
<li>Controllers <strong class="red">must not</strong> use any language which, in the exclusive discretion of Infinite Flight; may be deemed offensive (including, but not limited to, language that is unlawful, threatening, vulgar, sexually explicit, or racially, ethnically or otherwise objectionable)</li>
<li>Criticism and feedback will generally be given via DM; however, on occasion, it may be provided publicly if it is deemed to be a wider issue amongst Controllers</li>
</ul>
</section>
</section>
<section id="discord-voice-channel">
<h2><a class="header-anchor" href="#discord-voice-channel"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Discord Voice Channel</h2>
<section class="reference">
<ul>
<li>English <strong class="red">must</strong> be used at all times</li>
<li>The <em>#controlling[1-5]</em> voice channels <strong class="red">must</strong> only be used by members who are actively controlling with other Controllers</li>
<li>Coordination of the <em>#controlling[1-5]</em> voice channels <strong class="red">must</strong> only occur in <em>#controllers</em></li>
<li>Controllers <strong class="red">must not</strong> transmit anything that may be interpreted as disruptive</li>
<li>Controllers <strong class="red">must not</strong> transmit any private, identifying or sensitive information</li>
<li>Controllers <strong class="red">must not</strong> impersonate another user</li>
<li>Further guidance on the use of VC's can be found in Discord Communication Guidelines <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.1-discord-communication-guidelines#1a.1.5" class="documentation-content-link">1A.1.5</a> above)</em></li>
</ul>
<p><strong>Safeguarding</strong></p>
<p>Members may contact a Staff Member or IFC Moderator at any time to report a serious violation of VC rules or an unsafe situation. IFATC member safety and privacy is a top priority.</p>
<p><em>Note: Due to the nature of ATC and the representation of widely diverse social norms there may be accidental utterances provoked by excitement which do not warrant moderation (e.g. mild profanity and spontaneous phrases as a result of a startling event).</em></p>
</section>
</section>


1A.2  General Rules
Tip
: All Controllers must{.red} ensure that their Discord Nickname is either the same as their IFC Username or real name - this means that Controllers can be found easily if required (see 1A.2.1 below)
1A.2.1
The following rules must{.red} be followed at all times:
Controlling
All Controllers must{.red} announce in #controllers when opening/closing any frequency on the Expert Server. When closing, a MINIMUM{.red} of 5 minutes warning and the last ATIS letter used must{.red} be provided
Controllers must{.red} control within the bounds* of the ATC Schedule posted every week on the IFC and in #readonly on Discord. The only exception to this is when Controllers are not qualified to do so as per the rank structure (see 1A.3.1 below), in which case a sensible alternative can be selected
Unless otherwise specified in the ATC Schedule, the "region change" occurs at 0600Z (Controllers that are open during a region change must{.red} still meet the minimum controlling times before closing - see 1A.5.2 below). Controllers must not{.red} open airports in the new region before the region changeover time unless it is within 30 minutes of changeover, there are no active frequencies open AND{.red} no traffic exists in the CURRENT{.red} region. In addition, Controllers are expected to show courtesy to other Controllers by sharing where possible, and opening the frequencies before announcing in #controllers - Controllers must not{.red} purposely wait for the region changeover time and then post that they are 'open' in #controllers in an attempt to be 'first'
Opening frequencies is on a first come, first serve basis within #controllers. Therefore Controllers should not{.red} reserve frequencies privately or not open in anticipation of a particular frequency becoming available. This does not apply to certain events where frequency allocation may be authorized
Controllers must not{.red} control on the Training Server (see 7.5.4 below for exceptions)
Controllers must not{.red} act as a Controller and as a pilot simultaneously on separate devices, violating Infinite Flight’s Terms & Agreement
Standards of controlling are closely monitored – Controllers are expected to control within their means,  prioritizing quality over quantity{.red} (see 1A.3 below)
The "bounds of the ATC Schedule" is defined as the colored region that is highlighted for that day and/or time period. In addition, Controllers should*{.red} prioritize the opening of featured airports first, however all airports within the region are available
Discord
All Controllers must{.red} link their Community Forum Account BEFORE{.red} controlling
Controllers must{.red} ensure that their Discord Nickname is either the same as their IFC Username or real name
Controllers must not{.red} share any IFATC material or conversations (including audio) contained within the IFATC Discord externally (unless prior approval has been granted)
Controllers must{.red} be respectful to other users and practice common courtesies
Controllers must not{.red} use any language which, in the exclusive discretion of Infinite Flight; may be deemed offensive (including, but not limited to, language that is unlawful, threatening, vulgar, sexually explicit, or racially, ethnically or otherwise objectionable)
Criticism and feedback will generally be given via DM; however, on occasion, it may be provided publicly if it is deemed to be a wider issue amongst Controllers
Discord Voice Channel
English must{.red} be used at all times
The #controlling[1-5] voice channels must{.red} only be used by members who are actively controlling with other Controllers
Coordination of the #controlling[1-5] voice channels must{.red} only occur in #controllers
Controllers must not{.red} transmit anything that may be interpreted as disruptive
Controllers must not{.red} transmit any private, identifying or sensitive information
Controllers must not{.red} impersonate another user
Further guidance on the use of VC's can be found in Discord Communication Guidelines (see 1A.1.5 above)
Safeguarding
Members may contact a Staff Member or IFC Moderator at any time to report a serious violation of VC rules or an unsafe situation. IFATC member safety and privacy is a top priority.
Note: Due to the nature of ATC and the representation of widely diverse social norms there may be accidental utterances provoked by excitement which do not warrant moderation (e.g. mild profanity and spontaneous phrases as a result of a startling event).

1A.2 General Rules

<section id="1a.3-rank-structure">
<h1><a class="header-anchor" href="#1a.3-rank-structure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.3  Rank Structure</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>When you are promoted you will have access to airports that typically have more traffic. It is encouraged that you start off slowly, gradually building up to these more &quot;high-volume&quot; traffic airports within your new classification. This is particularly important during peak times or events such as Friday Night Flight (FNF). If in doubt, ask in <em>#controllers</em> for suggestions before opening – it takes time to get use to heavy traffic, start off <strong class="red">SLOWLY</strong></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="1a.3.1">
<h3><a class="header-anchor" href="#1a.3.1">1A.3.1</a></h3>
<section class="reference">
<p>The table below outlines the Rank Structure in place. Promotion is based on activity, performance, feedback and in some cases, a formal test (theory and/or practical).</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Rank</th>
<th>Frequencies Available</th>
<th>Test Required</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Rank">Apprentice</td>
<td data-label="Frequencies Available">C / D / ATIS</td>
<td data-label="Test Required">Theory and Practical (Initial)</td>
</tr>
<tr>
<td data-label="Rank">Specialist*</td>
<td data-label="Frequencies Available">B / C / D / ATIS</td>
<td data-label="Test Required">Practical (Check Ride)</td>
</tr>
<tr>
<td data-label="Rank">Officer**</td>
<td data-label="Frequencies Available">Radar / B / C / D / ATIS</td>
<td data-label="Test Required">Theory and Practical (Radar)***</td>
</tr>
</tbody>
</table>
<p>* On promotion to Specialist, Controllers are placed on probation until the &quot;Check Ride&quot; phase is completed <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-promotion-to-specialist-(check-ride)#7.4-promotion-to-specialist-(check-ride)" class="documentation-content-link">7.4</a> below)</em></p>
<p>** On promotion to Officer, Controllers are placed on probation (minimum period of 30 days) until the &quot;Officer Check Ride&quot; phase is completed <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.7" class="documentation-content-link">7.5.7</a> below)</em></p>
<p>*** Before commencement of training for the rank of Officer, the following requirements must be met (do not contact a Recruiter for Radar Training before you meet the minimum requirements):</p>
<ul>
<li>Minimum of 60 days at the rank of Specialist</li>
<li>Minimum of 2000 all-time operations</li>
<li>Attend a minimum of 10 training sessions per 30 days in the <em>#training-time[1-3]</em> Discord channels (this is counted with the honor system and members are expected to track their own attendance)</li>
<li>Maintain a minimum of 35%/31.5 days activity in a 90 day period to qualify for training services (this % will be shown on each user's activity profile at <a href="https://if-atc.com" class="documentation-content-link">https://if-atc.com</a>)</li>
</ul>
<p>In addition to the rank structure outlined above, further roles within IFATC are outlined below:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Title</th>
<th>Role</th>
<th>Violation Reversals</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Title">Appeals</td>
<td data-label="Role">Manage violation appeals</td>
<td data-label="Violation Reversals">Yes</td>
</tr>
<tr>
<td data-label="Title">Tester</td>
<td data-label="Role">Attend practical tests</td>
<td data-label="Violation Reversals">No</td>
</tr>
<tr>
<td data-label="Title">Trainer</td>
<td data-label="Role">Educate and train candidates/controllers</td>
<td data-label="Violation Reversals">No</td>
</tr>
<tr>
<td data-label="Title">Recruiter</td>
<td data-label="Role">Manage recruitment and administer all theory/practical tests</td>
<td data-label="Violation Reversals">Only if related to official tests</td>
</tr>
<tr>
<td data-label="Title">Supervisor</td>
<td data-label="Role">Moderate IFATC and provide guidance to controllers</td>
<td data-label="Violation Reversals">No</td>
</tr>
<tr>
<td data-label="Title">Moderator</td>
<td data-label="Role">Moderate the IFC and manage violation appeals</td>
<td data-label="Violation Reversals">Yes</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="1a.3.2">
<h3><a class="header-anchor" href="#1a.3.2">1A.3.2</a></h3>
<section class="reference">
<p>All Controllers have the ability to issue a Level 2 or 3 Violation once they have been added to IFATC. Guidelines are contained within this manual <em>(see <a href="/guide/atc-manual/1b.-violations/1b.1-guidelines#1b.1-guidelines" class="documentation-content-link">1B.1</a> below).</em></p>
</section>
</section>
<section id="1a.3.3">
<h3><a class="header-anchor" href="#1a.3.3">1A.3.3</a></h3>
<section class="reference">
<p>&quot;Recruiters&quot; are authorized to administer all Theory and Practical tests <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1" class="documentation-content-link">7.1.1</a> below)</em> in addition to the rank privileges of Supervisor.</p>
</section>
</section>
<section id="1a.3.4">
<h3><a class="header-anchor" href="#1a.3.4">1A.3.4</a></h3>
<section class="reference">
<p>&quot;Trainers&quot; are authorized to conduct training for all Practical tests <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.2" class="documentation-content-link">7.1.2</a> below)</em> in addition to the rank privileges of either Officer or Supervisor (dependent on their position within IFATC).</p>
</section>
</section>
<section id="1a.3.5">
<h3><a class="header-anchor" href="#1a.3.5">1A.3.5</a></h3>
<section class="reference">
<p><strong class="red">All Controllers are subject to promotion/demotion at any time based on activity, performance and feedback.</strong></p>
</section>
</section>


1A.3  Rank Structure
Tip
: When you are promoted you will have access to airports that typically have more traffic. It is encouraged that you start off slowly, gradually building up to these more "high-volume" traffic airports within your new classification. This is particularly important during peak times or events such as Friday Night Flight (FNF). If in doubt, ask in #controllers for suggestions before opening – it takes time to get use to heavy traffic, start off SLOWLY{.red}
1A.3.1
The table below outlines the Rank Structure in place. Promotion is based on activity, performance, feedback and in some cases, a formal test (theory and/or practical).
| Rank        | Frequencies Available    | Test Required                   |
| ----------- | ------------------------ | ------------------------------- |
| Apprentice  | C / D / ATIS             | Theory and Practical (Initial)  |
| Specialist* | B / C / D / ATIS         | Practical (Check Ride)          |
| Officer*   | Radar / B / C / D / ATIS | Theory and Practical (Radar)** |
\* On promotion to Specialist, Controllers are placed on probation until the "Check Ride" phase is completed (see 7.4#7.4-promotion-to-specialist-(check-ride)) below)
\* On promotion to Officer, Controllers are placed on probation (minimum period of 30 days) until the "Officer Check Ride" phase is completed (see 7.5.7 below)*
* Before commencement of training for the rank of Officer, the following requirements must be met (do not contact a Recruiter for Radar Training before you meet the minimum requirements):
Minimum of 60 days at the rank of Specialist
Minimum of 2000 all-time operations
Attend a minimum of 10 training sessions per 30 days in the #training-time[1-3] Discord channels (this is counted with the honor system and members are expected to track their own attendance)
Maintain a minimum of 35%/31.5 days activity in a 90 day period to qualify for training services (this % will be shown on each user's activity profile at https://if-atc.com)
In addition to the rank structure outlined above, further roles within IFATC are outlined below:
| Title      | Role                                                         | Violation Reversals               |
| ---------- | ------------------------------------------------------------ | --------------------------------- |
| Appeals    | Manage violation appeals                                     | Yes                               |
| Tester     | Attend practical tests                                       | No                                |
| Trainer    | Educate and train candidates/controllers                     | No                                |
| Recruiter  | Manage recruitment and administer all theory/practical tests | Only if related to official tests |
| Supervisor | Moderate IFATC and provide guidance to controllers           | No                                |
| Moderator  | Moderate the IFC and manage violation appeals                | Yes                               |
1A.3.2
All Controllers have the ability to issue a Level 2 or 3 Violation once they have been added to IFATC. Guidelines are contained within this manual (see 1B.1 below).
1A.3.3
"Recruiters" are authorized to administer all Theory and Practical tests (see 7.1.1 below) in addition to the rank privileges of Supervisor.
1A.3.4
"Trainers" are authorized to conduct training for all Practical tests (see 7.1.2 below) in addition to the rank privileges of either Officer or Supervisor (dependent on their position within IFATC).
1A.3.5
All Controllers are subject to promotion/demotion at any time based on activity, performance and feedback.{.red}

1A.3 Rank Structure

<section id="1a.4-disciplinary-and-suspension-procedure">
<h1><a class="header-anchor" href="#1a.4-disciplinary-and-suspension-procedure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.4  Disciplinary and Suspension Procedure</h1>
<section class="reference"></section>
<section id="1a.4.1">
<h3><a class="header-anchor" href="#1a.4.1">1A.4.1</a></h3>
<section class="reference">
<p>Controllers not following The ATC Manual can expect the following procedure:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Offense</th>
<th>Action Taken</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Offense">1st</td>
<td data-label="Action Taken">Warning via DM</td>
</tr>
<tr>
<td data-label="Offense">2nd</td>
<td data-label="Action Taken">3 day Controller &amp; Discord suspension</td>
</tr>
<tr>
<td data-label="Offense">3rd</td>
<td data-label="Action Taken">7 day Controller &amp; Discord suspension</td>
</tr>
<tr>
<td data-label="Offense">4th</td>
<td data-label="Action Taken">Removal from the IFATC Team</td>
</tr>
</tbody>
</table>
<p>Following any suspension, Controllers will return at the rank they previously held. The date they’re reinstated on will serve as the new start date at that rank <em>(this is to take into account minimum requirements for rank upgrades - see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> above)</em>.</p>
</section>
</section>
<section id="1a.4.2">
<h3><a class="header-anchor" href="#1a.4.2">1A.4.2</a></h3>
<section class="reference">
<p>If a Controller is issued a Level 2 or Level 3 Violation whilst operating as a pilot, the following can be expected (this will also count towards a Controllers total amount of offenses as outlined above):</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Violation</th>
<th>Action Taken</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Violation">Level 2</td>
<td data-label="Action Taken">3 day Controller &amp; Discord suspension</td>
</tr>
<tr>
<td data-label="Violation">Level 3</td>
<td data-label="Action Taken">7 day Controller &amp; Discord suspension</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="1a.4.3">
<h3><a class="header-anchor" href="#1a.4.3">1A.4.3</a></h3>
<section class="reference">
<p>Serious cases, reviewed by IFC Moderators, are subject to immediate removal or suspension.</p>
</section>
</section>
</section>


1A.4  Disciplinary and Suspension Procedure
1A.4.1
Controllers not following The ATC Manual can expect the following procedure:
| Offense | Action Taken                          |
| ------- | ------------------------------------- |
| 1st     | Warning via DM                        |
| 2nd     | 3 day Controller & Discord suspension |
| 3rd     | 7 day Controller & Discord suspension |
| 4th     | Removal from the IFATC Team           |
Following any suspension, Controllers will return at the rank they previously held. The date they’re reinstated on will serve as the new start date at that rank (this is to take into account minimum requirements for rank upgrades - see 1A.3.1 above).
1A.4.2
If a Controller is issued a Level 2 or Level 3 Violation whilst operating as a pilot, the following can be expected (this will also count towards a Controllers total amount of offenses as outlined above):
| Violation | Action Taken                          |
| --------- | ------------------------------------- |
| Level 2   | 3 day Controller & Discord suspension |
| Level 3   | 7 day Controller & Discord suspension |
1A.4.3
Serious cases, reviewed by IFC Moderators, are subject to immediate removal or suspension.

1A.4 Disciplinary and Suspension Procedure

<section id="1a.5-activity-requirements">
<h1><a class="header-anchor" href="#1a.5-activity-requirements"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1A.5  Activity Requirements</h1>
<section class="reference"></section>
<section id="1a.5.1">
<h3><a class="header-anchor" href="#1a.5.1">1A.5.1</a></h3>
<section class="reference">
<p>Controllers <strong class="red">should</strong> maintain some level of activity and proficiency. The following defines actions taken following periods of inactivity:</p>
<ul>
<li>
<p>30 Days:   Written reminder of activity requirements</p>
</li>
<li>
<p>90 Days:   Removal from IFATC and Discord, <strong class="red">must</strong> complete the Initial Practical test to re-join (minimum of 30 days <strong class="red">must</strong> elapse from the date of removal before able to complete the test)</p>
</li>
<li>
<p>6 Months:  <strong class="red">Must</strong> complete the Initial Theory and Practical tests to re-join</p>
</li>
</ul>
<p>For the purposes of activity, the ATIS frequency is not included, and therefore Controllers <strong class="red">must</strong> control Ground, Tower and/or Radar positions to be considered active.</p>
</section>
</section>
<section id="1a.5.2">
<h3><a class="header-anchor" href="#1a.5.2">1A.5.2</a></h3>
<section class="reference">
<p>Minimum controlling times are enforced to ensure that pilots receive a consistent service and are highlighted in the table below (please note that these are strictly <strong class="red">MINIMUM TIMES</strong> - there is no maximum time limit that a frequency can be open but Controllers <strong class="red">must</strong> ensure that the standard of controlling expected is maintained during long sessions):</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Airport</th>
<th>Minimum Time</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Airport">Class Charlie/Delta</td>
<td data-label="Minimum Time">30 minutes</td>
</tr>
<tr>
<td data-label="Airport">Class Bravo</td>
<td data-label="Minimum Time">60 minutes</td>
</tr>
<tr>
<td data-label="Airport">All Radar Facilities</td>
<td data-label="Minimum Time">60 minutes</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="1a.5.3">
<h3><a class="header-anchor" href="#1a.5.3">1A.5.3</a></h3>
<section class="reference">
<p>Before opening a frequency, Controllers <strong class="red">must</strong> ensure that they not only have the minimum time free but also have:</p>
<ul>
<li>
<p>An adequate amount of battery life on the device to be used</p>
</li>
<li>
<p>A good/reliable internet connection</p>
</li>
</ul>
</section>
</section>
</section>


1A.5  Activity Requirements
1A.5.1
Controllers should{.red} maintain some level of activity and proficiency. The following defines actions taken following periods of inactivity:
 30 Days:   Written reminder of activity requirements
 90 Days:   Removal from IFATC and Discord, must{.red} complete the Initial Practical test to re-join (minimum of 30 days must{.red} elapse from the date of removal before able to complete the test)
 6 Months:  Must{.red} complete the Initial Theory and Practical tests to re-join
For the purposes of activity, the ATIS frequency is not included, and therefore Controllers must{.red} control Ground, Tower and/or Radar positions to be considered active.
1A.5.2
Minimum controlling times are enforced to ensure that pilots receive a consistent service and are highlighted in the table below (please note that these are strictly MINIMUM TIMES{.red} - there is no maximum time limit that a frequency can be open but Controllers must{.red} ensure that the standard of controlling expected is maintained during long sessions):
| Airport              | Minimum Time |
| -------------------- | ------------ |
| Class Charlie/Delta  | 30 minutes   |
| Class Bravo          | 60 minutes   |
| All Radar Facilities | 60 minutes   |
1A.5.3
Before opening a frequency, Controllers must{.red} ensure that they not only have the minimum time free but also have:
 An adequate amount of battery life on the device to be used
 A good/reliable internet connection

1A.5 Activity Requirements

<section id="1b.1-guidelines">
<h1><a class="header-anchor" href="#1b.1-guidelines"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1B.1  Guidelines</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Consistency <strong class="red">must</strong> be maintained and therefore Controllers cannot be afraid to issue a Violation. Tolerance however, is equally as important – Controllers <strong class="red">should</strong> try to put themselves in the pilot’s position to determine if it was malicious or a genuine mistake</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="1b.1.1">
<h3><a class="header-anchor" href="#1b.1.1">1B.1.1</a></h3>
<section class="reference">
<p>The Expert Server is here to provide pilots with a realistic environment in which to fly, and as such; the Controllers are expected to strictly enforce the rules of this server so that serious users can enjoy the experience.</p>
</section>
</section>
<section id="1b.1.2">
<h3><a class="header-anchor" href="#1b.1.2">1B.1.2</a></h3>
<section class="reference">
<p>To facilitate Controllers in this role they are provided with access to &quot;reporting a user&quot;, which will issue the pilot a &quot;Violation&quot; (based on the reason, this will automatically be classified as either Level 2 or 3). Violations are split into three levels:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Violation</th>
<th>Consequence</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Violation">Level  1</td>
<td data-label="Consequence">These are automatically generated if a pilot violates any one of the set conditions  <em>(see Level 1 Violation Table below)</em>. If a pilot receives 3 or more in one flight, they will be automatically removed from the server and will have to start a new flight to return</td>
</tr>
<tr>
<td data-label="Violation">Level  2 (Amber)</td>
<td data-label="Consequence">The pilot is disconnected from the server but can continue the flight offline.  The pilot may return to the Expert Server *immediately by starting a new flight</td>
</tr>
<tr>
<td data-label="Violation">Level  3 (Red)</td>
<td data-label="Consequence">The pilot is disconnected from the server but can continue the flight offline.  The pilot will not be able to return to the Expert Server after the flight has been ended, with access being restricted for 7 days following this</td>
</tr>
</tbody>
</table>
<p>*Violations are kept on a pilot’s record and therefore, if a pilot continues to receive Violations (Level 2 and Level 3 only), Expert Server access will be restricted for longer. Currently, no more than <strong>5</strong> Level 2 and/or Level 3 Violations can be received within a 365 day rolling period for access to the server.</p>
<p><strong>Level 1 Violations Table:</strong></p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Rule</th>
<th>Conditions for Violation</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Rule">Ground Overspeed</td>
<td data-label="Conditions for Violation">Above 35kts GS (ground speed) on ground, excluding runways</td>
</tr>
<tr>
<td data-label="Rule">Flight Overspeed</td>
<td data-label="Conditions for Violation">Above 250kts IAS (indicated airspeed) below 10,000ft / exceeding max speed warning (VMO/MMO) - does not apply to military aircraft</td>
</tr>
<tr>
<td data-label="Rule">Aerobatics within Airspace</td>
<td data-label="Conditions for Violation">Aerobatics below 5,000ft and within 5 nautical miles of an airport</td>
</tr>
<tr>
<td data-label="Rule">Runway Idle</td>
<td data-label="Conditions for Violation">Sit idle on a runway longer than 60 seconds without ATC clearance</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="1b.1.3">
<h3><a class="header-anchor" href="#1b.1.3">1B.1.3</a></h3>
<section class="reference">
<p>Level 2 and 3 Violations <strong class="red">should not</strong> be used for actions that are already punishable by Level 1 Violations.</p>
</section>
</section>
<section id="1b.1.4">
<h3><a class="header-anchor" href="#1b.1.4">1B.1.4</a></h3>
<section class="reference">
<p>Users do not require prior warning to be issued a Violation, and this <strong class="red">should</strong> be used in scenarios where a lack of regard for others or procedures is present. However, Controllers <strong class="red">should</strong> exercise patience (traffic permitting) for simple mistakes when an opportunity for the user to correct exists - Controllers have an array of specific commands at their disposal to help with this as well as generic commands such as &quot;please follow instructions&quot;. Controllers <strong class="red">must</strong> exercise their best judgment on a case by case basis and if unsure, seek further guidance from a Supervisor or above.</p>
</section>
</section>
<section id="1b.1.5">
<h3><a class="header-anchor" href="#1b.1.5">1B.1.5</a></h3>
<section class="reference">
<p>Following a Violation Appeal, the pilot's replay is the primary method to provide evidence for incident resolution however the Controller's replay may also be requested by the Appeals team if required <em>(see <a href="/guide/atc-manual/1b.-violations/1b.2-incident-resolution-procedure#1b.2-incident-resolution-procedure" class="documentation-content-link">1B.2</a> below)</em>.</p>
</section>
</section>
<section id="1b.1.6">
<h3><a class="header-anchor" href="#1b.1.6">1B.1.6</a></h3>
<section class="reference">
<p>A summary of some of the reasons to issue a Violation are listed below:</p>
<ul>
<li>
<p>Not following procedures broadcast on ATIS</p>
</li>
<li>
<p>Pushback/taxiing without clearance</p>
</li>
<li>
<p>Crashing/taxiing into other aircraft</p>
</li>
<li>
<p>Taking-off/landing from a taxiway or grass</p>
</li>
<li>
<p>Entering the runway without clearance</p>
</li>
<li>
<p>Taking-off/landing without clearance</p>
</li>
<li>
<p>Not following the issued sequence</p>
</li>
<li>
<p>Not following the cleared altitude/heading/speed</p>
</li>
<li>
<p>Pilots who do not respond to an instruction after 2-3 attempts*</p>
</li>
<li>
<p>Pilots sending duplicate messages or unnecessary requests</p>
</li>
<li>
<p>Spamming a frequency</p>
</li>
<li>
<p>Repeated disruption</p>
</li>
<li>
<p>Insulting call-signs/usernames</p>
</li>
<li>
<p>Call-signs/usernames with profanity or discriminating/racist terms</p>
</li>
</ul>
<p>*Aircraft descending via VNAV may be issued a violation after a warning if they are unresponsive <strong class="red">AND</strong> conflict with others.</p>
<p>The full list of Violation reasons for each position are listed below (including the Violation Level that the pilot will receive); however, it is important to note that Controllers <strong class="red">must not</strong> pick a reason in order to decide if the pilot gets a Level 2 or Level 3 Violation. Each Violation is specifically paired with a Level, therefore Controllers <strong class="red">must</strong> pick the correct reason and allow the system to automatically decide what Level Violation is issued:</p>
</section>
</section>
<section id="ground">
<h2><a class="header-anchor" href="#ground"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Ground</h2>
<section class="reference">
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Reason">Blocking an active taxiway</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Crossing the hold line without permission</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Entered a runway without permission</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow ATIS</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow TFR</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to give way</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Inappropriate callsign</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Not following instructions</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Spamming frequency - unnecessary duplicate requests</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Taxi without permission</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Taxiing through grass or terminal area</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Taxiing through others</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Too close to aircraft ahead</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Unable to communicate</td>
<td data-label="Violation Level">N/A</td>
</tr>
<tr>
<td data-label="Reason">Unresponsive while climbing, descending, or maneuvering</td>
<td data-label="Violation Level">2</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="tower">
<h2><a class="header-anchor" href="#tower"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Tower</h2>
<section class="reference">
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Reason">Crossing the hold line without permission</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Entered a runway without permission</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Excessive speed in the airport environment</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to divert</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to exit runway</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow ATIS</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow sequence</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow TFR</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to go-around</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to maintain appropriate aircraft separation</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Flying through other aircraft</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Inappropriate callsign</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Incorrect arrival procedures - inappropriate altitude, speed, position</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Landing/departing on the wrong runway</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Not following instructions</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Spamming frequency - unnecessary duplicate requests</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Take-off/land without permission</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Take-off/landing from grass, ramp or taxiway</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Unable to communicate</td>
<td data-label="Violation Level">N/A</td>
</tr>
<tr>
<td data-label="Reason">Unresponsive while climbing, descending, or maneuvering</td>
<td data-label="Violation Level">2</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="radar">
<h2><a class="header-anchor" href="#radar"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Radar</h2>
<section class="reference">
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Reason">Aligned with the wrong runway</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Excessive speed in the airport environment</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to complete instrument approach</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to divert</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to execute missed approach</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow ATIS</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Failure to follow TFR</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Failure to maintain appropriate aircraft separation</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Following flight plan instead of ATC instructions</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Inappropriate callsign</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Incorrect arrival procedures - inappropriate altitude, speed, position</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Not following ATC assigned heading, altitude or speed</td>
<td data-label="Violation Level">3</td>
</tr>
<tr>
<td data-label="Reason">Not following instructions</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Spamming frequency - unnecessary duplicate requests</td>
<td data-label="Violation Level">2</td>
</tr>
<tr>
<td data-label="Reason">Unable to communicate</td>
<td data-label="Violation Level">N/A</td>
</tr>
<tr>
<td data-label="Reason">Unresponsive while climbing, descending, or maneuvering</td>
<td data-label="Violation Level">2</td>
</tr>
</tbody>
</table>
</section>
<section id="1b.1.7">
<h3><a class="header-anchor" href="#1b.1.7">1B.1.7</a></h3>
<section class="reference">
<p>Discretion <strong class="red">should</strong> be used when dealing with call-signs/usernames that could be related to aviation accidents (or other topics of a sensitive nature). It is unknown whether the intended use is to offend or pay respects.</p>
</section>
</section>
<section id="1b.1.8">
<h3><a class="header-anchor" href="#1b.1.8">1B.1.8</a></h3>
<section class="reference">
<p>All Violations are tracked and recorded. Controllers that are found to abuse the system will be given warning, suspension or removal from IFATC <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.4-disciplinary-and-suspension-procedure#1a.4-disciplinary-and-suspension-procedure" class="documentation-content-link">1A.4</a> above)</em>. If a Controller is unsure if issuing a Violation is necessary, they <strong class="red">should</strong> ask a Supervisor or above for guidance.</p>
</section>
</section>
<section id="1b.1.9">
<h3><a class="header-anchor" href="#1b.1.9">1B.1.9</a></h3>
<section class="reference">
<p>For some infractions that do not warrant a Violation, the use of &quot;please check the User Guide for assistance using ATC instructions&quot; can be a useful tool but it <strong class="red">should</strong> only be used sparingly and with good judgment. Do not attempt to fly the aircraft for pilots by bombarding them with countless commands – mistakes happen, both by pilots and Controllers. This command is specifically for scenarios where there is clear confusion between the command sent, and the subsequent pilot response and its sole purpose is to direct the pilot to the IFC Forum where they can ask questions, check tutorials, or contact the Controller directly to learn from the experience.</p>
</section>
</section>
</section>


1B.1  Guidelines
Tip
: Consistency must{.red} be maintained and therefore Controllers cannot be afraid to issue a Violation. Tolerance however, is equally as important – Controllers should{.red} try to put themselves in the pilot’s position to determine if it was malicious or a genuine mistake
1B.1.1
The Expert Server is here to provide pilots with a realistic environment in which to fly, and as such; the Controllers are expected to strictly enforce the rules of this server so that serious users can enjoy the experience.
1B.1.2
To facilitate Controllers in this role they are provided with access to "reporting a user", which will issue the pilot a "Violation" (based on the reason, this will automatically be classified as either Level 2 or 3). Violations are split into three levels:
| Violation        | Consequence                                                  |
| ---------------- | ------------------------------------------------------------ |
| Level  1         | These are automatically generated if a pilot violates any one of the set conditions  (see Level 1 Violation Table below). If a pilot receives 3 or more in one flight, they will be automatically removed from the server and will have to start a new flight to return |
| Level  2 (Amber) | The pilot is disconnected from the server but can continue the flight offline.  The pilot may return to the Expert Server *immediately by starting a new flight |
| Level  3 (Red)   | The pilot is disconnected from the server but can continue the flight offline.  The pilot will not be able to return to the Expert Server after the flight has been ended, with access being restricted for 7 days following this |
Violations are kept on a pilot’s record and therefore, if a pilot continues to receive Violations (Level 2 and Level 3 only), Expert Server access will be restricted for longer. Currently, no more than 5* Level 2 and/or Level 3 Violations can be received within a 365 day rolling period for access to the server.
Level 1 Violations Table:
| Rule                       | Conditions for Violation                                     |
| -------------------------- | ------------------------------------------------------------ |
| Ground Overspeed           | Above 35kts GS (ground speed) on ground, excluding runways   |
| Flight Overspeed           | Above 250kts IAS (indicated airspeed) below 10,000ft / exceeding max speed warning (VMO/MMO) - does not apply to military aircraft |
| Aerobatics within Airspace | Aerobatics below 5,000ft and within 5 nautical miles of an airport |
| Runway Idle                | Sit idle on a runway longer than 60 seconds without ATC clearance |
1B.1.3
Level 2 and 3 Violations should not{.red} be used for actions that are already punishable by Level 1 Violations.
1B.1.4
Users do not require prior warning to be issued a Violation, and this should{.red} be used in scenarios where a lack of regard for others or procedures is present. However, Controllers should{.red} exercise patience (traffic permitting) for simple mistakes when an opportunity for the user to correct exists - Controllers have an array of specific commands at their disposal to help with this as well as generic commands such as "please follow instructions". Controllers must{.red} exercise their best judgment on a case by case basis and if unsure, seek further guidance from a Supervisor or above.
1B.1.5
Following a Violation Appeal, the pilot's replay is the primary method to provide evidence for incident resolution however the Controller's replay may also be requested by the Appeals team if required (see 1B.2 below).
1B.1.6
A summary of some of the reasons to issue a Violation are listed below:
 Not following procedures broadcast on ATIS
 Pushback/taxiing without clearance
 Crashing/taxiing into other aircraft
 Taking-off/landing from a taxiway or grass
 Entering the runway without clearance
 Taking-off/landing without clearance
 Not following the issued sequence
 Not following the cleared altitude/heading/speed
 Pilots who do not respond to an instruction after 2-3 attempts*
 Pilots sending duplicate messages or unnecessary requests
 Spamming a frequency
 Repeated disruption
 Insulting call-signs/usernames
 Call-signs/usernames with profanity or discriminating/racist terms
Aircraft descending via VNAV may be issued a violation after a warning if they are unresponsive AND*{.red} conflict with others.
The full list of Violation reasons for each position are listed below (including the Violation Level that the pilot will receive); however, it is important to note that Controllers must not{.red} pick a reason in order to decide if the pilot gets a Level 2 or Level 3 Violation. Each Violation is specifically paired with a Level, therefore Controllers must{.red} pick the correct reason and allow the system to automatically decide what Level Violation is issued:
Ground
| Reason                                                  | Violation Level |
| ------------------------------------------------------- | --------------- |
| Blocking an active taxiway                              | 2               |
| Crossing the hold line without permission               | 2               |
| Entered a runway without permission                     | 3               |
| Failure to follow ATIS                                  | 2               |
| Failure to follow TFR                                   | 3               |
| Failure to give way                                     | 2               |
| Inappropriate callsign                                  | 3               |
| Not following instructions                              | 2               |
| Spamming frequency - unnecessary duplicate requests     | 2               |
| Taxi without permission                                 | 2               |
| Taxiing through grass or terminal area                  | 2               |
| Taxiing through others                                  | 2               |
| Too close to aircraft ahead                             | 2               |
| Unable to communicate                                   | N/A             |
| Unresponsive while climbing, descending, or maneuvering | 2               |
Tower
| Reason                                                       | Violation Level |
| ------------------------------------------------------------ | --------------- |
| Crossing the hold line without permission                    | 2               |
| Entered a runway without permission                          | 3               |
| Excessive speed in the airport environment                   | 3               |
| Failure to divert                                            | 3               |
| Failure to exit runway                                       | 2               |
| Failure to follow ATIS                                       | 2               |
| Failure to follow sequence                                   | 2               |
| Failure to follow TFR                                        | 3               |
| Failure to go-around                                         | 2               |
| Failure to maintain appropriate aircraft separation          | 2               |
| Flying through other aircraft                                | 3               |
| Inappropriate callsign                                       | 3               |
| Incorrect arrival procedures - inappropriate altitude, speed, position | 3               |
| Landing/departing on the wrong runway                        | 3               |
| Not following instructions                                   | 2               |
| Spamming frequency - unnecessary duplicate requests          | 2               |
| Take-off/land without permission                             | 3               |
| Take-off/landing from grass, ramp or taxiway                 | 3               |
| Unable to communicate                                        | N/A             |
| Unresponsive while climbing, descending, or maneuvering      | 2               |
Radar
| Reason                                                       | Violation Level |
| ------------------------------------------------------------ | --------------- |
| Aligned with the wrong runway                                | 2               |
| Excessive speed in the airport environment                   | 3               |
| Failure to complete instrument approach                      | 2               |
| Failure to divert                                            | 3               |
| Failure to execute missed approach                           | 3               |
| Failure to follow ATIS                                       | 2               |
| Failure to follow TFR                                        | 3               |
| Failure to maintain appropriate aircraft separation          | 2               |
| Following flight plan instead of ATC instructions            | 3               |
| Inappropriate callsign                                       | 3               |
| Incorrect arrival procedures - inappropriate altitude, speed, position | 3               |
| Not following ATC assigned heading, altitude or speed        | 3               |
| Not following instructions                                   | 2               |
| Spamming frequency - unnecessary duplicate requests          | 2               |
| Unable to communicate                                        | N/A             |
| Unresponsive while climbing, descending, or maneuvering      | 2               |
1B.1.7
Discretion should{.red} be used when dealing with call-signs/usernames that could be related to aviation accidents (or other topics of a sensitive nature). It is unknown whether the intended use is to offend or pay respects.
1B.1.8
All Violations are tracked and recorded. Controllers that are found to abuse the system will be given warning, suspension or removal from IFATC (see 1A.4 above). If a Controller is unsure if issuing a Violation is necessary, they should{.red} ask a Supervisor or above for guidance.
1B.1.9
For some infractions that do not warrant a Violation, the use of "please check the User Guide for assistance using ATC instructions" can be a useful tool but it should{.red} only be used sparingly and with good judgment. Do not attempt to fly the aircraft for pilots by bombarding them with countless commands – mistakes happen, both by pilots and Controllers. This command is specifically for scenarios where there is clear confusion between the command sent, and the subsequent pilot response and its sole purpose is to direct the pilot to the IFC Forum where they can ask questions, check tutorials, or contact the Controller directly to learn from the experience.

1B.1 Guidelines

<section id="1b.2-incident-resolution-procedure">
<h1><a class="header-anchor" href="#1b.2-incident-resolution-procedure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 1B.2  Incident Resolution Procedure</h1>
<section class="reference"></section>
<section id="1b.2.1">
<h3><a class="header-anchor" href="#1b.2.1">1B.2.1</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> keep their replays following a controlling session for a <strong class="red">MINIMUM</strong> of 7 days in case it is required for incident resolution, those that wish to raise a Violation Appeal and/or query are expected to contact the Controller or Appeals Team (on the IFC) within this time frame. If an appeal/query is raised after 7 days it can no longer be appealed.</p>
</section>
</section>
<section id="1b.2.2">
<h3><a class="header-anchor" href="#1b.2.2">1B.2.2</a></h3>
<section class="reference">
<p>In order to maintain consistency and to deescalate conflicts on the IFC Forum, the following procedure <strong class="red">must</strong> be followed at all times when dealing with Violation complaints and/or queries:</p>
<ul>
<li>The only place incidents may be resolved is on the IFC Forum. Any posts on IFFG or similar fan groups should be politely directed to the IFC Forum without addressing the actual complaint/query</li>
<li>When a complaint/query is posted on the IFC Forum you <strong class="red">must not</strong> respond – inform the Controller in the <em>#discussions</em> channel on Discord by tagging them</li>
<li>When the Controller in question is available, they will respond to the complaint/query (it is recommended that this is done via DM)</li>
<li>Any Controller that is unsure on how best to respond (and particularly new Controllers) <strong class="red">must</strong> contact a Supervisor or above via Discord before posting on the IFC Forum (it is important that the initial response from the Controller addresses the issue in its entirety and is factually correct)</li>
<li>If the incident has not been successfully resolved by all parties involved, then the Appeals Team will be required to assist in deescalation. This can be done by adding <em>@appeals</em> to the DM (not by tagging) on the IFC Forum</li>
<li>Controllers <strong class="red">must not</strong> engage in an argument or use definitive phrases such as &quot;this Violation will not be reversed&quot;, Appeals Team members will handle this</li>
</ul>
</section>
</section>
<section id="1b.2.3">
<h3><a class="header-anchor" href="#1b.2.3">1B.2.3</a></h3>
<section class="reference">
<p>If you are <strong class="red">NOT THE CONTROLLER INVOLVED</strong> you <strong class="red">must not</strong> respond.</p>
</section>
</section>
</section>


1B.2  Incident Resolution Procedure
1B.2.1
Controllers must{.red} keep their replays following a controlling session for a MINIMUM{.red} of 7 days in case it is required for incident resolution, those that wish to raise a Violation Appeal and/or query are expected to contact the Controller or Appeals Team (on the IFC) within this time frame. If an appeal/query is raised after 7 days it can no longer be appealed.
1B.2.2
In order to maintain consistency and to deescalate conflicts on the IFC Forum, the following procedure must{.red} be followed at all times when dealing with Violation complaints and/or queries:
 The only place incidents may be resolved is on the IFC Forum. Any posts on IFFG or similar fan groups should be politely directed to the IFC Forum without addressing the actual complaint/query
 When a complaint/query is posted on the IFC Forum you must not{.red} respond – inform the Controller in the #discussions channel on Discord by tagging them
 When the Controller in question is available, they will respond to the complaint/query (it is recommended that this is done via DM)
 Any Controller that is unsure on how best to respond (and particularly new Controllers) must{.red} contact a Supervisor or above via Discord before posting on the IFC Forum (it is important that the initial response from the Controller addresses the issue in its entirety and is factually correct)
 If the incident has not been successfully resolved by all parties involved, then the Appeals Team will be required to assist in deescalation. This can be done by adding @appeals to the DM (not by tagging) on the IFC Forum
 Controllers must not{.red} engage in an argument or use definitive phrases such as "this Violation will not be reversed", Appeals Team members will handle this
1B.2.3
If you are NOT THE CONTROLLER INVOLVED{.red} you must not{.red} respond.

1B.2 Incident Resolution Procedure

<section id="2.1-runway-selection-and-pushback">
<h1><a class="header-anchor" href="#2.1-runway-selection-and-pushback"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 2.1  Runway Selection and Pushback</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p><strong class="red">ALL</strong> available runways <strong class="red">should</strong> be used at <strong class="red">ALL</strong> times <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.1" class="documentation-content-link">4.1.1</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="runway-selection">
<h2><a class="header-anchor" href="#runway-selection"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Runway Selection</h2>
<section class="reference"></section>
<section id="2.1.1">
<h3><a class="header-anchor" href="#2.1.1">2.1.1</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> familiarize themselves with the taxiway layout before opening, this includes knowing what the largest aircraft type that can be accepted is, based on if it can physically maneuver without restricting traffic flow <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.6" class="documentation-content-link">4.1.6</a> below)</em>. Once open, liaison <strong class="red">must</strong> be made with the other Controllers to determine runway selection for departures and arrivals, as well as scanning where traffic currently is within the layout of the airport.</p>
</section>
</section>
<section id="2.1.2">
<h3><a class="header-anchor" href="#2.1.2">2.1.2</a></h3>
<section class="reference">
<p>The color of the runways (i.e. green, amber and red) are for guidance only. You <strong class="red">must</strong> look at the METAR (Meteorological Aerodrome Report) to determine the Headwind or Tailwind Component (H/TWC) for a particular runway. You <strong class="red">should</strong> also look at the TAF (Terminal Aerodrome Forecast), which will provide a trend of the expected wind over the coming hours. Controllers <strong class="red">should</strong> avoid switching runways as much as possible as this creates delays. Most aircraft can land with a TWC of up to 10kts. Therefore, runway changes <strong class="red">should</strong> be avoided until this point if at all possible.</p>
</section>
</section>
</section>
<section id="pushback">
<h2><a class="header-anchor" href="#pushback"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Pushback</h2>
<section class="reference"></section>
<section id="2.1.3">
<h3><a class="header-anchor" href="#2.1.3">2.1.3</a></h3>
<section class="reference">
<p>When issuing pushback to an aircraft, you <strong class="red">must</strong> check that the area is clear, if it isn’t, the use of &quot;hold position&quot; <strong class="red">must</strong> be used (a reminder can be set to avoid forgetting about the aircraft or if it is very busy). Take note, by looking at the strips; the oldest &quot;hold position&quot; command would have been sent to the bottom of the tab providing useful reference as to who requested pushback first.</p>
</section>
</section>
<section id="2.1.4">
<h3><a class="header-anchor" href="#2.1.4">2.1.4</a></h3>
<section class="reference">
<p>In addition to this, the Controller <strong class="red">should</strong> check that the request is valid i.e. is the aircraft capable of pushback? Is the aircraft parked in a position that requires pushback?</p>
</section>
</section>
<section id="2.1.5">
<h3><a class="header-anchor" href="#2.1.5">2.1.5</a></h3>
<section class="reference">
<p>The use of &quot;expect runway xx&quot; <strong class="red">should</strong> be used if the Controller deems it necessary for the aircraft to face a particular direction for pushback (to promote efficiency); however, it is not required for each pushback clearance.</p>
</section>
</section>
</section>


2.1  Runway Selection and Pushback

Tip

: ALL{.red} available runways should{.red} be used at ALL{.red} times (see 4.1.1 below)

Runway Selection

2.1.1

Controllers must{.red} familiarize themselves with the taxiway layout before opening, this includes knowing what the largest aircraft type that can be accepted is, based on if it can physically maneuver without restricting traffic flow (see 4.1.6 below). Once open, liaison must{.red} be made with the other Controllers to determine runway selection for departures and arrivals, as well as scanning where traffic currently is within the layout of the airport.

2.1.2

The color of the runways (i.e. green, amber and red) are for guidance only. You must{.red} look at the METAR (Meteorological Aerodrome Report) to determine the Headwind or Tailwind Component (H/TWC) for a particular runway. You should{.red} also look at the TAF (Terminal Aerodrome Forecast), which will provide a trend of the expected wind over the coming hours. Controllers should{.red} avoid switching runways as much as possible as this creates delays. Most aircraft can land with a TWC of up to 10kts. Therefore, runway changes should{.red} be avoided until this point if at all possible.

Pushback

2.1.3

When issuing pushback to an aircraft, you must{.red} check that the area is clear, if it isn’t, the use of "hold position" must{.red} be used (a reminder can be set to avoid forgetting about the aircraft or if it is very busy). Take note, by looking at the strips; the oldest "hold position" command would have been sent to the bottom of the tab providing useful reference as to who requested pushback first.

2.1.4

In addition to this, the Controller should{.red} check that the request is valid i.e. is the aircraft capable of pushback? Is the aircraft parked in a position that requires pushback?

2.1.5

The use of "expect runway xx" should{.red} be used if the Controller deems it necessary for the aircraft to face a particular direction for pushback (to promote efficiency); however, it is not required for each pushback clearance.

2.1 Runway Selection and Pushback

<section id="2.2-taxi-and-use-of-give-way">
<h1><a class="header-anchor" href="#2.2-taxi-and-use-of-give-way"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 2.2  Taxi and Use of Give Way</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Send aircraft to the closest runway in use if possible (traffic and aircraft performance permitting)</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="2.2.1">
<h3><a class="header-anchor" href="#2.2.1">2.2.1</a></h3>
<section class="reference">
<p>Active ground monitoring is required with use of the &quot;give way&quot; command when needed. In addition, Controllers <strong class="red">must</strong> monitor for runway incursions.</p>
</section>
</section>
<section id="2.2.2">
<h3><a class="header-anchor" href="#2.2.2">2.2.2</a></h3>
<section class="reference">
<p>&quot;Taxi to RWYXX, contact tower when ready&quot; and &quot;Taxi to Parking&quot; are the default commands that <strong class="red">must</strong> be used by Controllers for the purposes of departing/arriving aircraft. In addition to this, Controllers have Progressive Taxi Instructions to assist with ground movement including one way systems, potential conflicts and intersection departures. Controllers <strong class="red">should</strong> take note that <strong class="red">VERY CLOSE MONITORING</strong> is required when using this tool and therefore <strong class="red">should</strong> only use it when absolutely necessary. Before it’s used, Controllers <strong class="red">should</strong> send &quot;Expect Progressive Taxi Instructions&quot; to the aircraft in question (although this may not always be possible), once this is done the following commands are available:</p>
<ul>
<li>
<p>Cross runway XX</p>
</li>
<li>
<p>Turn left/right next taxiway</p>
</li>
<li>
<p>Continue straight ahead</p>
</li>
<li>
<p>Make 180 (Controllers <strong class="red">must</strong> ensure that the aircraft has the space required to make a 180 degree turn on the taxiway)</p>
</li>
<li>
<p>Follow aircraft ahead</p>
</li>
<li>
<p>Already cleared to cross</p>
</li>
</ul>
<p>Once the Progressive Taxi Instructions are no longer required, the Controller <strong class="red">must</strong> send ‘Continue Taxi at your discretion’.</p>
</section>
</section>
<section id="2.2.3">
<h3><a class="header-anchor" href="#2.2.3">2.2.3</a></h3>
<section class="reference">
<p>If an aircraft requests frequency change after being issued &quot;taxi to RWYXX, contact tower when ready&quot; (commonly encountered when the aircraft is holding short of the runway), a &quot;frequency change already sent&quot; message <strong class="red">should</strong> be used. Sometimes the pilots do not realise that the previous command gave them permission to change frequency.</p>
</section>
</section>


2.2  Taxi and Use of Give Way
Tip
: Send aircraft to the closest runway in use if possible (traffic and aircraft performance permitting)
2.2.1
Active ground monitoring is required with use of the "give way" command when needed. In addition, Controllers must{.red} monitor for runway incursions.
2.2.2
"Taxi to RWYXX, contact tower when ready" and "Taxi to Parking" are the default commands that must{.red} be used by Controllers for the purposes of departing/arriving aircraft. In addition to this, Controllers have Progressive Taxi Instructions to assist with ground movement including one way systems, potential conflicts and intersection departures. Controllers should{.red} take note that VERY CLOSE MONITORING{.red} is required when using this tool and therefore should{.red} only use it when absolutely necessary. Before it’s used, Controllers should{.red} send "Expect Progressive Taxi Instructions" to the aircraft in question (although this may not always be possible), once this is done the following commands are available:
 Cross runway XX
 Turn left/right next taxiway
 Continue straight ahead
 Make 180 (Controllers must{.red} ensure that the aircraft has the space required to make a 180 degree turn on the taxiway)
 Follow aircraft ahead
 Already cleared to cross
Once the Progressive Taxi Instructions are no longer required, the Controller must{.red} send ‘Continue Taxi at your discretion’.
2.2.3
If an aircraft requests frequency change after being issued "taxi to RWYXX, contact tower when ready" (commonly encountered when the aircraft is holding short of the runway), a "frequency change already sent" message should{.red} be used. Sometimes the pilots do not realise that the previous command gave them permission to change frequency.

2.2 Taxi and Use of Give Way

<section id="2.3-runway-crossing">
<h1><a class="header-anchor" href="#2.3-runway-crossing"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 2.3  Runway Crossing</h1>
<section class="reference"></section>
<section id="2.3.1">
<h3><a class="header-anchor" href="#2.3.1">2.3.1</a></h3>
<section class="reference">
<p>For runway crossings, the runway <strong class="red">must</strong> be referred to in the direction it is being used, regardless of the aircraft position or what the pilot requests <em>(see <a href="/guide/atc-manual/2.-ground/2.3-runway-crossing#2.3.4" class="documentation-content-link">2.3.4</a> below for exceptions)</em>. For example, if a pilot is by the threshold of RWY36, but the other end is being used for departures and arrivals, the pilot <strong class="red">must</strong> be instructed to cross RWY18, not RWY36.</p>
</section>
</section>
<section id="2.3.2">
<h3><a class="header-anchor" href="#2.3.2">2.3.2</a></h3>
<section class="reference">
<p>The crossing <strong class="red">must</strong> only be issued when the appropriate spacing exits to allow for the traffic to cross and clear the runway prior to the arriving traffic crossing the runway threshold. In addition, coordination with the Tower Controller is required to ensure another aircraft is not cleared for take-off.</p>
</section>
</section>
<section id="2.3.3">
<h3><a class="header-anchor" href="#2.3.3">2.3.3</a></h3>
<section class="reference">
<p>Anticipated runway crossings are encouraged and <strong class="red">should</strong> be used rather than waiting for the pilot to request it. If you see the runway crossing is required, issue it in advance if traffic permits.</p>
</section>
</section>
<section id="2.3.4">
<h3><a class="header-anchor" href="#2.3.4">2.3.4</a></h3>
<section class="reference">
<p>If the taxiways are not directly aligned with each other, then a back-taxi instruction <strong class="red">must</strong> be used instead of a runway crossing command as the pilot will have to taxi on the runway before exiting. In this case, the runway must be referred to in the direction that the Controller wants the aircraft to back-taxi in (however progressive taxi commands may be used in addition to this to ensure the aircraft exits at the appropriate taxiway).</p>
</section>
</section>
</section>


2.3  Runway Crossing

2.3.1

For runway crossings, the runway must{.red} be referred to in the direction it is being used, regardless of the aircraft position or what the pilot requests (see 2.3.4 below for exceptions). For example, if a pilot is by the threshold of RWY36, but the other end is being used for departures and arrivals, the pilot must{.red} be instructed to cross RWY18, not RWY36.

2.3.2

The crossing must{.red} only be issued when the appropriate spacing exits to allow for the traffic to cross and clear the runway prior to the arriving traffic crossing the runway threshold. In addition, coordination with the Tower Controller is required to ensure another aircraft is not cleared for take-off.

2.3.3

Anticipated runway crossings are encouraged and should{.red} be used rather than waiting for the pilot to request it. If you see the runway crossing is required, issue it in advance if traffic permits.

2.3.4

If the taxiways are not directly aligned with each other, then a back-taxi instruction must{.red} be used instead of a runway crossing command as the pilot will have to taxi on the runway before exiting. In this case, the runway must be referred to in the direction that the Controller wants the aircraft to back-taxi in (however progressive taxi commands may be used in addition to this to ensure the aircraft exits at the appropriate taxiway).

2.3 Runway Crossing

<section id="3.1-separation">
<h1><a class="header-anchor" href="#3.1-separation"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.1  Separation</h1>
<section class="reference"></section>
<section id="3.1.1">
<h3><a class="header-anchor" href="#3.1.1">3.1.1</a></h3>
<section class="reference">
<p>The table below outlines the separation requirements that <strong class="red">must</strong> be applied to <strong class="red">ALL</strong> aircraft:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Type</th>
<th>Rule</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Type">Departure / Departure</td>
<td data-label="Rule">The first aircraft <strong class="red">must</strong> be airborne before the second aircraft* commences the take-off roll</td>
</tr>
<tr>
<td data-label="Type">Arrival / Arrival</td>
<td data-label="Rule">The first aircraft <strong class="red">must</strong> have vacated the runway before the second aircraft crosses the threshold</td>
</tr>
<tr>
<td data-label="Type">Departure / Arrival</td>
<td data-label="Rule">The first aircraft <strong class="red">must</strong> be airborne before the second aircraft crosses the threshold</td>
</tr>
<tr>
<td data-label="Type">Intersecting</td>
<td data-label="Rule">Arriving/departing aircraft <strong class="red">must</strong> be beyond the runway intersection prior to a departure beginning it's takeoff roll or an arrival crossing the threshold on an intersecting runway</td>
</tr>
</tbody>
</table>
<p>*In addition, aircraft type <strong class="red">should</strong> be taken into account, e.g. if the first aircraft to depart is a Cessna 172, and the second aircraft is a Boeing 737; it is likely the 737 will catch up with the C172 very quickly if minimum separation rules are applied, therefore time <strong class="red">should</strong> be added before the second departure to allow for this</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-separation.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-separation@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-separation@3x.jpg 3x" alt="Image 3.1.1.1 - Tower Separation" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.1.1.1 - Tower Separation</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="3.1.2">
<h3><a class="header-anchor" href="#3.1.2">3.1.2</a></h3>
<section class="reference">
<p>Anticipation is encouraged and <strong class="red">should</strong> be used when appropriate, for example if a Boeing 737 has already been cleared for take-off and is rolling, rather than issuing a LUAW clearance to the next aircraft, ask yourself if issuing a take-off clearance is appropriate based on the assumption that the first aircraft will be airborne by the time the second aircraft is ready to roll <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.3" class="documentation-content-link">3.2.3</a> below).</em></p>
</section>
</section>
<section id="3.1.3">
<h3><a class="header-anchor" href="#3.1.3">3.1.3</a></h3>
<section class="reference">
<p>If at any time, separation is likely to be lost, the Controller <strong class="red">must</strong> be proactive. This is particularly important with a Departure / Arrival sequence, the arrival can be sent around but consideration <strong class="red">should</strong> also be made as to whether or not the departure should have its &quot;take-off clearance cancelled&quot; to prevent the departing traffic climbing into the traffic that is initiating the missed approach <em>(see <a href="/guide/atc-manual/3.-tower/3.5-exit-runway-go-around#3.5.4" class="documentation-content-link">3.5.4</a> below).</em></p>
</section>
</section>
<section id="3.1.4">
<h3><a class="header-anchor" href="#3.1.4">3.1.4</a></h3>
<section class="reference">
<p>Most commercial aircraft approach speeds are between 120-150kts. If a Controller needs more separation the use of &quot;maintain slowest practical speed&quot; can be utilized, however this <strong class="red">should not</strong> be used within 4 miles to touchdown as it is likely the aircraft is already at its final approach speed. In addition, the Controller <strong class="red">should</strong> also look at the groundspeed (GS)/indicated airspeed (IAS) of the aircraft in question before sending this command as the aircraft could already be at their final approach speed. Regardless of aircraft position, if an aircraft IAS is excessive then this command can be useful however it is important to take note of two points:</p>
<ul>
<li>if the aircraft is close in, it may already be too late and a go-around might be the only option left</li>
<li>try to avoid slowing aircraft down too far out if you have a Radar Controller present as they may have a line of aircraft on approach and it could have a detrimental effect to their spacing (if you need more space and a Radar Controller is present, tell them - <em>see <a href="/guide/atc-manual/3.-tower/3.6-tower-working-with-radar#3.6.1" class="documentation-content-link">3.6.1</a> below)</em></li>
</ul>
</section>
</section>
</section>


3.1  Separation
3.1.1
The table below outlines the separation requirements that must{.red} be applied to ALL{.red} aircraft:
| Type                  | Rule                                                         |
| --------------------- | ------------------------------------------------------------ |
| Departure / Departure | The first aircraft must{.red} be airborne before the second aircraft* commences the take-off roll |
| Arrival / Arrival     | The first aircraft must{.red} have vacated the runway before the second aircraft crosses the threshold |
| Departure / Arrival   | The first aircraft must{.red} be airborne before the second aircraft crosses the threshold |
| Intersecting          | Arriving/departing aircraft must{.red} be beyond the runway intersection prior to a departure beginning it's takeoff roll or an arrival crossing the threshold on an intersecting runway |
In addition, aircraft type should{.red} be taken into account, e.g. if the first aircraft to depart is a Cessna 172, and the second aircraft is a Boeing 737; it is likely the 737 will catch up with the C172 very quickly if minimum separation rules are applied, therefore time should*{.red} be added before the second departure to allow for this
Image 3.1.1.1 - Tower Separation
3.1.2
Anticipation is encouraged and should{.red} be used when appropriate, for example if a Boeing 737 has already been cleared for take-off and is rolling, rather than issuing a LUAW clearance to the next aircraft, ask yourself if issuing a take-off clearance is appropriate based on the assumption that the first aircraft will be airborne by the time the second aircraft is ready to roll (see 3.2.3 below).
3.1.3
If at any time, separation is likely to be lost, the Controller must{.red} be proactive. This is particularly important with a Departure / Arrival sequence, the arrival can be sent around but consideration should{.red} also be made as to whether or not the departure should have its "take-off clearance cancelled" to prevent the departing traffic climbing into the traffic that is initiating the missed approach (see 3.5.4 below).
3.1.4
Most commercial aircraft approach speeds are between 120-150kts. If a Controller needs more separation the use of "maintain slowest practical speed" can be utilized, however this should not{.red} be used within 4 miles to touchdown as it is likely the aircraft is already at its final approach speed. In addition, the Controller should{.red} also look at the groundspeed (GS)/indicated airspeed (IAS) of the aircraft in question before sending this command as the aircraft could already be at their final approach speed. Regardless of aircraft position, if an aircraft IAS is excessive then this command can be useful however it is important to take note of two points:
if the aircraft is close in, it may already be too late and a go-around might be the only option left
try to avoid slowing aircraft down too far out if you have a Radar Controller present as they may have a line of aircraft on approach and it could have a detrimental effect to their spacing (if you need more space and a Radar Controller is present, tell them - see 3.6.1 below)

3.1 Separation

<section id="3.2-departures">
<h1><a class="header-anchor" href="#3.2-departures"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.2  Departures</h1>
<section class="reference"></section>
<section id="hold-short">
<h2><a class="header-anchor" href="#hold-short"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Hold Short</h2>
<section class="reference"></section>
<section id="3.2.1">
<h3><a class="header-anchor" href="#3.2.1">3.2.1</a></h3>
<section class="reference">
<p>If an aircraft requests take-off and you cannot clear them or issue a LUAW command, then the &quot;hold short&quot; command <strong class="red">must</strong> be used, other commands such as &quot;standby&quot; are not appropriate.</p>
</section>
</section>
</section>
<section id="departure-sequence">
<h2><a class="header-anchor" href="#departure-sequence"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Departure Sequence</h2>
<section class="reference"></section>
<section id="3.2.2">
<h3><a class="header-anchor" href="#3.2.2">3.2.2</a></h3>
<section class="reference">
<p>Controllers can utilize the Departure Sequence menu if they wish to provide sequence information to aircraft that are ready for departure (particularly useful when aircraft are confused who is next due to factors such as taxiway layout). The use of &quot;Hold Short&quot; <strong class="red">must</strong> always be used if the aircraft is number 1 for departure, or if the Controller is unsure on the sequence number - however in any other circumstance the Controller can elect to inform the aircraft of their departure sequence if they want to. In addition, aircraft do not need to be first in line to announce &quot;ready for departure&quot; (and may also utilize the &quot;in sequence&quot; message) - this is useful for planning purposes and especially when Intersection Departures are in use <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.5" class="documentation-content-link">3.2.5</a> below)</em>.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Any aircraft that is instructed to LUAW or cleared for take-off is no longer considered in the departure sequence - therefore the next aircraft at the hold short line is now considered number 1 for departure</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="line-up-%26-wait-(luaw)">
<h2><a class="header-anchor" href="#line-up-%26-wait-(luaw)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Line Up &amp; Wait (LUAW)</h2>
<section class="reference"></section>
<section id="3.2.3">
<h3><a class="header-anchor" href="#3.2.3">3.2.3</a></h3>
<section class="reference">
<p>LUAW is a useful tool to have an aircraft on the runway ready for an imminent departure once separation rules are satisfied <em>(see <a href="/guide/atc-manual/3.-tower/3.1-separation#3.1-separation" class="documentation-content-link">3.1</a> above)</em>. But anticipated separation <strong class="red">should</strong> also be taken into account, especially with departure / departure sequences. If the first aircraft is already rolling, ask yourself how long it will take the second aircraft to line up on the runway and commence their take-off roll. If the assumption can be made that the first aircraft will be airborne, then you can save yourself the extra command and just clear the next aircraft for take-off, however consideration <strong class="red">should</strong> be given to the expected climb speed of the preceding aircraft <em>(see <a href="/guide/atc-manual/3.-tower/3.1-separation#3.1.1" class="documentation-content-link">3.1.1</a> above)</em>. Controllers can issue the LUAW command to more than one aircraft provided it will not compromise the integrity of the first aircraft that is due to depart.</p>
</section>
</section>
</section>
<section id="back-taxi">
<h2><a class="header-anchor" href="#back-taxi"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Back-Taxi</h2>
<section class="reference"></section>
<section id="3.2.4">
<h3><a class="header-anchor" href="#3.2.4">3.2.4</a></h3>
<section class="reference">
<p>If the only option to access full length of the runway is to back-taxi, Controllers <strong class="red">should</strong> issue a back-taxi command, thus allowing pilots to decide how much runway they require for departure. It is important to note that back-taxi is pilot discretion, and therefore even with clearance to LUAW or take-off, pilots may elect to back-taxi. Controllers <strong class="red">should</strong> be proactive by planning for the worst case scenario in terms of separation, and in particular; <strong class="red">should</strong> expect the aircraft to back-taxi no faster than normal taxiing speeds.</p>
</section>
</section>
</section>
<section id="intersection-departures">
<h2><a class="header-anchor" href="#intersection-departures"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Intersection Departures</h2>
<section class="reference"></section>
<section id="3.2.5">
<h3><a class="header-anchor" href="#3.2.5">3.2.5</a></h3>
<section class="reference">
<p>Intersection departures are a great method in which to optimize the departure sequence, and thus <strong class="red">must</strong> be utilized unless it blocks the only taxiway for aircraft to access full length <strong class="red">AND</strong> will affect the departure/arrival flow rate (if both these conditions are not met, they <strong class="red">must</strong> be allowed). Controllers <strong class="red">should not</strong> view intersection departures as ‘queue jumping’, but instead use it to their advantage to provide an expeditious service. For example, a gap between two arrivals that looks tight for a commercial aircraft to depart in, might be suitable for a fast jet? The flexibility it offers the Controller is a tool, not a hindrance.</p>
</section>
</section>
</section>
<section id="take-off">
<h2><a class="header-anchor" href="#take-off"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Take-Off</h2>
<section class="reference"></section>
<section id="3.2.6">
<h3><a class="header-anchor" href="#3.2.6">3.2.6</a></h3>
<section class="reference">
<p>The use of &quot;Immediate Take-Off&quot; <strong class="red">should</strong> only be reserved for Departure / Arrival separation where it is highly likely that separation could be lost if the departure does not depart expeditiously. This is normally when aircraft are on final with a range of 2nm or less, however it is also dependent on the final approach speed of the aircraft in question, and the type of aircraft to depart, i.e. 777 vs. 737 <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.7" class="documentation-content-link">3.2.7</a> below)</em>.</p>
</section>
</section>
<section id="3.2.7">
<h3><a class="header-anchor" href="#3.2.7">3.2.7</a></h3>
<section class="reference">
<p>The range displayed in nm on an aircraft tag is with reference to the tower, not the runway threshold that the aircraft is landing on. Controllers are encouraged to work out what the aircraft range is from the threshold so that they are aware when separation is close. A good way is by looking at the altitude of the aircraft, when aircraft fly a standard 3 degree glideslope, you can expect a range of 2nm from the touchdown to coincide with an altitude of approximately 600ft, assuming an airport elevation of 0ft <em>(see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4" class="documentation-content-link">6.10.4</a> below).</em></p>
</section>
</section>
<section id="3.2.8">
<h3><a class="header-anchor" href="#3.2.8">3.2.8</a></h3>
<section class="reference">
<p>When &quot;Straight Out Dept.&quot; is being broadcast in the current ATIS <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.6" class="documentation-content-link">4.1.6</a> below)</em>, the use of &quot;fly runway heading until at or above XXXXft&quot; <strong class="red">should</strong> be used with every take-off command sent as a final reminder to the departing aircraft; the options available include 1000ft, 3000ft and 5000ft AAL (rounded down to the nearest 500ft). Aircraft climb rates can vary significantly, thus; although aircraft have been instructed to maintain runway heading until a specific altitude, with &quot;Straight Out Dept.&quot; selected in the ATIS, aircraft cannot deviate from runway heading until the departing aircraft is clear of any conflict.</p>
</section>
</section>
<section id="3.2.9">
<h3><a class="header-anchor" href="#3.2.9">3.2.9</a></h3>
<section class="reference">
<p>SIDs often involve turns away from the airport shortly after departure; due to this, if &quot;Straight Out Dept.&quot; is being utilized, Controllers <strong class="red">should</strong> note that this may prevent pilots from flying the selected SID <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.6" class="documentation-content-link">4.1.6</a> and <a href="/guide/atc-manual/6.-radar/6.4-departure-check-in#6.4.3" class="documentation-content-link">6.4.3</a> below)</em>.</p>
</section>
</section>
</section>


3.2  Departures
Hold Short
3.2.1
If an aircraft requests take-off and you cannot clear them or issue a LUAW command, then the "hold short" command must{.red} be used, other commands such as "standby" are not appropriate.
Departure Sequence
3.2.2
Controllers can utilize the Departure Sequence menu if they wish to provide sequence information to aircraft that are ready for departure (particularly useful when aircraft are confused who is next due to factors such as taxiway layout). The use of "Hold Short" must{.red} always be used if the aircraft is number 1 for departure, or if the Controller is unsure on the sequence number - however in any other circumstance the Controller can elect to inform the aircraft of their departure sequence if they want to. In addition, aircraft do not need to be first in line to announce "ready for departure" (and may also utilize the "in sequence" message) - this is useful for planning purposes and especially when Intersection Departures are in use (see 3.2.5 below).
Tip
: Any aircraft that is instructed to LUAW or cleared for take-off is no longer considered in the departure sequence - therefore the next aircraft at the hold short line is now considered number 1 for departure
Line Up & Wait (LUAW)
3.2.3
LUAW is a useful tool to have an aircraft on the runway ready for an imminent departure once separation rules are satisfied (see 3.1 above). But anticipated separation should{.red} also be taken into account, especially with departure / departure sequences. If the first aircraft is already rolling, ask yourself how long it will take the second aircraft to line up on the runway and commence their take-off roll. If the assumption can be made that the first aircraft will be airborne, then you can save yourself the extra command and just clear the next aircraft for take-off, however consideration should{.red} be given to the expected climb speed of the preceding aircraft (see 3.1.1 above). Controllers can issue the LUAW command to more than one aircraft provided it will not compromise the integrity of the first aircraft that is due to depart.
Back-Taxi
3.2.4
If the only option to access full length of the runway is to back-taxi, Controllers should{.red} issue a back-taxi command, thus allowing pilots to decide how much runway they require for departure. It is important to note that back-taxi is pilot discretion, and therefore even with clearance to LUAW or take-off, pilots may elect to back-taxi. Controllers should{.red} be proactive by planning for the worst case scenario in terms of separation, and in particular; should{.red} expect the aircraft to back-taxi no faster than normal taxiing speeds.
Intersection Departures
3.2.5
Intersection departures are a great method in which to optimize the departure sequence, and thus must{.red} be utilized unless it blocks the only taxiway for aircraft to access full length AND{.red} will affect the departure/arrival flow rate (if both these conditions are not met, they must{.red} be allowed). Controllers should not{.red} view intersection departures as ‘queue jumping’, but instead use it to their advantage to provide an expeditious service. For example, a gap between two arrivals that looks tight for a commercial aircraft to depart in, might be suitable for a fast jet? The flexibility it offers the Controller is a tool, not a hindrance.
Take-Off
3.2.6
The use of "Immediate Take-Off" should{.red} only be reserved for Departure / Arrival separation where it is highly likely that separation could be lost if the departure does not depart expeditiously. This is normally when aircraft are on final with a range of 2nm or less, however it is also dependent on the final approach speed of the aircraft in question, and the type of aircraft to depart, i.e. 777 vs. 737 (see 3.2.7 below).
3.2.7
The range displayed in nm on an aircraft tag is with reference to the tower, not the runway threshold that the aircraft is landing on. Controllers are encouraged to work out what the aircraft range is from the threshold so that they are aware when separation is close. A good way is by looking at the altitude of the aircraft, when aircraft fly a standard 3 degree glideslope, you can expect a range of 2nm from the touchdown to coincide with an altitude of approximately 600ft, assuming an airport elevation of 0ft (see 6.10.4-approach#6.10.4) below).
3.2.8
When "Straight Out Dept." is being broadcast in the current ATIS (see 4.1.6 below), the use of "fly runway heading until at or above XXXXft" should{.red} be used with every take-off command sent as a final reminder to the departing aircraft; the options available include 1000ft, 3000ft and 5000ft AAL (rounded down to the nearest 500ft). Aircraft climb rates can vary significantly, thus; although aircraft have been instructed to maintain runway heading until a specific altitude, with "Straight Out Dept." selected in the ATIS, aircraft cannot deviate from runway heading until the departing aircraft is clear of any conflict.
3.2.9
SIDs often involve turns away from the airport shortly after departure; due to this, if "Straight Out Dept." is being utilized, Controllers should{.red} note that this may prevent pilots from flying the selected SID (see 4.1.6 and 6.4.3 below).

3.2 Departures

<section id="3.3-inbounds">
<h1><a class="header-anchor" href="#3.3-inbounds"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.3 Inbounds</h1>
<section class="reference"></section>
<section id="pattern-entry%2C-sequence-and-clearance">
<h2><a class="header-anchor" href="#pattern-entry%2C-sequence-and-clearance"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Pattern Entry, Sequence and Clearance</h2>
<section class="reference"></section>
<section id="3.3.1">
<h3><a class="header-anchor" href="#3.3.1">3.3.1</a></h3>
<section class="reference">
<p>When there is no Radar Controller present, Tower <strong class="red">must</strong> issue a pattern entry and clearance to <strong class="red">ALL</strong> aircraft as a <strong class="red">MINIMUM</strong>, regardless of what the aircraft uses to check in on the Tower frequency - the use of sequencing will be dependent on traffic <em>(see 3.3.1.1 below)</em>. In addition, Controllers may wish to take into account the aircraft flight plan (in particular the STAR) when issuing the pattern entry, however; traffic flow and common sense <strong class="red">should</strong> also be considered (i.e. if the STAR leads an aircraft into a straight in, but due to traffic it would be better for the aircraft to enter downwind; then Controllers <strong class="red">should</strong> be proactive in managing this).</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-sequencing.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-sequencing@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-tower-sequencing@3x.jpg 3x" alt="Image 3.3.1.1 - Tower Sequencing" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.3.1.1 - Tower Sequencing</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="3.3.2">
<h3><a class="header-anchor" href="#3.3.2">3.3.2</a></h3>
<section class="reference">
<p>If Controllers are unsure on which pattern entry to use (i.e. if the aircraft is still quite far away), then the use of &quot;Continue Inbound&quot; can be sent initially however, Controllers <strong class="red">must</strong> update the inbound aircraft <strong class="red">BEFORE</strong> reaching the pattern with a pattern entry <em>(see <a href="/guide/atc-manual/3.-tower/3.3-inbounds#3.3.1" class="documentation-content-link">3.3.1</a> above)</em>. Similarly, if Controllers are unsure on an aircrafts sequence number, a pattern entry without sequence can be sent, but this <strong class="red">must</strong> be updated when the Controller knows where to fit the aircraft in.</p>
</section>
</section>
</section>
<section id="runway-changes">
<h2><a class="header-anchor" href="#runway-changes"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Runway Changes</h2>
<section class="reference"></section>
<section id="3.3.3">
<h3><a class="header-anchor" href="#3.3.3">3.3.3</a></h3>
<section class="reference">
<p>Controllers <strong class="red">should</strong> try to accommodate aircraft requests for different runways, provided it does not compromise the level of service given to other aircraft</p>
</section>
</section>
<section id="3.3.4">
<h3><a class="header-anchor" href="#3.3.4">3.3.4</a></h3>
<section class="reference">
<p>If a runway change is issued, a new pattern entry and clearance <strong class="red">must</strong> be given (the use of sequencing will be dependent on traffic).</p>
</section>
</section>
</section>
<section id="cleared-for-the-option">
<h2><a class="header-anchor" href="#cleared-for-the-option"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Cleared for the Option</h2>
<section class="reference"></section>
<section id="3.3.5">
<h3><a class="header-anchor" href="#3.3.5">3.3.5</a></h3>
<section class="reference">
<p>If an aircraft is in the pattern &quot;Cleared for the Option&quot; <strong class="red">must</strong> be used as it gives the pilot the option of a landing / touch &amp; go / stop &amp; go or low approach.</p>
</section>
</section>
<section id="3.3.6">
<h3><a class="header-anchor" href="#3.3.6">3.3.6</a></h3>
<section class="reference">
<p>If the aircraft has already been instructed to make left/right traffic from the initial take-off clearance or the previous landing clearance, then the use of &quot;make left/right traffic&quot; is no longer required to be used as it is assumed the pilot will continue with this pattern unless told otherwise. If the pilot is given a new pattern entry or new runway, when clearing for the option, you <strong class="red">must</strong> tell the pilot whether to make left/right traffic.</p>
</section>
</section>
</section>
</section>


3.3 Inbounds
Pattern Entry, Sequence and Clearance
3.3.1
When there is no Radar Controller present, Tower must{.red} issue a pattern entry and clearance to ALL{.red} aircraft as a MINIMUM{.red}, regardless of what the aircraft uses to check in on the Tower frequency - the use of sequencing will be dependent on traffic (see 3.3.1.1 below). In addition, Controllers may wish to take into account the aircraft flight plan (in particular the STAR) when issuing the pattern entry, however; traffic flow and common sense should{.red} also be considered (i.e. if the STAR leads an aircraft into a straight in, but due to traffic it would be better for the aircraft to enter downwind; then Controllers should{.red} be proactive in managing this).
Image 3.3.1.1 - Tower Sequencing
3.3.2
If Controllers are unsure on which pattern entry to use (i.e. if the aircraft is still quite far away), then the use of "Continue Inbound" can be sent initially however, Controllers must{.red} update the inbound aircraft BEFORE{.red} reaching the pattern with a pattern entry (see 3.3.1 above). Similarly, if Controllers are unsure on an aircrafts sequence number, a pattern entry without sequence can be sent, but this must{.red} be updated when the Controller knows where to fit the aircraft in.
Runway Changes
3.3.3
Controllers should{.red} try to accommodate aircraft requests for different runways, provided it does not compromise the level of service given to other aircraft
3.3.4
If a runway change is issued, a new pattern entry and clearance must{.red} be given (the use of sequencing will be dependent on traffic).
Cleared for the Option
3.3.5
If an aircraft is in the pattern "Cleared for the Option" must{.red} be used as it gives the pilot the option of a landing / touch & go / stop & go or low approach.
3.3.6
If the aircraft has already been instructed to make left/right traffic from the initial take-off clearance or the previous landing clearance, then the use of "make left/right traffic" is no longer required to be used as it is assumed the pilot will continue with this pattern unless told otherwise. If the pilot is given a new pattern entry or new runway, when clearing for the option, you must{.red} tell the pilot whether to make left/right traffic.

3.3 Inbounds

<section id="3.4-pattern-work-%2F-transitions-%2F-flight-of-xx">
<h1><a class="header-anchor" href="#3.4-pattern-work-%2F-transitions-%2F-flight-of-xx"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.4  Pattern Work / Transitions / Flight of XX</h1>
<section class="reference"></section>
<section id="pattern-work">
<h2><a class="header-anchor" href="#pattern-work"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Pattern Work</h2>
<section class="reference"></section>
<section id="3.4.1">
<h3><a class="header-anchor" href="#3.4.1">3.4.1</a></h3>
<section class="reference">
<p>The pattern altitude is 1000ft AAL (above aerodrome level) for props and 1500ft AAL for jets. Controllers are encouraged to fly at the airport they intend on controlling at, before opening. Controllers <strong class="red">must</strong> assess the suitability for pattern work by using the following three conditions:</p>
<ul>
<li>Visual Meteorological Conditions (VMC) <strong class="red">must</strong> exist for pattern work to be allowed – for IF only purposes, this is a <strong class="red">MINIMUM</strong> of 3 statute miles (approx. 5000 meters) visibility</li>
<li>Aircraft <strong class="red">must</strong> be able to reasonably fly a standard pattern, if this is not possible due to terrain (such as at KASE, LOWI, NZQN etc), then pattern work <strong class="red">must</strong> be denied</li>
<li>If <strong class="red">CURRENT</strong> traffic levels increase to a level that prevents Controllers from providing an adequate service, pattern work <strong class="red">should</strong> be turned off <strong class="red">TEMPORARILY</strong> - as soon as traffic levels are manageable, Controllers <strong class="red">must</strong> resume pattern work</li>
</ul>
</section>
</section>
</section>
<section id="transitions">
<h2><a class="header-anchor" href="#transitions"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Transitions</h2>
<section class="reference"></section>
<section id="3.4.2">
<h3><a class="header-anchor" href="#3.4.2">3.4.2</a></h3>
<section class="reference">
<p>Aircraft <strong class="red">must</strong> request a transition if passing through the airspace of the Tower Controller unless the aircraft is with the radar facility of that airport. For Infinite Flight, Tower airspace is defined as the most immediate ring/boundary surrounding the airport and up to 5000ft AAL (therefore if the elevation of the airport is 1000ft, the tower’s airspace would be 1000ft – 6000ft).</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/atc-tower-airspace.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/atc-tower-airspace@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/atc-tower-airspace@3x.png 3x" alt="Image 3.3.2.1 - Tower Airspace for KDFW" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.3.2.1 - Tower Airspace for KDFW</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="3.4.3">
<h3><a class="header-anchor" href="#3.4.3">3.4.3</a></h3>
<section class="reference">
<p>A transition <strong class="red">must</strong> only be approved within tower’s airspace (so in the example above, no higher than 6000ft). Separation <strong class="red">must</strong> be applied if the Tower Controller has aircraft in the pattern.</p>
</section>
</section>
<section id="3.4.4">
<h3><a class="header-anchor" href="#3.4.4">3.4.4</a></h3>
<section class="reference">
<p>Using the above example, if the Tower Controller has 2 jet aircraft in the pattern, with an airport elevation of 1000ft, they would be expected to fly the pattern at 2500ft, therefore a transition for another aircraft <strong class="red">must</strong> be given that still allows it to stay within the tower’s airspace (up to 6000ft) but also gives separation to those that are in the pattern. 3000ft would be the minimum altitude that could be used to provide 500ft separation between VFR aircraft, however 1000ft or more is recommended to satisfy IFR separation rules <em>(see <a href="/guide/atc-manual/6.-radar/6.2-separation#6.2-separation" class="documentation-content-link">6.2</a> below)</em>.</p>
</section>
</section>
</section>
<section id="flight-of-xx">
<h2><a class="header-anchor" href="#flight-of-xx"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Flight of XX</h2>
<section class="reference"></section>
<section id="3.4.5">
<h3><a class="header-anchor" href="#3.4.5">3.4.5</a></h3>
<section class="reference">
<p>When controlling aircraft using the ‘Flight of XX’ callsign, you <strong class="red">must</strong> only send commands to the lead aircraft and treat the flight of xx as one aircraft. Separation is the pilot’s responsibility and it is likely that they will be within ½ mile separation of each other during the approach and landing.</p>
</section>
</section>
</section>
</section>


3.4  Pattern Work / Transitions / Flight of XX
Pattern Work
3.4.1
The pattern altitude is 1000ft AAL (above aerodrome level) for props and 1500ft AAL for jets. Controllers are encouraged to fly at the airport they intend on controlling at, before opening. Controllers must{.red} assess the suitability for pattern work by using the following three conditions:
Visual Meteorological Conditions (VMC) must{.red} exist for pattern work to be allowed – for IF only purposes, this is a MINIMUM{.red} of 3 statute miles (approx. 5000 meters) visibility
Aircraft must{.red} be able to reasonably fly a standard pattern, if this is not possible due to terrain (such as at KASE, LOWI, NZQN etc), then pattern work must{.red} be denied
If CURRENT{.red} traffic levels increase to a level that prevents Controllers from providing an adequate service, pattern work should{.red} be turned off TEMPORARILY{.red} - as soon as traffic levels are manageable, Controllers must{.red} resume pattern work
Transitions
3.4.2
Aircraft must{.red} request a transition if passing through the airspace of the Tower Controller unless the aircraft is with the radar facility of that airport. For Infinite Flight, Tower airspace is defined as the most immediate ring/boundary surrounding the airport and up to 5000ft AAL (therefore if the elevation of the airport is 1000ft, the tower’s airspace would be 1000ft – 6000ft).
Image 3.3.2.1 - Tower Airspace for KDFW
3.4.3
A transition must{.red} only be approved within tower’s airspace (so in the example above, no higher than 6000ft). Separation must{.red} be applied if the Tower Controller has aircraft in the pattern.
3.4.4
Using the above example, if the Tower Controller has 2 jet aircraft in the pattern, with an airport elevation of 1000ft, they would be expected to fly the pattern at 2500ft, therefore a transition for another aircraft must{.red} be given that still allows it to stay within the tower’s airspace (up to 6000ft) but also gives separation to those that are in the pattern. 3000ft would be the minimum altitude that could be used to provide 500ft separation between VFR aircraft, however 1000ft or more is recommended to satisfy IFR separation rules (see 6.2 below).
Flight of XX
3.4.5
When controlling aircraft using the ‘Flight of XX’ callsign, you must{.red} only send commands to the lead aircraft and treat the flight of xx as one aircraft. Separation is the pilot’s responsibility and it is likely that they will be within ½ mile separation of each other during the approach and landing.

3.4 Pattern Work / Transitions / Flight of XX

<section id="3.5-exit-runway-%2F-go-around">
<h1><a class="header-anchor" href="#3.5-exit-runway-%2F-go-around"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.5  Exit Runway / Go-Around</h1>
<section class="reference"></section>
<section id="exit-runway">
<h2><a class="header-anchor" href="#exit-runway"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Exit Runway</h2>
<section class="reference"></section>
<section id="3.5.1">
<h3><a class="header-anchor" href="#3.5.1">3.5.1</a></h3>
<section class="reference">
<p>The Exit Runway command <strong class="red">should</strong> be given once the aircraft is at a safe and controlled speed, typically less than 70kts <em>(see <a href="/guide/atc-manual/3.-tower/3.5-exit-runway-go-around#3.5.2" class="documentation-content-link">3.5.2</a> below for exceptions)</em>. The expedite command <strong class="red">should</strong> not be used unnecessarily. Typically aircraft that are within 2nm final or 3nm final if another aircraft is lined up on the runway to depart, would require the use of this.</p>
</section>
</section>
<section id="3.5.2">
<h3><a class="header-anchor" href="#3.5.2">3.5.2</a></h3>
<section class="reference">
<p>Time critical control instructions (e.g. such as a Go-Around instruction) <strong class="red">must</strong> always be prioritized. Therefore, in the absence of an Exit Runway command; aircraft are expected to exit the runway at the first available taxiway once reaching a taxi speed, cross the hold bars and contact Ground Control. If the aircraft does not change frequency, Controllers can issue a &quot;Frequency Change Approved&quot; or &quot;Contact Ground&quot; command when workload permits.</p>
</section>
</section>
<section id="3.5.3">
<h3><a class="header-anchor" href="#3.5.3">3.5.3</a></h3>
<section class="reference">
<p>Where Tower Controllers are controlling multiple runways in close proximity, it is encouraged to utilize the Exit Runway and Hold Short/Cross Runway command. The Tower Controller can then manage the crossing traffic (de-conflicting with departures/arrivals), hand over to the Ground Controller once clear, and ultimately reduce Controller workload.</p>
</section>
</section>
</section>
<section id="go-around">
<h2><a class="header-anchor" href="#go-around"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Go-Around</h2>
<section class="reference"></section>
<section id="3.5.4">
<h3><a class="header-anchor" href="#3.5.4">3.5.4</a></h3>
<section class="reference">
<p>A ‘go-around’ (G/A) can be pilot or Controller initiated and is the procedure used to cancel the approach and/or landing. Controllers <strong class="red">should</strong> try to be proactive when they see a conflict that requires the use of a go-around. When issuing a go-around instruction, the use of &quot;left/right traffic&quot; gives the pilot an indication of the direction you want them to take. No pattern entry is required however, sequencing (as appropriate) and a clearance will be needed. If working with a Radar Controller, you <strong class="red">should</strong> try to let them know that the aircraft is &quot;go-around&quot; traffic so that they can work them into the plan, the aircraft can then be handed over to the Radar Controller unless they are VFR traffic or a prior arrangement has been made between Controllers.</p>
</section>
</section>
</section>
</section>


3.5  Exit Runway / Go-Around
Exit Runway
3.5.1
The Exit Runway command should{.red} be given once the aircraft is at a safe and controlled speed, typically less than 70kts (see 3.5.2 below for exceptions). The expedite command should{.red} not be used unnecessarily. Typically aircraft that are within 2nm final or 3nm final if another aircraft is lined up on the runway to depart, would require the use of this.
3.5.2
Time critical control instructions (e.g. such as a Go-Around instruction) must{.red} always be prioritized. Therefore, in the absence of an Exit Runway command; aircraft are expected to exit the runway at the first available taxiway once reaching a taxi speed, cross the hold bars and contact Ground Control. If the aircraft does not change frequency, Controllers can issue a "Frequency Change Approved" or "Contact Ground" command when workload permits.
3.5.3
Where Tower Controllers are controlling multiple runways in close proximity, it is encouraged to utilize the Exit Runway and Hold Short/Cross Runway command. The Tower Controller can then manage the crossing traffic (de-conflicting with departures/arrivals), hand over to the Ground Controller once clear, and ultimately reduce Controller workload.
Go-Around
3.5.4
A ‘go-around’ (G/A) can be pilot or Controller initiated and is the procedure used to cancel the approach and/or landing. Controllers should{.red} try to be proactive when they see a conflict that requires the use of a go-around. When issuing a go-around instruction, the use of "left/right traffic" gives the pilot an indication of the direction you want them to take. No pattern entry is required however, sequencing (as appropriate) and a clearance will be needed. If working with a Radar Controller, you should{.red} try to let them know that the aircraft is "go-around" traffic so that they can work them into the plan, the aircraft can then be handed over to the Radar Controller unless they are VFR traffic or a prior arrangement has been made between Controllers.

3.5 Exit Runway / Go-Around

<section id="3.6-tower-working-with-radar">
<h1><a class="header-anchor" href="#3.6-tower-working-with-radar"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 3.6  Tower working with Radar</h1>
<section class="reference"></section>
<section id="3.6.1">
<h3><a class="header-anchor" href="#3.6.1">3.6.1</a></h3>
<section class="reference">
<p>Communication is key to ensure that you work together, offering the best possible service. Typically at busy times, the Radar Controllers are trained to use <strong class="red">ALL</strong> the available runways, and offer spacing of 5nm between arrivals to allow for a departure in between. You <strong class="red">should</strong> communicate with the Controller if you are concerned about a departure queue building and need more space but it is likely that the Radar Controller will monitor this and adjust arrivals accordingly. You <strong class="red">must not</strong> dictate to the Radar Controller which runways <strong class="red">should</strong> be used for arrivals vs. departures, <strong class="red">ALL</strong> runways <strong class="red">should</strong> be used <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.1" class="documentation-content-link">4.1.1</a> below)</em>. In addition, once aircraft have been handed over to Tower, runway changes <strong class="red">should</strong> be kept to a minimum for instrument arrivals.</p>
</section>
</section>
<section id="3.6.2">
<h3><a class="header-anchor" href="#3.6.2">3.6.2</a></h3>
<section class="reference">
<p>Pattern work <strong class="red">must</strong> stay with Tower, and <strong class="red">must not</strong> be handed over to the Radar Controller unless it has been decided to deny pattern work; in which case, those aircraft that are in the pattern can be converted into a radar pattern by handing them over to the Radar Controller.</p>
</section>
</section>
<section id="3.6.3">
<h3><a class="header-anchor" href="#3.6.3">3.6.3</a></h3>
<section class="reference">
<p>Below is a table that summarizes when to use pattern entries, sequences and clearances (when Radar is present):</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Approach Type</th>
<th>Pattern Entry</th>
<th>Sequence</th>
<th>Clearance</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Approach Type">ILS/GPS</td>
<td data-label="Pattern Entry">No</td>
<td data-label="Sequence">No</td>
<td data-label="Clearance">Yes</td>
</tr>
<tr>
<td data-label="Approach Type">Radar Vectors</td>
<td data-label="Pattern Entry">Yes</td>
<td data-label="Sequence">If  Req</td>
<td data-label="Clearance">Yes</td>
</tr>
<tr>
<td data-label="Approach Type">Flight Following</td>
<td data-label="Pattern Entry">Yes</td>
<td data-label="Sequence">If  Req</td>
<td data-label="Clearance">Yes</td>
</tr>
<tr>
<td data-label="Approach Type">Visual</td>
<td data-label="Pattern Entry">No</td>
<td data-label="Sequence">If  Req</td>
<td data-label="Clearance">Yes</td>
</tr>
</tbody>
</table>
<p><em>Note: &quot;if req&quot; means that unless the aircraft is number 1, a sequence is <strong>required</strong> before issuing the clearance</em></p>
</section>
</section>
</section>


3.6  Tower working with Radar
3.6.1
Communication is key to ensure that you work together, offering the best possible service. Typically at busy times, the Radar Controllers are trained to use ALL{.red} the available runways, and offer spacing of 5nm between arrivals to allow for a departure in between. You should{.red} communicate with the Controller if you are concerned about a departure queue building and need more space but it is likely that the Radar Controller will monitor this and adjust arrivals accordingly. You must not{.red} dictate to the Radar Controller which runways should{.red} be used for arrivals vs. departures, ALL{.red} runways should{.red} be used (see 4.1.1 below). In addition, once aircraft have been handed over to Tower, runway changes should{.red} be kept to a minimum for instrument arrivals.
3.6.2
Pattern work must{.red} stay with Tower, and must not{.red} be handed over to the Radar Controller unless it has been decided to deny pattern work; in which case, those aircraft that are in the pattern can be converted into a radar pattern by handing them over to the Radar Controller.
3.6.3
Below is a table that summarizes when to use pattern entries, sequences and clearances (when Radar is present):
| Approach Type    | Pattern Entry | Sequence | Clearance |
| ---------------- | ------------- | -------- | --------- |
| ILS/GPS          | No            | No       | Yes       |
| Radar Vectors    | Yes           | If  Req  | Yes       |
| Flight Following | Yes           | If  Req  | Yes       |
| Visual           | No            | If  Req  | Yes       |
Note: "if req" means that unless the aircraft is number 1, a sequence is required before issuing the clearance

3.6 Tower Working with Radar

<section id="4.1-atis">
<h1><a class="header-anchor" href="#4.1-atis"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 4.1 ATIS</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Controllers <strong class="red">should</strong> avoid adding too many REMARKS and NOTAMS into a single ATIS as this will dilute the message – Controllers <strong class="red">should</strong> ask themselves what the most important messages are, and prioritise as required <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.6" class="documentation-content-link">4.1.6</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="4.1.1">
<h3><a class="header-anchor" href="#4.1.1">4.1.1</a></h3>
<section class="reference">
<p>The Automatic Terminal Information Service, known as ATIS; enables the Controllers to broadcast the current weather as well as REMARKS and NOTAMS for pilots to be aware of. <strong class="red">ALL</strong> available runways <strong class="red">should</strong> be used – one runway for departures and another runway for arrivals <strong class="red">should</strong> be avoided if possible. Controllers may however, be exposed to an airport where terrain, airport layout or weather prevents <strong class="red">ALL</strong> runways from being used; in this case it is acceptable to not use <strong class="red">ALL</strong> runways (if there are any doubts as to what strategy <strong class="red">should</strong> be used, Controllers <strong class="red">should</strong> raise this with a Supervisor or above for guidance).</p>
</section>
</section>
<section id="4.1.2">
<h3><a class="header-anchor" href="#4.1.2">4.1.2</a></h3>
<section class="reference">
<p>Pattern work <strong class="red">must</strong> be denied if the weather conditions, terrain or traffic are not suitable <em>(see <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4-pattern-work-%2F-transitions-%2F-flight-of-xx" class="documentation-content-link">3.4</a> above)</em></p>
</section>
</section>
<section id="4.1.3">
<h3><a class="header-anchor" href="#4.1.3">4.1.3</a></h3>
<section class="reference">
<p>A letter of the Phonetic Alphabet is used to identify an ATIS transmission, this letter is then relayed between pilots and Controllers to ensure everyone is operating under the same airfield information. At any time, if the current ATIS does not reflect the current situation (including changes in weather or SIDs/STARs in use), Controllers <strong class="red">must</strong> change the ATIS without delay and ensure real time coordination with the other Controllers involved. As a <strong class="red">MINIMUM</strong>, the ATIS must be updated at least once an hour. In addition, a broadcast <strong class="red">must</strong> be made on Ground/Tower/Radar to ensure pilots check the new ATIS.</p>
</section>
</section>
<section id="4.1.4">
<h3><a class="header-anchor" href="#4.1.4">4.1.4</a></h3>
<section class="reference">
<p>The letters used when updating the ATIS <strong class="red">must</strong> be in alphabetical order and typically starts at Alpha unless the Controller has just taken over from another Controller.</p>
</section>
</section>
<section id="4.1.5">
<h3><a class="header-anchor" href="#4.1.5">4.1.5</a></h3>
<section class="reference">
<p>The facility to open multiple Ground/Tower/Radar frequencies exist at some airports. This can be useful when managing busy traffic. If this is to be used Controllers <strong class="red">must</strong> ensure that the ATIS is updated to reflect this (i.e. which frequency to contact, from which direction), prior coordination is made with the other Controllers; and during the controlling session, the IFATC Discord Channels are used to provide a good service.</p>
</section>
</section>
<section id="4.1.6">
<h3><a class="header-anchor" href="#4.1.6">4.1.6</a></h3>
<section class="reference">
<p>The table below highlights when certain REMARKS or NOTAMS <strong class="red">should</strong> be used:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>REMARK  / NOTAM</th>
<th>When to be used?</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="REMARK  / NOTAM">No Intersection Dept.</td>
<td data-label="When to be used?">Intersection departures <strong class="red">must</strong> always be allowed unless it blocks the only taxiway for aircraft to access full length <strong class="red">AND</strong> will affect the departure/arrival flow rate <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.5" class="documentation-content-link">3.2.5</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">No Pattern Work</td>
<td data-label="When to be used?">Weather below VMC? Terrain prevents a standard pattern from being flown? <strong class="red">CURRENT</strong> traffic levels will cause a drop in service standards? When 1 of these conditions is met, No Pattern Work <strong class="red">must</strong> be used <em>(see <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.1" class="documentation-content-link">3.4.1</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Flow Control</td>
<td data-label="When to be used?">Aircraft can expect a delay for departure if the Controller is trying to limit departing traffic (this could be due to aircraft all heading for the same destination).</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Long Taxi</td>
<td data-label="When to be used?">If the runways in use mean that some aircraft can expect a long taxi.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Gate Hold</td>
<td data-label="When to be used?">The use of hold position <em>(see <a href="/guide/atc-manual/2.-ground/2.1-runway-selection-and-pushback#2.1.3" class="documentation-content-link">2.1.3</a> above)</em> <strong class="red">should</strong> be favored but if a long line of  departures needs to be cleared and you have limited space on the taxiways,  gate hold can be used (it <strong class="red">should</strong> be limited to a maximum of 10 minutes).</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">No Light Aircraft</td>
<td data-label="When to be used?">This command <strong class="red">must</strong> be used at <strong class="red">ALL</strong> times for large airports that do not accept light aircraft IRL (e.g. EGLL, OMDB, VHHH etc). In addition, it is important to note that this command is not traffic dependent – a consistent message <strong class="red">must</strong> be sent that there are other, more appropriate airports for light* aircraft.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Rolling Dept.</td>
<td data-label="When to be used?">To expedite departures – when aircraft are cleared for take-off they will be expected to line up and start their take-off roll immediately. The LUAW command <strong class="red">must not</strong> be used when this is in use.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">FPL Required</td>
<td data-label="When to be used?">Only to be used when weather is below VMC minima <em>(see <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.1" class="documentation-content-link">3.4.1</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Straight Out Dept. **</td>
<td data-label="When to be used?">Runway heading <strong class="red">must</strong> be flown after departure until no conflict exists <strong class="red">AND</strong> the altitude specified by the Tower Controller has been met or exceeded <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.8" class="documentation-content-link">3.2.8</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Mult. Freq. In Use</td>
<td data-label="When to be used?"><em>(See <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.5" class="documentation-content-link">4.1.5</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Check Forum</td>
<td data-label="When to be used?">Only to be used when referring pilots to special instructions on the IFC pages e.g. VARB Summit.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">SID/STAR Use Rcmd***</td>
<td data-label="When to be used?">This command <strong class="red">should</strong> be used when light to moderate traffic exists and SID/STAR use is not essential for traffic management <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.7" class="documentation-content-link">4.1.7</a> below)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">SID/STAR Use Req***</td>
<td data-label="When to be used?">This command <strong class="red">should</strong> be used when heavy traffic exists and SID/STAR use is essential for traffic management <strong class="red">OR</strong> for events and/or main hub airports  <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.7" class="documentation-content-link">4.1.7</a> below)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Event</td>
<td data-label="When to be used?">IF LLC sponsored events only.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Size Restrictions</td>
<td data-label="When to be used?">When any aircraft cannot be accommodated because their size will restrict airport flow (i.e. block taxiways or ramp areas), this command <strong class="red">must</strong> be used <em>(see <a href="/guide/atc-manual/2.-ground/2.1-runway-selection-and-pushback#2.1.1" class="documentation-content-link">2.1.1</a> above)</em>.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Severe Weather</td>
<td data-label="When to be used?">High winds, turbulence and any other weather related phenomena.</td>
</tr>
<tr>
<td data-label="REMARK  / NOTAM">Low Visibility</td>
<td data-label="When to be used?">Low Visibility – visibility less than ¼  statute miles (400m).</td>
</tr>
</tbody>
</table>
<p>*For the purposes of IF, ‘light’ aircraft are defined as the C172, SR22, XCub, Spitfire Mk VIII and P38.</p>
<p>**Take note that the use of 'Straight Out Dept.' may prevent aircraft from flying their selected SID <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.8" class="documentation-content-link">3.2.8</a> above)</em></p>
<p>***Only to be used if the airport has published SID/STAR procedures available</p>
</section>
</section>
<section id="4.1.7">
<h3><a class="header-anchor" href="#4.1.7">4.1.7</a></h3>
<section class="reference">
<p>Controller's can select the preferred SIDs/STARs for the airport and <strong class="red">should</strong> include a reasonable variety of authorized procedures to allow for departures/arrivals from <strong class="red">ALL</strong> directions. By convention, this <strong class="red">should</strong> be decided by Radar Controllers (in their absence, the Tower Controller may choose but this is not encouraged).</p>
</section>
</section>


4.1 ATIS
Tip
: Controllers should{.red} avoid adding too many REMARKS and NOTAMS into a single ATIS as this will dilute the message – Controllers should{.red} ask themselves what the most important messages are, and prioritise as required (see 4.1.6 below)
4.1.1
The Automatic Terminal Information Service, known as ATIS; enables the Controllers to broadcast the current weather as well as REMARKS and NOTAMS for pilots to be aware of. ALL{.red} available runways should{.red} be used – one runway for departures and another runway for arrivals should{.red} be avoided if possible. Controllers may however, be exposed to an airport where terrain, airport layout or weather prevents ALL{.red} runways from being used; in this case it is acceptable to not use ALL{.red} runways (if there are any doubts as to what strategy should{.red} be used, Controllers should{.red} raise this with a Supervisor or above for guidance).
4.1.2
Pattern work must{.red} be denied if the weather conditions, terrain or traffic are not suitable (see 3.4 above)
4.1.3
A letter of the Phonetic Alphabet is used to identify an ATIS transmission, this letter is then relayed between pilots and Controllers to ensure everyone is operating under the same airfield information. At any time, if the current ATIS does not reflect the current situation (including changes in weather or SIDs/STARs in use), Controllers must{.red} change the ATIS without delay and ensure real time coordination with the other Controllers involved. As a MINIMUM{.red}, the ATIS must be updated at least once an hour. In addition, a broadcast must{.red} be made on Ground/Tower/Radar to ensure pilots check the new ATIS.
4.1.4
The letters used when updating the ATIS must{.red} be in alphabetical order and typically starts at Alpha unless the Controller has just taken over from another Controller.
4.1.5
The facility to open multiple Ground/Tower/Radar frequencies exist at some airports. This can be useful when managing busy traffic. If this is to be used Controllers must{.red} ensure that the ATIS is updated to reflect this (i.e. which frequency to contact, from which direction), prior coordination is made with the other Controllers; and during the controlling session, the IFATC Discord Channels are used to provide a good service.
4.1.6
The table below highlights when certain REMARKS or NOTAMS should{.red} be used:
| REMARK  / NOTAM       | When to be used?                                             |
| --------------------- | ------------------------------------------------------------ |
| No Intersection Dept. | Intersection departures must{.red} always be allowed unless it blocks the only taxiway for aircraft to access full length AND{.red} will affect the departure/arrival flow rate (see 3.2.5 above). |
| No Pattern Work       | Weather below VMC? Terrain prevents a standard pattern from being flown? CURRENT{.red} traffic levels will cause a drop in service standards? When 1 of these conditions is met, No Pattern Work must{.red} be used (see 3.4.1 above). |
| Flow Control          | Aircraft can expect a delay for departure if the Controller is trying to limit departing traffic (this could be due to aircraft all heading for the same destination). |
| Long Taxi             | If the runways in use mean that some aircraft can expect a long taxi. |
| Gate Hold             | The use of hold position (see 2.1.3 above) should{.red} be favored but if a long line of  departures needs to be cleared and you have limited space on the taxiways,  gate hold can be used (it should{.red} be limited to a maximum of 10 minutes). |
| No Light Aircraft     | This command must{.red} be used at ALL{.red} times for large airports that do not accept light aircraft IRL (e.g. EGLL, OMDB, VHHH etc). In addition, it is important to note that this command is not traffic dependent – a consistent message must{.red} be sent that there are other, more appropriate airports for light* aircraft. |
| Rolling Dept.         | To expedite departures – when aircraft are cleared for take-off they will be expected to line up and start their take-off roll immediately. The LUAW command must not{.red} be used when this is in use. |
| FPL Required          | Only to be used when weather is below VMC minima (see 3.4.1 above). |
| Straight Out Dept. * | Runway heading must{.red} be flown after departure until no conflict exists AND{.red} the altitude specified by the Tower Controller has been met or exceeded (see 3.2.8 above)*. |
| Mult. Freq. In Use    | (See 4.1.5 above). |
| Check Forum           | Only to be used when referring pilots to special instructions on the IFC pages e.g. VARB Summit. |
| SID/STAR Use Rcmd*  | This command should{.red} be used when light to moderate traffic exists and SID/STAR use is not essential for traffic management (see 4.1.7 below). |
| SID/STAR Use Req*   | This command should{.red} be used when heavy traffic exists and SID/STAR use is essential for traffic management OR{.red} for events and/or main hub airports  (see 4.1.7 below). |
| Event                 | IF LLC sponsored events only.                                |
| Size Restrictions     | When any aircraft cannot be accommodated because their size will restrict airport flow (i.e. block taxiways or ramp areas), this command must{.red} be used (see 2.1.1 above). |
| Severe Weather        | High winds, turbulence and any other weather related phenomena. |
| Low Visibility        | Low Visibility – visibility less than ¼  statute miles (400m). |
*For the purposes of IF, ‘light’ aircraft are defined as the C172, SR22, XCub, Spitfire Mk VIII and P38.
Take note that the use of 'Straight Out Dept.' may prevent aircraft from flying their selected SID (see 3.2.8 above)
*Only to be used if the airport has published SID/STAR procedures available
4.1.7
Controller's can select the preferred SIDs/STARs for the airport and should{.red} include a reasonable variety of authorized procedures to allow for departures/arrivals from ALL{.red} directions. By convention, this should{.red} be decided by Radar Controllers (in their absence, the Tower Controller may choose but this is not encouraged).

4.1 ATIS

<section id="5.1-airspace">
<h1><a class="header-anchor" href="#5.1-airspace"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 5.1 Airspace</h1>
<section class="reference"></section>
<section id="5.1.1">
<h3><a class="header-anchor" href="#5.1.1">5.1.1</a></h3>
<section class="reference">
<p>Controller airspace is defined by it's vertical jurisdiction, lateral boundaries and frequency range for the facility being operated. Below is a summary for each Controller position:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Facility</th>
<th>Vertical Jurisdiction</th>
<th>Lateral Boundary</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Facility">Tower</td>
<td data-label="Vertical Jurisdiction">SFC - 5000ft AAL</td>
<td data-label="Lateral Boundary">Most immediate ring/boundary surrounding the airport</td>
</tr>
<tr>
<td data-label="Facility">Departure/Approach</td>
<td data-label="Vertical Jurisdiction">SFC - 18,000ft/FL180</td>
<td data-label="Lateral Boundary">50nm</td>
</tr>
<tr>
<td data-label="Facility">Center</td>
<td data-label="Vertical Jurisdiction">SFC - 60,000ft/FL600</td>
<td data-label="Lateral Boundary">White boundaries</td>
</tr>
</tbody>
</table>
<p>Note: Airspace parameters and ATC jurisdictions may be altered with the use of NOTAMs and/or TFRs during special events</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-airspace-layout.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-airspace-layout@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-airspace-layout@3x.jpg 3x" alt="Image 5.1.1.1 - Airspace layout" class="documentation-image-lightbox-link" >
          <figcaption>Image 5.1.1.1 - Airspace layout</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="5.1.2">
<h3><a class="header-anchor" href="#5.1.2">5.1.2</a></h3>
<section class="reference">
<p>Departure/Approach facilities are intended to service a single airport or cluster of airports in close proximity, whereas Center is a region based facility that fills in the gaps outside of Departure/Approach radio range.</p>
</section>
</section>
<section id="5.1.3">
<h3><a class="header-anchor" href="#5.1.3">5.1.3</a></h3>
<section class="reference">
<p>Center Controller's may exercise Departure/Approach functions in the absence of a terminal radar facility (i.e. Departure/Approach), though this should be limited, with the primary focus on Center Controller roles <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.1" class="documentation-content-link">6.6.1</a> below)</em>.</p>
</section>
</section>
<section id="5.1.4">
<h3><a class="header-anchor" href="#5.1.4">5.1.4</a></h3>
<section class="reference">
<p>Special Use airspaces such as Military Operating Areas (MOAS), Warning Areas and Restricted Areas are identified with magenta boundaries. For the purposes of Infinite Flight these are currently not enforced or monitored.</p>
</section>
</section>
<section id="5.1.5">
<h3><a class="header-anchor" href="#5.1.5">5.1.5</a></h3>
<section class="reference">
<p>The different types of airspace are defined using a color code and these are shown in the following table <strong class="red">for information only</strong>:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Airspace Type</th>
<th>Color Code</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Airspace Type">Class B</td>
<td data-label="Color Code">Blue</td>
</tr>
<tr>
<td data-label="Airspace Type">Class C</td>
<td data-label="Color Code">Magenta</td>
</tr>
<tr>
<td data-label="Airspace Type">Class D</td>
<td data-label="Color Code">Light Blue</td>
</tr>
<tr>
<td data-label="Airspace Type">Terminal Control Area</td>
<td data-label="Color Code">Light Green</td>
</tr>
<tr>
<td data-label="Airspace Type">Flight Information Region (FIR)</td>
<td data-label="Color Code">White</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


5.1 Airspace
5.1.1
Controller airspace is defined by it's vertical jurisdiction, lateral boundaries and frequency range for the facility being operated. Below is a summary for each Controller position:
| Facility           | Vertical Jurisdiction | Lateral Boundary                                     |
| ------------------ | --------------------- | ---------------------------------------------------- |
| Tower              | SFC - 5000ft AAL      | Most immediate ring/boundary surrounding the airport |
| Departure/Approach | SFC - 18,000ft/FL180  | 50nm                                                 |
| Center             | SFC - 60,000ft/FL600  | White boundaries                                     |
Note: Airspace parameters and ATC jurisdictions may be altered with the use of NOTAMs and/or TFRs during special events
Image 5.1.1.1 - Airspace layout
5.1.2
Departure/Approach facilities are intended to service a single airport or cluster of airports in close proximity, whereas Center is a region based facility that fills in the gaps outside of Departure/Approach radio range.
5.1.3
Center Controller's may exercise Departure/Approach functions in the absence of a terminal radar facility (i.e. Departure/Approach), though this should be limited, with the primary focus on Center Controller roles (see 6.6.1 below).
5.1.4
Special Use airspaces such as Military Operating Areas (MOAS), Warning Areas and Restricted Areas are identified with magenta boundaries. For the purposes of Infinite Flight these are currently not enforced or monitored.
5.1.5
The different types of airspace are defined using a color code and these are shown in the following table for information only{.red}:
| Airspace Type                   | Color Code  |
| ------------------------------- | ----------- |
| Class B                         | Blue        |
| Class C                         | Magenta     |
| Class D                         | Light Blue  |
| Terminal Control Area           | Light Green |
| Flight Information Region (FIR) | White       |

5.1 Airspace

<section id="5.2-on-guard-procedures">
<h1><a class="header-anchor" href="#5.2-on-guard-procedures"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 5.2 On Guard Procedures</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>When opening a frequency, Controllers <strong class="red">must</strong> allow time for things to settle; for example, do not 'on guard' aircraft on short final, allow the aircraft to land and complete the rollout uninterrupted</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="5.2.1">
<h3><a class="header-anchor" href="#5.2.1">5.2.1</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> always check what frequency the aircraft is tuned into before sending an &quot;on guard&quot; message in case they are with another tower/radar facility. Radar Controllers <strong class="red">should</strong> also be aware of an aircraft's active/away status <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.5" class="documentation-content-link">6.6.5</a> below)</em>. Below is a summary of when &quot;on guard&quot; procedures are applicable, aircraft <strong class="red">must not</strong> be &quot;on guarded&quot; outside of these limits:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Facility</th>
<th>Vertical and Lateral Limits</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Facility">Tower</td>
<td data-label="Vertical and Lateral Limits">SFC - 10,000ft AAL and within 25nm</td>
</tr>
<tr>
<td data-label="Facility">Departure/Approach</td>
<td data-label="Vertical and Lateral Limits">SFC - 18,000ft AAL / FL180 and within 50nm</td>
</tr>
<tr>
<td data-label="Facility">Center</td>
<td data-label="Vertical and Lateral Limits">SFC - FL600 and within the white boundaries</td>
</tr>
</tbody>
</table>
<p><em>Note: If the airport elevation is deemed significant, Controllers may elect to take this into account (e.g. with an airport elevation of 5000ft, Controllers may adjust the 'on guard' altitude/FL by 5000ft/FL50 respectively).</em></p>
</section>
</section>
<section id="5.2.2">
<h3><a class="header-anchor" href="#5.2.2">5.2.2</a></h3>
<section class="reference">
<p>Aircraft <strong class="red">should</strong> be given a reasonable amount of time to tune into the frequency after being &quot;on guarded&quot;, in addition aircraft <strong class="red">must not</strong> be 'on guarded' if on another active frequency.</p>
</section>
</section>


5.2 On Guard Procedures
Tip
: When opening a frequency, Controllers must{.red} allow time for things to settle; for example, do not 'on guard' aircraft on short final, allow the aircraft to land and complete the rollout uninterrupted
5.2.1
Controllers must{.red} always check what frequency the aircraft is tuned into before sending an "on guard" message in case they are with another tower/radar facility. Radar Controllers should{.red} also be aware of an aircraft's active/away status (see 6.6.5 below). Below is a summary of when "on guard" procedures are applicable, aircraft must not{.red} be "on guarded" outside of these limits:
| Facility           | Vertical and Lateral Limits                 |
| ------------------ | ------------------------------------------- |
| Tower              | SFC - 10,000ft AAL and within 25nm          |
| Departure/Approach | SFC - 18,000ft AAL / FL180 and within 50nm  |
| Center             | SFC - FL600 and within the white boundaries |
Note: If the airport elevation is deemed significant, Controllers may elect to take this into account (e.g. with an airport elevation of 5000ft, Controllers may adjust the 'on guard' altitude/FL by 5000ft/FL50 respectively).
5.2.2
Aircraft should{.red} be given a reasonable amount of time to tune into the frequency after being "on guarded", in addition aircraft must not{.red} be 'on guarded' if on another active frequency.

5.2 On Guard Procedures

<section id="6.1-what-is-a-radar-controller%3F">
<h1><a class="header-anchor" href="#6.1-what-is-a-radar-controller%3F"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.1  What is a Radar Controller?</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>It is encouraged that new Radar Controllers start off slowly, gradually building up to the more &quot;high-volume&quot; traffic airports. This is particularly important during peak times or events such as Friday Night Flight (FNF)</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="6.1.1">
<h3><a class="header-anchor" href="#6.1.1">6.1.1</a></h3>
<section class="reference">
<p>Although the radar position and its responsibilities are vast, fundamentally, there are three main objectives. These are:</p>
<ul>
<li>
<p>Providing aircraft &amp; terrain separation</p>
</li>
<li>
<p>Reducing Tower Controller workload</p>
</li>
<li>
<p>Providing an expeditious departure, en-route and/or arrival service</p>
</li>
</ul>
</section>
</section>
<section id="6.1.2">
<h3><a class="header-anchor" href="#6.1.2">6.1.2</a></h3>
<section class="reference">
<p>Operating a radar frequency typically comes with a higher workload which is why extensive training is carried out before Controllers are granted the privilege <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5-radar-theory-and-practical-tests" class="documentation-content-link">7.5</a> below)</em>. Controlling aircraft from different directions in altitude, heading &amp; speed, ensuring separation rules are adhered to, whilst still providing an expeditious service are some of the reasons that contribute to this <em>(see 6.1.2.1 below).</em></p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/atc-center-frequency.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/atc-center-frequency@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/atc-center-frequency@3x.png 3x" alt="Image 6.1.2.1 - ATC Center Frequency" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.1.2.1 - ATC Center Frequency</figcaption>
        </figure>
      </p>
<p><strong class="red">BEFORE</strong> opening, Controllers <strong>must</strong> ensure that they have a plan to manage the expected workload.</p>
</section>
</section>


6.1  What is a Radar Controller?
Tip
: It is encouraged that new Radar Controllers start off slowly, gradually building up to the more "high-volume" traffic airports. This is particularly important during peak times or events such as Friday Night Flight (FNF)
6.1.1
Although the radar position and its responsibilities are vast, fundamentally, there are three main objectives. These are:
 Providing aircraft & terrain separation
 Reducing Tower Controller workload
 Providing an expeditious departure, en-route and/or arrival service
6.1.2
Operating a radar frequency typically comes with a higher workload which is why extensive training is carried out before Controllers are granted the privilege (see 7.5 below). Controlling aircraft from different directions in altitude, heading & speed, ensuring separation rules are adhered to, whilst still providing an expeditious service are some of the reasons that contribute to this (see 6.1.2.1 below).
Image 6.1.2.1 - ATC Center Frequency
BEFORE{.red} opening, Controllers must ensure that they have a plan to manage the expected workload.

6.1 What is a Radar Controller?

<section id="6.2-separation">
<h1><a class="header-anchor" href="#6.2-separation"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.2 Separation</h1>
<section class="reference"></section>
<section id="6.2.1">
<h3><a class="header-anchor" href="#6.2.1">6.2.1</a></h3>
<section class="reference">
<p>Terrain separation: aircraft <strong class="red">must</strong> be provided with at least 1000ft AGL (above ground level) terrain clearance at all times.</p>
</section>
</section>
<section id="6.2.2">
<h3><a class="header-anchor" href="#6.2.2">6.2.2</a></h3>
<section class="reference">
<p>Aircraft separation: aircraft <strong class="red">must</strong> be no closer than 3nm laterally or 1000ft vertically at all times <em>(see 6.2.2.1 below).</em></p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-aircraft-separation.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-aircraft-separation@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-aircraft-separation@3x.jpg 3x" alt="Image 6.2.2.1 - Aircraft Separation" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.2.2.1 - Aircraft Separation</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.2.3">
<h3><a class="header-anchor" href="#6.2.3">6.2.3</a></h3>
<section class="reference">
<p>If aircraft do not meet separation requirements on initial contact, the Radar Controller <strong class="red">should</strong> endeavour to provide this separation as soon as practicable. Until the minimum separation requirements are met, any continued flight with less than this is the pilots responsibility - therefore it does not prevent the Controller from offering a service (i.e. &quot;Expect Vectors for...&quot;).</p>
</section>
</section>
<section id="6.2.4">
<h3><a class="header-anchor" href="#6.2.4">6.2.4</a></h3>
<section class="reference">
<p>Aircraft receiving a VFR service are expected to 'see and avoid' while maintaining a <strong class="red">MINIMUM</strong> of 500ft vertical separation with other aircraft.</p>
</section>
</section>
</section>


6.2 Separation

6.2.1

Terrain separation: aircraft must{.red} be provided with at least 1000ft AGL (above ground level) terrain clearance at all times.

6.2.2

Aircraft separation: aircraft must{.red} be no closer than 3nm laterally or 1000ft vertically at all times (see 6.2.2.1 below).

Image 6.2.2.1 - Aircraft Separation

6.2.3

If aircraft do not meet separation requirements on initial contact, the Radar Controller should{.red} endeavour to provide this separation as soon as practicable. Until the minimum separation requirements are met, any continued flight with less than this is the pilots responsibility - therefore it does not prevent the Controller from offering a service (i.e. "Expect Vectors for...").

6.2.4

Aircraft receiving a VFR service are expected to 'see and avoid' while maintaining a MINIMUM{.red} of 500ft vertical separation with other aircraft.

6.2 Separation

<section id="6.3-drag-and-vector-feature">
<h1><a class="header-anchor" href="#6.3-drag-and-vector-feature"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.3  Drag and Vector Feature</h1>
<section class="reference"></section>
<section id="6.3.1">
<h3><a class="header-anchor" href="#6.3.1">6.3.1</a></h3>
<section class="reference">
<p>The Drag and Vector Feature is one of the most fundamental tools at the disposal of Radar Controllers and <strong class="red">should</strong> be utilized. When using this feature, the information displayed for the Controller is:</p>
<ul>
<li>
<p>Heading</p>
</li>
<li>
<p>Distance from aircraft’s current position</p>
</li>
<li>
<p>The time it will take to reach that point (at the aircraft’s current speed)</p>
</li>
<li>
<p>The highest terrain at that particular point</p>
</li>
<li>
<p>And the name of the Navigation Aid if in the vicinity</p>
</li>
</ul>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/frames/atc-drag-and-vector-manual.png" srcset="https://webcdn.infiniteflight.com/guide/manual/frames/atc-drag-and-vector-manual@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/frames/atc-drag-and-vector-manual@3x.png 3x" alt="Image 6.3.1.1 - Drag and Vector" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.3.1.1 - Drag and Vector</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.3.2">
<h3><a class="header-anchor" href="#6.3.2">6.3.2</a></h3>
<section class="reference">
<p>In order to scan for the minimum safe altitude that an aircraft can fly at, it is essential to scan the projected path that you plan on vectoring an aircraft on to look for the highest terrain. As a minimum, the highest terrain spotted <strong class="red">must</strong> then be rounded up to the next whole 1000ft, and then another 1000ft added to this to satisfy terrain separation rules <em>(see <a href="/guide/atc-manual/6.-radar/6.2-separation#6.2.1" class="documentation-content-link">6.2.1</a> above)</em>.</p>
</section>
</section>
<section id="6.3.3">
<h3><a class="header-anchor" href="#6.3.3">6.3.3</a></h3>
<section class="reference">
<p>From the image <em>(see 6.3.1.1 above)</em> the highest spotted terrain that was seen during this scan from the current aircraft’s position to where the drag and vector feature is currently, was 10,800ft. By rounding this figure up to the next 1000ft and then adding another 1000ft onto this to satisfy the terrain separation rules, the lowest altitude this aircraft <strong class="red">must</strong> be given in this area is 12,000ft.</p>
</section>
</section>
</section>


6.3  Drag and Vector Feature
6.3.1
The Drag and Vector Feature is one of the most fundamental tools at the disposal of Radar Controllers and should{.red} be utilized. When using this feature, the information displayed for the Controller is:
 Heading
 Distance from aircraft’s current position
 The time it will take to reach that point (at the aircraft’s current speed)
 The highest terrain at that particular point
 And the name of the Navigation Aid if in the vicinity
Image 6.3.1.1 - Drag and Vector
6.3.2
In order to scan for the minimum safe altitude that an aircraft can fly at, it is essential to scan the projected path that you plan on vectoring an aircraft on to look for the highest terrain. As a minimum, the highest terrain spotted must{.red} then be rounded up to the next whole 1000ft, and then another 1000ft added to this to satisfy terrain separation rules (see 6.2.1 above).
6.3.3
From the image (see 6.3.1.1 above) the highest spotted terrain that was seen during this scan from the current aircraft’s position to where the drag and vector feature is currently, was 10,800ft. By rounding this figure up to the next 1000ft and then adding another 1000ft onto this to satisfy the terrain separation rules, the lowest altitude this aircraft must{.red} be given in this area is 12,000ft.

6.3 Drag and Vector Feature

<section id="6.4-departure-%2F-check-in">
<h1><a class="header-anchor" href="#6.4-departure-%2F-check-in"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.4  Departure / Check In</h1>
<section class="reference"></section>
<section id="departure-and-sids">
<h2><a class="header-anchor" href="#departure-and-sids"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Departure and SIDs</h2>
<section class="reference"></section>
<section id="6.4.1">
<h3><a class="header-anchor" href="#6.4.1">6.4.1</a></h3>
<section class="reference">
<p>Departure control typically includes managing:</p>
<ul>
<li>
<p>VFR aircraft, with or without a flight plan</p>
</li>
<li>
<p>and IFR aircraft (which <strong class="red">should</strong> have a flight plan)</p>
</li>
</ul>
</section>
</section>
<section id="6.4.2">
<h3><a class="header-anchor" href="#6.4.2">6.4.2</a></h3>
<section class="reference">
<p>If straight-out departures are in use, the Departure and Tower Controllers <strong class="red">should</strong> coordinate to ensure a seamless service <em>(see <a href="/guide/atc-manual/3.-tower/3.6-tower-working-with-radar#3.6-tower-working-with-radar" class="documentation-content-link">3.6</a> above)</em>.</p>
</section>
</section>
<section id="6.4.3">
<h3><a class="header-anchor" href="#6.4.3">6.4.3</a></h3>
<section class="reference">
<p>Standard Instrument Departures, known as SIDs, are a published flight procedure that are followed by aircraft on an IFR flight plan immediately after departure. SIDs allow aircraft to depart an airspace following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and arriving traffic. Controllers <strong class="red">should</strong> let aircraft continue on a SID to the maximum extent possible after departure (therefore vectors and/or altitude assignments are not required on initial contact) unless required for sequencing or traffic avoidance. Due to this, Controllers <strong class="red">should</strong> limit the use of &quot;Straight Out Dept.&quot; to accommodate SIDs which often involve turns away from the airport shortly after departure <em>(see <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.9" class="documentation-content-link">3.2.9</a> and <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.6" class="documentation-content-link">4.1.6</a> above)</em>.</p>
</section>
</section>
</section>
<section id="the-use-of-check-in">
<h2><a class="header-anchor" href="#the-use-of-check-in"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> The Use of Check In</h2>
<section class="reference"></section>
<section id="6.4.4">
<h3><a class="header-anchor" href="#6.4.4">6.4.4</a></h3>
<section class="reference">
<p>The Check In feature serves two primary functions:</p>
<ul>
<li>
<p>Requesting an IFR Radar Control Service from the <strong>FIRST</strong> Radar Controller the pilot contacts</p>
</li>
<li>
<p>Advising a Radar Controller that they are on your frequency <strong>AFTER BEING SWITCHED</strong> by a previous radar controller</p>
</li>
</ul>
<p>Controllers can expect aircraft to &quot;Check In&quot; after departure if they want to follow their flight plan (including the SID). Controllers <strong class="red">must</strong> respond to all &quot;Check In&quot; requests with &quot;Radar Contact&quot;, this establishes two-way communication, acceptance of the filed flight plan and clearance to their initial cruising altitude. From this point onwards no further communication is required however aircraft can still be vectored or issued altitude assignments if required <em>(see <a href="https://infiniteflight.com/guide/atc-manual/6.-radar/6.5-flight-following#6.5.2" class="documentation-content-link">6.5.2</a> below).</em> Controllers <strong class="red">must</strong> issue &quot;Continue as Filed&quot; when vectors are no longer required (or &quot;Resume Own Navigation&quot; if the aircraft does not have a flight plan).</p>
</section>
</section>
<section id="6.4.5">
<h3><a class="header-anchor" href="#6.4.5">6.4.5</a></h3>
<section class="reference">
<p>If the aircraft has been provided with a previous service from another radar controller and has been handed over, then the pilot only needs to check in and the service can continue with the new controller.</p>
</section>
</section>
<section id="6.4.6">
<h3><a class="header-anchor" href="#6.4.6">6.4.6</a></h3>
<section class="reference">
<p>If however, the pilot wants a different service they will need to request it. If the Radar Controller is unable to provide the previous service, then the Radar Controller will either need to change the service the aircraft can expect, or ask for the pilots intentions.</p>
</section>
</section>
</section>
</section>


6.4  Departure / Check In
Departure and SIDs
6.4.1
Departure control typically includes managing:
 VFR aircraft, with or without a flight plan
 and IFR aircraft (which should{.red} have a flight plan)
6.4.2
If straight-out departures are in use, the Departure and Tower Controllers should{.red} coordinate to ensure a seamless service (see 3.6 above).
6.4.3
Standard Instrument Departures, known as SIDs, are a published flight procedure that are followed by aircraft on an IFR flight plan immediately after departure. SIDs allow aircraft to depart an airspace following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and arriving traffic. Controllers should{.red} let aircraft continue on a SID to the maximum extent possible after departure (therefore vectors and/or altitude assignments are not required on initial contact) unless required for sequencing or traffic avoidance. Due to this, Controllers should{.red} limit the use of "Straight Out Dept." to accommodate SIDs which often involve turns away from the airport shortly after departure (see 3.2.9 and 4.1.6 above).
The Use of Check In
6.4.4
The Check In feature serves two primary functions:
 Requesting an IFR Radar Control Service from the FIRST Radar Controller the pilot contacts
 Advising a Radar Controller that they are on your frequency AFTER BEING SWITCHED by a previous radar controller
Controllers can expect aircraft to "Check In" after departure if they want to follow their flight plan (including the SID). Controllers must{.red} respond to all "Check In" requests with "Radar Contact", this establishes two-way communication, acceptance of the filed flight plan and clearance to their initial cruising altitude. From this point onwards no further communication is required however aircraft can still be vectored or issued altitude assignments if required (see 6.5.2 below). Controllers must{.red} issue "Continue as Filed" when vectors are no longer required (or "Resume Own Navigation" if the aircraft does not have a flight plan).
6.4.5
If the aircraft has been provided with a previous service from another radar controller and has been handed over, then the pilot only needs to check in and the service can continue with the new controller.
6.4.6
If however, the pilot wants a different service they will need to request it. If the Radar Controller is unable to provide the previous service, then the Radar Controller will either need to change the service the aircraft can expect, or ask for the pilots intentions.

6.4 Departure / Check In

<section id="6.5-flight-following">
<h1><a class="header-anchor" href="#6.5-flight-following"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.5  Flight Following</h1>
<section class="reference"></section>
<section id="6.5.1">
<h3><a class="header-anchor" href="#6.5.1">6.5.1</a></h3>
<section class="reference">
<p>Flight Following is a VFR service that can be requested by a pilot with or without a Flight Plan, therefore Controllers can expect pilots to &quot;see and avoid&quot;. Radar Controllers can acknowledge this request and if the pilot has a flight plan, they will be expected to continue following it.</p>
</section>
</section>
<section id="6.5.2">
<h3><a class="header-anchor" href="#6.5.2">6.5.2</a></h3>
<section class="reference">
<p>Pilots are however, still subject to vectors and altitude assignments as dictated by traffic, Radar Controllers <strong class="red">must</strong> make this judgment to ensure separation is maintained with the other aircraft in their airspace.</p>
</section>
</section>
<section id="6.5.3">
<h3><a class="header-anchor" href="#6.5.3">6.5.3</a></h3>
<section class="reference">
<p>If you do issue a vector and/or altitude assignment, once the risk of conflict is no longer present, you <strong class="red">should</strong> let the pilot know by sending &quot;Continue as Filed&quot; and/or &quot;Altitude at your Discretion&quot; respectively (<em>see <a href="/guide/atc-manual/6.-radar/6.5-flight-following#6.5.5" class="documentation-content-link">6.5.5</a> below for exceptions)</em>. &quot;Resume Own Navigation&quot; <strong class="red">should</strong> be used instead of &quot;Continue as Filed&quot;  if the aircraft is no longer expected to return to their flight plan or does not have a flight plan filed.</p>
</section>
</section>
<section id="6.5.4">
<h3><a class="header-anchor" href="#6.5.4">6.5.4</a></h3>
<section class="reference">
<p>A frequency change <strong class="red">should</strong> be issued when the aircraft is departing your airspace <strong class="red">AND</strong> will no longer affect any other aircraft that is under your control.</p>
</section>
</section>
<section id="6.5.5">
<h3><a class="header-anchor" href="#6.5.5">6.5.5</a></h3>
<section class="reference">
<p>If an aircraft is inbound to the airport that you are controlling, you can &quot;upgrade&quot; the level of service they have requested (e.g. &quot;Expect Vectors for...&quot;) if the traffic does not allow for them to continue as VFR traffic. The &quot;expect deviation from your flight plan&quot; command is available if controllers need it.</p>
</section>
</section>
</section>


6.5  Flight Following
6.5.1
Flight Following is a VFR service that can be requested by a pilot with or without a Flight Plan, therefore Controllers can expect pilots to "see and avoid". Radar Controllers can acknowledge this request and if the pilot has a flight plan, they will be expected to continue following it.
6.5.2
Pilots are however, still subject to vectors and altitude assignments as dictated by traffic, Radar Controllers must{.red} make this judgment to ensure separation is maintained with the other aircraft in their airspace.
6.5.3
If you do issue a vector and/or altitude assignment, once the risk of conflict is no longer present, you should{.red} let the pilot know by sending "Continue as Filed" and/or "Altitude at your Discretion" respectively (see 6.5.5 below for exceptions). "Resume Own Navigation" should{.red} be used instead of "Continue as Filed"  if the aircraft is no longer expected to return to their flight plan or does not have a flight plan filed.
6.5.4
A frequency change should{.red} be issued when the aircraft is departing your airspace AND{.red} will no longer affect any other aircraft that is under your control.
6.5.5
If an aircraft is inbound to the airport that you are controlling, you can "upgrade" the level of service they have requested (e.g. "Expect Vectors for...") if the traffic does not allow for them to continue as VFR traffic. The "expect deviation from your flight plan" command is available if controllers need it.

6.5 Flight Following

<section id="6.6-center">
<h1><a class="header-anchor" href="#6.6-center"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.6 Center</h1>
<section class="reference">
<p><div class="embed-responsive embed-responsive-16by9"><iframe class="embed-responsive-item vimeo-player" type="text/html" width="500" height="281" src="https://player.vimeo.com/video/423210474" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
</section>
<section id="what-is-center%3F">
<h2><a class="header-anchor" href="#what-is-center%3F"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> What is Center?</h2>
<section class="reference"></section>
<section id="6.6.1">
<h3><a class="header-anchor" href="#6.6.1">6.6.1</a></h3>
<section class="reference">
<p>Center airspace is from surface up to FL600 and is defined by the white boundaries on the map. The main two functions of Center are to:</p>
<ul>
<li>
<p>Provide separation and services to all IFR/VFR aircraft under their control</p>
</li>
<li>
<p>And to provide sequence management to traffic during their flight to assist Departure/Approach Controller workload</p>
</li>
</ul>
<p>It is important to note that Center does not replace Departure/Approach and therefore, <strong class="red">should</strong> only be used to support a Departure/Approach frequency by providing upper air traffic management and sequencing. If however, no departure and/or approach frequency is present, the Center Controller can manage this airspace too.</p>
</section>
</section>
</section>
<section id="climb">
<h2><a class="header-anchor" href="#climb"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Climb</h2>
<section class="reference"></section>
<section id="6.6.2">
<h3><a class="header-anchor" href="#6.6.2">6.6.2</a></h3>
<section class="reference">
<p>Aircraft contacting Center in the climb after departure, or after being handed over from a Departure Controller will usually utilize the &quot;Check In&quot; function. The Radar Control Service (or previous service if different) will just continue <em>(see <a href="/guide/atc-manual/6.-radar/6.4-departure-check-in#6.4.4" class="documentation-content-link">6.4.4</a> above)</em>. Aircraft can however, still be vectored or issued altitude assignments if required <em>(see <a href="/guide/atc-manual/6.-radar/6.5-flight-following#6.5.2" class="documentation-content-link">6.5.2</a> above).</em> Controllers <strong class="red">must</strong> issue &quot;Continue as Filed&quot; when vectors are no longer required (or &quot;Resume Own Navigation&quot; if the aircraft does not have a flight plan).</p>
</section>
</section>
<section id="6.6.3">
<h3><a class="header-anchor" href="#6.6.3">6.6.3</a></h3>
<section class="reference">
<p>Aircraft may request a different service if they wish, the Center Controller <strong class="red">must</strong> determine what level of service can be offered based on their workload. If aircraft are flying VFR or do not have a flight plan, the use of &quot;Resume Own Navigation&quot; should be used instead of &quot;Continue as Filed&quot; <em>(see <a href="/guide/atc-manual/6.-radar/6.5-flight-following#6.5.3" class="documentation-content-link">6.5.3</a> and <a href="/guide/atc-manual/6.-radar/6.5-flight-following#6.5.5" class="documentation-content-link">6.5.5</a> above)</em>.</p>
</section>
</section>
</section>
<section id="cruise">
<h2><a class="header-anchor" href="#cruise"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Cruise</h2>
<section class="reference"></section>
<section id="6.6.4">
<h3><a class="header-anchor" href="#6.6.4">6.6.4</a></h3>
<section class="reference">
<p>During this phase of flight for aircraft, Controllers <strong class="red">should</strong> focus on:</p>
<ul>
<li>aircraft that are active/away to provide separation <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.5" class="documentation-content-link">6.6.5</a> below)</em></li>
<li>issue speed commands for traffic flow management</li>
<li>and pass aircraft onto adjacent facilities at the boundary of their airspace <em>(see <a href="/guide/atc-manual/5.-airspace/5.1-airspace#5.1.1" class="documentation-content-link">5.1.1</a> above)</em></li>
</ul>
</section>
</section>
<section id="6.6.5">
<h3><a class="header-anchor" href="#6.6.5">6.6.5</a></h3>
<section class="reference">
<p>Center controllers will be able to see if an aircraft is &quot;active&quot; or &quot;away&quot; by looking at their flight progress strip. Due to this, &quot;away&quot; aircraft <strong class="red">should</strong> be left alone and conflicts assumed unintentional <em>(see <a href="/guide/atc-manual/1b.-violations/1b.1-guidelines#1b.1.6" class="documentation-content-link">1B.1.6</a> above for exceptions)</em>.</p>
</section>
</section>
<section id="6.6.6">
<h3><a class="header-anchor" href="#6.6.6">6.6.6</a></h3>
<section class="reference">
<p>In the cruise phase speed control is essential in traffic flow management, controllers <strong class="red">must</strong> ensure that they are familiar with typical Mach cruising speeds for aircraft under their control <em>(see <a href="/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.5" class="documentation-content-link">6.14.5</a> below)</em>. An increase or decrease of Mach .01 can change an aircraft's arrival time significantly (dependent on how far ahead the instruction is sent). Therefore to control traffic flow, Center Controllers <strong class="red">should</strong> utilize speed control where possible (although altitude changes and vectors are always available if required). This will reduce Controller workload and prevent aircraft being taken hundreds of miles off their flight plan.</p>
</section>
</section>
<section id="6.6.7">
<h3><a class="header-anchor" href="#6.6.7">6.6.7</a></h3>
<section class="reference">
<p>IFR/VFR Semi-circular rules are not implemented, however they are something that are good to be kept in mind and can assist Controllers with providing separation to large amounts of traffic in the cruise.</p>
<p><strong>IFR</strong> - Assuming you are in RVSM airspace</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Heading</th>
<th>Level</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Heading">360 - 179 degrees</td>
<td data-label="Level">ODD (e.g. FL330, FL350, FL370 etc)</td>
</tr>
<tr>
<td data-label="Heading">180 - 359 degrees</td>
<td data-label="Level">EVEN (e.g. FL320, FL340, FL360 etc)</td>
</tr>
</tbody>
</table>
<p><strong>VFR</strong> - Odd or even levels with an extra 500ft added to all levels</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Heading</th>
<th>Level</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Heading">360 - 179 degrees</td>
<td data-label="Level">ODD (e.g. 1500, 3500, 5500, etc)</td>
</tr>
<tr>
<td data-label="Heading">180 - 359 degrees</td>
<td data-label="Level">EVEN (e.g. 2500, 4500, 6500, etc)</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>
<section id="stars">
<h2><a class="header-anchor" href="#stars"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> STARs</h2>
<section class="reference"></section>
<section id="6.6.8">
<h3><a class="header-anchor" href="#6.6.8">6.6.8</a></h3>
<section class="reference">
<p>Standard Terminal Arrival Routes, known as STARs, are a published flight procedure that are followed by aircraft on an IFR flight plan from an intermediate altitude. STARs allow aircraft to arrive following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and departing traffic. Controllers <strong class="red">should</strong> let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance <em>(see <a href="/guide/atc-manual/6.-radar/6.8-approach#6.8.4" class="documentation-content-link">6.8.4</a> below)</em>.</p>
</section>
</section>
<section id="6.6.9">
<h3><a class="header-anchor" href="#6.6.9">6.6.9</a></h3>
<section class="reference">
<p>The Controller can select preferred STARs, offering a variety of authorized procedures from different directions <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.7" class="documentation-content-link">4.1.7</a> above)</em>; Controllers <strong class="red">should</strong> review aircraft flight plans on initial contact to determine whether or not they include the preferred STAR for their destination airport. Aircraft not on a preferred STAR <strong class="red">should</strong> be instructed to &quot;Amend Flight Plan to Include Preferred STAR at Destination&quot; to give the aircraft time to refile.</p>
</section>
</section>
</section>
<section id="descent">
<h2><a class="header-anchor" href="#descent"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Descent</h2>
<section class="reference"></section>
<section id="6.6.10">
<h3><a class="header-anchor" href="#6.6.10">6.6.10</a></h3>
<section class="reference">
<p>Aircraft with a filed STAR are expected to &quot;Check In&quot; on initial contact with Center, if no STAR is present in a pilots flight plan, they <strong class="red">should</strong> initiate contact by requesting the desired service or approach for their destination airport.</p>
</section>
</section>
<section id="6.6.11">
<h3><a class="header-anchor" href="#6.6.11">6.6.11</a></h3>
<section class="reference">
<p>A pilot <strong class="red">should</strong> request descent via the STAR just prior to their Top of Descent (TOD); which Center can respond with either &quot;Descent via the STAR Approved&quot; or &quot;Unable, Expect Vectors&quot;. Aircraft that are cleared to descend via the STAR will display their approved STAR on their flight progress strip, allowing all subsequent Controllers to view this information and removing the need for pilots to make duplicate requests with different Controllers. If they are told to expect vectors, then Center <strong class="red">must</strong> provide heading/altitude assignments, and &quot;Continue as Filed&quot; when complete.  Center may also instruct an aircraft to &quot;Descend via the STAR&quot; if the pilot has not yet requested descent (any built in or pilot amended altitudes assigned to a STAR will be shown on the Controllers scope when an aircraft's icon is tapped).</p>
</section>
</section>
<section id="6.6.12">
<h3><a class="header-anchor" href="#6.6.12">6.6.12</a></h3>
<section class="reference">
<p>Aircraft already descending before making contact with Center <strong class="red">should</strong> be authorized to &quot;Descend via the STAR&quot;. Aircraft already established in the decent <strong class="red">should not</strong> be instructed to &quot;Amend Flight Plan to Include Preferred STAR at Destination&quot; as this could increase pilot workload. Instead, Controllers <strong class="red">should</strong> issue vectors for sequencing.</p>
</section>
</section>
<section id="6.6.13">
<h3><a class="header-anchor" href="#6.6.13">6.6.13</a></h3>
<section class="reference">
<p>Handoffs to the next controlling facility <strong class="red">should</strong> occur at or prior to the lateral and/or vertical boundary as long as all conflicts are resolved. In addition, Center <strong class="red">must</strong> ensure all aircraft are continuing to their destination in an organized manner, on their respective procedures and sequenced prior to handing off to Approach.</p>
</section>
</section>
</section>
</section>


6.6 Center
@vimeo
What is Center?
6.6.1
Center airspace is from surface up to FL600 and is defined by the white boundaries on the map. The main two functions of Center are to:
 Provide separation and services to all IFR/VFR aircraft under their control
 And to provide sequence management to traffic during their flight to assist Departure/Approach Controller workload
It is important to note that Center does not replace Departure/Approach and therefore, should{.red} only be used to support a Departure/Approach frequency by providing upper air traffic management and sequencing. If however, no departure and/or approach frequency is present, the Center Controller can manage this airspace too.
Climb
6.6.2
Aircraft contacting Center in the climb after departure, or after being handed over from a Departure Controller will usually utilize the "Check In" function. The Radar Control Service (or previous service if different) will just continue (see 6.4.4 above). Aircraft can however, still be vectored or issued altitude assignments if required (see 6.5.2 above). Controllers must{.red} issue "Continue as Filed" when vectors are no longer required (or "Resume Own Navigation" if the aircraft does not have a flight plan).
6.6.3
Aircraft may request a different service if they wish, the Center Controller must{.red} determine what level of service can be offered based on their workload. If aircraft are flying VFR or do not have a flight plan, the use of "Resume Own Navigation" should be used instead of "Continue as Filed" (see 6.5.3 and 6.5.5 above).
Cruise
6.6.4
During this phase of flight for aircraft, Controllers should{.red} focus on:
aircraft that are active/away to provide separation (see 6.6.5 below)
issue speed commands for traffic flow management
and pass aircraft onto adjacent facilities at the boundary of their airspace (see 5.1.1 above)
6.6.5
Center controllers will be able to see if an aircraft is "active" or "away" by looking at their flight progress strip. Due to this, "away" aircraft should{.red} be left alone and conflicts assumed unintentional (see 1B.1.6 above for exceptions).
6.6.6
In the cruise phase speed control is essential in traffic flow management, controllers must{.red} ensure that they are familiar with typical Mach cruising speeds for aircraft under their control (see 6.14.5 below). An increase or decrease of Mach .01 can change an aircraft's arrival time significantly (dependent on how far ahead the instruction is sent). Therefore to control traffic flow, Center Controllers should{.red} utilize speed control where possible (although altitude changes and vectors are always available if required). This will reduce Controller workload and prevent aircraft being taken hundreds of miles off their flight plan.
6.6.7
IFR/VFR Semi-circular rules are not implemented, however they are something that are good to be kept in mind and can assist Controllers with providing separation to large amounts of traffic in the cruise.
IFR - Assuming you are in RVSM airspace
| Heading           | Level                               |
| ----------------- | ----------------------------------- |
| 360 - 179 degrees | ODD (e.g. FL330, FL350, FL370 etc)  |
| 180 - 359 degrees | EVEN (e.g. FL320, FL340, FL360 etc) |
VFR - Odd or even levels with an extra 500ft added to all levels
| Heading           | Level                             |
| ----------------- | --------------------------------- |
| 360 - 179 degrees | ODD (e.g. 1500, 3500, 5500, etc)  |
| 180 - 359 degrees | EVEN (e.g. 2500, 4500, 6500, etc) |
STARs
6.6.8
Standard Terminal Arrival Routes, known as STARs, are a published flight procedure that are followed by aircraft on an IFR flight plan from an intermediate altitude. STARs allow aircraft to arrive following a pre-defined route (and in some cases with altitude/speed restrictions) that help them navigate adjacent airspaces, terrain and departing traffic. Controllers should{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance (see 6.8.4 below).
6.6.9
The Controller can select preferred STARs, offering a variety of authorized procedures from different directions (see 4.1.7 above); Controllers should{.red} review aircraft flight plans on initial contact to determine whether or not they include the preferred STAR for their destination airport. Aircraft not on a preferred STAR should{.red} be instructed to "Amend Flight Plan to Include Preferred STAR at Destination" to give the aircraft time to refile.
Descent
6.6.10
Aircraft with a filed STAR are expected to "Check In" on initial contact with Center, if no STAR is present in a pilots flight plan, they should{.red} initiate contact by requesting the desired service or approach for their destination airport.
6.6.11
A pilot should{.red} request descent via the STAR just prior to their Top of Descent (TOD); which Center can respond with either "Descent via the STAR Approved" or "Unable, Expect Vectors". Aircraft that are cleared to descend via the STAR will display their approved STAR on their flight progress strip, allowing all subsequent Controllers to view this information and removing the need for pilots to make duplicate requests with different Controllers. If they are told to expect vectors, then Center must{.red} provide heading/altitude assignments, and "Continue as Filed" when complete.  Center may also instruct an aircraft to "Descend via the STAR" if the pilot has not yet requested descent (any built in or pilot amended altitudes assigned to a STAR will be shown on the Controllers scope when an aircraft's icon is tapped).
6.6.12
Aircraft already descending before making contact with Center should{.red} be authorized to "Descend via the STAR". Aircraft already established in the decent should not{.red} be instructed to "Amend Flight Plan to Include Preferred STAR at Destination" as this could increase pilot workload. Instead, Controllers should{.red} issue vectors for sequencing.
6.6.13
Handoffs to the next controlling facility should{.red} occur at or prior to the lateral and/or vertical boundary as long as all conflicts are resolved. In addition, Center must{.red} ensure all aircraft are continuing to their destination in an organized manner, on their respective procedures and sequenced prior to handing off to Approach.

6.6 Center

<section id="6.7-holding">
<h1><a class="header-anchor" href="#6.7-holding"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.7 Holding</h1>
<section class="reference"></section>
<section id="what-is-a-hold%3F">
<h2><a class="header-anchor" href="#what-is-a-hold%3F"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> What is a Hold?</h2>
<section class="reference"></section>
<section id="6.7.1">
<h3><a class="header-anchor" href="#6.7.1">6.7.1</a></h3>
<section class="reference">
<p>The use of holds can be a very useful tool for Radar Controllers, in particular, they can help with:</p>
<ul>
<li>
<p>Congested airspace</p>
</li>
<li>
<p>Aircraft that are high to lose altitude</p>
</li>
<li>
<p>Delay arrivals to assist with clearing a long departure line</p>
</li>
<li>
<p>A full destination airport</p>
</li>
</ul>
</section>
</section>
<section id="6.7.2">
<h3><a class="header-anchor" href="#6.7.2">6.7.2</a></h3>
<section class="reference">
<p>Controllers can utilize airports, fixes or the aircraft’s present position for a hold. When selected, it will create a hold that the pilot will be able to follow on their map display, and will also automatically issue a speed command based on the selected altitude for the hold.</p>
</section>
</section>
<section id="6.7.3">
<h3><a class="header-anchor" href="#6.7.3">6.7.3</a></h3>
<section class="reference">
<p>Currently holds do not appear on the Radar Controller’s display. Due to this, it is important to know what a pilot is likely to fly if issued with a hold, including the expected flight path for a hold <em>(see 6.7.4.1 below)</em>, and the type of hold entries <em>(see 6.7.6.1 below)</em>.</p>
</section>
</section>
<section id="6.7.4">
<h3><a class="header-anchor" href="#6.7.4">6.7.4</a></h3>
<section class="reference">
<p>The standard pattern of a hold is shown in the below image <em>(see 6.7.4.1 below)</em>:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold@3x.jpg 3x" alt="Image 6.7.4.1 - Standard Holding Pattern" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.7.4.1 - Standard Holding Pattern</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
<section id="hold-entries">
<h2><a class="header-anchor" href="#hold-entries"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Hold Entries</h2>
<section class="reference"></section>
<section id="6.7.5">
<h3><a class="header-anchor" href="#6.7.5">6.7.5</a></h3>
<section class="reference">
<p>There are three types of hold entries, these are:</p>
<ul>
<li>
<p>Direct</p>
</li>
<li>
<p>Parallel</p>
</li>
<li>
<p>Teardrop</p>
</li>
</ul>
</section>
</section>
<section id="6.7.6">
<h3><a class="header-anchor" href="#6.7.6">6.7.6</a></h3>
<section class="reference">
<p>If an aircraft is approaching a hold from the direct entry side as shown in the image <em>(see 6.7.6.1 below)</em>, Controllers can expect the aircraft to go ‘direct’ to the origin of the hold and then fly the standard holding pattern from there. For a parallel entry, a flight path similar to the blue line below can be expected before the standard holding pattern is flown. And finally, for the teardrop entry, a flight path similar to the red line.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold-entry.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold-entry@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-standard-hold-entry@3x.jpg 3x" alt="Image 6.7.6.1 - Standard Hold Entries" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.7.6.1 - Standard Hold Entries</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>


6.7 Holding
What is a Hold?
6.7.1
The use of holds can be a very useful tool for Radar Controllers, in particular, they can help with:
 Congested airspace
 Aircraft that are high to lose altitude
 Delay arrivals to assist with clearing a long departure line
 A full destination airport
6.7.2
Controllers can utilize airports, fixes or the aircraft’s present position for a hold. When selected, it will create a hold that the pilot will be able to follow on their map display, and will also automatically issue a speed command based on the selected altitude for the hold.
6.7.3
Currently holds do not appear on the Radar Controller’s display. Due to this, it is important to know what a pilot is likely to fly if issued with a hold, including the expected flight path for a hold (see 6.7.4.1 below), and the type of hold entries (see 6.7.6.1 below).
6.7.4
The standard pattern of a hold is shown in the below image (see 6.7.4.1 below):
Image 6.7.4.1 - Standard Holding Pattern
Hold Entries
6.7.5
There are three types of hold entries, these are:
 Direct
 Parallel
 Teardrop
6.7.6
If an aircraft is approaching a hold from the direct entry side as shown in the image (see 6.7.6.1 below), Controllers can expect the aircraft to go ‘direct’ to the origin of the hold and then fly the standard holding pattern from there. For a parallel entry, a flight path similar to the blue line below can be expected before the standard holding pattern is flown. And finally, for the teardrop entry, a flight path similar to the red line.
Image 6.7.6.1 - Standard Hold Entries

6.7 Holding

<section id="6.8-approach">
<h1><a class="header-anchor" href="#6.8-approach"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.8  Approach</h1>
<section class="reference"></section>
<section id="what-is-approach%3F">
<h2><a class="header-anchor" href="#what-is-approach%3F"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> What is Approach?</h2>
<section class="reference"></section>
<section id="6.8.1">
<h3><a class="header-anchor" href="#6.8.1">6.8.1</a></h3>
<section class="reference">
<p>Approach airspace is from surface up to FL180 and 50nm around the airport although airport elevation can be taken into account if it is deemed significant <em>(see <a href="/guide/atc-manual/5.-airspace/5.2-on-guard-procedures#5.2.1" class="documentation-content-link">5.2.1</a> above)</em>. Below is a checklist of what you <strong class="red">must</strong> be aware of <strong class="red">BEFORE</strong> opening an approach facility (it is also recommended to fly the approach yourself, this will enable you to determine the ideal altitudes and vectors required for a good approach service):</p>
<ul>
<li>
<p>Airport Elevation: By determining what the elevation is, this can be used to find the best intercept altitudes <em>(see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.5" class="documentation-content-link">6.10.5</a> below)</em></p>
</li>
<li>
<p>Runway Exits: Rapid Exit Taxiways (RETs) will allow aircraft to exit the runway quicker than a 90 degree exit or if the aircraft has to back-taxi to exit, this <strong class="red">must</strong> be taken into account when spacing aircraft on final approach</p>
</li>
<li>
<p>If there are Controllers on the tower frequencies under your coverage area, liaise with them to confirm departure/arrival strategies and runway(s) in use. In addition, make prior arrangements with other Radar Controllers for handover points, altitudes, and headings when aircraft are travelling between airports <em>(see <a href="/guide/atc-manual/3.-tower/3.6-tower-working-with-radar#3.6.1" class="documentation-content-link">3.6.1</a> above)</em></p>
</li>
<li>
<p>Airport Plates: Controllers <strong class="red">should</strong> access approach plates for the airfield as it will increase your situational awareness, and in particular; terrain awareness <em>(see <a href="/guide/atc-manual/6.-radar/6.8-approach#6.8.6" class="documentation-content-link">6.8.6</a> below)</em></p>
</li>
</ul>
</section>
</section>
</section>
<section id="stars-and-initial-vectoring">
<h2><a class="header-anchor" href="#stars-and-initial-vectoring"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> STARs and Initial Vectoring</h2>
<section class="reference"></section>
<section id="6.8.2">
<h3><a class="header-anchor" href="#6.8.2">6.8.2</a></h3>
<section class="reference">
<p>It is important to note that most STARs normally occur in Approach airspace <em>(see <a href="/guide/atc-manual/5.-airspace/5.1-airspace#5.1.1" class="documentation-content-link">5.1.1</a> above)</em>, however if Center controllers are present, coordination <strong class="red">must</strong> take place between <strong class="red">ALL</strong> controllers involved to ensure a seamless service is provided.</p>
</section>
</section>
<section id="6.8.3">
<h3><a class="header-anchor" href="#6.8.3">6.8.3</a></h3>
<section class="reference">
<p>On initial contact with Approach, aircraft are expected to make their approach request. If the aircraft has already been cleared to descend via the STAR from a previous Controller, it will be visible on their flight progress strip <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.11" class="documentation-content-link">6.6.11</a> above)</em>, Approach Controllers <strong class="red">should</strong> respond with &quot;Continue as Filed, Expect the [approach type/runway] at [location]&quot; if they wish the aircraft to continue as previously cleared. If the aircraft was previously receiving vectors, was not approved for descent via the STAR or the Controller wants to issue vectors/altitude assignments, then &quot;Expect Vectors for the [approach type/runway] at [location]&quot; <strong class="red">should</strong> be used instead. In the absence of Center, aircraft who have already begun their initial descent via a STAR may continue their descent with the response 'Continue as Filed, Expect the [approach type/runway] at [location]' without a specific descent via clearance <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.12" class="documentation-content-link">6.6.12</a> above)</em>.</p>
</section>
</section>
<section id="6.8.4">
<h3><a class="header-anchor" href="#6.8.4">6.8.4</a></h3>
<section class="reference">
<p>Controllers <strong class="red">should</strong> let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance <em>(see <a href="/guide/atc-manual/6.-radar/6.8-approach#6.8.5" class="documentation-content-link">6.8.5</a> below)</em>. The Controller can select preferred STARs, offering a variety of authorized procedures from different directions <em>(see <a href="/guide/atc-manual/4.-atis/4.1-atis#4.1.7" class="documentation-content-link">4.1.7</a> above)</em>; aircraft not on a preferred STAR <strong class="red">should</strong> be instructed to &quot;Amend Flight Plan to Include Preferred STAR at Destination&quot; <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.8" class="documentation-content-link">6.6.8</a> above)</em>, unless the aircraft is established in the descent <em>(see <a href="/guide/atc-manual/6.-radar/6.6-center#6.6.12" class="documentation-content-link">6.6.12</a> above)</em>.</p>
</section>
</section>
<section id="6.8.5">
<h3><a class="header-anchor" href="#6.8.5">6.8.5</a></h3>
<section class="reference">
<p>Traffic and terrain permitting, aircraft <strong class="red">must</strong> be given the most direct routing possible, and therefore <strong class="red">should not</strong> be made to fly a full STAR procedure when these conditions exist.</p>
</section>
</section>
</section>
<section id="approach-charts">
<h2><a class="header-anchor" href="#approach-charts"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Approach Charts</h2>
<section class="reference"></section>
<section id="6.8.6">
<h3><a class="header-anchor" href="#6.8.6">6.8.6</a></h3>
<section class="reference">
<p>Approach charts can generally be found online by searching in any search engine for ‘approach charts’ with the related ICAO code; Controllers <strong class="red">should</strong> familiarize themselves with how to read these charts as it will increase the Controller’s situational awareness. In addition, Controllers are encouraged to utilize <a href="https://www.ifatc.org/" class="documentation-content-link">https://www.ifatc.org/</a>  - this site has been designed by one of our Controllers and is a fantastic tool which can allow the controller to monitor aircraft and the terrain around them, in real time.</p>
</section>
</section>
<section id="6.8.7">
<h3><a class="header-anchor" href="#6.8.7">6.8.7</a></h3>
<section class="reference">
<p>The MSA (Minimum Sector Altitude) is an area in which an aircraft can be safely vectored and have guaranteed terrain clearance provided the aircraft is not cleared below the altitude displayed within that sector. Most Charts have an MSA displayed <em>(see 6.8.7.1 below)</em> within segments of a circle (normally based around the airport itself or a navigation aid). Each segment contains an altitude which will guarantee terrain separation but Controllers can vector aircraft below this altitude if terrain clearance is assured.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/ksfo-chart.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/ksfo-chart@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/ksfo-chart@3x.jpg 3x" alt="Image 6.8.7.1 - KSFO FAA Chart" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.8.7.1 - KSFO FAA Chart</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.8.8">
<h3><a class="header-anchor" href="#6.8.8">6.8.8</a></h3>
<section class="reference">
<p>From the image <em>(see 6.8.7.1 above)</em> it can be assumed that aircraft approaching from the North will be clear of terrain down to 5100ft, aircraft from the South down to 4500ft and aircraft from out over the sea down to 3500ft. By flying the approach yourself before you control there, you can continue to build a full picture. Where are the high points of terrain, what is the best intercept altitude and so on.</p>
</section>
</section>
</section>
<section id="flight-plan-approach-prefixes">
<h2><a class="header-anchor" href="#flight-plan-approach-prefixes"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Flight Plan Approach Prefixes</h2>
<section class="reference"></section>
<section id="6.8.9">
<h3><a class="header-anchor" href="#6.8.9">6.8.9</a></h3>
<section class="reference">
<p>If a published approach has been selected by a pilot, this will be visible to the Controller within the pilot's flight plan. The following prefixes are used to help differentiate between the different approaches available at an airport:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Prefix</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Prefix">D</td>
<td data-label="Meaning">VOR/DME Approach</td>
</tr>
<tr>
<td data-label="Prefix">H</td>
<td data-label="Meaning">RNAV (RNP) Approach</td>
</tr>
<tr>
<td data-label="Prefix">I</td>
<td data-label="Meaning">ILS Approach</td>
</tr>
<tr>
<td data-label="Prefix">L</td>
<td data-label="Meaning">Localizer Only Approach</td>
</tr>
<tr>
<td data-label="Prefix">N</td>
<td data-label="Meaning">NDB Approach</td>
</tr>
<tr>
<td data-label="Prefix">Q</td>
<td data-label="Meaning">Combination (two or more) of ILS/DME/VOR/NDB</td>
</tr>
<tr>
<td data-label="Prefix">R</td>
<td data-label="Meaning">RNAV (GPS) Approach</td>
</tr>
<tr>
<td data-label="Prefix">S</td>
<td data-label="Meaning">VOR Only Approach</td>
</tr>
</tbody>
</table>
<p>After the prefix, the runway designator (such as 27 for Runway 27) will be shown. This will then be followed by any associated suffixes, these are shown in the table below:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Suffix</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Suffix">L</td>
<td data-label="Meaning">Left</td>
</tr>
<tr>
<td data-label="Suffix">R</td>
<td data-label="Meaning">Right</td>
</tr>
<tr>
<td data-label="Suffix">Y or Z</td>
<td data-label="Meaning">Differentiates between runways that utilize the same guidance</td>
</tr>
<tr>
<td data-label="Suffix">1, 2 etc.</td>
<td data-label="Meaning">Indicates same guidance is being used to a runway but with different approach paths (commonly found on the VOR/DME/NDB approaches)</td>
</tr>
</tbody>
</table>
<p><strong>Example:</strong></p>
<p>H35LZ - RNAV (RNP) Approach for Runway 35L, Zulu Procedure</p>
</section>
</section>
</section>
</section>


6.8  Approach
What is Approach?
6.8.1
Approach airspace is from surface up to FL180 and 50nm around the airport although airport elevation can be taken into account if it is deemed significant (see 5.2.1 above). Below is a checklist of what you must{.red} be aware of BEFORE{.red} opening an approach facility (it is also recommended to fly the approach yourself, this will enable you to determine the ideal altitudes and vectors required for a good approach service):
 Airport Elevation: By determining what the elevation is, this can be used to find the best intercept altitudes (see 6.10.5-approach#6.10.5) below)
 Runway Exits: Rapid Exit Taxiways (RETs) will allow aircraft to exit the runway quicker than a 90 degree exit or if the aircraft has to back-taxi to exit, this must{.red} be taken into account when spacing aircraft on final approach
 If there are Controllers on the tower frequencies under your coverage area, liaise with them to confirm departure/arrival strategies and runway(s) in use. In addition, make prior arrangements with other Radar Controllers for handover points, altitudes, and headings when aircraft are travelling between airports (see 3.6.1 above)
 Airport Plates: Controllers should{.red} access approach plates for the airfield as it will increase your situational awareness, and in particular; terrain awareness (see 6.8.6 below)
STARs and Initial Vectoring
6.8.2
It is important to note that most STARs normally occur in Approach airspace (see 5.1.1 above), however if Center controllers are present, coordination must{.red} take place between ALL{.red} controllers involved to ensure a seamless service is provided.
6.8.3
On initial contact with Approach, aircraft are expected to make their approach request. If the aircraft has already been cleared to descend via the STAR from a previous Controller, it will be visible on their flight progress strip (see 6.6.11 above), Approach Controllers should{.red} respond with "Continue as Filed, Expect the approach type/runway] at [location]" if they wish the aircraft to continue as previously cleared. If the aircraft was previously receiving vectors, was not approved for descent via the STAR or the Controller wants to issue vectors/altitude assignments, then "Expect Vectors for the [approach type/runway] at [location]" should{.red} be used instead. In the absence of Center, aircraft who have already begun their initial descent via a STAR may continue their descent with the response 'Continue as Filed, Expect the [approach type/runway] at [location]' without a specific descent via clearance (see [6.6.12 above).
6.8.4
Controllers should{.red} let aircraft continue on a STAR to the maximum extent possible for arrival unless vectors are required for an expeditious service, sequencing or traffic avoidance (see 6.8.5 below). The Controller can select preferred STARs, offering a variety of authorized procedures from different directions (see 4.1.7 above); aircraft not on a preferred STAR should{.red} be instructed to "Amend Flight Plan to Include Preferred STAR at Destination" (see 6.6.8 above), unless the aircraft is established in the descent (see 6.6.12 above).
6.8.5
Traffic and terrain permitting, aircraft must{.red} be given the most direct routing possible, and therefore should not{.red} be made to fly a full STAR procedure when these conditions exist.
Approach Charts
6.8.6
Approach charts can generally be found online by searching in any search engine for ‘approach charts’ with the related ICAO code; Controllers should{.red} familiarize themselves with how to read these charts as it will increase the Controller’s situational awareness. In addition, Controllers are encouraged to utilize https://www.ifatc.org/  - this site has been designed by one of our Controllers and is a fantastic tool which can allow the controller to monitor aircraft and the terrain around them, in real time.
6.8.7
The MSA (Minimum Sector Altitude) is an area in which an aircraft can be safely vectored and have guaranteed terrain clearance provided the aircraft is not cleared below the altitude displayed within that sector. Most Charts have an MSA displayed (see 6.8.7.1 below) within segments of a circle (normally based around the airport itself or a navigation aid). Each segment contains an altitude which will guarantee terrain separation but Controllers can vector aircraft below this altitude if terrain clearance is assured.
Image 6.8.7.1 - KSFO FAA Chart
6.8.8
From the image (see 6.8.7.1 above) it can be assumed that aircraft approaching from the North will be clear of terrain down to 5100ft, aircraft from the South down to 4500ft and aircraft from out over the sea down to 3500ft. By flying the approach yourself before you control there, you can continue to build a full picture. Where are the high points of terrain, what is the best intercept altitude and so on.
Flight Plan Approach Prefixes
6.8.9
If a published approach has been selected by a pilot, this will be visible to the Controller within the pilot's flight plan. The following prefixes are used to help differentiate between the different approaches available at an airport:
| Prefix | Meaning                                      |
| ------ | -------------------------------------------- |
| D      | VOR/DME Approach                             |
| H      | RNAV (RNP) Approach                          |
| I      | ILS Approach                                 |
| L      | Localizer Only Approach                      |
| N      | NDB Approach                                 |
| Q      | Combination (two or more) of ILS/DME/VOR/NDB |
| R      | RNAV (GPS) Approach                          |
| S      | VOR Only Approach                            |
After the prefix, the runway designator (such as 27 for Runway 27) will be shown. This will then be followed by any associated suffixes, these are shown in the table below:
| Suffix    | Meaning                                                      |
| --------- | ------------------------------------------------------------ |
| L         | Left                                                         |
| R         | Right                                                        |
| Y or Z    | Differentiates between runways that utilize the same guidance |
| 1, 2 etc. | Indicates same guidance is being used to a runway but with different approach paths (commonly found on the VOR/DME/NDB approaches) |
Example:
H35LZ - RNAV (RNP) Approach for Runway 35L, Zulu Procedure

6.8 Approach

<section id="6.9-global-positioning-system-(gps)-approach">
<h1><a class="header-anchor" href="#6.9-global-positioning-system-(gps)-approach"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.9  Global Positioning System (GPS) Approach</h1>
<section class="reference">
<p><div class="embed-responsive embed-responsive-16by9"><iframe class="embed-responsive-item vimeo-player" type="text/html" width="500" height="281" src="https://player.vimeo.com/video/442728868" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
</section>
<section id="6.9.1">
<h3><a class="header-anchor" href="#6.9.1">6.9.1</a></h3>
<section class="reference">
<p>The Global Positioning System (GPS) Approach is a non-precision approach within IF but is not commonly used as functionality is currently limited. If however, pilots request this type of approach, Controllers <strong class="red">should</strong> try to accommodate this when traffic permits. The GPS Approach is defined by a series of waypoints and altitude restrictions that the pilot will follow to the runway threshold, free of conventional guidance such as a localizer/glideslope etc.</p>
</section>
</section>
<section id="6.9.2">
<h3><a class="header-anchor" href="#6.9.2">6.9.2</a></h3>
<section class="reference">
<p>When a pilot requests the GPS Approach, Controllers <strong class="red">must</strong> check that the aircraft has a published procedure (i.e. denoted by a prefix in their flight plan - <em>see <a href="/guide/atc-manual/6.-radar/6.8-approach#6.8.9" class="documentation-content-link">6.8.9</a> above</em>) that provides lateral navigation to the intended arrival runway. Controllers can then expect aircraft to continue on their Flight Plan, and at an appropriate point (such as base), clear the aircraft for the GPS Approach. Vectors, altitude assignments, and/or intercepts <strong class="red">should not</strong> be required and the pilot is expected to follow their flight plan to the runway threshold.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If pilots edit their flight plan (such as removing the missed approach segment), it may remove the prefix showing that they have a published procedure. Controllers <strong class="red">should</strong>, in this case, use their best judgement and if the procedure looks correct, a GPS Approach can still be granted</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="6.9.3">
<h3><a class="header-anchor" href="#6.9.3">6.9.3</a></h3>
<section class="reference">
<p>Once the aircraft is inbound to the runway threshold (this may not be inline with the runway for various GPS Approaches that are offset) Controllers can then hand them off to Tower/Unicom as appropriate.</p>
</section>
</section>
<section id="6.9.4">
<h3><a class="header-anchor" href="#6.9.4">6.9.4</a></h3>
<section class="reference">
<p>Controllers can favor utilizing vectors in the following cases:</p>
<ul>
<li>
<p>if a STAR does not lead aircraft onto the final approach</p>
</li>
<li>
<p>if it would not be expeditious to allow aircraft to fly their entire flight plan with <strong>CURRENT</strong> traffic levels</p>
</li>
<li>
<p>or if the aircraft has declared a missed approach</p>
</li>
</ul>
<p>In these instances, Controllers <strong class="red">should</strong> provide the aircraft with vectors to the Initial Approach Fix (IAF) as a <strong>MINIMUM</strong>; and in <strong>ALL</strong> cases, <strong class="red">must</strong> ensure that the vectors will allow the aircraft to establish inbound on the GPS Approach. Once this is assured, the aircraft can be cleared for the GPS Approach (Controllers can use &quot;Continue as Filed&quot; instead, but a clearance will still be required once the aircraft is closer - <em>see <a href="/guide/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach#6.9.2" class="documentation-content-link">6.9.2</a> above</em>).</p>
</section>
</section>


6.9  Global Positioning System (GPS) Approach
@vimeo
6.9.1
The Global Positioning System (GPS) Approach is a non-precision approach within IF but is not commonly used as functionality is currently limited. If however, pilots request this type of approach, Controllers should{.red} try to accommodate this when traffic permits. The GPS Approach is defined by a series of waypoints and altitude restrictions that the pilot will follow to the runway threshold, free of conventional guidance such as a localizer/glideslope etc.
6.9.2
When a pilot requests the GPS Approach, Controllers must{.red} check that the aircraft has a published procedure (i.e. denoted by a prefix in their flight plan - see 6.8.9 above) that provides lateral navigation to the intended arrival runway. Controllers can then expect aircraft to continue on their Flight Plan, and at an appropriate point (such as base), clear the aircraft for the GPS Approach. Vectors, altitude assignments, and/or intercepts should not{.red} be required and the pilot is expected to follow their flight plan to the runway threshold.
Tip
: If pilots edit their flight plan (such as removing the missed approach segment), it may remove the prefix showing that they have a published procedure. Controllers should{.red}, in this case, use their best judgement and if the procedure looks correct, a GPS Approach can still be granted
6.9.3
Once the aircraft is inbound to the runway threshold (this may not be inline with the runway for various GPS Approaches that are offset) Controllers can then hand them off to Tower/Unicom as appropriate.
6.9.4
Controllers can favor utilizing vectors in the following cases:
if a STAR does not lead aircraft onto the final approach
if it would not be expeditious to allow aircraft to fly their entire flight plan with CURRENT traffic levels
or if the aircraft has declared a missed approach
In these instances, Controllers should{.red} provide the aircraft with vectors to the Initial Approach Fix (IAF) as a MINIMUM; and in ALL cases, must{.red} ensure that the vectors will allow the aircraft to establish inbound on the GPS Approach. Once this is assured, the aircraft can be cleared for the GPS Approach (Controllers can use "Continue as Filed" instead, but a clearance will still be required once the aircraft is closer - see 6.9.2-approach#6.9.2) above).

6.9 Global Positioning System (GPS) Approach

<section id="6.10-instrument-landing-system-(ils)-approach">
<h1><a class="header-anchor" href="#6.10-instrument-landing-system-(ils)-approach"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.10  Instrument Landing System (ILS) Approach</h1>
<section class="reference"></section>
<section id="what-is-an-ils-approach%3F">
<h2><a class="header-anchor" href="#what-is-an-ils-approach%3F"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> What is an ILS Approach?</h2>
<section class="reference"></section>
<section id="6.10.1">
<h3><a class="header-anchor" href="#6.10.1">6.10.1</a></h3>
<section class="reference">
<p>The ILS consists of two beams, the Localizer (LOC), providing lateral guidance (left/right) and the Glideslope (G/S) providing vertical guidance (up/down).</p>
</section>
</section>
<section id="6.10.2">
<h3><a class="header-anchor" href="#6.10.2">6.10.2</a></h3>
<section class="reference">
<p>The cone at the end of a runway provides a <strong class="red">VISUAL AID</strong> for both pilots and Controllers of where the LOC and G/S are, however it is important to remember that the LOC and G/S are not confined to the cone. The LOC and G/S are independent radio ‘signals’ that are sent out, and thus continue to go out. Aircraft can receive these signals and therefore intercept them - both within the cone or outside of the cone.</p>
</section>
</section>
</section>
<section id="intercepting-the-loc-and-g%2Fs">
<h2><a class="header-anchor" href="#intercepting-the-loc-and-g%2Fs"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Intercepting the LOC and G/S</h2>
<section class="reference"></section>
<section id="6.10.3">
<h3><a class="header-anchor" href="#6.10.3">6.10.3</a></h3>
<section class="reference">
<p>To intercept the LOC of an ILS, Controllers <strong class="red">should</strong> issue an intercept heading <em>(for exceptions see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.5" class="documentation-content-link">6.10.5</a> below)</em>; this heading <strong class="red">should</strong> be as close to 30 degrees as possible, offset from the runway designator <em>(see 6.10.3.1 below)</em>. The intercept heading needs to give the aircraft a good closing angle to get onto the LOC expeditiously and thus 10 degrees or less <strong class="red">should</strong> be avoided. Although the standard method for determination of the intercept headings to be used <strong class="red">should</strong> be based off the runway designator (e.g. for RWY 18, 30 degree intercepts would be headings 150 and 210), controllers may need to take into account the actual runway heading if it is considered significantly different (e.g. KMIA RWY 08R has an actual heading of 092). In this example, the ideal intercept headings would be 060 or 120 degrees.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-loc.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-loc@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-loc@3x.jpg 3x" alt="Image 6.10.3.1 - Intercepting the localizer" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.10.3.1 - Intercepting the localizer</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.10.4">
<h3><a class="header-anchor" href="#6.10.4">6.10.4</a></h3>
<section class="reference">
<p>To intercept the G/S of an ILS, Controllers <strong class="red">must</strong> issue an altitude that is below the G/S path <em>(see 6.10.4.1 below).</em> The typical G/S follows a 3 degree flight path angle that guides the aircraft to the runway threshold. At 1nm the G/S altitude would be 300ft AAL (above aerodrome level); at 2nm, 600ft AAL and so on.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-gs.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-gs@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-gs@3x.jpg 3x" alt="Image 6.10.4.1 - Intercepting the glideslope" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.10.4.1 - Intercepting the glideslope</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.10.5">
<h3><a class="header-anchor" href="#6.10.5">6.10.5</a></h3>
<section class="reference">
<p>Controllers may issue an ILS approach clearance at an appropriate position without an assigned intercept heading if the aircraft's filed STAR and/or Instrument Approach meet one of the following criteria:</p>
<ul>
<li>contains a reasonable intercept angle to the final approach course or,</li>
<li>joins the extended final at a distance of 20nm or greater</li>
</ul>
<p>In all cases, an appropriate altitude <strong class="red">must</strong> still be assigned to serve as the lowest authorized altitude until the aircraft is established on the localizer. If a Controller has an advanced understanding of an airport's specific ILS approach plate, the Controller may still issue a clearance without an intercept heading outside of the two conditions listed above. To do this, the Controller <strong class="red">must</strong> have familiarized themselves with the instrument approach procedure and be able to visually determine when aircraft are established.</p>
</section>
</section>
</section>
<section id="determining-the-intercept-altitude">
<h2><a class="header-anchor" href="#determining-the-intercept-altitude"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Determining the Intercept Altitude</h2>
<section class="reference"></section>
<section id="6.10.6">
<h3><a class="header-anchor" href="#6.10.6">6.10.6</a></h3>
<section class="reference">
<p>As already mentioned <em>(see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.2" class="documentation-content-link">6.10.2</a> above)</em>, the cone is a useful <strong class="red">VISUAL AID</strong> that Controllers can utilize for the ILS or GPS approach. The cones have a standard length of about 11nm and thus the G/S altitude at this point is approximately 3500ft AAL. Although this will assist in determining the best altitudes to use for the intercept, it will also be affected by the following:</p>
<ul>
<li>
<p>Terrain</p>
</li>
<li>
<p>Aircraft position</p>
</li>
<li>
<p>Elevation of aerodrome</p>
</li>
</ul>
<p>To ensure that aircraft intercept the G/S from below Controllers must use an altitude that is lower than the G/S at the point of interception <em>(see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4" class="documentation-content-link">6.10.4</a> above)</em> – by convention, this tends to be 500ft lower but there is no hard rule on this. For example, Airport A has an elevation of 1000ft, therefore the G/S altitude at the end of the cone is approximately 4500ft. Assuming the aircraft is intercepting at the end of the cone, an altitude of 4000ft would be a sensible intercept altitude (based on no terrain to effect apart from the airport elevation). If the aircraft was to intercept further out than the cone, or even within the cone itself, then you will need to adjust the intercept altitude to allow the aircraft to not be above the G/S when intercepting. Without flying the approach before controlling and/or using approach plates, it will be difficult to determine the best altitudes that ensure terrain separation and a good intercept!</p>
</section>
</section>
</section>
</section>


6.10  Instrument Landing System (ILS) Approach

What is an ILS Approach?

6.10.1

The ILS consists of two beams, the Localizer (LOC), providing lateral guidance (left/right) and the Glideslope (G/S) providing vertical guidance (up/down).

6.10.2

The cone at the end of a runway provides a VISUAL AID{.red} for both pilots and Controllers of where the LOC and G/S are, however it is important to remember that the LOC and G/S are not confined to the cone. The LOC and G/S are independent radio ‘signals’ that are sent out, and thus continue to go out. Aircraft can receive these signals and therefore intercept them - both within the cone or outside of the cone.

Intercepting the LOC and G/S

6.10.3

To intercept the LOC of an ILS, Controllers should{.red} issue an intercept heading (for exceptions see 6.10.5-approach#6.10.5) below); this heading should{.red} be as close to 30 degrees as possible, offset from the runway designator (see 6.10.3.1 below). The intercept heading needs to give the aircraft a good closing angle to get onto the LOC expeditiously and thus 10 degrees or less should{.red} be avoided. Although the standard method for determination of the intercept headings to be used should{.red} be based off the runway designator (e.g. for RWY 18, 30 degree intercepts would be headings 150 and 210), controllers may need to take into account the actual runway heading if it is considered significantly different (e.g. KMIA RWY 08R has an actual heading of 092). In this example, the ideal intercept headings would be 060 or 120 degrees.

Image 6.10.3.1 - Intercepting the localizer

6.10.4

To intercept the G/S of an ILS, Controllers must{.red} issue an altitude that is below the G/S path (see 6.10.4.1 below). The typical G/S follows a 3 degree flight path angle that guides the aircraft to the runway threshold. At 1nm the G/S altitude would be 300ft AAL (above aerodrome level); at 2nm, 600ft AAL and so on.

Image 6.10.4.1 - Intercepting the glideslope

6.10.5

Controllers may issue an ILS approach clearance at an appropriate position without an assigned intercept heading if the aircraft's filed STAR and/or Instrument Approach meet one of the following criteria:

contains a reasonable intercept angle to the final approach course or,
joins the extended final at a distance of 20nm or greater

In all cases, an appropriate altitude must{.red} still be assigned to serve as the lowest authorized altitude until the aircraft is established on the localizer. If a Controller has an advanced understanding of an airport's specific ILS approach plate, the Controller may still issue a clearance without an intercept heading outside of the two conditions listed above. To do this, the Controller must{.red} have familiarized themselves with the instrument approach procedure and be able to visually determine when aircraft are established.

Determining the Intercept Altitude

6.10.6

As already mentioned (see 6.10.2-approach#6.10.2) above), the cone is a useful VISUAL AID{.red} that Controllers can utilize for the ILS or GPS approach. The cones have a standard length of about 11nm and thus the G/S altitude at this point is approximately 3500ft AAL. Although this will assist in determining the best altitudes to use for the intercept, it will also be affected by the following:

 Terrain

 Aircraft position

 Elevation of aerodrome

To ensure that aircraft intercept the G/S from below Controllers must use an altitude that is lower than the G/S at the point of interception (see 6.10.4-approach#6.10.4) above) – by convention, this tends to be 500ft lower but there is no hard rule on this. For example, Airport A has an elevation of 1000ft, therefore the G/S altitude at the end of the cone is approximately 4500ft. Assuming the aircraft is intercepting at the end of the cone, an altitude of 4000ft would be a sensible intercept altitude (based on no terrain to effect apart from the airport elevation). If the aircraft was to intercept further out than the cone, or even within the cone itself, then you will need to adjust the intercept altitude to allow the aircraft to not be above the G/S when intercepting. Without flying the approach before controlling and/or using approach plates, it will be difficult to determine the best altitudes that ensure terrain separation and a good intercept!

6.10 Instrument Landing System (ILS) Approach

<section id="6.11-radar-vectors">
<h1><a class="header-anchor" href="#6.11-radar-vectors"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.11  Radar Vectors</h1>
<section class="reference"></section>
<section id="6.11.1">
<h3><a class="header-anchor" href="#6.11.1">6.11.1</a></h3>
<section class="reference">
<p>Radar Vectors are primarily used to put aircraft into the VFR pattern for an airport. Controllers <strong class="red">should</strong> vector aircraft into a recognizable position (e.g. downwind, base etc.), and before handing over to Tower, descend the aircraft down to pattern altitude (see table below). When aircraft call in following Radar Vectors, Tower <strong class="red">must</strong> issue a pattern entry, a sequence (if required) and then a clearance.  If the runway which is in use has an instrument approach (ILS or GPS), Controllers can vector the aircraft towards the localizer however the aircraft <strong class="red">must</strong> not be cleared for an approach, but instead handed over to tower who will issue a pattern entry, sequence (if required) and then a clearance.</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Aircraft Type</th>
<th>Pattern Altitude</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Aircraft Type">Prop</td>
<td data-label="Pattern Altitude">1000ft AAL</td>
</tr>
<tr>
<td data-label="Aircraft Type">Jet</td>
<td data-label="Pattern Altitude">1500ft AAL</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="6.11.2">
<h3><a class="header-anchor" href="#6.11.2">6.11.2</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> check the Airport Elevation of the airfield they are Radar Vectoring an aircraft to so that the correct pattern altitude can be determined; and as always, consideration to surrounding terrain <strong class="red">must</strong> be taken into account.</p>
</section>
</section>
<section id="6.11.3">
<h3><a class="header-anchor" href="#6.11.3">6.11.3</a></h3>
<section class="reference">
<p>If the weather at the airport in question is below VMC (see <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4-pattern-work-%2F-transitions-%2F-flight-of-xx" class="documentation-content-link">3.4</a> above), then aircraft <strong class="red">must</strong> be vectored towards the instrument approach for the airport (ILS or GPS), and then handed over to Tower/Unicom at an altitude and position that allows for the aircraft to independently set up for an instrument approach to landing. In this case, descent to pattern altitude is not required, but a suitable altitude <strong class="red">should</strong> be issued to take into account the position in relation to the airport and G/S (see <a href="/guide/atc-manual/6.-radar/6.10-instrument-landing-system-(ils)-approach#6.10.4" class="documentation-content-link">6.10.4</a> above).</p>
</section>
</section>
</section>


6.11  Radar Vectors

6.11.1

Radar Vectors are primarily used to put aircraft into the VFR pattern for an airport. Controllers should{.red} vector aircraft into a recognizable position (e.g. downwind, base etc.), and before handing over to Tower, descend the aircraft down to pattern altitude (see table below). When aircraft call in following Radar Vectors, Tower must{.red} issue a pattern entry, a sequence (if required) and then a clearance.  If the runway which is in use has an instrument approach (ILS or GPS), Controllers can vector the aircraft towards the localizer however the aircraft must{.red} not be cleared for an approach, but instead handed over to tower who will issue a pattern entry, sequence (if required) and then a clearance.

| Aircraft Type | Pattern Altitude |
| ------------- | ---------------- |
| Prop          | 1000ft AAL       |
| Jet           | 1500ft AAL       |

6.11.2

Controllers must{.red} check the Airport Elevation of the airfield they are Radar Vectoring an aircraft to so that the correct pattern altitude can be determined; and as always, consideration to surrounding terrain must{.red} be taken into account.

6.11.3

If the weather at the airport in question is below VMC (see 3.4 above), then aircraft must{.red} be vectored towards the instrument approach for the airport (ILS or GPS), and then handed over to Tower/Unicom at an altitude and position that allows for the aircraft to independently set up for an instrument approach to landing. In this case, descent to pattern altitude is not required, but a suitable altitude should{.red} be issued to take into account the position in relation to the airport and G/S (see 6.10.4-approach#6.10.4) above).

6.11 Radar Vectors

<section id="6.12-visual-approach">
<h1><a class="header-anchor" href="#6.12-visual-approach"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.12  Visual Approach</h1>
<section class="reference"></section>
<section id="6.12.1">
<h3><a class="header-anchor" href="#6.12.1">6.12.1</a></h3>
<section class="reference">
<p>A visual approach is an approach to a runway at an aerodrome conducted under IFR but where the pilot proceeds by visual reference when cleared to do so. This means that the pilot <strong class="red">must</strong> be visual before the Controller can clear the aircraft for the visual approach.</p>
</section>
</section>
<section id="6.12.2">
<h3><a class="header-anchor" href="#6.12.2">6.12.2</a></h3>
<section class="reference">
<p>Although similar to Radar Vectors, the underlying difference is that when aircraft are under Radar Vectors, they will not receive an approach clearance. Therefore when aircraft call in following Radar Vectors, Tower would issue a pattern entry, a sequence (if required) and then a clearance. Whereas with the visual approach, they do not require a pattern entry because they have been cleared for the approach, therefore only a sequence (if required) and a clearance is issued by Tower.</p>
</section>
</section>
<section id="6.12.3">
<h3><a class="header-anchor" href="#6.12.3">6.12.3</a></h3>
<section class="reference">
<p>There are multiple ways in which a visual approach can be given to the pilot but generally speaking, and terrain permitting; the aircraft <strong class="red">should</strong> be positioned in a recognizable position such as downwind, base, or even straight in. The Approach Controller must then ask the aircraft to &quot;report airport in sight&quot; (note that Controllers can still continue to issue vectors to the pilot after requesting the pilot to &quot;report airport in sight&quot;). Once the pilot has responded with the airport in sight, the Approach Controller can clear them for the visual approach (with or without a final vector) and then hand them off to Tower/Unicom as appropriate.</p>
</section>
</section>
<section id="6.12.4">
<h3><a class="header-anchor" href="#6.12.4">6.12.4</a></h3>
<section class="reference">
<p>There are some specific procedures for various aerodromes but this relies on both the Controller and pilot using the correct chart. This can be adopted using the same method as already outlined <em>(see <a href="/guide/atc-manual/6.-radar/6.8-approach#6.8.6" class="documentation-content-link">6.8.6</a> above).</em></p>
</section>
</section>
<section id="6.12.5">
<h3><a class="header-anchor" href="#6.12.5">6.12.5</a></h3>
<section class="reference">
<p>The Visual Approach at JFK, New York (KJFK) onto RWY13L/R <em>(see image 6.12.5.1 below)</em> is a good example of a specific procedure. For this procedure the Controller would need to vector aircraft towards the start which in this case is the Canarsie (CRI) VOR. The chart requires an inbound heading of 043, so a heading of 040 or similar would be appropriate and the minimum altitude for the approach is 2000ft initially. The pilot can then be instructed to report the airport in sight, and once they have, cleared for the visual approach and handed over to Tower. In this particular case, the aircraft would essentially be handed over on a right base for RWY13L/R, however if the pilot fails to report the airport in sight, further vectors may be required to ensure they continue to follow the prescribed tracks until they have confirmed that they are visual with the airport.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/kjfk-chart.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/kjfk-chart@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/kjfk-chart@3x.jpg 3x" alt="Image 6.12.5.1 - KJFK FAA Chart" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.12.5.1 - KJFK FAA Chart</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


6.12  Visual Approach

6.12.1

A visual approach is an approach to a runway at an aerodrome conducted under IFR but where the pilot proceeds by visual reference when cleared to do so. This means that the pilot must{.red} be visual before the Controller can clear the aircraft for the visual approach.

6.12.2

Although similar to Radar Vectors, the underlying difference is that when aircraft are under Radar Vectors, they will not receive an approach clearance. Therefore when aircraft call in following Radar Vectors, Tower would issue a pattern entry, a sequence (if required) and then a clearance. Whereas with the visual approach, they do not require a pattern entry because they have been cleared for the approach, therefore only a sequence (if required) and a clearance is issued by Tower.

6.12.3

There are multiple ways in which a visual approach can be given to the pilot but generally speaking, and terrain permitting; the aircraft should{.red} be positioned in a recognizable position such as downwind, base, or even straight in. The Approach Controller must then ask the aircraft to "report airport in sight" (note that Controllers can still continue to issue vectors to the pilot after requesting the pilot to "report airport in sight"). Once the pilot has responded with the airport in sight, the Approach Controller can clear them for the visual approach (with or without a final vector) and then hand them off to Tower/Unicom as appropriate.

6.12.4

There are some specific procedures for various aerodromes but this relies on both the Controller and pilot using the correct chart. This can be adopted using the same method as already outlined (see 6.8.6 above).

6.12.5

The Visual Approach at JFK, New York (KJFK) onto RWY13L/R (see image 6.12.5.1 below) is a good example of a specific procedure. For this procedure the Controller would need to vector aircraft towards the start which in this case is the Canarsie (CRI) VOR. The chart requires an inbound heading of 043, so a heading of 040 or similar would be appropriate and the minimum altitude for the approach is 2000ft initially. The pilot can then be instructed to report the airport in sight, and once they have, cleared for the visual approach and handed over to Tower. In this particular case, the aircraft would essentially be handed over on a right base for RWY13L/R, however if the pilot fails to report the airport in sight, further vectors may be required to ensure they continue to follow the prescribed tracks until they have confirmed that they are visual with the airport.

Image 6.12.5.1 - KJFK FAA Chart

6.12 Visual Approach

<section id="6.13-handover-to-tower%2Funicom">
<h1><a class="header-anchor" href="#6.13-handover-to-tower%2Funicom"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.13  Handover to Tower/Unicom</h1>
<section class="reference"></section>
<section id="6.13.1">
<h3><a class="header-anchor" href="#6.13.1">6.13.1</a></h3>
<section class="reference">
<p>Before the Controller can hand an aircraft over to Tower/Unicom they <strong class="red">must</strong> ensure that the aircraft has successfully established on the ‘intended approach path’ <strong class="red">AND</strong> has an acceptable closure rate with the aircraft ahead.</p>
</section>
</section>
<section id="6.13.2">
<h3><a class="header-anchor" href="#6.13.2">6.13.2</a></h3>
<section class="reference">
<p>The ‘intended approach path’ for the GPS Approach, Radar Vectors and a Visual Approach are covered above <em>(see <a href="/guide/atc-manual/6.-radar/6.9-global-positioning-system-(gps)-approach#6.9.3" class="documentation-content-link">6.9.3</a>, <a href="/guide/atc-manual/6.-radar/6.11-radar-vectors#6.11.1" class="documentation-content-link">6.11.1</a> and <a href="/guide/atc-manual/6.-radar/6.12-visual-approach#6.12.3" class="documentation-content-link">6.12.3</a> above respectively)</em>. For the ILS approach, Controllers <strong class="red">must</strong> ensure that the aircraft has successfully intercepted the LOC, this is especially important when parallel operations are in use <em>(see 6.13.2.1 below)</em>. Do not confuse aircraft being established on the LOC, with ‘being in the cone’ – aircraft must be aligned with the centerline of the runway to be established, regardless of their position inside or outside of the cone.</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-right-vs-wrong.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-right-vs-wrong@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-intercept-right-vs-wrong@3x.jpg 3x" alt="Image 6.13.2.1 - Radar intercept right vs wrong" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.13.2.1 - Radar intercept right vs wrong</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.13.3">
<h3><a class="header-anchor" href="#6.13.3">6.13.3</a></h3>
<section class="reference">
<p>Radar Controllers <strong class="red">must</strong> ensure that the aircraft closure rate is ‘acceptable’ - this can vary but a good example is if Aircraft A is established on the ILS ahead, and you have just issued the final intercept to Aircraft B, ask yourself what is their relative speed to each other? If Aircraft A is at 180kts GS (Groundspeed), and Aircraft B is intercepting at 250kts GS with only 3nm spacing, what will happen? Don’t give this problem to the Tower Controller, they do not have extensive speed commands like Radar - instead, slow Aircraft B down first, then hand over. All Tower Controllers can give to aircraft is ‘maintain slowest practical speed’, this could then have a knock-on effect if you have a line of aircraft on approach.</p>
</section>
</section>
<section id="6.13.4">
<h3><a class="header-anchor" href="#6.13.4">6.13.4</a></h3>
<section class="reference">
<p>Additionally, to ensure that the separation provided between aircraft is not compromised, Radar Controllers <strong class="red">should</strong> keep aircraft on frequency until they can be sure of this (this may mean that aircraft are kept on frequency down the final approach until fairly 'late' - this is encouraged over the Tower Controller having to issue a go-around due to separation issues). It is important to note that the Tower Controller's main responsibility (when a Radar Controller is present), is issuing the landing clearance; separation is set by the Radar Controller and therefore keeping aircraft until much later (even until 5 miles final) may be required to ensure this is provided.</p>
</section>
</section>
</section>


6.13  Handover to Tower/Unicom
6.13.1
Before the Controller can hand an aircraft over to Tower/Unicom they must{.red} ensure that the aircraft has successfully established on the ‘intended approach path’ AND{.red} has an acceptable closure rate with the aircraft ahead.
6.13.2
The ‘intended approach path’ for the GPS Approach, Radar Vectors and a Visual Approach are covered above (see 6.9.3-approach#6.9.3), 6.11.1 and 6.12.3 above respectively). For the ILS approach, Controllers must{.red} ensure that the aircraft has successfully intercepted the LOC, this is especially important when parallel operations are in use (see 6.13.2.1 below). Do not confuse aircraft being established on the LOC, with ‘being in the cone’ – aircraft must be aligned with the centerline of the runway to be established, regardless of their position inside or outside of the cone.
Image 6.13.2.1 - Radar intercept right vs wrong
6.13.3
Radar Controllers must{.red} ensure that the aircraft closure rate is ‘acceptable’ - this can vary but a good example is if Aircraft A is established on the ILS ahead, and you have just issued the final intercept to Aircraft B, ask yourself what is their relative speed to each other? If Aircraft A is at 180kts GS (Groundspeed), and Aircraft B is intercepting at 250kts GS with only 3nm spacing, what will happen? Don’t give this problem to the Tower Controller, they do not have extensive speed commands like Radar - instead, slow Aircraft B down first, then hand over. All Tower Controllers can give to aircraft is ‘maintain slowest practical speed’, this could then have a knock-on effect if you have a line of aircraft on approach.
6.13.4
Additionally, to ensure that the separation provided between aircraft is not compromised, Radar Controllers should{.red} keep aircraft on frequency until they can be sure of this (this may mean that aircraft are kept on frequency down the final approach until fairly 'late' - this is encouraged over the Tower Controller having to issue a go-around due to separation issues). It is important to note that the Tower Controller's main responsibility (when a Radar Controller is present), is issuing the landing clearance; separation is set by the Radar Controller and therefore keeping aircraft until much later (even until 5 miles final) may be required to ensure this is provided.

6.13 Handover to Tower/Unicom

<section id="6.14-aircraft-speed">
<h1><a class="header-anchor" href="#6.14-aircraft-speed"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 6.14  Aircraft Speed</h1>
<section class="reference"></section>
<section id="indicated-airspeed-(ias)-vs.-groundspeed-(gs)">
<h2><a class="header-anchor" href="#indicated-airspeed-(ias)-vs.-groundspeed-(gs)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Indicated Airspeed (IAS) Vs. Groundspeed (GS)</h2>
<section class="reference"></section>
<section id="6.14.1">
<h3><a class="header-anchor" href="#6.14.1">6.14.1</a></h3>
<section class="reference">
<p>There is a common misconception between the relationship between Indicated Airspeed (IAS) and Groundspeed (GS). For simplicity the reasons behind the difference are not covered, however there are two things that will ultimately affect the relationship: wind and altitude!</p>
</section>
</section>
<section id="6.14.2">
<h3><a class="header-anchor" href="#6.14.2">6.14.2</a></h3>
<section class="reference">
<p>Wind: if there is a tailwind of 20kts, that means there is 20kts of wind pushing the aircraft along in addition to its normal speed, so 180kts IAS will become 200kts GS. Similarly, if there is 20kts of headwind, that means there is 20kts of wind pushing against the aircraft, so 180kts IAS becomes 160kts GS.</p>
</section>
</section>
<section id="6.14.3">
<h3><a class="header-anchor" href="#6.14.3">6.14.3</a></h3>
<section class="reference">
<p>Altitude: as the altitude of aircraft increases, so will the difference between IAS and GS. Below are some very ‘ball-park’ figures which can be used for reference. With the aircraft flying at 250kts IAS with no wind:</p>
<p>3000ft           260kts GS (+10)</p>
<p>6000ft           270kts GS (+20)</p>
<p>9000ft           290kts GS (+40)</p>
<p>12000ft          300kts GS (+50)</p>
</section>
</section>
<section id="6.14.4">
<h3><a class="header-anchor" href="#6.14.4">6.14.4</a></h3>
<section class="reference">
<p>An aircraft's current IAS (Mach Number above FL280) is displayed on their information tab when opened along with other data, all speed commands are referenced to IAS or Mach Number although GS is displayed on the radar screen to assist controllers in the effects of altitude and wind <em>(see <a href="/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.2" class="documentation-content-link">6.14.2</a> and <a href="/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.3" class="documentation-content-link">6.14.3</a> above)</em>.</p>
</section>
</section>
</section>
<section id="mach-number-(m)">
<h2><a class="header-anchor" href="#mach-number-(m)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Mach Number (M)</h2>
<section class="reference"></section>
<section id="6.14.5">
<h3><a class="header-anchor" href="#6.14.5">6.14.5</a></h3>
<section class="reference">
<p>IAS is converted to Mach Number at FL280, with all speed referred to as Mach above this Flight Level. Below is a table that highlights typical cruising Mach Numbers for different aircraft types. Controllers <strong class="red">should</strong> note that altitude and weight have a huge influence on Mach Number and therefore if aircraft are asked to perform outside of the speed ranges below, the aircraft may be unable to comply:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Category</th>
<th>Aircraft Types</th>
<th>Speed Range (M)</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Category">Turbo Prop</td>
<td data-label="Aircraft Types">e.g. TBM-930, Dash-8 Q400 etc</td>
<td data-label="Speed Range (M)">.51 - .53</td>
</tr>
<tr>
<td data-label="Category">Narrow Body Jet</td>
<td data-label="Aircraft Types">e.g. CRJ, E-Jet, A320, B737 etc</td>
<td data-label="Speed Range (M)">.75 - .80</td>
</tr>
<tr>
<td data-label="Category">Wide Body Jet</td>
<td data-label="Aircraft Types">e.g. A330, B777, MD-11 etc</td>
<td data-label="Speed Range (M)">.82 - .85</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>
<section id="speed-control">
<h2><a class="header-anchor" href="#speed-control"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Speed Control</h2>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Controllers <strong class="red">should</strong> choose 2-3 common speeds (such as 250kts, 210kts and 180kts) which can be added to the quick command tab list when in use. Using the same speed assignments helps standardize the approach and manage traffic!</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="6.14.6">
<h3><a class="header-anchor" href="#6.14.6">6.14.6</a></h3>
<section class="reference">
<p>When issuing speed control to aircraft, Controllers <strong class="red">must</strong> utilize the following techniques:</p>
<ul>
<li>Compensate for closure rate when assigning speed adjustment in an 'in-trail' situation by either reducing the trailing aircraft speed first, or increasing the lead aircraft speed first <em>(see <a href="/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.7" class="documentation-content-link">6.14.7</a> below)</em></li>
<li>Implement specific speed control if required to maintain spacing</li>
<li>Allow sufficient time and distance to achieve speed adjustments (especially at higher altitudes, greater speed differentials and when aircraft are in a clean configuration)</li>
<li>Ensure that aircraft are able to operate in a clean configuration for as long as possible <em>(see <a href="/guide/atc-manual/6.-radar/6.14-aircraft-speed#6.14.8" class="documentation-content-link">6.14.8</a> below)</em></li>
</ul>
</section>
</section>
<section id="6.14.7">
<h3><a class="header-anchor" href="#6.14.7">6.14.7</a></h3>
<section class="reference">
<p>It is important to note that if you have only given a speed assignment to a single aircraft (when multiple aircraft are involved), it is unlikely this will provide the necessary separation, for example:</p>
<ul>
<li>Aircraft #1 can't be reduced unless aircraft #2 has been given a limit that won't overtake aircraft #1</li>
<li>Aircraft #2 can't reduce to follow aircraft #1, if aircraft #1 has not been issued with any speed control</li>
</ul>
<p>In addition, &quot;Adjust Speed to Follow Aircraft Ahead&quot; can be useful but does not replace the necessity for specific speed commands, therefore Controllers <strong class="red">should</strong> use it sparingly. As well as this, if used without assigning a specific speed command to the aircraft ahead, it is likely that the lead aircraft will start to dictate the entire flow into the airport, Controllers <strong class="red">must</strong> avoid this.</p>
</section>
</section>
<section id="6.14.8">
<h3><a class="header-anchor" href="#6.14.8">6.14.8</a></h3>
<section class="reference">
<p>When aircraft slow down, they may need to configure; Controllers <strong class="red">should</strong> avoid slowing aircraft down where they will have to configure until within 20 track miles to touchdown - expeditious approaches are only possible if aircraft keep their speed up until close to the airport.</p>
</section>
</section>
<section id="6.14.9">
<h3><a class="header-anchor" href="#6.14.9">6.14.9</a></h3>
<section class="reference">
<p>Once aircraft are cleared for the approach, speed is at their discretion unless they are subsequently assigned a speed command</p>
</section>
</section>


6.14  Aircraft Speed
Indicated Airspeed (IAS) Vs. Groundspeed (GS)
6.14.1
There is a common misconception between the relationship between Indicated Airspeed (IAS) and Groundspeed (GS). For simplicity the reasons behind the difference are not covered, however there are two things that will ultimately affect the relationship: wind and altitude!
6.14.2
Wind: if there is a tailwind of 20kts, that means there is 20kts of wind pushing the aircraft along in addition to its normal speed, so 180kts IAS will become 200kts GS. Similarly, if there is 20kts of headwind, that means there is 20kts of wind pushing against the aircraft, so 180kts IAS becomes 160kts GS.
6.14.3
Altitude: as the altitude of aircraft increases, so will the difference between IAS and GS. Below are some very ‘ball-park’ figures which can be used for reference. With the aircraft flying at 250kts IAS with no wind:
3000ft           260kts GS (+10)
6000ft           270kts GS (+20)
9000ft           290kts GS (+40)
12000ft          300kts GS (+50)
6.14.4
An aircraft's current IAS (Mach Number above FL280) is displayed on their information tab when opened along with other data, all speed commands are referenced to IAS or Mach Number although GS is displayed on the radar screen to assist controllers in the effects of altitude and wind (see 6.14.2 and 6.14.3 above).
Mach Number (M)
6.14.5
IAS is converted to Mach Number at FL280, with all speed referred to as Mach above this Flight Level. Below is a table that highlights typical cruising Mach Numbers for different aircraft types. Controllers should{.red} note that altitude and weight have a huge influence on Mach Number and therefore if aircraft are asked to perform outside of the speed ranges below, the aircraft may be unable to comply:
| Category        | Aircraft Types                  | Speed Range (M) |
| --------------- | ------------------------------- | --------------- |
| Turbo Prop      | e.g. TBM-930, Dash-8 Q400 etc   | .51 - .53       |
| Narrow Body Jet | e.g. CRJ, E-Jet, A320, B737 etc | .75 - .80       |
| Wide Body Jet   | e.g. A330, B777, MD-11 etc      | .82 - .85       |
Speed Control
Tip
: Controllers should{.red} choose 2-3 common speeds (such as 250kts, 210kts and 180kts) which can be added to the quick command tab list when in use. Using the same speed assignments helps standardize the approach and manage traffic!
6.14.6
When issuing speed control to aircraft, Controllers must{.red} utilize the following techniques:
Compensate for closure rate when assigning speed adjustment in an 'in-trail' situation by either reducing the trailing aircraft speed first, or increasing the lead aircraft speed first (see 6.14.7 below)
Implement specific speed control if required to maintain spacing
Allow sufficient time and distance to achieve speed adjustments (especially at higher altitudes, greater speed differentials and when aircraft are in a clean configuration)
Ensure that aircraft are able to operate in a clean configuration for as long as possible (see 6.14.8 below)
6.14.7
It is important to note that if you have only given a speed assignment to a single aircraft (when multiple aircraft are involved), it is unlikely this will provide the necessary separation, for example:
Aircraft #1 can't be reduced unless aircraft #2 has been given a limit that won't overtake aircraft #1
Aircraft #2 can't reduce to follow aircraft #1, if aircraft #1 has not been issued with any speed control
In addition, "Adjust Speed to Follow Aircraft Ahead" can be useful but does not replace the necessity for specific speed commands, therefore Controllers should{.red} use it sparingly. As well as this, if used without assigning a specific speed command to the aircraft ahead, it is likely that the lead aircraft will start to dictate the entire flow into the airport, Controllers must{.red} avoid this.
6.14.8
When aircraft slow down, they may need to configure; Controllers should{.red} avoid slowing aircraft down where they will have to configure until within 20 track miles to touchdown - expeditious approaches are only possible if aircraft keep their speed up until close to the airport.
6.14.9
Once aircraft are cleared for the approach, speed is at their discretion unless they are subsequently assigned a speed command

6.14 Aircraft Speed

<section id="7.1-overview">
<h1><a class="header-anchor" href="#7.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.1  Overview</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>It is the responsibility of the Candidate/Controller to ensure they meet the minimum requirements <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> above)</em> <strong class="red">BEFORE</strong> seeking training. Failure to do so may invalidate your training request and further progression may not be granted for a period of time</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7.1.1">
<h3><a class="header-anchor" href="#7.1.1">7.1.1</a></h3>
<section class="reference">
<p>The Recruitment Team (Recruiters) have two main responsibilities, these are to manage new entrants during the recruitment process to join IFATC and secondly, to administer all theory and practical tests, with the final say on the result of the test (i.e. pass/fail).</p>
</section>
</section>
<section id="7.1.2">
<h3><a class="header-anchor" href="#7.1.2">7.1.2</a></h3>
<section class="reference">
<p>The Training Team (Trainers) is here to educate and train individuals within their specific area of study as Air Traffic Controllers, ensuring test readiness and a high standard of controlling.</p>
</section>
</section>
<section id="7.1.3">
<h3><a class="header-anchor" href="#7.1.3">7.1.3</a></h3>
<section class="reference">
<p>For the purposes of this manual, the following definitions are provided:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Definition</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Definition">Candidate / Recruit</td>
<td data-label="Meaning">A potential IFATC Controller that is in the recruitment process</td>
</tr>
<tr>
<td data-label="Definition">Controller</td>
<td data-label="Meaning">A current IFATC Controller that is seeking training for their current position* or for the position of Officer (Radar Training)</td>
</tr>
<tr>
<td data-label="Definition">Trainee</td>
<td data-label="Meaning">A Candidate/Controller that has a Trainer assigned and is in the training process</td>
</tr>
</tbody>
</table>
<p>*Controller development is a key aspect within IFATC, Controllers can expect feedback during their time within the IFATC Team <strong class="red">and are expected to utilize this to improve.</strong></p>
</section>
</section>
<section id="7.1.4">
<h3><a class="header-anchor" href="#7.1.4">7.1.4</a></h3>
<section class="reference">
<p>All aspects of controlling are trained but Candidates and Controllers <strong class="red">should</strong> be aware of areas they wish to target so that the time allocated can be utilized to the Controllers benefit. <strong class="red">The Trainer reserves the right to terminate training at any point if they deem that the Trainee is not progressing or showing the dedication required.</strong> A training session can vary in length but typically last no longer than 1 hour. Trainees <strong class="red">must not</strong> have more than 1 training session in any 24 hour period.</p>
</section>
</section>


7.1  Overview
Tip
: It is the responsibility of the Candidate/Controller to ensure they meet the minimum requirements (see 1A.3.1 above) BEFORE{.red} seeking training. Failure to do so may invalidate your training request and further progression may not be granted for a period of time
7.1.1
The Recruitment Team (Recruiters) have two main responsibilities, these are to manage new entrants during the recruitment process to join IFATC and secondly, to administer all theory and practical tests, with the final say on the result of the test (i.e. pass/fail).
7.1.2
The Training Team (Trainers) is here to educate and train individuals within their specific area of study as Air Traffic Controllers, ensuring test readiness and a high standard of controlling.
7.1.3
For the purposes of this manual, the following definitions are provided:
| Definition          | Meaning                                                      |
| ------------------- | ------------------------------------------------------------ |
| Candidate / Recruit | A potential IFATC Controller that is in the recruitment process |
| Controller          | A current IFATC Controller that is seeking training for their current position* or for the position of Officer (Radar Training) |
| Trainee             | A Candidate/Controller that has a Trainer assigned and is in the training process |
Controller development is a key aspect within IFATC, Controllers can expect feedback during their time within the IFATC Team and are expected to utilize this to improve.*{.red}
7.1.4
All aspects of controlling are trained but Candidates and Controllers should{.red} be aware of areas they wish to target so that the time allocated can be utilized to the Controllers benefit. The Trainer reserves the right to terminate training at any point if they deem that the Trainee is not progressing or showing the dedication required.{.red} A training session can vary in length but typically last no longer than 1 hour. Trainees must not{.red} have more than 1 training session in any 24 hour period.

7.1 Overview

<section id="7.2-ifatc-support-documentation">
<h1><a class="header-anchor" href="#7.2-ifatc-support-documentation"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.2  IFATC Support Documentation</h1>
<section class="reference"></section>
<section id="7.2.1">
<h3><a class="header-anchor" href="#7.2.1">7.2.1</a></h3>
<section class="reference">
<p>The IFATC Support Documentation is a series of supplementary sections to this manual that contain any confidential procedures and guidelines for the various Departments to operate under. They are not available for public view and therefore <strong class="red">must not</strong> be shared outside of the relevant team channels without prior authorization.</p>
</section>
</section>
<section id="7.2.2">
<h3><a class="header-anchor" href="#7.2.2">7.2.2</a></h3>
<section class="reference">
<p>The following table lists the document names, and which Department they belong to:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Document Name</th>
<th>Department</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Document Name">Section 7A</td>
<td data-label="Department">Training</td>
</tr>
<tr>
<td data-label="Document Name">Section 7B</td>
<td data-label="Department">Testing</td>
</tr>
<tr>
<td data-label="Document Name">Section 7C</td>
<td data-label="Department">Recruitment</td>
</tr>
<tr>
<td data-label="Document Name">Section 7D</td>
<td data-label="Department">Supervisors</td>
</tr>
<tr>
<td data-label="Document Name">Section 7E</td>
<td data-label="Department">Appeals</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


7.2  IFATC Support Documentation
7.2.1
The IFATC Support Documentation is a series of supplementary sections to this manual that contain any confidential procedures and guidelines for the various Departments to operate under. They are not available for public view and therefore must not{.red} be shared outside of the relevant team channels without prior authorization.
7.2.2
The following table lists the document names, and which Department they belong to:
| Document Name | Department  |
| ------------- | ----------- |
| Section 7A    | Training    |
| Section 7B    | Testing     |
| Section 7C    | Recruitment |
| Section 7D    | Supervisors |
| Section 7E    | Appeals     |

7.2 IFATC Support Documentation

<section id="7.3-initial-theory-and-practical-tests">
<h1><a class="header-anchor" href="#7.3-initial-theory-and-practical-tests"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.3  Initial Theory and Practical Tests</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Candidates <strong class="red">must</strong> ensure that they have an adequate amount of battery life on their device and a good/reliable internet connection</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7.3.1">
<h3><a class="header-anchor" href="#7.3.1">7.3.1</a></h3>
<section class="reference">
<p>The minimum requirements for joining IFATC as well as the time limit for re-test if unsuccessful, are outlined on the IFC channel <a href="https://community.infiniteflight.com/t/infinite-flight-atc-recruiting/462983" class="documentation-content-link">here</a>.</p>
</section>
</section>
<section id="7.3.2">
<h3><a class="header-anchor" href="#7.3.2">7.3.2</a></h3>
<section class="reference">
<p>Candidates are allowed to go through the full recruitment process as outlined within the IFC channel without any training if they wish to do so. However, The Training Team is available <strong class="red">should</strong> they wish to utilize this resource. To ensure Candidates are committed to joining, training <strong class="red">must not</strong> be provided until the trainee has passed The Initial Theory Test as a <strong class="red">MINIMUM</strong>.</p>
</section>
</section>
<section id="7.3.3">
<h3><a class="header-anchor" href="#7.3.3">7.3.3</a></h3>
<section class="reference">
<p>All Candidates seeking training are required to notify their Recruiter who will change their status on the <a href="https://www.if-atc.com" class="documentation-content-link">website</a>. A Trainer will be in contact within 7 days and all further correspondence will be through this individual.</p>
</section>
</section>
<section id="7.3.4">
<h3><a class="header-anchor" href="#7.3.4">7.3.4</a></h3>
<section class="reference">
<p>All aircraft present at The Initial Practical Test <strong class="red">must</strong> fly conservative patterns, and <strong class="red">must not</strong> be bigger than a Boeing 757 (GA and fighter aircraft are also acceptable). The following table lists the items that are included in the Initial Practical test:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Element</th>
<th>Proficiency Required*</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Test Element">Pushback</td>
<td data-label="Proficiency Required*">Correctly identifies if the area is clear for  the aircraft to initiate a pushback maneuver.</td>
</tr>
<tr>
<td data-label="Test Element">Taxi</td>
<td data-label="Proficiency Required*">Effective ground management, runway selection  (usually based on wind) and use of give way commands if appropriate.</td>
</tr>
<tr>
<td data-label="Test Element">Departure</td>
<td data-label="Proficiency Required*">Use of LUAW or anticipated separation if  appropriate, use of left/right traffic for aircraft remaining in the pattern.</td>
</tr>
<tr>
<td data-label="Test Element"><strong class="red">Aircraft Separation</strong></td>
<td data-label="Proficiency Required*">Ensures that separation minima is complied with at all times, i.e. Dep/Dep, Arr/Arr, Dep/Arr and Intersecting <em>(see <a href="/guide/atc-manual/3.-tower/3.1-separation#3.1.1" class="documentation-content-link">3.1.1</a> above)</em></td>
</tr>
<tr>
<td data-label="Test Element">Runway  Usage</td>
<td data-label="Proficiency Required*">Effective use of both runways, and  facilitating requests for runway changes.</td>
</tr>
<tr>
<td data-label="Test Element">Pattern</td>
<td data-label="Proficiency Required*">Effective pattern management including  pattern entries (if required), sequencing (if required) and clearances.</td>
</tr>
<tr>
<td data-label="Test Element">Transition</td>
<td data-label="Proficiency Required*">Transition given that keeps inbound aircraft  within tower airspace and clear of aircraft in the pattern.</td>
</tr>
<tr>
<td data-label="Test Element">Go-Around</td>
<td data-label="Proficiency Required*">Proactive monitoring of separation between arrivals  and use of go-arounds when required.</td>
</tr>
<tr>
<td data-label="Test Element">Runway  Exit</td>
<td data-label="Proficiency Required*">Use of exit runway command with appropriate  use of expedite (if required).</td>
</tr>
</tbody>
</table>
<p><strong class="red">Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed</strong></p>
<p>*The recruiter has the final say on the result of the test <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1" class="documentation-content-link">7.1.1</a> above).</em></p>
</section>
</section>


7.3  Initial Theory and Practical Tests
Tip
: Candidates must{.red} ensure that they have an adequate amount of battery life on their device and a good/reliable internet connection
7.3.1
The minimum requirements for joining IFATC as well as the time limit for re-test if unsuccessful, are outlined on the IFC channel here.
7.3.2
Candidates are allowed to go through the full recruitment process as outlined within the IFC channel without any training if they wish to do so. However, The Training Team is available should{.red} they wish to utilize this resource. To ensure Candidates are committed to joining, training must not{.red} be provided until the trainee has passed The Initial Theory Test as a MINIMUM{.red}.
7.3.3
All Candidates seeking training are required to notify their Recruiter who will change their status on the website. A Trainer will be in contact within 7 days and all further correspondence will be through this individual.
7.3.4
All aircraft present at The Initial Practical Test must{.red} fly conservative patterns, and must not{.red} be bigger than a Boeing 757 (GA and fighter aircraft are also acceptable). The following table lists the items that are included in the Initial Practical test:
| Test Element                  | Proficiency Required*                                        |
| ----------------------------- | ------------------------------------------------------------ |
| Pushback                      | Correctly identifies if the area is clear for  the aircraft to initiate a pushback maneuver. |
| Taxi                          | Effective ground management, runway selection  (usually based on wind) and use of give way commands if appropriate. |
| Departure                     | Use of LUAW or anticipated separation if  appropriate, use of left/right traffic for aircraft remaining in the pattern. |
| Aircraft Separation{.red} | Ensures that separation minima is complied with at all times, i.e. Dep/Dep, Arr/Arr, Dep/Arr and Intersecting (see 3.1.1 above) |
| Runway  Usage                 | Effective use of both runways, and  facilitating requests for runway changes. |
| Pattern                       | Effective pattern management including  pattern entries (if required), sequencing (if required) and clearances. |
| Transition                    | Transition given that keeps inbound aircraft  within tower airspace and clear of aircraft in the pattern. |
| Go-Around                     | Proactive monitoring of separation between arrivals  and use of go-arounds when required. |
| Runway  Exit                  | Use of exit runway command with appropriate  use of expedite (if required). |
Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed{.red}
The recruiter has the final say on the result of the test (see 7.1.1 above).*

7.3 Initial Theory and Practical Tests

<section id="7.4-promotion-to-specialist-(check-ride)">
<h1><a class="header-anchor" href="#7.4-promotion-to-specialist-(check-ride)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.4  Promotion to Specialist (Check Ride)</h1>
<section class="reference"></section>
<section id="7.4.1">
<h3><a class="header-anchor" href="#7.4.1">7.4.1</a></h3>
<section class="reference">
<p>When Controllers are eligible for promotion to the rank of Specialist (based on activity, performance and feedback), they will receive a DM informing them of their promotion on a probationary basis.</p>
</section>
</section>
<section id="7.4.2">
<h3><a class="header-anchor" href="#7.4.2">7.4.2</a></h3>
<section class="reference">
<p>The probation period <strong class="red">should not</strong> exceed 7 days, unless it is due to Moderator/Supervisor availability <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-promotion-to-specialist-(check-ride)#7.4.4" class="documentation-content-link">7.4.4</a> below</em>). During this time, Controllers <strong class="red">must</strong>:</p>
<ul>
<li>
<p>Include an asterisk symbol (i.e. *) in <em>#controllers</em> when announcing that they are opening</p>
</li>
<li>
<p>Control Bravo classification airports where possible (Charlie classification airports are acceptable if they provide for adequate evaluation)</p>
</li>
<li>
<p>Control on a regular basis (at least 3 separate occasions)</p>
</li>
</ul>
</section>
</section>
<section id="7.4.3">
<h3><a class="header-anchor" href="#7.4.3">7.4.3</a></h3>
<section class="reference">
<p>Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback in all cases.</p>
</section>
</section>
<section id="7.4.4">
<h3><a class="header-anchor" href="#7.4.4">7.4.4</a></h3>
<section class="reference">
<p>If Moderators and/or Supervisors are unable to attend one of the Controllers sessions during their probation period, their probation will be extended provided that they have followed <strong class="red">ALL</strong> the instructions set out within this section <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-promotion-to-specialist-(check-ride)#7.4.2" class="documentation-content-link">7.4.2</a> above)</em> and in particular, controlling on a regular basis in which to maximize the chance of a review. If this is not the case, they will be demoted back to Apprentice, and a subsequent promotion will take place in due course.</p>
</section>
</section>
<section id="7.4.5">
<h3><a class="header-anchor" href="#7.4.5">7.4.5</a></h3>
<section class="reference">
<p>If the Controller has been successful, the probation period will end with immediate effect and the instructions contained within this section will no longer need to be followed. If they are unsuccessful, a waiting period will be given before they re-enter the Check Ride phase; in which time, the Controller will be able to improve in the areas briefed.</p>
</section>
</section>
<section id="7.4.6">
<h3><a class="header-anchor" href="#7.4.6">7.4.6</a></h3>
<section class="reference">
<p>Eligibility for promotion is dealt with on a case by case basis, and not solely on time served. With this is mind, Apprentice Controllers <strong class="red">must</strong> avoid asking when they will be promoted; and instead, <strong class="red">should</strong> focus on providing a good quality ATC service.</p>
</section>
</section>
<section id="7.4.7">
<h3><a class="header-anchor" href="#7.4.7">7.4.7</a></h3>
<section class="reference">
<p>A summary of the process for becoming a Specialist is contained within the following flow chart:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-specialist.svg" alt="Image 7.4.7.1 - Promotion to Specialist Flowchart" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.7.1 - Promotion to Specialist Flowchart</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


7.4  Promotion to Specialist (Check Ride)

7.4.1

When Controllers are eligible for promotion to the rank of Specialist (based on activity, performance and feedback), they will receive a DM informing them of their promotion on a probationary basis.

7.4.2

The probation period should not{.red} exceed 7 days, unless it is due to Moderator/Supervisor availability (see 7.4.4#7.4.4) below). During this time, Controllers must{.red}:

 Include an asterisk symbol (i.e. ) in #controllers* when announcing that they are opening

 Control Bravo classification airports where possible (Charlie classification airports are acceptable if they provide for adequate evaluation)

 Control on a regular basis (at least 3 separate occasions)

7.4.3

Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback in all cases.

7.4.4

If Moderators and/or Supervisors are unable to attend one of the Controllers sessions during their probation period, their probation will be extended provided that they have followed ALL{.red} the instructions set out within this section (see 7.4.2#7.4.2) above) and in particular, controlling on a regular basis in which to maximize the chance of a review. If this is not the case, they will be demoted back to Apprentice, and a subsequent promotion will take place in due course.

7.4.5

If the Controller has been successful, the probation period will end with immediate effect and the instructions contained within this section will no longer need to be followed. If they are unsuccessful, a waiting period will be given before they re-enter the Check Ride phase; in which time, the Controller will be able to improve in the areas briefed.

7.4.6

Eligibility for promotion is dealt with on a case by case basis, and not solely on time served. With this is mind, Apprentice Controllers must{.red} avoid asking when they will be promoted; and instead, should{.red} focus on providing a good quality ATC service.

7.4.7

A summary of the process for becoming a Specialist is contained within the following flow chart:

Image 7.4.7.1 - Promotion to Specialist Flowchart

7.4 Promotion to Specialist (Check Ride)

<section id="7.5-radar-theory-and-practical-tests">
<h1><a class="header-anchor" href="#7.5-radar-theory-and-practical-tests"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7.5 Radar Theory and Practical Tests</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Controllers <strong class="red">must</strong> ensure that they have an adequate amount of battery life on their device and a good/reliable internet connection</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7.5.1">
<h3><a class="header-anchor" href="#7.5.1">7.5.1</a></h3>
<section class="reference">
<p>The minimum requirements for becoming an Officer and subsequently controlling radar facilities is outlined within the rank structure <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> above).</em> Controllers that wish to upgrade <strong class="red">must</strong> contact a Recruiter (Controllers <strong class="red">must</strong> ensure they meet the minimum requirements <strong class="red">BEFORE APPLYING</strong>); in addition, they <strong class="red">must</strong> have demonstrated a high level of competency in the following areas:</p>
<ul>
<li>
<p>Knowledge of this manual in its entirety, complying fully where instructed (i.e. use of <strong class="red">must</strong>/<strong class="red">must not</strong>)</p>
</li>
<li>
<p>Able to manage a high level of traffic on both Ground and Tower frequencies, simultaneously</p>
</li>
<li>
<p>Controlling at featured airports or the main Bravo airfield’s on the ATC Schedule</p>
</li>
<li>
<p>Controlling during busy periods such as FNF, weekends and flashflights</p>
</li>
</ul>
</section>
</section>
<section id="7.5.2">
<h3><a class="header-anchor" href="#7.5.2">7.5.2</a></h3>
<section class="reference">
<p>All training is considered optional with the exception of Radar Training – Controllers that wish to upgrade to Radar <strong class="red">must</strong> have training, and meet the standards required <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.4" class="documentation-content-link">7.5.4</a> below)</em> <strong class="red">BEFORE</strong> The Radar Practical Test.</p>
</section>
</section>
<section id="7.5.3">
<h3><a class="header-anchor" href="#7.5.3">7.5.3</a></h3>
<section class="reference">
<p>The Recruiter will conduct a review on the performance of the Controller that has requested Radar Training, Supervisors may be polled if further details are required. The requirements laid out within this section <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.1" class="documentation-content-link">7.5.1</a> above)</em> will assist the Recruiter (and Supervisors if required) in gauging the Controller’s competency and suitability for the role. If the review is deemed successful, the Controller will be placed in the &quot;Training Pool&quot; ready for Trainer allocation. If the Controller is considered not to be ready, a set waiting period (minimum of 30 days) will be assigned where the Controller <strong class="red">must</strong> endeavor to address the feedback given. Subsequent reviews will continue until there is no doubt that they are ready for the position.</p>
</section>
</section>
<section id="7.5.4">
<h3><a class="header-anchor" href="#7.5.4">7.5.4</a></h3>
<section class="reference">
<p>Following a successful review, a Trainer will be assigned who will contact the Controller and commence Radar Training (training for the position of Radar is mandatory). At an appropriate point during training, as decided by the Trainer; a Recruiter will issue the The Radar Theory Test (and debrief as appropriate on the result) <strong class="red">BEFORE</strong> commencement of The Radar Practical Test. The Radar Practical Test will be organized at the Trainer’s discretion however a Recruiter will be required for the official test <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1" class="documentation-content-link">7.1.1</a> above).</em> Controlling on the Training Server is only authorized for Controllers that have met the requirements for upgrade to the rank of Officer <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.3-rank-structure#1a.3.1" class="documentation-content-link">1A.3.1</a> above)</em>, and have <strong class="red">STARTED</strong> their Radar Training with a Trainer.</p>
</section>
</section>
<section id="7.5.5">
<h3><a class="header-anchor" href="#7.5.5">7.5.5</a></h3>
<section class="reference">
<p>Whilst under Training, Controllers may wish to seek fellow Controllers to fly radar patterns on the IFATC Server for extra practice if the Trainer is not available. Provided the Controller has the Trainer’s permission, the use of the Discord <em>#training-time[1-3]</em> channels is authorized to try and find Controllers that are free (Controllers <strong class="red">must</strong> only use a channel that is currently not in use for a training session).</p>
</section>
</section>
<section id="7.5.6">
<h3><a class="header-anchor" href="#7.5.6">7.5.6</a></h3>
<section class="reference">
<p>All aircraft present at The Radar Practical Test <strong class="red">must</strong> fly in accordance with the radar service being provided; in addition, any aircraft type can be selected but it <strong class="red">must</strong> be deemed suitable to meet the training objective. The following table lists the items that are included in the Radar Practical test:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Element</th>
<th>Proficiency Required*</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Test Element"><strong class="red">Terrain  Separation</strong></td>
<td data-label="Proficiency Required*">Ensures that a minimum of 1000ft clearance is  maintained with terrain at all times.</td>
</tr>
<tr>
<td data-label="Test Element"><strong class="red">Aircraft  Separation</strong></td>
<td data-label="Proficiency Required*">Ensures that a minimum of 3nm separation  laterally or 1000ft separation vertically is maintained at all times.</td>
</tr>
<tr>
<td data-label="Test Element">Time  Management</td>
<td data-label="Proficiency Required*">Consistently provides an expeditious approach  to all aircraft under radar control, minimal vectoring to get aircraft in the  correct area for an approach and combined commands (altitude and heading)  where appropriate.</td>
</tr>
<tr>
<td data-label="Test Element">Approach  Type</td>
<td data-label="Proficiency Required*">Able to deliver all types of service as  outlined within this manual, and in particular, consistent timing and the  correct technique (below the G/S) for the intercept heading of the ILS/GPS  Approach.</td>
</tr>
<tr>
<td data-label="Test Element">Go-Around</td>
<td data-label="Proficiency Required*">Correct use of missed-approach command and  subsequent vectoring. Proactive monitoring and use of go-around if aircraft  set up incorrectly for the type of approach they are flying.</td>
</tr>
</tbody>
</table>
<p><strong class="red">Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed</strong></p>
<p>* The recruiter has the final say on the result of the test <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.1" class="documentation-content-link">7.1.1</a> above).</em></p>
</section>
</section>
<section id="7.5.7">
<h3><a class="header-anchor" href="#7.5.7">7.5.7</a></h3>
<section class="reference">
<p>Controllers that are successful in The Radar Practical Test will be promoted and placed in the Officer Check Ride phase for a period of 30 days. During this time, Controllers <strong class="red">must</strong> include an asterisk symbol (i.e. *) in <em>#controllers</em> when announcing that they are opening. Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Officer Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback in all cases. <strong class="red">During this time, Controllers are expected to be responsible in their new role; starting off slowly and ensuring quality of service, over quantity.</strong></p>
</section>
</section>
<section id="7.5.8">
<h3><a class="header-anchor" href="#7.5.8">7.5.8</a></h3>
<section class="reference">
<p>A summary of the process for becoming an Officer is contained within the following flow chart:</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-recruitment.svg" alt="Image 7.5.8.1 - Promotion to Officer Flowchart" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.5.8.1 - Promotion to Officer Flowchart</figcaption>
        </figure>
      </p>
</section>
</section>


7.5 Radar Theory and Practical Tests
Tip
: Controllers must{.red} ensure that they have an adequate amount of battery life on their device and a good/reliable internet connection
7.5.1
The minimum requirements for becoming an Officer and subsequently controlling radar facilities is outlined within the rank structure (see 1A.3.1 above). Controllers that wish to upgrade must{.red} contact a Recruiter (Controllers must{.red} ensure they meet the minimum requirements BEFORE APPLYING{.red}); in addition, they must{.red} have demonstrated a high level of competency in the following areas:
 Knowledge of this manual in its entirety, complying fully where instructed (i.e. use of must{.red}/must not{.red})
 Able to manage a high level of traffic on both Ground and Tower frequencies, simultaneously
 Controlling at featured airports or the main Bravo airfield’s on the ATC Schedule
 Controlling during busy periods such as FNF, weekends and flashflights
7.5.2
All training is considered optional with the exception of Radar Training – Controllers that wish to upgrade to Radar must{.red} have training, and meet the standards required (see 7.5.4 below) BEFORE{.red} The Radar Practical Test.
7.5.3
The Recruiter will conduct a review on the performance of the Controller that has requested Radar Training, Supervisors may be polled if further details are required. The requirements laid out within this section (see 7.5.1 above) will assist the Recruiter (and Supervisors if required) in gauging the Controller’s competency and suitability for the role. If the review is deemed successful, the Controller will be placed in the "Training Pool" ready for Trainer allocation. If the Controller is considered not to be ready, a set waiting period (minimum of 30 days) will be assigned where the Controller must{.red} endeavor to address the feedback given. Subsequent reviews will continue until there is no doubt that they are ready for the position.
7.5.4
Following a successful review, a Trainer will be assigned who will contact the Controller and commence Radar Training (training for the position of Radar is mandatory). At an appropriate point during training, as decided by the Trainer; a Recruiter will issue the The Radar Theory Test (and debrief as appropriate on the result) BEFORE{.red} commencement of The Radar Practical Test. The Radar Practical Test will be organized at the Trainer’s discretion however a Recruiter will be required for the official test (see 7.1.1 above). Controlling on the Training Server is only authorized for Controllers that have met the requirements for upgrade to the rank of Officer (see 1A.3.1 above), and have STARTED{.red} their Radar Training with a Trainer.
7.5.5
Whilst under Training, Controllers may wish to seek fellow Controllers to fly radar patterns on the IFATC Server for extra practice if the Trainer is not available. Provided the Controller has the Trainer’s permission, the use of the Discord #training-time[1-3] channels is authorized to try and find Controllers that are free (Controllers must{.red} only use a channel that is currently not in use for a training session).
7.5.6
All aircraft present at The Radar Practical Test must{.red} fly in accordance with the radar service being provided; in addition, any aircraft type can be selected but it must{.red} be deemed suitable to meet the training objective. The following table lists the items that are included in the Radar Practical test:
| Test Element                   | Proficiency Required*                                        |
| ------------------------------ | ------------------------------------------------------------ |
| Terrain  Separation{.red}  | Ensures that a minimum of 1000ft clearance is  maintained with terrain at all times. |
| Aircraft  Separation{.red} | Ensures that a minimum of 3nm separation  laterally or 1000ft separation vertically is maintained at all times. |
| Time  Management               | Consistently provides an expeditious approach  to all aircraft under radar control, minimal vectoring to get aircraft in the  correct area for an approach and combined commands (altitude and heading)  where appropriate. |
| Approach  Type                 | Able to deliver all types of service as  outlined within this manual, and in particular, consistent timing and the  correct technique (below the G/S) for the intercept heading of the ILS/GPS  Approach. |
| Go-Around                      | Correct use of missed-approach command and  subsequent vectoring. Proactive monitoring and use of go-around if aircraft  set up incorrectly for the type of approach they are flying. |
Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed{.red}
\* The recruiter has the final say on the result of the test (see 7.1.1 above).
7.5.7
Controllers that are successful in The Radar Practical Test will be promoted and placed in the Officer Check Ride phase for a period of 30 days. During this time, Controllers must{.red} include an asterisk symbol (i.e. ) in #controllers* when announcing that they are opening. Moderators and/or Supervisors will receive automatic notifications when the Controller opens, and those that are available will attend the Controller’s current session and monitor their performance. At the end of the Officer Check Ride phase, all evaluations will be collated, with a final review taking place. The Controller will be informed if they have been successful or unsuccessful, and given feedback in all cases. During this time, Controllers are expected to be responsible in their new role; starting off slowly and ensuring quality of service, over quantity.{.red}
7.5.8
A summary of the process for becoming an Officer is contained within the following flow chart:
Image 7.5.8.1 - Promotion to Officer Flowchart

7.5 Radar Theory and Practical Tests

<section id="7a.1-overview">
<h1><a class="header-anchor" href="#7a.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7A.1 Overview</h1>
<section class="reference"></section>
<section id="7a.1.1">
<h3><a class="header-anchor" href="#7a.1.1">7A.1.1</a></h3>
<section class="reference">
<p>The Training Team (Trainers) is here to educate and train individuals within their specific area of study as Air Traffic Controllers, ensuring test readiness and a high standard of controlling.</p>
</section>
</section>
<section id="7a.1.2">
<h3><a class="header-anchor" href="#7a.1.2">7A.1.2</a></h3>
<section class="reference">
<p>Trainers <strong class="red">must</strong> ensure that all requirements are met before taking on a Trainee. In an instance where there is ambiguity, this manual overrides any conflicting information. Trainers unsure as to the circumstances of a Candidate/Controller (or possible exemptions to the prescribed guidelines) <strong class="red">must</strong> consult a Recruiter for a final verdict.</p>
</section>
</section>
<section id="7a.1.3">
<h3><a class="header-anchor" href="#7a.1.3">7A.1.3</a></h3>
<section class="reference">
<p>Members of the Training Team are selected on a merit-only basis with regards to past service and current skill levels as a Controller. Merit is based on, but not limited to:</p>
<ul>
<li>
<p>community service</p>
</li>
<li>
<p>good behavior</p>
</li>
<li>
<p>comprehensive understanding of this manual</p>
</li>
<li>
<p>and other considerations as appropriate at the time of choosing</p>
</li>
</ul>
<p>Any Controller considered <strong class="red">must</strong> hold the rank of Officer as a minimum in order to qualify (this is to guarantee that all components of the training program can be taught).</p>
</section>
</section>
<section id="7a.1.4">
<h3><a class="header-anchor" href="#7a.1.4">7A.1.4</a></h3>
<section class="reference">
<p>Trainers <strong class="red">must</strong> comply with the following when in the process of being added as members of the team:</p>
<ul>
<li>Meet with the Training Team Administrator over a call in order to outline expectations and bring up questions should the need arise</li>
<li>Be subject to a 30 day probationary period during which time the trainer <strong class="red">must not</strong> take more than 3 trainees at any given time (this is to allow Trainers to decide whether or not the role is for them and to avoid staffing issues if there is a lapse in coverage)</li>
</ul>
</section>
</section>
<section id="7a.1.5">
<h3><a class="header-anchor" href="#7a.1.5">7A.1.5</a></h3>
<section class="reference">
<p>As representatives of the Training Team, Trainers <strong class="red">must</strong> conduct themselves in a professional manner, reflective of the team and service they provide on a daily basis. Trainers may be demoted or removed from the Training Team if expectations are not met.</p>
</section>
</section>
<section id="7a.1.6">
<h3><a class="header-anchor" href="#7a.1.6">7A.1.6</a></h3>
<section class="reference">
<p>Complaints pertaining to the behavior of Trainers <strong class="red">should</strong> be forwarded to the Training Team Administrator, and/or then to the IFATC Manager based on the circumstances of the given situation(s).</p>
</section>
</section>
<section id="7a.1.7">
<h3><a class="header-anchor" href="#7a.1.7">7A.1.7</a></h3>
<section class="reference">
<p>When new Trainers are selected, they will be added to the following channels within Discord:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#testers</td>
<td data-label="Purpose">Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers <strong class="red">must not</strong> &quot;react&quot; to the request if all available slots are already filled.</td>
</tr>
<tr>
<td data-label="Channel">#testers[1-3]</td>
<td data-label="Purpose">All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
<tr>
<td data-label="Channel">#trainers</td>
<td data-label="Purpose">Main channel for coordination purposes within the Training Team.</td>
</tr>
<tr>
<td data-label="Channel">#trainer-trainee[1-3]</td>
<td data-label="Purpose">Voice Channels specifically available for coordination between the Trainer and Trainee <strong>ONLY</strong> <em>(for further guidance see <a href="/guide/atc-manual/7a.-trainers/7a.1-overview#7a.1.8" class="documentation-content-link">7A.1.8</a> below)</em>.</td>
</tr>
<tr>
<td data-label="Channel">#training-time</td>
<td data-label="Purpose">Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in.</td>
</tr>
<tr>
<td data-label="Channel">#training-time[1-3]</td>
<td data-label="Purpose">All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7a.1.8">
<h3><a class="header-anchor" href="#7a.1.8">7A.1.8</a></h3>
<section class="reference">
<p>The use of VC's for coordination between Trainers and their Trainees <strong class="red">must</strong> be conducted in accordance with Section 1A - New Entrants <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.1-discord-communication-guidelines#1a.1.5" class="documentation-content-link">1A.1.5</a> and <a href="/guide/atc-manual/1a.-new-entrants/1a.2-general-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> above)</em>. It’s intended use is for one-on-one training through the session but may also be used to brief/debrief before or after a session, or for general Trainer/Trainee meetings. The VCs may also be used for Trainer/Trainee meetings or to brief upcoming sessions. It is entirely voluntary and at the discretion of the Trainer and Trainee.</p>
</section>
</section>
</section>


7A.1 Overview
7A.1.1
The Training Team (Trainers) is here to educate and train individuals within their specific area of study as Air Traffic Controllers, ensuring test readiness and a high standard of controlling.
7A.1.2
Trainers must{.red} ensure that all requirements are met before taking on a Trainee. In an instance where there is ambiguity, this manual overrides any conflicting information. Trainers unsure as to the circumstances of a Candidate/Controller (or possible exemptions to the prescribed guidelines) must{.red} consult a Recruiter for a final verdict.
7A.1.3
Members of the Training Team are selected on a merit-only basis with regards to past service and current skill levels as a Controller. Merit is based on, but not limited to:
community service
good behavior
comprehensive understanding of this manual
and other considerations as appropriate at the time of choosing
Any Controller considered must{.red} hold the rank of Officer as a minimum in order to qualify (this is to guarantee that all components of the training program can be taught).
7A.1.4
Trainers must{.red} comply with the following when in the process of being added as members of the team:
Meet with the Training Team Administrator over a call in order to outline expectations and bring up questions should the need arise
Be subject to a 30 day probationary period during which time the trainer must not{.red} take more than 3 trainees at any given time (this is to allow Trainers to decide whether or not the role is for them and to avoid staffing issues if there is a lapse in coverage)
7A.1.5
As representatives of the Training Team, Trainers must{.red} conduct themselves in a professional manner, reflective of the team and service they provide on a daily basis. Trainers may be demoted or removed from the Training Team if expectations are not met.
7A.1.6
Complaints pertaining to the behavior of Trainers should{.red} be forwarded to the Training Team Administrator, and/or then to the IFATC Manager based on the circumstances of the given situation(s).
7A.1.7
When new Trainers are selected, they will be added to the following channels within Discord:
| Channel               | Purpose                                                      |
| --------------------- | ------------------------------------------------------------ |
| #testers              | Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers must not{.red} "react" to the request if all available slots are already filled. |
| #testers[1-3]         | All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel must{.red} be used at any one time). |
| #trainers             | Main channel for coordination purposes within the Training Team. |
| #trainer-trainee1-3] | Voice Channels specifically available for coordination between the Trainer and Trainee ONLY (for further guidance see [7A.1.8 below). |
| #training-time        | Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in. |
| #training-time[1-3]   | All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel must{.red} be used at any one time). |
7A.1.8
The use of VC's for coordination between Trainers and their Trainees must{.red} be conducted in accordance with Section 1A - New Entrants (see 1A.1.5 and 1A.2.1 above). It’s intended use is for one-on-one training through the session but may also be used to brief/debrief before or after a session, or for general Trainer/Trainee meetings. The VCs may also be used for Trainer/Trainee meetings or to brief upcoming sessions. It is entirely voluntary and at the discretion of the Trainer and Trainee.

7A.1 Overview

<section id="7a.2-training-structure">
<h1><a class="header-anchor" href="#7a.2-training-structure"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7A.2 Training Structure</h1>
<section class="reference"></section>
<section id="7a.2.1">
<h3><a class="header-anchor" href="#7a.2.1">7A.2.1</a></h3>
<section class="reference">
<p>Candidates/Controllers <strong class="red">must</strong> ensure that all requirements are met before requesting training. These requirements and the full process are outlined in the following locations:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Trainee Type</th>
<th>Location</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Trainee Type">Candidate</td>
<td data-label="Location"><a href="https://community.infiniteflight.com/t/atc-training/416531" class="documentation-content-link">ATC Training Post</a> on the IFC Forum</td>
</tr>
<tr>
<td data-label="Trainee Type">Controller</td>
<td data-label="Location">See <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5-radar-theory-and-practical-tests" class="documentation-content-link">7.5</a> above</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7a.2.2">
<h3><a class="header-anchor" href="#7a.2.2">7A.2.2</a></h3>
<section class="reference">
<p>All Trainers <strong class="red">must</strong> proactively monitor the website for <a href="https://if-atc.com/atc/waitlist" class="documentation-content-link">training requests</a>. Trainees <strong class="red">should</strong> be claimed within a 7 day timeframe by accepting the request <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.1" class="documentation-content-link">7A.3.1</a> below).</em></p>
</section>
</section>
<section id="7a.2.3">
<h3><a class="header-anchor" href="#7a.2.3">7A.2.3</a></h3>
<section class="reference">
<p>Once a Trainer has accepted a training request <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.1" class="documentation-content-link">7A.3.1</a> below)</em>, the Trainer <strong class="red">must</strong> message the Trainee to begin dialogue and to organize training sessions. All sessions <strong class="red">must</strong> be added to the <a href="https://if-atc.com/atc/schedule" class="documentation-content-link">Training Schedule</a> on the website. Each session is broken down into half hour blocks every day on a weekly basis, allowing for multiple Trainers and Trainees to coordinate their own sessions. Training <strong class="red">must not</strong> be conducted between 1700Z and 2359Z on Fridays unless prior authorization has been given due to limited availability of the trainer and/or trainee.</p>
</section>
</section>
<section id="7a.2.4">
<h3><a class="header-anchor" href="#7a.2.4">7A.2.4</a></h3>
<section class="reference">
<p>A first-come, first-served basis is utilized for slots in the Training Schedule. Equal priority is shared with respect to the time(s) booked by those who need them (not applicable to testing).</p>
</section>
</section>
<section id="7a.2.5">
<h3><a class="header-anchor" href="#7a.2.5">7A.2.5</a></h3>
<section class="reference">
<p>Trainers <strong class="red">should</strong> utilize the &quot;Request Pilots On Discord&quot; website function 30 - 60 minutes before a scheduled training session <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.3" class="documentation-content-link">7A.3.3</a> below)</em> which will send a notification to the <em>#training-time</em> Discord channel for pilots. Once the specific training channel to be used for that session is established, all subsequent coordination <strong class="red">should</strong> only be in that channel.</p>
</section>
</section>
<section id="7a.2.6">
<h3><a class="header-anchor" href="#7a.2.6">7A.2.6</a></h3>
<section class="reference">
<p>Trainers reserve the right to terminate training at any point <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.4" class="documentation-content-link">7.1.4</a> above and <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.6" class="documentation-content-link">7A.3.6</a> below)</em>, but <strong class="red">should</strong> speak to the Trainee's Recruiter <strong>BEFORE</strong> termination as this may effect the Trainee's eligibility for joining IFATC (or future promotions if already within IFATC). A two strike policy is normally observed allowing the Trainee the benefit of the doubt when mistakes are made however appeals may be reviewed by the Training Team Administrator and/or the IFATC Manager on a case-by-case basis.</p>
<p>Reasons for termination can include (but are not limited to):</p>
<ul>
<li>failure to respond or communicate with their assigned Trainer(s)</li>
<li>failure to attend scheduled training sessions</li>
<li>not receptive to feedback and/or a bad attitude</li>
</ul>
</section>
</section>
<section id="7a.2.7">
<h3><a class="header-anchor" href="#7a.2.7">7A.2.7</a></h3>
<section class="reference">
<p>For Initial Training, Trainers <strong class="red">must</strong> conduct training at airports with parallel and/or intersecting runways depending on the circumstances of their Trainees. The following table outlines recommended airports for Radar Training (Trainers are encouraged to rotate through each site on a consistent basis). Trainers <strong class="red">must not</strong> train (or allow training to take place) at test sites in order to avoid any unfair advantages <em>(see <a href="/guide/atc-manual/7b.-testers/7b.2-initial-testing#7b.2.1" class="documentation-content-link">7B.2.1</a> and <a href="/guide/atc-manual/7b.-testers/7b.3-radar-testing#7b.3.2" class="documentation-content-link">7B.3.2</a> below)</em>.</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Airport</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Airport">CYVR</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">CYXE</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KAUS</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KEGE</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KFWA</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KGJT</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KLSV</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KPVU</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KSBP</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">LPPT</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">MGTK</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">OAKB</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">PHOG</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">PHTO</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">SACO</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">SBGL</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">SCEL</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">SKRG</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">YSCB</td>
<td data-label="Notes"></td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7a.2.8">
<h3><a class="header-anchor" href="#7a.2.8">7A.2.8</a></h3>
<section class="reference">
<p>Before approving any Trainee to conduct a practical test, Trainers <strong class="red">must</strong> consult the following checklists to ensure that all necessary materials are covered before the Trainee proceeds forward:</p>
<table class="ui table definition unstackable documentation-table checklist fixed">
<thead>
<tr>
<th>Initial</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Initial">Weather</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Pushback / Taxi Commands</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Ground Monitoring and Situational Awareness</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Gate Holds</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Runway Crossings</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Broadcast Commands</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Runway Assignments</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Usage of &quot;Expect Runway&quot;</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Take-Off / Landing / Option Clearances</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Separation Requirements</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Pattern / Transition Commands</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Sequencing</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Initial">Runway Exit Commands</td>
<td data-label="">Y / N</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table checklist fixed">
<thead>
<tr>
<th>Radar</th>
<th></th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Radar">Radar User Interface</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">ILS / GPS / Visual Approach</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Separation Requirements</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Flight Following [VFR]</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Check In [IFR]</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Radar Vectors / Patterns</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">SIDs / STARs</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Center</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Speed Commands</td>
<td data-label="">Y / N</td>
</tr>
<tr>
<td data-label="Radar">Airspace</td>
<td data-label="">Y / N</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


7A.2 Training Structure
7A.2.1
Candidates/Controllers must{.red} ensure that all requirements are met before requesting training. These requirements and the full process are outlined in the following locations:
| Trainee Type | Location                                                     |
| ------------ | ------------------------------------------------------------ |
| Candidate    | ATC Training Post on the IFC Forum |
| Controller   | See 7.5 above |
7A.2.2
All Trainers must{.red} proactively monitor the website for training requests. Trainees should{.red} be claimed within a 7 day timeframe by accepting the request (see 7A.3.1 below).
7A.2.3
Once a Trainer has accepted a training request (see 7A.3.1 below), the Trainer must{.red} message the Trainee to begin dialogue and to organize training sessions. All sessions must{.red} be added to the Training Schedule on the website. Each session is broken down into half hour blocks every day on a weekly basis, allowing for multiple Trainers and Trainees to coordinate their own sessions. Training must not{.red} be conducted between 1700Z and 2359Z on Fridays unless prior authorization has been given due to limited availability of the trainer and/or trainee.
7A.2.4
A first-come, first-served basis is utilized for slots in the Training Schedule. Equal priority is shared with respect to the time(s) booked by those who need them (not applicable to testing).
7A.2.5
Trainers should{.red} utilize the "Request Pilots On Discord" website function 30 - 60 minutes before a scheduled training session (see 7A.3.3 below) which will send a notification to the #training-time Discord channel for pilots. Once the specific training channel to be used for that session is established, all subsequent coordination should{.red} only be in that channel.
7A.2.6
Trainers reserve the right to terminate training at any point (see 7.1.4 above and 7A.3.6 below), but should{.red} speak to the Trainee's Recruiter BEFORE termination as this may effect the Trainee's eligibility for joining IFATC (or future promotions if already within IFATC). A two strike policy is normally observed allowing the Trainee the benefit of the doubt when mistakes are made however appeals may be reviewed by the Training Team Administrator and/or the IFATC Manager on a case-by-case basis.
Reasons for termination can include (but are not limited to):
failure to respond or communicate with their assigned Trainer(s)
failure to attend scheduled training sessions
not receptive to feedback and/or a bad attitude
7A.2.7
For Initial Training, Trainers must{.red} conduct training at airports with parallel and/or intersecting runways depending on the circumstances of their Trainees. The following table outlines recommended airports for Radar Training (Trainers are encouraged to rotate through each site on a consistent basis). Trainers must not{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages (see 7B.2.1 and 7B.3.2 below).
| Airport | Notes |
| ------- | ----- |
| CYVR    |       |
| CYXE    |       |
| KAUS    |       |
| KEGE    |       |
| KFWA    |       |
| KGJT    |       |
| KLSV    |       |
| KPVU    |       |
| KSBP    |       |
| LPPT    |       |
| MGTK    |       |
| OAKB    |       |
| PHOG    |       |
| PHTO    |       |
| SACO    |       |
| SBGL    |       |
| SCEL    |       |
| SKRG    |       |
| YSCB    |       |
7A.2.8
Before approving any Trainee to conduct a practical test, Trainers must{.red} consult the following checklists to ensure that all necessary materials are covered before the Trainee proceeds forward:
| Initial                                     |       |
| ------------------------------------------- | ----- |
| Weather                                     | Y / N |
| Pushback / Taxi Commands                    | Y / N |
| Ground Monitoring and Situational Awareness | Y / N |
| Gate Holds                                  | Y / N |
| Runway Crossings                            | Y / N |
| Broadcast Commands                          | Y / N |
| Runway Assignments                          | Y / N |
| Usage of "Expect Runway"                    | Y / N |
| Take-Off / Landing / Option Clearances      | Y / N |
| Separation Requirements                     | Y / N |
| Pattern / Transition Commands               | Y / N |
| Sequencing                                  | Y / N |
| Runway Exit Commands                        | Y / N |
{.checklist}
| Radar                       |       |
| --------------------------- | ----- |
| Radar User Interface        | Y / N |
| ILS / GPS / Visual Approach | Y / N |
| Separation Requirements     | Y / N |
| Flight Following [VFR]      | Y / N |
| Check In [IFR]              | Y / N |
| Radar Vectors / Patterns    | Y / N |
| SIDs / STARs                | Y / N |
| Center                      | Y / N |
| Speed Commands              | Y / N |
| Airspace                    | Y / N |
{.checklist}

7A.2 Training Structure

<section id="7a.3-trainer-admin">
<h1><a class="header-anchor" href="#7a.3-trainer-admin"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7A.3 Trainer Admin</h1>
<section class="reference"></section>
<section id="how-to-accept-a-trainee">
<h2><a class="header-anchor" href="#how-to-accept-a-trainee"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Accept a Trainee</h2>
<section class="reference"></section>
<section id="7a.3.1">
<h3><a class="header-anchor" href="#7a.3.1">7A.3.1</a></h3>
<section class="reference">
<p>The following procedure outlines how to accept a new Candidate/Controller as a Trainee:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Select &quot;Waitlist&quot; from the navigation bar at the top of the screen</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Select &quot;Trainees&quot; from the tab</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Select the &quot;IF Name&quot; of the Trainee that you wish to take on</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>To accept, tap &quot;Accept Assignment (No PM)&quot; or Accept Assignment &amp; PM&quot;. The latter will automatically open the IFC Forum in a new window, allowing a PM to be sent to the Recruit to begin the process</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If you are using iOS, make sure to allow pop ups! Without this, the &quot;Accept Assignment &amp; PM&quot; button may not work</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="how-to-view-the-trainee-profile">
<h2><a class="header-anchor" href="#how-to-view-the-trainee-profile"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to View the Trainee Profile</h2>
<section class="reference"></section>
<section id="7a.3.2">
<h3><a class="header-anchor" href="#7a.3.2">7A.3.2</a></h3>
<section class="reference">
<p>The following procedure outlines how to view a Trainee's profile:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>The &quot;My Dashboard&quot; tab will automatically show and under &quot;My Recruits&quot; will be a list of current Trainee's that are assigned to you</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Select the name of the Trainee under &quot;IFC&quot; and their profile will open showing all information for that Trainee</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Alternatively, you can select the &quot;Recruits&quot; tab from the navigation bar at the top of the screen and use the search function to find the Trainee</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="how-to-schedule-a-training-session">
<h2><a class="header-anchor" href="#how-to-schedule-a-training-session"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Schedule a Training Session</h2>
<section class="reference"></section>
<section id="7a.3.3">
<h3><a class="header-anchor" href="#7a.3.3">7A.3.3</a></h3>
<section class="reference">
<p>The following procedure outlines how to schedule a training session:</p>
<dl>
<dt>Step 1</dt>
<dd>Coordinate with the Trainee to check availability</dd>
<dt>Step 2</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Schedule&quot; from the navigation bar at the top of the screen</dd>
<dt>Step 4</dt>
<dd>Select the day you want to check by tapping the date within the calendar. You can then check for conflicts and ensure that you select a date/time that is available</dd>
<dt>Step 5</dt>
<dd>Access the Trainee's Profile <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.2" class="documentation-content-link">7A.3.2</a> above)</em> and select the &quot;Sessions&quot; tab</dd>
<dt>Step 6</dt>
<dd>Tap &quot;Schedule a Session&quot;</dd>
<dt>Step 7</dt>
<dd>Populate the required fields and at the bottom, tap &quot;Add Session&quot; for it to be scheduled</dd>
<dt>Step 8</dt>
<dd>The &quot;pencil&quot; symbol can be used to make edits and the &quot;bin&quot; symbol if you would like to delete/cancel the session</dd>
<dt>Step 9</dt>
<dd>At the discretion of the Trainer (although usually 30-60 minutes before the scheduled start time), access the session by tapping the 'pencil' symbol and tap &quot;Request Pilots On Discord&quot; for a notification to be sent to the <em>#training-time</em> Discord channel</dd>
<dt>Step 10</dt>
<dd>&quot;Attendees&quot; can be added as they volunteer for the session (or once the session is completed if the Trainer prefers) using the same editing process above</dd>
</dl>
</section>
</section>
</section>
<section id="trainee-ready-to-take-the-radar-theory-test">
<h2><a class="header-anchor" href="#trainee-ready-to-take-the-radar-theory-test"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Trainee ready to take The Radar Theory Test</h2>
<section class="reference"></section>
<section id="7a.3.4">
<h3><a class="header-anchor" href="#7a.3.4">7A.3.4</a></h3>
<section class="reference">
<p>Candidates would have already taken The Initial Theory Test before commencement of training, therefore the following procedure only applies to Controllers that are undergoing Radar Training:</p>
<dl>
<dt>Step 1</dt>
<dd>The Controller can take The Radar Theory Test at any time <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.4" class="documentation-content-link">7.5.4</a> above)</em>, therefore when they are ready, Trainers can message the Recruiter (as listed on the Trainee's profile) that they are ready for the test</dd>
<dt>Step 2</dt>
<dd>All test correspondence will be between the Recruiter and Trainee</dd>
<dt>Step 3</dt>
<dd>The Recruiter will inform the Trainer when the theory test has been completed by the Trainee</dd>
</dl>
</section>
</section>
</section>
<section id="trainee-ready-to-take-the-radar-practical-test">
<h2><a class="header-anchor" href="#trainee-ready-to-take-the-radar-practical-test"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Trainee ready to take The Radar Practical Test</h2>
<section class="reference"></section>
<section id="7a.3.5">
<h3><a class="header-anchor" href="#7a.3.5">7A.3.5</a></h3>
<section class="reference">
<p>When the Trainer is satisfied that the Controller is ready for The Radar Practical Test <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.4" class="documentation-content-link">7.5.4</a> above)</em>, the following procedure can be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Trainers can message the Recruiter (as listed on the Trainee's profile) that they are ready for the test</dd>
<dt>Step 2</dt>
<dd>All test correspondence will be between the Recruiter and Trainee</dd>
<dt>Step 3</dt>
<dd>The Recruiter will inform the Trainer when the practical test has been completed by the Trainee</dd>
</dl>
</section>
</section>
</section>
<section id="how-to-terminate-a-trainee">
<h2><a class="header-anchor" href="#how-to-terminate-a-trainee"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Terminate a Trainee</h2>
<section class="reference"></section>
<section id="7a.3.6">
<h3><a class="header-anchor" href="#7a.3.6">7A.3.6</a></h3>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>Trainers <strong class="red">should</strong> speak to the Trainee's Recruiter <strong>BEFORE</strong> terminating training as this may effect the Trainee's eligibility for joining IFATC (or promotion if already within IFATC)</dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Trainee's Profile using the steps outlined above <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.3-trainer-admin#7a.3.2" class="documentation-content-link">7A.3.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Select &quot;notes&quot; from the navigation bar on their profile and then add any applicable notes to highlight the reasoning (this can be saved by clicking &quot;Add Note&quot;)</dd>
<dt>Step 4</dt>
<dd>Select &quot;---&quot; in the &quot;Trainer&quot; field and then scroll to the bottom and tap &quot;Save&quot; to un-assign the Trainer</dd>
<dt>Step 5</dt>
<dd>Liaise with the Trainee's Recruiter who can then inform the Trainee that their training (and possibly the entire recruitment process - if applicable) has been terminated</dd>
</dl>
</section>
</section>
</section>


7A.3 Trainer Admin
How to Accept a Trainee
7A.3.1
The following procedure outlines how to accept a new Candidate/Controller as a Trainee:
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Select "Waitlist" from the navigation bar at the top of the screen
Step 3
: Select "Trainees" from the tab
Step 4
: Select the "IF Name" of the Trainee that you wish to take on
Step 5
: To accept, tap "Accept Assignment (No PM)" or Accept Assignment & PM". The latter will automatically open the IFC Forum in a new window, allowing a PM to be sent to the Recruit to begin the process
Tip
: If you are using iOS, make sure to allow pop ups! Without this, the "Accept Assignment & PM" button may not work
How to View the Trainee Profile
7A.3.2
The following procedure outlines how to view a Trainee's profile:
Step 1
: Go to website and login via the "Dashboard"
Step 2
: The "My Dashboard" tab will automatically show and under "My Recruits" will be a list of current Trainee's that are assigned to you
Step 3
:  Select the name of the Trainee under "IFC" and their profile will open showing all information for that Trainee
Tip
: Alternatively, you can select the "Recruits" tab from the navigation bar at the top of the screen and use the search function to find the Trainee
How to Schedule a Training Session
7A.3.3
The following procedure outlines how to schedule a training session:
Step 1
: Coordinate with the Trainee to check availability
Step 2
: Go to website and login via the "Dashboard"
Step 3
: Select "Schedule" from the navigation bar at the top of the screen
Step 4
: Select the day you want to check by tapping the date within the calendar. You can then check for conflicts and ensure that you select a date/time that is available
Step 5
: Access the Trainee's Profile (see 7A.3.2 above) and select the "Sessions" tab
Step 6
: Tap "Schedule a Session"
Step 7
: Populate the required fields and at the bottom, tap "Add Session" for it to be scheduled
Step 8
: The "pencil" symbol can be used to make edits and the "bin" symbol if you would like to delete/cancel the session
Step 9
: At the discretion of the Trainer (although usually 30-60 minutes before the scheduled start time), access the session by tapping the 'pencil' symbol and tap "Request Pilots On Discord" for a notification to be sent to the #training-time Discord channel
Step 10
: "Attendees" can be added as they volunteer for the session (or once the session is completed if the Trainer prefers) using the same editing process above
Trainee ready to take The Radar Theory Test
7A.3.4
Candidates would have already taken The Initial Theory Test before commencement of training, therefore the following procedure only applies to Controllers that are undergoing Radar Training:
Step 1
: The Controller can take The Radar Theory Test at any time (see 7.5.4 above), therefore when they are ready, Trainers can message the Recruiter (as listed on the Trainee's profile) that they are ready for the test
Step 2
: All test correspondence will be between the Recruiter and Trainee
Step 3
: The Recruiter will inform the Trainer when the theory test has been completed by the Trainee
Trainee ready to take The Radar Practical Test
7A.3.5
When the Trainer is satisfied that the Controller is ready for The Radar Practical Test (see 7.5.4 above), the following procedure can be followed:
Step 1
: Trainers can message the Recruiter (as listed on the Trainee's profile) that they are ready for the test
Step 2
: All test correspondence will be between the Recruiter and Trainee
Step 3
: The Recruiter will inform the Trainer when the practical test has been completed by the Trainee
How to Terminate a Trainee
7A.3.6
Tip
: Trainers should{.red} speak to the Trainee's Recruiter BEFORE terminating training as this may effect the Trainee's eligibility for joining IFATC (or promotion if already within IFATC)
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Trainee's Profile using the steps outlined above (see 7A.3.2 above)
Step 3
: Select "notes" from the navigation bar on their profile and then add any applicable notes to highlight the reasoning (this can be saved by clicking "Add Note")
Step 4
: Select "---" in the "Trainer" field and then scroll to the bottom and tap "Save" to un-assign the Trainer
Step 5
: Liaise with the Trainee's Recruiter who can then inform the Trainee that their training (and possibly the entire recruitment process - if applicable) has been terminated

7A.3 Trainer Admin

<section id="7b.1-testing-process">
<h1><a class="header-anchor" href="#7b.1-testing-process"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7B.1 Testing Process</h1>
<section class="reference"></section>
<section id="7b.1.1">
<h3><a class="header-anchor" href="#7b.1.1">7B.1.1</a></h3>
<section class="reference">
<p>All tests (regardless of position) are conducted by Recruiters and issued based on the given materials and/or scenarios provided in this section. Testing scenarios will vary from one recruit to the next. This is to ensure that Candidates/Controllers are better prepared for a wide array of situations found in the Expert Server environment. Care should be taken by the Recruiter(s) to avoid issuing the same testing scenario repeatedly. Only those involved in the test <strong class="red">should</strong> attend (unless previously authorized for a specific purpose) - an audience is not authorized.</p>
</section>
</section>
<section id="7b.1.2">
<h3><a class="header-anchor" href="#7b.1.2">7B.1.2</a></h3>
<section class="reference">
<p>When new Testers are selected, they will be added to the following channels within Discord:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#testers</td>
<td data-label="Purpose">Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers <strong class="red">must not</strong> &quot;react&quot; to the request if all available slots are already filled.</td>
</tr>
<tr>
<td data-label="Channel">#testers[1-3]</td>
<td data-label="Purpose">All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7b.1.3">
<h3><a class="header-anchor" href="#7b.1.3">7B.1.3</a></h3>
<section class="reference">
<p>It is the responsibility of all Recruiter(s), Trainer(s), and Tester(s) to maintain familiarity with this section and follow all procedures accordingly. All instructions provided by the Recruiter(s) <strong class="red">must</strong> be followed in order to ensure a test is carried out in a fair manner. Any behavior not falling in line with the expectations of being a participant of the Testing Team are grounds for review and appropriate disciplinary measures as deemed by the IFATC Manager and/or the IFATC Moderator(s).</p>
</section>
</section>
<section id="7b.1.4">
<h3><a class="header-anchor" href="#7b.1.4">7B.1.4</a></h3>
<section class="reference">
<p>The following table outlines the minimum notice period that <strong class="red">must</strong> be given to a Candidate/Controller before their Initial or Radar Practical Test (including the test location):</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Type</th>
<th>Minimum Notice Period</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Test Type">Initial</td>
<td data-label="Minimum Notice Period">No minimum</td>
</tr>
<tr>
<td data-label="Test Type">Radar</td>
<td data-label="Minimum Notice Period">24 hours*</td>
</tr>
</tbody>
</table>
<p>*The notice period may be reduced if the Recruiter and Candidate/Controller find a mutually acceptable time.</p>
</section>
</section>
</section>


7B.1 Testing Process
7B.1.1
All tests (regardless of position) are conducted by Recruiters and issued based on the given materials and/or scenarios provided in this section. Testing scenarios will vary from one recruit to the next. This is to ensure that Candidates/Controllers are better prepared for a wide array of situations found in the Expert Server environment. Care should be taken by the Recruiter(s) to avoid issuing the same testing scenario repeatedly. Only those involved in the test should{.red} attend (unless previously authorized for a specific purpose) - an audience is not authorized.
7B.1.2
When new Testers are selected, they will be added to the following channels within Discord:
| Channel       | Purpose                                                      |
| ------------- | ------------------------------------------------------------ |
| #testers      | Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers must not{.red} "react" to the request if all available slots are already filled. |
| #testers[1-3] | All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel must{.red} be used at any one time). |
7B.1.3
It is the responsibility of all Recruiter(s), Trainer(s), and Tester(s) to maintain familiarity with this section and follow all procedures accordingly. All instructions provided by the Recruiter(s) must{.red} be followed in order to ensure a test is carried out in a fair manner. Any behavior not falling in line with the expectations of being a participant of the Testing Team are grounds for review and appropriate disciplinary measures as deemed by the IFATC Manager and/or the IFATC Moderator(s).
7B.1.4
The following table outlines the minimum notice period that must{.red} be given to a Candidate/Controller before their Initial or Radar Practical Test (including the test location):
| Test Type | Minimum Notice Period |
| --------- | --------------------- |
| Initial   | No minimum            |
| Radar     | 24 hours*             |
*The notice period may be reduced if the Recruiter and Candidate/Controller find a mutually acceptable time.

7B.1 Testing Process

<section id="7b.2-initial-testing">
<h1><a class="header-anchor" href="#7b.2-initial-testing"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7B.2 Initial Testing</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Trainers <strong class="red">must not</strong> train (or allow training to take place) at test sites in order to avoid any unfair advantages <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.7" class="documentation-content-link">7A.2.7</a> above)</em>.</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7b.2.1">
<h3><a class="header-anchor" href="#7b.2.1">7B.2.1</a></h3>
<section class="reference">
<p>For Initial testing there are three scenarios used, these are outlined below:</p>
<p><strong>Scenario #1:</strong> Standard Test</p>
<p><strong>Locations:</strong> KSSC/KVAD/EDDL</p>
<p><strong>Aircraft Limit:</strong> 7</p>
<p><strong>Description:</strong> Majority of Testers spawn at test airport and wait for the test to begin before taxiing to create ground conflict and complexity. 1 Tester will depart a nearby airport to make a transition request. 1 Tester may depart from a nearby airport to call inbound for pattern work.</p>
<p><strong>Purpose:</strong> Scenario #1 is intended to evaluate a candidate’s ability to manage pattern traffic, recognize a loss of separation, and efficiently use two runways to minimize delays.</p>
<p><strong>Scenario #2:</strong> Inbounds</p>
<p><strong>Locations:</strong> KADW/LFBO/KBOI</p>
<p><strong>Aircraft Limit:</strong> 7</p>
<p><strong>Description:</strong> Majority of Testers will spawn at nearby airports and will call inbound to tower for pattern work. 1-2 Testers should spawn at the test airport and remain in the traffic pattern prior to the inbound aircraft’s arrival. Testers may do full stop and taxi back to create a workload on both tower &amp; ground simultaneously.</p>
<p><strong>Purpose:</strong> Scenario #2 is intended to evaluate the candidate’s ability to integrate arrivals, departures, and closed pattern traffic without undue delay. Varying aircraft characteristics and directions of arrival will require the candidate to strategically manage the flow of traffic.</p>
<p><strong>Scenario #3:</strong> Intersections</p>
<p><strong>Locations:</strong> KSAV/KABE/EDDH</p>
<p><strong>Aircraft Limit:</strong> 6</p>
<p><strong>Description:</strong> Intersection tests should be a mix of inbound for full stop, departing into the pattern,  and inbound for the pattern. For aircraft inbound to a full stop, please do one full stop, taxi back (taxi back to the active and depart again) so that the tested controller has a chance to work a full stop arrival into the gap, taxi you during the test, and again has to depart you in a gap on the intersection.</p>
<p><strong>Purpose:</strong> Scenario #3 is intended to test a candidate’s proficiency with intersecting runways, knowing both the prescribed separation and having the ability to recognize conflict.</p>
</section>
</section>


7B.2 Initial Testing
Tip
: Trainers must not{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages (see 7A.2.7 above).
7B.2.1
For Initial testing there are three scenarios used, these are outlined below:
Scenario #1: Standard Test
Locations: KSSC/KVAD/EDDL
Aircraft Limit: 7
Description: Majority of Testers spawn at test airport and wait for the test to begin before taxiing to create ground conflict and complexity. 1 Tester will depart a nearby airport to make a transition request. 1 Tester may depart from a nearby airport to call inbound for pattern work.
Purpose: Scenario #1 is intended to evaluate a candidate’s ability to manage pattern traffic, recognize a loss of separation, and efficiently use two runways to minimize delays.
Scenario #2: Inbounds
Locations: KADW/LFBO/KBOI
Aircraft Limit: 7
Description: Majority of Testers will spawn at nearby airports and will call inbound to tower for pattern work. 1-2 Testers should spawn at the test airport and remain in the traffic pattern prior to the inbound aircraft’s arrival. Testers may do full stop and taxi back to create a workload on both tower & ground simultaneously.
Purpose: Scenario #2 is intended to evaluate the candidate’s ability to integrate arrivals, departures, and closed pattern traffic without undue delay. Varying aircraft characteristics and directions of arrival will require the candidate to strategically manage the flow of traffic.
Scenario #3: Intersections
Locations: KSAV/KABE/EDDH
Aircraft Limit: 6
Description: Intersection tests should be a mix of inbound for full stop, departing into the pattern,  and inbound for the pattern. For aircraft inbound to a full stop, please do one full stop, taxi back (taxi back to the active and depart again) so that the tested controller has a chance to work a full stop arrival into the gap, taxi you during the test, and again has to depart you in a gap on the intersection.
Purpose: Scenario #3 is intended to test a candidate’s proficiency with intersecting runways, knowing both the prescribed separation and having the ability to recognize conflict.

7B.2 Initial Testing

<section id="7b.3-radar-testing">
<h1><a class="header-anchor" href="#7b.3-radar-testing"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7B.3 Radar Testing</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Trainers <strong class="red">must not</strong> train (or allow training to take place) at test sites in order to avoid any unfair advantages <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.7" class="documentation-content-link">7A.2.7</a> above)</em>.</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7b.3.1">
<h3><a class="header-anchor" href="#7b.3.1">7B.3.1</a></h3>
<section class="reference">
<p>A standard radar test <strong class="red">must</strong> consist of no more than 8 Testers flying in from locations assigned by the Recruiter. Attempts should be made to stagger aircraft departures from their respective locations in order to simulate the kind of traffic flow found on the Expert Server. Over the course of the test, the Trainee must be evaluated on the following material:</p>
<ul>
<li>types of approaches</li>
<li>terrain separation</li>
<li>aircraft separation</li>
<li>time management</li>
<li>and go-arounds/missed approaches <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5.6" class="documentation-content-link">7.5.6</a> above)</em>.</li>
</ul>
<p>Testers must carry out a number of listed maneuvers per instructions from the Recruiter:</p>
<ul>
<li>minimum of ONE departure from the test airport &amp; request a radar pattern</li>
<li>minimum of THREE inbounds with the purpose of a full stop</li>
<li>minimum of ONE inbound with the intent to do one radar pattern after the first touch &amp; go</li>
<li>minimum of TWO pilots <strong class="red">must</strong> have a STAR embedded in their FPLs for testing purposes (they <strong class="red">must</strong> request approaches whilst inbound on those STARs and be handled accordingly)</li>
</ul>
<p>Types of approaches will be assigned at the discretion of the Recruiter. No testing will be done on Center control, though any information on the handling of that position will come from both the training process and relevant supplementary material.</p>
</section>
</section>
<section id="7b.3.2">
<h3><a class="header-anchor" href="#7b.3.2">7B.3.2</a></h3>
<section class="reference">
<p>The following locations are pre-approved radar test sites and are the only locations that <strong class="red">must</strong> be used for the Radar Practical Test:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Airport</th>
<th>Notes</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Airport">KCOS</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KRNO</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KSAN</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">KSLC</td>
<td data-label="Notes"></td>
</tr>
<tr>
<td data-label="Airport">LJLJ</td>
<td data-label="Notes"></td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7b.3.3">
<h3><a class="header-anchor" href="#7b.3.3">7B.3.3</a></h3>
<section class="reference">
<p>In the event that an Officer is demoted, <strong>KLAS</strong> is the retest site that <strong class="red">must</strong> be used.</p>
</section>
</section>


7B.3 Radar Testing
Tip
: Trainers must not{.red} train (or allow training to take place) at test sites in order to avoid any unfair advantages (see 7A.2.7 above).
7B.3.1
A standard radar test must{.red} consist of no more than 8 Testers flying in from locations assigned by the Recruiter. Attempts should be made to stagger aircraft departures from their respective locations in order to simulate the kind of traffic flow found on the Expert Server. Over the course of the test, the Trainee must be evaluated on the following material:
types of approaches
terrain separation
aircraft separation
time management
and go-arounds/missed approaches (see 7.5.6 above).
Testers must carry out a number of listed maneuvers per instructions from the Recruiter:
minimum of ONE departure from the test airport & request a radar pattern
minimum of THREE inbounds with the purpose of a full stop
minimum of ONE inbound with the intent to do one radar pattern after the first touch & go
minimum of TWO pilots must{.red} have a STAR embedded in their FPLs for testing purposes (they must{.red} request approaches whilst inbound on those STARs and be handled accordingly)
Types of approaches will be assigned at the discretion of the Recruiter. No testing will be done on Center control, though any information on the handling of that position will come from both the training process and relevant supplementary material.
7B.3.2
The following locations are pre-approved radar test sites and are the only locations that must{.red} be used for the Radar Practical Test:
| Airport | Notes |
| ------- | ----- |
| KCOS    |       |
| KRNO    |       |
| KSAN    |       |
| KSLC    |       |
| LJLJ    |       |
7B.3.3
In the event that an Officer is demoted, KLAS is the retest site that must{.red} be used.

7B.3 Radar Testing

<section id="7c.1-overview">
<h1><a class="header-anchor" href="#7c.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7C.1 Overview</h1>
<section class="reference"></section>
<section id="7c.1.1">
<h3><a class="header-anchor" href="#7c.1.1">7C.1.1</a></h3>
<section class="reference">
<p>The Recruitment Team (Recruiters) have two main responsibilities, these are to manage new entrants during the recruitment process to join IFATC and secondly, to administer all theory and practical tests, with the final say on the result of the test (i.e. pass/fail).</p>
</section>
</section>
<section id="7c.1.2">
<h3><a class="header-anchor" href="#7c.1.2">7C.1.2</a></h3>
<section class="reference">
<p>Recruiters are selected by the IFATC Manager based on a number of criteria, including, but not limited to:</p>
<ul>
<li>
<p>ATC theoretical knowledge &amp; practical application</p>
</li>
<li>
<p>time zone availability</p>
</li>
<li>
<p>standing within IFATC</p>
</li>
<li>
<p>and/or contributions to the IFATC team as a whole</p>
</li>
</ul>
</section>
</section>
<section id="7c.1.3">
<h3><a class="header-anchor" href="#7c.1.3">7C.1.3</a></h3>
<section class="reference">
<p>The following table outlines the minimum notice period that <strong class="red">must</strong> be given to a Candidate/Controller before their Initial or Radar Practical Test (including the test location):</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Type</th>
<th>Minimum Notice Period</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Test Type">Initial</td>
<td data-label="Minimum Notice Period">No minimum</td>
</tr>
<tr>
<td data-label="Test Type">Radar</td>
<td data-label="Minimum Notice Period">24 hours*</td>
</tr>
</tbody>
</table>
<p>*The notice period may be reduced if the Recruiter and Candidate/Controller find a mutually acceptable time.</p>
</section>
</section>
<section id="7c.1.4">
<h3><a class="header-anchor" href="#7c.1.4">7C.1.4</a></h3>
<section class="reference">
<p>When new Recruiters are selected, they will be added to the following channels within Discord:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#recruiters</td>
<td data-label="Purpose">Main channel for coordination purposes within the Recruitment Team.</td>
</tr>
<tr>
<td data-label="Channel">#testers</td>
<td data-label="Purpose">Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers <strong class="red">must not</strong> &quot;react&quot; to the request if all available slots are already filled.</td>
</tr>
<tr>
<td data-label="Channel">#testers[1-3]</td>
<td data-label="Purpose">All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
<tr>
<td data-label="Channel">#trainers</td>
<td data-label="Purpose">Main channel for coordination purposes within the Training Team.</td>
</tr>
<tr>
<td data-label="Channel">#trainer-trainee[1-3]</td>
<td data-label="Purpose">Voice Channels specifically available for coordination between the Trainer and Trainee <strong>ONLY</strong> <em>(for further guidance see <a href="/guide/atc-manual/7a.-trainers/7a.1-overview#7a.1.8" class="documentation-content-link">7A.1.8</a> below)</em>.</td>
</tr>
<tr>
<td data-label="Channel">#training-time</td>
<td data-label="Purpose">Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in.</td>
</tr>
<tr>
<td data-label="Channel">#training-time[1-3]</td>
<td data-label="Purpose">All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel <strong class="red">must</strong> be used at any one time).</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


7C.1 Overview
7C.1.1
The Recruitment Team (Recruiters) have two main responsibilities, these are to manage new entrants during the recruitment process to join IFATC and secondly, to administer all theory and practical tests, with the final say on the result of the test (i.e. pass/fail).
7C.1.2
Recruiters are selected by the IFATC Manager based on a number of criteria, including, but not limited to:
ATC theoretical knowledge & practical application
time zone availability
standing within IFATC
and/or contributions to the IFATC team as a whole
7C.1.3
The following table outlines the minimum notice period that must{.red} be given to a Candidate/Controller before their Initial or Radar Practical Test (including the test location):
| Test Type | Minimum Notice Period |
| --------- | --------------------- |
| Initial   | No minimum            |
| Radar     | 24 hours*             |
*The notice period may be reduced if the Recruiter and Candidate/Controller find a mutually acceptable time.
7C.1.4
When new Recruiters are selected, they will be added to the following channels within Discord:
| Channel               | Purpose                                                      |
| --------------------- | ------------------------------------------------------------ |
| #recruiters           | Main channel for coordination purposes within the Recruitment Team. |
| #testers              | Recruiters will post in this channel when they require pilots to join in for a Practical Test (Initial or Radar), including which testers channel the session will take place in. Testers must not{.red} "react" to the request if all available slots are already filled. |
| #testers[1-3]         | All test session coordination to take place in the designated channel as directed by the Recruiter (no more than one test per channel must{.red} be used at any one time). |
| #trainers             | Main channel for coordination purposes within the Training Team. |
| #trainer-trainee1-3] | Voice Channels specifically available for coordination between the Trainer and Trainee ONLY (for further guidance see [7A.1.8 below). |
| #training-time        | Trainers will post in this channel when they require pilots to join in for training sessions, including which training-time channel the session will take place in. |
| #training-time[1-3]   | All training session coordination to take place in the designated channel as directed by the Trainer (no more than one training session per channel must{.red} be used at any one time). |

7C.1 Overview

<section id="7c.2-recruitment-process-(initial)">
<h1><a class="header-anchor" href="#7c.2-recruitment-process-(initial)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7C.2 Recruitment Process (Initial)</h1>
<section class="reference"></section>
<section id="7c.2.1">
<h3><a class="header-anchor" href="#7c.2.1">7C.2.1</a></h3>
<section class="reference">
<p>The summary below outlines the complete recruitment process for a Candidate (Recruit):</p>
<dl>
<dt>Step 1</dt>
<dd>Provided that the Recruit has been verified by a Moderator (&quot;Moderator Verified&quot; box ticked), accept the Recruit <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.1" class="documentation-content-link">7C.4.1</a> below)</em></dd>
<dt>Step 2</dt>
<dd>Once accepted, complete the Profile Verification to ensure that the Recruit meets the minimum requirements (see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.2" class="documentation-content-link">7C.2.2</a> and <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.4" class="documentation-content-link">7C.4.4</a> below)</dd>
<dt>Step 3</dt>
<dd>Assign The Initial Theory Test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.5" class="documentation-content-link">7C.4.5</a> below)</em></dd>
<dt>Step 4</dt>
<dd>The result of The Initial Theory Test will determine the next steps to be taken <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.3" class="documentation-content-link">7C.2.3</a> below)</em>. If the Recruit passes they can move onto The Initial Practical Test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.6" class="documentation-content-link">7C.4.6</a> below)</em></dd>
<dt>Step 5</dt>
<dd>The result of The Initial Practical Test will determine the next steps to be taken <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.4" class="documentation-content-link">7C.2.4</a> below)</em>. If the Recruit passes they can be added to IFATC <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.7" class="documentation-content-link">7C.4.7</a> below)</em></dd>
</dl>
</section>
</section>
<section id="7c.2.2">
<h3><a class="header-anchor" href="#7c.2.2">7C.2.2</a></h3>
<section class="reference">
<p>Once a Candidate has applied and a Moderator Check of their IFC profile has been completed, they will be approved for recruitment. It is then the responsibility of the Recruiter to verify that the Candidate meets the following requirements:</p>
<ul>
<li><strong>Trust Level 1</strong> on the IFC Forum in good standing</li>
<li>At least 14 years of age or as specified by Discord <a href="https://support.discord.com/hc/en-us/articles/360040724612-Why-is-Discord-asking-for-my-birthday-" class="documentation-content-link">here</a> for your country</li>
<li>Minimum stats to enter Expert Server (Grade 3)</li>
<li>Infinite Flight Account <strong class="red">must</strong> be linked to IFC account in-app</li>
<li><strong>All-time</strong> stats do not exceed 50% Level 1 Violation to landings ratio</li>
<li>Minimum of 500 ATC operations</li>
<li>At least 60 days since last Level 2 and/or 3 Violation</li>
<li>Valid email address (for Discord addition purposes)</li>
</ul>
<p>Verification of the above requirements can be assisted using the ATC Dashboard (a link is available within the <em>#recruiter</em> channel and login credentials are provided on joining the Recruitment Team). If a Candidate fails to meet the requirements outlined above, the application <strong class="red">must</strong> be denied. If the Candidate is successful, then the Recruit can move to the next stage.</p>
</section>
</section>
<section id="7c.2.3">
<h3><a class="header-anchor" href="#7c.2.3">7C.2.3</a></h3>
<section class="reference">
<p>After Candidates have been verified (Moderator and Profile), they are then granted clearance to take The Initial Theory Test. Recruiters <strong class="red">must</strong> ensure that the <a href="https://www.classmarker.com/online-test/start/?quiz=x9v565cbee44cdad" class="documentation-content-link">Classmarker Link</a> to the Initial Theory Test <strong>AND</strong> a valid test code (a number of which is provided by the IFATC Manager upon request) is included in the initial message. Additional relevant information and/or commentary may be provided at the Recruiter's discretion <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.5" class="documentation-content-link">7C.4.5</a> below)</em>.</p>
<p>Once a Candidate has taken The Initial Theory Test, the final score will determine whether or not the process can continue. A <strong class="red">pass mark of 80% or more must</strong> be achieved to move onto The Initial Practical Test. The following wait periods are required if a Candidate does not pass:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Score</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Score">00 - 49%</td>
<td data-label="Wait Period before Retake">30 days</td>
</tr>
<tr>
<td data-label="Score">50 - 79%</td>
<td data-label="Wait Period before Retake">14 days</td>
</tr>
</tbody>
</table>
<p>Three failed attempts at The Initial Theory Test results in a 90 day wait period to restart the process. This may be modified at Recruiter and/or IFATC Manager discretion if necessary.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If a Candidate does not pass The Initial Theory Test on their first attempt, they will become eligible for training if they want it. Recruiters <strong class="red">must</strong> ensure that Candidates are aware of this <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.3-initial-theory-and-practical-tests#7.3.2" class="documentation-content-link">7.3.2</a> above)</em>. Trainers <strong class="red">should</strong> inform Recruiters if a Trainee's performance is of concern, and if this has resulted in termination of training. Recruiters will then have discretion as to whether this effects the Trainee's eligibility criteria <em>(see <a href="/guide/atc-manual/7a.-trainers/7a.2-training-structure#7a.2.6" class="documentation-content-link">7A.2.6</a> above)</em>.</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="7c.2.4">
<h3><a class="header-anchor" href="#7c.2.4">7C.2.4</a></h3>
<section class="reference">
<p>Once The Initial Theory Test has been successfully passed, the Candidate can move onto The Initial Practical Test <em>(see <a href="/guide/atc-manual/7b.-testers/7b.1-testing-process#7b.1-testing-process" class="documentation-content-link">7B.1</a> and <a href="/guide/atc-manual/7b.-testers/7b.2-initial-testing#7b.2-initial-testing" class="documentation-content-link">7B.2</a> above)</em>. Recruiters <strong class="red">must</strong> ensure that the Candidate is provided with adequate notice, including a time and location of the test once this has been agreed <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.6" class="documentation-content-link">7C.4.6</a> below)</em>.</p>
<p>Once The Initial Practical Test has been completed, the Recruiter <strong class="red">must</strong> inform the Candidate of the result. The following wait periods are required if a Candidate does not pass:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Performance</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Performance">Poor</td>
<td data-label="Wait Period before Retake">30 days</td>
</tr>
<tr>
<td data-label="Performance">Marginal</td>
<td data-label="Wait Period before Retake">14 days</td>
</tr>
<tr>
<td data-label="Performance">Undetermined</td>
<td data-label="Wait Period before Retake">Recruiter Discretion</td>
</tr>
</tbody>
</table>
<p>Three failed attempts at The Initial Practical Test results in a 90 day wait period to restart the process. A &quot;no show&quot; to a scheduled test does not constitute an attempt however will result in a 14 day wait period before retake unless a valid reason (as determined by the Recruiter) is given. A subsequent &quot;no show&quot; will result in termination of the recruitment process. Recruiters <strong class="red">must</strong> ensure that they document everything in the recruit's profile <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.6" class="documentation-content-link">7C.2.6</a> below)</em>.</p>
</section>
</section>
<section id="7c.2.5">
<h3><a class="header-anchor" href="#7c.2.5">7C.2.5</a></h3>
<section class="reference">
<p>Provided that both The Initial Theory and Practical Tests have been passed, the Candidate can be invited to join the IFATC Team <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.7" class="documentation-content-link">7C.4.7</a> below)</em>.</p>
</section>
</section>
<section id="7c.2.6">
<h3><a class="header-anchor" href="#7c.2.6">7C.2.6</a></h3>
<section class="reference">
<p>All Recruiters <strong class="red">should</strong> do a comprehensive review of their list of recruits at least once a month to check for activity. Contact attempts (and termination of their application if applicable) <strong class="red">must</strong> be documented in the &quot;notes&quot; section of the recruit's profile. This can be done via the <a href="https://if-atc.com" class="documentation-content-link">website</a> by following the steps below:</p>
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>The &quot;My Dashboard&quot; tab will automatically show and under &quot;My Recruits&quot; will be a list of current Recruit's that are assigned to you</dd>
<dt>Step 3</dt>
<dd>Select the name of the Recruit under &quot;IFC&quot; and their profile will open showing all information for that Recruit</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>Alternatively, you can select the &quot;Recruits&quot; tab from the navigation bar at the top of the screen and use the search function to find the Recruit</dd>
</dl>
<dl>
<dt>Step 4</dt>
<dd>Select their name from under IFC and then &quot;notes&quot; from the navigation bar on their profile</dd>
<dt>Step 5</dt>
<dd>Applicable notes can be added and then saved by clicking &quot;Add Note&quot;</dd>
</dl>
</section>
</section>


7C.2 Recruitment Process (Initial)
7C.2.1
The summary below outlines the complete recruitment process for a Candidate (Recruit):
Step 1
: Provided that the Recruit has been verified by a Moderator ("Moderator Verified" box ticked), accept the Recruit (see 7C.4.1 below)
Step 2
: Once accepted, complete the Profile Verification to ensure that the Recruit meets the minimum requirements (see 7C.2.2#7c.2.2) and 7C.4.4 below)
Step 3
: Assign The Initial Theory Test (see 7C.4.5 below)
Step 4
: The result of The Initial Theory Test will determine the next steps to be taken (see 7C.2.3#7c.2.3) below). If the Recruit passes they can move onto The Initial Practical Test (see 7C.4.6 below)
Step 5
: The result of The Initial Practical Test will determine the next steps to be taken (see 7C.2.4#7c.2.4) below). If the Recruit passes they can be added to IFATC (see 7C.4.7 below)
7C.2.2
Once a Candidate has applied and a Moderator Check of their IFC profile has been completed, they will be approved for recruitment. It is then the responsibility of the Recruiter to verify that the Candidate meets the following requirements:
Trust Level 1 on the IFC Forum in good standing
At least 14 years of age or as specified by Discord here for your country
Minimum stats to enter Expert Server (Grade 3)
Infinite Flight Account must{.red} be linked to IFC account in-app
All-time stats do not exceed 50% Level 1 Violation to landings ratio
Minimum of 500 ATC operations
At least 60 days since last Level 2 and/or 3 Violation
Valid email address (for Discord addition purposes)
Verification of the above requirements can be assisted using the ATC Dashboard (a link is available within the #recruiter channel and login credentials are provided on joining the Recruitment Team). If a Candidate fails to meet the requirements outlined above, the application must{.red} be denied. If the Candidate is successful, then the Recruit can move to the next stage.
7C.2.3
After Candidates have been verified (Moderator and Profile), they are then granted clearance to take The Initial Theory Test. Recruiters must{.red} ensure that the Classmarker Link to the Initial Theory Test AND a valid test code (a number of which is provided by the IFATC Manager upon request) is included in the initial message. Additional relevant information and/or commentary may be provided at the Recruiter's discretion (see 7C.4.5 below).
Once a Candidate has taken The Initial Theory Test, the final score will determine whether or not the process can continue. A pass mark of 80% or more must{.red} be achieved to move onto The Initial Practical Test. The following wait periods are required if a Candidate does not pass:
| Score    | Wait Period before Retake |
| -------- | ------------------------- |
| 00 - 49% | 30 days                   |
| 50 - 79% | 14 days                   |
Three failed attempts at The Initial Theory Test results in a 90 day wait period to restart the process. This may be modified at Recruiter and/or IFATC Manager discretion if necessary.
Tip
: If a Candidate does not pass The Initial Theory Test on their first attempt, they will become eligible for training if they want it. Recruiters must{.red} ensure that Candidates are aware of this (see 7.3.2 above). Trainers should{.red} inform Recruiters if a Trainee's performance is of concern, and if this has resulted in termination of training. Recruiters will then have discretion as to whether this effects the Trainee's eligibility criteria (see 7A.2.6 above).
7C.2.4
Once The Initial Theory Test has been successfully passed, the Candidate can move onto The Initial Practical Test (see 7B.1 and 7B.2 above). Recruiters must{.red} ensure that the Candidate is provided with adequate notice, including a time and location of the test once this has been agreed (see 7C.4.6 below).
Once The Initial Practical Test has been completed, the Recruiter must{.red} inform the Candidate of the result. The following wait periods are required if a Candidate does not pass:
| Performance  | Wait Period before Retake |
| ------------ | ------------------------- |
| Poor         | 30 days                   |
| Marginal     | 14 days                   |
| Undetermined | Recruiter Discretion      |
Three failed attempts at The Initial Practical Test results in a 90 day wait period to restart the process. A "no show" to a scheduled test does not constitute an attempt however will result in a 14 day wait period before retake unless a valid reason (as determined by the Recruiter) is given. A subsequent "no show" will result in termination of the recruitment process. Recruiters must{.red} ensure that they document everything in the recruit's profile (see 7C.2.6#7c.2.6) below).
7C.2.5
Provided that both The Initial Theory and Practical Tests have been passed, the Candidate can be invited to join the IFATC Team (see 7C.4.7 below).
7C.2.6
All Recruiters should{.red} do a comprehensive review of their list of recruits at least once a month to check for activity. Contact attempts (and termination of their application if applicable) must{.red} be documented in the "notes" section of the recruit's profile. This can be done via the website by following the steps below:
Step 1
: Go to website and login via the "Dashboard"
Step 2
: The "My Dashboard" tab will automatically show and under "My Recruits" will be a list of current Recruit's that are assigned to you
Step 3
:  Select the name of the Recruit under "IFC" and their profile will open showing all information for that Recruit
Tip
: Alternatively, you can select the "Recruits" tab from the navigation bar at the top of the screen and use the search function to find the Recruit
Step 4
: Select their name from under IFC and then "notes" from the navigation bar on their profile
Step 5
: Applicable notes can be added and then saved by clicking "Add Note"

7C.2 Recruitment Process (Initial)

<section id="7c.3-recruitment-process-(radar)">
<h1><a class="header-anchor" href="#7c.3-recruitment-process-(radar)"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7C.3 Recruitment Process (Radar)</h1>
<section class="reference"></section>
<section id="7c.3.1">
<h3><a class="header-anchor" href="#7c.3.1">7C.3.1</a></h3>
<section class="reference">
<p>For Controllers to enter the Radar certification process, all instructions in this manual <strong class="red">must</strong> be followed <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.5-radar-theory-and-practical-tests#7.5-radar-theory-and-practical-tests" class="documentation-content-link">7.5</a> above)</em>. Following a successful review, the Recruiter <strong class="red">must</strong> instruct the Controller to submit an application.</p>
<p>The radar certification process is relatively straightforward as a Recruiter - they are only to provide and coordinate The Radar Theory and Practical Tests whenever a Trainer clears a Controller to take either. Recruiters need not concern themselves with any particulars outside of those two functions, though they reserve the right to terminate the radar process of a Controller if necessary.</p>
</section>
</section>
<section id="7c.3.2">
<h3><a class="header-anchor" href="#7c.3.2">7C.3.2</a></h3>
<section class="reference">
<p>When a Controller is ready to take The Radar Theory Test, the Recruiter must provide them with the <a href="https://www.classmarker.com/online-test/start/?quiz=q4h5a75fac936d32" class="documentation-content-link">Classmarker Link</a> and the password <strong>terrainpullup</strong>. To keep the Controller's record on the website current, the same process as used for Candidates <strong class="red">must</strong> be followed <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.5" class="documentation-content-link">7C.4.5</a> below)</em>.</p>
<p>Once a Controller has taken The Radar Theory Test, the final score will determine whether or not the process can continue. A <strong class="red">pass mark of 70% or more must</strong> be achieved to move onto The Radar Practical Test (provided the Trainer has endorsed* this). The following wait periods are required if a Controller does not pass:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Score</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Score">00 - 40%</td>
<td data-label="Wait Period before Retake">30 days</td>
</tr>
<tr>
<td data-label="Score">41 - 69%</td>
<td data-label="Wait Period before Retake">14 days</td>
</tr>
</tbody>
</table>
<p>Three failed attempts at the Radar Theory Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires).</p>
<p>*<em>Once the Radar Theory Test has been passed, the Controller must have the permission of the Trainer to move onto The Radar Practical Test, further training may be required before the Controller can progress</em></p>
</section>
</section>
<section id="7c.3.3">
<h3><a class="header-anchor" href="#7c.3.3">7C.3.3</a></h3>
<section class="reference">
<p>Once The Radar Theory Test has been successfully passed, the Controller can move onto The Radar Practical Test following permission from their Trainer <em>(see <a href="/guide/atc-manual/7b.-testers/7b.1-testing-process#7b.1-testing-process" class="documentation-content-link">7B.1</a> and <a href="/guide/atc-manual/7b.-testers/7b.3-radar-testing#7b.3-radar-testing" class="documentation-content-link">7B.3</a> above)</em>. Recruiters <strong class="red">must</strong> ensure that the Controller is provided with adequate notice, including a time and location of the test once this has been agreed <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.3" class="documentation-content-link">7C.1.3</a> above)</em>. To keep the Controller's record on the website current, the same process as used for Candidates <strong class="red">must</strong> be followed <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.6" class="documentation-content-link">7C.4.6</a> below)</em>.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If the Controller is part of the <em>#testers</em> group, they <strong class="red">must</strong> be removed <strong class="red">BEFORE</strong> commencement of the test. Recruiters <strong class="red">must</strong> post in <em>#recruiters</em> with adequate notice to allow a Moderator the time to remove the individual - once the test is completed, they can be re-added in the same way</p>
</dd>
</dl>
</dl>
<p>Once the Radar Practical test has been completed, the Recruiter <strong class="red">must</strong> inform the Controller of the result. The following wait periods are required if a Controller does not pass:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Performance</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Performance">Poor</td>
<td data-label="Wait Period before Retake">30 days</td>
</tr>
<tr>
<td data-label="Performance">Marginal</td>
<td data-label="Wait Period before Retake">14 days</td>
</tr>
<tr>
<td data-label="Performance">Undetermined</td>
<td data-label="Wait Period before Retake">Recruiter Discretion</td>
</tr>
</tbody>
</table>
<p>Three failed attempts at the Radar Theory Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires).</p>
</section>
</section>
</section>
<section id="7c.3.4">
<h3><a class="header-anchor" href="#7c.3.4">7C.3.4</a></h3>
<section class="reference">
<p>Provided that both The Radar Theory and Practical Tests have been passed, the Controller can be promoted to the rank of Officer using the same process as Candidates <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.7" class="documentation-content-link">7C.4.7</a> below)</em>.</p>
</section>
</section>


7C.3 Recruitment Process (Radar)

7C.3.1

For Controllers to enter the Radar certification process, all instructions in this manual must{.red} be followed (see 7.5 above). Following a successful review, the Recruiter must{.red} instruct the Controller to submit an application.

The radar certification process is relatively straightforward as a Recruiter - they are only to provide and coordinate The Radar Theory and Practical Tests whenever a Trainer clears a Controller to take either. Recruiters need not concern themselves with any particulars outside of those two functions, though they reserve the right to terminate the radar process of a Controller if necessary.
7C.3.2

When a Controller is ready to take The Radar Theory Test, the Recruiter must provide them with the Classmarker Link and the password terrainpullup. To keep the Controller's record on the website current, the same process as used for Candidates must{.red} be followed (see 7C.4.5 below).

Once a Controller has taken The Radar Theory Test, the final score will determine whether or not the process can continue. A pass mark of 70% or more must{.red} be achieved to move onto The Radar Practical Test (provided the Trainer has endorsed* this). The following wait periods are required if a Controller does not pass:

| Score    | Wait Period before Retake |
| -------- | ------------------------- |
| 00 - 40% | 30 days                   |
| 41 - 69% | 14 days                   |

Three failed attempts at the Radar Theory Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires).

*Once the Radar Theory Test has been passed, the Controller must have the permission of the Trainer to move onto The Radar Practical Test, further training may be required before the Controller can progress

7C.3.3

Once The Radar Theory Test has been successfully passed, the Controller can move onto The Radar Practical Test following permission from their Trainer (see 7B.1 and 7B.3 above). Recruiters must{.red} ensure that the Controller is provided with adequate notice, including a time and location of the test once this has been agreed (see 7C.1.3 above). To keep the Controller's record on the website current, the same process as used for Candidates must{.red} be followed (see 7C.4.6 below).

Tip

: If the Controller is part of the #testers group, they must{.red} be removed BEFORE{.red} commencement of the test. Recruiters must{.red} post in #recruiters with adequate notice to allow a Moderator the time to remove the individual - once the test is completed, they can be re-added in the same way

Once the Radar Practical test has been completed, the Recruiter must{.red} inform the Controller of the result. The following wait periods are required if a Controller does not pass:

| Performance  | Wait Period before Retake |
| ------------ | ------------------------- |
| Poor         | 30 days                   |
| Marginal     | 14 days                   |
| Undetermined | Recruiter Discretion      |

Three failed attempts at the Radar Theory Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires).

7C.3.4

Provided that both The Radar Theory and Practical Tests have been passed, the Controller can be promoted to the rank of Officer using the same process as Candidates (see 7C.4.7 below).

7C.3 Recruitment Process (Radar)

<section id="7c.4-recruiter-admin">
<h1><a class="header-anchor" href="#7c.4-recruiter-admin"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7C.4 Recruiter Admin</h1>
<section class="reference"></section>
<section id="how-to-accept-a-recruit">
<h2><a class="header-anchor" href="#how-to-accept-a-recruit"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Accept a Recruit</h2>
<section class="reference"></section>
<section id="7c.4.1">
<h3><a class="header-anchor" href="#7c.4.1">7C.4.1</a></h3>
<section class="reference">
<p>The following procedure outlines how to accept a new Candidate/Controller as a Recruit:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>A notification in the <em>#recruiters</em> Discord channel will inform all Recruiters that there is a new recruit awaiting assignment</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Select &quot;Waitlist&quot; from the navigation bar at the top of the screen</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Select &quot;Recruits&quot; from the tab (if it is not already displayed)</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>Select the &quot;IF Name&quot; of the Recruit that you wish to take on</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Before a Recruit is accepted, they <strong class="red">must</strong> be verified by a Moderator. Ensure that this box is ticked before accepting the assignment</p>
</dd>
</dl>
<dl>
<dt>Step 6</dt>
<dd>
<p>To accept, tap &quot;Accept Assignment (No PM)&quot; or Accept Assignment &amp; PM&quot;. The latter will automatically open the IFC Forum in a new window, allowing a PM to be sent to the Recruit to begin the process</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If you are using iOS, make sure to allow pop ups! Without this, the &quot;Accept Assignment &amp; PM&quot; button may not work</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="how-to-view-the-recruits-profile">
<h2><a class="header-anchor" href="#how-to-view-the-recruits-profile"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to View the Recruits Profile</h2>
<section class="reference"></section>
<section id="7c.4.2">
<h3><a class="header-anchor" href="#7c.4.2">7C.4.2</a></h3>
<section class="reference">
<p>The following procedure outlines how to view a Recruit's profile:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>The &quot;My Dashboard&quot; tab will automatically show and under &quot;My Recruits&quot; will be a list of current Recruit's that are assigned to you</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Select the name of the Recruit under &quot;IFC&quot; and their profile will open showing all information for that Recruit</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Alternatively, you can select the &quot;Recruits&quot; tab from the navigation bar at the top of the screen and use the search function to find the Recruit</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="how-to-update-the-recruit-progress">
<h2><a class="header-anchor" href="#how-to-update-the-recruit-progress"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Update the Recruit Progress</h2>
<section class="reference"></section>
<section id="7c.4.3">
<h3><a class="header-anchor" href="#7c.4.3">7C.4.3</a></h3>
<section class="reference">
<p>The following procedure outlines how to update a recruits progress:</p>
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Recruit's Profile <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.2" class="documentation-content-link">7C.4.2</a> above)</em> and select the &quot;Summary&quot; tab (if it has not appeared automatically)</dd>
<dt>Step 3</dt>
<dd>Under &quot;Recruit Progress&quot;, tick the box as applicable (make sure that you have sent the corresponding PM, if applicable, using the &quot;PM Templates&quot; beneath this)</dd>
<dt>Step 4</dt>
<dd>Scroll to the bottom and tap &quot;Save&quot;</dd>
</dl>
</section>
</section>
</section>
<section id="how-to-complete-the-profile-verification-of-a-recruit">
<h2><a class="header-anchor" href="#how-to-complete-the-profile-verification-of-a-recruit"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Complete the Profile Verification of a Recruit</h2>
<section class="reference"></section>
<section id="7c.4.4">
<h3><a class="header-anchor" href="#7c.4.4">7C.4.4</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Recruits Profile using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.2" class="documentation-content-link">7C.4.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Use the ATC Dashboard (a link is available within the <em>#recruiter</em> channel and login credentials are provided on joining the Recruitment Team) to check the profile of the Recruit, they must meet the minimum requirements to continue <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.2" class="documentation-content-link">7C.2.2</a> above)</em></dd>
<dt>Step 4</dt>
<dd>Provided the requirements are met, tick the &quot;Profile Verified&quot; box under &quot;Recruit Progress&quot; using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.3" class="documentation-content-link">7C.4.3</a> above)</em></dd>
</dl>
</section>
</section>
</section>
<section id="how-to-assign-the-initial-theory-test-to-a-recruit">
<h2><a class="header-anchor" href="#how-to-assign-the-initial-theory-test-to-a-recruit"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Assign The Initial Theory Test to a Recruit</h2>
<section class="reference"></section>
<section id="7c.4.5">
<h3><a class="header-anchor" href="#7c.4.5">7C.4.5</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Recruits Profile using the steps outlined above <em>(see <a href="//guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.2" class="documentation-content-link">7C.4.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Provided the requirements are met <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.3" class="documentation-content-link">7C.2.3</a> above)</em>, tick the &quot;Written Phase&quot; box under &quot;Recruit Progress&quot; using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.3" class="documentation-content-link">7C.4.3</a> above)</em></dd>
<dt>Step 4</dt>
<dd>Scroll to the bottom and tap &quot;Save&quot;</dd>
<dt>Step 5</dt>
<dd>Send the corresponding PM using the &quot;PM Templates&quot; - Recruiters <strong class="red">must</strong> ensure that the <a href="https://www.classmarker.com/online-test/start/?quiz=x9v565cbee44cdad" class="documentation-content-link">Classmarker Link</a> to the Initial Theory Test <strong>AND</strong> a valid test code are included <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.3" class="documentation-content-link">7C.2.3</a> above)</em></dd>
<dt>Step 6</dt>
<dd>If the Recruit passes then they can move onto the next stage <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.4" class="documentation-content-link">7C.2.4</a> above)</em>. If they fail, they will need to have the test re-scheduled (unless it was their third attempt, in which case the recruitment process is terminated) - in all cases, their profile <strong class="red">must</strong> be updated to reflect this <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.7" class="documentation-content-link">7C.4.7</a> below)</em></dd>
</dl>
</section>
</section>
</section>
<section id="how-to-assign-the-initial-practical-test-to-a-recruit">
<h2><a class="header-anchor" href="#how-to-assign-the-initial-practical-test-to-a-recruit"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Assign The Initial Practical Test to a Recruit</h2>
<section class="reference"></section>
<section id="7c.4.6">
<h3><a class="header-anchor" href="#7c.4.6">7C.4.6</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Recruits Profile using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.2" class="documentation-content-link">7C.4.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Provided the requirements are met <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.4" class="documentation-content-link">7C.2.4</a> above)</em>, tick the &quot;Practical Phase&quot; box under &quot;Recruit Progress&quot; using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.3" class="documentation-content-link">7C.4.3</a> above)</em></dd>
<dt>Step 4</dt>
<dd>Scroll to the bottom and tap &quot;Save&quot;</dd>
<dt>Step 5</dt>
<dd>Send the corresponding PM using the &quot;PM Templates&quot; <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.4" class="documentation-content-link">7C.2.4</a> above)</em></dd>
<dt>Step 6</dt>
<dd>If the Recruit passes then they can be accepted into IFATC. If they fail, they will need to have the test re-scheduled (unless it was their third attempt, in which case the recruitment process is terminated) - in all cases, their profile <strong class="red">must</strong> be updated to reflect this <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.7" class="documentation-content-link">7C.4.7</a> below)</em></dd>
</dl>
</section>
</section>
</section>
<section id="how-to-pass%2Fterminate-a-recruit">
<h2><a class="header-anchor" href="#how-to-pass%2Fterminate-a-recruit"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> How to Pass/Terminate a Recruit</h2>
<section class="reference"></section>
<section id="7c.4.7">
<h3><a class="header-anchor" href="#7c.4.7">7C.4.7</a></h3>
<section class="reference">
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Access the Recruits Profile using the steps outlined above <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.4-recruiter-admin#7c.4.2" class="documentation-content-link">7C.4.2</a> above)</em></dd>
<dt>Step 3</dt>
<dd>Once the Recruit has completed The Initial Theory Test, their profile will automatically be updated under the &quot;Test Scores&quot; tab (Recruiters will receive notification of this in the <em>#recruiters</em> channel - if the test score did not update, a test ID can be copied and pasted in the &quot;Test Scores&quot; tab, Recruiters can then tap the &quot;Link Online Test&quot; to save it). If the Recruit has passed, they can move onto The Initial Practical Test; if they have failed, they will need to wait to re-take the test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.2-recruitment-process-(initial)#7c.2.3" class="documentation-content-link">7C.2.3</a> above)</em>.</dd>
<dt>Step 4</dt>
<dd>If the Recruit has just completed their Initial Practical Test; then provided they have passed, the &quot;End Process - Passed - IFATC!&quot; box <strong class="red">must</strong> be ticked. If they have failed, they will need to wait to re-take the test (unless it was their third attempt, in which case the recruitment process is terminated by ticking the &quot;End Process - Failed Out&quot; box). After ticking the respective box, make sure to scroll to the bottom and tap &quot;Save&quot;</dd>
<dt>Step 5</dt>
<dd>Send the corresponding PM using the &quot;PM Templates&quot;</dd>
</dl>
</section>
</section>
</section>


7C.4 Recruiter Admin
How to Accept a Recruit
7C.4.1
The following procedure outlines how to accept a new Candidate/Controller as a Recruit:
Step 1
: A notification in the #recruiters Discord channel will inform all Recruiters that there is a new recruit awaiting assignment
Step 2
: Go to website and login via the "Dashboard"
Step 3
: Select "Waitlist" from the navigation bar at the top of the screen
Step 4
: Select "Recruits" from the tab (if it is not already displayed)
Step 5
: Select the "IF Name" of the Recruit that you wish to take on
Tip
: Before a Recruit is accepted, they must{.red} be verified by a Moderator. Ensure that this box is ticked before accepting the assignment
Step 6
: To accept, tap "Accept Assignment (No PM)" or Accept Assignment & PM". The latter will automatically open the IFC Forum in a new window, allowing a PM to be sent to the Recruit to begin the process
Tip
: If you are using iOS, make sure to allow pop ups! Without this, the "Accept Assignment & PM" button may not work
How to View the Recruits Profile
7C.4.2
The following procedure outlines how to view a Recruit's profile:
Step 1
: Go to website and login via the "Dashboard"
Step 2
: The "My Dashboard" tab will automatically show and under "My Recruits" will be a list of current Recruit's that are assigned to you
Step 3
:  Select the name of the Recruit under "IFC" and their profile will open showing all information for that Recruit
Tip
: Alternatively, you can select the "Recruits" tab from the navigation bar at the top of the screen and use the search function to find the Recruit
How to Update the Recruit Progress
7C.4.3
The following procedure outlines how to update a recruits progress:
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Recruit's Profile (see 7C.4.2 above) and select the "Summary" tab (if it has not appeared automatically)
Step 3
: Under "Recruit Progress", tick the box as applicable (make sure that you have sent the corresponding PM, if applicable, using the "PM Templates" beneath this)
Step 4
: Scroll to the bottom and tap "Save"
How to Complete the Profile Verification of a Recruit
7C.4.4
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Recruits Profile using the steps outlined above (see 7C.4.2 above)
Step 3
: Use the ATC Dashboard (a link is available within the #recruiter channel and login credentials are provided on joining the Recruitment Team) to check the profile of the Recruit, they must meet the minimum requirements to continue (see 7C.2.2#7c.2.2) above)
Step 4
: Provided the requirements are met, tick the "Profile Verified" box under "Recruit Progress" using the steps outlined above (see 7C.4.3 above)
How to Assign The Initial Theory Test to a Recruit
7C.4.5
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Recruits Profile using the steps outlined above (see 7C.4.2 above)
Step 3
: Provided the requirements are met (see 7C.2.3#7c.2.3) above), tick the "Written Phase" box under "Recruit Progress" using the steps outlined above (see 7C.4.3 above)
Step 4
: Scroll to the bottom and tap "Save"
Step 5
: Send the corresponding PM using the "PM Templates" - Recruiters must{.red} ensure that the Classmarker Link to the Initial Theory Test AND a valid test code are included (see 7C.2.3#7c.2.3) above)
Step 6
: If the Recruit passes then they can move onto the next stage (see 7C.2.4#7c.2.4) above). If they fail, they will need to have the test re-scheduled (unless it was their third attempt, in which case the recruitment process is terminated) - in all cases, their profile must{.red} be updated to reflect this (see 7C.4.7 below)
How to Assign The Initial Practical Test to a Recruit
7C.4.6
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Recruits Profile using the steps outlined above (see 7C.4.2 above)
Step 3
: Provided the requirements are met (see 7C.2.4#7c.2.4) above), tick the "Practical Phase" box under "Recruit Progress" using the steps outlined above (see 7C.4.3 above)
Step 4
: Scroll to the bottom and tap "Save"
Step 5
: Send the corresponding PM using the "PM Templates" (see 7C.2.4#7c.2.4) above)
Step 6
: If the Recruit passes then they can be accepted into IFATC. If they fail, they will need to have the test re-scheduled (unless it was their third attempt, in which case the recruitment process is terminated) - in all cases, their profile must{.red} be updated to reflect this (see 7C.4.7 below)
How to Pass/Terminate a Recruit
7C.4.7
Step 1
: Go to website and login via the "Dashboard"
Step 2
: Access the Recruits Profile using the steps outlined above (see 7C.4.2 above)
Step 3
: Once the Recruit has completed The Initial Theory Test, their profile will automatically be updated under the "Test Scores" tab (Recruiters will receive notification of this in the #recruiters channel - if the test score did not update, a test ID can be copied and pasted in the "Test Scores" tab, Recruiters can then tap the "Link Online Test" to save it). If the Recruit has passed, they can move onto The Initial Practical Test; if they have failed, they will need to wait to re-take the test (see 7C.2.3#7c.2.3) above).
Step 4
: If the Recruit has just completed their Initial Practical Test; then provided they have passed, the "End Process - Passed - IFATC!" box must{.red} be ticked. If they have failed, they will need to wait to re-take the test (unless it was their third attempt, in which case the recruitment process is terminated by ticking the "End Process - Failed Out" box). After ticking the respective box, make sure to scroll to the bottom and tap "Save"
Step 5
: Send the corresponding PM using the "PM Templates"

7C.4 Recruiter Admin

<section id="7d.1-overview">
<h1><a class="header-anchor" href="#7d.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7D.1 Overview</h1>
<section class="reference"></section>
<section id="7d.1.1">
<h3><a class="header-anchor" href="#7d.1.1">7D.1.1</a></h3>
<section class="reference">
<p>The purpose of the Supervisor Team is to assist in the day-to-day operations of IFATC, provide leadership and/or mentoring of individual controllers, monitor controlling quality via the &quot;Check Ride&quot; process, and to moderate the Infinite Flight Expert Server.</p>
<p>To carry this out, Supervisors will be added to the following channel within Discord:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#supervisors</td>
<td data-label="Purpose">This channel is used to facilitate communications between all Supervisors for any purpose deemed necessary.</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7d.1.2">
<h3><a class="header-anchor" href="#7d.1.2">7D.1.2</a></h3>
<section class="reference">
<p>Supervisors are selected by the IFATC Manager based on a number of criteria, including, but not limited to:</p>
<ul>
<li>current standing within IFATC</li>
<li>contributions to IFATC</li>
<li>operational necessity</li>
<li>and/or the ability to assist in internal team affairs within a professional context</li>
</ul>
<p>Supervisors may be demoted or removed from the Supervisor Team for any reason as deemed by the IFATC Manager (e.g. breach of trust, abuse of power, lack of commitment etc.).</p>
</section>
</section>
<section id="7d.1.3">
<h3><a class="header-anchor" href="#7d.1.3">7D.1.3</a></h3>
<section class="reference">
<p>Supervisors <strong class="red">must</strong> maintain proficiency by meeting the minimum activity requirements <em>(see <a href="/guide/atc-manual/1a.-new-entrants/1a.5-activity-requirements#1a.5.1" class="documentation-content-link">1A.5.1</a> above)</em>. Removal from IFATC due to inactivity, will also result in removal of the Supervisor role.</p>
</section>
</section>
</section>


7D.1 Overview
7D.1.1
The purpose of the Supervisor Team is to assist in the day-to-day operations of IFATC, provide leadership and/or mentoring of individual controllers, monitor controlling quality via the "Check Ride" process, and to moderate the Infinite Flight Expert Server.
To carry this out, Supervisors will be added to the following channel within Discord:
| Channel      | Purpose                                                      |
| ------------ | ------------------------------------------------------------ |
| #supervisors | This channel is used to facilitate communications between all Supervisors for any purpose deemed necessary. |
7D.1.2
Supervisors are selected by the IFATC Manager based on a number of criteria, including, but not limited to:
current standing within IFATC
contributions to IFATC
operational necessity
and/or the ability to assist in internal team affairs within a professional context
Supervisors may be demoted or removed from the Supervisor Team for any reason as deemed by the IFATC Manager (e.g. breach of trust, abuse of power, lack of commitment etc.).
7D.1.3
Supervisors must{.red} maintain proficiency by meeting the minimum activity requirements (see 1A.5.1 above). Removal from IFATC due to inactivity, will also result in removal of the Supervisor role.

7D.1 Overview

<section id="7d.2-violations">
<h1><a class="header-anchor" href="#7d.2-violations"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7D.2 Violations</h1>
<section class="reference"></section>
<section id="7d.2.1">
<h3><a class="header-anchor" href="#7d.2.1">7D.2.1</a></h3>
<section class="reference">
<p>Supervisors are granted the ability to issue Violations as a pilot in order to fulfil their duty of moderating the Infinite Flight Expert Server. When these are issued, they <strong class="red">must</strong> be documented in the <em>#supervisors</em> Discord channel <em>(see <a href="/guide/atc-manual/7d.-supervisors/7d.2-violations#7d.2.4" class="documentation-content-link">7D.2.4</a> below)</em>.</p>
</section>
</section>
<section id="7d.2.2">
<h3><a class="header-anchor" href="#7d.2.2">7D.2.2</a></h3>
<section class="reference">
<p>The following are examples of situations where it may be considered appropriate to exercise this ability:</p>
<ul>
<li>unmanned airports with no order</li>
<li>clear violations of Expert Server rules</li>
<li>environments where IFATC controllers are not enforcing instructions</li>
</ul>
</section>
</section>
<section id="7d.2.3">
<h3><a class="header-anchor" href="#7d.2.3">7D.2.3</a></h3>
<section class="reference">
<p>Violations <strong class="red">must</strong> be issued for blatant offenses to the point where pilots on the Expert Server are being negatively affected by the actions of other pilots.</p>
<p>Taxiing through other aircraft, landing on top of aircraft/failure to go around, going too fast in a controlled environment, and/or other clearly distinguishable acts of interference are some of the most common reasons to issue a Violation in the absence of a Controller.</p>
</section>
</section>
<section id="7d.2.4">
<h3><a class="header-anchor" href="#7d.2.4">7D.2.4</a></h3>
<section class="reference">
<p>Violations can be issued by following the process below:</p>
<dl>
<dt>Step 1</dt>
<dd>Tap on the aircraft icon from your map/mini map</dd>
<dt>Step 2</dt>
<dd>The pilot callsign/display name will appear, tap this to open the information tab</dd>
<dt>Step 3</dt>
<dd>Tap the report button and select the reason most appropriate</dd>
<dt>Step 4</dt>
<dd>Post in the <em>#supervisors</em> Discord channel details of the Violation issued including Username, Callsign, Identifier, Location and Violation Reason</dd>
</dl>
</section>
</section>
<section id="7d.2.5">
<h3><a class="header-anchor" href="#7d.2.5">7D.2.5</a></h3>
<section class="reference">
<p>The pilot(s) have the ability to appeal their Violation via @appeals on the IFC within a 7 day span of time <em>(see <a href="/guide/atc-manual/1b.-violations/1b.2-incident-resolution-procedure#1b.2.1" class="documentation-content-link">1B.2.1</a> above)</em>. It is strongly recommended that Supervisors have replays of their sessions on hand for that duration in order to deal with inquiries should the need arise. Moderators and/or the IFATC Manager reserve the final say on the verdict of appeal(s).</p>
</section>
</section>
</section>


7D.2 Violations
7D.2.1
Supervisors are granted the ability to issue Violations as a pilot in order to fulfil their duty of moderating the Infinite Flight Expert Server. When these are issued, they must{.red} be documented in the #supervisors Discord channel (see 7D.2.4 below).
7D.2.2
The following are examples of situations where it may be considered appropriate to exercise this ability:
unmanned airports with no order
clear violations of Expert Server rules
environments where IFATC controllers are not enforcing instructions
7D.2.3
Violations must{.red} be issued for blatant offenses to the point where pilots on the Expert Server are being negatively affected by the actions of other pilots.
Taxiing through other aircraft, landing on top of aircraft/failure to go around, going too fast in a controlled environment, and/or other clearly distinguishable acts of interference are some of the most common reasons to issue a Violation in the absence of a Controller.
7D.2.4
Violations can be issued by following the process below:
Step 1
: Tap on the aircraft icon from your map/mini map
Step 2
: The pilot callsign/display name will appear, tap this to open the information tab
Step 3
: Tap the report button and select the reason most appropriate
Step 4
: Post in the #supervisors Discord channel details of the Violation issued including Username, Callsign, Identifier, Location and Violation Reason
7D.2.5
The pilot(s) have the ability to appeal their Violation via @appeals on the IFC within a 7 day span of time (see 1B.2.1 above). It is strongly recommended that Supervisors have replays of their sessions on hand for that duration in order to deal with inquiries should the need arise. Moderators and/or the IFATC Manager reserve the final say on the verdict of appeal(s).

7D.2 Violations

<section id="7d.3-check-ride-process">
<h1><a class="header-anchor" href="#7d.3-check-ride-process"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7D.3 Check Ride Process</h1>
<section class="reference"></section>
<section id="7d.3.1">
<h3><a class="header-anchor" href="#7d.3.1">7D.3.1</a></h3>
<section class="reference">
<p>When a Controller enters the &quot;Check Ride&quot; phase <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-promotion-to-specialist-(check-ride)#7.4-promotion-to-specialist-(check-ride)" class="documentation-content-link">7.4</a> above)</em>, an automatic message will be sent to the <em>#supervisors</em> Discord channel every time the Controller opens a frequency. As part of the &quot;Check Ride&quot; phase, Supervisors <strong class="red">should</strong> make attempts to observe and/or fly for Controllers under review, this is to ensure that a certain quality and level of suitable improvement exists.</p>
</section>
</section>
<section id="7d.3.2">
<h3><a class="header-anchor" href="#7d.3.2">7D.3.2</a></h3>
<section class="reference">
<p>Following attendance of a Controllers session the procedure below outlines how to submit feedback:</p>
<dl>
<dt>Step 1</dt>
<dd>Access the <em>#atcsupervisor</em> Discord channel and click the &quot;HERE&quot; link provided by the IFATC Website Bot for the Controller you wish to provide feedback for</dd>
<dt>Step 2</dt>
<dd>This will take you to the &quot;Sessions&quot; tab of the Controller who is currently undergoing their Check Ride</dd>
<dt>Step 3</dt>
<dd>Tap the green &quot;Sessions&quot; button which is located directly above &quot;Session Date / Feedback&quot;, this will open a new session feedback form where details can be provided</dd>
</dl>
</section>
</section>
<section id="7d.3.3">
<h3><a class="header-anchor" href="#7d.3.3">7D.3.3</a></h3>
<section class="reference">
<p>At the end of a Controller’s probationary period, the IFATC Manager will review the feedback conducted by Supervisors at &quot;Check Ride&quot; sessions <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-promotion-to-specialist-(check-ride)#7.4.5" class="documentation-content-link">7.4.5</a> above)</em>. A decision will be made and repeated if necessary.</p>
</section>
</section>
</section>


7D.3 Check Ride Process
7D.3.1
When a Controller enters the "Check Ride" phase (see 7.4#7.4-promotion-to-specialist-(check-ride)) above), an automatic message will be sent to the #supervisors Discord channel every time the Controller opens a frequency. As part of the "Check Ride" phase, Supervisors should{.red} make attempts to observe and/or fly for Controllers under review, this is to ensure that a certain quality and level of suitable improvement exists.
7D.3.2
Following attendance of a Controllers session the procedure below outlines how to submit feedback:
Step 1
: Access the #atcsupervisor Discord channel and click the "HERE" link provided by the IFATC Website Bot for the Controller you wish to provide feedback for
Step 2
: This will take you to the "Sessions" tab of the Controller who is currently undergoing their Check Ride
Step 3
: Tap the green "Sessions" button which is located directly above "Session Date / Feedback", this will open a new session feedback form where details can be provided
7D.3.3
At the end of a Controller’s probationary period, the IFATC Manager will review the feedback conducted by Supervisors at "Check Ride" sessions (see 7.4.5#7.4.5) above). A decision will be made and repeated if necessary.

7D.3 Check Ride Process

<section id="7d.4-leadership">
<h1><a class="header-anchor" href="#7d.4-leadership"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7D.4 Leadership</h1>
<section class="reference"></section>
<section id="7d.4.1">
<h3><a class="header-anchor" href="#7d.4.1">7D.4.1</a></h3>
<section class="reference">
<p>Accountability exists for everyone within the team, and therefore Controllers are expected to utilize any feedback given to improve. Supervisors <strong class="red">should</strong> make every effort to give both positive and negative feedback to Controllers (even if they are not in the Check Ride phase). When the opportunity exists and if deemed necessary <em>(see <a href="/guide/atc-manual/7d.-supervisors/7d.4-leadership#7d.4.4" class="documentation-content-link">7D.4.4</a> below)</em>, Supervisors can add a &quot;note&quot; to the Controller's record on the <a href="https://if-atc.com" class="documentation-content-link">website</a> by following the steps below:</p>
<dl>
<dt>Step 1</dt>
<dd>Go to <a href="https://if-atc.com" class="documentation-content-link">website</a> and login via the &quot;Dashboard&quot;</dd>
<dt>Step 2</dt>
<dd>Select &quot;Controllers&quot; from the navigation bar at the top of the screen</dd>
<dt>Step 3</dt>
<dd>Utilize the &quot;search&quot; function to find the Controller</dd>
<dt>Step 4</dt>
<dd>Select their name from under IFC and then &quot;notes&quot; from the navigation bar on their profile</dd>
<dt>Step 5</dt>
<dd>Applicable notes can be added and then saved by clicking &quot;Add Note&quot;</dd>
</dl>
</section>
</section>
<section id="7d.4.2">
<h3><a class="header-anchor" href="#7d.4.2">7D.4.2</a></h3>
<section class="reference">
<p>When offering guidance to team members, be sure to emphasize that Controllers never stop learning and that any setbacks and/or criticisms <strong class="red">should</strong> be taken in their stride.</p>
</section>
</section>
<section id="7d.4.3">
<h3><a class="header-anchor" href="#7d.4.3">7D.4.3</a></h3>
<section class="reference">
<p>Supervisors may assist in general matters within IFATC, but must leave other sensitive requests to the appropriate groups (i.e. violations to Moderators, recruiting questions to Recruiters and training to Trainers).</p>
</section>
</section>
<section id="7d.4.4">
<h3><a class="header-anchor" href="#7d.4.4">7D.4.4</a></h3>
<section class="reference">
<p>It is highly encouraged that Supervisors use the &quot;note&quot; function to record both positive and negative feedback for Controllers. This is always taken into consideration when Controllers are considered for promotions within IFATC and therefore (no matter how minor), will help track trends or potential issues that may arise in the future. Supervisors <strong class="red">should</strong> take note that, by definition, an absence of negative notes indicates a good track record.</p>
</section>
</section>
</section>


7D.4 Leadership

7D.4.1

Accountability exists for everyone within the team, and therefore Controllers are expected to utilize any feedback given to improve. Supervisors should{.red} make every effort to give both positive and negative feedback to Controllers (even if they are not in the Check Ride phase). When the opportunity exists and if deemed necessary (see 7D.4.4 below), Supervisors can add a "note" to the Controller's record on the website by following the steps below:

Step 1

: Go to website and login via the "Dashboard"

Step 2

: Select "Controllers" from the navigation bar at the top of the screen

Step 3

: Utilize the "search" function to find the Controller

Step 4

: Select their name from under IFC and then "notes" from the navigation bar on their profile

Step 5

: Applicable notes can be added and then saved by clicking "Add Note"

7D.4.2

When offering guidance to team members, be sure to emphasize that Controllers never stop learning and that any setbacks and/or criticisms should{.red} be taken in their stride.

7D.4.3

Supervisors may assist in general matters within IFATC, but must leave other sensitive requests to the appropriate groups (i.e. violations to Moderators, recruiting questions to Recruiters and training to Trainers).

7D.4.4

It is highly encouraged that Supervisors use the "note" function to record both positive and negative feedback for Controllers. This is always taken into consideration when Controllers are considered for promotions within IFATC and therefore (no matter how minor), will help track trends or potential issues that may arise in the future. Supervisors should{.red} take note that, by definition, an absence of negative notes indicates a good track record.

7D.4 Leadership

<section id="7e.1-overview">
<h1><a class="header-anchor" href="#7e.1-overview"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7E.1 Overview</h1>
<section class="reference"></section>
<section id="7e.1.1">
<h3><a class="header-anchor" href="#7e.1.1">7E.1.1</a></h3>
<section class="reference">
<p>The Infinite Flight Appeals Team objective is to review User-Appealed <a href="/guide/getting-started/pilot-user-interface/violations" class="documentation-content-link">Level 2 and 3 Violations</a> issued by IFATC on the Expert Server. Appeals Team members <strong class="red">must</strong> consider all factors and make an independent or team determination to uphold or reverse the issued Violation based on server rules, user history, and personal ATC experience.</p>
<p>To carry this out, Appeals Team members will be added to the following channel within Discord:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Channel">#appeals</td>
<td data-label="Purpose">This is where the appeals team can discuss appeals, procedures, and request additional input from Staff and IFC Moderators.</td>
</tr>
</tbody>
</table>
</section>
</section>
<section id="7e.1.2">
<h3><a class="header-anchor" href="#7e.1.2">7E.1.2</a></h3>
<section class="reference">
<p>In rare circumstances a Level 1 Violation may be appealed and reviewed if it was the result of a technical issue outside of the User’s control <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.1" class="documentation-content-link">7E.2.1</a> below)</em>.</p>
</section>
</section>
<section id="7e.1.3">
<h3><a class="header-anchor" href="#7e.1.3">7E.1.3</a></h3>
<section class="reference">
<p>The following rules <strong class="red">must</strong> be followed at all times:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th style="text-align:center">Rules</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Rules">The Appeals Team <strong class="red">must</strong> communicate professionally and respectfully at <strong>ALL</strong> times to best represent Infinite Flight as an extension of the company’s voice.</td>
</tr>
<tr>
<td data-label="Rules">Members <strong class="red">must not</strong> use any language which may be deemed offensive and <strong class="red">must</strong> practice common courtesies to best serve a uniquely diverse User base.</td>
</tr>
<tr>
<td data-label="Rules">Appeals Team members <strong class="red">must not</strong> discuss appeals or share User replays outside of the appropriate channels to maintain User confidentiality.</td>
</tr>
<tr>
<td data-label="Rules">Appeals Team members <strong class="red">must not</strong> share the contents of the Appeals Administrator Dashboard and may forfeit service with Infinite Flight if the distribution of sensitive information is discovered.</td>
</tr>
<tr>
<td data-label="Rules">Members <strong class="red">must</strong> make an effort to remain active to keep each member’s commitment low.</td>
</tr>
</tbody>
</table>
</section>
</section>
</section>


7E.1 Overview
7E.1.1
The Infinite Flight Appeals Team objective is to review User-Appealed Level 2 and 3 Violations issued by IFATC on the Expert Server. Appeals Team members must{.red} consider all factors and make an independent or team determination to uphold or reverse the issued Violation based on server rules, user history, and personal ATC experience.
To carry this out, Appeals Team members will be added to the following channel within Discord:
| Channel  | Purpose                                                      |
| -------- | ------------------------------------------------------------ |
| #appeals | This is where the appeals team can discuss appeals, procedures, and request additional input from Staff and IFC Moderators. |
7E.1.2
In rare circumstances a Level 1 Violation may be appealed and reviewed if it was the result of a technical issue outside of the User’s control (see 7E.2.1 below).
7E.1.3
The following rules must{.red} be followed at all times:
|                            Rules                             |
| :----------------------------------------------------------: |
| The Appeals Team must{.red} communicate professionally and respectfully at ALL times to best represent Infinite Flight as an extension of the company’s voice. |
| Members must not{.red} use any language which may be deemed offensive and must{.red} practice common courtesies to best serve a uniquely diverse User base. |
| Appeals Team members must not{.red} discuss appeals or share User replays outside of the appropriate channels to maintain User confidentiality. |
| Appeals Team members must not{.red} share the contents of the Appeals Administrator Dashboard and may forfeit service with Infinite Flight if the distribution of sensitive information is discovered. |
| Members must{.red} make an effort to remain active to keep each member’s commitment low. |

7E.1 Overview

<section id="7e.2-appeals-process">
<h1><a class="header-anchor" href="#7e.2-appeals-process"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7E.2 Appeals Process</h1>
<section class="reference"></section>
<section id="7e.2.1">
<h3><a class="header-anchor" href="#7e.2.1">7E.2.1</a></h3>
<section class="reference">
<p>The following Violations <strong class="red">should not</strong> be reversed:</p>
<ul>
<li>Level 1 Violations as these are system generated (unless evidence provided can show the root cause is technical - <em>see <a href="/guide/atc-manual/7e.-appeals/7e.1-overview#7e.1.2" class="documentation-content-link">7E.1.2</a> above</em>)</li>
<li>Violations occurring whilst the User is away from their device</li>
<li>Violations that are related to network/device issues</li>
</ul>
</section>
</section>
<section id="7e.2.2">
<h3><a class="header-anchor" href="#7e.2.2">7E.2.2</a></h3>
<section class="reference">
<p>Appeals <strong class="red">should</strong> be handled on a first come, first served basis so that a resolution can be found as expeditiously as possible for the User. By convention, once an Appeals Team member is dealing with an Appeal, it is their responsibility to ensure that a resolution is found and the Appeal is closed. If however, another team member becomes available and notices an opportunity to expedite the process, then this is permitted but they <strong class="red">should</strong> ensure that they communicate with the original team member assigned first to avoid confusing the situation.</p>
</section>
</section>
<section id="7e.2.3">
<h3><a class="header-anchor" href="#7e.2.3">7E.2.3</a></h3>
<section class="reference">
<p>The following process outlines how appeals <strong class="red">must</strong> be handled. If Appeals Team members feel that an exception is required, they may consult with Staff/IFC Moderators beforehand if they wish to do so:</p>
<dl>
<dt>Step 1</dt>
<dd>A User will initiate a Level 2/3 Violation Appeal by making a public topic or by submitting a direct message addressed to the <em>@appeals</em> group, on the IFC <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.5" class="documentation-content-link">7E.2.5</a> below)</em></dd>
<dt>Step 2</dt>
<dd>Assign yourself by scrolling to the bottom of the PM, tapping &quot;Assign&quot; (if using a mobile device, tap &quot;Topic Controls&quot; and then select &quot;Assign&quot; from the dropdown list)</dd>
<dt>Step 3</dt>
<dd>Enter your IFC Username and tap &quot;Assign&quot; (if you do this in error, you can &quot;Unassign&quot; yourself using the same method)</dd>
<dt>Step 4</dt>
<dd>If not provided already, request that the User provides all pertinent information which can be done using a number of canned responses <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.7" class="documentation-content-link">7E.2.7</a> below)</em></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>When a request is made for more information, the User <strong class="red">must</strong> be given 72 hours in which to reply. IFC Moderators may set a timer of 72 hours on the appeal if workload permits, if no reply is received the appeal will automatically close. Appeal Team members will still need to be proactive and request an IFC Moderator close the appeal if this is not done automatically</dd>
</dl>
<dl>
<dt>Step 5</dt>
<dd>The minimum required information to successfully review a Violation is Callsign and/or User Identifier, Date/Time Received, Controller Name, Replay/Screenshots (when applicable), and Scenario Details - <strong class="red">Violations more than 7 days old are not eligible for an appeal</strong></dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>As well as using the &quot;Map and Messages&quot; and &quot;States&quot; tabs when reviewing a replay, you can also find the User information by tapping on the aircraft from the map and selecting &quot;Show Details for [callsign]&quot;</dd>
</dl>
<dl>
<dt>Step 6</dt>
<dd>The Appeal is then reviewed using all available tools, perspectives, and media provided in the Appeal request. A determination to uphold or reverse the Violation is made and the User is notified of the Appeal resolution (justified Violations may be reversed sparingly when it has no impact on others or the User has a profile in good standing)</dd>
</dl>
<details>
<summary><span class="details-marker">&nbsp;</span>Decision - Violation Upheld</summary><ul>
<li>Begin by thanking them for sending the replay</li>
<li>Consider pointing out the reason the User was issued with a Violation. This will set the foundation for your decision</li>
<li>Describe the events that led to the Violation being issued</li>
<li>Follow up with any other issues that you may have recognized</li>
<li>Conclude by informing them that you're rejecting the Appeal in a polite manner and to the maximum extent possible provide resources (i.e. User Guide, Video Tutorial, Community Topics and/or an explanation of correct procedure) to prevent a similar Violation being issued in the future</li>
</ul>
</details>
<details>
<summary><span class="details-marker">&nbsp;</span>Decision - Violation Reversed</summary><ul>
<li>Begin by thanking them for sending the replay</li>
<li>If the replay shows the User followed instructions prior to the violation or if no other User was negatively impacted by their actions (and they have been polite/understanding about the situation), the Violation can be removed</li>
<li>If ATC was at fault, apologize on behalf of the Controller for any inconvenience caused</li>
<li>Remove the Violation from the dashboard with appropriate notes and inform the User to relaunch the Infinite Flight app for the reversal to take effect</li>
</ul>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If it was a courtesy reversal, the Appeals Team member <strong class="red">must</strong> communicate that this is a &quot;one-time&quot; offering</p>
</dd>
</dl>
</dl>
</details>
</section>
</section>
</section>
<section id="7e.2.4">
<h3><a class="header-anchor" href="#7e.2.4">7E.2.4</a></h3>
<section class="reference">
<p>Following the completion of an Appeal, the Appeals Team member <strong class="red">must</strong> &quot;Archive&quot; the Appeal by following the steps below:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Open the message on the <a href="https://community.infiniteflight.com" class="documentation-content-link">IFC</a> <em>(same Steps 1 - 5 as <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.7" class="documentation-content-link">7E.2.7</a> below)</em></p>
</dd>
<dt>Step 2</dt>
<dd>
<p>&quot;Unassign&quot; yourself by scrolling to the bottom of the PM and tapping &quot;Unassign&quot; (if using a mobile device, tap &quot;Topic Controls&quot; and then select &quot;Unassign&quot; from the dropdown list)</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Select &quot;Archive&quot; at the bottom of the PM</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>The message will be sent to the Appeals Archive where it can be accessed in the future if needed</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Appeals do not need to be &quot;closed&quot; (&quot;archiving&quot; <strong class="red">should</strong> be sufficient) unless the User continues to message after a final decision on the Appeal has been made, it has been more than 72 hours with no response <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.3" class="documentation-content-link">7E.2.3</a> above)</em> or the User is abusive in nature <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.3-escalation-process#7e.3.2" class="documentation-content-link">7E.3.2</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7e.2.5">
<h3><a class="header-anchor" href="#7e.2.5">7E.2.5</a></h3>
<section class="reference">
<p>If when the <em>@appeals</em> team is added, the Controller that issued the Violation is already present and has given the reasons for the violation coherently (and you can see that these are justified), no input is required unless:</p>
<ul>
<li>the User has not accepted this decision and requested a review</li>
<li>and/or the Controller has asked the appeals team to get involved</li>
</ul>
<p>If the Controller was not in the topic/PM at the time of the Appeal, they <strong class="red">should not</strong> be added unless it is deemed absolutely necessary. Anyone that is not involved with the Appeal <strong class="red">must</strong> be removed by requesting an IFC Moderator to do so. If input from the Controller is required, the Appeals Team member <strong class="red">should</strong> reach out privately and request this.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If you find that you are the Controller that issued the Violation, you <strong class="red">should</strong> let another Appeals Team member deal with the appeal to promote transparency</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7e.2.6">
<h3><a class="header-anchor" href="#7e.2.6">7E.2.6</a></h3>
<section class="reference">
<p>The following procedure outlines how to reverse a Violation:</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>Access the Appeals Administrator Dashboard (link is provided in the <em>#appeals</em> Discord channel)</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Select &quot;Users&quot; from the navigation bar and then enter the User information to search for their profile</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>To access the Users Profile, select the arrow under &quot;Profile&quot; that is in-line with their User information</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Select &quot;Violations&quot; from the navigation bar and then scroll to find the Violation you would like to reverse</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>Tick the corresponding box and then scroll to the top of the page and select &quot;Delete&quot; to remove it. Any reversed Violation will prompt the Appeals Team member to input a reason (e.g. <em>&quot;Violation Reversed: User performed go-around as instructed and was not given ample time to react&quot;</em>).</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>User notes <strong class="red">must</strong> be recorded to monitor for possible User trends, Appeal Team actions, and identify repeat offenders. If for any reason a User Note was not added, this <strong class="red">must</strong> be brought to the attention of an IFC Moderator so that this can be corrected</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="7e.2.7">
<h3><a class="header-anchor" href="#7e.2.7">7E.2.7</a></h3>
<section class="reference">
<p>Below is a list of the different canned replies available that can be sent on the IFC. Appeals Team members <strong class="red">should</strong> try to use these as often as possible to give Users a standardized experience, however at times it may be necessary to message outside of these or to customize them:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Canned Reply</th>
<th>Recommended Usage</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Canned Reply">1st - Replay Request</td>
<td data-label="Recommended Usage">If no replay file has been sent</td>
</tr>
<tr>
<td data-label="Canned Reply">2nd - Correct Template Reply</td>
<td data-label="Recommended Usage">If the original message includes all the information required to process the appeal <em>(see <a href="/guide/atc-manual/7e.-appeals/7e.2-appeals-process#7e.2.3" class="documentation-content-link">7E.2.3</a> above)</em></td>
</tr>
<tr>
<td data-label="Canned Reply">Sending Options Only</td>
<td data-label="Recommended Usage">A customized message can be sent which includes the &quot;Sending Options Only&quot; if you do not want to send the full &quot;Replay Request&quot; message, and/or have already been in dialogue with the User</td>
</tr>
<tr>
<td data-label="Canned Reply">Violation Removal</td>
<td data-label="Recommended Usage">If the violation has been removed</td>
</tr>
</tbody>
</table>
<dl>
<dt>Step 1</dt>
<dd>Login to the <a href="https://community.infiniteflight.com" class="documentation-content-link">IFC</a></dd>
<dt>Step 2</dt>
<dd>Click your profile image in the top right hand corner</dd>
<dt>Step 3</dt>
<dd>Click the messages tab twice (represented by an &quot;envelope&quot; icon)</dd>
<dt>Step 4</dt>
<dd>Select &quot;appeals&quot; from the navigation bar on the left of the screen (if you are using a mobile device you may have to select &quot;inbox&quot; to find the &quot;appeals&quot; messages)</dd>
<dt>Step 5</dt>
<dd>Select the appeals message you wish to deal with</dd>
<dt>Step 6</dt>
<dd>Use the &quot;reply&quot; icon and then select the &quot;settings cog&quot; icon</dd>
<dt>Step 7</dt>
<dd>Select &quot;Canned Replies&quot; and then scroll on the right hand side of the message screen to find the reply you wish to use (if you are using a mobile device, a drop down box is used instead)</dd>
<dt>Step 8</dt>
<dd>Tap the corresponding &quot;clipboard&quot; icon (if using a mobile device, just select the canned reply that you want to use and then tap &quot;insert reply&quot;), this will move the message to the left where it can be edited (if required) and then sent (by clicking &quot;reply&quot;)</dd>
</dl>
</section>
</section>


7E.2 Appeals Process
7E.2.1
The following Violations should not{.red} be reversed:
Level 1 Violations as these are system generated (unless evidence provided can show the root cause is technical - see 7E.1.2 above)
Violations occurring whilst the User is away from their device
Violations that are related to network/device issues
7E.2.2
Appeals should{.red} be handled on a first come, first served basis so that a resolution can be found as expeditiously as possible for the User. By convention, once an Appeals Team member is dealing with an Appeal, it is their responsibility to ensure that a resolution is found and the Appeal is closed. If however, another team member becomes available and notices an opportunity to expedite the process, then this is permitted but they should{.red} ensure that they communicate with the original team member assigned first to avoid confusing the situation.
7E.2.3
The following process outlines how appeals must{.red} be handled. If Appeals Team members feel that an exception is required, they may consult with Staff/IFC Moderators beforehand if they wish to do so:
Step 1
: A User will initiate a Level 2/3 Violation Appeal by making a public topic or by submitting a direct message addressed to the @appeals group, on the IFC (see 7E.2.5 below)
Step 2
: Assign yourself by scrolling to the bottom of the PM, tapping "Assign" (if using a mobile device, tap "Topic Controls" and then select "Assign" from the dropdown list)
Step 3
: Enter your IFC Username and tap "Assign" (if you do this in error, you can "Unassign" yourself using the same method)
Step 4
: If not provided already, request that the User provides all pertinent information which can be done using a number of canned responses (see 7E.2.7 below)
Tip
: When a request is made for more information, the User must{.red} be given 72 hours in which to reply. IFC Moderators may set a timer of 72 hours on the appeal if workload permits, if no reply is received the appeal will automatically close. Appeal Team members will still need to be proactive and request an IFC Moderator close the appeal if this is not done automatically
Step 5
: The minimum required information to successfully review a Violation is Callsign and/or User Identifier, Date/Time Received, Controller Name, Replay/Screenshots (when applicable), and Scenario Details - Violations more than 7 days old are not eligible for an appeal{.red}
Tip
: As well as using the "Map and Messages" and "States" tabs when reviewing a replay, you can also find the User information by tapping on the aircraft from the map and selecting "Show Details for [callsign]"
Step 6
: The Appeal is then reviewed using all available tools, perspectives, and media provided in the Appeal request. A determination to uphold or reverse the Violation is made and the User is notified of the Appeal resolution (justified Violations may be reversed sparingly when it has no impact on others or the User has a profile in good standing)
+++ Decision - Violation Upheld
Begin by thanking them for sending the replay
Consider pointing out the reason the User was issued with a Violation. This will set the foundation for your decision
Describe the events that led to the Violation being issued
Follow up with any other issues that you may have recognized
Conclude by informing them that you're rejecting the Appeal in a polite manner and to the maximum extent possible provide resources (i.e. User Guide, Video Tutorial, Community Topics and/or an explanation of correct procedure) to prevent a similar Violation being issued in the future
+++
+++ Decision - Violation Reversed
Begin by thanking them for sending the replay
If the replay shows the User followed instructions prior to the violation or if no other User was negatively impacted by their actions (and they have been polite/understanding about the situation), the Violation can be removed
If ATC was at fault, apologize on behalf of the Controller for any inconvenience caused
Remove the Violation from the dashboard with appropriate notes and inform the User to relaunch the Infinite Flight app for the reversal to take effect
Tip
: If it was a courtesy reversal, the Appeals Team member must{.red} communicate that this is a "one-time" offering
+++
7E.2.4
Following the completion of an Appeal, the Appeals Team member must{.red} "Archive" the Appeal by following the steps below:
Step 1
: Open the message on the IFC (same Steps 1 - 5 as 7E.2.7 below)
Step 2
: "Unassign" yourself by scrolling to the bottom of the PM and tapping "Unassign" (if using a mobile device, tap "Topic Controls" and then select "Unassign" from the dropdown list)
Step 3
: Select "Archive" at the bottom of the PM
Step 4
: The message will be sent to the Appeals Archive where it can be accessed in the future if needed
Tip
: Appeals do not need to be "closed" ("archiving" should{.red} be sufficient) unless the User continues to message after a final decision on the Appeal has been made, it has been more than 72 hours with no response (see 7E.2.3 above) or the User is abusive in nature (see 7E.3.2 below)
7E.2.5
If when the @appeals team is added, the Controller that issued the Violation is already present and has given the reasons for the violation coherently (and you can see that these are justified), no input is required unless:
the User has not accepted this decision and requested a review
and/or the Controller has asked the appeals team to get involved
If the Controller was not in the topic/PM at the time of the Appeal, they should not{.red} be added unless it is deemed absolutely necessary. Anyone that is not involved with the Appeal must{.red} be removed by requesting an IFC Moderator to do so. If input from the Controller is required, the Appeals Team member should{.red} reach out privately and request this.
Tip
: If you find that you are the Controller that issued the Violation, you should{.red} let another Appeals Team member deal with the appeal to promote transparency
7E.2.6
The following procedure outlines how to reverse a Violation:
Step 1
: Access the Appeals Administrator Dashboard (link is provided in the #appeals Discord channel)
Step 2
: Select "Users" from the navigation bar and then enter the User information to search for their profile
Step 3
: To access the Users Profile, select the arrow under "Profile" that is in-line with their User information
Step 4
: Select "Violations" from the navigation bar and then scroll to find the Violation you would like to reverse
Step 5
: Tick the corresponding box and then scroll to the top of the page and select "Delete" to remove it. Any reversed Violation will prompt the Appeals Team member to input a reason (e.g. "Violation Reversed: User performed go-around as instructed and was not given ample time to react").
Tip
: User notes must{.red} be recorded to monitor for possible User trends, Appeal Team actions, and identify repeat offenders. If for any reason a User Note was not added, this must{.red} be brought to the attention of an IFC Moderator so that this can be corrected
7E.2.7
Below is a list of the different canned replies available that can be sent on the IFC. Appeals Team members should{.red} try to use these as often as possible to give Users a standardized experience, however at times it may be necessary to message outside of these or to customize them:
| Canned Reply                 | Recommended Usage                                            |
| ---------------------------- | ------------------------------------------------------------ |
| 1st - Replay Request         | If no replay file has been sent                              |
| 2nd - Correct Template Reply | If the original message includes all the information required to process the appeal (see 7E.2.3 above) |
| Sending Options Only         | A customized message can be sent which includes the "Sending Options Only" if you do not want to send the full "Replay Request" message, and/or have already been in dialogue with the User |
| Violation Removal            | If the violation has been removed                            |
Step 1
: Login to the IFC
Step 2
: Click your profile image in the top right hand corner
Step 3
: Click the messages tab twice (represented by an "envelope" icon)
Step 4
: Select "appeals" from the navigation bar on the left of the screen (if you are using a mobile device you may have to select "inbox" to find the "appeals" messages)
Step 5
: Select the appeals message you wish to deal with
Step 6
: Use the "reply" icon and then select the "settings cog" icon
Step 7
: Select "Canned Replies" and then scroll on the right hand side of the message screen to find the reply you wish to use (if you are using a mobile device, a drop down box is used instead)
Step 8
: Tap the corresponding "clipboard" icon (if using a mobile device, just select the canned reply that you want to use and then tap "insert reply"), this will move the message to the left where it can be edited (if required) and then sent (by clicking "reply")

7E.2 Appeals Process

<section id="7e.3-escalation-process">
<h1><a class="header-anchor" href="#7e.3-escalation-process"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> 7E.3 Escalation Process</h1>
<section class="reference"></section>
<section id="7e.3.1">
<h3><a class="header-anchor" href="#7e.3.1">7E.3.1</a></h3>
<section class="reference">
<p>When an appeal cannot be resolved independently or with the help of additional Appeals Team members via the <em>#appeals</em> Discord Channel, an Appeals Team member <strong class="red">should</strong> request assistance from an IFC Moderator to provide a final determination (where necessary, the final authority for all appeals is with Infinite Flight Staff members).</p>
</section>
</section>
<section id="7e.3.2">
<h3><a class="header-anchor" href="#7e.3.2">7E.3.2</a></h3>
<section class="reference">
<p>Any IFC member submitting an Appeal is expected to remain calm, courteous, and respectful. Abusive language or behavior will not be tolerated and <strong class="red">should</strong> be &quot;flagged&quot; so that it can be brought to the attention of IFC Moderators who will close the Appeal.</p>
</section>
</section>
<section id="7e.3.3">
<h3><a class="header-anchor" href="#7e.3.3">7E.3.3</a></h3>
<section class="reference">
<p>If Appeals Team members feel it is necessary to provide Controller feedback following an Appeal, or notice consistent violation reversals for the same Controller, they <strong class="red">should</strong>:</p>
<dl>
<dt>Step 1</dt>
<dd>Raise this in the <em>#appeals</em> Discord Channel to reach a consensus with other members</dd>
<dt>Step 2</dt>
<dd>If it is deemed to be a potential issue the Controller can be spoken to directly to try and establish the root cause (and if appropriate, provide corrective feedback)</dd>
<dt>Step 3</dt>
<dd>Document this by going to the <a href="https://if-atc.com" class="documentation-content-link">website</a> and logging in via the &quot;Dashboard&quot;</dd>
<dt>Step 4</dt>
<dd>Select &quot;Controllers&quot; from the navigation bar at the top of the screen</dd>
<dt>Step 5</dt>
<dd>Utilize the &quot;search&quot; function to find the Controller</dd>
<dt>Step 6</dt>
<dd>Select their name from under IFC and then &quot;notes&quot; from the navigation bar on their profile</dd>
<dt>Step 7</dt>
<dd>Applicable notes can be added (we recommended starting with &quot;From Appeals:&quot; so that it is clear) and then saved by clicking &quot;Add Note&quot;</dd>
<dt>Step 8</dt>
<dd>If the Appeals Team member feels that the Controller was not receptive to feedback, the issue continues and/or any other reason they feel makes it necessary, this can escalated by bringing it to the attention of an IFC Moderator</dd>
</dl>
</section>
</section>
</section>


7E.3 Escalation Process
7E.3.1
When an appeal cannot be resolved independently or with the help of additional Appeals Team members via the #appeals Discord Channel, an Appeals Team member should{.red} request assistance from an IFC Moderator to provide a final determination (where necessary, the final authority for all appeals is with Infinite Flight Staff members).
7E.3.2
Any IFC member submitting an Appeal is expected to remain calm, courteous, and respectful. Abusive language or behavior will not be tolerated and should{.red} be "flagged" so that it can be brought to the attention of IFC Moderators who will close the Appeal.
7E.3.3
If Appeals Team members feel it is necessary to provide Controller feedback following an Appeal, or notice consistent violation reversals for the same Controller, they should{.red}:
Step 1
: Raise this in the #appeals Discord Channel to reach a consensus with other members
Step 2
: If it is deemed to be a potential issue the Controller can be spoken to directly to try and establish the root cause (and if appropriate, provide corrective feedback)
Step 3
: Document this by going to the website and logging in via the "Dashboard"
Step 4
: Select "Controllers" from the navigation bar at the top of the screen
Step 5
: Utilize the "search" function to find the Controller
Step 6
: Select their name from under IFC and then "notes" from the navigation bar on their profile
Step 7
: Applicable notes can be added (we recommended starting with "From Appeals:" so that it is clear) and then saved by clicking "Add Note"
Step 8
: If the Appeals Team member feels that the Controller was not receptive to feedback, the issue continues and/or any other reason they feel makes it necessary, this can escalated by bringing it to the attention of an IFC Moderator

7E.3 Escalation Process

If you're new to Infinite Flight, this is the place to start. We'll get you up and running quickly with our comprehensive Getting Started guide!

Getting Started

Now that you know your way around the user interface, it's time to take to the skies. Our Flying Guide will help you on your journey to the Expert Server!

Flying Guide

Whether you're a qualified controller or just beginning your journey, the ATC Manual will be your guide to controlling the skies of Infinite Flight.

ATC Manual

Still having trouble? Our expert support team will get you back up and running in no time.

Get Help

Explore our developer documentation and find out how to extend Infinite Flight with our APIs.

Support & Features

Connect