NATO UNCLASSIFIED / RS UNCLASSIFIED RSFCC SOP 1 ANNEX A... · RSFCC NATO UNCLASSIFIED / RS UNCLASSIFIED SOP 1- A REV DATE: 10 OCT 2018 NATO UNCLASSIFIED / RS UNCLASSIFIED PAGE A-2

RSFCC SOP 1-A REVISION DATE: 10 OCTOBER 2018

NATO UNCLASSIFIED / RS UNCLASSIFIED

RSFCC STANDARD OPERATING PROCEDURES – 1 ANNEX – A

OPERATIONS, INFORMATION, AND RS MISSION COORDINATION

Resolute Support Strategic Flight Coordination Centre, SHAPE

Commercial: +32 6544 8631 / 8633

DSN: 314-423-8631 / 8633

NATO Unclassified Email Address: [email protected]

NATO Secret E-mail Address: [email protected]

RSFCC NATO UNCLASSIFIED / RS UNCLASSIFIED SOP 1- A

REV DATE: 10 OCT 2018 NATO UNCLASSIFIED / RS UNCLASSIFIED PAGE A-2

Purpose

The purpose of this publication is to serve as reference material for international organizations

wishing to conduct strategic airlift operations into and out of Afghanistan in support of NATO

Resolute Support (RS). This publication provides an overview of Resolute Support Strategic Flight

Coordination Centre (RSFCC) roles and responsibilities as well as briefly explaining RS strategic

airlift mission coordination operations and regulations. Additionally, this publication provides

terms, definitions, and other operational guidelines used when coordinating and interacting with

the RSFCC. This publication is the only authorized source for regulations governing coordinating

a NATO strategic airlift mission into Afghanistan.

Visit the RSFCC website at https://isfcc.ncia.nato.int and verify

you are using the most recent revision of this document.

Deviation from any rules, regulations, and procedures outlined

in this document will result in mission request being denied.

https://isfcc.ncia.nato.int/



Contents

1 RSFCC INFORMATION ....................................................................................................................... 4

RSFCC DESCRIPTION ......................................................................................................................... 4 1.1

RSFCC KEY DUTIES ........................................................................................................................... 4 1.2

FLIGHTS NOT COORDINATED BY RSFCC:.............................................................................................. 4 1.3

2 RSFCC NATIONAL REPRESENTATION ........................................................................................... 5

RESPONSIBILITIES OF NAA/NATREPS: ................................................................................................. 5 2.1

NAA/NATREP CALL SIGN ISSUE PROCESS ........................................................................................... 6 2.2

BECOME A NAA/NATREP .................................................................................................................... 6 2.3

3 GENERAL CALL SIGN INFORMATION ............................................................................................. 7

RESOLUTE SUPPORT (NAG) CALL SIGNS ............................................................................................. 7 3.1

HEAVY AIRLIFT WING (HAW) CALL SIGNS ............................................................................................ 8 3.2

STRATEGIC AIR LIFT INTERIM SOLUTION CALL SIGNS ............................................................................ 8 3.3

TANKER AIRLIFT CONTROL CENTER (TACC) ........................................................................................ 8 3.4

4 REGULATIONS FOR RESOLUTE SUPPORT MISSIONS ................................................................. 9

MISSION LIMITATIONS FOR NAG CALL SIGNS ........................................................................................ 9 4.1

DANGEROUS GOODS CARGO ............................................................................................................. 10 4.2

REMAIN OVER NIGHT (RON) ............................................................................................................. 10 4.3

VIP FLIGHTS ..................................................................................................................................... 11 4.4

MOVEMENT REQUEST FORM .............................................................................................................. 11 4.5

RS AIRFIELD SLOT TIME COORDINATION ............................................................................................ 12 4.6

PERMANENT PARKING ON CIVILIAN RAMPS ......................................................................................... 13 4.7

IDENTIFICATION, FRIEND, OR FOE/SQUAWK CODE ............................................................................... 13 4.8

MISSION DATA UPDATES ................................................................................................................... 14 4.9

5 RSFCC WEBSITE .............................................................................................................................. 17

GAINING ACCESS TO WEBSITE ........................................................................................................... 17 5.1

MISSION DATA CONTENT ON WEBSITE ............................................................................................... 17 5.2

MISSION COORDINATION STATUS ....................................................................................................... 18 5.3

6 MRF SUBMISSION GUIDELINES ..................................................................................................... 19



1 RSFCC Information

RSFCC Description 1.1

The RSFCC is a multi-national organization located at Supreme Headquarters Allied Powers

Europe (SHAPE) in Mons, Belgium. Daily operations are managed by military personnel from

multiple NATO nations. The RSFCC is the sole organization authorized by the Government of

Afghanistan to provide strategic airlift mission coordination support for Resolute Support (RS)

operations in Afghanistan. RSFCC personnel coordinate airlift operations for Bagram (OAIX),

Kabul (OAKB), Kandahar (OAKN), Mazar-e-Sharif (OAMS), and Herat (OAHR). These five

airfields are the only NATO Operation Resolute Support airfields in Afghanistan.

RSFCC Key Duties 1.2

Generate and distribute all RS Call Signs 1.2.1

Assign Identify Friend or Foe (IFF)/Squawk codes 1.2.2

Negotiate airfield slot times for all RS strategic airlift missions 1.2.3

1.2.3.1 SHAPE Air Movement Coordination Centre (AMCC) and Tanker Airlift Control Center (TACC) have agreed all US Military Aircraft will be coordinated by TACC

1.2.3.2 As needed the RSFCC can request TACC coordinated mission data by SMS data feed.

Provide RS mission data to operators and Combined Air Operations Center (CAOC) 1.2.4

Flights not coordinated by RSFCC: 1.3

Rotary Wing Missions – The RSFCC does not have a role in Rotary Wing (RW) 1.3.1Mission coordination. These missions are only coordinated by the TAAC level. The RSFCC will only coordinate the approval for these missions in special situations or emergencies. The use of RS Call Signs for RW Missions is not authorized.

Non-NATO Civilian Missions – RS Call signs are not to be used for these missions. 1.3.2Flight coordination procedures for non-NATO civilian aircraft operating in Afghanistan’s airspace are detailed in the Republic of Afghanistan’s Aeronautical Information Publication (AIP) on the Afghanistan Civil Aviation Authority (ACAA) website: http://acaa.gov.af/en/page/civil-aviation-authority/atm/aip---important-information.

USAF Inter-theatre Fixed-Wing (Strategic) Missions – USAF inter-theatre fixed-1.3.3wing strategic flights are coordinated by the TACC.

Resolute Support Intra-theatre Fixed-Wing Flights – The Force Movements Control 1.3.4Centre (FMCC) within HQ RS, Kabul, directs procedures for the coordination of RS Intra-Theatre Airlift System (ITAS) fixed-wing flights.

ANA Flights – Flights in support of the Afghan National Army are not in support of RS 1.3.5or a specific Theater Contributing Nation (TCN) so the RSFCC does not coordinate these missions.

http://acaa.gov.af/en/page/civil-aviation-authority/atm/aip---important-information



2 RSFCC National Representation

There are 40 Theater Contributing Nations (TCNs) conducting military operations for NATO in

Afghanistan. Each one of these nations participates in the strategic airlift mission using military

and contracted civilian aircraft to provide the much needed logistical support for ongoing Resolute

Support operations. Such a large effort with no intermediate verification could lead to duplicate or

unauthorized missions being coordinated by the RSFCC. To alleviate confusion and duplicated

effort a select few individuals are selected by their nation and to act as this intermediate agent in

charge of verifying the validity and accuracy of all new mission requests submitted to the RSFCC

for coordination. National Airflow Authority (NAA) and National Representatives (NatReps) are the

appointed individuals in charge of ensuring their nation’s strategic airlift planning is timely,

accurate, and efficient. NAA/NatReps are thoroughly vetted by their TCN before being submitted

to the RSFCC for final approval.

Responsibilities of NAA/NatReps: 2.1

Protect their own nations Operational Security (OPSEC) by confirming all individuals 2.1.1requesting call signs have a verified need-to-know before issuing a call sign.

Protect NATO OPSEC by confirming all individuals requesting access to RSFCC 2.1.2website have been cleared and have a verified need-to-know before submitting the Username and Password request for the RSFCC website.

Complete and submit all RSFCC website Username and Password requests to 2.1.3Reporting & Briefing.

Notify RSFCC Reporting & Briefing immediately when a user’s access needs to be 2.1.4suspended or terminated completely.

Ensure the mission submitted by contractor is a valid mission. 2.1.5

Verify all required documentation is completely and correctly filled out before 2.1.6submission to the RSFCC for coordination.

Ensure the contractor will not violate any of the terms and conditions in their contract 2.1.7by executing the mission.

Verify that all cargo transported into Afghanistan complies with the RS rules and 2.1.8regulations outlined in this document.

Ensure the contractors understand all of the rules, regulations, and procedures 2.1.9outlined in this document and the Afghan Ministry of Transport and Civil Aviation websites and understand the ramifications of noncompliance.

Check the RSFCC website and review the Future Plan and Flow Table regularly to 2.1.10ensure all of their nation’s call signs currently in use were coordinated through the NAA/NatRep.

Contact RSFCC Ops or Reporting & Briefing if you have any questions or concerns 2.1.11

The RSFCC is not legally responsible for any, fees, fines, or damages levied as a 2.1.12result of incorrect mission data being submitted for coordination.



NAA/NatRep Call Sign Issue Process 2.2

NatReps/NAA receives requests from contractors for Call Signs for RS missions. They 2.2.1check their list of authorized contractors to verify their entitlement to a Call Sign, and that the load is within the provision of the contract.

NatReps/NAA issue Call Signs to the requesting contractor who may, in turn, issue 2.2.2single Call Signs to sub-contractors if required. NatReps/NAA should not issue blocks of Call Signs to contractors.

NatReps/NAA are to maintain visibility of the flights for which they have issued Call 2.2.3Signs, through the RSFCC website and liaison with airfields. They should investigate instances of unauthorized use of Call Signs that they have issued, use of duplicate Call Signs by contractors, Significant delays, cancellation of flights, and that the Cargo POC has cleared the load.

Become a NAA/NatRep 2.3

If your nation is already a TCN supporting NATO Resolute Support, contact one of 2.3.1your nation’s NAA/NatReps to start the process.

If your nation is not a TCN please contact RSFCC Reports & Briefing via unclassified 2.3.2email at: [email protected] to start the process.

mailto:[email protected]



3 General Call Sign Information

Resolute Support (NAG) Call Signs 3.1

A NAG call sign is a 7-character alphanumeric ‘word’ that is comprised of a prefix, a numerical

designator, and contracting country code suffix. The first three characters of the call sign are the

prefix. The ‘NAG’ prefix indicates the aircraft is operating in direct support of NATO Resolute

Support missions in Afghanistan. The next two characters of the call sign are the numerical

designator and can be any two-digit number from 01 to 99. The final two character 2-charater

country code issued by the RSFCC.

The prefix is constant and will never change as long as the aircraft is supporting NATO 3.1.1Resolute Support.

The numerical designator can and will change depending on the requirements of the 3.1.2operator.

The country code is issued to the TCN’s National Airflow Authorities (NAA) and/or 3.1.3National Representatives (NatReps) at least two months before the month of use.

3.1.3.1 The RSFCC is the only organization authorized to generate, control, and distribute NAG call sign country codes.

3.1.3.2 The NAG country code is only valid for the assigned month.

3.1.3.3 The RSFCC will annually issue the new unique country codes for all RS TCNs corresponding to the 12 months in the year.

All call sign country codes change on a monthly basis to prevent illegal use and to help 3.1.4maintain operational security (OPSEC) for TCNs.

If a two-day mission profile carries from one month to the next then the call sign 3.1.5country code will be based on when the flight makes its first stop in Afghanistan

If a mission is delayed from the last day of one month to 1st of the following month; the 3.1.6RSFCC will keep the old call sign if it is not possible to change the call sign due to diplomatic clearance procedures.

NAG call signs are valid for a max of 48 hours 3.1.7

NAG call signs are valid for a max of TWO calendar days. 3.1.8

NAG Call Signs shall not be used for 2 separate missions on consecutive days. If this 3.1.9is done and the first flight is delayed, two flights with the same call sign could operate on the same day which is not authorized.

NAG01XX



Heavy Airlift Wing (HAW) Call Signs 3.2

HAW C-17 missions operating into and out of Afghanistan require an RS Call Sign, 3.2.1PPR co-ordination and an IFF squawk code.

The RS Call Sign will be provided by the NatReps/NAA of the nation whose cargo is 3.2.2being carried, in accordance with RSFCC Operating Procedures.

When the aircraft load is comprised of cargo from more than one nation, the nation 3.2.3funding the mission is responsible for applying to their NatReps/NAA for an RS Call Sign. The issuing nation will be entered into the appropriate fields of the MRF and PPR.

When other legs of this mission are in support of another nation, another Call Sign is 3.2.4to be used (and coordinated accordingly).

Strategic Air Lift Interim Solution Call Signs 3.3

Strategic Air Lift Interim Solution (SALIS) Chartered An-124 supporting the Strategic Airlift

Coordination Cell (SALCC) participating Nations. For more information see the SALCC tab on

MCCE website.(http://mcce-mil.com/) The SALCC is a multi-national military organization,

established on 23rd of January 2006. The permanent staff of the SALCC is located in the MCCE

at Royal Netherlands Air Force Base Eindhoven, Netherlands. The aim of SALCC is to manage

the SALIS contract. The thirteen nations on the SALIS-Contract are Belgium, Czech Republic,

Germany, Finland, France, Greece, Hungary, Luxemburg, Norway, Poland, Slovakia, Slovenia,

and Sweden. The contract guarantees availability of two AN124-100 aircraft under part-time

charter for any of the participant’s national purpose, and the availability of up to six AN124-100

aircraft on priority call for the rapid deployment of forces in support of NATO/EU operations

The RS Call Sign will be provided by the RSFCC to SALCC and subsequently the 3.3.1RSFCC process will be followed. The coordination for these missions is based on a multinational usage and will be centrally coordinated by SALCC.

Each month SALCC will inform RSFCC for which nations the mission and mission legs 3.3.2have been performed.

Tanker Airlift Control Center (TACC) 3.4

Located at Scott Air Force Base, is Air Mobility Command's execution arm for providing America's

Global Reach. The TACC plans, schedules and directs a fleet of more than 1,300 mobility aircraft

in support of combat delivery and strategic airlift, air refueling and aero medical evacuation

operations around the world. TACC is the global air operations center responsible for centralized

command and control of Air Force and commercial contract air mobility assets 24-hours-a-day. It

plans, schedules and tracks tanker, airlift, and aero medical evacuation aircraft worldwide to

efficiently and effectively accomplish AMC's Global Reach mission. This organization is capable

of seamlessly transitioning from day-to-day operations to contingency support or disaster relief.

TACC issues specific Call Signs for these kinds of missions. The USA has designated US-Lanes

at several RS Airfields with their own personnel and equipment. Slot allocation for these specific

lines is coordinated by TACC. RSFCC and TACC can, if required, arrange for exchange of these

facilities.

http://mcce-mil.com/



4 Regulations for Resolute Support Missions

Mission Limitations for NAG Call Signs 4.1

Carriers using NAG call signs are exempt from landing fees and routine customs 4.1.1inspections.

Only cargo and/or passenger flights in direct support of RS are authorized to use the 4.1.2NAG call sign.

The RSFCC is the only authorized source to obtain NAG call signs, RS squawk codes, 4.1.3and RS airfield coordination.

Passenger and/or cargo missions for the UN, TCN Embassies, NGOs, and charities 4.1.4are not authorized to use NAG call signs.

A very select few of Strategic Supporting Flights using Afghanistan Stationed but non-4.1.5ITAS Assigned Aircraft are authorized to use the NAG call signs.

Commercial cargo missions to Afghanistan are not authorized to operate under a NAG 4.1.6call sign. Operators are to ensure that no commercial freight bound for Afghanistan is loaded on any aircraft operating under a NAG call sign.

Mixed cargo missions to Afghanistan are not authorized to operate under a NAG call 4.1.7sign. Mixed cargo in this context is defined as an aircraft being partially loaded with RS cargo and the remaining cargo capacity is used for non RS efforts within Afghanistan like commercial shipping.

Shared load or aircraft sharing between RS TCNs for different contracts is allowed. 4.1.8One RS TCN contracting an aircraft can share unused cargo capacity with another RS TCN. The cargo restriction still applies if the aircraft uses a NAG call sign. The TCN with the majority of the freight onboard is considered the primary contractor and is to assign the RS call sign.

An aircraft carrying RS cargo and non-RS cargo is authorized as long as the non-RS 4.1.9cargo is NOT offloaded in Afghanistan. This is also known as Transit Load. The following mandatory conditions must be met before transit loads are authorized:

Separate cargo manifest documents for transit load

Transit load cannot contain any Dangerous Goods (DG)

Transit load cannot contain prohibited/sanctioned cargo

Operators using NAG call signs are subject to random and unannounced spot checks 4.1.10of aircraft to ensure compliance with regulations.

Operators who knowingly or unknowingly violate NAG call sign cargo limitations or use 4.1.11NAG call signs to support any non-RS efforts will be permanently “Blacklisted” at the RSFCC. The RSFCC will not accept or process any mission/coordination requests from blacklisted operators.

Any suspected violation of NAG call sign restrictions will be reported to ACAA for 4.1.12investigation.



Dangerous Goods Cargo 4.2

To provide maximum cargo load visibility for airfield management and to the Combined Air

Terminal Operations (CATO) centers in Afghanistan, detailed cargo information is to be included in

the MRF on the cargo information tab. Every leg has its own cargo tab where the cargo

information must be detailed.

Load handling and parking restrictions are driven by ground crew and aircrew safety. 4.2.1

Dangerous Goods (DG) are those goods that fall in UN Hazardous Material Class 1. 4.2.2

Division 1.1 Mass explosion hazard

Division 1.2 Projection hazard only

Division 1.3 Fire hazard and minor blast or minor projection hazard

Division 1.4 Minimal hazard

Division 1.5 Blasting agents

Division 1.6 Very insensitive detonating articles

It is essential that all Dangerous Goods are specified with the correct UN Class, UN 4.2.3Number, and the Net Explosive Quantity (NEQ) where appropriate.

Explosives are declared as NEQ when described in the cargo spreadsheet which is 4.2.4not the gross weight.

Accurate hazardous goods information is more critical at Kabul where hot cargo 4.2.5parking and certified ground crews are limited.

The excel spreadsheet on the cargo information tab in the MRF will calculate the 4.2.6required values based on the weight and properties of dangerous cargo and it will automatically populate the front page of the MRF with the totals.

The quantity and weight on the front page of the MRF should not be changed manually 4.2.7because that will cause an error in the formula. Please list the most dangerous goods which require handling on the DAC-ramp as the first Dangerous Goods Item in your information.

If cargo information is not yet available, submit MRF as early as possible with the 4.2.8estimated cargo and then submit a MRF change when actual cargo information becomes available.

Cargo information updates are submitted using the same process as changing a slot 4.2.9time or route change.

Remain Over Night (RON) 4.3

When a flight needs to remain over night at an airfield the details of the RON must be requested in

the Remarks section of the MRF. These details must include the justification for a RON, when the

aircraft will be departing, what the next destination is, and any call sign changes.

RON Request Example:

“NAG25XR requests to RON to accommodate crew rest. Aircraft will depart OAKN 24 Jul 2018

0330Z as NAG26XR headed to UBBB”



VIP Flights 4.4

VIP flights require special coordination to ensure the airfield is prepared for their arrival. There are

special cases that the VIP info can be left out of the mission coordination, but this must first be

approved by the airfield.

VIP is considered any passenger equivalent to a one-star general 4.4.1

VVIP is considered anyone equivalent to a two-star general or above. 4.4.2

Unless approved by the RSFCC and the airfield the following information is required 4.4.3for every VIP/VVIP mission

4.4.3.1 Title/Rank: For military members use the proper name for their rank. For Civilians use Mr/Mrs/Ms and the equivalent NATO code for their position.

Rank/Title

Full First and Last Name

Position

NATO Code associated with their rank

Point of Contact Full First and Last Name and Non-DSN phone number

NATO Code OF-10 OF-9 OF-8 OF-7 OF-6

US DoD Pay Grade Special O-10 O-9 O-8 O-7

Military Example:

VVIP Lt Gen Michael Jackson, OF-8, US AFCENT Commander POC: Maj Tito Jackson, +1-713-555-5555

Civilian Example:

VIP Mr. Steven Spielberg, OF-6, US AFMC Dirtector POC: Capt Martin Brody, +1-281-555-5555

Movement Request Form 4.5

The Movement Request Form (MRF) is the form used by any organization requesting to operate a

strategic airlift mission in support of NATO RS missions in Afghanistan. This form is specific to

RSFCC coordination processes and requirements. The form and its contents are managed

exclusively by the RSFCC. The operator or NAA/NatRep fills in all of the data associated with the

desired mission profile data and then the NAA/NatRep submits it to the RSFCC for coordination

and approval. This is the only approved form for NATO RS mission requests and coordination.

The latest version can be found on the RSFCC website via the “Documents” tab next to the

“home” tab. (https://isfcc.ncia.nato.int/Pages/Documents.aspx)

There are two different MRF templates to accommodate missions of different lengths 4.5.1(6 mission legs and 12 mission legs)

The initial mission request (MRF V0) must come directly from the NAA/NatRep. This 4.5.2process is in place to ensure the accuracy of the missions submitted and ensure TCNs are aware of every RS mission being operated on behalf of their nation.

The RSFCC will only accept MRFs sent via email. 4.5.3

Only one MRF may be attached to each email request. 4.5.4

https://isfcc.ncia.nato.int/Pages/Documents.aspx



E-mails containing multiple MRFs will be rejected. 4.5.5

MRFs should be submitted to the RSFCC at least 24 hours before the first departure 4.5.6time of the mission to allow for coordination.

The RSFCC will coordinate missions within the 24-hour window on a case by case 4.5.7basis.

Operators are expected to plan effectively to avoid “Same-Day” requests. Airfield slot 4.5.8time availability can be very limited this close to execution and some airfields will not approve “Same-Day” requests.

Aero Medical Evacuation/Extraction (MEDEVAC) missions are the exception and 4.5.9every effort and resource will be given to facilitate the fastest possible coordination.

All MRFs must contain a 24-hour Point of Contact (POC) for the Aircraft operator and 4.5.10the Primary Contractor so the RSFCC can call and email them for mission clarification or to coordinate the resolution of issues/conflicts.

If the RSFCC requires clarification or an issue/conflict arises during the coordination 4.5.11process all progress will stop until the issue is resolved.

MRFs submitted with execution dates 7 days or less into the future will be processed 4.5.12immediately upon receipt.

MRFs submitted with execution dates of 8 to 14 days in the future will be imported into 4.5.13the flight database, but the coordination process will not be started until the mission execution dates is 7 days or less into the future.

Without prior coordination for special circumstances any MRF submitted with 4.5.14execution dates more than 14 days into the future will be deleted.

Incomplete or incorrectly filled out MRFs will not be processed by the RSFCC. The 4.5.15incorrect MRF will be sent back to the email address it came from, with a brief explanation of what is wrong with the MRF.

The RSFCC uses a First-Come-First-Served (FCFS) system which prioritizes RSFCC 4.5.16coordination efforts based on the date that the MRF V0 was submitted to the RSFCC.

The same MRF is used in the mission data update process. 4.5.17

RS Airfield Slot Time Coordination 4.6

To ensure suitable parking and proper ground handling is available at RS airfields, all aircraft

wanting to land must reserve a spot on the ground for a specific period of time called a “Slot Time.”

Airfield managers use slot times to maximize the effectiveness of their limited ramp/apron space

and ground crews. The RSFCC coordinates directly with the airfield managers to obtain slot times

for all NATO RS Missions. The RSFCC exports mission profile data from the EVE database into

the “Prior Permission Required (PPR) Request Form.”

The PPR form contains the mission data associated with a particular airfield and it outlines how

and when the mission will affect the airfield. If the airfield manager approves the request they will

assign a slot time specific alphanumeric code called a “PPR Number.” A PPR number must be

issued for every airfield visited within a mission. The RSFCC is the only organization authorized to

submit PPR requests. Airfields will not accept any request for processing of a mission using an

RS call sign unless it comes directly from the RSFCC.



The Aeronautical Information Publication (AIP) for Afghanistan clearly states that RS 4.6.1missions will be coordinated with airfields through RSFCC.

All aircraft operating under an RS call sign will be denied authorization to land if they 4.6.2do not already have a PPR number associated with a slot time.

Once all PPR numbers have been obtained from the destination airfields the RSFCC 4.6.3will assign an IFF/Squawk code to the mission.

PPR numbers and IFF/Squawk codes will be visible on the RSFCC website in the Flow 4.6.4Table which is updated after each DISTRO.

Do not call the RSFCC inquiring about PPR status; check the website. 4.6.5

The RS Afghan airfields have added a 30 minute window to both side of an inbound 4.6.6flight’s requested arrival time. This window will not appear on any documentation. This is an effort by the airfields to accommodate small delays.

Any aircraft that arrives outside of that window may be turned away at the airfield’s 4.6.7discretion.

If a mission has experienced a delay that will cause them to arrive more than 30 4.6.8minutes late a new slot time must be requested through the RSFCC.

If a new slot time is required, the aircraft operator must submit a mission data update. 4.6.9

Any mission data update must be submitted to the RSFCC for coordination in the form 4.6.10of a new MRF using the mission data process.

Permanent Parking on Civilian Ramps 4.7

Some civilian operators have received permission to park their aircraft overnight on the civilian

parking ramp at certain airfields. Such operators may be required to include a copy of their

parking permit with their MRF, if requested by the airfield. Additionally, where these aircraft are

required to taxi from their overnight parking slot on the civilian ramp to a military ramp prior to

loading RS cargo/passengers, the airfield may require a PPR to allocate the military parking slot.

In such cases the civilian operator will be required to submit a MRF to RSFCC to achieve

coordination.

Identification, Friend, or Foe/Squawk Code 4.8

Identification, friend, or foe (IFF) is a tool within the broader military action of combat identification.

is an identification system designed for command and control. It enables military and national

(civilian) air traffic control (ATC) interrogation systems to identify aircraft, vehicles, or forces as

friendly. It also facilitates verification of the bearing and range measurements made by the

interrogator radar. Use of the word “Squawk” comes from the system’s origin in the WWII

Identification, Friend, or Foe system which was code-named “Parrot.”

The RSFCC is the sole organization authorized by the Aeronautical Information Publication (AIP)

for Afghanistan to generate and distribute IFF/Squawk codes for RS missions in Afghanistan. The

Afghan airspace is over active military operations and is protected by armed military aircraft. Only

those aircraft that have been vetted through a coordination process will be granted entry.

Aircraft operating under an RS call sign attempting to enter Afghan airspace without an 4.8.1IFF/Squawk code issued by the RSFCC will be denied access to the airspace.



Continued authorized entry to a military controlled airspace could cause aircraft to be 4.8.2perceived as a threat which could lead to deadly force being authorized to protect personnel, equipment, and ongoing operations

AN RSFCC coordinated mission does not receive an IFF/Squawk until all stops have 4.8.3been coordinated and the required PPR numbers are assigned.

RS IFF/Squawk codes a tied directly to the RS call sign and are only valid with that 4.8.4specific call sign operating within a very specific pre-coordinated timeframe.

IFF/Squawk codes are not transferrable. 4.8.5

Mission Data Updates 4.9

Changes to any of the data in a mission submitted to the RSFCC must be done using the RSFCC

MRF. There are many reasons to deviate from coordinated mission data. These reasons can

include weather delays, aircraft failure, Notice to Airman (NOTAM), cargo delay, and individual leg

cancellation.

All mission data changes must comply with Mission, Cargo, and call sign limitations 4.9.1outlined in this publication.

The RSFCC MRF form is used for submitting mission data changes/updates to the 4.9.2RSFCC for coordination.

All changes to coordinated mission data must be requested formally through email 4.9.3with the updated MRF included as an attachment.

The body of the mission data change request email must contain a listing of the 4.9.4desired changes.

Operators/NAA/NatReps submit an updated version of the previously submitted MRF 4.9.5V0 and increment the version number by 1 for every subsequent change. For example, a slot time change is requested for NAG55XR on 5th of October 2018 so, the new MRF should be titled NAG55XR 05 OCT 2018 MRF V1.

If an airfield rejects a PPR request during the initial mission coordination the RSFCC 4.9.6will reply back to the original request email with the suggested action and the new data must be submitted in a MRF V1 for coordination.

RSFCC operations controllers are not authorized to make alterations to a MRF/PPR 4.9.7Form manually.

Mission data changes will be visible on the RSFCC website in the Flow Table which is 4.9.8updated after each DISTRO.

Do not call the RSFCC inquiring about mission data status; check the website. 4.9.9

Changes to execution times (slot time changes) within 24 hours can come directly from 4.9.10the aircraft operator in the form of a new version of the original MRF V0.

Chances to Aircraft type can come directly from the aircraft operator in the form of a 4.9.11new version of the original MRF V0.

Changes to Aircraft Registration (Tail Number) can come directly from the aircraft 4.9.12operator in the form of a new version of the original MRF V0.



Mission data changes that require the NAA/NatReps are specifically outlined in this 4.9.13publication.

Do not use previously assigned PPR numbers and IFF/Squawk codes for a modified 4.9.14mission unless the mission status is reported as “Confirmed” with the new mission data in the Flow Table

On a case by case basis the RSFCC will process mission data updates while the 4.9.15mission is being executed. This “Short Notice” process should only be used a last resort to deal with unforeseen issues and emergencies.

Thorough and effective mission planning on the operator’s part will minimize the risk of 4.9.16unforeseen delays or interruptions which will save time for everyone involved.

If a mission data update is submitted during mission execution the aircraft is not 4.9.17authorized to depart for the affected airfield until the change has been approved by the airfield.

In the case of a “Short Notice” mission data change the approval notification will likely 4.9.18come in the form of an email or telephone call from the RSFCC to the aircraft operator.

The following paragraphs outline additional requirements for a mission being delayed 4.9.19for 24 hours or more from the original mission profile time.

4.9.19.1 A mission delay of 24 hours or more is not authorized and the aircraft operator will be required to officially cancel the mission via email notification and have NAA/NatRep submit a new MRF V0 under a new call sign.

4.9.19.2 Any mission that had a priority or a pre-allocated mission status will lose that status as a result of this change.

4.9.19.3 The only situation the RSFCC will authorize the operator to delay a mission for 24 or more hours and retain the original call sign is to accommodate for the inflexible Diplomatic Clearance Request (DCR) process.

4.9.19.4 This situation usually only applies to military operated missions, but in any case the NAA/NatRep must receive prior approval from the RSFCC before submitting the MRF V0 for initial coordination.

4.9.19.5 Once the RSFCC gives the approval the first mission request email containing the MRF V0 must have a statement about the mission being constrained by a DCR and requires additional call sign flexibility if delayed.

4.9.19.6 The maximum amount of flexibility the RSFCC will give DCR missions is an additional 24 hours. This means that with prior approval a DCR mission can be delayed up to 48 hours after the original execution date/time and retain the original call sign.

The following paragraphs outline additional requirements and clarification for data 4.9.20changes to individual legs of a mission.

4.9.20.1 The RSFCC will change cargo on a mission to Dangerous Goods (UN Class 1) unless an email from the NAA/NatRep accompanies the new MRF version or the NAA/NatRep sends the new MRF version directly to the RSFCC. Dangerous Goods required special aircraft parking at some airfields and also required specially trained ground crews.



4.9.20.2 The RSFCC will not make changes Non-Dangerous cargo amounts unless an email from the NAA/NatRep accompanies the new MRF version or the NAA/NatRep sends the new MRF version directly to the RSFCC.

4.9.20.3 The RSFCC will not add a leg to a mission unless an email from the NAA/NatRep accompanies the new MRF version or the NAA/NatRep sends the new MRF version directly to the RSFCC.

4.9.20.4 The RSFCC will not make changes to the RS airfields the mission stops at unless an email from the NAA/NatRep accompanies the new MRF version or the NAA/NatRep sends the new MRF version directly to the RSFCC.

4.9.20.5 If an operator is frequently cancelling legs, this will be assessed as blocking slots from other users and may result in limited support or restriction being placed on the offending operator.

Complete mission cancellations can come directly from the aircraft operator in the form 4.9.21of an email detailing the call sign, date of execution, and reason for cancellation.

A separate email must be sent for mission that requires cancellation. 4.9.22

All cancellation request coordination with the airfields is completed exclusively by the 4.9.23RSFCC after the email is received from the operator.

To provide best possible logistical support to RS and the TCNs the RSFCC records 4.9.24the reasons for mission cancellation. This data is compiled into a report that is sent to the military authorities of the TCN. This helps them to identify any trends in operator performance. Poor or irregular performance could have contractual ramifications.



5 RSFCC Website

The RSFCC website is a web based share point where all RSFCC coordinated mission data is

stored. Access to the website is granted by the RSFCC after applicants have been vetted and

have a verified nee-to-know. The Username and Password issued to the NAA/NatReps and

aircraft operators are enabled with the minimum level of permissions required to complete their

mission planning tasks. Once access is granted users can view/verify mission data and ascertain

the current coordination status for all of their active missions. This information is also available to

NATO Nations and RS Agencies in and around Afghanistan on the NATO SECRET or MISSION

SECRET Wide Area Network within the EVE software environment. The unclassified RSFCC

website can be found at: https://isfcc.ncia.nato.int.

Gaining Access to Website 5.1

If you are a civilian contractor for a TCN supporting NATO Resolute Support, contact 5.1.1one of that nation’s current NAA/NatReps to start the process.

If you are becoming a NAA/NatRep you must use a current NAA/NatRep to complete 5.1.2the access process as well.

Mission Data Content on Website 5.2

The RSFCC exports mission profile data from the Effective Visible Execution (EVE) database and

posts the information to the RSFCC website. This process is called the Distribution or DISTRO for

short. The RSFCC website is the only location where operators can retrieve Prior Permission

Required (PPR) numbers and IFF/Squawk codes for approved RS missions. Operators can also

use the information posted to the website to determine coordination status of RS missions

submitted to RSFCC.

The DISTRO is accomplished by the RSFCC at 0000Z, 0400Z, 0800Z, 1200Z, 1600Z, 5.2.1and 2000Z.

The DISTRO provides the following 7 updates to the RSFCC website: 5.2.2

5.2.2.1 MNFEP: The Multi National Flight Execution Plan (MNFEP) file is the exported file of all EVE missions, including passenger and cargo information. This is a *.eve file that is only viewable using the EVE software. This file is only shared on the Military Operators and the CAOC tabs of the website.

5.2.2.2 CNX: The CNX file provides the CAOC with a list of cancelled missions that were scheduled to execute during the next two calendar days. This file is an Excel spreadsheet and is only loaded on the CAOC tab of the website.

5.2.2.3 ATO Feeder: The ATO Feeder provides all Military-operated missions scheduled to execute within the next two calendar days. The CAOC integrates this information into the Air Tasking Order. This file is an Excel workbook with spreadsheet tabs for every coordinated mission. This file is only loaded on the CAOC tab of the website.

5.2.2.4 Flow Table: The RS Flow Table provides a list of all Civilian and Military operated missions scheduled to execute within the next 7 calendar days. This file is an Excel workbook that has a spreadsheet tabs for every RS ICAO for the next 7 days. This file is only loaded on the Military Operators tab of the website.

https://isfcc.ncia.nato.int/



5.2.2.5 CIV Flow Table: The CIV Flow Table provides a list of only Civilian operated missions scheduled to execute within the next 7 calendar days. This file is an Excel workbook that has a spreadsheet tabs for every RS ICAO for the next 7 days. This file is only loaded on the Civilian Operators tab of the website.

5.2.2.6 Future Plan: The RS Future Plan provides a list of all Civilian and Military operated missions scheduled to execute between 8 and 14 calendar days into the future. This file is a *.html document that outlines all of the RS missions

5.2.2.7 CIV Future Plan: This output provides a list of only Civilian operated missions scheduled to execute between 8 and 14 calendar days into the future. This file is a *.html document that outlines only the civilian operated RS missions

Mission Coordination Status 5.3

Operators can verify mission profile data accuracy on the website using theFlow 5.3.1Tables and the Future Plans.

If a discrepancy is found then the operator can send an email to the RSFCC for 5.3.2clarification.

Website users can determine the current coordination status of a submitted MRF 5.3.3based on the four possible flight status designations reported in the Flow Table on the website,

5.3.3.1 Requested: This is the default status assigned by EVE to all newly imported missions. This status indicates that coordination has not started on the mission. Missions that have execution dates between 8 and 14 days in the future will have this status.

5.3.3.2 Booked: This status is assigned to a mission when the time slot coordination process has started.

5.3.3.3 Confirmed: This status is assigned to a mission when all slot times have been reserved. When a mission is reported as confirmed this mission is fully authorized to operate according to the mission data on the website.

5.3.3.4 Cancelled: This status is assigned to a mission when all PPR numbers, IFF/Squawk, and call sign have all been cancelled.

Operators are not to call RSFCC and check on the status of a submitted MRF. The 5.3.4mission data will appear on the RSFCC website after the next DISTRO.

If mission profile data is incorrect on the website the operators must submit an update 5.3.5in the form of a new MRF version.



6 MRF Submission Guidelines

Aircraft operators will obtain the call sign from the NAA/NatReps of the TCN they are 6.1.1flying the mission for. The list of approved NAA/NatReps may be found on the RSFCC website. https://isfcc.ncia.nato.int/default.aspx

That call sign is entered into the RSFCC Movement Request Form (MRF) VERSION 0 6.1.2along with the desired mission profile.

Mission dates and times are always in Greenwich Mean Time (GMT/Zulu); do not use 6.1.3local or regional time zones.

The operator submits the MRF V0 to the NAA/NatReps for validation/verification and to 6.1.4make sure there are no scheduling conflicts or duplications.

The NAA/NatReps must ensure the MRF V0 is completely and correctly filled-out 6.1.5before it is sent to the RSFCC for coordination.

The MRF V0 can only be submitted to the RSFCC by an approved NAA/NatReps of 6.1.6the country for which the mission is being completed, but any subsequent version change can be submitted by the aircraft operator.

MRFs with invalid call signs will not be processed and repeated attempts to submit an 6.1.7MRF with an invalid call sign will be reported to the appropriate security agency and NAA/NatReps.

The NAG Call Sign, mission execution date, and MRF version are to be the only 6.1.8components of the email subject line and the MRF excel filename as per the example below.

Email Subject Line: NAG55RS 05 OCT 2018 MRF V0

Excel Filename: NAG55RS 05 OCT 2018 MRF V0.xlsx

The RSFCC will only receive and process completely and correctly filled-out MRFs. If 6.1.9the format and content are not correct the request will be rejected and the NAA/NatRep will be required to fix any issues.

The RSFCC imports mission profile data into Effective Visible Execution (EVE) 6.1.10database where all NATO RS missions are tracked and archived.

The RSFCC coordinates the requested slot-times directly with the 5 NATO RS Airfields 6.1.11in Afghanistan: Bagram (OAIX), Kabul (OAKB), Kandahar (OAKN), Mazar-e-Sharif (OAMS), Herat (OAHR).

Airfields are not to process any slot-time requests coming directly from operators for 6.1.12any mission with an RS call sign.

The RSFCC is the only organization authorized to process and coordinate slot-time 6.1.13requests for missions with an RS Call Sign.

The airfields assign a Prior Permission Required (PPR) number to the slot-time and 6.1.14call sign and then send that information directly to the RSFCC.

Once the RSFCC has received PPR numbers from all of the airfields on that mission 6.1.15an IFF/Squawk code is assigned to the mission.

Any change to a mission after the V0 has been submitted requires a new version to be 6.1.16submitted to the RSFCC for coordination.

https://isfcc.ncia.nato.int/default.aspx