Download as pdf or txt
Download as pdf or txt
You are on page 1of 9

19 FEB 24 PAGE 1 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

This information covers a developing event: further versions will likely follow. Check Dashboard / Daily
Brief for updates. Please report any additional information you have to team@ops.group. Thank you!

TO: ALL OPSGROUP MEMBERS


ATTN: OPERATING FLIGHT CREW, FLIGHT OPS DEPARTMENTS, SAFETY DEPARTMENTS

Quick Summary – ATC Conflict in Somalia

• This affects aircraft transiting the Mogadishu FIR


• Enroute aircraft are being addressed by competing ATC units on the same frequency.
• Numerous aircraft have received climb/descent instructions from unauthorized ATC units.
• Location: Primarily within radio range of Hargeisa (VHF 132.5), also via HF (11300)
19 FEB 24 PAGE 2 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Key information for Flight Crew


In the past week, OPSGROUP has received at least 10 reports of aircraft within the Mogadishu FIR being
contacted by a second ‘controller’ on the same frequency, issuing conflicting instructions.

Crews have been issued climb and descent clearances, that are not from the sector controller. Incidents have
been reported mostly in the northern part of Mogadishu airspace.

The situation emanates from a political dispute between Somaliland and Somalia, two different countries, though
the former does not have international recognition. Both countries now claim authority over the Mogadishu FIR.

Excerpt, full map on first page..


19 FEB 24 PAGE 3 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Situation
OPSGROUP has now received 10 separate reports (and counting) from flight crews that have experienced this.

Common to the majority of events are the following:

• Initial contact with Mogadishu Control is normal.


• Subsequently (5, 10, 20 minutes later), another voice asks for waypoint estimates
• In some cases, a climb or descent instruction has been issued to crews by the second “controller”
• One crew reports three different “controllers” on one frequency
• This has happened on VHF 132.5 and HF 11300

Full crew reports are appended to this note.

An analysis follows after this.


19 FEB 24 PAGE 4 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Crew/Operator Reports

Feb 17, 2024 Embraer Lineage 1000. The ATC controller and another airline in the sector today was aware. We
had 3 different "controllers" on the frequency during the transition. 2 were fake. They also asked for ETA at next
way points and routing, like the legit controller. One asked us to descent or climb due upcoming traffic. The real
controller picked that transmission up and asked us to maintain level and disregard VHF and stay on CPDLC.
FlyDubai was in the sector, one was commenting, "Sorry you got stepped on by the illegal controller" - the other
questioning if he had a lady controller working with him today. The answer was a clear no. That lady was the one
we had initial contact to, and she questioned our exit point and wanted revised ETAs.

Feb 17, 2024 Boeing 777. We experienced the unlawful communication on a B777 to Nairobi. Entering Mogadishu
from the Oceanic portion of Sanaa FIR we were lucky to establish the first contact with the real controller. Only after
approaching the land we heard the fake controller asking for ETAs. He was quite convincing in the act, however we
were anticipating the issue after reading the enroute and company NOTAMs. We were asked by the real controller
to continue via CPDLC.

Feb __, 2024 Boeing 787. On VHF 132.5, we were required to give onward estimates on two different occasions
and at one point approximately 15 minutes to Sanaa FIR a call came through instructing us to descend to FL330
due conflicting traffic at position IMKAD. To confirm identity of the ATS unit we requested a Selcal check without
giving the code itself, with the assumption that a genuine ATS unit would have this on the filed CFP. This was not
forthcoming. Attempts were made to call Sanaa and once contacted his only request was we climb and maintain
FL370 and he indicated that he relayed our position to Mogadishu. He couldn’t confirm the earlier instructions from
“Mogadishu ” to descent. Shortly after this transmission we were request to provide overflight permission number
in the muscat fir. This was relayed and the flight progressed without further incidences.

Feb 2024 Boeing 787. Westbound towards Mogadishu, between waypoints VUTAS and UNRED when the crew got
an HF call on 11300 identifying as Mogadishu control. At the same time another voice claimed to be Mogadishu
ATC and requested to switch to 8879 (HF) using CPDLC with HCSM.

Feb 2024 Boeing 777-200. On VHF around waypoint DAROT when someone called the flight on 132.5 and asked
the crew for further ETA to some waypoints along the route. Later Mogadishu control contacted the crew and asked
them to ignore the person who spoke with them and to switch to CPDLC.
19 FEB 24 PAGE 5 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

18 Feb, 2024 Multiple reports. A collated report of incidents furnished by XXX, provided to OPSGROUP, lists 6
different occurrences during the week ending Feb 18, 2024. 1st aircraft is over IMTIS waypoint. 2nd ETH644 at
MERMI. 3rd UAE719 approaching DAROT. 4th ABY735 at position MUSBI. 5th AXY46K at position AVAKA, also
AVEDA. In all cases the aircraft were contacted by a second “controller”.

If you have similar reports to share, please send to team@ops.group. All operator and crew
information is de-identified, these are shared only for the purposes of helping to understand the
issue.
19 FEB 24 PAGE 6 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Analysis

The background to the situation is an escalating political dispute between Somaliland and Somalia. Somaliland
has been an independent country since 1991, but without international recognition.

Somaliland has to date maintained control over its airports, but Somalia controls the upper airspace from
Mogadishu. In January 2024, Ethiopia signed an agreement with Somaliland, essentially exchanging port rights on
the Red Sea for recognition of their country. This was met with condemnation by Somalia.

Somalia, in response, began restricting movements into Somaliland by way of denying airspace entry to the
Mogadishu FIR in some instances. This has led to Somaliland declaring its right to exercise control over their
airspace.

The net result is an airspace dispute between the two territories. Both Somalia and Somaliland now claim the right
to control traffic. This is why crews have been contacted by other “controllers” on 132.5 (VHF) and 11300 (HF).
Although it is likely that these other “controllers” are genuine Air Traffic Controllers, they are operating outside their
area of jurisdiction as things stand.

Currently, the authority over the entire Mogadishu FIR is Mogadishu Control. They remain the sole authority to
control, coordinate, and provide ATS services in the Upper FIR.

The secondary transmissions are coming from Hargeisa in Somaliland. Although the motive for these
transmissions can be understood, they present clear danger to enroute traffic. The transmissions appear to
19 FEB 24 PAGE 7 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

attempt to mimic Mogadishu rather than present as “Hargeisa Control”, “Somaliland Control”, or any clear
differentiator from Mogadishu.

It would also appear from the reports that we have received, that the control instructions are not being issued to
de-conflict traffic, but rather to create confusion. This may be an effort to draw attention to the airspace issue, but
could have tragic consequences.

For flight crews, we follow with some guidance to mitigate the situation.

The situation is volatile and may escalate. On Sunday, February 18, an AIS Officer from Somaliland, working in
Mogadishu, was found dead at his home. His death appears related to this situation.

Avoidance of Mogadishu airspace would provide ultimate safety, and if the situation continues, would be wise.
19 FEB 24 PAGE 8 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Guidance & Procedures


The following are only suggested guidance and procedures, to mitigate and deal with the situation.

Awareness of risk location

All reports have been within the Mogadishu FIR.

Traffic overflying or intending to overfly Somaliland is most at risk.

For specific locations, see the map.

Recommended Actions
1. If possible, avoid the Mogadishu FIR.

2. If entering the airspace, expect secondary ATC transmissions from Hargeisa.

3. Limit any contact with Mogadishu to CPDLC only. Only controllers in Mogadishu have access to CPDLC.

4. Do not accept any level changes without ensuring they are genuinely from Mogadishu Control.

5. Avoid requesting any level changes while within the Mogadishu FIR.

6. Listen out on 126.9 (IFBP) and follow the IFBP procedure.

7. Note that related NOTAMs issued by Somalia may not present the full picture, or be updated regularly.
19 FEB 24 PAGE 9 SOMALIA ATC CONFLICT OPSGROUP RISK WARNING

ISSUED BY OPSGROUP TEAM


RISK WARNING EMAIL TEAM@OPS.GROUP
WHATSAPP +1 747 200 1993
SOMALIA ATC CONFLICT
19 FEB 2024 Version 1
.

Further updates

This information covers a developing event: further versions will likely follow. Check your members
Dashboard / Daily Brief for updates.

Much of the information is compiled from member feedback. If you have any expertise to share, or
information to add – please email team@ops.group, or send a WhatsApp message to +1 747 200 1993.

Thank you!

Contacts / Links

• Contact OPSGROUP Team: team@ops.group | WhatsApp: +1 747 200 1993


• Member Dashboard: https://ops.group/dashboard
• Crewroom: https://ops.group/dashboard/about-crewroom/

You might also like