2016–2017 video game voice actor strike, 2016–2017 strike
The first picket began on October 24, 2016 in Playa Vista, California against Electronic Arts. Additional picketing lines occurred at the Los Angeles headquarters for WB Games and Insomniac Games over the month of November. These picket lines were joined by members of the American Federation of Musicians, the Writers Guild of America, the International Alliance of Theatrical Stage Employees, the International Brotherhood of Teamsters and UNITE HERE, and drew between 300 and 400 people each.


2016–2017 video game voice actor strike, 2016–2017 strike
More than 500 people participated in a rally march from the SAG-AFTRA headquarters to a park near the La Brea Tar Pits to support the strike. In addition to physical picketing of the various industry companies, SAG-AFTRA encouraged its members to use virtual picketing by engaging with their fans on Twitter and other social media under the hashtag, "#PerformanceMatters".


2016–2017 video game voice actor strike, 2016–2017 strike
In response to the strike, the affected companies launched a website to inform the SAG-AFTRA members and the public what the state of negotiations were to demonstrate that they were trying to bargain but had been refused by the union. On this site, the companies stated that their proposed payments would be an upfront system and guaranteed regardless of how well a video game sold, making it a better deal for actors.


2016–2017 video game voice actor strike, 2016–2017 strike
They also noted that they had agreed to terms to split "vocally stressful" sessions from four-hour blocks into two two-hour ones, as long as actors could complete both within a week, but this proposal was rejected by the union. The companies further criticized the union for not bringing its proposed offers to a vote to its members before calling the strike. They also claimed to be the "largest clients of SAG-AFTRA talent" in an industry that "overwhelmingly uses non-union performers". Union attorneys demanded the public relations firm, which set up the website, to immediately stop using their trademarks, citing possible confusion.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
By the end of 2016, it was unclear how much of an effect the strike had on the video game industry, as none of the companies struck had reported delays of upcoming titles due to the lack of voice actors. SAG-AFTRA noted that they had only targeted strike actions against a subset of the industry, and other publishers and developers would not be affected by their action. Union president Gabrielle Carteris said that with the production time cycle for video games, immediate effects of the strike would not be easily seen, anticipating the strike to last for a long time.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
In the interim, they are working to craft amenable contracts with other developers and producers that they have not struck. By May 2017, SAG-AFTRA stated that it had already signed twenty other companies for thirty games under their alternate contract for low-production titles, with "new deals are being signed every week".


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
One of the first reported effects of the strike was the prequel to Life Is Strange, "Before the Storm", which had its first episode released on August 31, 2017. Actress Ashly Burch, a member of SAG-AFTRA who voiced lead character Chloe in the original game, was unable to reprise her voice role due to the strike, though she served to help consult on the character for the game. However, with the strike concluded, Burch was able to return to voice Chloe in an additional episode for Before the Storm produced after the strike's resolution.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
In a separate case, Giant Sparrow had approached John Carpenter to provide narrative voice work for a section of What Remains of Edith Finch modeled after Carpenter's Tales from the Crypt but the strike prevented Carpenter from participating in this manner. Instead, Carpenter allowed the studio to license his iconic Halloween theme for the section.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
It also caused accusations between actors, with Felicia Day calling the new actor that portrayed Chloe in "Before the Storm" a "scab" on Twitter. PCGamesN noted that Burch does not resent the producers as she still worked on the game as a story consultant.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
It was the first such organized strike within the video game industry and the first voice actors' strike in 17 years, as well as the first strike within the merged SAG-AFTRA organization. As of April 26, 2017, it is the longest strike within SAG, surpassing the both the 95-day 1980 Emmy Awards strike, as well as the 180-day 2000 commercials strike.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
Other members of SAG-AFTRA, and other entertainment workers' unions, looked to the voice actor strike as a possible point in their favor during pending contract renegotiations, in light of how many entertainment industries are transitioning towards digital and streaming media; notably, the main SAG-AFTRA contract for film and television industries is due to expire in June 2017, and the solidarity behind the video game voice actors could be used as leverage in these negotiations. SAG-AFTRA and the film and television producers were able to reach a negotiated agreement for new terms in early July, preventing a possible strike action.


2016–2017 video game voice actor strike, 2016–2017 strike, Impact
The video game industry itself has not had any type of trade union concept due to its origins in the tech sector and the white-collar nature of the industry, though there have been some efforts towards forming such unions. The voice actor strike had reengaged discussions about unionization of video game programmers and developers.


2016–2017 video game voice actor strike, 2017 agreement
On September 23, 2017, SAG-AFTRA and the video game companies came to an agreement, effectively ending the strike. The agreement crafted a new three-year contract with the companies to start after ratification by SAG-AFTRA's board of directors, expected to occur within a few weeks from the agreement. The agreement does not include residuals as SAG-AFTRA sought for, but does include a sliding-scale bonus payment for each recording session a voice actor participates in, starting at $75 for the first session, up to $2,100 for ten or more sessions.


2016–2017 video game voice actor strike, 2017 agreement
Keythe Farley, the chair of the SAG-AFTRA negotiations committee, said that these payments "are significantly larger now than what we had 11 months ago" and praised the new structure.


2016–2017 video game voice actor strike, 2017 agreement
Video game companies must provide additional transparencies for roles voice actors are to perform under the new terms; while they do not need to name the game or character to maintain confidentiality when offering roles, companies must provide actors with project code names, gameplay genre, if the work is based on an existing franchise or character, and whether the work will include profanity, racial slurs, obscure technology terms, sexual or violent overtures, or physical stunts. The agreement also will have SAG-AFTRA and the video game companies continue to work on addressing issues related to vocal stress within recording sessions.


2016–2017 video game voice actor strike, 2017 agreement
Voice actors expressed some concern with the agreement, believing SAG-AFTRA conceded too much to the video game companies. Specifically, the failure to come up with residual payment model was an issue, as the union cited "fanatical refusal" from the publishers. Actors as well as some video game producers believe that without a residual-type payment system, the current approach keeps participation in the video game industry extremely different from other traditional forms of media. They also cited concerns that no specifics were made on the vocal stress aspects of the union's complaint. Some actors found the struck studios readily using non-union voice actors at higher rates than their union terms during the strike, and feared that SAG-AFTRA was not doing enough to support voice actors in the video game industry, which are only a small portion of the union's membership.


2016–2017 video game voice actor strike, 2017 agreement
The tentative agreement was approved unanimously by SAG-AFTRA's board of directors on October 9, 2017, sending the issue to member vote. The vote was completed on November 7, 2017, and 90% of the 10% that voted approved the agreement. A new three-year agreement subsequently went into effect on November 8, 2017. The agreement was extended for a further two years in 2020.


2016–2018 Ethiopian state of emergency
A state of emergency was declared on Sunday, 9 October 2016 by Ethiopian Prime Minister Hailemariam Desalegn, although the state of emergency reportedly took effect on Saturday, 8 October 2016. The state of emergency authorizes the military to enforce security nationwide. It also imposes restrictions on freedom of speech and access to information. Media have reported the state of emergency’s duration was announced for six months. The Constitution of Ethiopia provides for a six-month state of emergency under certain conditions.


2016–2018 Ethiopian state of emergency
The government’s declaration of state of emergency followed massive protests by the Oromo and Amhara ethic groups against the government, which is controlled by people in the Tigrayan ethnic group, a smaller ethnic minority. It is the first time in approximately 25 years that a state of emergency has been declared in Ethiopia. In March 2017, Ethiopia’s parliament voted to extend the state of emergency for another four months.


2016–2018 Ethiopian state of emergency, Historical background
Ethiopia, one of the oldest states in the world, has a great history of victory against the colonial powers. Ethiopia's more than 80 ethnic groups have lived together in harmony for generations. The diversity of ethnicity is beautiful, but also tends to perturb the unity of the state. After the downfall of Mengistu Haile Mariam's military regime in 1991, the Ethiopian People’s Revolutionary Democratic Front took over the state. The first thing it did was implement a Federal system of government in the country, a difficult task because the country was a unitary state for more than three thousand years. After implementing the federal system, there was different ethnic based conflicts over natural resources, lands, and others factors.


2016–2018 Ethiopian state of emergency, Historical background
A couple of months before the state of emergency was declared, U.S. State Department officials criticized Ethiopia (historically a strong ally) for how it was dealing with protestors. U.S. Ambassador on human rights Tom Malinkowski wrote (in remarks later attributed to Secretary of State Kerry by the L.A. Times) "security forces have continued to use excessive force to prevent Ethiopians from congregating peacefully, killing and injuring many people and arresting thousands."


2016–2018 Ethiopian state of emergency, Oromo opposition and Amhara resistance
After 25 years of leading this country, the Ethiopian government is facing opposition from all directions of the country. The two major ethnic groups—the Oromo and the Amhara—together represent approximately 61.4% of the country’s population, and the Oromo started a resistance movement against the Tigray-dominated government that began in November 2015. This movement went to different parts of the country. Corruption, poor administration, injustice, lack of equal economic benefits and losing their land in the name of investments are some of the causes that triggered the movement. The situation with the opposition became particularly difficult in October 2016.


2016–2018 Ethiopian state of emergency, Oromo opposition and Amhara resistance
Due to corruption in the country, human rights violations and lack of equal economic benefits, the opposition has been accepted by most protesters. On October 2, there was an annual Oromo religious festival called Irreechaa, a festival where people from the entire Oromia region come and give thanks to their God in a city named Bishoftu. Bishoftu is approximately 50 km (30 miles) from Addis Ababa, Ethiopia's capital. During this festival people all Oromo people come to give thanks to their god. In this event, people started shouting and showing different signs and protesting the government. Police fired tear gas into a crowd of people protesting the government at this festival, which was attended by approximately two million people; this resulted in a stampede and more than 50 deaths.


2016–2018 Ethiopian state of emergency, Political implication
Those who supported what the government did to stop the opposition say “it was the right and the only decision to stop further destruction and conflicts between different ethnic conflicts. And the government is responsible to protect the country peace so the measure taken was right and necessary.” Whereas another group that strongly blames the government for the measure taken during the festivals says “people have the right to express their feeling anywhere and anytime.


2016–2018 Ethiopian state of emergency, Political implication
So the government needs to respect this right of their own people.”Although it is not clear if the measure taken by the government was necessary or not, or proportional or not, this was an immediate reason that led the people all over the Oromia region to go out for the opposition. People started to burn the government property and also foreign investor’s property. After the government’s call for an immediate council of minister’s meeting, the government declared a six-month state of emergency. Due to this, most rights will be suspended.


2016–2018 Ethiopian state of emergency, Political implication
The police may arrest people without court arrest warrant and search any house they suspect without search warrant. The following is also prohibited by the government according to this declaration of a State of Emergency: Any kind of demonstration and meeting, watching Ethiopian Satellite Television (which is led by the political groups outside the country), writing articles which will incite people to go for opposition, having any communication with the opposition groups outside the country, having any sign of opposition on mobile phones and laptops, and accessing websites which criticize the government.


2016–2018 Ethiopian state of emergency, Political implication
This action of the government is getting support as well as opposition. These who support the declaration of State of Emergency say that it’s a decision which will save the country from civil war and ethnic conflicts. Whereas some scholars don’t agree with this, saying that the civil war in the country wouldn’t happen. The opposition is targeting the ruling government and not an ethnic group.


2016–2018 Ethiopian state of emergency, FDRE constitution
According to the Ethiopian constitution, the council of ministers has the power to declare the State of Emergency under three conditions: 1) during foreign invasion, 2) during a natural disaster or natural epidemic, and 3) when there is a breakdown of the country’s law and regulation which will endanger the constitutional order.


2016–2018 Ethiopian state of emergency, Impacts
The declaration of State of Emergency creates fear in most people. Most adults in the country have a bad experience with states of emergency. During the dictatorial Derg regime the government used violence to quell dissent. There was a state of emergency in which they put curfews on cities. During this time, the police went to different houses and did whatever they wanted. Due to this bad memory, most people get home early. Whereas, others have said “it’s a key to safety”, and the country’s security became better after the declaration of the state of emergency.


2016–2018 Ethiopian state of emergency, Impacts
However, most business in big cities of the country have decreased due to the blockage of internet services. Tourist traffic outside the capital city, Addis Ababa, decreases due to different security reasons. Additionally, most people who live in cities prefer to stay home or go home early rather than working. Most economists also predict that this declaration will highly affect the income of the only internet service provider in the country called Ethio telecom.


2016–2018 Ethiopian state of emergency, Impacts, Restrictions on communication
The government tightened restrictions on internet use during the state of emergency. The government shut down the internet for several days, criminalized reporting on protests via social media, and criminalized communicating with exiled dissidents (which are classified by the government as terrorists).


2016–2018 Ethiopian state of emergency, Impacts, Arrests, releases and trials
Within two weeks of announcing a state of emergency, the government, by its own count had arrested 1,645 people. Merera Gudina, an Oromo opposition leader, was arrested after testifying before the European Parliament. On November 12, 2016 the government announced the names and reasons for arrest for 11,067 people who were arrested. In late December, Voice of America reported that the government was releasing over 9,000 people who had been arrested since the start of the state of emergency; the government planned to arraign 2,449 others. Deutsche Welle reported in February 2017 that the government claims 20,000 people are arrested in Oromia, while opposition groups claim 70,000 people are arrested; the government has indicated it will release 22,000 prisoners, having released 11,000 prisoners on February 3.


2016–2018 India–Pakistan border skirmishes
The 2016–2018 India–Pakistan border skirmishes were a series of armed clashes between India and Pakistan, mostly consisting of heavy exchanges of gunfire between Indian and Pakistani forces across the de facto border, known as the Line of Control (LoC), between the two states in the disputed region of Kashmir. The skirmishes began after India claimed to have conducted surgical strikes against militant launch pads within the Pakistani-administered territory of Azad Jammu and Kashmir on 29 September 2016.


2016–2018 India–Pakistan border skirmishes
Pakistan rejected the reports that any deep strike had taken place, stating that Indian forces had only engaged in a gunfight with Pakistani troops at the LoC without crossing over into Pakistani territory, an engagement that reportedly resulted in the deaths of two Pakistani soldiers and the wounding of nine. Pakistan also rejected India's claims that there had been additional casualties. Following this, Pakistani sources reported that in the 29 September skirmish, at least eight Indian soldiers were killed while one was captured by the Pakistan Army. India subsequently confirmed that one of its soldiers was in Pakistani custody, but denied that the mentioned gunfight was linked to the surgical strike incident or that any of its soldiers had been killed in the hostilities.


2016–2018 India–Pakistan border skirmishes
The Indian operation was said to be in retaliation for a militant attack on an Indian Army base in Uri, in the Indian-administered state of Jammu and Kashmir, that left 19 Indian Army soldiers dead on 18 September 2016. Over the course of the next 20 months, India and Pakistan continued to regularly exchange fire across the LoC in Kashmir, resulting in dozens of military and civilian casualties on both sides.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – initial strikes
On 29 September, eleven days after the Uri attack, the Indian army reported it conducted surgical strikes against suspected militants in Pakistani-administered Kashmir. Lt Gen Ranbir Singh, Indian Director General of Military Operations (DGMO), said that it had received "very credible and specific information" about "terrorist teams" who were preparing to "carry out infiltration and conduct terrorist strikes inside Jammu and Kashmir and in various metros in other states". The Indian action was meant to pre-empt their infiltration. Indian media reported variously that between 35 and 70 terrorists had been killed.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – initial strikes
Pakistan denied that such surgical strikes occurred. The Inter-Services Public Relations said that there had been only "cross border firing". But, Pakistan Prime Minister Nawaz Sharif condemned the "unprovoked and naked aggression of Indian forces", which he said resulted in the death of two Pakistani soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – initial strikes
UN Secretary General Ban Ki-Moon said that the UN Observer Group in Pakistani Kashmir did not directly observe any "firing across the Line of Control" relating to the incident. The Indian envoy at UN Syed Akbaruddin dismissed this statement, saying "facts on the ground do not change whether somebody acknowledges or not."


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – initial strikes
Analyst Sandeep Singh, writing in The Diplomat, said that the operation is better characterised as a cross-border raid because "surgical strikes" involve striking deep into the enemy territory and typically using air power.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 1 October, Pakistan said its soldiers had come under fire in Bhimber and they responded to the attack. Indian media stated that Pakistan had started the firing. 6 Indian civilians in Poonch district were reported to be injured in firing from Pakistani soldiers on 3 October. On 4 October, the Indian Border Security Force said it witnessed Pakistani-operated unmanned aerial vehicles (UAVs) flying close to the border, presumably to survey Indian positions. The same day, an Indian soldier was injured by Pakistani fire in the Naushera sector of Rajouri district in the Indian state of Jammu and Kashmir. Three to at least four Indian soldiers were injured on 5 October because of firing and shelling. Nine Pakistani soldiers were also reported to be injured in retaliatory fire.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Border skirmishes continued throughout the month of October. An Indian soldier was killed by Pakistani fire in the Rajouri District of Indian controlled Jammu and Kashmir on 16 October. One Pakistani civilian was stated to have been killed by Pakistani authorities while 12 others were stated to have been injured in firing by Indian forces on 19 October.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 21 October, the BSF said that it killed 7 Pakistan rangers, a militant and injured 3 other Pakistani soldier in retaliatory fire after a sniper attack by Pakistani forces injured an Indian soldier, Gurnam Singh in Hiranagar, who later succumbed to his injuries in hospital. The BSF claimed that the Pakistani media confirmed the "fatalities suffered by Pakistani rangers" with a news report that put the number of dead at 5. Pakistan's ISPR denied that any of its soldiers died and claimed that Indian forces resorted to unprovoked firing, which was dealt by Pakistani soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 24 October, a BSF personnel and an Indian civilian were reported to have been killed in exchange of fire between both countries, while nine Indian civilians were reported to be injured. BSF also stated that four to five Pakistan Rangers were injured in firing from Indian side. Pakistani authorities also stated that 2 Pakistani civilians were killed in firing by Indian forces, with 6 civilians being injured.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Pakistani military claimed that it had killed 5 Indian soldiers and destroyed 4 Indian military outposts on 25 October. Pakistani authorities on 26 October alleged that two civilians were killed while nine others were injured in firing by Indian troops at the working boundary in Chaprar and Harpal sectors and on the LoC in Bhimber sector on 25–26 October. A BSF personnel was reported to be killed on 27 October in R.S. Pora sector while ten Indian civilians were reported to be injured along the International Border in Jammu region in firing by Pakistani forces.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
BSF claimed that it killed one Pakistan Ranger and injured another in retaliatory firing. 6 Pakistani civilians were killed and 22 were injured in firing by Indian forces at Shakargarh and Nikial sectors on the same day in a claim made 2 days later by Pakistani authorities. In addition, another two civilians were reported to be killed while nine others were reported to be injured in Chaprar, Harpal and Bhimber sectors.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Two Indian civilians were reported to be killed, while four civilians were reported to be injured in shelling by Pakistani forces on 28 October. A BSF constable was killed in an accident while retaliating to fire by Pakistani forces on the same day. Meanwhile, BSF claimed that 15 Pakistani soldiers had been killed in retaliatory fire. Three Pakistani civilians were reported to have been killed while five others were injured in firing by Indian forces on the same day in Nakyal sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
According to a report by India Today, the Indian Army had destroyed a company headquarters and four military posts of the Pakistan Army on 29 October in retaliation to the beheading of an Indian soldiers by militants who were aided by cover fire from Pakistan Army. At least 20 Pakistani soldiers were reported to be killed in the attack according to the report.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
A soldier was killed in Tarkundi area of Rajouri while a civilian was killed in Mendhar and another was injured in firing and shelling by Pakistani forces on 31 October. Pakistani authorities claimed on the same day that 4 Pakistani civilians were reported to be killed while 6 were injured in firing by Indian forces. 8 Indian civilians were reported to be killed in firing and shelling by Pakistan Rangers while 23 were injured on 1 November. The Indian Army stated that it had killed 2 Pakistani soldiers and destroyed 14 military posts in retaliation. 2 Indian soldiers were reported to be killed while two other soldiers and a woman were reported to be injured in firing by Pakistan Army who were trying to facilitate an infiltration bid on 5 November in Poonch district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Pakistani officials stated on 7 November that 3 Pakistani civilians were killed while 6 civilians were injured in firing by Indian troops. On 8 November, three Pakistani civilians were killed while three were others were injured in shelling by Indian troops according to a senior police official of Poonch district. On the same day, an Indian soldier was reportedly killed while another was seriously injured in shelling by Pakistani troops in Nowshera sector. Another 4 Indian soldiers were also reportedly injured in shelling by Pakistani troops on the same day.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
The soldier who was seriously wounded in Rajouri succumbed to his injuries on the following day while another was killed in sniper fire by Pakistani troops in Machil sector of Kupwara according to an Indian Army official. On 9 November, Pakistani authorities stated that 4 civilians were killed while 7 were injured in firing by Indian troops in Khuirata and Battal sectors on the previous day.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
An Indian soldier was reportedly killed in Keran sector on 11 November in firing by Pakistan Army while 6 soldiers were injured. Pakistani authorities stated on 14 November that 7 Pakistani soldiers had been killed in gunfire by Indian forces. General Raheel Sharif later claimed that they had killed 11 Indian soldiers on the same day in retaliatory firing. The Indian Army rejected the claim. On 17 November, Northern Command of the Indian Army said in a tweet: "No fatal casualties due to Pak firing on 14,15 or 16 Nov. Pak Army Chief claim of killing Indian soldiers on 14 Nov false."


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 18 November, the Pakistan Navy alleged that its warship had intercepted and prevented the covert infiltration of Indian submarine in Pakistan's seaborne territories on 14 November. The ISPR released the military video footage of the alleged Indian submarine patrolling in the Arabian sea. However, Pakistan had not identified the type of submarine it claim to have intercepted. The Navy claimed that its warships had intercepted the incurring Indian submarine once it was detected on their military radars, and diverted the submarine from its course of actions.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
The Indian Navy strongly rejected the claims and termed Pakistan's interception claims as: "blatant lies". The Indian Navy also said that none of its ships are near Pakistan." An Indian Navy officer said in a statement, "Why would an Indian submarine surface or come to snorkelling depth near Pakistani waters? ", Submarines are meant to be stealthy, and they do not reveal their presence so easily whether they are on intelligence gathering or in combat missions.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Another navy officer stated that there are more than 150 ships in the northern Arabian Sea and the Persian Gulf of different nations including submarines of the China, "either the Pakistan Navy mistook some other nation's submarine as an Indian one or is just doing propaganda warfare." NDTV stated that, analysis of the video and the images released by Pakistani authorities does not indicate that the mast of the submarine which are visible in the images matches the mast of either India's Shishumar-class submarines, its Kilo-class submarines or its Chakra nuclear attack submarine.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 18 November, Commander of X Corps of the Pakistan Army Lieutenant-General Malik Zafar Iqbal said to a selected gathering of Pakistani parliamentarians and journalists in Gilgit: "Only 20 of our soldiers embraced martyrdom" and claimed: "they [Indian Army] lost more than 40 soldiers".


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 19 November, the Pakistani military claimed that it shot down an Indian quad-copter type drone that had allegedly crossed the LoC into Pakistani controlled Kashmir. The same day, the Pakistani police said that four Pakistani civilians were killed in cross-border firing.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 22 November, Indian reports said that militants or a Pakistani "Border Action Team" killed three Indian soldiers and savagely mutilated one of the bodies in Machhil sector of Kupwara district along the LoC. The Northern Command of the Indian Army said that "retribution will be heavy for this cowardly act". This was the second such incident of mutilation of an Indian soldier's body in the same sector since 28 October, when the militants mutilated the body of Mandeep Singh of 17 Sikh Regiment before retreating back into Pakistan controlled Kashmir under covering fire from Pakistan Army. Pakistan denied the accusation, calling it fabricated.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 23 November the Indian army launched a massive attack. 120 mm heavy mortars and machine guns were used in the attack on Pakistani army posts. Artillery fire and shelling from India targeted several Pakistani villages and struck a passenger bus near the dividing line in the disputed region of Kashmir on Wednesday killing 9 civilians. Pakistan announced that it also killed 3 soldiers including an army captain. Two more civilians were also killed in another region of Kashmir. Pakistan military also claims 7 Indian soldiers have been killed in retaliatory fire, which was not confirmed by India.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
Following the incident, DGMO of Pakistan requested for unscheduled talks on hotline and complain about killing of civilians caused by Indian Army fire. However, Indian DGMO, Lt Gen Ranbir Singh made it clear to its counterpart about the unprovoked firing by Pakistani troops to provide cover fire to the terrorists coming from POK.


2016–2018 India–Pakistan border skirmishes, Timeline, 2016 – Post-strikes
On 29 November, Pakistan and India exchanged fire on the LOC north of Baramulla sector as well as in Uri sector. On 2 December, a Border Security Force trooper was wounded by a Pakistani sniper in Bhimbher Gali sector of Rajouri district. On 29 December, it was reported that Pakistan Army fired at Indian positions in Gulpur sector of Poonch district. No casualties were reported on the Indian side.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 13 February 2017, Pakistan Army's official public relations outlet, the ISPR stated that three Pakistani soldiers were killed in cross-border firing by Indian troops.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
The Indian Army stated on 1 May that the Border Action Team (BAT), which is alleged to be made up from terrorists and soldiers of Pakistan's Army, killed and mutilated bodies of 2 Indian soldiers. Pakistan's government denied it.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 11 May 2017, the two countries exchanged artillery and small-arms fire. Pakistan's foreign office stated that a civilian had been killed while 2 others were injured by Indian shelling in Subzkot in Azad Kashmir while the Associated Press reported that an Indian civilian had been killed in Nowshera. On 14 May 2017, an Indian army official claimed that Pakistan shelling in Nowshera killed 3 Indian civilians and injured 9 others including a BSF officer.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 23 May 2017, the Indian Army claimed it had "bombed" Pakistani army checkposts in Nowshera Sector along the border. An Indian military spokesman said the action was taken to prevent infiltration of militants into the Indian side. However, the Pakistani military swiftly rejected the claim as "false".


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
The Indian Army stated on 26 May that it had scuttled the attempts at a cross-border infiltration by BAT, killing 2 BAT terrorists. 2 days later it stated that an army porter was killed and another injured in firing by Pakistan Army in Keran sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 29 May 2017, the Indian media reports, citing defence sources, said that special forces of the Indian Army foiled an attack by Pakistan's Border Action Team, killing 2 Pakistani soldiers along the Line of Control in Jammu and Kashmir's Uri sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 1 June 2017, Livemint reported, quoting an Indian government official, that the Indian Army's special forces eliminated a Pakistani Border Action Team composed of five enemy soldiers along the Line of Control in the Muzaffarabad sector. On the same day one Indian civilian was also killed after Pakistani troops attacked Indian military positions along the line of control. On 2 June 2017, Indian military reported that one personnel of General Reserve Engineer Force (GREF) was killed and two Border Security Force (BSF) personnel were injured after Pakistani military opened fire on Indian military positions.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 4 June, Pakistan's ISPR said that the military destroyed Indian bunkers during cross-border firing, in which five Indian soldiers were killed. It released video footage showing the Pakistani forces' destruction of the posts. However, the Indian Army denied the claim. "No casualties have been caused to our own soldiers in ceasefire violation along LoC," a senior officer of 16 Corps of the Indian Army said. "The claim of the Pakistan Army that it killed 5 Indian soldiers, destroyed bunkers in firing on LoC, is totally wrong," he said.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
Following hotline contact, the ISPR stated any Indian violations would be responded with "full force at the time and place of our choosing with the onus of responsibility on Indian aggressive behaviour." Dawn reported the number of Indian ceasefire violations in 2017 at over 400, crossing last year's 382. Pakistan's DGMO, Major-General Sahir Shamshad Mirza, said that Indian forces were killing civilians and inadvertent crossers of the LoC and labeling them infiltrators, which was "highly unprofessional and unsoldierly". He told his Indian counterpart to "look inwards" instead of at Pakistan for the unrest in Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 14 June, a cross border firing between Indian and Pak army, in Poonch and Rajouri area along LOC, left two Pak soldiers dead. On 16 June, An Indian soldier was killed by Pakistan army's cross-border firing on forward posts along the Line of Control (LoC) in Rajouri district of Jammu and Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 22 June, Pakistan Border action team (BAT) sneaked 600 metres across the LoC into the Poonch sector and killed two Indian soldiers. The same day, two Pakistani civilians were injured by Indian army's firing in Kotli district of Azad Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 25 June, Pakistan army cross border firing resulted in death of 1 civilian in Naushera sector. On 29 June, Indian military reported that two Indian soldiers were injured after Pakistan's army fired mortar, targeting Indian military positions along the Line of Control in Poonch district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 1 July 2017, a Pakistani civilian was injured by Indian army's cross border firing in Rawlakot, Azad Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 8 July, Indian officials reported that an on leave Indian soldier and his wife were killed and their three children were injured after Pakistani military opened fire targeting Poonch district along LOC. On next day of incident, Pande Rajiv Omparkash, SSP Poonch, said that Indian army destroyed a Pakistani checkpost.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 10 July, Pakistan's ISPR said that Pak army responded with an attack that destroyed two Indian military posts and killed four of their soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 12 July, two Indian soldiers were killed after a cross border firing by Pakistan army in Kupwara area along LOC.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 15 July, an Indian soldier was killed by Pakistan army's cross border firing in Rajouri.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 16 July, Indian army targeted one of the military vehicles of Pak army which eventually fell into Neelum River at Athmuqam along LOC resulting in deaths of 4 Pak army soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 17 July, an Indian army men and a minor girl were killed while 2 other civilians were critically injured in cross border firing by Pakistan army along the Line of Control in Jammu and Kashmir on Monday in Rajouri's Manjakote sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 18 July, two Indian army men were killed by Pakistan army's firing in Rajouri district. The deceased were rifleman Vimal Sinjali and Sepoy Jaspreet Singh. Around six Indian civilians were also reported to be injured as result of Pakistan's army shelling of hamlets and military posts along Line of Control.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 19 July, an Indian army Junior Commissioned Officer (JCO) Shashi Kumar succumbed to his injuries. He was grievously injured as a result of Pakistan firing in Naushera yesterday. That same day, the Pakistan Army said that it targeted Indian military posts in retaliation to Indian army ceasefire violations the previous day. Pakistan Army stated that it had killed around five Indian soldiers in this attack.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 21 July, an Indian Army soldier was killed in cross-border firing across the Line of Control on Friday by Pakistani army in Sunderbani sector of Jammu and Kashmir's Rajouri district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 8 August, an Indian soldier was killed by Pakistani fire in skirmishing along the Line of Control.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 12 August, an Indian army Junior commissioned officer (JCO) and one Indian civilian were killed by Pakistani shelling in Poonch district of Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 13 August 3 Indian soldiers were injured in Pakistan firing in Uri Sector of Baramulla.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 25 August, a BSF soldier sustained injuries when he was hit by a Pakistani sniper just below his right ear in the RS Pura sector. His condition was said to be stable. The next day, on 26 August, the BSF said that the Pakistani rangers started unprovoked mortar shelling at forward Indian posts in Dewra village of Rajouri's Sunderbani district and in retaliation it "shot dead at least three Pakistan Rangers".


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 1 September 1 Border Security Force (BSF) soldier was Killed in Pakistani Sniper Fire From Across Line of Control in Poonch.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 13 September, Indian officials stated that three BSF troopers sustained injuries as result of unprovoked firing by Pakistani forces on BSF posts in Poonch and Jammu districts.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 14 September, the BSF said it killed two Pakistani soldiers in retaliatory fire.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 15 September, an Indian border guard was killed by Pakistani fire in skirmishing along the Line of Control.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 17 September, One woman killed, 5 injured as a result of Pakistan army firing in Arina sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 20 September, an Indian army soldier was killed in Keran sector as a result of Pakistan army firing.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 22 September, the Pakistan military said that six Pak civilians were killed while 26 others including 15 women and 5 children were injured by Indian army's firing in Charwah and Harpal sector. That same day, Indian police officials said that the Pakistani forces violated the ceasefire first, injuring four Indian civilians.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 2 October, the Indian Army said that two children were killed and a dozen civilians were wounded in "unprovoked and indiscriminate firing of small arms, automatics and mortars" by Pakistan soldiers in Poonch, where Indian troops killed 5 militants trying to infiltrate into India from the Pakistani side. Hindustan Times, citing an Indian Army spokesperson, said that Indian troops retaliated and the exchange of firing continued till afternoon.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 3 October, an Indian Army soldier was killed when Pakistani troops violated the ceasefire along the LoC in Poonch.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 4 October, the Press Trust of India (PTI) reported that three Indian soldiers sustained injuries when Pakistani troops opened "unprovoked and indiscriminate" fire at them. A Defence spokesperson said that Indian troops "retaliated effectively". That same day, the Pakistan Army said that two children were killed from Indian firing across the LoC. The Pakistan Army added that it was engaging Indian posts, and three Indian soldiers were reported killed in addition to five injured during retaliatory firing.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 12 October, eight Indian Army personnel including two porters sustained injuries due to unprovoked firing by the Pakistani troops. An army soldier and a porter later succumbed to their injuries. A defence spokesperson said, "The Pakistan Army initiated unprovoked and indiscriminate firing of small arms and automatics from 1035 hours in Krishnagati sector along the Line of Control (LoC)."


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 21 October, Indian army porter was killed and a girl was injured in Baramulla district as result of ceasefire violation.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 2 November, a BSF constable was killed in Samaba sector as result of ceasefire violation.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 4 December, a Pakistani soldier was killed as result of ceasefire violation on LOC. The deceased was Juma Khan Bugti belonging to 47 Baloch Regiment.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 6 December, a Pakistan Army Junior Commissioned Officer (JCO) on leave, Subedar Shaukat Kiani was killed due to Indian shelling in Abbaspur sector along with a civilian.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 23 December, the Indian Army said that four Indian soldiers including an army major were killed in Keri sector in unprovoked firing by Pakistan. The next day, the Indian media reported that two Pakistani snipers were killed in Poonch and Rajouri districts. On 25 December, the Indian Army said that a team of 5–6 Ghatak commandos carried out a cross-LoC raid, during which they went around 250–300 meters inside the Pakistani side of the LoC, killing at least 3 Pakistani soldiers and injuring a few others.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
The Times of India cited a senior Indian Army officer as saying that intelligence inputs suggested that Pakistanis could have suffered more casualties. Pakistan rejected Indian media reports that Indian soldiers had crossed the Line of Control. Initially, the Pakistan Army said that the soldiers were killed by ceasefire violation, and the Foreign Office later said that India provided cover fire for "non-state actors" to plant improvised explosive devices that killed the soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2017
On 31 December 2017, an Indian soldier was killed as a result of ceasefire violation in Nowshera sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 3 January 2018, a BSF head constable was killed as a result of ceasefire violation in Samba sector of Jammu and Kashmir.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 4 January 2018, Pakistani media reported that three Pakistani civilians were injured as a result of ceasefire violation in Sialkot's Zafarwal sector. The Indian media reported that BSF had destroyed three Pakistani border outposts and two mortar positions killing 10-12 Pakistani Rangers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 10 January 2018, India reported that it had killed 138 Pakistani soldiers along the Line of Control during 2017, wounding 155 more. During the same time period the Indian government admitted that it suffered 28 soldiers killed in action and a further 70 more wounded in fighting along the Line of Control.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 14 January 2018, an Indian army soldier was killed in Pakistani firing in Rajouri district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 15 January, the Indian Army said that it killed seven Pakistani soldiers, including a Major-rank officer and injured four others in retaliation. Additionally, the Indian army said it also foiled an infiltration bid, killing 6 Jaish-e-Muhammad militants. A senior Indian Army officer said, "Though we responded strongly and effectively on Saturday as well, we retaliated on Monday, resulting in seven fatal casualties and four injuries on Pakistan’s side in Janglote area across the LoC opposite Mendhar." The same day, the Pakistani army said that four of its soldiers were killed in Indian firing along the LoC in Jandrot, Kotli sector. It also claimed that it killed three Indian soldiers. The Indian Army denied any casualties.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 18 January, India claimed that one BSF constable and a teenage girl were killed in shelling by Pakistani Rangers in RS Pura sector. Pakistan claimed that 2 civilians were killed and 5 others wounded in cross-border firing by Indian troops in Sialkot.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 19 January, India claimed that one BSF and an Indian Army soldier were killed in ceasefire violations along the LoC in Samba sector in the Sunderbani sector of Rajouri district respectively. In addition, two civilians were killed in the RS Pura sector while eleven others were injured. In retaliation, Indian claimed to have killed 4-10 Pakistani Rangers and destroyed six Pakistani posts. Pakistan claimed that a man and a minor girl were killed in Bhimber district because of "unprovoked" shelling by the Indian forces.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 20 January, India claimed that one Indian Army soldier and two civilians were killed in ceasefire violations in Poonch and Jammu districts respectively. Pakistan claimed that one Pakistan Army soldier and two civilians were killed in ceasefire violations by the Indian army in Nakyal sector of Kotli district. In addition, 5 civilians were reported wounded. One Indian army soldier who sustained injuries in Krishna Gati sector succumbed to his wounds on 24 January.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 21 January, Pakistan claimed that two of its civilians were killed in a ceasefire violation in Nikial sector. India claimed that one Indian Army soldier and three civilians were killed in ceasefire violations in Mendhar and RS Pura and Kanachak sectors respectively.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 22 January, India claimed that a 35-year-old woman was injured in cross border shelling by Pakistan. She was reported to have succumbed to her wounds on 28 January.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 28 January, Pakistan claimed that three civilians were injured during ceasefire violations in Khuiratta, Kotli and Battal in Rawalakot.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 4 February, four Indian Army soldiers were reported killed and one injured during cross-border shelling in Rajouri sector. Two other Indian soldiers were also reported injured by ceasefire violations in Poonch district. One soldier who suffered splinter injuries in Poonch district succumbed to his wounds on 12 February.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 8 February, India claimed that one Indian civilian was killed as a result of ceasefire violations by Pakistan in Krishna Gati sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 11 February, India claimed that one civilian was killed during a ceasefire violation in Pkukherni and Lairan villages of Noushera.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 15 February, the Indian media, citing government sources, said that the Indian Army killed 20 Pakistani soldiers in retaliatory firing this year, while suffering 10 casualties of its own. The same day, the Pakistan Army claimed that it destroyed an Indian army post, leaving five soldiers killed and several injured. Pakistan reported that the "retaliative" strike took place hours after shelling from Indian troops hit a school van on the Pakistani side, killing its driver. India rejected Pakistan's claim as "totally false". A senior Indian Army officer said, "Unlike Pakistan Army, we do not, and cannot, hide our casualties."


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 19 February, Pakistani media reported that an eight-year-old boy was killed due to Indian firing across the LoC. The Pakistan Army claimed that it had neutralized an Indian army post killing two soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 20 February, Indian Army claimed that in a direct fire assault they had destroyed a Pakistani post in the Tangdhar sector killing one soldier and seriously injuring another. Another Pakistani post was destroyed in the Haji Pir sector killing at least 2 soldiers.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 28 February, Indian Army claimed that they killed two Pakistani soldiers in retaliation against ceasefire violations in the Bhimber Gali sector in Rajouri district. The Pakistan Army claimed that these 2 soldiers were killed in Indian firing.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 2 March, Indian media claimed that two Pakistani soldiers were killed in retaliation by the Indian Army in Poonch district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 18 March, India claimed that five civilians were killed and two wounded as a result of Pakistan army shelling on Balakote sector of Poonch.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 3 April, Indian army claimed that a soldier was killed and four wounded as a result of Pakistan army shelling in Krishna Ghati sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 10 April, Indian army claimed that two soldiers were killed as a result of Pakistan army firing in Rajouri.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 12 April, Indian army claimed that a soldier was killed as result of Pakistan army firing in Poonch's Krishna Ghati sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 16 April, India claimed that an army porter was killed as result of Pakistan army firing in Baramulla district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 17 April, India claimed that a soldier was injured as a result of Pakistan firing in Rajouri and later succumbed to his wounds on 21 April.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 23 April, Indian Army claimed that they killed five Pakistani soldiers and destroyed three Pakistani bunkers in Poonch and Rajouri districts in retaliatory fire.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 26 April, Indian Army claimed that three Pakistani soldiers were killed in retaliation in Padhar sector, opposite Sunderbani, in Rajouri district. Pakistan Army claimed that two civilians were killed in Bramla village, Padhar Sector) during a ceasefire violation.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 12 May, India claimed that a civilian was killed as result of Pakistan firing in Gulpur-Degawar area in Poonch district of Jammu division.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 16 May, India claimed that a BSF soldier was killed as result of Pakistan firing on Mangu Chak border outpost on the international border. Pakistan also claimed that 1 of its civilian was killed as result of Indian firing


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 19 May, India claimed that a BSF soldier and four civilians were killed as a result of Pakistan firing in R S Pura and Arnia sectors of Jammu. Pakistan claimed that four civilians were killed in Indian firing in Pukhlian, Cahprar, Harpal, Charwah and Shakargarh sectors.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 21 May, India claimed that a civilian was killed and six other wounded as a result of Pakistan firing in Jammu district. Pakistan claimed that a Pakistani Ranger was killed and three others wounded in Indian shelling of Badwal post in Charwah sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 22 May, Pakistan claimed that a Pakistani Ranger and a civilian was killed in Indian firing in Shakargarh sector.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 23 May, India claimed that five civilians were killed as result of Pakistani shelling in Jammu, Kathua and Samba district.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 24 May, India claimed that had killed 8–10, injured 12 Pakistani Rangers and destroyed several posts in retaliatory fire during the past few days.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018
On 27 June, an alleged Partial footage of the strikes was released by the Indian government to the Indian media as proof to the strike. Pakistan's foreign office spokesman, however, rejected the alleged video and termed Indian claims as farcical.


2016–2018 India–Pakistan border skirmishes, Timeline, 2018 – Ceasefire
On 29 May, India and Pakistan agreed to "fully implement" the 2003 ceasefire and stop cross-border firing. Despite this, cross-border clashes continued until mid-June, during which seven more Indian soldiers were killed and eleven civilians were wounded. India also claimed to had carried out nine strikes which destroyed ten bunkers and posts of the Pakistani Rangers in Kanachak and Akhnoor sectors of Jammu district, killing at least five Pakistani Rangers and injuring three. The last confirmed death was of an Indian soldier on 16 June.


2016–2018 India–Pakistan border skirmishes, Aftermath
Subsequently, the ceasefire along the Line of Control largely held, despite sporadic violations, leading to cautious optimism among Indian officials that it would continue.


2016–2018 India–Pakistan border skirmishes, Aftermath
Between early August and early September, Pakistan reported four civilians were killed in Indian cross-border shelling. In addition, India reported two civilian deaths due to Pakistani fire by the start of October and claimed that in retaliation its Army had killed two Pakistani soldiers. Despite this, during military talks between India and Pakistan that were held in mid-August, Pakistan expressed satisfaction on the measures being taken along the Line of Control by troops to maintain the ceasefire. Firing continued for the next months, after the end of ceasefire. From November to December, 7 Indian army soldiers were killed by Pakistani sniper fire from across the border. Indian media reported that there were 2,936 instances of ceasefire violations by Pakistan in Jammu and Kashmir in 2018.


2016–2018 Montenegrin municipal elections
Montenegrin municipal elections were held in all 23 municipalities, between April 2016 and May 2018.


2016–2018 Montenegrin municipal elections, Results, 2016 elections, Tivat
This election was boycotted by several opposition parties and coalitions due to unfair conditions.


2016–2018 Montenegrin municipal elections, Results, 2017 elections, Nikšić
Local election for Nikšić Municipality was held on 12 March 2017. It was boycotted by all the opposition parties after the Government announced the imprisonment of the leaders of the opposition coalition Democratic Front. Only the ruling DPS and its minor partner SD ran in the election, with voter turnout at 45%, while 11% of the votes cast were spoilt.


2016–2019 United Kingdom rail strikes
Since 2016, major industrial action – in the form of periodic strikes and protests – has been ongoing on the national railway network of the United Kingdom. The dispute centres on the planned introduction of driver-only operation (DOO) by several train operating companies, transferring the operation of passenger train doors from the guard to the driver. Later strikes have also included disputes over pay rates, planned redundancies and working hours.


2016–2019 United Kingdom rail strikes
Supporters claim that DOO will save costs and shorten journey times, although opponents claim that the scheme is unsafe to passengers as drivers may not have as good visibility of the train doors as guards, who are able to step out onto the platform. Opponents also claim that the scheme could lead to hundreds of job losses to train guards, although several train operating companies have denied this, stating that guards will be redeployed to an otherwise equivalent role on board.


2016–2019 United Kingdom rail strikes
The strikes started on 26 April 2016, initially on Govia Thameslink Railway's Southern trains, and have since spread to eight more rail franchises across the country. The strikes were led initially by Mick Cash, General Secretary of the National Union of Rail, Maritime and Transport Workers (RMT); the Associated Society of Locomotive Engineers and Firemen (ASLEF) joined the strikes in November 2016, followed by the Transport Salaried Staffs' Association (TSSA) in January 2018. Opposition to the strikes was led by then Prime Minister Theresa May and Secretary of State for Transport Chris Grayling, who labelled the strikes as "appalling"  and "palpable nonsense".


2016–2019 United Kingdom rail strikes, Background
In April 2016, Southern introduced a new method of door operation, with control of the doors moving from the conductor to the driver. Southern also proposed that, following the changes to the door operation, conductors would take on an "on-board supervisor role", which would let them concentrate on passengers more than doors, but the RMT and ASLEF described this as an attempt to make conductors unnecessary, and would also be unsafe. However, the rail safety regulator, the Rail Safety and Standards Board, said that "We have 30 years of data which we have analysed.


2016–2019 United Kingdom rail strikes, Background
We have found that the driver performing the task does not increase the risk to passengers at all." The BBC suggested that the RMT was particularly worried about the new method of operation because if trains could run without conductors any strike action they took would be ineffectual. As a result of this, the RMT and ASLEF unions went on strike over the changes, causing severe disruption to Southern services.


2016–2019 United Kingdom rail strikes, Industrial action
The strikes began on 26 April, as Southern conductors who were members of the RMT walked out on strike for 24 hours. Industrial action spread nationally across eight further franchises, peaking in the second half of 2017.


2016–2019 United Kingdom rail strikes, Industrial action
On 17 January 2017, the Trades Union Congress (TUC) announced that ASLEF had called off a three-day strike on the Southern network that was due to occur at the end of January. The overtime ban by ASLEF-affiliated Southern drivers was also suspended as talks were being held at the TUC between Govia Thameslink Railway and the union. On 2 February, the TUC announced that talks between Southern and ASLEF had in principle reached an agreement, meaning that the dispute with ASLEF had been resolved.


2016–2019 United Kingdom rail strikes, Industrial action
The Assistant General Secretary of the RMT, Steve Hedley, said of ASLEF that it was "scandalous other people think they can do a deal that affects our members" and that "we are not bound by that deal. The dispute is still on". The RMT met with Govia Thameslink Railway for further talks, but were unable to come to a final deal. The TUC-brokered agreement between ASLEF and Southern broke down the following month. When the proposed deal was put to a ballot of ASLEF's driver members on 16 February, it was overwhelmingly rejected, and industrial action resumed nationally.


2016–2019 United Kingdom rail strikes, Industrial action, CrossCountry
Industrial action by RMT-affiliated on-board train managers and senior conductors employed by Arriva CrossCountry began in late 2017, due to an industrial dispute over working hours, particularly in relation to staff rostering and Sunday working. At present, CrossCountry has no plans to introduce driver-only operation on its services.


2016–2019 United Kingdom rail strikes, Industrial action, CrossCountry
CrossCountry staff went on strike for 24 hours on four Sundays at the end of 2017: 19 November, 26 November, 24 December and 31 December. Additionally, a 48-hour strike took place across the weekend of 9–10 December. Further strikes were called for 24 hours on 23 December and 27 December, due to what the RMT called the "shocking attitude of the company management" towards the dispute. During the strikes, CrossCountry operated a reduced hourly service on most long-distance routes between 9am and 7pm, with most services cancelled outside of these times. Local services across the Midlands did not operate.


2016–2019 United Kingdom rail strikes, Industrial action, CrossCountry
Further strikes were called in early January 2018, scheduled for 48 hours on 20–21 January and 24 hours on 28 January. Following negotiations between the RMT and CrossCountry, the planned January strikes were called off on 11 January.


2016–2019 United Kingdom rail strikes, Industrial action, CrossCountry
In late January, the Transport Salaried Staffs' Association (TSSA) threatened CrossCountry with industrial action after staff were offered only a 1% pay rise, compared to a 3.3% pay rise offered at other Arriva-owned train operating companies. Industrial action was planned for 26 January, but it was later called off as CrossCountry matched demands for an equal pay rise for CrossCountry employees.


2016–2019 United Kingdom rail strikes, Industrial action, Eurostar
On 29 February 2016, the RMT opened a formal dispute with Eurostar over concerns regarding staff rostering, particularly allegations of train managers being made to work alone on some sections of route, following an incident involving a female train manager being charged with gross misconduct after refusing to operate a service which would have resulted in her running a section of the route with no other Eurostar staff members on board. Eurostar train managers based at St Pancras International station in London were balloted for potential industrial action several months later, which passed in favour of full strike action.


2016–2019 United Kingdom rail strikes, Industrial action, Eurostar
Seven days of strikes were announced for two weekends in August 2016: for 96 hours on 12–15 August, coinciding with the Assumption Day public holiday in Belgium and France; and for 72 hours on 27–29 August, coinciding with the late August bank holiday weekend in the United Kingdom. The TSSA announced that it would be joining both RMT strikes for 48-hour periods, covering 14–15 August and 28–29 August. During the strikes, Eurostar planned to operate a mostly normal level of service, with eight services expected to be cancelled across the four-day first strike.


2016–2019 United Kingdom rail strikes, Industrial action, Eurostar
The first joint RMT/TSSA strike, scheduled to last for four days amongst RMT-affiliated staff over the Assumption Day weekend, began at midnight on Friday 12 August. Following progress made in negotiations on 12 August, the RMT strike was cut short, ending after only 24 hours at midnight on 13 August. The TSSA strike, which had not yet started, was cancelled. Following further successful negotiations, the second joint RMT/TSSA strike planned for the late August bank holiday weekend was cancelled; the dispute between the RMT, the TSSA and Eurostar has now been resolved.


2016–2019 United Kingdom rail strikes, Industrial action, Eurostar
In October 2016, the RMT released a statement expressing concern at the prospect of 80 redundancies by Eurostar, but no further action was taken in this dispute.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
Southern conductors went on strike on 26 April 2016. Afterwards, on 29 April, talks were held at the dispute resolution service Acas (Advisory, Conciliation and Arbitration Service), but this did not stop the strikes, and more were called. As a result of the strikes and a high period of staff sickness, Southern introduced an "amended timetable [that] would be a temporary measure until staffing returned to normal", with slightly reduced service levels, from 5 July.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
The RMT trade union said that 350 services would be cancelled every day in the new timetable; the company previously ran 2,242 daily weekday services under the standard timetable. The RMT denied that high levels of sickness were the cause of cancellations, while agreeing that there were an insufficient number of guards and drivers.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
In November 2016, ASLEF held a ballot for drivers working for Southern on whether they wanted to go on strike. The strike ballot was initially suspended due to "technical difficulties", but when the ballot was re-run, drivers voted overwhelmingly to strike. As a result, on 6 December, ASLEF drivers started an indefinite overtime ban. ASLEF drivers at Southern went on strike on 13–14 and 16 December.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
As the strikes would result in no trains being able to run on the Southern network, Southern's parent company, Govia Thameslink Railway, launched a High Court case in a bid to stop them, citing that they "breach customer rights under EU law". However, the court ruled that ASLEF could strike. On 13 December, the first day of ASLEF strike action, Southern took its case to the Court of Appeal, but judges upheld the decision.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
The strikes by ASLEF were branded as "causing the worst rail disruption in 20 years" by The Guardian as all 2,242 daily weekday services operated by Southern were cancelled throughout the strikes. Thameslink services became much busier as a result of the strike, and other operators were accepting Southern's tickets. GTR and ASLEF held further talks at Acas, but no deal was reached, despite reports that "progress has been made" within the talks.


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
In December 2016, ASLEF announced that its drivers would be holding a week-long strike on the Southern network alongside RMT drivers from 9 to 16 January. On 4 January, three days of the planned one-week strike were called off, with the remaining strike dates being pushed back to the end of the month. The RMT's leader, Mick Whelan, threatened that "more strikes were to come", while Southern described ASLEF as "showing pure contempt for the travelling public".


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
On 5 January 2017, the Office of Rail and Road published a report into Southern's plans for driver only operation. The report declared that driver only operation on Southern services were "safe if conditions are met". As a result of the report, the government called on the unions to "end the strikes immediately", but Whelan argued that "the report does not give driver-only operation a clean bill of health".


2016–2019 United Kingdom rail strikes, Industrial action, Govia Thameslink Railway
On 11 January 2018, Govia Thameslink Railway announced that it had launched a legal challenge at the Supreme Court against ASLEF. The next day, the RMT announced that Southern conductors would walk out on strike on 23 January for 24 hours.


2016–2019 United Kingdom rail strikes, Industrial action, Greater Anglia
In May 2017 the RMT raised concerns over plans by Abellio Greater Anglia to close 57 of its 64 station ticket offices. On 17 July, the RMT announced that it would ballot Greater Anglia staff for potential strike action over the planned ticket office closures and the introduction of driver-only operation on Greater Anglia services. The ballot was later suspended indefinitely due to progress in negotiations. The next day, the RMT started an online petition to halt the closures. On 20 July, Clive Lewis, Member of Parliament for the Norwich South constituency, tabled a motion in the House of Commons raising concerns and seeking clarification over Greater Anglia's closure plans.


2016–2019 United Kingdom rail strikes, Industrial action, Greater Anglia
On 14 August, the RMT announced that due to a breakdown in negotiations it would resume balloting Greater Anglia staff over industrial action. The ballot resulted in a vote in favour of full strike action, with the first two 24-hour strikes taking place on 3 October and 5 October. Disruption during the Greater Anglia guard strikes was limited by the company training office staff and placing them into contingency roles on trains during the strike days; the RMT criticised this move, accusing Greater Anglia of raising a 'scab army' to quash the industrial action, threatening passenger safety. In response, the RMT launched a full overtime and rest day working ban between 10 October and 6 November.


2016–2019 United Kingdom rail strikes, Industrial action, Greater Anglia
Several incidents occurred involving substitute guards, referred to as "Persons Utilised as Guards" or PUGs, during the two October strikes. The most serious occurred on 3 October, involving the 13:50 service from Peterborough to Ipswich. Upon arrival at Ipswich, the PUG unlocked the doors on the wrong side of the train, resulting in many passengers disembarking onto the tracks. Nobody was injured, although the RMT claimed that passenger safety was "jeopardised".


2016–2019 United Kingdom rail strikes, Industrial action, Greater Anglia
Further minor incidents involving improperly-trained PUGs occurred on trains at Cromer and Colchester on 3 October, resulting in the RMT alerting the Office of Rail and Road (ORR, the rail safety regulator), over Greater Anglia's actions. The ORR issued an interim report on 20 October, identifying "numerous deficiencies" in the use of PUGs during the strikes. In the aftermath, the RMT called for Abellio to be stripped of the East Anglia rail franchise.


2016–2019 United Kingdom rail strikes, Industrial action, Greater Anglia
Further strike action was held for 48 hours on 8–9 November. Despite the controversy over the use of PUGs in the October, the ORR approved Greater Anglia's proposed strike day timetable, which again used PUGs to maintain a similar level of service to the usual timetable. Another 24-hour strike was held on 27 December, followed by three further 24-hour strikes on 8, 10 and 12 January 2018. A full service was again operated during these strikes, using PUGs. The dispute between the RMT and Greater Anglia was resolved on 19 July 2018, where it was agreed that drivers would operate the door providing a second member of staff was onboard.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
In January 2016, the RMT published the results of a survey in which it claimed that 78% of regular Merseyrail passengers opposed proposals for the operator to introduce driver-only operation and remove guards from its services. The RMT launched a public campaign lobbying for Merseyrail to keep the guard on the train.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
Relations between the RMT and Merseyrail broke down in May 2016 following a lack of progress in negotiations and concerns over planned staff rostering by Merseyrail on the day of the Rock 'n' Roll Liverpool Marathon & 1/2 Marathon, scheduled for 29 May. As a result, the RMT announced that members would be balloted over potential strike action. The ballot was eventually cancelled without any industrial action following an improvement in negotiations.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
On 16 December 2016, Merseytravel announced that it would be taking delivery of 52 new four-car Stadler METRO electric multiple units, designated as the Class 777, from 2020 onwards to replace the existing Merseyrail fleet. The trains were ordered in a driver-only configuration, with Merseyrail announcing that guards would be removed from its services following the introduction of the Class 777 trains. As a result, in early January, the RMT issued a statement requesting clarification from Merseyrail on the issue of driver-only operation on its services, setting a deadline of 26 January to resolve the dispute. When the deadline passed without progress in talks, the RMT moved officially into dispute with Merseyrail on 2 February, launching a ballot of its members.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
On 28 February, the RMT issued a statement confirming that 81.8% of union members at Merseyrail had voted in favour of industrial action, setting the first strike for 24 hours on 13 March; in addition, members were instructed to take part in an indefinite overtime ban, commencing from 7 March. Merseyrail launched legal action at the High Court to prevent the strikes going ahead. However, its case for an injunction against industrial action was unsuccessful. On the day of the strike, services were suspended entirely on the Ellesmere Port, Hunts Cross and Kirkby lines, while 23 stations on other lines were closed due to lack of staff. Most services began to wind down from around 17:30.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
On 17 March, four days after the first strike and with the overtime ban still in effect, the RMT confirmed that it would meet Merseyrail representatives for "exploratory talks" to resolve the conflict. On 20 March the negotiations collapsed after three days of talks. The next day, the RMT announced details of further strike action, scheduled for 24 hours on 8 April, the date of the Grand National at Aintree Racecourse.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
Merseytravel criticised the choice of date for the industrial action, stating that it would "do immeasurable damage" to Liverpool's reputation; the RMT responded by stating that it "wanted to make the loudest voice possible". Services were largely reduced across the Merseyrail network during the strike, although trains continued to operate every seven to eight minutes between central Liverpool and Aintree at key times to serve the Grand National. Although ASLEF was not officially a part of the industrial action, reports suggested that Merseyrail staff affiliated with ASLEF also refused to cross picket lines set up by the RMT, adding to the disruption.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
Negotiations between the RMT and Merseyrail collapsed again on 24 April. A third 24-hour strike was announced, due to place on 30 May. Following the Manchester Arena bombing on 22 May, the RMT announced that it would be suspending all industrial action nationwide indefinitely, scrapping plans for the 30 May strike on Merseyrail. In June 2017, a lack of progress in negotiations led to the RMT calling three new 24-hour strikes, scheduled for 8, 10 and 23 July. During the strikes, 33 Merseyrail stations were closed and a reduced level of service was in operation. The strike on 23 July caused disruption to passengers travelling to the final day of the 2017 Open Championship at the Royal Birkdale Golf Club.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
The day after the most recent strike action, on 24 July, representatives from the RMT met with Steve Rotheram, the Mayor of the Liverpool City Region. Further talks between Rotheram, the RMT and Merseyrail failed to avert further strike action being announced by mid-August, which took place for 24 hours on 1 September and for 48 hours on 3–4 September. Further 24-hour strikes took place on 3 and 5 October another happened on 8 November. adding to disruption from the planned three-week closure of Liverpool Lime Street station for refurbishment over that period. Another 24-hour strike took place on 22 December, followed by three more on 8, 10 and 12 January 2018.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
On 15 February 2018, the RMT announced that a further 24-hour strike would take place, scheduled for 3 March. It was the sixteenth day of strike action on Merseyrail since the dispute began.


2016–2019 United Kingdom rail strikes, Industrial action, Merseyrail
On 31 August 2018, it was announced that Merseyrail had abandoned driver-only trains, thus bringing an end to the dispute.


2016–2019 United Kingdom rail strikes, Industrial action, ScotRail
On 15 April 2016, the RMT threatened to launch a ballot of its members over possible industrial action on the Abellio ScotRail network as a result of ScotRail's proposals to introduce driver-only operation. Following a breakdown in negotiations, a ballot was launched, with union members voting 75% in favour of industrial action, from a 75% turnout, on 7 June.


2016–2019 United Kingdom rail strikes, Industrial action, ScotRail
24-hour strikes were called for 21 June, 23 June, 3 July, 14 July, 24 July and 31 July, as well as 48-hour strikes for 25–26 June, 10–11 July and 16–17 July; overtime bans were also announced for the whole of June and July 2016. On 20 June, the day before the first planned strike, RMT members held a protest outside the head office of Abellio ScotRail.


2016–2019 United Kingdom rail strikes, Industrial action, ScotRail
In late July, further strike action was announced for 24-hour periods on 7 August and 11 August, and for 48 hours on 13–14 August. On 1 August, Abellio ScotRail threatened the RMT with legal action over further strikes. On 3 August, it was announced that the RMT's planned industrial action on ScotRail during August had been suspended, as negotiations with Abellio continued.


2016–2019 United Kingdom rail strikes, Industrial action, ScotRail
On 20 September, the RMT announced that it had reached a deal with Abellio ScotRail protecting the role of guards on its trains. The RMT called the deal "a major breakthrough in the battle against Driver Only Operation" which would be used as a "benchmark" for further negotiations with other operators. The deal was accepted by RMT members after a referendum on 5 October, formally closing the dispute.


2016–2019 United Kingdom rail strikes, Industrial action, ScotRail
From November 2016, the RMT called for Abellio to be stripped of the ScotRail franchise, with it being returned to public ownership, due to a slump in performance and an alleged increase in "profiteering". On 14 September 2017, the RMT voted in favour of further industrial action on the ScotRail network over plans to cut CCTV operator jobs at two locations, although no date was set for industrial action.


2016–2019 United Kingdom rail strikes, Industrial action, First Great Western / Great Western Railway
The introduction of the Class 800 on the Great Western Main Line saw a series of strikes on First Great Western about plans to introduce DOO and other changes to working practices, including changes to the customer experience such as the removal of buffet cars. Despite multiple strikes, the company removed them. But some of the other issues were resolved. In 2016 another series of strikes took place over its outsourced cleaners contract.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
The RMT opened its first ballot of Virgin Trains East Coast (VTEC) staff in July 2016, regarding concerns over the planned introduction of driver-only operation, the possibility of around 200 compulsory redundancies within the operation and concerns over staff pay. On 9 August, the RMT issued a statement confirming that the ballot had passed 84% in favour of full strike action.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
Three 24-hour strikes, involving all VTEC staff members except depot maintenance workers, were announced for August 2016, starting at 03:00 BST on 19, 26 and 29 August. Additionally, a 48-hour overtime ban was to be enforced from 03:00 on 27 August. On 16 August, it was announced that all industrial action at VTEC had been suspended indefinitely by the RMT to allow for further negotiations, with all three strikes and the overtime ban being cancelled as a result.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
Following a breakdown in negotiations in September, further industrial action was announced, with the first 24-hour strike scheduled for 3 October.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
The RMT said that the strike was "well-supported" and "solid", although VTEC ran a near-normal level of service throughout the strike, following what the RMT described as "the biggest scabbing operation in recent rail history"; the RMT later claimed that this "cavalier management" resulted in an incident in which the 08:30 VTEC service from Edinburgh Waverley to London King's Cross was allowed to operate with the doors of a defective carriage locked out of use, but still carrying passengers, against railway guidelines. The service was eventually terminated short at Newcastle after the RMT and Office of Rail and Road alerted VTEC to the incident.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
Further industrial action was announced in early 2017 as negotiations once again stalled. A 48-hour strike was scheduled for 28–29 April. In a statement on 24 April, the RMT announced that all industrial action on VTEC had once again been indefinitely suspended following "progress" in talks between the union and VTEC, resulting in the planned April strike being cancelled. As of February 2018, there has been no further industrial action at VTEC.


2016–2019 United Kingdom rail strikes, Industrial action, Virgin Trains East Coast
In June 2017, the RMT called for the InterCity East Coast franchise to be returned to public ownership, as it claimed the franchise was on the brink of "financial collapse" following the announcement by Stagecoach that the franchise had made a loss of £84 million since its takeover in March 2015. In February 2018, the government confirmed that Stagecoach/Virgin would be stripped of the franchise "within a small number of months" due to its failure to meet financial obligations, marking the third collapse of the franchise in eleven years.


2016–2019 United Kingdom rail strikes, Industrial action, Other operators
Industrial action has been threatened by the RMT amongst staff of various other operators. In December 2016, cleaners working for employment agency Servest UK, outsourced by Great Western Railway, voted 98% in favour of strike action over concerns about inequality in pay and working conditions compared to cleaners employed directly by GWR. These concerns were raised following a difficult period transferring the outsourcing contract from Mitie to Servest UK earlier in 2016, resulting in the creation of what the RMT called a "two-tier workforce". Two 24-hour cleaners' strikes took place from 06:00 on 16 December and 23 December. A further 48-hour strike was held between 06:00 on 19 January and 06:00 on 21 January 2017, before further industrial action was suspended by the RMT as negotiations improved. In July 2017, a new pay deal was accepted at a ballot of RMT members, formally ending the dispute.


2016–2019 United Kingdom rail strikes, Industrial action, Other operators
A similar situation arose at Southeastern, whose cleaners' jobs are outsourced to Wettons. In September 2017, the RMT announced that Southeastern cleaners employed by Wettons would be balloted for potential industrial action over pay and working conditions. The ballot passed in favour of industrial action. The first strike by Wettons cleaners at Southeastern took place for 24 hours from 20:30 on 19 October. There has been no further industrial action since the mid-October strike, although negotiations remain ongoing between the RMT, Southeastern and Wettons.


2016–2019 United Kingdom rail strikes, Industrial action, Other operators
In September 2017, the RMT warned that staff at East Midlands Trains would be balloted for potential strike action due to negotiations breaking down in an ongoing pay dispute; the dispute was later resolved without industrial action. East Midlands Trains at present has no plans to introduce driver-only operation.


2016–2019 United Kingdom rail strikes, Industrial action, Other operators
In January 2017, the RMT announced that it would ballot guards at London Midland for potential industrial action over concerns regarding the introduction of externally-contracted security staff on its trains at the end of December 2016, which the RMT alleged would replace the role of "safety-critical" guards on some services, paving the way for DOO operation. London Midland denied having plans in place to implement DOO operation on its network. Following negotiations with the RMT, London Midland ceased using externally-contracted security staff on its trains on 30 January; as a result, the RMT suspended its ballot on 2 February, averting potential industrial action, before formally declaring the dispute closed.


2016–2019 Wau clashes
Armed clashes took in Wau State from late June 2016 to January 2019 between the Dinka-dominated Sudan People's Liberation Army (SPLA) and local opposition forces, consisting of tribal Fertit militias as well as fighters claiming allegiance to Riek Machar. It is unclear to what extent these rebels were actually part of the SPLM-IO or acting independently while using the SPLM-IO's name. The clashes resulted in the arrest of the state's governor, Elias Waya Nyipuoc, widespread death and destruction in the state capital, Wau town, and the displacement of up to 150,000 people.


2016–2019 Wau clashes, Background
Rivalries and violence between various ethnic groups have a long history in South Sudan. Many minorities in the country believe that their communities are threatened and marginalized by the Dinka people who have traditionally dominated the administration of southern Sudan. The Fertit are one such minority, and mostly concentrated in areas of former Western Bahr el Ghazal, including Wau State. The animosity between Dinka and Fertit became deeply entrenched during the Second Sudanese Civil War, when the Dinka-dominated Sudan People's Liberation Army (SPLA) waged a rebellion against the Sudanese government.


2016–2019 Wau clashes, Background
Many Fertit opted to stay loyal to Sudan or remain neutral, as they feared suppression at the hands of the Dinka in an independent South Sudan. The SPLA responded by attacking Fertit as perceived enemies of the rebellion, causing militant Fertit to organize the so-called Army of Peace in self-defense. This militia then became involved in widespread massacres of Dinka from 1986, worsening ethnic relations even further.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
In 2015, the South Sudanese government and the SPLM-IO signed the ARCSS peace deal in an attempt to end the civil war. Both sides used concessions in the agreement to their advantage, however, and the agreement gradually fell apart. Wau State was an area which was affected by the ARCSS. The SPLM-IO mobilized forces in Wau, and then demanded that these rebels were granted cantonment zones and be included in the ARCSS' security provisions. This was unacceptable to Gen. Paul Malong Awan, the SPLA's chief of staff, who responded by mobilizing loyal army elements such as Mathiang Anyoor units.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
He then circumvented the formal chain of command, and ordered these SPLA troops to crush the opposition by force, even though the peace agreement was still in force. This resulted in growing ethnic tensions in Wau State from early December 2015. The SPLA soldiers deployed to the region for counter-insurgency operations mostly belonged to tribes from Northern Bahr el Ghazal and Warrap, while the local SPLM-IO fighters intensified their operations.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
On 2 December, the SPLM-IO reportedly attacked government units at Busseri and Firka, causing the SPLA to send reinforcements to these area, which were in turn ambushed and defeated by the rebels. Three days later, clashes between rebel and government fighters broke out around Bisellia, Bazia, Faraj Allah, Bringi, Mapel, and the Bo River Post. Amid the fighting there were reports that the Ugandan People's Defence Air Force and/or the South Sudan Air Force conducted aerial attacks against both rebel as well as civilian targets using attack helicopters. The UNO consequently criticised the SPLA for breaching the national ceasefire by conducting offensive operations.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
At the same time, Human Rights Watch reported that the newly deployed government soldiers, mostly Dinka, began to abuse the local Fertit population, forcing tens of thousands to flee Wau. Many civilians were arrested and then murdered as purported SPLM-IO supporters. Governor Elias Waya Nyipuoc admitted that by 30 May 2016, he had confirmed that at least 100 civilians had been murdered by SPLA soldiers, and had reported the cases to the government. Unable to stop them, he said that the soldiers probably abused the local population because the government had failed to pay or feed them.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
This caused them to rob what they needed. Waya argued that this behavior was to be expected when the government neglected their military forces. The SPLA leadership, meanwhile, denied that any abuses at the hands of SPLA soldiers had taken place in Wau. In addition to the violence of the SPLA against civilians, no progress was made in the attempts to enforce the ceasefire between the SPLA and local SPLM-IO groups, as the government denied that the SPLM-IO had any presence in the whole Bahr el Ghazal region to which Wau State belongs. As result, no agreement for SPLM-IO cantonment areas in Wau State was reached. On 9 April, the SPLA command even announced that they would launch an offensive in Bahr el Ghazal and Equatoria to destroy all SPLM-IO units in these regions.


2016–2019 Wau clashes, Background, Increasing violence in Wau State
At the same time, the SPLA soldiers were accused by the opposition of intensifying their abuses of Fertit civilians, while reportedly working together with local Dinka militants and armed cattle herders in their attacks. The violence in Wau further increased in June, as individual Fertit began to fight back by murdering soldiers, policemen and Dinkas. This in turn caused revenge killings by Dinkas and SPLA against Fertit. In addition, insecurity in the state increased dramatically, as local SPLM-IO and SPLA units ignored the ceasefire and clashed on several occasions at Bagari and Angu Angu. At least 8 SPLA soldiers were killed, while Raga town in the neighbouring Lol State was overrun by rebels for a short time, resulting in the death of several bodyguards of the local governor.


2016–2019 Wau clashes, Clashes, Battle in Wau town
By 23 June, a larger battle south of the state capital, Wau town, broke out between SPLA and SPLM-IO, the latter claiming to fight in order to protect the local Fertit people from attacks by the Dinka-dominated SPLA. As result of the increasing violence, a state of emergency was declared in Wau town, and the SPLA's 5th Division moved in, officially to prevent further escalation of violence. These forces were under the command of Lt. Gen. Gabriel Jok Riak, who had been accused of human rights abuses by the United Nations during the South Sudanese Civil War.


2016–2019 Wau clashes, Clashes, Battle in Wau town
Governor Waya initially claimed to support the emergency declaration, stating "All who are here are rebels, so the Division [5 of the] SPLA is ready and even those who are just walking around are ready". However, opposition groups claimed that the army soon began to plunder the state capital, and to assault the civilian population, leading Governor Waya to criticise the soldiers. On 24 June 2016, President Kiir unexpectedly sacked Waya, and just a few hours later, had him arrested.


2016–2019 Wau clashes, Clashes, Battle in Wau town
A local SPLA commander declared that Waya had been arrested because he was responsible for the deteriorating situation in the state, claiming that he had no respect for the military and talked "nonsense". A few days later, a document began to circulate on the internet that claimed that Lt. Gen. Mangar Buong Aluenge of the SPLA had plotted from the very beginning to remove and arrest Waya, while the Society for Threatened Peoples believed that Waya's criticism of the army had led to his arrest.


2016–2019 Wau clashes, Clashes, Battle in Wau town
As result of Waya's dismissal, the situation escalated completely, as a heavy battle broke out in Wau town on evening of 24 June. Dinka youth militants in civilian clothing and uniforms entered Wau's south-western neighbourhoods, where they murdered and raped Fertit civilians. According to independent and opposition sources, as army soldiers and Dinka militias intensified their attacks on the town's Fertit population, many locals picked up arms and began to fight the pro-government forces. They were supported by armed Fertit youth from the countryside, who also came into Wau town to take revenge against the Dinkas.


2016–2019 Wau clashes, Clashes, Battle in Wau town
The SPLM-IO claimed that their forces had stayed out of Wau town, but attacked SPLA soldiers to protect Fertit civilians in the settlement's southern outskirts. Massacres continued throughout the night, but by late 25 June the SPLA claimed to have secured the town and began to search for hiding insurgents. The army imposed a curfew in Wau town the next day, and, according to local civilians, together with Dinka tribal fighters once again began to kill, rape and rob the local Fertit civilians.