# DENMILL

# AIR-TO-AIR REFUELLING

## Air-to-Air Refuelling Operations

This document describes how Copenhagen FIR controllers handle Air-to-Air Refuelling (AAR) operations on published AAR tracks.

The purpose of this procedure is to:

- Give controllers a common procedure for AAR operations.
- Protect the airspace used for the AAR operation.
- Give clear coordination requirements.
- Give standard phraseology examples.
- Reduce the effect of AAR operations on other traffic.

<p class="callout warning">
This procedure applies to approved <b>vSOA operations</b> on the VATSIM network.<br/><br/>
The controller provides ATC service and protects the required airspace.<br/>
The flight crew is responsible for close formation, joining, refuelling, and breakaway manoeuvres.
</p>

---

### Word Lookup

> **AAR**<br/>
> Air-to-Air Refuelling

> **ACC**<br/>
> Area Control Centre

> **FL**<br/>
> Flight Level

> **vSOA**<br/>
> VATSIM Special Operations Association

---

## Published Air-to-Air Refuelling Tracks

The following AAR tracks are published for use in Copenhagen FIR.

<table style="min-width:100%">
  <tr>
    <th class="tablerow">Track</th>
    <th class="tablerow">Published Level Block</th>
    <th class="tablerow">Reference Position</th>
  </tr>
  <tr>
    <td><b>RANDI</b></td>
    <td>FL150-240</td>
    <td>N57°00.00’ E009°00.00’</td>
  </tr>
  <tr>
    <td><b>SARAH</b></td>
    <td>FL150-240</td>
    <td>N55°20.00’ E008°45.00’</td>
  </tr>
  <tr>
    <td><b>SOFIA</b></td>
    <td>FL180-280</td>
    <td>N56°12.00’ E005°55.00’</td>
  </tr>
  <tr>
    <td><b>ROBIN</b></td>
    <td>FL180-280</td>
    <td>N56°48.00’ E005°35.00’</td>
  </tr>
  <tr>
    <td><b>STORK</b></td>
    <td>FL180-280</td>
    <td>N55°08.00’ E007°18.00’</td>
  </tr>
</table>

<style>
.tablerow{
  background-color:#1a475f;
  color:white;
}
</style>

The published level block defines the vertical limits available for the AAR track.

The tanker can request a base level inside the published level block.

For example:

- RANDI is available between FL150 and FL240.
- A tanker can request FL220 as its base level.
- FL220 does **not** change the published limits of RANDI.

<p class="callout warning">
<b>Protect the airspace required for the operation.</b><br/>
Do not protect only the current radar position of the tanker.
</p>

---

### Chart

![Copenhagen FIR Air-to-Air Refuelling Tracks](AAR_CHART_IMAGE)

**Reference:** MIL AIP DENMARK ENR 5.3-5.

---

## AAR Operation

An AAR operation consists of the following phases:

1. Request
2. Airspace check
3. Coordination
4. Airspace protection
5. Tanker entry
6. Receiver join
7. Refuelling operation
8. Receiver departure
9. Tanker departure
10. Airspace release

The controller must know the status of the AAR operation during all phases.

---

## Joining the Track

### Information from the Tanker

Before the tanker enters an AAR track, obtain:

1. AAR track.
2. Requested base level.
3. Entry time.
4. Expected duration.
5. Receiver callsign or callsigns, if known.

The controller can request missing information.

#### Example

**OAN1:**  
`Request AAR track RANDI.`

**ACC:**  
`OAN1, confirm AAR track RANDI, base level and duration.`

**OAN1:**  
`RANDI, base level FL220, duration 15 minutes.`

**ACC:**  
`OAN1, copied, standby.`

<p class="callout warning">
Do not approve the AAR operation before the required airspace checks and coordination are complete.
</p>

---

## Before Approval

Before approval:

1. Check that the requested track is available.
2. Check that the requested base level is inside the published level block.
3. Check that the required levels are available.
4. Check that no conflicting traffic is inside the protected airspace.
5. Check that crossing traffic can remain clear.
6. Check that climbing and descending traffic can remain clear.
7. Coordinate with all affected ATC sectors.

If the operation cannot start immediately:

**ACC:**  
`OAN1, unable AAR operation at this time, expect 10 minutes delay.`

If an accurate delay is not available:

**ACC:**  
`OAN1, unable AAR operation at this time, standby.`

---

## Protect the Airspace

Before the tanker enters the track, protect the required airspace.

The protected airspace must include:

- The complete applicable AAR area.
- The required vertical level block.

<p class="callout danger">
<b>Do not use only the tanker position as the protected area.</b><br/>
Protect the published AAR airspace for the complete duration of the operation.
</p>

### Conflicting Traffic

If traffic conflicts with an active AAR operation, use one of the following methods.

#### Vertical Separation

Clear the aircraft above or below the protected level block.

Example:

If RANDI is protected from FL150 to FL240, unrelated traffic can be kept:

- Below the protected airspace; or
- Above the protected airspace.

<p class="callout warning">
Use the protected AAR level block when you determine if traffic is clear.<br/>
Do not use only the tanker base level.
</p>

#### Lateral Separation

Vector or route the aircraft around the protected AAR airspace.

#### Delay

Delay or hold the aircraft if vertical or lateral separation is not available.

<p class="callout warning">
<b>Consider the complete aircraft trajectory.</b><br/>
An aircraft can be clear of the AAR area at its present level but conflict with the area during a climb or descent.
</p>

---

## Coordination

Coordinate the AAR operation with all affected ATC sectors before activation.

The coordination must include, as applicable:

- AAR track.
- Protected level block.
- Tanker callsign.
- Expected activation time.
- Expected duration.

#### Example

`RANDI active for OAN1, FL150 to FL240, expected 15 minutes.`

The exact coordination method can depend on sector ownership and controller configuration.

All affected controllers must know that the airspace is protected.

<p class="callout warning">
Coordination is required before the AAR airspace is activated and when it is released.
</p>

---

## Tanker Approval

When the required airspace is protected, approve the tanker operation.

#### Example

**ACC:**  
`OAN1, cleared to operate RANDI, base level FL220.`

**OAN1:**  
`Cleared to operate RANDI, base level FL220, OAN1.`

If an entry point or restriction is required:

**ACC:**  
`OAN1, cleared to operate RANDI, base level FL220, enter at [POINT].`

Continue to monitor the tanker until it enters the AAR track.

When the tanker enters the track, consider the AAR operation **ACTIVE**.

---

## Receiver Aircraft

Receiver aircraft remain under normal ATC service until the tactical join starts.

Before the join:

1. Identify the receiver.
2. Confirm which tanker the receiver will join.
3. Check the receiver level.
4. Check other traffic.
5. Position the receiver for the join.
6. Give tanker traffic information as necessary.

#### Example

**ACC:**  
`VIPER21, OAN1 twelve o'clock, 15 miles, FL220.`

**VIPER21:**  
`Traffic in sight, VIPER21.`

When the receiver is in a suitable position:

**ACC:**  
`VIPER21, join OAN1, maintain own separation.`

<p class="callout warning">
ATC positions the receiver for the join.<br/>
ATC does not control the close formation manoeuvre.<br/>
The participating pilots are responsible for separation during close formation and refuelling.
</p>

---

## During the AAR Operation

While the AAR operation is active, monitor:

- Tanker position.
- Receiver aircraft.
- Protected airspace.
- Protected level block.
- Crossing traffic.
- Climbing and descending traffic.
- Expected completion time.

Do not clear unrelated traffic into the protected AAR airspace.

Normal ATC operations can continue outside the protected airspace.

---

## Breakaway

A **breakaway** is a tactical manoeuvre between the tanker and receiver.

ATC does not give tactical breakaway instructions.

If an aircraft reports a breakaway:

1. Keep the AAR airspace protected.
2. Keep unrelated traffic clear.
3. Protect the required vertical airspace.
4. Avoid unnecessary ATC instructions.
5. Monitor the aircraft.
6. Wait until the aircraft reports ready for ATC instructions.

<p class="callout danger">
<b>BREAKAWAY</b><br/>
Do not assume that an aircraft will remain at its previous level during a breakaway.<br/>
Do not issue unnecessary instructions during the immediate manoeuvre.
</p>

#### Example

**VIPER21:**  
`BREAKAWAY, BREAKAWAY, BREAKAWAY.`

When the aircraft reports ready:

**VIPER21:**  
`VIPER21, ready for further clearance.`

Normal ATC service can then continue.

---

## Receiver Leaves the Tanker

When refuelling is complete, the receiver leaves the tanker formation.

Before you issue an onward clearance:

1. Identify the receiver.
2. Confirm its level.
3. Confirm its intentions.
4. Check other traffic.
5. Establish the required ATC separation.

#### Example

**VIPER21:**  
`VIPER21, refuelling complete, leaving OAN1.`

**ACC:**  
`VIPER21, radar contact, climb FL280, direct [POINT].`

<p class="callout warning">
Do not release the AAR airspace if the tanker or other receivers continue the operation.
</p>

---

## Tanker Leaves the Track

When the tanker reports that the AAR operation is complete, do not immediately release the protected airspace.

First confirm that:

1. All receivers have left the operation.
2. The tanker has left the protected AAR airspace.
3. No breakaway manoeuvre continues.
4. No recovery manoeuvre requires continued protection.

When all AAR aircraft are clear, release the protected airspace.

Coordinate the release with affected ATC sectors.

#### Example

`RANDI released, all levels available.`

The airspace can then return to normal use.

---

## Unable or Delayed AAR Operation

ATC can delay an AAR operation when the required airspace is not available.

Possible causes include:

- Traffic complexity.
- Traffic inside the AAR area.
- Traffic that cannot be routed around the area.
- Adjacent sector restrictions.
- Controller workload.

#### Delay

**ACC:**  
`OAN1, unable AAR operation, expect 10 minutes delay.`

#### Unable

**ACC:**  
`OAN1, unable AAR operation due traffic.`

<p class="callout warning">
The aircraft must not enter the AAR track until ATC gives approval.
</p>

## Quick Phraseology

<table style="min-width:100%">
  <tr>
    <th class="tablerow">Situation</th>
    <th class="tablerow">Phraseology</th>
  </tr>
  <tr>
    <td>Request information</td>
    <td><code>[CALLSIGN], confirm AAR track, base level and duration.</code></td>
  </tr>
  <tr>
    <td>Delay</td>
    <td><code>[CALLSIGN], unable AAR operation, expect [TIME] delay.</code></td>
  </tr>
  <tr>
    <td>Standby</td>
    <td><code>[CALLSIGN], unable AAR operation at this time, standby.</code></td>
  </tr>
  <tr>
    <td>Approve tanker</td>
    <td><code>[CALLSIGN], cleared to operate [TRACK], base level [LEVEL].</code></td>
  </tr>
  <tr>
    <td>Tanker information</td>
    <td><code>[RECEIVER], [TANKER] twelve o'clock, [DISTANCE] miles, [LEVEL].</code></td>
  </tr>
  <tr>
    <td>Permit join</td>
    <td><code>[RECEIVER], join [TANKER], maintain own separation.</code></td>
  </tr>
  <tr>
    <td>Receiver returns to ATC</td>
    <td><code>[RECEIVER], radar contact, [CLEARANCE].</code></td>
  </tr>
  <tr>
    <td>Release coordination</td>
    <td><code>[TRACK] released, all levels available.</code></td>
  </tr>
</table>