<section id="pushback">
<h1><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</h1>
<section class="reference">
<p>A pushback is a maneuver that can be used by aircraft to position from their parked position, onto a taxiway ready to taxi.</p>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>General Aviation (GA) and military aircraft (with the exception of the C-130) are not able to perform a pushback maneuver</p>
</dd>
</dl>
</dl>
<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/558244099" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft requests pushback, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>If it is clear, tap &quot;Pushback Approved &gt; Send&quot;. In all other cases tap &quot;Hold Position&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Set a reminder by tapping the aircraft on the map followed by &quot;Set Reminder&quot;. The aircraft and their flight progress strip will flash green when the timer is up!</p>
</dd>
</dl>
</section>
</dl>
</section>
<section id="flow-control">
<h2><a class="header-anchor" href="#flow-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> Flow Control</h2>
<section class="reference">
<p>Flow Control is a technique used by Controllers to limit the amount of aircraft inbound to a particular destination. This is usually done by holding aircraft at the gate to help stagger departures.</p>
<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/560106119" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft requests pushback, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>If &quot;Flow Control&quot; is in effect, tap the aircraft on the map followed by &quot;Show Information&quot;</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>From the information tab, check the filed destination</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>If a large amount of aircraft are inbound to this destination, you can stagger departures by holding aircraft at the gate</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>Access the communication menu and then tap &quot;Hold Position&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Set a reminder by tapping the aircraft on the map followed by &quot;Set Reminder&quot;. The aircraft and their flight progress strip will flash green when the timer is up!</p>
</dd>
</dl>
</dl>
</section>
</section>


Pushback

<section id="taxi">
<h1><a class="header-anchor" href="#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> Taxi</h1>
<section class="reference">
<p>Taxiing is when aircraft maneuver on the ground under their own power. This is usually to get from the gate to the departure runway, or after landing to get from the runway to the gate.</p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft requests taxi, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Tap &quot;Taxi to &gt; [select RWY]&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Dependent on traffic, a taxi command may need to be immediately followed with progressive taxi or give way instructions</p>
</dd>
</dl>
</dl>
</section>
</section>
<section id="progressive-taxi-and-give-way">
<h2><a class="header-anchor" href="#progressive-taxi-and-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> Progressive Taxi and Give Way</h2>
<section class="reference">
<p>As well as using the normal taxi commands, progressive taxi and give way instructions can be useful to help assist the Controller with ground management, particularly with one way systems, potential conflicts, and intersection departures.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>&quot;Taxi to RWYXX, contact tower when ready&quot; and &quot;Taxi to parking&quot; are the default commands that <strong class="red">must</strong> be used by Controllers for the purposes of departing/arriving aircraft. <a href="/guide/atc-manual/2.-ground/2.2-taxi-and-use-of-give-way#2.2.2" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/560117809" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<p><strong>Give Way Commands</strong></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>In the event of a potential conflict, tap the aircraft that you want to take corrective action. You can do this by tapping the aircraft on the map (and then &quot;Other Message&quot;), or by tapping their flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>This will bring up the communication menu, tap &quot;Give way to &gt; [select appropriate reference to other aircraft]&quot;</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Once the conflict is clear, the aircraft giving way can continue as cleared</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Try to be proactive rather than reactive! Predict ground movement and potential conflicts and use the tools available to solve the problem early on, this will help you stay ahead and maintain a low workload!</p>
</dd>
</dl>
</section>
</dl>
<p><strong>Progressive Taxi Commands</strong></p>
<dl>
<dt>Step 1</dt>
<dd>In the event that progressive taxi instructions are required (e.g. complicated layout or potential conflict), tap the aircraft that you want to direct. You can do this by tapping the aircraft on the map (and then &quot;Other Message&quot;), or by tapping their flight progress strip</dd>
<dt>Step 2</dt>
<dd>This will bring up the communication menu. After issuing the normal taxi clearance (i.e. taxi to RWYXX or taxi to parking), tap &quot;Progressive Taxi &gt; [select appropriate directions]&quot;</dd>
<dt>Step 3</dt>
<dd>Once you have completed the progressive taxi instructions, tap &quot;Progressive Taxi &gt; Continue taxi at your discretion&quot; to allow the aircraft to continue on their own</dd>
</dl>
</section>


Taxi

<section id="separation">
<h1><a class="header-anchor" href="#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> Separation</h1>
<section class="reference">
<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>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>The table below outlines the separation requirements that <strong class="red">must</strong> be applied to <strong class="red">ALL</strong> aircraft:</p>
</dd>
</dl>
</dl>
<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> have vacated the runway 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>Intersecting</td>
<td>Arriving/departing aircraft <strong class="red">must</strong> be beyond the runway intersection prior to a departure beginning it's takeoff roll or an arrival crossing the threshold on an intersecting runway. 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>
<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/574512422" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
</section>
</section>


Separation

<section id="departures">
<h1><a class="header-anchor" href="#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> Departures</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/560144457" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
</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">
<p>The use of &quot;hold short&quot; is primarily used with departing traffic to ensure that they do not enter the runway until cleared to do so.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>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. <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.1" class="documentation-content-link">More info?</a></dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>When an aircraft calls ready for departure, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</dd>
<dt>Step 2</dt>
<dd>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 3</dt>
<dd>If it is not appropriate to issue a take-off or LUAW clearance, tap &quot;Hold Short &gt; [select RWY]&quot; instead</dd>
</dl>
</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">
<p>When there are multiple aircraft queuing for departure, it can be useful to provide sequencing information so that aircraft know what order to expect departure in.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>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. <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.2" class="documentation-content-link">More info?</a></dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>To let aircraft know their departure number, either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 2</dt>
<dd>Tap &quot;Departure Sequence &gt; [select departure number]&quot;</dd>
</dl>
</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">
<p>With one departure rolling and another aircraft holding short of the runway, sometimes anticipated separation may be better and you can just clear the second aircraft for take-off if you know the first aircraft will be airborne by the time they start rolling. But if you are in doubt, or if you have just had an aircraft land, then using the &quot;Line Up &amp; Wait&quot; (LUAW) command may be more appropriate.</p>
<p>The use of this command instructs the aircraft holding short to taxi onto the runway and line up ready for departure meaning that as soon as separation criteria is satisfied, you can clear them for take-off.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>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. <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.3" class="documentation-content-link">More info?</a></dd>
</dl>
<dl>
<dt>Step 1</dt>
<dd>When an aircraft calls ready for departure, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</dd>
<dt>Step 2</dt>
<dd>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 3</dt>
<dd>If you want to issue a LUAW command tap &quot;Line Up &amp; Wait &gt; [select RWY]&quot;</dd>
</dl>
</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">
<p>A back-taxi instruction will be required if the aircraft is unable to access full length for departure or when landing aircraft have passed the last available runway exit.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>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. <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.4" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/560560579" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>When an aircraft calls ready for departure, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</dd>
<dt>Step 2</dt>
<dd>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 3</dt>
<dd>If you want to issue a LUAW command tap &quot;Back Taxi &gt; [select RWY] &gt; [select Contact Ground when off the Runway / LUAW] &gt; [select Send / Expedite]&quot;</dd>
</dl>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Options</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>&quot;Contact Ground when off the Runway&quot;</td>
<td>Once the aircraft has completed the back-taxi and vacated the runway, they can contact Ground</td>
</tr>
<tr>
<td>&quot;Line Up &amp; Wait&quot;</td>
<td>Once the aircraft has completed the back-taxi they can do a 180 turn on the runway, ready for departure</td>
</tr>
<tr>
<td>&quot;Send&quot;</td>
<td>Sends the back-taxi instruction</td>
</tr>
<tr>
<td>&quot;Expedite&quot;</td>
<td>Sends the back-taxi instruction but asks the aircraft to expedite (usually due to arrival traffic)</td>
</tr>
</tbody>
</table>
</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">
<p>Utilizing multiple entry points to the runway for departure will give you the flexibility to decide on the departure sequence. The table below gives some examples of when this can be useful:</p>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Consider</th>
<th>Why</th>
</tr>
</thead>
<tbody>
<tr>
<td>Aircraft Flight Plan</td>
<td>If multiple departures are about to be cleared with no arrivals in-between, choose aircraft that have flight plans that depart in different directions to help ease airspace congestion (e.g. one departure has a flight plan filed that departs to the north and the other to the south)</td>
</tr>
<tr>
<td>Aircraft Size</td>
<td>If the gap between two arrivals looks quite close, perhaps consider choosing an aircraft that you know will be able to depart quicker (e.g. a fighter jet instead of a large commercial aircraft)</td>
</tr>
<tr>
<td>Aircraft position</td>
<td>You may be able to depart aircraft quicker if you line up two aircraft at the same time</td>
</tr>
</tbody>
</table>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>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. <a href="/guide/atc-manual/3.-tower/3.2-departures#3.2.5" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
</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">
<dl>
<dt>Step 1</dt>
<dd>When an aircraft calls ready for departure, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</dd>
<dt>Step 2</dt>
<dd>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 3</dt>
<dd>If you want to issue a take-off clearance, tap &quot;Cleared for Takeoff &gt; [select option]&quot;</dd>
</dl>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Options</th>
<th>When to Use</th>
</tr>
</thead>
<tbody>
<tr>
<td>&quot;Send&quot;</td>
<td>In most cases when you want to just send a normal take-off clearance</td>
</tr>
<tr>
<td>&quot;Straight Out (Altitude)&quot;</td>
<td>When &quot;Straight Out Dept.&quot; is being broadcast in the current ATIS. Aircraft will fly runway heading until they have reached the altitude specified AND no conflict exists</td>
</tr>
<tr>
<td>&quot;Request Immediate Takeoff&quot;</td>
<td>Recommended when separation is likely to be lost between the departing aircraft and arrival traffic on final (usually within 2nm)</td>
</tr>
</tbody>
</table>
</section>
</section>


Departures

<section id="inbounds">
<h1><a class="header-anchor" href="#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> Inbounds</h1>
<section class="reference"></section>
<section id="pattern-entry%2C-sequence-and-clearance">
<h2><a class="header-anchor" href="#pattern-entry%2C-sequence-and-clearance"><svg class="permalink" viewBox="0 0 16 16" version="1.1" width="16" height="16" aria-hidden="true"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a> Pattern Entry, Sequence and Clearance</h2>
<section class="reference">
<p>In Infinite Flight the pattern altitude is 1000ft AAL (above aerodrome level) for prop aircraft, and 1500ft AAL for jet aircraft. It consists of multiple legs, each being joined by a 90 degree turn, and these are shown in the image below:</p>
<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="The Traffic Pattern" class="documentation-image-lightbox-link" >
          <figcaption>The Traffic Pattern</figcaption>
        </figure>
      </p>
<p>Pattern entries are key in making sure that pilots know where to join the pattern, and by doing so, promotes airport efficiency and good traffic management. Controllers can do this by imagining that each pattern leg continues to extend out, away from the airport. The leg that intersects with the aircraft's flight path is usually the best option but Controllers may need to change this based on current traffic.</p>
<p>The art of sequencing allows controllers to let pilots know who they are supposed to be following and is not just to be used with aircraft in the pattern. All inbounds need to be told who they are following, unless of course they aren't following anyone! For effective sequencing, it requires:</p>
<ul>
<li>both the controller and the pilot to have a knowledge of the different pattern legs</li>
<li>the controller to issue sequencing in good time to keep the pilots informed</li>
<li>the controller to update the sequencing when things change or don't go to plan</li>
<li>the pilots to be courteous to each other by giving each pilot the space they need to maneuver</li>
<li>the pilots to follow the issued sequence</li>
</ul>
<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>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>When there is no Radar Controller present, Tower <strong class="red">must</strong> issue a pattern entry and clearance to <strong class="red">ALL</strong> aircraft as a <strong class="red">MINIMUM</strong>, regardless of what the aircraft uses to check in on the Tower frequency - the use of sequencing will be dependent on traffic. <a href="/guide/atc-manual/3.-tower/3.3-inbounds#3.3.1" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/560880041" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft calls inbound, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Determine the pattern entry required, then tap &quot;Pattern Instructions &gt; [select Pattern Entry] &gt; [select RWY] &gt; Send&quot;</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Once the aircraft has been given a pattern entry (and sequence if not number 1), the aircraft can be cleared by tapping &quot;Cleared to Land/For the Option &gt; [select number] &gt; [select Cleared to Land/Cleared for the Option] &gt; [select RWY]&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If the aircraft is not number 1, once you know which aircraft they are following, sequencing can be given by tapping &quot;Sequencing... &gt; [select number] &gt; [select current position of traffic to follow]&quot;</p>
</dd>
</dl>
</section>
</section>
</dl>
<details>
<summary><span class="details-marker">&nbsp;</span>SCENARIO - Multiple Inbounds</summary><div class="scenario-heading">
<p>Scenario</p>
</div>
<div class="scenario">
<p>Multiple aircraft have just announced inbound but the Controller is unsure on what order to sequence them in.</p>
</div>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-inbound.png" srcset="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-inbound@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-inbound@3x.png 3x" alt="" class="documentation-image-lightbox-link" >
          <figcaption></figcaption>
        </figure>
      </p>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 1</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Only send a pattern entry to the aircraft you are unsure about in terms of sequencing</td>
</tr>
<tr>
<td>2: Wait until the aircraft are closer, and once certain of their sequence, issue this along with their clearance</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 1</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Offers flexibility</td>
</tr>
<tr>
<td><i class="icon check circle"></i></td>
<td>Ensures aircraft know who they are following</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>May increase workload as you have to send two separate commands</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 2</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Send a pattern entry and the most likely sequence to all aircraft</td>
</tr>
<tr>
<td>2: Monitor and if required, change the sequence as they get closer</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 2</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Good for workload management</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>Aircraft may be unsure who they are following if the sequence is given too early</td>
</tr>
</tbody>
</table>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Work from the inside out by making sure that all aircraft closest to the airport have been given a pattern entry, sequence (unless they are number 1) and clearance. Then progressively work your way out to all the other aircraft!</p>
</dd>
</dl>
</dl>
</details>
</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">
<p>Once a runway assignment has been issued, it would be ideal if we did not need to change it. However, by using all available runways, changing the assigned runway (if required) is a useful tool to help deal with a dynamic environment and promoting an efficient operation.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<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). <a href="/guide/atc-manual/3.-tower/3.3-inbounds#3.3.3" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/562931877" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>If an aircraft requests a runway change, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>If the Controller is unable to grant the request, tap &quot;Unable&quot;</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>If the Controller is able to approve the request, or if the Controller decides to issue a runway change without a request from the aircraft (e.g. due to traffic), determine the pattern entry required, then tap &quot;Pattern Instructions &gt; [select Pattern Entry] &gt; [select RWY] &gt; Send&quot;</p>
</dd>
<dt>Step 5</dt>
<dd>
<p>Once the aircraft has been given a pattern entry (and sequence if not number 1), the aircraft can be cleared by tapping &quot;Cleared to Land/For the Option &gt; [select number] &gt; [select Cleared to Land/Cleared for the Option] &gt; [select RWY]&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If the aircraft is not number 1, once you know which aircraft they are following, sequencing can be given by tapping &quot;Sequencing... &gt; [select number] &gt; [select current position of traffic to follow]&quot;</p>
</dd>
</dl>
</section>
</dl>
<details>
<summary><span class="details-marker">&nbsp;</span>SCENARIO - Runway Changes</summary><div class="scenario-heading">
<p>Scenario</p>
</div>
<div class="scenario">
<p><em>VP-MAX</em> is departing RWY32L and <em>I F A E Eleven</em> is departing RWY32R. Both departures happened simultaneously. <em>I F A E Eleven</em> then asks for a RWY change to RWY32L.</p>
</div>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-runway-change.png" srcset="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-runway-change@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-runway-change@3x.png 3x" alt="" class="documentation-image-lightbox-link" >
          <figcaption></figcaption>
        </figure>
      </p>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 1</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Instruct <em>I F A E Eleven</em> to &quot;enter right downwind RWY32L, number 2, traffic to follow is on left downwind”</td>
</tr>
<tr>
<td>2: If you are concerned about a conflict on the other end, then you can also tell <em>I F A E Eleven</em> to &quot;extend downwind, I'll call your base&quot; to alleviate this</td>
</tr>
<tr>
<td>3: When you clear <em>I F A E Eleven</em>, you can then give them left traffic if you wish to do so to move them onto that side for subsequent patterns</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 1</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Offers flexibility</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>May cause confusion on who is following who</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 2</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Instruct <em>VP-MAX</em> to &quot;turn crosswind”</td>
</tr>
<tr>
<td>2: When you are happy with the separation, tell <em>I F A E Eleven</em> to &quot;enter left downwind for RWY32L, number 2, traffic to follow is on left downwind”</td>
</tr>
<tr>
<td>3: If during this time, <em>I F A E Eleven</em> starts a right turn for RWY32R, then adopt Technique 1 instead</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 2</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Ensures separation between both aircraft</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td><em>I F A E Eleven</em> may start the turn onto a right downwind before you have time to give the new pattern entry</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 3</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Instruct <em>I F A E Eleven</em> &quot;extend upwind, I'll call your crosswind”</td>
</tr>
<tr>
<td>2: Wait until separation between <em>VP-MAX</em> and <em>I F A E Eleven</em> is adequate (you can expedite this by telling <em>VP-MAX</em> to &quot;turn crosswind&quot;), and then tell <em>I F A E Eleven</em> to &quot;enter left downwind for RWY32L, number 2, traffic to follow is on left downwind”</td>
</tr>
<tr>
<td>3: The new pattern entry supersedes the previous instruction</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 3</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Prevents <em>I F A E Eleven</em> from entering right downwind</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>May add confusion when a pattern entry is used instead of &quot;turn crosswind&quot;</td>
</tr>
</tbody>
</table>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>Remember that other variables (such as terrain) might influence what is the best technique to use on the day, be flexible!</p>
</dd>
</dl>
</dl>
</details>
</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">
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<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. <a href="/guide/atc-manual/3.-tower/3.3-inbounds#3.3.5" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/562934956" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft calls inbound for touch &amp; go's, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Determine the pattern entry required, then tap &quot;Pattern Instructions &gt; [select Pattern Entry] &gt; [select RWY] &gt; Send&quot;</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Once the aircraft has been given a pattern entry (and sequence if not number 1), the aircraft can be cleared by tapping &quot;Cleared to Land/For the Option &gt; [select number] &gt; [select Cleared for the Option] &gt; [select RWY] &gt; [select send or make left/right traffic]&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>If the aircraft is not number 1, once you know which aircraft they are following, sequencing can be given by tapping &quot;Sequencing... &gt; [select number] &gt; [select current position of traffic to follow]&quot;</p>
</dd>
</dl>
</section>
</dl>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Options</th>
<th>When to Use</th>
</tr>
</thead>
<tbody>
<tr>
<td>&quot;Send&quot;</td>
<td>If the aircraft has already been instructed to make left/right traffic from the initial take-off clearance or the previous landing clearance</td>
</tr>
<tr>
<td>&quot;Make Left/Right Traffic&quot;</td>
<td>If the pilot is given a new pattern entry or new runway</td>
</tr>
</tbody>
</table>
</section>


Inbounds

<section id="pattern-work">
<h1><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</h1>
<section class="reference">
<p>The traffic pattern is a standard flight path followed by aircraft when taking-off and landing while maintaining visual contact with the airport. In Infinite Flight the pattern altitude is 1000ft AAL (above aerodrome level) for prop aircraft, and 1500ft AAL for jet aircraft. It consists of multiple legs, each being joined by a 90 degree turn, and these are shown in the image below:</p>
<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="The Traffic Pattern" class="documentation-image-lightbox-link" >
          <figcaption>The Traffic Pattern</figcaption>
        </figure>
      </p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>For Pattern Work to be allowed, Visual Meteorological Conditions (VMC) <strong class="red">must</strong> exist, aircraft <strong class="red">must</strong> be able to fly a standard pattern and traffic levels need to be manageable. <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.1" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<p>For a step by step guide on how to issue pattern entries, sequencing and clearances, make sure to check out the <a href="/guide/atc-guide/tower/inbounds" class="documentation-content-link">Inbounds</a> page.</p>
<details>
<summary><span class="details-marker">&nbsp;</span>SCENARIO - Re-Sequencing</summary><div class="scenario-heading">
<p>Scenario</p>
</div>
<div class="scenario">
<p><em>I-DRUM</em> and <em>N1DC</em> have both already been sequenced and cleared for RWY05L. As both aircraft continue downwind, <em>I-DRUM</em> has gone further downwind than the Controller expected.</p>
</div>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-downwind.png" srcset="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-downwind@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-downwind@3x.png 3x" alt="" class="documentation-image-lightbox-link" >
          <figcaption></figcaption>
        </figure>
      </p>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 1</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Re-clear <em>N1DC</em> as number 1</td>
</tr>
<tr>
<td>2: Re-sequence <em>I-DRUM</em> as number 2</td>
</tr>
<tr>
<td>3: If you are concerned about separation, you can tell <em>I-DRUM</em> to &quot;extend downwind, I'll call your base&quot; to alleviate this</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 1</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Efficient</td>
</tr>
<tr>
<td><i class="icon check circle"></i></td>
<td>Greater Pilot satisfaction</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>May increase workload as you have to send various commands</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table technique">
<thead>
<tr>
<th>Technique 2</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Instruct <em>I-DRUM</em> to &quot;turn base&quot;</td>
</tr>
<tr>
<td>2: This will force <em>I-DRUM</em> to fly a tighter pattern</td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 2</th>
<th>Pro or Con?</th>
</tr>
</thead>
<tbody>
<tr>
<td><i class="icon check circle"></i></td>
<td>Can be efficient</td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
<td>Some pilots/aircraft may not be able to fly as tight a pattern</td>
</tr>
</tbody>
</table>
</details>
</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">
<p>Transitions can be requested by aircraft when they are not with a radar facility and are transiting through the tower controller's airspace. 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>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<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. <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.2" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/563250409" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When an aircraft requests a transition, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
<dt>Step 3</dt>
<dd>
<p>Determine an altitude that will keep the aircraft within tower's airspace, but also provide separation with traffic that may be in the pattern</p>
</dd>
<dt>Step 4</dt>
<dd>
<p>Tap &quot;Respond to Transition &gt; [select &lt;10,000ft / &gt;=10,000ft ] &gt; [select altitude]&quot;</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>A minimum of 500ft is required between VFR traffic however we recommend giving a transition that provides a minimum of 1000ft separation to satisfy IFR requirements too!</p>
</dd>
</dl>
</section>
</dl>
</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">
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<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. <a href="/guide/atc-manual/3.-tower/3.4-pattern-work-transitions-flight-of-xx#3.4.5" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/563261625" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>
<p>When the lead aircraft makes a request, the aircraft symbol will flash amber on the map as well as their callsign on the flight progress strip</p>
</dd>
<dt>Step 2</dt>
<dd>
<p>Either tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</p>
</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>It may be easier to use the flight progress strip as multiple aircraft flying in formation can make tapping the aircraft on the map a bit tricky!</p>
</dd>
</dl>
</section>
</dl>
</section>


Pattern Work

<section id="exit-runway">
<h1><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</h1>
<section class="reference">
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<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. <a href="/guide/atc-manual/3.-tower/3.5-exit-runway-go-around#3.5.1" class="documentation-content-link">More Info?</a></p>
</dd>
</dl>
</dl>
<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/563268378" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>Tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 2</dt>
<dd>Tap &quot;Exit Runway &gt; [select left/right/any] &gt; [select from options below]&quot;</dd>
</dl>
<table class="ui table definition unstackable documentation-table">
<thead>
<tr>
<th>Options</th>
<th>Meaning</th>
</tr>
</thead>
<tbody>
<tr>
<td>&quot;Send&quot;</td>
<td>Sends normal exit command with permission to change frequency</td>
</tr>
<tr>
<td>&quot;Expedite&quot;</td>
<td>Sends &quot;expedite&quot; exit command with permission to change frequency</td>
</tr>
<tr>
<td>&quot;Expedite, Traffic on [Select Final/Base]&quot;</td>
<td>Sends &quot;expedite&quot; exit command (and position of landing traffic) with permission to change frequency</td>
</tr>
<tr>
<td>&quot;Cross Runway &gt; [Select RWY]&quot;</td>
<td>Sends normal exit command, permission to cross another runway and to change frequency</td>
</tr>
<tr>
<td>&quot;Hold Short &gt; [Select RWY]&quot;</td>
<td>Sends normal exit command and instructions to hold short of another runway. Aircraft remain on frequency and only changed to ground once traffic has crossed the runway</td>
</tr>
</tbody>
</table>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>The expedite command is usually best used when there is an aircraft on final within 2nm (or 3nm with another aircraft lined up on the runway ready to depart)</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>Dependant on what option is sent, a frequency change may be required. To do this, tap &quot;Contact Other Frequency &gt; [select frequency]&quot;</dd>
</dl>
</section>
</section>


Exit Runway

<section id="go-around">
<h1><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</h1>
<section class="reference">
<p>A Go-Around (G/A) is an aborted landing by an aircraft on final approach and can either be initiated by the pilot or ATC.</p>
<p>Possible reasons to Go-Around can include:</p>
<ul>
<li>Loss of separation with the aircraft ahead</li>
<li>Landing/intersecting runway blocked by another aircraft</li>
<li>or an unstable approach (both pilot induced or due to environmental factors)</li>
</ul>
<p>It is important to note that the responsibility for a go-around lies equally with the pilot and the controller, if ATC is present.</p>
<dl class="manual">
<dt>
<i class="book icon big"></i>
</dt>
<dd>
<p>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. <a href="/guide/atc-manual/3.-tower/3.5-exit-runway-go-around#3.5.4" class="documentation-content-link">More info?</a></p>
</dd>
</dl>
</dl>
<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/563272230" frameborder="0" allow="autoplay; fullscreen" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe></div></p>
<dl>
<dt>Step 1</dt>
<dd>Tap the aircraft on the map (and then &quot;Other Message&quot;), or the flight progress strip to bring up the communication menu</dd>
<dt>Step 2</dt>
<dd>Tap &quot;Go Around &gt; make [left/right] traffic &gt; [select RWY]&quot;</dd>
</dl>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>When selecting the direction for G/A traffic, make sure to take other aircraft and terrain into consideration!</dd>
</dl>
<dl>
<dt>Step 3</dt>
<dd>If there is an aircraft that has been cleared for take-off and a collision risk exists, cancel their take-off clearance by tapping &quot;Cancel Take-Off Clearance&quot;</dd>
<dt>Step 4</dt>
<dd>Unless the traffic is VFR (or a prior arrangement has been made with the Radar Controller), hand the go-around traffic to them (if present) by tapping &quot;Contact Other Frequency &gt; [select frequency]&quot;</dd>
</dl>
<details>
<summary><span class="details-marker">&nbsp;</span>SCENARIO - Go-Around Avoidance</summary><div class="scenario-heading">
<p>Scenario</p>
</div>
<div class="scenario">
<p>Both <em>N1DC</em> and <em>I-DRUM</em> are on final for RWY05L. With minimum separation and an Approach Speed difference in excess of 80kts, the possibility of a go-around is high.</p>
</div>
<p>
      <figure>
          <img src="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-go-around.png" srcset="https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-go-around@2x.png 2x, https://webcdn.infiniteflight.com/guide/manual/screens/atcg-pw-go-around@3x.png 3x" alt="" class="documentation-image-lightbox-link" >
          <figcaption></figcaption>
        </figure>
      </p>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 1</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Try to anticipate the problem by creating separation sooner rather than later</td>
</tr>
<tr>
<td>2: If both aircraft were downwind, rather than allowing <em>I-DRUM</em> to follow <em>N1DC</em> with minimum separation, you could instruct <em>I-DRUM</em> to &quot;extend downwind, I'll call your base&quot; to build more separation in between the two aircraft</td>
</tr>
<tr class="technique">
<td></td>
</tr>
<tr>
<td>Technique 1</td>
</tr>
<tr>
<td>------------------------------------------------------------</td>
</tr>
<tr>
<td><i class="icon check circle"></i></td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
</tr>
<tr>
<td></td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 2</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: Instruct <em>I-DRUM</em> to &quot;maintain slowest practical speed&quot;</td>
</tr>
<tr>
<td>2: Once <em>N1DC</em> has landed and is at a sensible speed, you can instruct them to exit the runway expeditiously (if it is a full-stop)</td>
</tr>
<tr class="technique">
<td></td>
</tr>
<tr>
<td>Technique 2</td>
</tr>
<tr>
<td>------------------------------------------------------------</td>
</tr>
<tr>
<td><i class="icon check circle"></i></td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
</tr>
<tr>
<td></td>
</tr>
</tbody>
</table>
<table class="ui table definition unstackable documentation-table prosandcons">
<thead>
<tr>
<th>Technique 3</th>
</tr>
</thead>
<tbody>
<tr>
<td>1: If you have multiple runways available, you could change the runway that <em>I-DRUM</em> is cleared for</td>
</tr>
<tr>
<td>2: Instruct <em>I-DRUM</em> to &quot;enter straight in RWY 05R&quot;</td>
</tr>
<tr>
<td>3: Re-clear <em>I-DRUM</em> for RWY05R with the appropriate traffic pattern instruction if it is a touch &amp; go</td>
</tr>
<tr class="technique">
<td></td>
</tr>
<tr>
<td>Technique 3</td>
</tr>
<tr>
<td>-----------------</td>
</tr>
<tr>
<td><i class="icon check circle"></i></td>
</tr>
<tr>
<td><i class="icon times circle"></i></td>
</tr>
<tr>
<td></td>
</tr>
</tbody>
</table>
<dl class="tip">
<dt>
<i class="lightbulb icon big"></i>
</dt>
<dd>
<p>There is nothing wrong with a go-around but it is the final defence - if you can prevent this by being proactive then great!</p>
</dd>
</dl>
</dl>
</section>
</details>
</section>


Go-Around

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.

Support & Features

Connect