<section id="1.1-overview">
<h1><a class="header-anchor" href="#1.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> 1.1 Overview</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>
<dl>
<dt>Must</dt>
<dd>The use of <strong class="red">must</strong> or <strong class="red">must not</strong> within this manual is considered <strong>MANDATORY</strong> and strict compliance is <strong>REQUIRED</strong></dd>
<dt>Should</dt>
<dd>The use of <strong class="red">should</strong> or <strong class="red">should not</strong> within this manual is considered <strong>ADVISORY</strong> and compliance is <strong>STRONGLY RECOMMENDED</strong></dd>
</dl>
</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.</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>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 ATC Manager via the IFC or the IFATC Discord.</p>
</section>
</section>
</section>


1.1 Overview

<section id="1.2-abbreviations">
<h1><a class="header-anchor" href="#1.2-abbreviations"><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.2 Abbreviations</h1>
<section class="reference"></section>
<section id="1.2.1">
<h3><a class="header-anchor" href="#1.2.1">1.2.1</a></h3>
<section class="reference">
<p>All abbreviations contained within this manual are listed below with their associated definition:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Abbreviation</th>
<th>Definition</th>
</tr>
</thead>
<tbody>
<tr>
<td>AAL</td>
<td>Above Aerodrome Level</td>
</tr>
<tr>
<td>AGL</td>
<td>Above Ground Level</td>
</tr>
<tr>
<td>Alt</td>
<td>Altitude</td>
</tr>
<tr>
<td>ATC</td>
<td>Air Traffic Control</td>
</tr>
<tr>
<td>ATIS</td>
<td>Automatic Terminal Information Service</td>
</tr>
<tr>
<td>CAF</td>
<td>Continue As Filed</td>
</tr>
<tr>
<td>DM</td>
<td>Direct Message</td>
</tr>
<tr>
<td>FAA</td>
<td>Federal Aviation Administration</td>
</tr>
<tr>
<td>FF</td>
<td>Flash Flight</td>
</tr>
<tr>
<td>FF</td>
<td>Flight Following</td>
</tr>
<tr>
<td>FPL</td>
<td>Flight Plan</td>
</tr>
<tr>
<td>FS</td>
<td>Full Stop</td>
</tr>
<tr>
<td>Ft</td>
<td>Feet</td>
</tr>
<tr>
<td>GMT</td>
<td>Greenwich Mean Time</td>
</tr>
<tr>
<td>GPS</td>
<td>Global Positioning System</td>
</tr>
<tr>
<td>GA</td>
<td>General Aviation</td>
</tr>
<tr>
<td>G/A</td>
<td>Go-Around</td>
</tr>
<tr>
<td>GS</td>
<td>Groundspeed</td>
</tr>
<tr>
<td>G/S</td>
<td>Glideslope</td>
</tr>
<tr>
<td>HWC</td>
<td>Headwind Component</td>
</tr>
<tr>
<td>KIAS</td>
<td>Knots Indicated Airspeed</td>
</tr>
<tr>
<td>IAS</td>
<td>Indicated  Airspeed</td>
</tr>
<tr>
<td>ICAO</td>
<td>International Civil Aviation Organization</td>
</tr>
<tr>
<td>IFATC</td>
<td>Infinite Flight Air Traffic Controllers</td>
</tr>
<tr>
<td>IF</td>
<td>Infinite Flight</td>
</tr>
<tr>
<td>IFC</td>
<td>Infinite Flight Community</td>
</tr>
<tr>
<td>IFFG</td>
<td>Infinite Flight Fan Group</td>
</tr>
<tr>
<td>IFR</td>
<td>Instrument Flight Rules</td>
</tr>
<tr>
<td>ILS</td>
<td>Instrument Landing System</td>
</tr>
<tr>
<td>IMC</td>
<td>Instrument Meteorological Conditions</td>
</tr>
<tr>
<td>IRL</td>
<td>In Real Life</td>
</tr>
<tr>
<td>Kts</td>
<td>Knots</td>
</tr>
<tr>
<td>LLC</td>
<td>Limited Liability Company</td>
</tr>
<tr>
<td>LOC</td>
<td>Localizer</td>
</tr>
<tr>
<td>LUAW</td>
<td>Line Up And Wait</td>
</tr>
<tr>
<td>METAR</td>
<td>Meteorological Aerodrome Report</td>
</tr>
<tr>
<td>MSA</td>
<td>Minimum Sector Altitude</td>
</tr>
<tr>
<td>Nm</td>
<td>Nautical Mile</td>
</tr>
<tr>
<td>NOTAMS</td>
<td>Notification to Airmen</td>
</tr>
<tr>
<td>RAIS</td>
<td>Report Airport In Sight</td>
</tr>
<tr>
<td>RET</td>
<td>Rapid Exit Taxiway</td>
</tr>
<tr>
<td>RV</td>
<td>Radar Vectors</td>
</tr>
<tr>
<td>RWY</td>
<td>Runway</td>
</tr>
<tr>
<td>SFC</td>
<td>Surface</td>
</tr>
<tr>
<td>SID</td>
<td>Standard Instrument Departure</td>
</tr>
<tr>
<td>STAR</td>
<td>Standard Terminal Arrival Route</td>
</tr>
<tr>
<td>TAF</td>
<td>Terminal Aerodrome Forecast</td>
</tr>
<tr>
<td>TOD</td>
<td>Top of Descent</td>
</tr>
<tr>
<td>TWC</td>
<td>Tailwind Component</td>
</tr>
<tr>
<td>UFN</td>
<td>Until Further Notice</td>
</tr>
<tr>
<td>UTC</td>
<td>Coordinated Universal Time</td>
</tr>
<tr>
<td>VARB</td>
<td>Virtual Airline Regulatory Board</td>
</tr>
<tr>
<td>VC / VCs</td>
<td>Voice Channel / Voice Channels</td>
</tr>
<tr>
<td>VFR</td>
<td>Visual Flight Rules</td>
</tr>
<tr>
<td>VIS</td>
<td>Visual</td>
</tr>
<tr>
<td>VMC</td>
<td>Visual Meteorological Conditions</td>
</tr>
<tr>
<td>VNAV</td>
<td>Vertical Navigation</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


1.2 Abbreviations

<section id="1a.1-discord-communication">
<h1><a class="header-anchor" href="#1a.1-discord-communication"><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</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</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>The channels and their use is outlined in the table below:</p>
<div class="table-wrapper"><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>#atc-schedule</td>
<td style="text-align:left">The ATC Schedule briefing room channel can be used to brief/plan anything related to featured airports on any given day</td>
</tr>
<tr>
<td>#announcements</td>
<td style="text-align:left">Official Infinite Flight updates (such as new blog updates, new versions of the ATC Manual, and Beta information) to be made in this channel by the ATC Manager, Staff and Moderators only</td>
</tr>
<tr>
<td>#botcommands</td>
<td style="text-align:left">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.-administration/1a.1-discord-communication#1a.1.3" class="documentation-content-link">1A.1.3</a> below)</em></td>
</tr>
<tr>
<td>#controllers</td>
<td style="text-align:left">All normal Controller communications to occur in this channel. This channel <strong class="red">should not</strong> be used unless <strong>ACTIVELY</strong> controlling. Controllers can use the abbreviations found below this table when sending opening/closing messages instead of the full facility names if they prefer to do so</td>
</tr>
<tr>
<td>#discussions</td>
<td style="text-align:left">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>#events</td>
<td style="text-align:left">The Events briefing room channel may be used to coordinate official and unofficial events such as FF, GA Day and streams</td>
</tr>
<tr>
<td>#flights</td>
<td style="text-align:left">This channel is used for Controllers to coordinate group flights together. All coordination <strong class="red">should</strong> remain in this channel</td>
</tr>
<tr>
<td>#help-request</td>
<td style="text-align:left">If Controllers require support that cannot be found elsewhere, they can &quot;raise&quot; a ticket in this channel by reacting to the relevant role <em>(for further guidance see <a href="/guide/atc-manual/1a.-administration/1a.2-discord-rules#1a.2.4" class="documentation-content-link">1A.2.4</a> below)</em></td>
</tr>
<tr>
<td>#important-info</td>
<td style="text-align:left">Useful links as well as the Terms &amp; Conditions that <strong class="red">must</strong> be accepted by &quot;reacting&quot; before access is granted to the rest of the server</td>
</tr>
<tr>
<td>#infinite-flight-rules</td>
<td style="text-align:left">Highlights where to find the rules of the IFATC Discord server</td>
</tr>
<tr>
<td>#offtopic</td>
<td style="text-align:left">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>#readonly</td>
<td style="text-align:left">Day to day posts (such as housekeeping and event specific procedures) to be made in this channel by the ATC Manager, Staff and Moderators only</td>
</tr>
<tr>
<td>#role-assignments</td>
<td style="text-align:left">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. Controllers that use the mentioned phrase <strong class="red">must</strong> only use it when necessary to avoid spamming other Controllers <em>(see <a href="/guide/atc-manual/1a.-administration/1a.3-controller-rules#1a.3.1" class="documentation-content-link">1A.3.1</a> below)</em></td>
</tr>
<tr>
<td>#screenshots</td>
<td style="text-align:left">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>#social-media</td>
<td style="text-align:left">Automated official Infinite Flight social media updates. 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>#training-time</td>
<td style="text-align:left">Trainers will post in this channel when they require pilots to join in for training sessions <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.5" class="documentation-content-link">7.1.5</a> below)</em></td>
</tr>
</tbody>
</table></div><blockquote>
<p>When Controllers send opening/closing messages, the following letters/abbreviations can be used if Controllers find it more convenient than using the full facility names:</p>
<ul>
<li>
<p>G - Ground</p>
</li>
<li>
<p>T - Tower</p>
</li>
<li>
<p>S - ATIS</p>
</li>
<li>
<p>A or App - Approach</p>
</li>
<li>
<p>D or Dep - Departure</p>
</li>
<li>
<p>C or Center - Center</p>
</li>
</ul>
<p>e.g. &quot;EGLL GTS open&quot;</p>
</blockquote>
</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.3">
<h3><a class="header-anchor" href="#1a.1.3">1A.1.3</a></h3>
<section class="reference">
<p>By typing &quot;/&quot; into the Discord message bar, a list of commands will be generated that can be used for various functions.</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.4">
<h3><a class="header-anchor" href="#1a.1.4">1A.1.4</a></h3>
<section class="reference">
<p>Voice Channels (VCs) <strong class="red">must</strong> only be used in accordance with the Discord Rules <em>(see <a href="/guide/atc-manual/1a.-administration/1a.2-discord-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 the <em>#controllers</em> Discord channel</li>
</ul>
</section>
</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 VCs is <strong class="red">not required</strong> and is at the sole discretion of the Controller (there may be select events where the use of VCs 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 <strong>ONLY</strong> do so if <strong>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>
</section>
</section>
<section id="1a.1.6">
<h3><a class="header-anchor" href="#1a.1.6">1A.1.6</a></h3>
<section class="reference">
<p>To open a VC, the following steps are to be followed:</p>
<dl>
<dt>Step 1</dt>
<dd>Open the IFATC Discord and using the navigation bar on the left side of the screen, find the &quot;Controlling&quot; tab</dd>
<dt>Step 2</dt>
<dd>Under this, click &quot;Select to Create VC&quot;, a new VC will be created with you as the owner of that channel. It will automatically be titled with your Discord username</dd>
<dt>Step 3</dt>
<dd>The VC title <strong class="red">must</strong> then be changed to an appropriate* name so that it is clear to other Controllers what the VC purpose is <em>(see <a href="https://infiniteflight.com/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.7" class="documentation-content-link">1A.1.7</a> below)</em></dd>
</dl>
<p>*<em>An appropriate name is one that provides no ambiguity - the standard or preferred naming is to use the ICAO code of the airport being controlled (e.g. EGPH) however if more than one airport is being controlled in a particular VC, then a more generic title can be chosen (e.g. New York Area, Oceanic Centers, Dubai Flyout Event etc.)</em></p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Only the owner of the VC can change the name or user limit <em>(see <a href="https://infiniteflight.com/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.7" class="documentation-content-link">1A.1.7</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
<section id="1a.1.7">
<h3><a class="header-anchor" href="#1a.1.7">1A.1.7</a></h3>
<section class="reference">
<p>Below are the commands that can be used in the <em>#botcommands</em> Discord channel to manage a VC:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Commands</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>!voice-claim @[username]</td>
<td>Claim ownership of the VC</td>
</tr>
<tr>
<td>!voice-limit [number]</td>
<td>Change the user limit of the VC (the default is 10)</td>
</tr>
<tr>
<td>!voice-owner</td>
<td>Will inform you who is the current owner of the VC</td>
</tr>
<tr>
<td>!voice-rename [ICAO code]</td>
<td>Rename the VC</td>
</tr>
<tr>
<td>!voice-transfer @[username]</td>
<td>*Transfer ownership of the VC</td>
</tr>
</tbody>
</table></div><p>*<em>Ownership can only be transferred to Controllers that are in the VC. VC owners <strong class="red">should</strong> ensure that ownership is transferred before leaving the VC to avoid the channel being closed (channels will automatically close when vacant for 1 minute)</em></p>
</section>
</section>
<section id="1a.1.8">
<h3><a class="header-anchor" href="#1a.1.8">1A.1.8</a></h3>
<section class="reference">
<p>Below are some useful tips for VCs:</p>
<ul>
<li>You can see how many members currently occupy a VC at any time by noting the [00/10] channel count</li>
<li>Selecting &quot;Mute&quot; (microphone symbol) means no one can hear you</li>
<li>Selecting &quot;Deafen&quot; (headphones symbol) 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 whilst controlling</li>
</ul>
</section>
</section>


1A.1 Discord Communication

<section id="1a.2-discord-rules">
<h1><a class="header-anchor" href="#1a.2-discord-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  Discord 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.-administration/1a.2-discord-rules#1a.2.1" class="documentation-content-link">1A.2.1</a> below)</em></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.2.1">
<h3><a class="header-anchor" href="#1a.2.1">1A.2.1</a></h3>
<section class="reference">
<ul>
<li>All Controllers <strong class="red">must</strong> link their <a href="/guide/getting-started-guide/home-user-interface/user-profile#linking-community-forum-account" class="documentation-content-link">Community Forum</a> and <a href="/guide/getting-started-guide/home-user-interface/user-profile#linking-a-discord-account" class="documentation-content-link">Discord</a> accounts <strong>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>
<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.2.2">
<h3><a class="header-anchor" href="#1a.2.2">1A.2.2</a></h3>
<section class="reference">
<ul>
<li>English <strong class="red">must</strong> be used at all times</li>
<li>The voice channels <strong class="red">must</strong> only be used by members who are actively controlling with other Controllers</li>
<li>Coordination to use voice channels <strong class="red">must</strong> only occur in the <em>#controllers</em> Discord channel</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 VCs can be found in Discord Communication <em>(see <a href="/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.4" class="documentation-content-link">1A.1.4</a> above)</em></li>
</ul>
</section>
</section>
<section id="1a.2.3">
<h3><a class="header-anchor" href="#1a.2.3">1A.2.3</a></h3>
<section class="reference">
<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>
<blockquote>
<p>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)</p>
</blockquote>
</section>
</section>
</section>
<section id="support">
<h2><a class="header-anchor" href="#support"><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> Support</h2>
<section class="reference"></section>
<section id="1a.2.4">
<h3><a class="header-anchor" href="#1a.2.4">1A.2.4</a></h3>
<section class="reference">
<ul>
<li>In the first instance, Controllers <strong class="red">should</strong> make every effort to use the resources available to them, including this manual and fellow Controllers, to seek support</li>
<li>If Controllers are unable to find the answer they need, they can &quot;raise&quot; a ticket in the <em>#help-request</em> Discord Channel by &quot;reacting&quot; to the relevant role. A new private channel will be created which the Controller can then open to start a dialogue and get the support they need</li>
<li>The Rank Structure can be helpful to find out what the different roles in IFATC are, and therefore who might be appropriate to ask <em>(see <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.1" class="documentation-content-link">1A.6.1</a> below)</em></li>
</ul>
</section>
</section>
</section>


1A.2 Discord Rules

<section id="1a.3-controller-rules">
<h1><a class="header-anchor" href="#1a.3-controller-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.3 Controller Rules</h1>
<section class="reference"></section>
<section id="1a.3.1">
<h3><a class="header-anchor" href="#1a.3.1">1A.3.1</a></h3>
<section class="reference">
<ul>
<li>
<p>All Controllers <strong class="red">must</strong> announce in <em>#controllers</em> when opening/closing any frequency (including which facilities, such as Ground and Tower) on the Expert Server. When closing, a <strong>MINIMUM</strong> of 5 minutes warning and the last ATIS letter used <strong class="red">must</strong> be provided. Use of abbreviations in place of the full facility names is acceptable <em>(see <a href="/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.2" class="documentation-content-link">1A.1.2</a> above)</em></p>
</li>
<li>
<p>Controllers are expected to show common courtesy to other Controllers by sharing where possible, opening frequencies that promote traffic between airports, and opening before announcing in <em>#controllers</em></p>
</li>
<li>
<p>Opening frequencies is on a first come, first serve basis within <em>#controllers</em>. Therefore Controllers <strong class="red">must not</strong> reserve frequencies privately or not open in anticipation of a particular frequency becoming available. Controllers may commit to specific frequencies/positions for community events and <strong class="red">should</strong> be afforded the opportunity to staff those at the event start time by fellow controllers</p>
</li>
<li>
<p>Controllers <strong class="red">should</strong> avoid staffing or providing service to airports which do not have ramp spawns points for aircraft</p>
</li>
<li>
<p>Controllers that utilize the <em>@Tower Relief</em> and <em>@Radar Relief</em> reaction roles <strong class="red">must</strong> only use these once, and <strong class="red">must</strong> include the airport and time they are closing</p>
</li>
<li>
<p>Controllers that utilize the <em>@split</em> reaction role <strong class="red">must</strong> only use it once, and <strong class="red">must</strong> include the airport. It is recommended to use this prior to opening</p>
</li>
<li>
<p>Controllers <strong class="red">must not</strong> tag other Controllers that are currently open on an active frequency unless it is operationally critical (this does not include Controllers open on a different frequency that are sending operational messages to each other)</p>
</li>
<li>
<p>Controllers <strong class="red">must not</strong> control on the Training Server <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.4" class="documentation-content-link">7.4.4</a> below for exceptions)</em></p>
</li>
<li>
<p>Controllers <strong class="red">must not</strong> actively control and fly on separate devices. Autopilot+ may be used for active flights in the background while controlling or participating in a training session</p>
</li>
<li>
<p>Controllers <strong class="red">must not</strong> control Infinite Flight on other platforms (such as BlueStacks) due to Controller replays not being stored <em>(see <a href="/guide/atc-manual/1b.-violations/1b.3-incident-resolution-procedure#1b.3.1" class="documentation-content-link">1B.3.1</a> above)</em></p>
</li>
<li>
<p>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.-administration/1a.6-rank-structure#1a.6-rank-structure" class="documentation-content-link">1A.6</a> below)</em></p>
</li>
</ul>
</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-overview#1b.1-overview" class="documentation-content-link">1B.1</a> below).</em></p>
</section>
</section>
</section>


1A.3 Controller Rules

<section id="1a.4-airport-selection">
<h1><a class="header-anchor" href="#1a.4-airport-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> 1A.4 Airport Selection</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">
<ul>
<li>
<p>The ATC Schedule posted on the <a href="https://community.infiniteflight.com" class="documentation-content-link">IFC</a> will feature 3 - 5 daily airports (changing at 0600Z each day) to help focus traffic into a concentrated area of the world</p>
</li>
<li>
<p>Controllers can control anywhere in the world at any time (featured airports do not have to be fully staffed before a Controller is permitted to open an airport of their choosing) with the exception of official events</p>
</li>
<li>
<p>Official event timings and rules will always be posted in <em>#readonly</em>. Controllers <strong class="red">must</strong> fully staff the event airports during this time <strong>BEFORE</strong> any other airport is opened. 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.-administration/1a.6-rank-structure#1a.6.1" class="documentation-content-link">1A.6.1</a> below)</em>, in which case a sensible alternative* <strong class="red">should</strong> be selected</p>
</li>
</ul>
<p>*<em>A sensible alternative is seen as an airport in keeping with the general theme and geographic area of the Official Event, if a Controller is in doubt they <strong class="red">should</strong> ask their fellow Controllers for help in choosing</em></p>
<blockquote>
<p>For official events (e.g. FF, GA Day or livesteams), Controllers can open the event airports up to 1 hour (maximum) before the event start time to ensure full coverage</p>
</blockquote>
</section>
</section>
</section>


1A.4 Airport Selection

<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 - Controllers that are removed from IFATC for inactivity more than twice, are not permitted to rejoin - <em>see <a href="/guide/atc-manual/1a.-administration/1a.5-activity-requirements#1a.5.2" class="documentation-content-link">1A.5.2</a> below</em>)</p>
</li>
<li>
<p>12 Months:  <strong class="red">Must</strong> complete the Initial Theory and Practical tests to re-join</p>
</li>
</ul>
<blockquote>
<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>
</blockquote>
</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>Controllers that are removed twice for inactivity will not be permitted to rejoin due to the strain this has on recruitment and training resources. This can be appealed with the IFATC Manager or IFATC Moderators and will be handled on a case by case basis.</p>
</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>Minimum and maximum controlling times are enforced to ensure that pilots receive a good and consistent service. These are highlighted in the table below:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Rank</th>
<th>Minimum Time</th>
<th>Maximum Time</th>
</tr>
</thead>
<tbody>
<tr>
<td>Apprentice</td>
<td>30 minutes</td>
<td>12 hours</td>
</tr>
<tr>
<td>Specialist*</td>
<td>1 hour</td>
<td>12 hours</td>
</tr>
<tr>
<td>Officer*</td>
<td>1 hour</td>
<td>12 hours</td>
</tr>
<tr>
<td>Supervisor</td>
<td>1 hour</td>
<td>12 hours</td>
</tr>
</tbody>
</table></div><p>*<em>This includes Controllers currently in the Specialist/Officer Check Ride phase (see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1" class="documentation-content-link">1A.7.1</a> below)</em></p>
<blockquote>
<p>Controllers <strong class="red">must</strong> ensure that the standard of controlling expected is maintained during long sessions, the maximum controlling times are cumulative and <strong class="red">must not</strong> be exceeded in a 24 hour period</p>
</blockquote>
</section>
</section>
<section id="1a.5.4">
<h3><a class="header-anchor" href="#1a.5.4">1A.5.4</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

<section id="1a.6-rank-structure">
<h1><a class="header-anchor" href="#1a.6-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.6  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 official events. If in doubt, ask in <em>#controllers</em> for suggestions before opening – it takes time to get used to heavy traffic, start off <strong>SLOWLY</strong></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="1a.6.1">
<h3><a class="header-anchor" href="#1a.6.1">1A.6.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, training and testing:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Rank</th>
<th>Frequencies Available</th>
<th>Test Required</th>
<th>Check Ride</th>
</tr>
</thead>
<tbody>
<tr>
<td>Apprentice</td>
<td>B / C / D / ATIS</td>
<td>Theory and Practical (Tower)</td>
<td>No</td>
</tr>
<tr>
<td>Specialist</td>
<td>B / C / D / ATIS</td>
<td>No</td>
<td>Yes*</td>
</tr>
<tr>
<td>Officer</td>
<td>Radar / B / C / D / ATIS</td>
<td>Theory and Practical (Radar)</td>
<td>Yes**</td>
</tr>
<tr>
<td>Supervisor</td>
<td>No restrictions</td>
<td>No</td>
<td>No</td>
</tr>
</tbody>
</table></div><p>*<em>On promotion to Specialist, Controllers are placed on probation until the &quot;Specialist Check Ride&quot; phase is completed (see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.4" class="documentation-content-link">1A.7.4</a> below)</em></p>
<p>**<em>On promotion to Officer, Controllers are placed on probation until the &quot;Officer Check Ride&quot; phase is completed (see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.6" class="documentation-content-link">1A.7.6</a> below)</em></p>
<blockquote>
<p>All Controllers are subject to promotion/demotion at any time based on activity, performance and feedback!</p>
</blockquote>
</section>
</section>
<section id="apprentice">
<h2><a class="header-anchor" href="#apprentice"><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> Apprentice</h2>
<section class="reference"></section>
<section id="1a.6.2">
<h3><a class="header-anchor" href="#1a.6.2">1A.6.2</a></h3>
<section class="reference">
<p>This is the entry rank for IFATC and so the maximum arrival count at the time of opening any airport is 25 aircraft. Apprentices <strong class="red">must not</strong> control any facility which is a livestream airport, official event airport, or HUB of published event featured on the ATC Schedule <em>(other official events are permitted unless indicated otherwise - see <a href="/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1" class="documentation-content-link">1A.4.1</a> above)</em></p>
<blockquote>
<p>It is acceptable for the arrival count to increase above this limit once open, however Apprentices <strong class="red">should</strong> try to select appropriate airports that take into account the length of time they are controlling for, and any increases in traffic <em>(see <a href="/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1" class="documentation-content-link">1A.4.1</a> and <a href="/guide/atc-manual/1a.-administration/1a.5-activity-requirements#1a.5.3" class="documentation-content-link">1A.5.3</a> above)</em></p>
</blockquote>
</section>
</section>
</section>
<section id="promotion-to-specialist">
<h2><a class="header-anchor" href="#promotion-to-specialist"><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> Promotion to Specialist</h2>
<section class="reference"></section>
<section id="1a.6.3">
<h3><a class="header-anchor" href="#1a.6.3">1A.6.3</a></h3>
<section class="reference">
<p>Promotion to the rank of Specialist is dealt with on a case by case basis, and not solely on time served. With this in 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. Controllers will be notified when they have been promoted and placed in the Specialist Check Ride phase <em>(see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.4" class="documentation-content-link">1A.7.4</a> below)</em>.</p>
</section>
</section>
</section>
<section id="promotion-to-officer">
<h2><a class="header-anchor" href="#promotion-to-officer"><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> Promotion to Officer</h2>
<section class="reference"></section>
<section id="1a.6.4">
<h3><a class="header-anchor" href="#1a.6.4">1A.6.4</a></h3>
<section class="reference">
<p>Promotion to the rank of Officer is by application only <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1" class="documentation-content-link">7.4.1</a> below)</em> and the Radar Training program <strong class="red">must</strong> be successfully passed in order to achieve this rank and subsequently control radar facilities.</p>
</section>
</section>
<section id="1a.6.5">
<h3><a class="header-anchor" href="#1a.6.5">1A.6.5</a></h3>
<section class="reference">
<p>Before commencement of training for the rank of Officer, the following requirements <strong class="red">must</strong> be met:</p>
<ul>
<li>
<p>Minimum of 60 days at the rank of Specialist</p>
</li>
<li>
<p>Minimum of 2000 all-time operations</p>
</li>
<li>
<p>Attended a total of 10 training sessions as a pilot</p>
<p><em>Note</em>: Once accepted, trainees are expected to participate in at least one training session as a pilot for every training session they're afforded as ATC</p>
</li>
<li>
<p>Maintain an active controlling record* over the previous 30 days to ensure proficiency (this will be determined by the Recruiter at the time of application)</p>
</li>
</ul>
<p>*<em>An active controlling record is considered to be 2-3 ATC sessions per week</em></p>
</section>
</section>
<section id="1a.6.6">
<h3><a class="header-anchor" href="#1a.6.6">1A.6.6</a></h3>
<section class="reference">
<p>Returning members of IFATC that previously held the rank of Officer are not subject to the above same criteria and may apply (and commence training) for the rank of Officer immediately following the successful completion of the &quot;Specialist Check Ride&quot; phase <em>(see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1" class="documentation-content-link">1A.7.1</a> below)</em>.</p>
</section>
</section>
</section>
<section id="promotion-to-supervisor">
<h2><a class="header-anchor" href="#promotion-to-supervisor"><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> Promotion to Supervisor</h2>
<section class="reference"></section>
<section id="1a.6.7">
<h3><a class="header-anchor" href="#1a.6.7">1A.6.7</a></h3>
<section class="reference">
<p>The rank of Supervisor is only awarded when a need exists and to Controllers that have demonstrated a high standard of controlling and professional conduct within IFATC. Their role 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. The following prerequisites are required for promotion to the rank of Supervisor:</p>
<ul>
<li>Officer rank with demonstrated proficiency on <strong>all</strong> facility types/classes</li>
<li>Correct usage of the report feature with no history of misuse</li>
<li>Proficient pilot who leads by example and aviates in accordance with all server rules</li>
<li>Positive IFATC record</li>
<li>Ability to communicate respectfully and professionally</li>
</ul>
</section>
</section>
</section>
<section id="other-ifatc-roles">
<h2><a class="header-anchor" href="#other-ifatc-roles"><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> Other IFATC Roles</h2>
<section class="reference"></section>
<section id="1a.6.8">
<h3><a class="header-anchor" href="#1a.6.8">1A.6.8</a></h3>
<section class="reference">
<p>In addition to the rank structure outlined above, individuals may hold other roles within IFATC. These are shown below:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Title</th>
<th>Role</th>
<th>Rank</th>
<th>Violation Reversals</th>
</tr>
</thead>
<tbody>
<tr>
<td>Appeals</td>
<td>Manage violation appeals</td>
<td>N/A</td>
<td>Yes</td>
</tr>
<tr>
<td>Tester</td>
<td>Attend practical tests</td>
<td>N/A</td>
<td>No</td>
</tr>
<tr>
<td>Trainer</td>
<td>Educate and train Candidates/Controllers</td>
<td>Officer or above</td>
<td>No</td>
</tr>
<tr>
<td>Recruiter</td>
<td>Manage recruitment and administer all theory/practical tests</td>
<td>Officer or above</td>
<td>Only if related to official tests</td>
</tr>
<tr>
<td>Moderator</td>
<td>Moderates the IFATC team, including day to day operations, quality assurance, personnel issues, member Violations, performance and disciplinary demotions and/or suspensions</td>
<td>N/A</td>
<td>Yes</td>
</tr>
<tr>
<td>Manager</td>
<td>Representative of the Infinite Flight Staff team that manages all of IFATC</td>
<td>N/A</td>
<td>Yes</td>
</tr>
</tbody>
</table></div><blockquote>
<p>IFC Moderators are present within the IFATC team however IFATC Moderators will usually deal with most day to day tasks</p>
</blockquote>
</section>
</section>
</section>


1A.6 Rank Structure

<section id="1a.7-check-ride-process">
<h1><a class="header-anchor" href="#1a.7-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> 1A.7  Check Ride Process</h1>
<section class="reference"></section>
<section id="1a.7.1">
<h3><a class="header-anchor" href="#1a.7.1">1A.7.1</a></h3>
<section class="reference">
<p>The Check Ride process is used to monitor newly promoted Specialists and Officers, the procedures to be followed are outlined below:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Check Ride</th>
<th>Period</th>
<th>Max Arrival Count*</th>
<th>Eligibility</th>
</tr>
</thead>
<tbody>
<tr>
<td>Specialist</td>
<td>7 days</td>
<td>50</td>
<td>See <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.2" class="documentation-content-link">1A.6.2</a> above</td>
</tr>
<tr>
<td>Officer</td>
<td>30 days</td>
<td>50</td>
<td>See <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.3" class="documentation-content-link">1A.6.3</a> above</td>
</tr>
<tr>
<td>Prior Officer</td>
<td>15 days</td>
<td>50</td>
<td>See <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.6" class="documentation-content-link">1A.6.6</a> above</td>
</tr>
</tbody>
</table></div><p>*<em>at the time of opening</em></p>
<blockquote>
<p>One of the main aspects of the Check Ride process is ensuring that quality of service is maintained with the Controller's new role. Therefore during the evaluation, the Controller's ability to select sensible airports and set a personal limitation <strong class="red">must</strong> be satisfactory to complete the Check Ride phase</p>
</blockquote>
</section>
</section>
<section id="1a.7.2">
<h3><a class="header-anchor" href="#1a.7.2">1A.7.2</a></h3>
<section class="reference">
<p>When Controllers are eligible for promotion to the rank of Specialist (based on activity, performance and feedback) or have passed The Radar Practical Test for the rank of Officer, they will receive a DM informing them of their promotion on a probationary basis. 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 when applicable.</p>
</section>
</section>
<section id="1a.7.3">
<h3><a class="header-anchor" href="#1a.7.3">1A.7.3</a></h3>
<section class="reference">
<p>The Check Ride phase should not be longer than the periods outlined <em>(see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.1" class="documentation-content-link">1A.7.1</a> above)</em>, however 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>ALL</strong> the instructions set out within this section 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 their previous rank, and a subsequent promotion will take place in due course.</p>
</section>
</section>
<section id="specialist-check-ride">
<h2><a class="header-anchor" href="#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> Specialist Check Ride</h2>
<section class="reference"></section>
<section id="1a.7.4">
<h3><a class="header-anchor" href="#1a.7.4">1A.7.4</a></h3>
<section class="reference">
<p>Controllers that are currently in the Specialist Check Ride phase:</p>
<ul>
<li>
<p><strong class="red">must</strong> control Bravo classification airports where possible (Charlie classification airports are acceptable if they provide for adequate evaluation)</p>
</li>
<li>
<p><strong class="red">must</strong> control on a regular basis (at least 3 separate occasions)</p>
</li>
<li>
<p><strong class="red">must not</strong> control any facility which has 50 or more total inbounds at the time of opening</p>
</li>
<li>
<p><strong class="red">must not</strong> control any facility which is a livestream airport, official event airport, or HUB of a published event featured on the ATC Schedule <em>(other official events are permitted unless indicated otherwise - see <a href="/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1" class="documentation-content-link">1A.4.1</a> above)</em></p>
</li>
</ul>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Splitting the frequencies (such as just controlling Ground) with other Controllers is heavily encouraged, especially at featured airports</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="1a.7.5">
<h3><a class="header-anchor" href="#1a.7.5">1A.7.5</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/promotion-to-specialist-v2.svg" alt="Image 1A.7.5.1 - Promotion to Specialist Flowchart " class="documentation-image-lightbox-link" >
          <figcaption>Image 1A.7.5.1 - Promotion to Specialist Flowchart </figcaption>
        </figure>
      </p>
</section>
</section>
<section id="officer-check-ride">
<h2><a class="header-anchor" href="#officer-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> Officer Check Ride</h2>
<section class="reference"></section>
<section id="1a.7.6">
<h3><a class="header-anchor" href="#1a.7.6">1A.7.6</a></h3>
<section class="reference">
<p>Controllers that are currently in the Officer Check Ride phase:</p>
<ul>
<li>
<p><strong class="red">must not</strong> control any facility (including Center) which has 50 or more total inbounds at the time of opening</p>
</li>
<li>
<p><strong class="red">must not</strong> control any facility which is a livestream airport, official event airport, or HUB of a published event featured on the ATC Schedule <em>(other official events are permitted unless indicated otherwise - see <a href="/guide/atc-manual/1a.-administration/1a.4-airport-selection#1a.4.1" class="documentation-content-link">1A.4.1</a> above)</em></p>
</li>
</ul>
<blockquote>
<p>Controllers are expected to be responsible in their new role; starting off slowly and ensuring quality of service, over quantity.</p>
</blockquote>
</section>
</section>
<section id="1a.7.7">
<h3><a class="header-anchor" href="#1a.7.7">1A.7.7</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/radar-recruitment-v3.svg" alt="Image 7.4.9.1 - Radar Recruitment Flowchart" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.9.1 - Radar Recruitment Flowchart</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


1A.7 Check Ride Process

<section id="1a.8-disciplinary-and-suspension-procedure">
<h1><a class="header-anchor" href="#1a.8-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.8  Disciplinary and Suspension Procedure</h1>
<section class="reference"></section>
<section id="1a.8.1">
<h3><a class="header-anchor" href="#1a.8.1">1A.8.1</a></h3>
<section class="reference">
<p>Controllers not following the ATC Manual can expect the following procedure:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Offense</th>
<th>Action Taken</th>
</tr>
</thead>
<tbody>
<tr>
<td>1st</td>
<td>Warning via DM</td>
</tr>
<tr>
<td>2nd</td>
<td>3 day Controller &amp; Discord suspension</td>
</tr>
<tr>
<td>3rd</td>
<td>7 day Controller &amp; Discord suspension</td>
</tr>
<tr>
<td>4th</td>
<td>Removal from the IFATC Team</td>
</tr>
</tbody>
</table></div><p>Following any suspension, Controllers will return at the rank they previously held. Usually the date they’re reinstated on will serve as the new start date at that rank; however, this is dealt with on a case by case basis <em>(this is to take into account minimum requirements for rank upgrades - see <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.1" class="documentation-content-link">1A.6.1</a> above)</em>.</p>
</section>
</section>
<section id="1a.8.2">
<h3><a class="header-anchor" href="#1a.8.2">1A.8.2</a></h3>
<section class="reference">
<p>If a controller is issued a Level 2 or Level 3 Violation whilst operating as a pilot, an IFATC Moderator will initiate a review of the session to determine if the Violation is to be upheld or removed. Excessive Violations or total lack of regard for rules may result in IFATC suspension or permanent removal.</p>
</section>
</section>
</section>


1A.8 Disciplinary and Suspension Procedure

<section id="1b.1-overview">
<h1><a class="header-anchor" href="#1b.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> 1B.1  Overview</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; 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Violation</th>
<th>Consequence</th>
</tr>
</thead>
<tbody>
<tr>
<td>Level  1</td>
<td>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>Level  2 (Amber)</td>
<td>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>Level  3 (Red)</td>
<td>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></div><p>*<em>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</em></p>
<details>
<summary><span class="details-marker">&nbsp;</span>Level 1 Violation Table</summary><div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Rule</th>
<th>Conditions for Violation</th>
</tr>
</thead>
<tbody>
<tr>
<td>Ground Overspeed</td>
<td>Above 35kts GS (ground speed) on ground, excluding runways</td>
</tr>
<tr>
<td>Flight Overspeed</td>
<td>Above 250kts IAS (indicated airspeed) below 10,000ft / exceeding max speed warning (VMO/MMO) - does not apply to military aircraft</td>
</tr>
<tr>
<td>Aerobatics within Airspace</td>
<td>Aerobatics below 5,000ft and within 5 nautical miles of an airport</td>
</tr>
<tr>
<td>Runway Idle</td>
<td>Sit idle on a runway longer than 60 seconds without ATC clearance</td>
</tr>
</tbody>
</table></div></details>
<blockquote>
<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>
</blockquote>
</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>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.4">
<h3><a class="header-anchor" href="#1b.1.4">1B.1.4</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 <em>(see <a href="/guide/atc-manual/1b.-violations/1b.3-incident-resolution-procedure" class="documentation-content-link">1B.3</a> below)</em>.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If a Controller issues a Violation in error, they can &quot;raise&quot; a ticket in the <em>#help-request</em> Discord channel with the Appeals Team to get this rectified <em>(see <a href="/guide/atc-manual/1a.-administration/1a.2-discord-rules#1a.2.4" class="documentation-content-link">1A.2.4</a> above)</em></p>
</dd>
</dl>
</dl>
</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>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.6">
<h3><a class="header-anchor" href="#1b.1.6">1B.1.6</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.-administration/1a.8-disciplinary-and-suspension-procedure" class="documentation-content-link">1A.8</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.7">
<h3><a class="header-anchor" href="#1b.1.7">1B.1.7</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 id="1b.1.8">
<h3><a class="header-anchor" href="#1b.1.8">1B.1.8</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must not</strong> ask other Controllers to issue Violations on their behalf under <strong>ANY</strong> circumstances.</p>
</section>
</section>


1B.1 Overview

<section id="1b.2-violation-reasons">
<h1><a class="header-anchor" href="#1b.2-violation-reasons"><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  Violation Reasons</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>Some of the possible scenarios that could result in a Violation being issued are listed below:</p>
<ul>
<li>Not following procedures broadcast on ATIS or in a published TFR/NOTAM</li>
<li>Pushback/taxiing without clearance</li>
<li>Crashing/taxiing into other aircraft/buildings/objects*</li>
<li>Taking-off/landing from a taxiway or grass</li>
<li>Entering the runway without clearance</li>
<li>Taking-off/landing without clearance</li>
<li>Not following the issued sequence</li>
<li>Not following the cleared altitude/heading/speed</li>
<li>Pilots who do not respond to an instruction after 2-3 attempts**</li>
<li>Pilots sending duplicate messages or unnecessary requests</li>
<li>Spamming a frequency</li>
<li>Repeated disruption</li>
<li>Insulting or inappropriate call-signs/usernames or flight path/plan(s)</li>
<li>Call-signs/usernames with profanity or discriminating/racist terms</li>
<li>Excessive speed in the airport environment***</li>
</ul>
<p>*<em>Rendering issues may mean that aircraft did not see the other aircraft/buildings/objects, care should be taken to ensure that violations are only issued for aircraft that have blatantly done it on purpose</em></p>
<p>**<em>Aircraft descending via VNAV may be issued a violation after a warning if they are unresponsive <strong>AND</strong> conflict with others</em></p>
<p>***<em>Speed which results in rapid closure with other aircraft, loss of separation, or airspace disruption may be deemed “excessive”. Good judgment <strong class="red">must</strong> be used</em></p>
<blockquote>
<p>Fighter aircraft <strong class="red">must not</strong> exceed 350KIAS when below 10,000ft and under ATC control, however pilots are expected to maintain a reasonable speed in the vicinity of other aircraft or when instructed to slow down by Controllers. Reporting for excessive speed can be issued when a lack of etiquette is shown. Standard speed restrictions for commercial aircraft also apply to military cargo aircraft (i.e. maximum 250 KIAS when below 10,000ft and under ATC control)</p>
</blockquote>
</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>A full list of the in-app options that can be selected 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>
<details>
<summary><span class="details-marker">&nbsp;</span>Ground</summary><div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td>Blocking an active taxiway</td>
<td>2</td>
</tr>
<tr>
<td>Crossing the hold line without permission</td>
<td>2</td>
</tr>
<tr>
<td>Entered a runway without permission</td>
<td>3</td>
</tr>
<tr>
<td>Failure to follow ATIS</td>
<td>2</td>
</tr>
<tr>
<td>Failure to follow TFR</td>
<td>3</td>
</tr>
<tr>
<td>Failure to give way</td>
<td>2</td>
</tr>
<tr>
<td>Inappropriate callsign</td>
<td>3</td>
</tr>
<tr>
<td>Not following instructions</td>
<td>2</td>
</tr>
<tr>
<td>Spamming frequency - unnecessary duplicate requests</td>
<td>2</td>
</tr>
<tr>
<td>Taxi without permission</td>
<td>2</td>
</tr>
<tr>
<td>Taxiing through grass or terminal area</td>
<td>2</td>
</tr>
<tr>
<td>Taxiing through others</td>
<td>2</td>
</tr>
<tr>
<td>Too close to aircraft ahead</td>
<td>2</td>
</tr>
<tr>
<td>Unable to communicate</td>
<td>N/A</td>
</tr>
<tr>
<td>Unresponsive while climbing, descending, or maneuvering</td>
<td>2</td>
</tr>
</tbody>
</table></div></details>
<details>
<summary><span class="details-marker">&nbsp;</span>Tower</summary><div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td>Crossing the hold line without permission</td>
<td>2</td>
</tr>
<tr>
<td>Entered a runway without permission</td>
<td>3</td>
</tr>
<tr>
<td>Excessive speed in the airport environment</td>
<td>3</td>
</tr>
<tr>
<td>Failure to divert</td>
<td>3</td>
</tr>
<tr>
<td>Failure to exit runway</td>
<td>2</td>
</tr>
<tr>
<td>Failure to follow ATIS</td>
<td>2</td>
</tr>
<tr>
<td>Failure to follow sequence</td>
<td>2</td>
</tr>
<tr>
<td>Failure to follow TFR</td>
<td>3</td>
</tr>
<tr>
<td>Failure to go-around</td>
<td>2</td>
</tr>
<tr>
<td>Failure to maintain appropriate aircraft separation</td>
<td>2</td>
</tr>
<tr>
<td>Flying through other aircraft</td>
<td>3</td>
</tr>
<tr>
<td>Inappropriate callsign</td>
<td>3</td>
</tr>
<tr>
<td>Incorrect arrival procedures - inappropriate altitude, speed, position</td>
<td>3</td>
</tr>
<tr>
<td>Landing/departing on the wrong runway</td>
<td>3</td>
</tr>
<tr>
<td>Not following instructions</td>
<td>2</td>
</tr>
<tr>
<td>Spamming frequency - unnecessary duplicate requests</td>
<td>2</td>
</tr>
<tr>
<td>Take-off/land without permission</td>
<td>3</td>
</tr>
<tr>
<td>Take-off/landing from grass, ramp or taxiway</td>
<td>3</td>
</tr>
<tr>
<td>Unable to communicate</td>
<td>N/A</td>
</tr>
<tr>
<td>Unresponsive while climbing, descending, or maneuvering</td>
<td>2</td>
</tr>
</tbody>
</table></div></details>
<details>
<summary><span class="details-marker">&nbsp;</span>Radar</summary><div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Reason</th>
<th>Violation Level</th>
</tr>
</thead>
<tbody>
<tr>
<td>Aligned with the wrong runway</td>
<td>2</td>
</tr>
<tr>
<td>Excessive speed in the airport environment</td>
<td>3</td>
</tr>
<tr>
<td>Failure to complete instrument approach</td>
<td>2</td>
</tr>
<tr>
<td>Failure to divert</td>
<td>3</td>
</tr>
<tr>
<td>Failure to execute missed approach</td>
<td>3</td>
</tr>
<tr>
<td>Failure to follow ATIS</td>
<td>2</td>
</tr>
<tr>
<td>Failure to follow TFR</td>
<td>3</td>
</tr>
<tr>
<td>Failure to maintain appropriate aircraft separation</td>
<td>2</td>
</tr>
<tr>
<td>Following flight plan instead of ATC instructions</td>
<td>3</td>
</tr>
<tr>
<td>Inappropriate callsign</td>
<td>3</td>
</tr>
<tr>
<td>Incorrect arrival procedures - inappropriate altitude, speed, position</td>
<td>3</td>
</tr>
<tr>
<td>Not following ATC assigned heading, altitude or speed</td>
<td>3</td>
</tr>
<tr>
<td>Not following instructions</td>
<td>2</td>
</tr>
<tr>
<td>Spamming frequency - unnecessary duplicate requests</td>
<td>2</td>
</tr>
<tr>
<td>Unable to communicate</td>
<td>N/A</td>
</tr>
<tr>
<td>Unresponsive while climbing, descending, or maneuvering</td>
<td>2</td>
</tr>
</tbody>
</table></div></details>
</section>
</section>
</section>


1B.2 Violation Reasons

<section id="1b.3-incident-resolution-procedure">
<h1><a class="header-anchor" href="#1b.3-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.3  Incident Resolution Procedure</h1>
<section class="reference"></section>
<section id="1b.3.1">
<h3><a class="header-anchor" href="#1b.3.1">1B.3.1</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> keep <strong>ALL</strong> replays following a controlling session for a <strong>MINIMUM</strong> of 7 days. These replays may be requested by IFATC Leadership or Appeals team members for quality assurance and/or Violation resolution.</p>
<blockquote>
<p>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 is usually no longer eligible for appeal, however may be reviewed at the discretion of the Appeals Team</p>
</blockquote>
</section>
</section>
<section id="1b.3.2">
<h3><a class="header-anchor" href="#1b.3.2">1B.3.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>In the event that both the Controller and the Appeals Team are added to the DM, the Controller <strong class="red">must</strong> observe only and allow the Appeals Team to deal with the appeal. If input is required by the Controller, the Appeals Team member dealing with the appeal will privately message the Controller</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.3.3">
<h3><a class="header-anchor" href="#1b.3.3">1B.3.3</a></h3>
<section class="reference">
<p>If you are <strong>NOT THE CONTROLLER INVOLVED</strong> you <strong class="red">must not</strong> respond.</p>
</section>
</section>
</section>


1B.3 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>ALL</strong> available runways <strong class="red">should</strong> be used at <strong>ALL</strong> times <em>(see <a href="/guide/atc-manual/4.-atis/4.1-overview#4.1.4" class="documentation-content-link">4.1.4</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.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.1</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">
<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/1050790791" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
</section>
<section id="2.1.3">
<h3><a class="header-anchor" href="#2.1.3">2.1.3</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> check that the area is clear before issuing pushback clearance. If it is not clear, the use of &quot;hold position&quot; or a give way command <strong class="red">must</strong> be used prior to issuing the pushback clearance (a reminder can be set to avoid forgetting about the aircraft or if it is very busy).</p>
<blockquote>
<p>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>
</blockquote>
</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>Under most circumstances, the Controller <strong class="red">should</strong> approve an aircraft’s initial request to pushback or taxi, regardless of aircraft type or parking, due to the availability of pushback equipment for all aircraft and the wide variety of parking spot configurations.</p>
<blockquote>
<p>Controllers <strong class="red">should</strong> be familiar with their airport’s parking configuration while operating. i.e. can aircraft pull straight through their remote stand? Do aircraft require a pushback to safely exit the spot?</p>
</blockquote>
</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>Auto pushback and/or tail position assignment <strong class="red">should</strong> be used to the max extent possible at eligible airports to dictate the pushback path and beginning taxi position of aircraft under control. To pause an auto pushback in progress, advise the aircraft to “hold position”. A subsequent “pushback approved” is approval to resume the previously assigned auto pushback. When a conflict is not present Controllers <strong class="red">may</strong> elect to approve a pushback without tail or auto push guidance.</p>
<blockquote>
<p>To amend a pushback path Controllers should advise the aircraft to &quot;hold position&quot; and reissue a new pushback clearance with the amended path.</p>
</blockquote>
</section>
</section>
<section id="2.1.6">
<h3><a class="header-anchor" href="#2.1.6">2.1.6</a></h3>
<section class="reference">
<p>The use of &quot;expect runway xx&quot; <strong class="red">may</strong> be used if the Controller deems it necessary; however, it is not required for each pushback clearance.</p>
</section>
</section>
</section>


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 as well as prioritize issuing &quot;give way&quot; commands to aircraft that could conflict with traffic exiting the runway.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If a conflict exists, resolve this by issuing the &quot;give way&quot; command first, followed by the taxi instructions. This ensures that the pilot is aware of the potential conflict <strong>BEFORE</strong> they start to taxi</p>
</dd>
</dl>
</dl>
</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 taxiing departing/arriving aircraft. Where available, Controllers <strong class="red">should</strong> use the &quot;drag and taxi&quot; feature to issue specific taxi routes. Controllers <strong class="red">must</strong> issue a crossing clearance to aircraft for each runway their route crosses (and an aircraft <strong class="red">must</strong> have crossed a previous runway before another runway crossing clearance may be issued).</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>At large and complex airports (e.g. KORD, EHAM, KJFK etc) it is often most effective to issue partial taxi instructions to intermediate holding points rather than a route from the parking spot all the way to the runway (or vice versa)</p>
</dd>
</dl>
</dl>
</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>Controllers <strong class="red">should</strong> not assign specific gates for arriving aircraft requesting taxi to park. Parking spot determination <strong class="red">should</strong> be made by the pilot and accommodated by ATC, when possible. Aircraft requesting a clearance to taxi to parking without a specific spot may be given specific routing via progressive instructions or drag &amp; taxi routing to deconflict with other traffic, however they <strong class="red">should</strong> be allowed to proceed to their desired spot once all conflicts are resolved.</p>
</section>
</section>
<section id="2.2.4">
<h3><a class="header-anchor" href="#2.2.4">2.2.4</a></h3>
<section class="reference">
<p>Controllers also 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>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 &quot;Continue Taxi at your discretion&quot;.</p>
</section>
</section>
<section id="2.2.5">
<h3><a class="header-anchor" href="#2.2.5">2.2.5</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

<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 exists to allow for the traffic to cross and clear the runway edge (not hold short line) safely. Aircraft <strong class="red">must not</strong> be crossed unless:</p>
<ul>
<li>the departing aircraft has not yet commenced the take-off roll</li>
<li>the departing aircraft has commenced their take-off roll but is airborne and visibly turning, or past the crossing point (regardless of altitude)</li>
<li>the arriving aircraft has not yet crossed the runway threshold</li>
<li>the arriving aircraft has crossed the runway threshold but is either visibly exiting prior to the crossing point, or is past the crossing point</li>
</ul>
<blockquote>
<p>In all cases, coordination with the Tower Controller is essential!</p>
</blockquote>
</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

<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">
<p>The same separation should be afforded in these scenarios to protect for missed approaches/go arounds.</p>
</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>ALL</strong> aircraft:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Type</th>
<th>Rule</th>
</tr>
</thead>
<tbody>
<tr>
<td>Departure / Departure</td>
<td>The first aircraft <strong class="red">must</strong> be airborne before the second aircraft* commences the take-off roll</td>
</tr>
<tr>
<td>Arrival / Arrival</td>
<td>The first aircraft <strong class="red">must</strong> be clear of the runway edge (not the hold short line) before the second aircraft crosses the threshold</td>
</tr>
<tr>
<td>Departure / Arrival</td>
<td>The first aircraft <strong class="red">must</strong> be airborne before the second aircraft crosses the threshold</td>
</tr>
<tr>
<td>Arrival / Departure</td>
<td>The first aircraft <strong class="red">must</strong> be clear of the runway edge (not the hold short line) before the second aircraft commences the take-off roll</td>
</tr>
<tr>
<td>Intersecting</td>
<td>Arriving/departing aircraft <strong class="red">must</strong> be beyond the runway intersection prior to a departure beginning it's take-off roll or an arrival crossing the threshold on an intersecting runway. Consideration <strong class="red">should</strong> also be given to the extended centerline of runways, where the runway does not physically intersect, but aircraft flight paths would during take-off and landing. In these cases the same separation criteria <strong class="red">should</strong> be afforded</td>
</tr>
</tbody>
</table></div><p>*<em>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</em></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>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Aircraft that have been cleared for take-off are not guaranteed to get airborne and may reject the take-off roll if needed. Active monitoring is required by Controllers to ensure separation with other aircraft is maintained (e.g. if another aircraft has been cleared for take-off from the same runway, cancel their take-off clearance)</p>
</dd>
</dl>
</dl>
</section>
</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>
<blockquote>
<p>It is generally considered too late to request an aircraft to reject the takeoff roll when they are above 100kts</p>
</blockquote>
</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>


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>
<blockquote>
<p>An aircraft that has been cleared for take-off is no longer considered in the departure sequence - therefore the next aircraft holding short is considered number 1 for departure. However, if an aircraft has been instructed to LUAW, the next aircraft holding short is considered number 2 for departure</p>
</blockquote>
</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 will affect the departure/arrival flow rate. Controllers <strong class="red">should not</strong> view intersection departures as &quot;queue jumping&quot;, 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>Jet aircraft are assumed ready for departure upon reaching the hold short line at the assigned departure runway. Controllers may issue a line up &amp; wait or takeoff clearance <strong>prior</strong> to the aircraft requesting departure.</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 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.8" class="documentation-content-link">3.2.8</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>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.11-instrument-landing-system-(ils)-approach#6.11.4" class="documentation-content-link">6.11.4</a> below).</em></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>When &quot;Straight Out Dept.&quot; is being broadcast in the current ATIS <em>(see <a href="/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.1</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.10">
<h3><a class="header-anchor" href="#3.2.10">3.2.10</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.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.1</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>
<section id="frequency-change">
<h2><a class="header-anchor" href="#frequency-change"><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> Frequency Change</h2>
<section class="reference"></section>
<section id="3.2.11">
<h3><a class="header-anchor" href="#3.2.11">3.2.11</a></h3>
<section class="reference">
<p>Departing aircraft <strong class="red">should</strong> be issued a frequency change 1/2 mile off the departure end unless there are potential conflicts (these <strong class="red">must</strong> be resolved prior to approving a frequency change). Controllers <strong class="red">should</strong> avoid changes during critical phases of flight (i.e. immediately after rotation).</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If an aircraft does not change frequency, just swipe the aircraft data strip. Multiple frequency change requests or warnings are not necessary</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>


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">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Local flights may be authorized if inbound at a position, altitude, and speed which does not disrupt the flow of traffic. Controllers <strong class="red">should</strong> attempt to accommodate inbound traffic, regardless of flight time, but may deny services if an unreasonable request is made that will diminish service for other aircraft</p>
</dd>
</dl>
</dl>
</section>
</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>ALL</strong> aircraft as a <strong>MINIMUM</strong>, regardless of what the aircraft uses to check in on the Tower frequency. Pilots may call inbound on the ILS, GPS, or Visual approach, even in the absence of approach control, if flying the charted approach. The assigned pattern entry and sequence will still be dependent on traffic, though published approaches should be accommodated to the max extent possible <em>(see 3.3.1.1 below)</em>.</p>
<blockquote>
<p>Controllers <strong class="red">should</strong> take into account the aircraft flight plan (in particular the STAR or instrument approach) 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>
</blockquote>
<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>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 aircraft's 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>


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 <em>(see 3.4.1.1 below)</em>. 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>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>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>TEMPORARILY</strong> - as soon as traffic levels are manageable, Controllers <strong class="red">must</strong> resume pattern work</li>
</ul>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-traffic-pattern.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-traffic-pattern@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-traffic-pattern@3x.jpg 3x" alt="Image 3.4.1.1 - The Traffic Pattern" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.4.1.1 - The Traffic Pattern</figcaption>
        </figure>
      </p>
</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.4.2.1 - Tower Airspace for KDFW" class="documentation-image-lightbox-link" >
          <figcaption>Image 3.4.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 &quot;Flight of XX&quot; 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

<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>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If aircraft are in the pattern and have not announced a full stop, the Controller can assume the aircraft intends on performing a touch &amp; go or stop &amp; go <em>(see <a href="/guide/atc-manual/3.-tower/3.3-inbounds#3.3.5" class="documentation-content-link">3.3.5</a> above)</em>. In this case, delay the exit command until it is clear that the aircraft is intending on a full stop (i.e. either starting to exit the runway or there is no longer sufficient runway left for the aircraft to take-off again)</p>
</dd>
</dl>
</dl>
</section>
</section>
</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 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 &quot;go-around&quot; (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/fly runway heading&quot; <strong class="red">must</strong> be used to maintain positive control. 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. In most instances, an aircraft returning to Radar from a go-around <strong class="red">should</strong> be instructed to &quot;fly runway heading&quot;.</p>
</section>
</section>
</section>


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>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>ALL</strong> runways <strong class="red">should</strong> be used <em>(see <a href="/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.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>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>When Tower Controllers have finished their session and are handing over to a new Tower Controller, it is recommended to use the same frequency unless it has been agreed with the Radar Controller which frequency will be used after the switch - this helps ensure the frequency change quick commands are unaffected during the Controller changeover</p>
</dd>
</dl>
</dl>
</section>
</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. It will then be up to the Radar Controller's discretion to decide if they can accept radar pattern work based on their workload (consideration <strong class="red">should</strong> also be given to the Tower Controller's workload such as a long departure line).</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>
<div class="table-wrapper"><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>ILS/GPS</td>
<td>No</td>
<td>No</td>
<td>Yes</td>
</tr>
<tr>
<td>Radar Vectors</td>
<td>Yes</td>
<td>If  Req</td>
<td>Yes</td>
</tr>
<tr>
<td>Flight Following</td>
<td>Yes</td>
<td>If  Req</td>
<td>Yes</td>
</tr>
<tr>
<td>Visual</td>
<td>No</td>
<td>If  Req</td>
<td>Yes</td>
</tr>
</tbody>
</table></div><blockquote>
<p>&quot;If req&quot; means that unless the aircraft is number 1, a sequence is <strong>required</strong> before issuing the clearance</p>
</blockquote>
</section>
</section>


3.6 Tower Working with Radar

<section id="4.1-overview">
<h1><a class="header-anchor" href="#4.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> 4.1 Overview</h1>
<section class="reference"></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 to keep pilots informed.</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>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>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>
<blockquote>
<p>Pilots will advise on contact with Controllers what ATIS information they have received. Those checking in with the wrong ATIS identifier can be instructed to recheck the latest ATIS information. Pilots then assume all responsibility for checking before making further requests. Controllers are not required to recheck that the pilot has received the latest ATIS information following this</p>
</blockquote>
</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>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.4">
<h3><a class="header-anchor" href="#4.1.4">4.1.4</a></h3>
<section class="reference">
<p><strong>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>ALL</strong> runways from being used; in this case it is acceptable to not use <strong>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.5">
<h3><a class="header-anchor" href="#4.1.5">4.1.5</a></h3>
<section class="reference">
<p>When a servicing radar facility is active, the ATIS <strong class="red">must</strong> specify which approach type (ILS, GPS, or Visual) is in use. The advertised approach <strong class="red">must</strong> be available in the procedure selection menu (i.e. a GPS approach is published for the airport if it is to be the advertised approach). Controllers may still deviate from the advertised approach if operationally advantageous. Tower only airports may advertise an approach in use, though standard pattern entries will primarily dictate aircraft navigation to the landing runway(s).</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 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>


4.1 Overview

<section id="4.2-remarks-and-notams">
<h1><a class="header-anchor" href="#4.2-remarks-and-notams"><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.2 Remarks and NOTAMs</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.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.1</a> below)</em></p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="4.2.1">
<h3><a class="header-anchor" href="#4.2.1">4.2.1</a></h3>
<section class="reference">
<p>The table below highlights when certain REMARKS or NOTAMS <strong class="red">should</strong> be used:</p>
<div class="table-wrapper"><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>No Intersection Dept.</td>
<td>Intersection departures <strong class="red">must</strong> always be allowed unless it blocks the only taxiway for aircraft to access full length <strong>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>No Pattern Work</td>
<td>Weather below VMC? Terrain prevents a standard pattern from being flown? <strong>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>Gate Hold</td>
<td>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>No Light Aircraft</td>
<td>This command <strong class="red">must not</strong> be used at GA focused airports but can be used at the Controller's discretion at any other airport based on airport accommodations (such as GA parking and airport layout), current traffic, and airport staffing. Controllers <strong class="red">should</strong> make every attempt to accept light aircraft at airports which accept them IRL. <br />Light aircraft are defined as the C172, SR22, XCub, Spitfire Mk VIII and P38.</td>
</tr>
<tr>
<td>Rolling Dept.</td>
<td>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 can still be used when there is an operational advantage such as an arrival / departure sequence, or departure / departure sequence where the first aircraft is slow to begin their take-off roll</td>
</tr>
<tr>
<td>FPL Required</td>
<td>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> or when SID/STAR usage is mandated</td>
</tr>
<tr>
<td>Straight Out Dept. **</td>
<td>Runway heading <strong class="red">must</strong> be flown after departure until no conflict exists <strong>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>Mult. Freq. In Use</td>
<td><em>(See <a href="/guide/atc-manual/4.-atis/4.1-overview#4.1.5" class="documentation-content-link">4.1.5</a> above)</em></td>
</tr>
<tr>
<td>Check Forum</td>
<td>Only to be used when referring pilots to special instructions on the IFC pages e.g. VARB Summit</td>
</tr>
<tr>
<td>SID/STAR Use Rcmd***</td>
<td>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.2-remarks-and-notams#4.2.2" class="documentation-content-link">4.2.2</a> below)</em></td>
</tr>
<tr>
<td>SID/STAR Use Req***</td>
<td>This command <strong class="red">should</strong> be used when heavy traffic exists and SID/STAR use is essential for traffic management <strong>OR</strong> for events and/or main hub airports  <em>(see <a href="/guide/atc-manual/4.-atis/4.2-remarks-and-notams#4.2.2" class="documentation-content-link">4.2.2</a> below)</em></td>
</tr>
<tr>
<td>Event</td>
<td>IF LLC sponsored events only</td>
</tr>
<tr>
<td>Size Restrictions</td>
<td>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>Low Visibility</td>
<td>Low Visibility – visibility less than ¼  statute miles (400m)</td>
</tr>
</tbody>
</table></div><p>**<em>Take note that the use of &quot;Straight Out Dept.&quot; may prevent aircraft from flying their selected SID (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>***<em>Only to be used if the airport has published SID/STAR procedures available</em></p>
</section>
</section>
<section id="4.2.2">
<h3><a class="header-anchor" href="#4.2.2">4.2.2</a></h3>
<section class="reference">
<p>Controllers 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>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.2 Remarks and NOTAMs

<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 its vertical jurisdiction, lateral boundaries and frequency range for the facility being operated. Below is a summary for each Controller position:</p>
<div class="table-wrapper"><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>Tower</td>
<td>SFC - 5000ft AAL</td>
<td>Most immediate ring/boundary surrounding the airport</td>
</tr>
<tr>
<td>Departure/Approach</td>
<td>SFC - 18,000ft/FL180</td>
<td>50nm</td>
</tr>
<tr>
<td>Center</td>
<td>SFC - 60,000ft/FL600</td>
<td>White boundaries</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Airspace parameters and ATC jurisdictions may be altered with the use of NOTAMs and/or TFRs during special events</p>
</blockquote>
<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 <strong class="red">should</strong> 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Airspace Type</th>
<th>Color Code</th>
</tr>
</thead>
<tbody>
<tr>
<td>Class B</td>
<td>Blue</td>
</tr>
<tr>
<td>Class C</td>
<td>Magenta</td>
</tr>
<tr>
<td>Class D</td>
<td>Light Blue</td>
</tr>
<tr>
<td>Terminal Control Area</td>
<td>Light Green</td>
</tr>
<tr>
<td>Flight Information Region (FIR)</td>
<td>White</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


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 &quot;on guard&quot; 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Facility</th>
<th>Vertical and Lateral Limits</th>
</tr>
</thead>
<tbody>
<tr>
<td>Tower</td>
<td>SFC - 10,000ft AAL and within 25nm</td>
</tr>
<tr>
<td>Departure/Approach</td>
<td>SFC - 18,000ft AAL / FL180 and within 50nm</td>
</tr>
<tr>
<td>Center</td>
<td>SFC - FL600 and within the white boundaries</td>
</tr>
</tbody>
</table></div><blockquote>
<p>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 &quot;on guard&quot; altitude/FL by 5000ft/FL50 respectively)</p>
</blockquote>
</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; and <strong class="red">must not</strong> be &quot;on guarded&quot; if on another active frequency.</p>
</section>
</section>


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</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.4-radar-written-and-practical-tests" class="documentation-content-link">7.4</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>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?

<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>The collision alert system will alert Controllers of airborne conflicts. If it is believed that the alert is valid then Controllers <strong class="red">must</strong> immediately issue a traffic alert and, if feasible, offer an immediate alternate course of action to reestablish IFR separate minima.</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Collision Alert</th>
<th>Criteria</th>
</tr>
</thead>
<tbody>
<tr>
<td>Red Target</td>
<td>&lt;1000ft and/or 3nm</td>
</tr>
<tr>
<td>Red Target and Audible Alarm</td>
<td>&lt;500ft and/or 1.5nm</td>
</tr>
</tbody>
</table></div></section>
</section>
<section id="6.2.5">
<h3><a class="header-anchor" href="#6.2.5">6.2.5</a></h3>
<section class="reference">
<p>Aircraft receiving a VFR service are expected to &quot;see and avoid&quot; while maintaining a <strong>MINIMUM</strong> of 500ft vertical separation with other aircraft.</p>
</section>
</section>
</section>


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

<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">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If there is no Departure Controller present at an airport, it is recommended that the Center or Approach Controller handles departing traffic (in addition to arrivals) provided their workload permits, this is particularly important if departure routes are likely to conflict with arrivals</p>
</dd>
</dl>
</dl>
</section>
</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.2-remarks-and-notams#4.2.1" class="documentation-content-link">4.2.1</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> 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. &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.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>


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>
<blockquote>
<p>When busy, Flight Following or other VFR services may be denied, however it is recommended you work the traffic when possible to provide vectors away from hazardous areas such as final and busy arrival/departure corridors</p>
</blockquote>
</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>
<blockquote>
<p>It is important to note that final separation from other aircraft, terrain, and IMC conditions falls on the pilot, not ATC</p>
</blockquote>
</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>Aircraft under Flight Following <strong class="red">must not</strong> be asked for their approach request as this is a VFR advisory service with the sole purpose of monitoring their flight and providing traffic alerts <strong>when able</strong>. However, if an aircraft is inbound to an airport that you are controlling and it is busy, you can consider some of the following options to manage your workload (in partnership with the Tower Controller as required):</p>
<ul>
<li>issue vectors for the approach sequence before being handed to the Tower Controller</li>
<li>switch the aircraft early so the Tower Controller can provide entry and sequence instructions</li>
<li>or place the aircraft on a leg of the pattern for the Tower Controller (similar to Radar Vectors) before handover</li>
</ul>
</section>
</section>
</section>


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>
<blockquote>
<p>Although Center airspace is defined by white boundaries on the map, it is important to note that any Center frequency has a radio emitter range of 400nm from the station selected. Controllers <strong class="red">should</strong> choose a facility frequency based off of a location that provides the most coverage for the primary airport(s) served. For example, if serving as Center for LAX and SAN it may be operationally advantageous to select the Center frequency from SNA</p>
</blockquote>
</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>  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. &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.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; <strong class="red">should</strong> 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.</p>
<blockquote>
<p>Aircraft descending via VNAV may be issued a violation after a warning if they are unresponsive <strong>AND</strong> conflict with others <em>(see <a href="/guide/atc-manual/1b.-violations/1b.2-violation-reasons#1b.2.1" class="documentation-content-link">1B.2.1</a> above)</em></p>
</blockquote>
</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>Aircraft at cruise may utilize the &quot;Resume Flight&quot; feature if all criteria has been met which means aircraft may unexpectedly return at cruise. Controllers are not responsible for a loss of separation for returning players, though efforts <strong class="red">should</strong> be made to reestablish the appropriate separation minima as soon as practical.</p>
<p><strong>Resume Flight Criteria:</strong></p>
<ul>
<li>Altitude &gt; 28,000ft MSL</li>
<li>Level flight</li>
<li>LNAV activated</li>
<li>Estimated time en-route (ETE) to destination &gt; 30 minutes</li>
<li>On flight plan track</li>
</ul>
</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>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.15-aircraft-speed#6.15.5" class="documentation-content-link">6.15.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.8">
<h3><a class="header-anchor" href="#6.6.8">6.6.8</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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Heading</th>
<th>Level</th>
</tr>
</thead>
<tbody>
<tr>
<td>360 - 179 degrees</td>
<td>ODD (e.g. FL330, FL350, FL370 etc)</td>
</tr>
<tr>
<td>180 - 359 degrees</td>
<td>EVEN (e.g. FL320, FL340, FL360 etc)</td>
</tr>
</tbody>
</table></div><p><strong>VFR</strong> - Odd or even levels with an extra 500ft added to all levels</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Heading</th>
<th>Level</th>
</tr>
</thead>
<tbody>
<tr>
<td>360 - 179 degrees</td>
<td>ODD (e.g. 1500, 3500, 5500, etc)</td>
</tr>
<tr>
<td>180 - 359 degrees</td>
<td>EVEN (e.g. 2500, 4500, 6500, etc)</td>
</tr>
</tbody>
</table></div></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.9">
<h3><a class="header-anchor" href="#6.6.9">6.6.9</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.9-approach#6.9.4" class="documentation-content-link">6.9.4</a> below)</em>.</p>
</section>
</section>
<section id="6.6.10">
<h3><a class="header-anchor" href="#6.6.10">6.6.10</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.2-remarks-and-notams#4.2.2" class="documentation-content-link">4.2.2</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.11">
<h3><a class="header-anchor" href="#6.6.11">6.6.11</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. If aircraft make other requests such as an approach request, Controllers <strong class="red">should</strong> respond with &quot;Continue as Filed, Expect the [approach type/runway] at [location]&quot; if the approach in use is known. The subsequent Approach Controller can still change the expected approach if required.</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>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 vectors and altitude assignments, and &quot;Continue as Filed&quot; and &quot;Altitude at your Discretion&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.13">
<h3><a class="header-anchor" href="#6.6.13">6.6.13</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 descent <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.14">
<h3><a class="header-anchor" href="#6.6.14">6.6.14</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

<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 &quot;direct&quot; 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

<section id="6.8-diversion">
<h1><a class="header-anchor" href="#6.8-diversion"><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  Diversion</h1>
<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>Aircraft may request to divert at any point throughout their flight while on an active radar frequency. ATC will have the ability to approve or deny this request, advising the aircraft to resume own navigation to the requested airport or to expect radar vectors.</p>
</section>
</section>
<section id="6.8.2">
<h3><a class="header-anchor" href="#6.8.2">6.8.2</a></h3>
<section class="reference">
<p>In congested or complex airspace, aircraft <strong class="red">should</strong> be given radar vectors to avoid unpredictable pilot actions whilst departing the area. Once clear aircraft can be told to resume own navigation or, workload permitting, Controllers may elect to provide radar services to the divert airport if within your area of jurisdiction.</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>Diversion denial <strong class="red">should</strong> be used <em>sparingly</em> and only to prevent diversion to an unsuitable airport or an airport at capacity.</p>
</section>
</section>
</section>


6.8 Diversion

<section id="6.9-approach">
<h1><a class="header-anchor" href="#6.9-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  Approach</h1>
<section class="reference">
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Local flights may be authorized if inbound at a position, altitude, and speed which does not disrupt the flow of traffic. Controllers <strong class="red">should</strong> attempt to accommodate inbound traffic, regardless of flight time, but may deny services if an unreasonable request is made that will diminish service for other aircraft</p>
</dd>
</dl>
</dl>
</section>
</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.9.1">
<h3><a class="header-anchor" href="#6.9.1">6.9.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>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.11-instrument-landing-system-(ils)-approach#6.11.5" class="documentation-content-link">6.11.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.9-approach#6.9.6" class="documentation-content-link">6.9.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.9.2">
<h3><a class="header-anchor" href="#6.9.2">6.9.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>ALL</strong> controllers involved to ensure a seamless service is provided.</p>
</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>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 &quot;Continue as Filed, Expect the [approach type/runway] at [location]&quot; 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.9.4">
<h3><a class="header-anchor" href="#6.9.4">6.9.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.9-approach#6.9.5" class="documentation-content-link">6.9.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.2-remarks-and-notams#4.2.2" class="documentation-content-link">4.2.2</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.9.5">
<h3><a class="header-anchor" href="#6.9.5">6.9.5</a></h3>
<section class="reference">
<p>At any time if you do issue a vector and/or altitude assignment and then want the aircraft to return to their flight plan, 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. 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.9.6">
<h3><a class="header-anchor" href="#6.9.6">6.9.6</a></h3>
<section class="reference">
<p>Approach charts can generally be found online by searching in any search engine for &quot;approach charts&quot; 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.</p>
</section>
</section>
<section id="6.9.7">
<h3><a class="header-anchor" href="#6.9.7">6.9.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.9.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.9.7.1 - KSFO FAA Chart" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.9.7.1 - KSFO FAA Chart</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.9.8">
<h3><a class="header-anchor" href="#6.9.8">6.9.8</a></h3>
<section class="reference">
<p>From the image <em>(see 6.9.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.9.9">
<h3><a class="header-anchor" href="#6.9.9">6.9.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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Prefix</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>D</td>
<td>VOR/DME Approach</td>
</tr>
<tr>
<td>H</td>
<td>RNAV (RNP) Approach</td>
</tr>
<tr>
<td>I</td>
<td>ILS Approach</td>
</tr>
<tr>
<td>J</td>
<td>GLS Approach</td>
</tr>
<tr>
<td>L</td>
<td>LOC (Localizer) Only Approach</td>
</tr>
<tr>
<td>N</td>
<td>NDB Approach</td>
</tr>
<tr>
<td>Q</td>
<td>Combination (two or more) of ILS/DME/VOR/NDB</td>
</tr>
<tr>
<td>R</td>
<td>RNAV (GPS) Approach</td>
</tr>
<tr>
<td>S</td>
<td>VOR Only Approach</td>
</tr>
<tr>
<td>X</td>
<td>LDA (Localizer Type Directional Aid) Approach</td>
</tr>
</tbody>
</table></div><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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Suffix</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>L</td>
<td>Left</td>
</tr>
<tr>
<td>R</td>
<td>Right</td>
</tr>
<tr>
<td>Y or Z</td>
<td>Differentiates between runways that utilize the same guidance</td>
</tr>
<tr>
<td>1, 2 etc.</td>
<td>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></div><p><strong>Example:</strong></p>
<p>H35LZ - RNAV (RNP) Approach for Runway 35L, Zulu Procedure</p>
</section>
</section>
</section>


6.9 Approach

<section id="6.10-global-positioning-system-(gps)-approach">
<h1><a class="header-anchor" href="#6.10-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.10  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.10.1">
<h3><a class="header-anchor" href="#6.10.1">6.10.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.10.2">
<h3><a class="header-anchor" href="#6.10.2">6.10.2</a></h3>
<section class="reference">
<p>When a pilot requests the GPS Approach and this is approved by the Controller (or if the GPS Approach is issued by the Controller), Controllers can expect aircraft to continue on their FPL (or the new FPL if they had a different approach programmed previously). 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.10.3">
<h3><a class="header-anchor" href="#6.10.3">6.10.3</a></h3>
<section class="reference">
<p>Once the aircraft is established (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.10.4">
<h3><a class="header-anchor" href="#6.10.4">6.10.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 aircraft is able to establish inbound on the GPS Approach. Once this is assured <strong>AND</strong> the observed track of the aircraft suggests a successful rejoin, the aircraft can be cleared for the GPS Approach (<em>see <a href="/guide/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach#6.10.2" class="documentation-content-link">6.10.2</a> above</em>).</p>
<p>*<em>Establish inbound is defined as a vector that will allow the aircraft to join the FPL or the Controller sending &quot;Continue as Filed&quot; to allow the aircraft to make their own way to the FPL</em></p>
</section>
</section>


6.10 Global Positioning System (GPS) Approach

<section id="6.11-instrument-landing-system-(ils)-approach">
<h1><a class="header-anchor" href="#6.11-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.11  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.11.1">
<h3><a class="header-anchor" href="#6.11.1">6.11.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.11.2">
<h3><a class="header-anchor" href="#6.11.2">6.11.2</a></h3>
<section class="reference">
<p>The cone at the end of a runway provides a <strong>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.11.3">
<h3><a class="header-anchor" href="#6.11.3">6.11.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.11-instrument-landing-system-(ils)-approach#6.11.5" class="documentation-content-link">6.11.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.11.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 27, 30 degree intercepts would be headings 240 and 300 as shown in the image below), 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, therefore 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-v2.jpeg" alt="Image 6.11.3.1 - Intercepting the localizer" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.11.3.1 - Intercepting the localizer</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.11.4">
<h3><a class="header-anchor" href="#6.11.4">6.11.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.11.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.11.4.1 - Intercepting the glideslope" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.11.4.1 - Intercepting the glideslope</figcaption>
        </figure>
      </p>
</section>
</section>
<section id="6.11.5">
<h3><a class="header-anchor" href="#6.11.5">6.11.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. If in doubt, Controllers <strong class="red">should</strong> opt for issuing vectors instead <em>(see <a href="/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.3" class="documentation-content-link">6.11.3</a> above)</em>.</p>
<p>*<em>reasonable is considered anything that resembles the usual intercept angle of approximately 30 degrees and/or allows aircraft to turn onto final without difficulty</em></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.11.6">
<h3><a class="header-anchor" href="#6.11.6">6.11.6</a></h3>
<section class="reference">
<p>As already mentioned <em>(see <a href="/guide/atc-manual/6.-radar/6.11-instrument-landing-system-(ils)-approach#6.11.2" class="documentation-content-link">6.11.2</a> above)</em>, the cone is a useful <strong>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 <strong class="red">must</strong> 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.11-instrument-landing-system-(ils)-approach#6.11.4" class="documentation-content-link">6.11.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 id="parallel-operations">
<h2><a class="header-anchor" href="#parallel-operations"><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> Parallel Operations</h2>
<section class="reference">
<blockquote>
<p>Reduced separation for Parallel Operations are only to be applied to aircraft that are on ILS or GPS approaches</p>
</blockquote>
</section>
<section id="6.11.7">
<h3><a class="header-anchor" href="#6.11.7">6.11.7</a></h3>
<section class="reference">
<p>Controllers <strong class="red">must</strong> ensure that aircraft continue to meet the IFR separation criteria <em>(see <a href="/guide/atc-manual/6.-radar/6.2-separation#6.2.2" class="documentation-content-link">6.2.2</a> above)</em> until they are established on the LOC or lateral guidance <em>(see <a href="/guide/atc-manual/6.-radar/6.14-handover-to-towerunicom#6.14.2" class="documentation-content-link">6.14.2</a> below)</em>. Once established, the IFR separation criteria no longer need to be applied between aircraft aligned with parallel runways.</p>
</section>
</section>
<section id="6.11.8">
<h3><a class="header-anchor" href="#6.11.8">6.11.8</a></h3>
<section class="reference">
<p>During parallel operations, lateral separation will always be lost first, therefore during the intercept, only vertical separation can be relied upon. If Controllers identify two or more aircraft that will end up being &quot;parallel&quot; during the final approach, there are two steps that <strong class="red">should</strong> be followed to ensure the separation requirement above is met:</p>
<ul>
<li>ensure that all aircraft involved are <strong>LEVEL</strong> at the altitude you intend on clearing them at for the approach, separated by 1000ft as a minimum (ideally before the base turn)</li>
<li>vector all aircraft so that they intercept the LOC or lateral guidance in-line with each other. This will mean that no aircraft has begun to descend on the G/S or vertical guidance (which could compromise vertical separation), until all the aircraft are established on the LOC or lateral guidance</li>
</ul>
<p><strong>Example:</strong></p>
<p>In the following image <em>(see 6.11.8.1 below)</em>, both aircraft are level for the intercept (one at 3000ft and the other at 4000ft). In the example on the left, the aircraft will be established on the LOC before the G/S is met. However in the example on the right, the aircraft have not intercepted the LOC in-line with each other and thus the aircraft that was at 4000ft has already met the G/S and begun their descent. Subsequently, the vertical separation is lost before both aircraft are established on the LOC!</p>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-parallel-ops.jpg" srcset="https://webcdn.infiniteflight.com/guide/manual/graphics/atc-parallel-ops@2x.jpg 2x, https://webcdn.infiniteflight.com/guide/manual/graphics/atc-parallel-ops@3x.jpg 3x" alt="Image 6.11.8.1 - Parallel Operations" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.11.8.1 - Parallel Operations</figcaption>
        </figure>
      </p>
</section>
</section>
</section>
</section>


6.11 Instrument Landing System (ILS) Approach

<section id="6.12-radar-vectors">
<h1><a class="header-anchor" href="#6.12-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.12  Radar Vectors</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>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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Aircraft Type</th>
<th>Pattern Altitude</th>
</tr>
</thead>
<tbody>
<tr>
<td>Prop</td>
<td>1000ft AAL</td>
</tr>
<tr>
<td>Jet</td>
<td>1500ft AAL</td>
</tr>
</tbody>
</table></div></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>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.12.3">
<h3><a class="header-anchor" href="#6.12.3">6.12.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.11-instrument-landing-system-(ils)-approach#6.11.4" class="documentation-content-link">6.11.4</a> above).</p>
</section>
</section>
</section>


6.12 Radar Vectors

<section id="6.13-visual-approach">
<h1><a class="header-anchor" href="#6.13-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.13  Visual Approach</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>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. To accommodate this, Visual Meteorological Conditions (VMC) <strong class="red">must</strong> exist for visual approaches to be allowed – for IF only purposes, this is a <strong>MINIMUM</strong> of 3 statute miles (approx. 5000 meters) visibility.</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>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.13.3">
<h3><a class="header-anchor" href="#6.13.3">6.13.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.13.4">
<h3><a class="header-anchor" href="#6.13.4">6.13.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.9-approach#6.9.6" class="documentation-content-link">6.9.6</a> above).</em></p>
</section>
</section>
<section id="6.13.5">
<h3><a class="header-anchor" href="#6.13.5">6.13.5</a></h3>
<section class="reference">
<p>The Visual Approach at JFK, New York (KJFK) onto RWY13L/R <em>(see image 6.13.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.13.5.1 - KJFK FAA Chart" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.13.5.1 - KJFK FAA Chart</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


6.13 Visual Approach

<section id="6.14-handover-to-tower%2Funicom">
<h1><a class="header-anchor" href="#6.14-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.14  Handover to Tower/Unicom</h1>
<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>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 &quot;intended approach path&quot; <strong>AND</strong> has an acceptable closure rate with the aircraft ahead.</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>The &quot;intended approach path&quot; for the GPS Approach, Radar Vectors and a Visual Approach are covered above <em>(see <a href="/guide/atc-manual/6.-radar/6.10-global-positioning-system-(gps)-approach#6.10.3" class="documentation-content-link">6.10.3</a>, <a href="/guide/atc-manual/6.-radar/6.12-radar-vectors#6.12.1" class="documentation-content-link">6.12.1</a> and <a href="/guide/atc-manual/6.-radar/6.13-visual-approach#6.13.3" class="documentation-content-link">6.13.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.14.2.1 below)</em>. Do not confuse aircraft being established on the LOC, with &quot;being in the cone&quot; – 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.14.2.1 - Radar intercept right vs wrong" class="documentation-image-lightbox-link" >
          <figcaption>Image 6.14.2.1 - Radar intercept right vs wrong</figcaption>
        </figure>
      </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>Radar Controllers <strong class="red">must</strong> ensure that the aircraft closure rate is &quot;acceptable&quot; and issue speed control if the desired separation cannot be maintained (e.g. if Aircraft A is at 180kts GS on final approach, and Aircraft B is intercepting at 250kts GS with only 3nm spacing, separation could be compromised and result in a go-around). Aircraft <strong class="red">should</strong> be kept on frequency until separation is assured, this may mean leaving the frequency change until very late!</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>To help with separation on final approach, the use of &quot;maintain XXXkts until X mile final&quot; <strong class="red">should</strong> be used by Radar Controllers when traffic levels are busy. Aircraft will be expected to reduce their IAS to the specified speed, maintain this until the specified distance has been met and then reduce to their final approach speed following this.</p>
</section>
</section>
</section>


6.14 Handover to Tower/Unicom

<section id="6.15-aircraft-speed">
<h1><a class="header-anchor" href="#6.15-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.15  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.15.1">
<h3><a class="header-anchor" href="#6.15.1">6.15.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.15.2">
<h3><a class="header-anchor" href="#6.15.2">6.15.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.15.3">
<h3><a class="header-anchor" href="#6.15.3">6.15.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 &quot;ball-park&quot; figures which can be used for reference. With the aircraft flying at 250kts IAS with no wind:</p>
<ul>
<li>3000ft ~ 260kts GS (+10)</li>
<li>6000ft ~ 270kts GS (+20)</li>
<li>9000ft ~ 290kts GS (+40)</li>
<li>12000ft ~ 300kts GS (+50)</li>
</ul>
</section>
</section>
<section id="6.15.4">
<h3><a class="header-anchor" href="#6.15.4">6.15.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.15-aircraft-speed#6.15.2" class="documentation-content-link">6.15.2</a> and <a href="/guide/atc-manual/6.-radar/6.15-aircraft-speed#6.15.3" class="documentation-content-link">6.15.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.15.5">
<h3><a class="header-anchor" href="#6.15.5">6.15.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>
<div class="table-wrapper"><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>Turbo Prop</td>
<td>e.g. TBM-930, Dash-8 Q400 etc</td>
<td>.51 - .53</td>
</tr>
<tr>
<td>Narrow Body Jet</td>
<td>e.g. CRJ, E-Jet, A320, B737 etc</td>
<td>.75 - .80</td>
</tr>
<tr>
<td>Wide Body Jet</td>
<td>e.g. A330, B777, MD-11 etc</td>
<td>.82 - .85</td>
</tr>
</tbody>
</table></div></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.15.6">
<h3><a class="header-anchor" href="#6.15.6">6.15.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 &quot;in-trail&quot; 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.15-aircraft-speed#6.15.7" class="documentation-content-link">6.15.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.15-aircraft-speed#6.15.8" class="documentation-content-link">6.15.8</a> below)</em></li>
</ul>
</section>
</section>
<section id="6.15.7">
<h3><a class="header-anchor" href="#6.15.7">6.15.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.15.8">
<h3><a class="header-anchor" href="#6.15.8">6.15.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.15.9">
<h3><a class="header-anchor" href="#6.15.9">6.15.9</a></h3>
<section class="reference">
<p>If aircraft have been holding, once they are cleared to leave the hold, speed is at their discretion unless they are subsequently assigned a speed command.</p>
</section>
</section>
<section id="6.15.10">
<h3><a class="header-anchor" href="#6.15.10">6.15.10</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. In this instance Controllers <strong class="red">should</strong> use the &quot;maintain XXXkts until X mile final&quot; option <em>(see <a href="/guide/atc-manual/6.-radar/6.14-handover-to-towerunicom#6.14.4" class="documentation-content-link">6.14.4</a> above)</em>.</p>
</section>
</section>


6.15 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">
<blockquote>
<p>It is the responsibility of the Recruit to ensure they meet the minimum requirements <strong>BEFORE</strong> applying. Failure to do so may invalidate the recruitment request and further progression may not be granted for a period of time</p>
</blockquote>
</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 written 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Definition</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>Recruit</td>
<td>Either a potential IFATC Controller that is in the Tower recruitment process, or a current IFATC Controller that is in the Radar recruitment process</td>
</tr>
<tr>
<td>Trainee</td>
<td>A Recruit that has a Trainer assigned and is in the training process</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Controller development is a key aspect within IFATC and so Controllers can seek training at any time for their current position if they feel they need help. Irrespective of being in training or not, Controllers can expect feedback during their time within the IFATC Team <strong class="red">and must utilize this to improve.</strong>.</p>
</blockquote>
</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 Trainees <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 time if they deem that the Trainee is not progressing or showing the dedication required.</strong> Trainees <strong class="red">must not</strong> have more than 1 training session in any 24 hour period.</p>
<blockquote>
<p>Although training sessions usually last approximately 30 minutes, they can vary in length, and therefore all attendees <strong class="red">must</strong> ensure that they are available for the entirety of the session</p>
</blockquote>
</section>
</section>
<section id="7.1.5">
<h3><a class="header-anchor" href="#7.1.5">7.1.5</a></h3>
<section class="reference">
<p>The <em>#training-time</em> Discord channels are used by Trainers to coordinate training sessions for a Trainee by announcing how many pilots are required to join, and in which channel. Controllers that wish to participate in these training sessions by flying can opt in to notifications by &quot;reacting&quot; to the relevant role in the <em>#role-assignments</em> Discord channel <em>(see <a href="/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.2" class="documentation-content-link">1A.1.2</a> above)</em>.</p>
<p>Any Controller that participates in training sessions is expected to fly in the most standard and predictable way possible to promote a good training environment. Speed and climb/descent rates <strong class="red">must</strong> remain appropriate for the terminal environment and Controllers <strong class="red">must</strong> react promptly/accurately to all ATC instructions. Disruptive or distracting pilot behaviour during training sessions is not tolerated and may result in being disconnected or reported. This will then be handled in the same way as other violations that are issued to IFATC <em>(see <a href="/guide/atc-manual/1a.-administration/1a.8-disciplinary-and-suspension-procedure#1a.8.2" class="documentation-content-link">1A.8.2</a> above)</em>.</p>
<p><strong>Recommended profile for commercial aircraft:</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Pattern</th>
<th>Speed</th>
</tr>
</thead>
<tbody>
<tr>
<td>Downwind</td>
<td>210 - 250 KIAS</td>
</tr>
<tr>
<td>Base</td>
<td>180 - 210 KIAS</td>
</tr>
<tr>
<td>Final</td>
<td>160 - 180 KIAS</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


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 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Document Name</th>
<th>Department</th>
</tr>
</thead>
<tbody>
<tr>
<td>Section 7A</td>
<td>Training</td>
</tr>
<tr>
<td>Section 7B</td>
<td>Testing</td>
</tr>
<tr>
<td>Section 7C</td>
<td>Recruitment</td>
</tr>
<tr>
<td>Section 7D</td>
<td>Supervisors</td>
</tr>
<tr>
<td>Section 7E</td>
<td>Appeals</td>
</tr>
</tbody>
</table></div></section>
</section>
</section>


7.2 IFATC Support Documentation

<section id="7.3-tower-written-and-practical-tests">
<h1><a class="header-anchor" href="#7.3-tower-written-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  Tower Written and Practical Tests</h1>
<section class="reference">
<blockquote>
<p>Recruits <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>
</blockquote>
</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, application instructions and the time limit for re-test if unsuccessful, are outlined on the IFC channel <a href="https://community.infiniteflight.com/t/atc-recruiting/843545" class="documentation-content-link">here</a>.</p>
<p>Controllers <strong class="red">must</strong> ensure they meet the minimum requirements <strong>BEFORE APPLYING</strong>.</p>
<p><a href="/joinatc" class="documentation-content-link button ui">APPLY NOW</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>Recruits 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 Recruits are committed to joining, training <strong class="red">must not</strong> be provided until the Recruit has passed the Tower Written Test as a <strong>MINIMUM</strong>.</p>
<blockquote>
<p>Returning members of IFATC are not required to complete the Tower Written Test if they submit an application to join within 1 year of leaving IFATC</p>
</blockquote>
</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><strong class="red">Tower Training Currently at Recruiter Discretion</strong></p>
<p>Following successful completion of the Tower Written Test, Recruits will be given the option to have training. If accepted, a Trainer will be in contact within 7 days to commence training with the Recruit. Trainees will be afforded 15 training sessions. Upon reaching 15 sessions, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach the skill level required for certification.</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 Tower 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 Tower Practical test:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Element</th>
<th>Proficiency Required*</th>
</tr>
</thead>
<tbody>
<tr>
<td>Pushback</td>
<td>Correctly identifies if the area is clear for the aircraft to initiate a pushback maneuver</td>
</tr>
<tr>
<td>Taxi</td>
<td>Effective ground management, runway selection (usually based on wind) and use of give way commands if appropriate</td>
</tr>
<tr>
<td>Departure</td>
<td>Use of LUAW or anticipated separation if appropriate, use of left/right traffic for aircraft remaining in the pattern</td>
</tr>
<tr>
<td><strong class="red">Aircraft Separation</strong></td>
<td>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>Runway  Usage</td>
<td>Effective use of both runways, and facilitating requests for runway changes</td>
</tr>
<tr>
<td>Pattern</td>
<td>Effective pattern management including pattern entries (if required), sequencing (if required) and clearances</td>
</tr>
<tr>
<td>Transition</td>
<td>Transition given that keeps inbound aircraft within tower airspace and clear of aircraft in the pattern</td>
</tr>
<tr>
<td>Go-Around</td>
<td>Proactive monitoring of separation between arrivals and use of go-arounds when required</td>
</tr>
<tr>
<td>Runway  Exit</td>
<td>Use of exit runway command with appropriate use of expedite (if required)</td>
</tr>
</tbody>
</table></div><p><strong class="red">Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed.</strong></p>
<p>*<em>The recruiter has the final say on the result of the test (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>


7.3 Tower Written and Practical Tests

<section id="7.4-radar-written-and-practical-tests">
<h1><a class="header-anchor" href="#7.4-radar-written-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.4 Radar Written and Practical Tests</h1>
<section class="reference">
<blockquote>
<p>Recruits <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>
</blockquote>
</section>
<section id="7.4.1">
<h3><a class="header-anchor" href="#7.4.1">7.4.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.-administration/1a.6-rank-structure#1a.6.4" class="documentation-content-link">1A.6.4</a> above).</em> 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 large Bravo or &quot;hub&quot; airports</p>
</li>
<li>
<p>Controlling during busy periods such as events, weekends and flashflights</p>
</li>
</ul>
<p>Controllers <strong class="red">must</strong> ensure they meet the minimum requirements <strong>BEFORE APPLYING</strong>.</p>
<p><a href="/joinatc" class="documentation-content-link button ui">APPLY NOW</a></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>After submitting an application, a Recruiter will conduct a review on the performance of the Controller. The requirements laid out within this section <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4.1" class="documentation-content-link">7.4.1</a> above)</em> will assist the Recruiter in gauging the Controller’s competency and suitability for the role. If the review is deemed successful, the Controller will be given the Radar Written Test. To ensure Recruits are ready, training <strong class="red">must not</strong> be provided until the Recruit has passed the Radar Written Test as a <strong>MINIMUM</strong>. 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.4.3">
<h3><a class="header-anchor" href="#7.4.3">7.4.3</a></h3>
<section class="reference">
<p>After successful completion of the Radar Written Test, the Recruit will be placed in the &quot;Training Waitlist&quot; ready for Trainer allocation. Training for the rank of Officer is mandatory and <strong class="red">must</strong> be successfully completed <strong>BEFORE</strong> the Radar Practical Test.</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>A Trainer will assign themselves to the Recruits application and Radar Training will then commence. The Radar Training program will consist of structured training sessions designed to teach basic radar fundamentals and techniques in a variety of airport environments. Trainees will be afforded 20 training sessions. Upon reaching 20 sessions, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach the skill level required for certification.</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>At an appropriate point during training, as decided by the Trainer; the Recruiter will issue the Radar Practical Test (and debrief as appropriate on the results - <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>). The Radar Practical Test will only be organized once the Trainer is satisfied that the Trainee is ready. Controlling on the Training Server is only permitted with the explicit permission of a Trainer - this will only be authorized if Trainees have met the requirements for upgrade to the rank of Officer <em>(see <a href="/guide/atc-manual/1a.-administration/1a.6-rank-structure#1a.6.4" class="documentation-content-link">1A.6.4</a> above)</em>, and have <strong>STARTED</strong> their Radar Training with a Trainer.</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>Whilst under Training, Trainees 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 Trainee has the Trainer’s permission, the use of the Discord <em>#training-time</em> channel is authorized to try and find Controllers that are free.</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>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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Element</th>
<th>Proficiency Required*</th>
</tr>
</thead>
<tbody>
<tr>
<td><strong class="red">Terrain  Separation</strong></td>
<td>Ensures that a minimum of 1000ft clearance is maintained with terrain at all times</td>
</tr>
<tr>
<td><strong class="red">Aircraft  Separation</strong></td>
<td>Ensures that a minimum of 3nm separation laterally or 1000ft separation vertically is maintained at all times</td>
</tr>
<tr>
<td>Efficiency</td>
<td>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>Approach Type</td>
<td>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>Go-Around</td>
<td>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></div><p><strong class="red">Automatic Failure: if proficiency is not met for elements marked in red, the test is automatically failed.</strong></p>
<p>*<em>The recruiter has the final say on the result of the test (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.4.8">
<h3><a class="header-anchor" href="#7.4.8">7.4.8</a></h3>
<section class="reference">
<p>Recruits that are successful in the Radar Practical Test will be promoted and placed in the Officer Check Ride phase <em>(see <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.6" class="documentation-content-link">1A.7.6</a> above)</em>.</p>
</section>
</section>
<section id="7.4.9">
<h3><a class="header-anchor" href="#7.4.9">7.4.9</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/radar-recruitment-v3.svg" alt="Image 7.4.9.1 - Radar Recruitment Flowchart" class="documentation-image-lightbox-link" >
          <figcaption>Image 7.4.9.1 - Radar Recruitment Flowchart</figcaption>
        </figure>
      </p>
</section>
</section>
</section>


7.4 Radar Written 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 Trainee (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>When new Trainers are added, they are 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).</p>
</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>When new Trainers are selected, they will be added to the following channels within Discord:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#leadership-hq</td>
<td>This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed</td>
</tr>
<tr>
<td>#tests</td>
<td>Recruiters will post in this channel with assignments and communication for a test</td>
</tr>
<tr>
<td>#tester [VC]</td>
<td>This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback <strong class="red">should</strong> still given in writing via the test topic</td>
</tr>
<tr>
<td>#test-time</td>
<td>Automatic notifications of upcoming tests will appear in this channel. Testers <strong class="red">must</strong> &quot;react&quot; to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the <em>#tests</em> Discord channel</td>
</tr>
<tr>
<td>#trainers</td>
<td>Main channel for coordination purposes within the Training Team</td>
</tr>
<tr>
<td>#training</td>
<td>Trainers will use this channel to create a topic for each scheduled training session. This is where training session objectives, assignments, and feedback will be given</td>
</tr>
<tr>
<td>#training-time</td>
<td>Trainers will post in this channel when they require pilots to join in for a training session. Pilots available for the session can &quot;react&quot; to the post to indicate attendance. If all available slots are already filled, Pilots <strong class="red">must not</strong> &quot;react&quot; to the request</td>
</tr>
<tr>
<td>#training [VC]</td>
<td>This can be used for participants as a general lounge or operationally to coordinate during an active training session. All feedback <strong class="red">should</strong> still given in writing via the training topic</td>
</tr>
</tbody>
</table></div><blockquote>
<p>All test session coordination <strong class="red">must</strong> take place in the designated channel as directed by the Recruiter</p>
</blockquote>
</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>The use of VCs for coordination between Trainers and their Trainees <strong class="red">must</strong> be conducted in accordance with Section 1A - Administration <em>(see <a href="/guide/atc-manual/1a.-administration/1a.1-discord-communication#1a.1.4" class="documentation-content-link">1A.1.4</a> and <a href="/guide/atc-manual/1a.-administration/1a.2-discord-rules#1a.2.2" class="documentation-content-link">1A.2.2</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. It is entirely voluntary and at the discretion of the Trainer and Trainee.</p>
</section>
</section>
</section>


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>Recruits <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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Trainee Type*</th>
<th>Location</th>
</tr>
</thead>
<tbody>
<tr>
<td>Tower</td>
<td><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>Radar</td>
<td>See <a href="/guide/atc-manual/7.-recruitment-and-training/7.4-radar-written-and-practical-tests#7.4-radar-theory-and-practical-tests" class="documentation-content-link">7.4</a> above</td>
</tr>
</tbody>
</table></div><p>*<em>Definitions of the different trainee types can be found here (see <a href="/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.3" class="documentation-content-link">7.1.3</a> above)</em></p>
</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>Trainees <strong class="red">should</strong> be claimed within a 7 day timeframe by accepting the request.</p>
</section>
</section>
<section id="summary">
<h2><a class="header-anchor" href="#summary"><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> Summary</h2>
<section class="reference"></section>
<section id="7a.2.3">
<h3><a class="header-anchor" href="#7a.2.3">7A.2.3</a></h3>
<section class="reference">
<p>Below if a summary that outlines the complete training process for a Tower or Radar Recruit:</p>
<details>
<summary><span class="details-marker">&nbsp;</span>Tower/Radar Recruit</summary><dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;ATC Recruits&quot; under &quot;IFATC&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Training Waitlist&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>All Recruits awaiting training will be listed, Recruits can be accepted as a Trainee by tapping the yellow button with a person/plus symbol that is inline with that Recruit (Trainers <strong class="red">should</strong> consider the timezone of the Recruit before accepting to ensure it is workable)</dd>
<dt>Step 5</dt>
<dd>To review the &quot;ATC Recruitment&quot; profile of a Trainee, return to the &quot;ATC Recruits&quot; page and then select &quot;In Training&quot; from the top navigation bar, and then tick the &quot;Show Only My Recruits&quot; tickbox to filter the list</dd>
<dt>Step 6</dt>
<dd>Tap the purple button with an arrow symbol that is inline with the Trainee that you would like to select</dd>
<dt>Step 7</dt>
<dd>This action will open up their &quot;ATC Recruitment&quot; profile</dd>
</dl>
<blockquote>
<p>For Radar Trainee's, Trainers <strong class="red">must</strong> inform the assigned Recruiter when the Trainee is ready for the Radar Practical Test</p>
</blockquote>
</details>
</section>
</section>
</section>
<section id="training-sessions">
<h2><a class="header-anchor" href="#training-sessions"><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> Training Sessions</h2>
<section class="reference"></section>
<section id="7a.2.4">
<h3><a class="header-anchor" href="#7a.2.4">7A.2.4</a></h3>
<section class="reference">
<p>Trainers <strong class="red">must</strong> utilize the &quot;Add Session&quot; function (and ensure &quot;Training Session&quot; is selected under &quot;Type&quot;) within the Recruit's ATC Recruitment profile before a scheduled session. This will send an automatic notification to the <em>#training-time</em> Discord channel for pilots. Once the specific channel to be used for that session is established, all subsequent coordination <strong class="red">should</strong> only be in that channel.</p>
<blockquote>
<p>The notification is sent 30 minutes before the start time unless the session was added with less than 30 minutes notice, in which case the notification will be immediate</p>
</blockquote>
</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>The maximum amount of training sessions allowed before a review of trainee performance are listed below:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Trainee Type</th>
<th>Maximum Training Sessions</th>
</tr>
</thead>
<tbody>
<tr>
<td>Tower</td>
<td>15</td>
</tr>
<tr>
<td>Radar</td>
<td>20</td>
</tr>
</tbody>
</table></div><p>Upon reaching the session limit, the training team will review overall progress to determine preparedness for testing, need for termination, or will allocate more sessions to reach skill level required for certification.</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</em> <em><a href="https://infiniteflight.com/guide/atc-manual/7.-recruitment-and-training/7.1-overview#7.1.4" class="documentation-content-link">7.1.4</a></em> <em>above)</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>
<section id="recommended-training-airports">
<h2><a class="header-anchor" href="#recommended-training-airports"><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> Recommended Training Airports</h2>
<section class="reference"></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 Tower Training, Trainers <strong class="red">should</strong> conduct training at airports with parallel and/or intersecting runways depending on the circumstances of their Trainees.</p>
</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>The following list 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-tower-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>
<details>
<summary><span class="details-marker">&nbsp;</span>Beginner Airports</summary><p><strong>Location: KSBP (elevation 212ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>07</td>
<td>GPS</td>
</tr>
<tr>
<td>11</td>
<td>ILS</td>
</tr>
<tr>
<td>25</td>
<td>GPS</td>
</tr>
<tr>
<td>29</td>
<td>GPS</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Minimal terrain in the vicinity of the airport (high terrain to the East but no factor). Single ILS Runway configuration</p>
</blockquote>
<p><strong>Location: NZAA (elevation 23ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>05R</td>
<td>ILS</td>
</tr>
<tr>
<td>23L</td>
<td>ILS</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Minimal terrain in the vicinity of the airport. Single ILS runway configuration, use of runway 23L recommended. Provides good training for an introduction into STAR management</p>
</blockquote>
</details>
<details>
<summary><span class="details-marker">&nbsp;</span>Intermediate Airports</summary><p><strong>Location: PHOG (elevation 53ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>02</td>
<td>ILS</td>
</tr>
<tr>
<td>05</td>
<td>GPS</td>
</tr>
<tr>
<td>20</td>
<td>GPS</td>
</tr>
<tr>
<td>23</td>
<td>GPS</td>
</tr>
</tbody>
</table></div><blockquote>
<p>High Terrain to the East and West of the airport. For RWY05 visual approaches it is recommended to bring traffic onto right downwind for RWY02 and feed in between RWY02 arrivals, or bring them directly onto a left downwind for RWY05. Trainee awareness on when to turn aircraft onto base/final to maintain terrain separation essential</p>
</blockquote>
<p><strong>Location: SKRG (elevation 7027ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>01</td>
<td>ILS</td>
</tr>
<tr>
<td>19</td>
<td>GPS</td>
</tr>
</tbody>
</table></div><p>Recommended STARs: KORB1A (North), OPME1A (Northwest), and MATR3A (South)</p>
<blockquote>
<p>High terrain on left/right downwind for RWY01. Provides good training for introduction to terrain awareness, high elevation airports and STAR management</p>
</blockquote>
<details>
<summary><span class="details-marker">&nbsp;</span>Advanced Airports</summary><p><strong>Location: LFMN (elevation 12ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>04L</td>
<td>ILS</td>
</tr>
<tr>
<td>04R</td>
<td>ILS</td>
</tr>
<tr>
<td>22L</td>
<td>GPS (recommend Visual only)</td>
</tr>
<tr>
<td>22R</td>
<td>GPS (recommend Visual only)</td>
</tr>
</tbody>
</table></div><p>Recommended STARs:  PERU6R (North-west), ABDI6R (West), and ABLA6R (West)</p>
<blockquote>
<p>High terrain to the North, North-east and West of the airport. Staggered approach technique recommended due to close proximity of parallel runways. Southwesterly runway configuration can be used for advanced visual approach training</p>
</blockquote>
<p><strong>Location: MMMX (elevation 7316ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>05L</td>
<td>GPS</td>
</tr>
<tr>
<td>05R</td>
<td>ILS</td>
</tr>
<tr>
<td>23L</td>
<td>ILS</td>
</tr>
<tr>
<td>23R</td>
<td>GPS</td>
</tr>
</tbody>
</table></div><p>Recommended STARs: AVSA1C (North), and TIKE1C (North-west)</p>
<blockquote>
<p>High terrain surrounds the airport. Short 6 mile final approach for RWY05R recommended, use left downwind and turn aircraft at San Mateo (SMO) VOR. Provides good training for aircraft speed management and high altitude airports</p>
</blockquote>
<p><strong>Location: OAKB (elevation 5876ft)</strong></p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>RWY</th>
<th>Approach Type</th>
</tr>
</thead>
<tbody>
<tr>
<td>11</td>
<td>GPS</td>
</tr>
<tr>
<td>29</td>
<td>ILS</td>
</tr>
</tbody>
</table></div><blockquote>
<p>High terrain on left/right downwind as well as multiple high-peaks throughout the region. Terrain awareness essential and provides good training opportunity for pre-session planning</p>
</blockquote>
</details>
</details>
<details>
<summary><span class="details-marker">&nbsp;</span>Other Airports</summary><ul>
<li>CYXE</li>
<li>KAUS</li>
<li>KEGE</li>
<li>KFWA</li>
<li>KGJT</li>
<li>KLSV</li>
<li>KONT</li>
<li>KPVU</li>
<li>KSNA</li>
<li>LEMG</li>
<li>MGTK</li>
<li>PHTO</li>
<li>SACO</li>
<li>SBGL</li>
<li>SCEL</li>
</ul>
</details>
</section>
</section>
</section>
<section id="training-complete-checklist">
<h2><a class="header-anchor" href="#training-complete-checklist"><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> Training Complete Checklist</h2>
<section class="reference"></section>
<section id="7a.2.9">
<h3><a class="header-anchor" href="#7a.2.9">7A.2.9</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>
<blockquote>
<p>If you leave this page, items that you have &quot;checked off&quot; will not be remembered. Do not navigate away or refresh this page until you have completed the checklist</p>
</blockquote>
<details>
<summary><span class="details-marker">&nbsp;</span>Tower Checklist</summary><ul class="task-list">
<li class="task-list-item"><input type="checkbox" id="if_task_check_0"><label for="if_task_check_0"> Weather / ATIS</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_1"><label for="if_task_check_1"> Pushback / Taxi Commands</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_2"><label for="if_task_check_2"> Ground Monitoring and Situational Awareness</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_3"><label for="if_task_check_3"> Gate Holds</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_4"><label for="if_task_check_4"> Runway Crossings</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_5"><label for="if_task_check_5"> Broadcast Commands</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_6"><label for="if_task_check_6"> Runway Assignments</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_7"><label for="if_task_check_7"> Usage of &quot;Expect Runway&quot;</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_8"><label for="if_task_check_8"> Take-Off / Landing / Option Clearances</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_9"><label for="if_task_check_9"> Separation Requirements / Go-Arounds</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_10"><label for="if_task_check_10"> Pattern / Transition Commands</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_11"><label for="if_task_check_11"> Sequencing</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_12"><label for="if_task_check_12"> Runway Exit Commands</label></li>
</ul>
</details>
<details>
<summary><span class="details-marker">&nbsp;</span>Radar Checklist</summary><ul class="task-list">
<li class="task-list-item"><input type="checkbox" id="if_task_check_13"><label for="if_task_check_13"> Radar User Interface</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_14"><label for="if_task_check_14"> ILS / GPS / Visual Approach</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_15"><label for="if_task_check_15"> Separation Requirements</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_16"><label for="if_task_check_16"> Flight Following [VFR]</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_17"><label for="if_task_check_17"> Check In [IFR]</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_18"><label for="if_task_check_18"> Radar Vectors / Patterns</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_19"><label for="if_task_check_19"> SIDs / STARs</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_20"><label for="if_task_check_20"> Center</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_21"><label for="if_task_check_21"> Speed Commands</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_22"><label for="if_task_check_22"> Airspace</label></li>
<li class="task-list-item"><input type="checkbox" id="if_task_check_23"><label for="if_task_check_23"> GA traffic management</label></li>
</ul>
</details>
</section>
</section>
</section>
</section>


7A.2 Training Structure

<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">
<blockquote>
<p>All Testers <strong class="red">must</strong> ensure that &quot;in-progress airports&quot; are hidden to ensure that taxiway networks are the same for both Testers and Recruits, thus avoiding confusion (Settings &gt; Hide in-progress airports)</p>
</blockquote>
</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 Recruits 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#tests</td>
<td>Recruiters will post in this channel with assignments and communication for a test</td>
</tr>
<tr>
<td>#tester [VC]</td>
<td>This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback <strong class="red">should</strong> still given in writing via the test topic</td>
</tr>
<tr>
<td>#test-time</td>
<td>Automatic notifications of upcoming tests will appear in this channel. Testers <strong class="red">must</strong> &quot;react&quot; to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the <em>#tests</em> Discord channel</td>
</tr>
</tbody>
</table></div><blockquote>
<p>All test session coordination <strong class="red">must</strong> take place in the designated thread as directed by the Recruiter</p>
</blockquote>
</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 Recruit before their Tower or Radar Practical Test (including the test location):</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Type</th>
<th>Minimum Notice Period</th>
</tr>
</thead>
<tbody>
<tr>
<td>Tower</td>
<td>No minimum</td>
</tr>
<tr>
<td>Radar</td>
<td>24 hours*</td>
</tr>
</tbody>
</table></div><p>*<em>The notice period may be reduced if the Recruiter and Recruit find a mutually acceptable time</em></p>
</section>
</section>
</section>


7B.1 Testing Process

<section id="7b.2-tower-testing">
<h1><a class="header-anchor" href="#7b.2-tower-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 Tower Testing</h1>
<section class="reference">
<blockquote>
<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.8" class="documentation-content-link">7A.2.8</a> above)</em></p>
</blockquote>
</section>
<section id="7b.2.1">
<h3><a class="header-anchor" href="#7b.2.1">7B.2.1</a></h3>
<section class="reference">
<p>The following scenario and locations disclosed on the Discord <strong class="red">must</strong> be used for the Tower Practical Test:</p>
<p><strong>Objective:</strong> Successfully operate ground and local frequency simultaneously, displaying the ability to efficiently handle ground conflicts utilizing core features like drag and push/taxi, blend airport inbounds and pattern traffic, and ensure separation throughout a variety of terminal operations</p>
<p><strong>Locations:</strong> See &quot;Post Guidelines&quot; in <em>#tests</em> Discord channel for approved test locations</p>
<p><strong>Maximum Aircraft Limit:</strong> 6</p>
<p><strong>Tester Instructions:</strong> Spawn in at your assigned location, await the Recruiter's instruction to begin, and once started, coordinate with other testers to create manageable conflicts from your respective starting point and ensure all test objectives are evaluated</p>
<p><strong>Tester Assignments:</strong>
T1 - Spawn at test site, create ground conflict, fly traffic patterns</p>
<p>T2 - Spawn at test site, create ground conflict, fly traffic patterns</p>
<p>T3 - Spawn at test site, create ground conflict, fly traffic patterns</p>
<p>T4 - Depart nearby airport, transition airspace, then call inbound for pattern work</p>
<p>T5 - Depart nearby airport and proceed inbound on instrument approach via flight plan for pattern work</p>
<p>T6 - Depart nearby airport and proceed inbound on instrument approach via flight for full stop</p>
</section>
</section>
</section>


7B.2 Tower 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">
<blockquote>
<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.8" class="documentation-content-link">7A.2.8</a> above)</em></p>
</blockquote>
</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 <strong class="red">should</strong> 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.4-radar-written-and-practical-tests#7.4.6" class="documentation-content-link">7.4.6</a> above)</em>.</li>
</ul>
<p>Testers <strong class="red">must</strong> 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>Only the pre-approved radar test sites <strong class="red">must</strong> be used for the Radar Practical Test, this includes for re-test if an Officer has been demoted (i.e. from Officer to Specialist) or for returning members. See &quot;Post Guidelines&quot; in <em>#tests</em> Discord channel for locations.</p>
</section>
</section>
</section>


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>
<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 testing program can be administered).</p>
</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 Recruit before their Tower or Radar Practical Test (including the test location):</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Test Type</th>
<th>Minimum Notice Period</th>
</tr>
</thead>
<tbody>
<tr>
<td>Tower</td>
<td>No minimum</td>
</tr>
<tr>
<td>Radar</td>
<td>24 hours*</td>
</tr>
</tbody>
</table></div><p>*<em>The notice period may be reduced if the Recruiter and Recruit find a mutually acceptable time</em></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>To ensure test transparency (and provided resources allow), Recruiters <strong class="red">should not</strong> administer the Tower or Radar Practical Test(s) for any Recruit that they have personally trained.</p>
</section>
</section>
<section id="7c.1.5">
<h3><a class="header-anchor" href="#7c.1.5">7C.1.5</a></h3>
<section class="reference">
<p>When new Recruiters are selected, they will be added to the following channels within Discord:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#leadership-hq</td>
<td>This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed</td>
</tr>
<tr>
<td>#recruiters</td>
<td>Main channel for coordination purposes within the Recruitment Team</td>
</tr>
<tr>
<td>#tests</td>
<td>Recruiters will post in this channel with assignments and communication for a test</td>
</tr>
<tr>
<td>#tester [VC]</td>
<td>This can be used for test participants as a general lounge or operationally to coordinate during an active test. All feedback <strong class="red">should</strong> still given in writing via the test topic</td>
</tr>
<tr>
<td>#test-time</td>
<td>Automatic notifications of upcoming tests will appear in this channel. Testers <strong class="red">must</strong> &quot;react&quot; to the post to confirm attendance. Further communication for a test will be in the specific thread for that test in the <em>#tests</em> Discord channel</td>
</tr>
<tr>
<td>#trainers</td>
<td>Main channel for coordination purposes within the Training Team</td>
</tr>
<tr>
<td>#training</td>
<td>Trainers will use this channel to create a topic for each scheduled training session. This is where training session objectives, assignments, and feedback will be given</td>
</tr>
<tr>
<td>#training-time</td>
<td>Trainers will post in this channel when they require pilots to join in for a training session. Pilots available for the session can &quot;react&quot; to the post to indicate attendance. If all available slots are already filled, Pilots <strong class="red">must not</strong> &quot;react&quot; to the request</td>
</tr>
<tr>
<td>#training [VC]</td>
<td>This can be used for participants as a general lounge or operationally to coordinate during an active training session. All feedback <strong class="red">should</strong> still given in writing via the training topic</td>
</tr>
</tbody>
</table></div><blockquote>
<p>All test session coordination <strong class="red">must</strong> take place in the designated thread as directed by the Recruiter</p>
</blockquote>
</section>
</section>
<section id="recruit-user-notes-and-activity-checks">
<h2><a class="header-anchor" href="#recruit-user-notes-and-activity-checks"><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> Recruit User Notes and Activity Checks</h2>
<section class="reference"></section>
<section id="7c.1.6">
<h3><a class="header-anchor" href="#7c.1.6">7C.1.6</a></h3>
<section class="reference">
<p>Recruiters <strong class="red">must</strong> add user notes for any performance related issues during the recruitment process (including contact attempts and ban/termination). This ensures that there is an accurate summary displayed if the need arose for a review or there was an appeal on any decision made. In addition, Recruiters <strong class="red">should</strong> do a comprehensive review of their list of Recruits at least once a month to check for activity. Both of these functions can be done by following the steps below:</p>
<dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;ATC Dashboard&quot; under &quot;IFATC&quot;</dd>
<dt>Step 3</dt>
<dd>Recruiters will be able to see a summary of their Recruits, and what stage they are each at</dd>
<dt>Step 4</dt>
<dd>Select the purple arrow that is inline with the name of the Recruit that you would like to look at, this will open their &quot;ATC&quot; profile</dd>
<dt>Step 5</dt>
<dd>The top navigation bar can then be used to navigate through the different tabs pertaining to that profile, and in particular, &quot;User Notes&quot; can be selected if a note is required</dd>
</dl>
<blockquote>
<p>Recruiters <strong class="red">must</strong> ensure they use the &quot;IFATC&quot; label for notes that are related to recruitment</p>
</blockquote>
<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 on the left of the screen and then search for the Recruit to access their profile</p>
</dd>
</dl>
</dl>
</section>
</section>
</section>
</section>
<section id="returning-ifatc-members">
<h2><a class="header-anchor" href="#returning-ifatc-members"><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> Returning IFATC Members</h2>
<section class="reference"></section>
<section id="7c.1.7">
<h3><a class="header-anchor" href="#7c.1.7">7C.1.7</a></h3>
<section class="reference">
<p>Returning members of IFATC <strong class="red">must</strong> apply in the same manner as all Recruits, with the normal Profile Verification completed to ensure they are still eligible to join.</p>
<blockquote>
<p>Returning members of IFATC are not required to complete the Tower Written Test if they submit an application to join within 1 year of leaving IFATC, therefore Recruiters may need to utilize the &quot;Skip to Training/Practical&quot; buttons as appropriate</p>
</blockquote>
</section>
</section>
</section>
<section id="additional-permissions-(violations)">
<h2><a class="header-anchor" href="#additional-permissions-(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> Additional Permissions (Violations)</h2>
<section class="reference"></section>
<section id="7c.1.8">
<h3><a class="header-anchor" href="#7c.1.8">7C.1.8</a></h3>
<section class="reference">
<p>Recruiters are granted the ability to issue Violations as a pilot whilst flying on the Infinite Flight Expert Server. Whilst moderating the server is a responsibility of Supervisors, it is recognised that Recruiters have the experience to also do this when they witness inappropriate behaviour.</p>
</section>
</section>
<section id="7c.1.9">
<h3><a class="header-anchor" href="#7c.1.9">7C.1.9</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="7c.1.10">
<h3><a class="header-anchor" href="#7c.1.10">7C.1.10</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="7c.1.11">
<h3><a class="header-anchor" href="#7c.1.11">7C.1.11</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>
</dl>
</section>
</section>
<section id="7c.1.12">
<h3><a class="header-anchor" href="#7c.1.12">7C.1.12</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.3-incident-resolution-procedure#1b.3.1" class="documentation-content-link">1B.3.1</a> above)</em>. It is strongly recommended that Recruiters have replays of their sessions on hand for that duration in order to deal with inquiries if required. Moderators, the Appeals Team and/or the IFATC Manager reserve the final say on the verdict of appeal(s).</p>
</section>
</section>
</section>


7C.1 Overview

<section id="7c.2-recruitment-process">
<h1><a class="header-anchor" href="#7c.2-recruitment-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> 7C.2 Recruitment Process</h1>
<section class="reference"></section>
<section id="summary">
<h2><a class="header-anchor" href="#summary"><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> Summary</h2>
<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 summaries below outline the complete recruitment process for a Tower and Radar Recruit:</p>
<details>
<summary><span class="details-marker">&nbsp;</span>Tower Recruit</summary><dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;ATC Recruits&quot; under &quot;IFATC&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Recruit Waitlist&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>Select the Recruit you would like to accept by tapping the orange &quot;Assign Yourself&quot; button (Recruiters <strong class="red">should</strong> consider the timezone of the Recruit before accepting to ensure it is workable)</dd>
</dl>
<blockquote>
<p>The Recruiter will then need to send the Recruit a PM (this can be done either via Discord or the IFC)</p>
</blockquote>
<dl>
<dt>Step 5</dt>
<dd>Select &quot;Written Test&quot; from the top navigation bar, and then tick the &quot;Show Only My Recruits&quot; tickbox to filter the list</dd>
<dt>Step 6</dt>
<dd>Tap the purple button with an arrow symbol that is inline with the Recruit that you would like to select</dd>
<dt>Step 7</dt>
<dd>This action will open up their &quot;ATC Recruitment&quot; profile. From here, tap &quot;Assign Written Test&quot;. Returning members of IFATC may not be required to complete the Written Test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.7" class="documentation-content-link">7C.1.7</a> below)</em></dd>
</dl>
<blockquote>
<p>This will automatically send another PM to the Recruit with instructions, a link, and unqiue test code to complete the Written Test</p>
</blockquote>
<dl>
<dt>Step 8</dt>
<dd>Once they have completed the Tower Written Test, they are instructed to message the Recruiter in the PM that has already been created with any questions they have. Provided they have passed, they can also request training if they wish to do so before continuing with the Tower Practical Test</dd>
</dl>
<blockquote>
<p>The test results as well as assigning training or the Tower Practical Test can be done from the &quot;ATC Recruitment&quot; profile</p>
</blockquote>
<dl>
<dt>Step 9</dt>
<dd>To access test results/request training/assign the practical, select &quot;Written Test&quot; from the top navigation bar, and then tick the &quot;Show Only My Recruits&quot; tickbox to filter the list</dd>
<dt>Step 10</dt>
<dd>Tap the purple button with an arrow symbol that is inline with the Recruit that you would like to select</dd>
<dt>Step 11</dt>
<dd>This action will open up there &quot;ATC Recruitment&quot; profile where these options are available</dd>
</dl>
</details>
<details>
<summary><span class="details-marker">&nbsp;</span>Radar Recruit</summary><blockquote>
<p>For the radar certification process, Recruiters are only required to:</p>
<ul>
<li>review the Recruit and to administer the Radar Written test before approving their training</li>
<li>and to administer the Radar Practical test (subject to Trainer approval)</li>
</ul>
<p>Recruiters <strong class="red">should not</strong> be required for other functions however reserve the right to terminate the radar process of a Trainee if necessary</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Go to the <a href="https://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and login using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 2</dt>
<dd>From the navigation bar on the left of the screen, select &quot;ATC Recruits&quot; under &quot;IFATC&quot;</dd>
<dt>Step 3</dt>
<dd>Select &quot;Recruit Waitlist&quot; from the top navigation bar</dd>
<dt>Step 4</dt>
<dd>Select the Recruit you would like to accept by tapping the orange &quot;Assign Yourself&quot; button (Recruiters <strong class="red">should</strong> consider the timezone of the Recruit before accepting to ensure it is workable)</dd>
<dt>Step 5</dt>
<dd>Conduct a review of the Recruit, and determine their suitability for the role</dd>
<dt>Step 6</dt>
<dd>Select &quot;Written Test&quot; from the top navigation bar, and then tick the &quot;Show Only My Recruits&quot; tickbox to filter the list</dd>
<dt>Step 7</dt>
<dd>Tap the purple button with an arrow symbol that is inline with the Recruit that you would like to select</dd>
<dt>Step 8</dt>
<dd>This action will open up their &quot;ATC Recruitment&quot; profile where the Radar Written Test can be assigned if they have been approved, otherwise they <strong class="red">must</strong> be informed of the agreed waiting time before their application will be reviewed again, and any areas for improvement</dd>
</dl>
<blockquote>
<p>The Recruiter will need to send a PM to the Trainee with instructions, a unique link (this is copied to your clipboard when tapping &quot;Assign Written Test&quot; and can just be pasted into the PM), and the test code <em>terrainpullup</em> to complete the Written Test</p>
</blockquote>
<dl>
<dt>Step 9</dt>
<dd>Once they have completed the Radar Written Test, they are instructed to message the Recruiter in the PM that has already been created with any questions they have. Provided they have passed, they can commence training and the Trainer will advise when they are ready to complete the Radar Practical Test</dd>
<dt>Step 11</dt>
<dd>To access test results/request training/assign the practical, select &quot;Written Test&quot; from the top navigation bar, and then tick the &quot;Show Only My Recruits&quot; tickbox to filter the list</dd>
<dt>Step 12</dt>
<dd>Tap the purple button with an arrow symbol that is inline with the Recruit that you would like to select</dd>
<dt>Step 13</dt>
<dd>This action will open up there &quot;ATC Recruitment&quot; profile where these options are available</dd>
</dl>
</details>
</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>Recruiters may terminate Recruits from the process if any of the expiries below are exceeded (a new application will need to be made if they still wish to join IFATC):</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Recruitment Stage</th>
<th>Expiry</th>
</tr>
</thead>
<tbody>
<tr>
<td>Initial message to the Recruit</td>
<td>30 days</td>
</tr>
<tr>
<td>Tower Written Test Code</td>
<td>24 hours</td>
</tr>
<tr>
<td>Passing* Tower Written Test</td>
<td>30 days</td>
</tr>
<tr>
<td>Discord Invite</td>
<td>24 hours (single use code)</td>
</tr>
</tbody>
</table></div><p>*<em>On passing the Tower Written Test, the Recruit has 30 days to make their first attempt at the Tower Practical Test (this can be extended at the Recruiter's discretion)</em></p>
</section>
</section>
</section>
</section>


7C.2 Recruitment Process

<section id="7c.3-verification">
<h1><a class="header-anchor" href="#7c.3-verification"><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 Verification</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>Once a Recruit has applied, an initial verification will automatically check if the application meets the minimum criteria, these are:</p>
<ul>
<li><strong>Trust Level 1</strong> on the IFC Forum and in good standing</li>
<li>Minimum stats to enter Expert Server (i.e. 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>
</ul>
<p>If these checks are successful, the application is then reviewed by a Moderator to check for any duplicate accounts and their IFC profile for a potential history that may deem them unfit to join. Once this is approved, the application will then be sent to the &quot;Review Waitlist&quot; for Recruiters to assign themselves.</p>
<blockquote>
<p>Although age cannot be requested, the minimum age is 14 (or as specified by <a href="https://support.discord.com/hc/en-us/articles/360040724612-Why-is-Discord-asking-for-my-birthday-" class="documentation-content-link">Discord</a> for their country). If a Recruits/Controllers age becomes known and is below the minimum, their application/membership of IFATC <strong class="red">must</strong> be terminated</p>
</blockquote>
</section>
</section>
</section>


7C.3 Verification

<section id="7c.4-written-test">
<h1><a class="header-anchor" href="#7c.4-written-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> 7C.4 Written Test</h1>
<section class="reference"></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"></section>
<section id="7c.4.1">
<h3><a class="header-anchor" href="#7c.4.1">7C.4.1</a></h3>
<section class="reference">
<p>Once a Recruit has taken the Tower Written 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 Tower Practical Test. The following wait periods are required if a Recruit does not pass:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Score</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td>00 - 49%</td>
<td>30 days</td>
</tr>
<tr>
<td>50 - 79%</td>
<td>14 days</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Three failed attempts at the Tower Written 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. Recruiters <strong class="red">must</strong> use the &quot;pause application&quot; function on the dashboard with a 90 day cooldown (and ensure that a user note is added with the reasoning)</p>
</blockquote>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Once a Recruit passes the Tower Written Test, they will become eligible for training if they want it. Recruiters <strong class="red">must</strong> ensure that Recruits are aware of this <em>(see <a href="/guide/atc-manual/7.-recruitment-and-training/7.3-tower-written-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 to join the IFATC Team <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>
<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"></section>
<section id="7c.4.2">
<h3><a class="header-anchor" href="#7c.4.2">7C.4.2</a></h3>
<section class="reference">
<p>Once a Recruit has taken the Radar Written 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 Radar Training and the Radar Practical Test (provided the Trainer has endorsed* this). The following wait periods are required if a Recruit does not pass:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Score</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td>00 - 40%</td>
<td>30 days</td>
</tr>
<tr>
<td>41 - 69%</td>
<td>14 days</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Three failed attempts at the Radar Written Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires)</p>
</blockquote>
<p>*<em>Once the Radar Written Test has been passed, the Recruit <strong class="red">must</strong> complete Radar Training and have the permission of the Trainer to move onto the Radar Practical Test</em></p>
</section>
</section>
</section>


7C.4 Written Test

<section id="7c.5-practical-test">
<h1><a class="header-anchor" href="#7c.5-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> 7C.5 Practical Test</h1>
<section class="reference"></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"></section>
<section id="7c.5.1">
<h3><a class="header-anchor" href="#7c.5.1">7C.5.1</a></h3>
<section class="reference">
<p>Once the Tower Written Test has been successfully passed, the Recruit can move onto the Tower 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-tower-testing#7b.2-tower-testing" class="documentation-content-link">7B.2</a> above)</em>. Recruiters <strong class="red">must</strong> ensure that the Recruit 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> below)</em>. If the Recruit has been trained by the Recruiter, another Recruiter <strong class="red">should</strong> administer the test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.4" class="documentation-content-link">7C.1.4</a> above)</em>.</p>
</section>
</section>
<section id="7c.5.2">
<h3><a class="header-anchor" href="#7c.5.2">7C.5.2</a></h3>
<section class="reference">
<p>Recruiters <strong class="red">must</strong> utilize the &quot;Add Session&quot; function (and ensure &quot;Practical Test&quot; is selected under &quot;Type&quot;) within the Recruit's ATC Recruitment profile before a scheduled test. This will send an automatic notification to the <em>#test-time</em> Discord channel for pilots. Once the specific channel to be used for that session is established, all subsequent coordination <strong class="red">should</strong> only be in that channel.</p>
<blockquote>
<p>The notification is sent 30 minutes before the start time unless the session was added with less than 30 minutes notice, in which case the notification will be immediate</p>
</blockquote>
</section>
</section>
<section id="7c.5.3">
<h3><a class="header-anchor" href="#7c.5.3">7C.5.3</a></h3>
<section class="reference">
<p>On completion of the Tower Practical Test, the Recruiter <strong class="red">must</strong> inform the Recruit of the result. The following wait periods are required if a Recruit does not pass:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Performance</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td>Poor</td>
<td>30 days</td>
</tr>
<tr>
<td>Marginal</td>
<td>14 days</td>
</tr>
<tr>
<td>Undetermined</td>
<td>Recruiter Discretion</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Three failed attempts at the Tower 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 &quot;User Notes&quot; <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.6" class="documentation-content-link">7C.1.6</a> above)</em>.</p>
</blockquote>
</section>
</section>
<section id="7c.5.4">
<h3><a class="header-anchor" href="#7c.5.4">7C.5.4</a></h3>
<section class="reference">
<p>Provided that both the Tower Written and Practical Tests have been passed, the Recruit can be invited to join the IFATC Team (this process is automatic when the &quot;Passed Practical&quot; button is tapped within the Recruits &quot;ATC Recruitment&quot; profile).</p>
</section>
</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"></section>
<section id="7c.5.5">
<h3><a class="header-anchor" href="#7c.5.5">7C.5.5</a></h3>
<section class="reference">
<p>Once the Radar Written Test and Radar Training have been successfully passed, the Recruit can move onto the Radar 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.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 Recruit 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>. If the Recruit has been trained by the Recruiter, another Recruiter <strong class="red">should</strong> administer the test <em>(see <a href="/guide/atc-manual/7c.-recruiters/7c.1-overview#7c.1.4" class="documentation-content-link">7C.1.4</a> above)</em>.</p>
<blockquote>
<p>If the Recruit is part of the <em>#testers</em> group, they <strong class="red">must</strong> be removed <strong>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>
</blockquote>
</section>
</section>
<section id="7c.5.6">
<h3><a class="header-anchor" href="#7c.5.6">7C.5.6</a></h3>
<section class="reference">
<p>Recruiters <strong class="red">must</strong> utilize the &quot;Add Session&quot; function (and ensure &quot;Practical Test&quot; is selected under &quot;Type&quot;) within the Recruit's ATC Recruitment profile before a scheduled test. This will send an automatic notification to the <em>#test-time</em> Discord channel for pilots. Once the specific channel to be used for that session is established, all subsequent coordination <strong class="red">should</strong> only be in that channel.</p>
<blockquote>
<p>The notification is sent 30 minutes before the start time unless the session was added with less than 30 minutes notice, in which case the notification will be immediate</p>
</blockquote>
</section>
</section>
<section id="7c.5.7">
<h3><a class="header-anchor" href="#7c.5.7">7C.5.7</a></h3>
<section class="reference">
<p>On completion of the Radar Practical test, the Recruiter <strong class="red">must</strong> inform the Recruit of the result. The following wait periods are required if a Recruit does not pass:</p>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Performance</th>
<th>Wait Period before Retake</th>
</tr>
</thead>
<tbody>
<tr>
<td>Poor</td>
<td>30 days</td>
</tr>
<tr>
<td>Marginal</td>
<td>14 days</td>
</tr>
<tr>
<td>Undetermined</td>
<td>Recruiter Discretion</td>
</tr>
</tbody>
</table></div><blockquote>
<p>Three failed attempts at the Radar Practical Test results in a 90 day wait period (although restarting the process is not required and can continue after the wait period expires). Recruiters <strong class="red">must</strong> use the &quot;pause application&quot; function on the dashboard with a 90 day cooldown (and ensure that a user note is added with the reasoning)</p>
</blockquote>
</section>
</section>
<section id="7c.5.8">
<h3><a class="header-anchor" href="#7c.5.8">7C.5.8</a></h3>
<section class="reference">
<p>Provided that the Radar Written Test, Radar Training and Radar Practical Test have been passed, the Recruit can be promoted to the rank of Officer (this process is automatic when the &quot;Passed Practical&quot; button is tapped within the Recruits &quot;ATC Recruitment&quot; profile).</p>
</section>
</section>
</section>
</section>


7C.5 Practical Test

<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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#leadership-hq</td>
<td>This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed</td>
</tr>
<tr>
<td>#supervisors</td>
<td>This channel is used to facilitate communications between all Supervisors for any purpose deemed necessary</td>
</tr>
</tbody>
</table></div></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>
<blockquote>
<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>
</blockquote>
</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.-administration/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

<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.</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>
</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.3-incident-resolution-procedure#1b.3.1" class="documentation-content-link">1B.3.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 if required. Moderators, the Appeals Team and/or the IFATC Manager reserve the final say on the verdict of appeal(s).</p>
</section>
</section>
</section>


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/1a.-administration/1a.7-check-ride-process#1a.7-check-ride-process" class="documentation-content-link">1A.7</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>#supervisor</em> Discord channel and click the &quot;Give Feedback&quot; button provided by the Infinite Flight Bot for the Controller you wish to provide feedback for</dd>
<dt>Step 2</dt>
<dd>This will open the &quot;Give Checkride Feedback&quot; text box where any feedback can be added</dd>
<dt>Step 3</dt>
<dd>Once finished, click the &quot;Submit&quot; button</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/1a.-administration/1a.7-check-ride-process#1a.7.6" class="documentation-content-link">1A.7.6</a> and <a href="/guide/atc-manual/1a.-administration/1a.7-check-ride-process#1a.7.8" class="documentation-content-link">1A.7.8</a> above)</em>. A decision will be made and repeated if necessary.</p>
</section>
</section>
<section id="7d.3.4">
<h3><a class="header-anchor" href="#7d.3.4">7D.3.4</a></h3>
<section class="reference">
<p>The <em>/checkrides</em> command can be used in the <em>#supervisors</em> channel to see which Controllers are currently in their Check Ride phase.</p>
</section>
</section>
</section>


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).</p>
</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 giving feedback, Supervisors <strong class="red">should</strong> follow the below points to ensure that it is proportionate, valid and in keeping with the team ethos:</p>
<ul>
<li>Only one person to give the feedback to the individual, this can be collated first in the <em>#supervisors</em> Discord channel</li>
<li>All feedback to be given via PM unless the feedback is targeted and will immediately alleviate* the current situation that is happening under their control</li>
<li>Know the difference between technique and rule</li>
<li>Try to ask open questions (How do you feel your session went? Was there anything you would do differently next time?)</li>
<li>Always reenforce the good points</li>
<li>Before sending feedback, ask yourself if it really is needed? Will this feedback achieve the desired affect?</li>
</ul>
<p>*<em>E.g. you see that the Controller's base turn is starting to slip further downwind and terrain is a factor, you suggest in the #controllers Discord channel that the Controller sends [callsign] further upwind before turning them downwind to help build space that can then be used to bring the base turn back. This is an example of targeted advice that is being sent to try and alleviate the current situation</em></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 <strong class="red">must</strong> leave other sensitive requests to the appropriate groups (i.e. violations to the Appeals Team, recruiting questions to Recruiters and training questions 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;user 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. Notes can be added by following the steps below:</p>
<blockquote>
<p>An absence of negative notes indicates a good track record</p>
</blockquote>
<dl>
<dt>Step 1</dt>
<dd>Open the IFATC Discord and begin to type <em>/usernote</em></dd>
<dt>Step 2</dt>
<dd>The &quot;Commands Matching&quot; list will appear, select <em>/usernote</em> from this list</dd>
<dt>Step 3</dt>
<dd>Start to type the username in the &quot;Member&quot; box</dd>
<dt>Step 4</dt>
<dd>The &quot;Members&quot; list will appear, select the username from this list</dd>
<dt>Step 5</dt>
<dd>Populate the note box with the note that you would like to add to their record and then press &quot;enter/send&quot;</dd>
</dl>
</section>
</section>
</section>


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-guide/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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Channel</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>#appeals</td>
<td>This is where the appeals team can discuss appeals, procedures, and request additional input from Staff and IFC Moderators</td>
</tr>
<tr>
<td>#leadership-hq</td>
<td>This channel will be used as a read only announcement channel for all leadership roles. Conversation prompts will be hosted in threads, when needed</td>
</tr>
</tbody>
</table></div></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>
<blockquote>
<p>User replays with session times totaling 50 hours or more <strong class="red">should</strong> be ignored and the User advised to perform regular refreshes of the app. Extreme app use is discouraged and may result in technical errors which cannot be reproduced</p>
</blockquote>
</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>
<ul>
<li>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</li>
<li>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</li>
<li>Appeals Team members <strong class="red">must not</strong> discuss appeals or share User replays outside of the appropriate channels to maintain User confidentiality</li>
<li>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</li>
<li>Members <strong class="red">must</strong> make an effort to remain active to keep each member’s commitment low</li>
</ul>
</section>
</section>
</section>


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">
<blockquote>
<p>All Violations involving current IFATC <strong class="red">must</strong> be handled by the IFATC Manager/Moderators <em>(see <a href="/guide/atc-manual/1a.-administration/1a.8-disciplinary-and-suspension-procedure#1a.8.2" class="documentation-content-link">1A.8.2</a> above)</em></p>
</blockquote>
</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 template 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>
<blockquote>
<p>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</p>
</blockquote>
<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 appeal however, at the discretion of the Appeals Team, they can still be reviewed</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>
<blockquote>
<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>
</blockquote>
</details>
<blockquote>
<p>If the Violation is upheld and the User is a member of IFATC. The IFATC Manager or Moderators <strong class="red">must</strong> be informed so that further disciplinary action can be carried out <em>(see <a href="/guide/atc-manual/1a.-administration/1a.8-disciplinary-and-suspension-procedure#1a.8.2" class="documentation-content-link">1A.8.2</a> above)</em></p>
</blockquote>
</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>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></dd>
<dt>Step 2</dt>
<dd>&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)</dd>
<dt>Step 3</dt>
<dd>Select &quot;Archive&quot; at the bottom of the PM</dd>
<dt>Step 4</dt>
<dd>The message will be sent to the Appeals Archive where it can be accessed in the future if needed</dd>
</dl>
<blockquote>
<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>
</blockquote>
</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>
<blockquote>
<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>
</blockquote>
</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>Access the Appeals Administrator Dashboard (link is provided in the <em>#appeals</em> Discord channel)</dd>
<dt>Step 2</dt>
<dd>Select &quot;Users&quot; from the navigation bar and then enter the User information to search for their profile</dd>
<dt>Step 3</dt>
<dd>To access the Users Profile, select the arrow under &quot;Profile&quot; that is in-line with their User information</dd>
<dt>Step 4</dt>
<dd>Select &quot;Violations&quot; from the navigation bar and then scroll to find the Violation you would like to reverse</dd>
<dt>Step 5</dt>
<dd>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>).</dd>
</dl>
<blockquote>
<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>
</blockquote>
</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 templates 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>
<div class="table-wrapper"><table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Template</th>
<th>Recommended Usage</th>
</tr>
</thead>
<tbody>
<tr>
<td>Appeals - 1st - Replay Request</td>
<td>If no replay file has been sent</td>
</tr>
<tr>
<td>Appeals - 2nd - Correct Template Reply</td>
<td>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>Appeals - Sending Options Only</td>
<td>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>Appeals - Violation Removal</td>
<td>If the violation has been removed</td>
</tr>
</tbody>
</table></div><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;Insert Template&quot; and then scroll to find the reply you wish to use (on PC this will appear on the right hand side of the message screen)</dd>
<dt>Step 8</dt>
<dd>Tap the corresponding &quot;clipboard&quot; icon to move the message into the reply window, this can then be edited (if required) before being sent (by clicking &quot;reply&quot;)</dd>
</dl>
</section>
</section>
</section>


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://dashboard.infiniteflight.com" class="documentation-content-link">Dashboard</a> and logging in using your IFC credentials (if required, login is normally automatic)</dd>
<dt>Step 4</dt>
<dd>From the navigation bar on the left of the screen, select &quot;Users&quot; if not already selected</dd>
<dt>Step 5</dt>
<dd>Use the search function to find either the Discord or IFC username</dd>
<dt>Step 6</dt>
<dd>Select the arrow on the right of the screen that is inline with the name of the User that you would like to look at, this will open their profile</dd>
<dt>Step 7</dt>
<dd>The top navigation bar can then be used to navigate through the different tabs pertaining to that profile, and in particular, &quot;User Notes&quot; can be selected if a note is required</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>When adding notes, it is recommended to start with &quot;From Appeals:&quot; so that it is clear who has written the note</dd>
</dl>
<dl>
<dt>Step 8</dt>
<dd>Click &quot;Add Note&quot; to save it</dd>
</dl>
<blockquote>
<p>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 be escalated by bringing it to the attention of an IFC Moderator</p>
</blockquote>
</section>
</section>
</section>


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 Guide

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

Want to control the aircraft of Infinite Flight? Learn about the user interface with our ATC Guide before moving onto our ATC Manual to learn the rules of controlling!

ATC Guide

Whether you're a qualified controller or just beginning your journey, the ATC Manual will be your rulebook 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.

Developer Reference

Help the airports of Infinite Flight come to life with both 2D and 3D editing. This manual is the rulebook on how to use our Scenery Editor within Infinite Flight.

Scenery Editor Manual

Help the airports of Infinite Flight come to life with both 2D and 3D editing. This manual is the rulebook on how to use our Scenario Editor within Infinite Flight.