Coding decisions on state forces, political militias, external forces, and more
Published on: 28 February 2023 | Last updated: 26 September 2024
After staging protests against the removal of fuel subsidies, the Houthi Movement overran the Yemeni capital, Sanaa, in September 2014. Shortly after, the Peace and National Partnership Agreement was signed, stipulating the formation of a technocratic government, including advisors from the Houthis and the Southern Movement (al-Hirak). In January 2015, the Houthis put President Abdrabbuh Mansur Hadi, Prime Minister Khalid Bahah, and several cabinet ministers under house arrest, leading to their resignations and precipitating the constitutional crisis. The Houthis seized the opportunity to dismiss the government and form an executive body known as the Supreme Revolutionary Committee, chaired by Muhammad Ali al-Houthi. In the following weeks, Saudi Arabia and its allies launched a military intervention to restore the government of President Hadi and prevent Aden from falling to the Houthis. These events marked the beginning of the Yemen conflict, which has killed thousands of people and prompted a major humanitarian crisis.
After seven years of war, in April 2022, a nationwide United Nations-mediated truce took effect in Yemen, resulting in a substantial de-escalation and reduction of activity by the warring parties. However, a low-intensity conflict has since surfaced, continuing to threaten civilian lives and uphold consistently severe violence. Alongside these domestic developments, the Houthis have increasingly shifted their strategic focus toward the Red Sea, causing major disruptions to international shipping lanes.
The conflict presents some important methodological challenges for the recording of political violence: violent events unfold in a number of ways, which are not replicated in other contexts; a variety of actors partake in the conflict, reflecting the highly volatile and fragmented socio-political environment; and media coverage often suffers from reporting biases and little access to Yemen’s most remote regions. The report aims to outline ACLED’s efforts to address these challenges and accurately capture manifestations of violence during the Yemen conflict.
ACLED’s work is conducted in collaboration with the Yemen Data Project (YDP), which provides contributions to enhance conflict monitoring and data sharing. Separately, YDP collates data on Saudi-led Coalition airstrikes in Yemen since 2015. In 2024, ACLED and YDP strengthened their partnership by launching the Yemen Conflict Observatory (YCO).
What does ACLED cover in Yemen?
ACLED’s coverage of political violence and protest in Yemen spans from January 2015 to the present.
Yemen’s conflict environment is known to be one of the most volatile in the region. The current conflict, with its wider implications for the region, has added complexity to an already fractured political setting.1Adam Baron, ‘Mapping the Yemen conflict,’ European Council on Foreign Relations, 19 October 2015
As a result, ACLED records a wide range of violent events, including air or drone strikes and armed battles between opposing factions, as well as typically less reported episodes like tribal or communal clashes, assassinations, bombings — either suicidal or remotely-activated — and peaceful or violent demonstrations. ACLED does not track criminal or domestic violence, nor does it record deaths from famine or diseases.
What does ACLED cover in Yemen?
As a consequence of a highly volatile conflict environment, ACLED has recorded more than 700 distinct conflict agents operating in Yemen since 2015. Many of these actors defy traditional classifications, and require further scrutiny:
- ACLED treats the forces allied with both the Internationally Recognized Government (IRG) and the Houthi-led de facto authorities in Sanaa (DfA) as state forces. It is important to note that the classification does not imply legitimacy but rather acknowledges the fact that there currently exist two distinct governing authorities exercising control over different portions of the Yemeni territory. The actor names and accompanying regime years of these two authorities change in the dataset to reflect internal significant developments over the course of the conflict. For example, the IRG is identified as Government of Yemen (2012-2022) Hadi and then as Government of Yemen (2022-) Presidential Leadership Council. The DfA is identified as Government of Yemen (2015-2017) Houthi-Saleh and then as Government of Yemen (2017-) Houthi only from 2017. Within these overarching authorities, military, or paramilitary actors often maintain no more than a formal relation with the government — such as in the case of the Elite Forces in Hadramawt2United Security Council, ‘Letter dated 26 January 2018 from the Panel of Experts on Yemen mandated by Security Council resolution 2342 (2017) addressed to the President of the Security Council,’ 26 January 2018, p.19 — or may have split from their former allies, the Saleh-led Republican Guard being the most notable case. To reflect this fragmentation, key military, and security actors within the IRG and the DfA are identified by their specific names (e.g. Military Forces of Yemen (2015-2017) Houthi-Saleh – Republican Guard).
- Political militias are a primary agent of violence in Yemen. They include a wide range of armed groups that operate independently, in cooperation with state forces, or as the armed wing of political parties or rebel factions. Although some might be commonly regarded as government forces, they operate outside the formal lines of military command. A notable example is the Joint Forces on the West Coast, a coalition of militias active along the western coast that brings together the Giants Brigades, the Tihama Resistance, and the National Resistance (Guards of the Republic). Similarly, forces affiliated with the Southern Transitional Council (STC) are coded as political militias until the nomination of the president of the STC, Aydarus al-Zubaydi, as a member of the PLC in April 2022. Since April 2022, they have been coded as state forces under the PLC umbrella. Forces affiliated with the STC remain identifiable throughout the various phases of the conflict through the presence of “STC” in their name (e.g. Police Forces of Yemen (2022-) Presidential Leadership Council – STC Aden Security). Meanwhile, the Giants Brigades and the National Resistance (Guards of the Republic) remain coded as political militias. Although their respective leaders, Abdulrahman ‘Abu Zuraa’ al-Muharrami and Tariq Saleh, were also nominated as members of the PLC, the forces were never officially integrated into the IRG command-and-control structure. The Popular Resistance and the Southern Resistance also identify composite cartels of local actors operating across much of central and southern Yemen, often in conjunction with, or at the behest of, state forces. Often subsumed within the above-mentioned larger coalitions, armed wings of Yemen’s political parties — including the General People’s Congress (GPC) or the Islah Party — are also recorded as political militias.
- Compared to other conflict contexts involving national-level contestation, like in Syria, the number of actors classified as rebels in Yemen is relatively low. This is because the main ‘rebel group’ active in Yemen — the Houthis — transformed into a state actor following the takeover of the capital Sanaa and its institutions and the formation of the Supreme Revolutionary Committee in February 2015. The rebel groups coded in Yemen include the Southern Movement, and Islamist armed groups like al-Qaeda in the Arabian Peninsula (AQAP) and the Yemeni branch of the Islamic State (IS).
- Tribal, clan, or other communal groups are coded when reported to be operating ‘on behalf of’ their communities, and not when fighting within the ranks of the army, of rebel groups, or of larger coalitions. These actors make up the vast majority of all actors recorded in Yemen, although they are typically reported to be involved in a limited number of events.
- External forces include both forces of foreign governments and private security operators. The Saudi-led Coalition is coded using the tag name of “Operation Decisive Storm” from 26 March 2015 to 21 April 2015 and “Operation Restoring Hope” from 22 April 2015 onwards, with the participating countries reportedly involved in an event recorded as associated actors (despite leading the coalition, Saudi forces have not been directly involved in each event). In a number of cases, the coalition operates in conjunction with Yemeni ground forces, either state forces or militias, and is therefore coded as an associated actor. The United States, which has operated in Yemen with drones and ground forces, is coded as a separate actor.
- Similarly, ACLED aims to record the political, tribal, or societal identity of civilian actors. Doing this allows users to track specific trends in civilian targeting and their exposure to the conflict. Among the civilian groups most regularly targeted and recorded by ACLED as associated actors, are fishermen, farmers, clerics, tribal shayks, and members of political parties like the GPC and Islah.
How are events sourced?
Each week, researchers from ACLED and our partner organization YDP review hundreds of Arabic and English language sources to provide the most comprehensive database on political violence in Yemen. Over 600 local and foreign media outlets and news agencies have been used to record political violence and protest events in Yemen since 2015. In addition, selected social media accounts are monitored for information on events in hard-to-access contexts, while reports produced by reputed international institutions and nongovernmental organizations supplement the regular coding process.
Nearly two-thirds of events recorded since 2015 were sourced through ACLED’s partnership with YDP. YDP shares news reports outlining relevant political or conflict dynamics with ACLED researchers; ACLED researchers then code in accordance with ACLED’s interpretation of political violence, and supplement coding through the review of a multitude of additional sources to account for reporting lags or to capture additional events. This extensive monitoring effort has allowed ACLED and YDP to provide the most comprehensive coverage of political violence across Yemen, in an attempt to adequately address the multiple challenges that both local and foreign media face in their daily reporting. 3Zainab Sultan, ‘Why the press struggles to cover the war in Yemen,’ Columbia Journalism Review, 2 September 2019Among these challenges are that all warring parties have attempted to manipulate the war narratives by capturing independent media and state-owned news agencies, as well as actively polarizing public discourse.4Afrah Nasser, ‘The Yemen War, Media, and Propaganda, Atlantic Council, 3 May 2017 Media stations have been targeted by destructive violence,5Maya Oppenheim, ‘Yemeni journalists and their three children killed in Saudi-led airstrikes in the capital of Yemen, The Independent, 12 February 2016 government repression severely hampers the ability of local journalists to report independently,6Joshua Holmes, ‘Radio Becomes New Battlefield in Yemen War,’ The Media Line, 28 August 2019and international media access continues to be limited, resulting in often inaccurate accounts of the conflict.7Kareem Fahim, ‘The deadly war in Yemen rages on. So why does the death toll stand still?,’ The Washington Post, 3 August 2018 According to Yemeni researcher and journalist Afrah Nasser, “[a]s a result of the hindered and biased media landscape, both the international community and, more particularly, the Yemeni public receive a distorted picture of the Yemen war.”8Afrah Nasser, ‘The Yemen War, Media, and Propaganda,’ Atlantic Council, 3 May 2017
In this highly polarized and often restricted media environment, the data collection relies on a wide spectrum of sources that, when triangulated, account for the multiple partisan and geographical biases. Overall, more than 90% of events recorded by ACLED are sourced through Yemeni media (mostly national); most of these are sourced via ACLED’s partnership with YDP. These include the official media channels of warring parties (i.e. the governments’ respective news agencies), the Houthi-affiliated al-Masirah TV and Ansar Allah Media Center, the National Resistance (Guards of the Republic)-affiliated 2 December News website, as well as national and local outlets displaying a variety of political leanings.
These groups are partisan in the conflict and, as such, they might have incentives to share distorted information. However, relying merely on other official or independent sources risks introducing another type of bias into the data — namely the recording of violence only in areas where such sources have access or have vested political interests. For example, investigations conducted by Bellingcat9Bellingcat, Bellingcat Yemen Project, 2019 and the Yemeni Archive10Yemeni Archive, ‘Medical Facilities Under Fire’, 1 September 2019 have shown that official Saudi-led Coalition sources have often downplayed or deliberately obscured the impact of airstrikes on civilian populated areas, and that only partisan media sources or social media accounts reported the occurrence of such incidents. Excluding information from these sources comes at the cost of providing a partial view of the conflict.
Instead, ACLED considers the inclusion of events from these sources relevant, and has determined that while some of the information may indeed be biased (e.g. providing higher casualty numbers), not all information is. For example, they typically tend to be reliable on whether or not an event occurred. This is why, unless otherwise determined, ACLED researchers tend to record events reported by Houthi sources and other parties in the war. Researchers triangulate, when possible, the additional details that are considered to be less reliable in the Yemen context — including the number of fatalities or the identity of the actors involved — and always coded using the most conservative interpretation available when discrepancies between reports exist. Some violent incidents are also particularly prone to reporting lags, and more accurate information only surfaces months after their occurrence. In such cases, ACLED revises existing published data with updated and more accurate information as it becomes available.
The geographical coverage of these sources, however, is not uniform across Yemen. Along the frontline, sources affiliated with governments or armed groups widely report the occurrence of incidents, yet they often tend to only acknowledge their opponents’ losses. This is especially evident in the sparsely populated areas of al-Jawf and Hajjah governorates, where the limited presence of independent reporting has often made it difficult to corroborate the credibility of the information, which is usually done by triangulating multiple sources. In these contexts, ACLED researchers often have to rely on single sources to code events during real-time data collection. Subsequent news gathering, in some cases, may help corroborate the information and adjust initial biases that emerge from real-time data collection. In contrast, the prevalence of subnational sources is higher in the southern governorates of Aden and Abyan, where a rich media environment consisting of dozens of local outlets is helpful in capturing most of the low-intensity violence occurring in these areas. Subnational sources are used for approximately 20% of events in Aden and Abyan, versus less than 3% nationwide.
Meanwhile, foreign media (regional and international) sources account for sourcing in nearly 4% of events since 2015 (and less than 0.5% of events more recently in 2023). Among these, Gulf-based media is currently limited and often tends to engage in reporting biases. For example, Emirati media The National and Gulf News11Coded in the ‘Source’ column as “Gulf News (UAE)” and “National (UAE),” respectively. display a tendency to report specifically on cases where regional interests are at stake and foreign troops are active on the ground. For example, the highest proportion of events recorded using these two sources is in the western coast governorates of al-Hudayda and Taizz, where the UAE was spearheading an offensive against Houthi forces in 2018. Similarly, the Saudi Al Arabiya media has reported heavily on the northern governorates of Hajjah and Saada, which border Saudi Arabia.
A limited yet increasing proportion of events is sourced through ‘new media,’ most notably reputable accounts on X, formerly Twitter, and Telegram channels. These provide valuable information about the activity of non-state groups and activity from Yemen’s easternmost governorates. Over 15% of events involving rebel groups like AQAP and IS are captured through new media sources, pointing to their importance in tracking conflict incidents. Indeed, as these groups suffered several setbacks that severely curbed their operational capacities, social media and encrypted messaging applications became increasingly important tools to publish their activity.
In addition to the daily monitoring of traditional and new media sources, ACLED regularly reviews ‘Other’ sources, mainly reports produced by the UN, nongovernmental organizations like Human Rights Watch, Amnesty International, New America Foundation, The Bureau of Investigative Journalism, and local monitoring groups and think tanks such as Mwatana Organization for Human Rights and the Sana’a Center for Strategic Studies. These reports are a useful resource to update information that is often not available or accurate in real-time reporting, like total fatality estimates or geolocation. They also significantly supplement ACLED’s coverage of violence targeting civilians where such instances fail to be reported by traditional media or require months of investigations; these include, among other examples, mine-related incidents and violence targeting women in conflict environments. Additional, yet limited, data from ACLED partners such as the Aid Workers Security Database further supplement the data.
Where does violence take place, and how are locations recorded in Yemen?
The coding of locations in Yemen reflects the irregular natural and physical geography of the country. Violent events are recorded in both urban and rural spaces, with significant regional variations within the country. The variety of the recorded locations reveals the composite subnational geography of the conflict, which bears further implications for the conduct of the conflict.
Over 5,200 distinct locations have been recorded by ACLED in Yemen. These include towns (and neighborhoods in major cities like Sanaa, Aden, al-Hudayda, and Taizz), villages, and other populated places, as well as natural locations like the Red Sea islands, the desert areas in the northeastern region of the country spanning across the border with Saudi Arabia, rugged mountainous areas, and valleys. Depending on the accuracy of the sources and the size of the recorded location, researchers will select the appropriate geo-precision code to reflect the precision of the coordinates.
Events on the Saudi-Yemeni border
Reporting on the Yemeni-Saudi border faces major shortcomings as reports from the border regions can rarely be triangulated due to unilateral and partisan reporting. Events often occur in either mountainous or desert areas that span between Saudi and Yemeni territory, resulting in exact locations often remaining unknown. To address these challenges, ACLED adopts two main strategies.
1. Former Saudi Arabia events coded to a corresponding Yemeni location
Following a review of open source information, 12Joshua Koontz, ‘Geolocating An Iranian AM-50 Sayyad Sniper Rifle in Majaza Battlefront, Baqim District, Saada Governorate, Yemen,’ Medium, 21 February 2020; X @abduljabbar1612, 4 December 2018 ACLED assumes that events reportedly taking place in the Saudi locations listed in Table 1 below can confidently be re-coded to a corresponding location in Yemen directly across the border. For events in these locations, a short explanation is added to the notes: “*ACLED defaults to coding the event on the Yemeni side when the source describes a large area along the Saudi-Yemeni border.” Additionally, events in these locations are coded with geo-precision code 2. See Table 1 below for information on the location changes.
Table 1
Formerly coded Saudi Admin 1 | Formerly coded Saudi Location | Formerly coded Saudi Latitude | Formerly coded Saudi Longitude | Newly coded Yemeni Admin1 | Newly coded Yemeni location | Newly coded Yemeni latitude | Newly coded Yemeni longitude |
---|---|---|---|---|---|---|---|
Jizan | Wadi al Jarah | 16.8165 | 43.2147 | Sadah | Wadi al Jarah | 16.8251 | 43.2277 |
Najran | Al Buqa | 17.4712 | 44.6451 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Jizan | Rahwan | 16.8333 | 43.2167 | Sadah | Tuwayliq | 16.8500 | 43.2167 |
Asir | Aqabat al Alb | 17.5667 | 43.4000 | Sadah | Aqabat al Alb | 17.5449 | 43.4545 |
Jizan | At Tuwal | 16.5294 | 42.9676 | Hajjah | At Tuwal Border Crossing | 16.4962 | 42.9921 |
Najran | As Sawah | 17.4047 | 44.1073 | Sadah | As Sawh | 17.3481 | 44.1279 |
Najran | Al Ajashir | 17.3138 | 45.6726 | Sadah | Al Ajashir | 17.1833 | 44.8000 |
Asir | Al Mijazah | 17.5204 | 43.5667 | Sadah | Al Mijazah Frontline | 17.4871 | 43.5174 |
Asir | Al Raboah | 17.5760 | 43.3246 | Sadah | Ar Raboah Frontline | 17.5407 | 43.3593 |
Najran | Jabal al Sudais | 17.4361 | 44.1611 | Sadah | As Sudais | 17.3883 | 44.1491 |
Jizan | Jabal ad Dud | 16.7602 | 43.2406 | Sadah | Jabal ad Dud Frontline | 16.7611 | 43.2584 |
Jizan | Jabal ad Dukhan | 16.7481 | 43.2140 | Sadah | Jabal ad Dukhan | 16.7441 | 43.2266 |
2. Former Saudi Arabia events coded to standard Yemeni location
However, there are additional locations along the Saudi-Yemeni border for which ACLED did not manage to establish a direct corresponding location in Yemen, but which are nonetheless also likely to have taken place in Yemeni territory.
As such, ACLED has adapted certain procedures to deal specifically with events near these locations in which it is known that the geographic location is uncertain (i.e. events coded with geo-precision code 2 and 3).
Indeed, some events occurring in these locations on the border between Saudi Arabia and Yemen fall on the Saudi side of the border. Events falling on the Saudi side of the Yemeni-Saudi border that are coded with a geo-precision of 1 remain unchanged.
The majority of events coded at a geo-precision of 2, with a few caveats noted below, are coded to one of four standardized locations in Yemen based on geographic proximity. ACLED views locations coded at a geo-precision of 2 along the Saudi border as uncertain; these are events that occurred in very close proximity to the border, without clear information distinguishing the specific country in which they may have occurred. There is evidence, using open-source intelligence, that some events claimed to have occurred in Saudi Arabia actually took place in Yemen.13Joshua Koontz, ‘Geolocating An Iranian AM-50 Sayyad Sniper Rifle in Majaza Battlefront, Baqim District, Saada Governorate, Yemen,’ Medium, 21 February 2020 Given this, and as these events are associated with the war in Yemen, ACLED has determined that such events and their respective fatalities ought to be aggregated with the Yemen data, instead of the Saudi Arabia data. These events are assumed to not be already captured elsewhere in either country.
The four standardized locations are Al Buqa, Al Malahit, and Baqim Junction in Sadah governorate, and Harad in Hajjah governorate. A list of Saudi locations from which events are moved to the four corresponding Yemeni locations can be found in Table 2 at the end of this section. However, not all events on the Saudi side of the border with a geo-precision of 2 are moved to the corresponding Yemeni locations, and the following caveats apply to the general rule.
2.1 Houthi drone activity in border areas
Houthi drone activity is likely to take place on the Saudi side of the border; these events are often within 20 kilometers of the border, yet frequently do not have a precise location. The following sub-event types reflect such activity and hence their location has been kept on the Saudi side of the border: ‘Looting/property destruction’, ‘Disrupted weapons use’, and ‘Air/drone strikes’ that are perpetrated by the Military Forces of Yemen (2017-) Houthi.
2.2 Missile and artillery activity in border areas
Events coded with the sub-event type ‘Shelling/artillery/missile attacks’ with keywords in the Notes section including “missile,” “precision-guided artillery rocket,” “precision guided artillery rocket,” or “artillery rocket” are also kept in Saudi Arabia as such events capture Houthi ballistic missile et al. activity and are very likely to have actually occurred on the Saudi side of the border.
2.3 Territorial gains in border areas
Events capturing transfers of territory are likewise most often kept in Saudi Arabia as they are assumed to reflect changes to the specific location that was coded. As such, events with the following sub-event types are not moved: ‘Government regains territory’, ‘Non-state actor overtakes territory’, and ‘Non-violent transfer of territory’,
The events that are moved to Yemeni locations are edited as follows:
- All events have their geo-precision code changed to 3 in order to reflect that these locations are estimates.
- The ‘Notes’ column of these events is appended with the following sentence: “*ACLED uses a Yemeni location close to the border to record events between pro-Houthi and anti-Houthi troops where the location reported within 20 km of the border in Saudi Arabia has an unclear geoprecision.”
- Interaction codes are amended, as necessary (for information on the ‘Interaction’ columns and what they mean, see ACLED’s Codebook ).
Events that remain on the Saudi side of the Yemeni-Saudi border, and where fatalities are reported to have occurred but where the exact number of fatalities is unknown, continue to be coded with an estimated 10 fatalities. This is to reflect that the Saudi side of this border is engaged in a war, given the activity and proximity to Yemen (see the ACLED Fatality Methodology).
Table 2 below shows the Saudi locations along the Saudi-Yemeni border and outlines the corresponding location of the four chosen locations on the Yemeni side of the border.
Table 2
Formerly coded Saudi admin1 | Formerly coded Saudi location | Formerly coded Saudi latitude | Formerly coded Saudi longitude | Newly coded Yemeni admin1 | Newly coded Yemeni location | Newly coded Yemeni latitude | Newly coded Yemeni longitude |
---|---|---|---|---|---|---|---|
Najran | Akifah | 17.4953 | 43.7585 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Al Fauwaz | 17.4783 | 44.2463 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Al Khadra | 17.4046 | 44.0200 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Ash Shurfah | 17.5235 | 44.3095 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Bir Askar | 17.6062 | 44.0352 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Khubash | 17.5440 | 44.7350 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Nahuqah | 17.4359 | 44.1157 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Najran | 17.4933 | 44.1277 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Rajla | 17.4994 | 44.2284 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Siqam | 17.4836 | 44.2300 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Najran | Wadi Aleeb | 17.6450 | 43.7625 | Sadah | Al Buqa | 17.3317 | 44.6066 |
Jizan | Ad Dair | 17.3375 | 43.1364 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Al Abadiyah | 16.8417 | 43.1820 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Al Aridah | 17.0394 | 43.0859 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Al Dafiniyah | 16.7875 | 43.1931 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Al Khobh | 16.7818 | 43.2157 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Al Khushel | 16.8801 | 43.1373 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | As Sahhar | 16.9512 | 43.1505 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Ash Shabakah | 16.7825 | 43.2297 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Bani Malik | 17.3982 | 43.1947 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Jabal Juhfan | 16.6836 | 43.1822 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Jabal Malhama | 16.8587 | 43.1656 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Qarn Muzabbar | 16.7868 | 43.2018 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Qays | 17.0340 | 43.2160 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Sala | 17.0403 | 43.1518 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Samitah | 16.5960 | 42.9440 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Jizan | Wadi Awjabah | 17.1080 | 43.1271 | Sadah | Al Malahit | 16.7685 | 43.2758 |
Asir | Al Maarif | 17.5667 | 43.4500 | Sadah | Baqim Junction | 17.4008 | 43.4498 |
Asir | Al Osha | 17.5597 | 43.6139 | Sadah | Baqim Junction | 17.4008 | 43.4498 |
Asir | Zahran | 17.6723 | 43.5236 | Sadah | Baqim Junction | 17.4008 | 43.4498 |
Jizan | Abu ad Darbah | 16.5533 | 43.1139 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Abu ar Radif | 16.6186 | 43.1312 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Ahad al Masarihah | 16.7099 | 42.9550 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Al Kirs | 16.5773 | 42.9476 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Al Mezaab | 16.5766 | 43.0916 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Al Mubakharah | 16.5386 | 43.0841 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Al Muwassam | 16.4167 | 42.8258 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Al Qanboor | 16.4150 | 42.8931 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Ar Ramadah | 16.6915 | 42.9930 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Ghawiyah | 16.5651 | 43.1110 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Hamdah | 16.7619 | 42.9222 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Mathan | 16.4266 | 42.9238 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Ramdah | 16.4667 | 42.9000 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Samitah | 16.5960 | 42.9444 | Hajjah | Harad | 16.4097 | 43.0588 |
Jizan | Shaib adh Dhib | 16.5471 | 42.9796 | Hajjah | Harad | 16.4097 | 43.0588 |
How does ACLED record fatalities?
Fatality data are typically the most biased, and least accurate, part of any conflict report as they are particularly prone to manipulation by armed groups, and occasionally the media. As such, all figures should be treated as ‘reported fatalities.’ These estimates include both combatants and non-combatants.
ACLED does not code fatality figures according to which group suffered fatalities because most source reports do not offer this level of detail, and instead report on the total number of deaths arising from a conflict event. The only exception to this is in events with civilians coded as ‘Actor 2’ because ACLED treats civilians as unarmed non-combatants, the number of fatalities reported for each event with civilians coded as ‘Actor 2’ — typically coded under the ‘Violence against civilians’ or ‘Explosions/Remote violence’ event types — is taken to be the reported number of civilians killed (unless the perpetrator dies as a result of his action, like a suicide bomber). As such, ACLED’s conservative estimates of civilian fatalities used for analysis do not include civilians that may have died during fighting between armed groups or as a result of the remote targeting of armed groups (e.g. an airstrike hitting militant positions but that also kills civilians).14ACLED has developed a tool which automatically combines all ‘Violence against civilians’ or ‘Explosions/Remote violence’ events featuring targeted attacks against unarmed protesters and civilians into a single file. It is available for download on the curated data page, here.
Fatality counting in the Yemen conflict faces several obstacles, which make any effort to provide reliable estimates highly difficult.15Kareem Fahim, ‘The deadly war in Yemen rages on. So why does the death toll stand still?,’ The Washington Post, 3 August 2018 Scarce or biased reporting, as well as limited media access to the sites of violence, may indeed result in substantially different fatality estimates arising from the same event, uncertain figures, or one-sided coverage of conflict events in certain areas. This partially explains why official estimates, which rely on selected data from health facilities, tend to be significantly lower compared to what is perceived to be the real impact of the conflict in Yemen.16Kareem Shaheen, ‘Yemen death toll has reached 10,000 UN says,’ The Guardian, 16 January 2017
To avoid artificially increasing the number of reported fatalities, ACLED has taken several steps to ensure that fatality estimates during the Yemen conflict are the most accurate possible and least subject to media biases:
- Researchers triangulate reported fatality counts to always select the most conservative available, unless more recent or verified information is released;
- High fatality estimates reported by only one source are verified thoroughly, and discarded if they are not confirmed by multiple sources;
- If “casualties” are reported, ACLED assumes that there have been injuries, but not fatalities;
- If fatality estimates are unknown — this happens often as many reports tend to be vague and only mention the occurrence of “deaths and injuries” or “losses” — ACLED uses a standard estimate of 10, or three when the event is known to have caused less than 10 fatalities (e.g. the bombing of a motorcycle resulting in some fatalities). Additional intermediate estimates are used to capture other inaccurate reported figures (e.g. dozens, scores, etc.).
Although the use of a discretionary fatality estimate can result in artificially increasing the number of fatalities, we can easily assume that there are several cases where fatalities go under-reported or are not reported at all. In the end, these expedients help control the inherent bias and avoid inflating fatality counts significantly while ensuring consistency within the country and across other regions (for more information on fatalities, see ACLED’s Fatality Methodology).
Saudi-led Coalition reporting of airstrikes and associated Houthi fatalities since October 2021
On 10 October 2021, the spokesperson of the Saudi-led Coalition announced the killing of more than 400 Houthi fighters from airstrikes in al-Abdiya district of Marib governorate over the preceding 96 hours (6 to 9 October 2021).17Saudi Press Agency, @SPAregions, 10 October 2021 The next day, a new announcement claimed the killing of more than 156 Houthi fighters from airstrikes in the same district over the preceding 24 hours.18Saudi Press Agency, @SPAregions, 11 October 2021This represented a significant shift in reporting. Before that announcement, the Saudi-led Coalition only rarely published fatality figures from its airstrikes, and never with that level of precision. For more than three months, similar announcements with the same ‘canned’ language were made on a near-daily basis. They mostly reported on Marib governorate, though also the governorates of al-Bayda, al-Jawf, Shabwa, and later Taizz and Hajjah, coinciding with anti-Houthi offensives on the ground. An example of the canned language used is as follows:
“الاستهدافات دمرت 22 آلية عسكرية وخسائر بشرية بأكثر من 250 عنصرا”
Translated to: “the targeting destroyed 22 military vehicles and caused human losses of more than 250 personnel”
On 31 January 2022, Saudi-led Coalition reporting shifted again. While near-daily announcements about the specific number of operations carried out and the specific number of vehicles destroyed continued (as outlined above), the specific numbers about the fatalities were removed from the reports. The reports instead only reported unspecified “human losses,” which, according to ACLED’s Fatality Methodology, would be coded as 10 fatalities.
This short-lived, precise — yet high — reporting of fatalities from Saudi-led Coalition airstrikes resulted in a dramatic 332% spike in fatality data between October 2021 and January 2022, compared to the three months prior to the initial reporting shift. These figures would suggest that the months following the initial shift in reporting represent the deadliest time period of the entire conflict in Yemen. Between January 2015 and September 2021, there was only one week where more than 1,000 fatalities were reported, during the week of 3 to 9 November 2018. However, this new reporting resulted in 10 weeks where more than 1,000 fatalities have been reported within a span of 16 weeks. Although fighting had indeed intensified on the ground since September 2021, overall levels of political violence remained relatively low compared to previous years. In other words, the trends reported following this initial shift underlined an unrealistically dramatic change in conflict patterns, especially when considering the lack of such reporting by other primary sources. For this reason, ACLED has decided to not code the precise number of fatalities reported by Saudi sources during this brief shift in reporting, instead opting to treat these reports as an ‘unspecified number’ of fatalities, which ACLED codes as 10 fatalities in war zones like Yemen, according to ACLED’s Fatality Methodology.
The strategy of coding reported fatalities from all of these reports since October 2021 — both those with ‘precise reporting’ between 10 October 2021 and 30 January 2022, as well as those since 31 January 2022 which note “unspecified losses” — as 10 allows ACLED to capture the rise in airstrike fatalities, while avoiding an artificial fatality spike in the data. The outside experts who were consulted confirmed the likelihood of an increase in Houthi fatalities from Saudi-led Coalition airstrikes, though there was no general sense that the exact fatality figures provided by the Saudi-led Coalition were accurate. This decision is also consistent with ACLED’s overall conservative approach to coding fatalities, as well as ACLED’s additional caution when coding fatalities reported by conflict actors (for example, see ACLED’s decisions in the Afghan context). Note that ACLED integrates these fatalities into ‘Battle’ events whenever possible to reflect the recent increase in Saudi-led Coalition air support to ground offensives confirmed by outside experts, rather than attribute them to isolated ‘Air/drone strike’ events in frontline areas.