NATO UNCLASSIFIED / RS UNCLASSIFIED
Resolute Support Strategic Flight
Coordination Centre
(RSFCC)
03 DECEMBER 2015
PO Box 90102
5600 RA Eindhoven
Tel; +31 (0) 40 289 8908/8909
Email: amcceindhoven1@abeheh.nl
ANNEX A to STANDARD OPERATING PROCEDURES 1
(ANNEX A to SOP-1)
GENERIC PROCESS OF
RESOLUTE SUPPORT (RS)
RESOLUTE SUPPORT STRATEGIC FLIGHT
COORDINATION CENTRE
(RSFCC)
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-1
NATO UNCLASSIFIED / RS UNCLASSIFIED
RSFCC Role For Coordinating All Strategic RS Flights
This document has been set up as follows:
1. Applicability.
1.1. Main task for RSFCC.
1.2. What RSFCC does not coordinate?
1.3. Limitations for transport of Non-RS passengers and cargo.
2. General RSFCC Procedures.
2.1.
2.2.
2.3.
2.4.
2.5.
2.6.
2.7.
2.8.
2.9.
2.10.
Call Signs (general).
Call Signs for the Coordination of Heavy Airlift Wing Missions.
Call Signs for the Coordination of Strategic Airlift Interim Solution flights.
Call Signs for Tanker Airlift Control Centre (TACC) flights.
Movement Request Form (MRF).
Cargo Information.
Remain Over Night (RON).
Permanent Parking on Civil Ramps.
VIP/VVIP Flights.
Changes to a Mission.
3. Prior Permission Request (PPR).
4. RSFCC Website – Flow Table.
5. National Representatives (NatReps) and National Airflow Authorities (NAA).
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-2
NATO UNCLASSIFIED / RS UNCLASSIFIED
1. Applicability
1.1.
The Resolute Support Strategic Flight Coordination Centre (RSFCC) is the single
coordinating agency for the issue of RS Call Signs, the allocation of Identification Friend
or Foe (IFF) squawks and the negotiation of airfield slot times for all1 strategic, fixedwing flights carrying RS passengers and cargo into, out of and between those Afghan
airfields that require prior permission to land.
1.2.
The following missions are NOT coordinated by RSFCC:
1.2.1. Rotary Wing (RW).
RSFCC does not coordinate Rotary Wing Missions. These ‘In theatre’ Missions
are coordinated at TAAC level. RSFCC will only process these missions in
special situations or emergencies. The use of RS Call Signs for RW Missions is
not authorized.
1.2.2. Non-NATO Civilian Missions
The procedures for non-NATO civilian aircraft operating into, out of and within
Afghanistan are detailed in Republic of Afghanistan’s Aeronautical Information
Publication (AIP) to be found on the Afghanistan Civil Aviation Authority website
at:
http://acaa.gov.af/en/page/civil-aviation-authority/atm/aip---important-information.
RS Call Signs are not to be used for these missions.
1.2.3. USAF Inter-theatre Fixed-Wing (Strategic) Missions
USAF inter-theatre fixed-wing strategic flights are coordinated by the US Tanker
and Airlift Control Centre (TACC).
1.2.4. RS assigned Intra-theatre Fixed-Wing Flights
The Force Movements Control Centre (FMCC) within HQ RS, Kabul, directs
procedures for the coordination of RS Intra-Theatre Airlift System (ITAS) fixedwing flights.
1.2.5. ANA Flights.
Flights in support of the Afghan National Army are ‘in theatre flights’ and are not
in support of RS or a specific TCN. They are not strategic therefore RSFCC has
no coordination responsibility with these missions.
1
As agreed with SHAPE-AMCC and TACC, All USAF Military Aircraft (Grey-Birds) will be coordinated by TACC, including PPR#, IFF
Squawk and slotting negotiations. To maintain coalition awareness, RSFCC will continue receiving TACC mission data by selected SMS
data feed.
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-3
NATO UNCLASSIFIED / RS UNCLASSIFIED
1.3. The following aspects should be considered;
1.3.1. Only cargo and/or passenger flights in direct support of RS are authorized to use
the RSFCC procedures, including obtaining Call Signs, squawk numbers and
coordination. It is a responsibility of the carrier to check and confirm only RS
contracted or assigned passengers and cargo are using these flights.
1.3.2. Passenger and/or cargo for UN tasks, TCN Embassies, NGOs and charities are not
legitimate users.
1.3.3. By using the RSFCC process, carriers are exempt landing fees and no routine
customs inspection is carried out. Mixed cargo e.g. partial loaded for RS with the
remaining capacity used for non RS (e.g. commercial) loads is not legitimate and
contrary to established agreements. The carriage of commercial cargo i.e. non RS cargo
is strictly prohibited when operating on a RS (NAG) call sign. Operators assigned a RS
(NAG) call sign to meet a RS air cargo contract are to ensure no commercial freight is
loaded to an aircraft arriving into Afghanistan using a RS NAG) call sign. Spot checks of
aircraft are undertaken at RS airfields. Any violation or indication of mixed loads will be
reported to ACAA for investigation- no exceptions will be granted.
1.3.4. The sharing of an AC between contribution Nations for different contracts is allowed.
Thus one nation contracting an AC can share spare capacity with another RS
Nation; this is termed as a Shared load. Only RS freight can be carried, no civilian
commercial freight is to be carried. The Nation with the majority of freight onboard is
to assign the RS call sign.
1.3.5. Transit load. An AC carrying RS freight but with freight in transit which is NOT to be
offloaded in Afghanistan. Caveats apply: separate set of documents for transit load,
No Dangerous Goods (DG) and no prohibited/sanctioned cargo.
Operators who abuse “RS Call Signs” to support the above excluded items will be
denied further coordination by RSFCC and reported to ACAA for investigation.
2. RSFCC Operating Procedures
2.1.
Call Signs (general) In order to submit a Movement Request Form (MRF) VERSION 0
for an RS mission, military and civilian operators must first obtain a RS Call Sign from
the National Representative (NatReps), or the National Airflow Authorities (NAA), of the
Nation they are flying the mission for. The list of NatReps may be found on the RSFCC
website. (https://isfcc.ncia.nato.int/default.aspx).
2.1.1. The two-letter codes of the RS Call Signs are issued by RSFCC and are only to
be used for RS Strategic Flights in coordination with RSFCC. However, based
upon established procedures, some Strategic Supporting Flights using
Afghanistan Stationed but non-ITAS Assigned Aircraft are authorized to use the
RSFCC procedure and RS Call Signs.
2.1.2. Dates and Times are always in Greenwich Mean Time (GMT)/Zulu (Z)-time; do
not use local or regional time zones.
2.1.3. All aircraft flying an RS mission must use a valid RS Call Sign in the format
NAGYYXX, where YY is a 2 digit number allocated by the NatReps/NAA, and XX
are 2 letters allocated to each NatReps/NAA, by RSFCC and changed every
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-4
NATO UNCLASSIFIED / RS UNCLASSIFIED
month. MRFs with invalid Call Signs will not be processed and repeated attempts
to issue an MRF with an invalid Call Sign will be reported to the appropriate
security agency and NatReps/NAA. For RS Strategic Air Transport, RSFCC is
the only agency allowed to issue RS Call Signs.
2.1.4. RS Airfields are not to process any Slot Request or provide support for any
Mission with an RS Call Sign coming directly from Operators; only RSFCC is
authorized to process and coordinate Slot Request for missions with an RS Call
Sign.
2.1.5. RS Call Signs are issued by RSFCC to the NatReps/NAA of each RS TCN. The
NatReps/NAA is responsible for further distribution of these Call Signs.
2.1.6. All Call Signs change on a monthly basis to prevent illegal use. The Call Signs for
each month are sent to the NatReps/NAA at least two months before the month
of use.
2.1.7. If a mission crosses a calendar month, the Call Sign for the month in which the
flight makes the first touchdown in Afghanistan will be used. For example, a
mission departing on the 31st of the month and lands on the 1st of the new month
uses the new month’s Call Sign. The only exception to this is where, due to
diplomatic clearance restrictions, RSFCC may accept a Call Sign from the
previous month. For example, a flight could be delayed from the 30th to the 1st of
the following month; RSFCC will accept the old Call Sign if it is not possible to
change the Call Sign due to diplomatic clearance procedures.
2.1.8. RSFCC Call Signs are not to be used for 2 separate flights on consecutive days.
If this is attempted and the first flight is delayed there is the possibility that two
flights with the same Call Sign will operate on the same day. The same Call Sign
can be used for a mission that begins on one day and is completed on the next,
but flights that operate on behalf of the same nation later that day will need to
use a different Call Sign.
2.1.9. The RS Call Sign and mission date are to be included in the subject line of all email correspondence with RSFCC. (i.e. MRF V0 NAG55RO 25DEC15)
2.2.
Call Signs for the Coordination of Heavy Airlift Wing (HAW) Missions.
2.2.1. HAW C-17 missions operating into and out of Afghanistan require an RS Call
Sign, PPR co-ordination and an IFF squawk code.
2.2.2. The RS Call Sign will be provided by the NatReps/NAA of the nation whose cargo
is being carried, in accordance with RSFCC Operating Procedures.
2.2.3. When the aircraft load comprises cargo from more than one nation, the nation
funding 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.
2.2.4. When other legs of this mission are in support of another nation, another Call
Sign is to be used (and coordinated accordingly).
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-5
NATO UNCLASSIFIED / RS UNCLASSIFIED
2.3.
Call Signs for the Coordination of Strategic Air Lift Interim Solution (SALIS) Chartered
An-124 in support of SALCC participating Nations. For more information see the SALCC
tab on MCCE Website. (http://mcce-mil.com/)
2.3.1. The Strategic Air Lift Coordination Cell (SALCC) is a multinational military
organization, established on 23rd of January 2006. The permanent staff of the
SALCC is located in the building of the MCCE at Royal Netherlands Air Force
Base Eindhoven (The Netherlands). The aim of SALCC is to manage the SALIS
(Strategic Air Lift Interim Solution) contract on an executive level in an efficient
and effective way. The thirteen (13) participating nations in the SALIS-Contract
are Belgium, Czech Republic, Germany, Finland, France, Greece, Hungary,
Luxemburg, Norway, Poland, Slovakia, Slovenia and Sweden. The assured
access guarantees the assured availability of two (2) AN124-100 under part-time
charter for any of the participant’s national purpose, and the assured availability
of up to six (6) AN124-100 aircraft on priority call for the rapid deployment of
forces in support of NATO/EU operations
2.3.2. The RS Call Sign will be provided by the RSFCC to SALCC and subsequently the
RSFCC process will be followed. Using this methodology inbound and outbound
mission and all mission legs will use one RS Call Sign. The Coordination for
these missions, based on a multinational usage, will be centrally coordinated by
SALCC.
2.3.3. Each month SALCC will inform RSFCC for which nations the mission and
mission legs have been performed.
2.4.
Tanker Airlift Control Centre (TACC), 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 refuelling and aero medical evacuation operations around the world. TACC is the global
air operations centre 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. The organization is capable of seamlessly transitioning from dayto-day operations to contingency support or disaster relief. TACC issue specific Call Signs for
these kinds of missions. At several RS Airfields, the USA has designated US-Lanes with
their own personnel and equipment and all slot allocation for these lines is solely
coordinated by TACC with the appropriate Airfields. RSFCC and TACC can, if required,
arrange for exchange of these facilities.
2.5.
Movement Request Form (MRF). Two (2) different MRF templates (6 legs and 12 legs)
can be downloaded from the RSFCC website via the “Documents” tab next to the “home”
tab. (https://isfcc.ncia.nato.int/Pages/Documents.aspx). MRFs must be send to the
RSFCC as a soft copy (only via email on internet or NATO Secret WAN). Only one RS
mission request may be submitted in each e-mail. E-mails containing multiple MRFs are
problematic for our processing and filing and will be rejected.
2.5.1. Timings for submission (General). RSFCC will accept MRFs up to 14 days prior
to mission execution and they should be sent at least 24 hours before the
estimated departure time of the flight. However, on a case by case basis and if
capacity is available the RSFCC may try to accommodate the request, but
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-6
NATO UNCLASSIFIED / RS UNCLASSIFIED
Operators should be aware that airfield slot availability is very restricted this close
to execution. The RSFCC is using the First-Come-First-Served (FCFS) system.
The Operators are starting to process the MRFs 7 days ahead of execution.
2.5.2. Visibility of the coordination. To inform all users frequently, an extract of the
planning data package, including the status of your missions as submitted in your
MRF, will be updated on the RSFCC website every four hours (see paragraph 4).
Operators are not to call RSFCC asking ‘have you received my MRF’. Check the
website and subsequently the data entered. If data is incorrect, submit an
updated MRF. RSFCC will NOT perform any manual alteration of data requested
verbally e.g. typing new submitted data. We need a new MRF to maintain
legitimate documentation.
2.6.
Cargo information. To provide maximum cargo load visibility for airfield management and
to the Combined Air Terminal Operations (CATO) centres 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.
2.6.1. Due to safety concerns, load handling and parking restrictions, it is essential that
hazardous goods are specified with the correct UN Class, UN Number and the
Net Explosive Quantity (NEQ) where appropriate. Accurate hazardous goods
information is critical at Kabul where hot cargo parking is very restricted.
Explosives are declared as NEQ (Net Explosive Quantity) when described in the
cargo spreadsheet, separate to the gross weight.
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
2.6.2. The cargo spreadsheet in the MRF cargo information tab will automatically
calculate the items, weight and properties of dangerous cargo and put the totals
on the front page of the MRF. The quantity and weight on the front page of the
MRF should not be changed manually because that will cause an error in the
formula. Please list the ‘most dangerous goods’ which requires handling on the
DAC-ramp as the first Dangerous Goods Item in your information.
2.6.3. Only correctly filled out and completed MRFs will be entered into the RSFCC
processing system. If the MRF is not filled out correctly or completed, RSFCC will
send it back to the email address where it came from, together with an
explanation but without processing it.
2.6.4. If a mission’s cargo information is not available until shortly before the flight,
operators should still submit their MRF as early as possible (within the 14 days
pre-flight window) with the estimated cargo. Cargo information updates are
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-7
NATO UNCLASSIFIED / RS UNCLASSIFIED
important and encouraged and can be submitted whenever they become
available.
2.7.
Remain Over Night (RON). When a flight needs to remain over night at an airfield, this
must be requested in the Remarks section of the MRF, together with details of when the
flight will be departing the airfield and also with the next destination. For example, “RON,
Departs OAKN 24 Jul 2015 0330Z to UBBB” Airfields often require justification for a
RON flight. Provide the explanation in the e-mail submission. For example, “NAG01XY
04 Dec 15 requires RON to accommodate VIP visit”.
2.8.
Permanent Parking on Civilian Ramps. 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.
2.9.
VIP / VVIP flights. A VIP is considered any passenger equivalent to a one-star general
and a VVIP is considered anyone equivalent to a two-star general or above. Always list
the name, title, rank or position of the VIP and provide a point of contact name and
telephone number.
2.10. Changes to a mission. The RSFCC Controllers are not allowed to make alterations to a
MRF/PPR Form manually, so operators have to submit a MRF for amendments such as
cancellations or slot time changes. Therefore, all MRFs must contain a 24-hour Point of
Contact (POC). This POC must be available for communication with RSFCC by phone
and email all times. Immediate responses to RSFCC communications are crucial for the
successful management of all flights. If a flight cannot be executed as requested,
RSFCC will inform the operator as soon as possible and will provide an offer of the best
possible alternative. Do not use/reuse previous assigned PPR numbers and SQUAWK
codes for the modified mission unless this is announced by RSFCC.
2.10.1. The following changes to a mission are of special interest and require additional
coordination:
2.10.1.1.
A delay of a mission by 24 hours or more constitutes a cancellation of
the submitted MRF2, and RSFCC will require the operator to send an
e-mail cancelling the original flight, and another e-mail with a new
MRF for the rescheduled flight. In case the original mission was a
priority or pre-allocated mission, this change will result in losing the
priority status. Be cautious when your Slot Time Request results in
the mission being executed the next calendar day.
2.10.1.2.
A change of mission profile, e.g. adding new legs, will only be
processed if this change is approved by the NatRep who has
awarded you the contract to perform this mission. Before RSFCC will
process this modified mission, RSFCC needs a confirmation by your
NAA or NatReps for this change. Information like ‘we have got
2
Only for some specific Nations and due to diplomatic clearance process complications RSFCC will accept to remain
the usage of the original RS Call Sign.
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-8
NATO UNCLASSIFIED / RS UNCLASSIFIED
approval from NAA or NatReps is not acceptable. Initially RSFCC will
retain approved information e.g. PPR# for already arranged slots.
2.10.1.3.
If an operator is frequently cancelling legs, this will be assessed as
improperly blocking slots for all other users and may result in limited
support or restriction being placed on the offending operator.
2.10.1.4.
The change of Aircraft type must be performed by submitting a new
MRF version3 here NatReps must be informed of all changes with
contractual implications. RSFCC will coordinate with the Airfield(s)
involved. Especially pay attention when Aircraft Types are changed
into larger aircraft requiring additional parking space or enhanced
servicing. It will be an Airfield decision if they are able to support your
request.
2.10.1.5.
The change of Aircraft Registration (Tail Number) must be performed
by submitting a new MRF version4; here NatReps/NAA must be
informed of all changes with contractual implications. It will be an
Airfield decision if they are able to support your request. An aircraft
registration is a unique alphanumeric string that identifies a
civil/military aircraft. In accordance with the Convention on
International Civil Aviation, all aircraft must be registered with a
national aviation authority and they must carry proof of this
registration in the form of a legal document called a Certificate of
Registration at all times when in operation.
2.10.1.6.
Changes to Cargo and Cargo Types must be requested by
submission of a new MRF; especially when the original MRF (v0) was
for non dangerous, and/or for non support required unloading/loading
requirements etc; this change must be clearly stated in amendment emails being provided with new MRF. It will be an Airfield decision if
they are able to support requests.
2.10.1.7.
Visibility of changes. After the submission of initial MRFs, all changes
will be visible at the RSFCC website. Do not call but check the
Flowtable on the website.
2.10.2. Registration of cancellations. To aid identification of abuse of RSFCC
procedures, RSFCC registers the reasons for cancellation. On a regular basis, a
report of cancellations will be sent to the military authorities of the TCN. The
intention is to provide maximum logistical support to RS but if operators’ practices
are seriously harming these efforts, we will no longer process their flight requests.
3.
3
4
Prior Permission Request (PPR) To ensure that suitable parking and ground handling is
available at Afghan airfields, a PPR number must be issued for every Airfield to be visited
within a mission. RSFCC will send a PPR request form to each airfield on a mission’s
itinerary on behalf of the operator, and according to each airfield’s submission guidelines.
RSFCC is the only authorized Coordination Centre for aircraft operating under an RS Call
Signs to establish any approval. Airfields will not accept any request for processing of a
mission using an RS Call Sign unless requested by RSFCC.
Even these type of changes are not to be altered by RSFCC Controllers; RSFCC require an updated MRF.
Even these types of changes are not to be altered by RSFCC Controllers; RSFCC require an updated MRF.
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-9
NATO UNCLASSIFIED / RS UNCLASSIFIED
3.1.
Afghan Air fields’ inbound flights will be allocated a window of 15/30 minutes either
side of their requested arrival time. Any aircraft that arrives outside of that window
may be turned away.
3.2.
Operators are not allowed to submit PPR requests direct to the airfields. The
Aeronautical Information Publication (AIP) for Afghanistan clearly states that RS
missions will be coordinated with airfields through RSFCC. Once the necessary PPR
number(s) has been obtained from the destination airfield(s), RSFCC will assign an
IFF/Squawk number to the mission, without which the aircraft will not be allowed to
cross into Afghan airspace.
3.3.
Visibility of the approved PPR number and the applied Squawk number will be visible
at the RSFCC website on the Flowtable. Do not call, check the website.
4. RSFCC Website – Flow plan. All data related to received MRFs and current status for NATO
Nations and for RS Agencies in and around Afghanistan is available on the NATO SECRET or
MISSION SECRET Wide Area Network and within this system in the EVE software
environment.
4.1.
To create visibility for non-NATO users, TCN outside the NATO and RS Secure network
and for all Operators, an extract of EVE data is displayed and updated 6 times per day
(0000z / 0400z / 0800z /1200z / 1600z / 2000z) within the RSFCC Website.
4.2.
Military users can check the status of a flight under “MIL Flowtables” and civilian users
can link to “CIV Flow tables” on the RSFCC website. The flight information is protected
by a username and password. Operators are to contact the NatRep of the nation that
they are flying for website access, who will in turn request a username and password
from RSFCC.
4.3.
Missions up to 7 days out are listed in the “MIL Flow table” or “CIV Flow table” MS Excel
files.
4.4.
RSFCC is responsible for publishing the IFF/squawks and PPR numbers and for
confirmed flights in the Flow Plan and Future Plan.
5. National Representatives (NatReps.) and National Air Flow Authorities (NAA).
5.1.
National Representatives (NatReps). Act on behalf of National MODs, each RS TCN
will appoint a NatRep who have specific responsibilities for the coordination of military
and/or contractor-operated flights into and out of airfields in Afghanistan. Nations
wishing to stand up a NatRep should contact Chief RSFCC via the contact details given
on the RSFCC website. RSFCC maintains a list of all NatRep contact details on the
RSFCC website; NatReps are to inform RSFCC Reports and Briefings Section of any
change to NatRep details.
5.2.
National Airflow Authorities (NAA). Some nations have a NAA system implemented. By
sending the MRF from civilian and military operators via the NAA, the NAA is
responsible for submitting only approved national missions.
5.3.
Specific Responsibilities of NatReps/NAA:
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-10
NATO UNCLASSIFIED / RS UNCLASSIFIED
5.3.1. Forwarding selected Call Signs to prime contractors ONLY.
5.3.2. Verifying the credentials of contractors requesting Call Signs for missions in
support of the NatReps/NAA RS contingent.
5.3.3. Verifying that the load is constituted entirely of RS cargo/passengers.
5.3.4. Ensuring that the contractor is operating within the terms and conditions of their
contract; maintaining liaison with contract management staff including obtaining
copies of all contracts.
5.3.5. Ensuring that the contractors work within the procedures detailed on the RSFCC
and Afghan Ministry of Transport and Civil Aviation websites.
5.3.6. Forwarding to RSFCC Reports and Briefings Section requests from prime
contractors for RSFCC website User Name and Passwords to allow them access
to flight information.
5.3.7. Checking the RSFCC Future Plan and Flow Table regularly to ensure that they
have personally issued all of their Call Signs in-use.
5.4.
NatReps/NAA Call Sign Issue Process
5.4.1. NatReps/NAA receives requests from contractors for Call Signs for RS missions.
They check their list of authorized contractors to verify their entitlement to a Call
Sign, and that the load is within the provision of the contract.
5.4.2. NatReps/NAA issue Call Signs to the requesting contractor who may, in turn, issue
single Call Signs to sub-contractors if required. NatReps/NAA should not issue
blocks of Call Signs to contractors.
5.4.3. NatReps/NAA are to maintain visibility of the flights for which they have issued Call
Signs, 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.
If you have any questions concerning information in this SOP, Please
contact the RSFCC Controllers (amcceindhoven1@abeheh.nl or +31 (0)
40 289 8908/8909) who are 24/7 available.
NATO UNCLASSIFIED / RS UNCLASSIFIED
ANNEX A to RSFCC SOP 1
Page A-11