Ghouta chemical attack

From Infogalactic: the planetary knowledge core
(Redirected from 2013 Ghouta attacks)
Jump to: navigation, search
Ghouta chemical attack
Part of the Syrian Civil War
Ghouta massacre1.JPG
Some of the victims of the Ghouta chemical attack.
Location Ghouta, Syria
Coordinates Eastern Ghouta: within 750 meters (2,460 ft) from[1]
Lua error in package.lua at line 80: module 'strict' not found.
Western Ghouta: within 500 meters (1,600 ft) from[1]
Lua error in package.lua at line 80: module 'strict' not found.
Date 21 August 2013 (2013-08-21)
Attack type
Chemical attack
Deaths Various estimates:
at least 281 (French intelligence)[2]
at least 350 (UK intelligence)[3]
355 (MSF)[4]
494 (Damascus Media Office)[5]
502 (SOHR)[6]
635 (SRGC)[7]
924 (VDC)[8]
1,300 (SNC)[9]
1,338 (LCC)[10]
1,429 (United States)[11][12]
1,729 (FSA)[13]
Injured 3,600 patients displaying neurotoxic symptoms in 3 hospitals supported by MSF[4]
Perpetrators Unknown

The Ghouta chemical attack occurred in Ghouta, Syria, during the Syrian Civil War in the early hours of 21 August 2013. Two opposition-controlled areas in the suburbs around Damascus, Syria were struck by rockets containing the chemical agent sarin. Estimates of the death toll range from at least 281 people[2] to 1,729.[13] The attack was the deadliest use of chemical weapons since the Iran–Iraq War.[14][15][16]

Inspectors from the United Nations Mission arrived in Syria on 18 August, three days before the attack. They were present at the Syrian government's invitation to look into previous alleged chemical weapons use.[17](p6) The inspectors were staying in central Damascus, 12 kilometers or less from all three attack sites.[18] The UN requested access to sites in Ghouta the day after the attack.[19][20][21] Syrian government and rebel forces continued to clash in the area on 22 and 23 August.[22][23] The Syrian military continued to shell Ghouta,[21] and the UN called for a ceasefire to allow inspectors to visit the Ghouta sites.[19] The Syrian government granted the UN's request on 25 August.[24][25][26] The inspectors visited and investigated Moadamiyah in Western Ghouta on 26 August and Zamalka and Ein Tarma in Eastern Ghouta on 28 and 29 August.[17](p6)[27][28]

In mid-September 2013, the UN investigation team reported that it had confirmed the use of sarin in the Ghouta attack.[17] The Mission "collected clear and convincing evidence that surface-to-surface rockets containing the nerve agent sarin were used in Ein Tarma, Moadamiyah and Zalmalka in the Ghouta area of Damascus."[29] In 2014, a report of the UN Human Rights Council found that "significant quantities of sarin were used in a well-planned indiscriminate attack targeting civilian-inhabited areas, causing mass casualties. The evidence available concerning the nature, quality and quantity of the agents used on 21 August indicated that the perpetrators likely had access to the chemical weapons stockpile of the Syrian military, as well as the expertise and equipment necessary to manipulate safely large amount of chemical agents."[30] It also stated that the chemical agents used in the Khan al-Assal chemical attack "bore the same unique hallmarks as those used in Al-Ghouta."[30][31][32]

The Syrian government and opposition blamed each other for the attack.[33] Many governments said the attack was carried out by forces of Syrian President Bashar al-Assad,[34] a conclusion echoed by the Arab League and the European Union.[35][36][37] The Russian government called the attack a false flag operation by the opposition to draw foreign powers into the civil war on the rebels' side.[38] Åke Sellström, the leader of the UN Mission, characterized government explanations of rebel chemical weapons acquisition as unconvincing, resting in part upon "poor theories."[39]

Several countries including France, the United Kingdom, and the United States debated whether to intervene militarily against Syrian government forces.[40][41][42][43] On 6 September 2013, the United States Senate filed a resolution to authorize use of military force against the Syrian military in response to the Ghouta attack.[44] On 10 September 2013, the military intervention was averted when the Syrian government accepted a US–Russian negotiated deal to turn over "every single bit" of its chemical weapons stockpiles for destruction and declared its intention to join the Chemical Weapons Convention.[45][46]

Background

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The Ghouta area is composed of densely populated suburbs to the east and south of Damascus, part of the province of Rif Dimashq.[47] Ghouta is a primarily conservative Sunni region.[48] Since early in the civil war, civilians in rebel-held Eastern Ghouta have almost entirely sided with the opposition to Syria's government.[49][50] The opposition has controlled much of Eastern Ghouta since 2012, partly cutting off Damascus from the countryside.[47] Muadamiyat al-Sham in Western Ghouta had been under government siege since April 2013.[51] Ghouta had been the scene of continuing clashes for more than a year before the chemical attack, with government forces launching repeated missile assaults trying to dislodge the rebels. The week of the attack, the Syrian government launched an offensive to capture opposition-held Damascus suburbs.[50]

The attack came one year and one day after US President Barack Obama's 20 August 2012 "red line" remarks, in which he warned: "We have been very clear to the Assad regime, but also to other players on the ground, that a red line for us is we start seeing a whole bunch of chemical weapons moving around or being utilized. That would change my calculus. That would change my equation."[52][53][54] Syria was one of five non-signatories to the 1997 Chemical Weapons Convention at the time. After the "red line" remarks, and before the chemical attack in Ghouta, chemical weapons were suspected to have been used in four attacks in the country.[55]

Khan al-Assal chemical attack

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The Khan al-Assal chemical attack occurred on 19 March 2013, when a government-controlled area of Khan al-Asal was struck by a rocket containing the nerve agent sarin. The Syrian government reported to the United Nations that one soldier and 19 civilians died and that 17 soldiers and 107 civilians were injured.[56](p32) A medic at the local civilian hospital said he personally had witnessed Syrian army soldiers helping the wounded and dealing with fatalities at the scene.[57]

The Syrian government informed the UN Security Council about the attack the day it happened.[58] The next day, the Syrian government requested a specialized, impartial and independent UN mission to investigate the attack.[59][60] As a response to the Syrian request, UN Secretary-General Ban Ki-moon decided to create a UN fact-finding mission to investigate the attack. The mission was named the "United Nations Mission to Investigate Alleged Uses of Chemical Weapons in the Syrian Arab Republic."[60][61] The Syrian government later refused to allow the UN investigation to be expanded to places outside Khan al-Assal.[62]

On 23 April 2013, the New York Times reported that the British and French governments had sent a confidential letter to the UN Secretary-General, stating there was evidence that the Syrian government had used chemical weapons in Aleppo, Homs and perhaps Damascus. Israel also claimed that the Syrian government had used chemical weapons on 19 March near Aleppo and Damascus.[63] On 24 April, Syria blocked UN investigators from entering Syria, while UN Under-Secretary for Political Affairs Jeffrey Feltman said this would not prevent an inquiry from being carried out.[64] US Secretary of Defense Chuck Hagel stated on 25 April that US intelligence showed the Assad government had likely used sarin on a small scale.[65] However, the White House announced that "much more" work had to be done to verify the intelligence assessments.[66]

Jobar chemical attacks

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

After clandestinely spending two months around Damascus in the spring of 2013, several reporters for the French news media Le Monde witnessed the Syrian army's use of chemical weapons on civilians in the Jobar chemical attacks between April 12 and 14.[67][68] French intelligence later said that samples from the Jobar attack in April had confirmed the use of sarin.[69] However, the UN fact-finding mission that investigated the alleged attack did not find sufficient or credible information to support the allegation.[56](p10)

Independent International Commission of Inquiry on the Syrian Arab Republic

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The United Nations Human Rights Council established the Independent International Commission of Inquiry on the Syrian Arab Republic on 22 August 2011 to investigate human rights violations during the Syrian civil war. One of the topics the commission investigated was possible use of chemical weapons. In early June 2013, the Fifth Report of the Commission of Inquiry stated that there were reasonable grounds to believe that limited amounts of toxic chemicals were used in four attacks, but more evidence was needed "to determine the precise chemical agents used, their delivery systems or the perpetrator."[70](p21)[71][72] On 22 June, the head of the Commission of Inquiry, Paulo Pinheiro, said the UN could not determine who used chemical weapons in Syria based on evidence sent by the United States, Britain and France.[73]

Assessments prior to the attack

US assessment

On 13 June 2013, the United States government publicly announced it had concluded that the Assad government had used limited amounts of chemical weapons on multiple occasions against rebel forces, killing 100 to 150 people. US officials stated that sarin was the agent used.[74] Deputy National Security Advisor Ben Rhodes did not say whether this showed that Syria had crossed the "red line" established by President Obama in August 2012. Rhodes stated: "The president has said that the use of chemical weapons would change his calculus, and it has."[75] The French government announced that its own tests confirmed US assertions.[76]

Russian assessment

Russian Foreign Minister Sergei Lavrov said "the accusations of Damascus using chemical weapons put forth by the USA are not backed by credible facts."[77] Lavrov further stated that the Syrian government had no motive to use chemical weapons since the government already maintained a military advantage over the rebel fighters.[78]

Attacks

The attacks affected two separate opposition-controlled districts in the Damascus suburbs, located 16 kilometres apart.[1](p1)

Eastern Ghouta attack

The first attack took place around 2:30 a.m. on 21 August 2013[79][80] in Eastern Ghouta, a rebel-held suburb to the east of Damascus.[81] The area was on a rebel weapons supply route from Jordan and had been under siege by the Syrian military and Hezbollah for months.[82][83]

At least 8, and possibly 12, rockets struck within a 1500 by 500 meter area in the Zamalka and nearby Ein Tarma neighborhoods.[note 1] The rockets were all of the same improvised type, each with an estimated capacity to carry 50–60 liters (11–13 imp gal; 13–16 U.S. gal) of sarin.[1](p9)[17](p24) The rocket engine was similar in type and parameters to a 122 mm GRAD unguided surface-to-surface rocket, while the chemical warhead and the stabilization fin was of an artisan-type.[1][84] One (or both) of the labs examining the environmental samples taken from Zamalka (and Ein Tarma[17](pp28–29)) found at least traces of sarin in 14 of the 17 cases.[56](pp45–49) One of the labs described the sarin level as a "high level concentration" in 4 of the 17 samples.[56](pp45–49)

Western Ghouta attack

The second attack took place in the Western Ghouta area around 5:00 in the morning on 21 August. On 22 August, a witness who works for Moadamiya media center said he had counted seven rockets that fell in two areas of Moadamiya during the early morning of 21 August. He said four rockets hit next to the Rawda Mosque and another three in the area between Qahweh Street and Zeytouneh Street, which he said was approximately 500 meters to the east of the Rawda Mosque. He said all the rockets were of the same type.[1]

While no chemical warhead was ever found in the Western Ghouta area, one rocket engine has been identified as a 140mm M-14 unguided surface-to-surface rocket. This type of rocket can be fitted with three types of warheads: high explosive-fragmentation, white phosphorus smoke, or a chemical warhead containing 2 liters (0.44 imp gal; 0.53 U.S. gal) of sarin.[1](p5) None of the 13 environmental samples taken from Western Ghouta tested positive for sarin, although three had "degradation and/or by-products."[56](pp43–45)

Chemical weapons capability

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

At the time of the attack, Syria was not a party to the Chemical Weapons Convention,[85] which prohibits the development, production, stockpiling, transfer and use of chemical weapons, although in 1968 it acceded to the 1925 Geneva Protocol for the Prohibition of the Use in War of Asphyxiating, Poisonous or Other Gases. In 2012 Syria publicly stated it possessed chemical and biological weapons and would use them if it faced a foreign attack.[86]

According to French intelligence, the Syrian Scientific Studies and Research Center (SSRC) is responsible for producing toxic agents for use in war. A group named "Branch 450" is allegedly responsible for filling munitions with chemicals and maintaining security of the chemical agent stockpiles.[69] As of September 2013, French intelligence estimated the Syrian stockpile at 1,000 tonnes, including Yperite, VX and "several hundred tonnes of sarin."[69]

The UK's Joint Intelligence Committee publicly dismissed the possibility of rebel responsibility for the attack in Ghouta, stating that rebels are incapable of an attack of its scale.[87] The Committee stated that "there is no credible intelligence or evidence to substantiate the claims or the possession of CW by the opposition."[88]

Åke Sellström, a Swedish scientist who led the UN mission to investigate the attacks, said it was difficult to see how rebels could have weaponized the toxins,[89] but admitted that he didn't know who the perpetrator was.[39] According to the Associated Press, "chemical and biological weapons experts have been relatively consistent in their analysis, saying only a military force with access to and knowledge of missile delivery systems and the sarin gas suspected in Ghouta could have carried out an attack capable of killing hundreds of people."[90]

Initial claims

Both the opposition and the Syrian government said a chemical attack was carried out in the suburbs around Damascus on 21 August 2013. Anti-government activists said the Syrian government was to blame for the attack, while the Syrian government said foreign fighters and their international backers were to blame.[80][91]

Opposition claims

On the day of the attack, George Sabra, the head of the Syrian National Council, said 1,300 people had been killed as shells loaded with poisonous gas rained down on the capital's eastern suburbs of Douma, Jobar, Zamalka, Arbeen and Ein Tarma.[92] A spokesman for the Free Syrian Army's Supreme Military Council, Qassim Saadeddine, said, "people are growing desperate as they watch another round of political statements and UN meetings without any hope of action."[81] Ahmad Jarba, who was the president of the Syrian National Coalition at the time of the attack, called on the UN investigators to travel to "the site of the massacre" and for an urgent United Nations Security Council meeting on the subject.[9] The Syrian Observatory for Human Rights said the attack was committed by the Syrian regime and called on Ban Ki-moon, Secretary-General of the United Nations, "to apply all pressure within his powers to pressure the Syrian regime."[93][94]

The next day, a spokesman for the Syrian National Coalition, Khaled al-Saleh, said at least six doctors died after treating victims, and that they didn't yet have the number of dead first responders.[95]

Government claims

Syria's Deputy Prime Minister for Economic Affairs, Qadri Jamil, said foreign fighters and their international backers were to blame for the attack.[91] Syrian state television, SANA, said the accusations were fabricated to distract a team of UN chemical weapons experts which had arrived three days before the attacks.[5] Syrian President Bashar al-Assad said the claims that his government had used chemical weapons would go against elementary logic and that "accusations of this kind are entirely political."[96][97]

UN investigation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The Four Seasons Hotel Damascus, where the UN team stayed.

On 18 August 2013, three days before the attack, a UN mission headed by Åke Sellström[17] arrived in Damascus with permission from the Syrian government to investigate earlier alleged chemical weapons use.[98] On the day of the attack, UN Secretary-General Ban Ki-moon expressed "the need to investigate [the Ghouta incident as] soon as possible," hoping for consent from the Syrian government.[98] The next day, UN High Commissioner for Human Rights Navi Pillay urged government and opposition forces to allow an investigation[99] and Ban requested the government provide immediate access.[24][100] On 23 August, clashes between rebel and government forces continued in and around Ghouta, government shelling continued and UN inspectors were denied access for a second day.[21][23] White House officials were convinced that the Syrian government was trying to hide the evidence of chemical weapons use by shelling the sites and delaying their inspection.[24] Ban called for a ceasefire to allow the inspectors to visit the attack sites.[19] On 25 August the government and various rebel factions agreed to a ceasefire for five hours each day from 26 to 29 August.[101][102]

Early in the morning of 26 August several mortars hit central Damascus, including one that fell near the Four Seasons hotel where the UN inspectors were staying.[103] Later in the day the UN team came under sniper fire en route to Moadamiyah in western Ghouta (to the southwest of central Damascus), forcing them to return to their hotel and replace one of their vehicles before continuing their investigation four hours later.[104][105] The attack prompted a rebuke from Ban toward the fighters.[106][107] After returning to Moadamiyah the UN team visited clinics and makeshift field hospitals, collected samples and conducted interviews with witnesses, survivors and doctors.[104] The inspectors spoke with 20 victims of the attacks and took blood and hair samples, soil samples, and samples from domestic animals.[107] As a result of the delay caused by the sniper attack, the team's time in Moadamiyah was substantially shortened, with the scheduled expiry of the daily cease-fire leaving them around 90 minutes on the ground.[102][107][108]

On 28 and 29 August the UN team visited Zamalka and Ein Tarma in Eastern Ghouta, east of central Damascus, for a total time of five-and-a-half hours.[17](p6) On 30 August the team visited a Syrian government military hospital in Mazzeh and collected samples.[109] The mission left Syria early on August 31,[110] promising to return to complete the original objective to investigate the previously alleged attack sites. The Syrian government wanted the mission to stay and investigate them at that time.[111]

UN Ghouta Area report

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The UN report on the investigation into the Ghouta chemical attacks was published on 16 September 2013. The report stated: "the environmental, chemical and medical samples we have collected provide clear and convincing evidence that surface-to-surface rockets containing the nerve agent sarin were used in Ein Tarma, Moadamiyah and Zamalka in the Ghouta area of Damascus."[17](p8)[29] UN Secretary-General Ban Ki-moon called the findings "beyond doubt and beyond the pale,” and clear evidence of a war crime. "The results are overwhelming and indisputable," he said. Ban stated a majority of the blood samples, environmental samples and rockets or rocket fragments recovered tested positive for sarin.[112] The report, which was "careful not to blame either side," said that during the mission's work in areas under rebel control, "individuals arrived carrying other suspected munitions indicating that such potential evidence is being moved and possibly manipulated."[113] The UN investigators were accompanied by a rebel leader:

<templatestyles src="Template:Blockquote/styles.css" />

A leader of the local opposition forces ... was identified and requested to take 'custody' of the Mission ... to ensure the security and movement of the Mission, to facilitate the access to the most critical cases/witnesses to be interviewed and sampled by the Mission and to control patients and crowd in order for the Mission to focus on its main activities.[17](p13)

The British UN Ambassador stated that the report's lead author, Åke Sellström, said the quality of the sarin used in the attack was higher than that used by Iraq in the Iran-Iraq war,[114] implying a purity higher than the Iraqi chemical weapons program's low purity of 45–60%.[115] (By comparison, Aum Shinrikyo used nearly pure sarin in the 1994 Matsumoto incident.[116])

Responses

According to Human Rights Watch, hundreds of kilograms of sarin were used in the attack, which it said suggested government responsibility, as opposition forces were not known to possess significant amounts of sarin.[117]

The Russian government dismissed the initial UN report after it was released, calling it "one-sided" and "distorted."[118] On 17 September, Russian Foreign Minister Sergei Lavrov reiterated his government's belief that the opposition carried out the attacks as a "provocation."[119] The United Nations High Representative for Disarmament Affairs Angela Kane said the inspection team would review Russia's objections.[111]

An August 2013 Scientific American article described difficulties that could arise when attempting to identify the manufacturer of sarin from soil or tissue samples.[120]

An Iranian chemical weapons expert, Abbas Foroutan, said in October 2013 that the UN should publish more details about the investigation than were provided in the report, including victims' pulse rates and blood pressure and their response to the atropine treatment, the victims' levels of acetylcholinesterase (sarin is an acetylcholinesterase inhibitor) and more technical details on the lab testing process.[121][122]

Final UN Mission report

The UN inspection team returned to Syria to continue investigations into other alleged chemical attacks in late September 2013. A final report on Ghouta and six other alleged attacks (including three alleged to have occurred after the Ghouta attack) was released in December 2013.[111] The inspectors wrote that they "collected clear and convincing evidence that chemical weapons were used also against civilians, including children, on a relatively large scale in the Ghouta area of Damascus on 21 August 2013." The conclusion was based on:

  • Impacted and exploded surface-to-surface rockets, capable to carry a chemical payload, were found to contain sarin;
  • Close to the rocket impact sites, in the area where patients were affected, the environment was found to be contaminated by sarin;
  • The epidemiology of over fifty interviews given by survivors and health care workers provided ample corroboration of the medical and scientific results;
  • A number of patients/survivors were clearly diagnosed as intoxicated by an organophosphorous compound;
  • Blood and urine samples from the same patients were found positive for sarin and sarin signatures.[56](p19)

UN Human Rights Council report

The 7th Report of the Independent International Commission of Inquiry on the Syrian Arab Republic, a different group than the UN fact-finding mission, stated the sarin used in the Ghouta attack bore the "same unique hallmarks" as the sarin used in the Khan al-Assal attack. The report, dated 12 February 2014, also indicated that the perpetrators likely had access to the chemical weapons stockpile of the Syrian military. These conclusions were based on the fact-finding mission's evidence, as the Commission of Inquiry did not conduct its own investigation of either chemical attack.[30]

Aftermath

The continuous fighting has severely limited the quality of medical care for injured survivors of the attack. A month after the attack, approximately 450 survivors still required medical attention for lingering symptoms such as respiratory and vision problems.[123] By early October 2013, the 13,000 residents of Moadhamiya, one of the places targeted in the August attack, had been surrounded by pro-government forces and under siege for five months. Severe malnourishment and medical emergencies become pressing as all supply lines had stopped.[124] Care for chronic symptoms of sarin exposure had become "just one among a sea of concerns."[123]

As countries such as the United States and the United Kingdom debated their response to the attacks, they encountered significant popular and legislative resistance to military intervention. In particular, British Prime Minister David Cameron's request to the House of Commons to use military force was declined by a 285–272 margin.[125][126] UK government policy subsequently focused on providing humanitarian assistance inside Syria and to refugees in neighboring countries.[127]

Within a month of the attacks, Syria agreed to join the Chemical Weapons Convention and allow all its stockpiles to be destroyed.[128] The destruction began under OPCW supervision on 6 October 2013.[129] On 23 June 2014, the last shipment of Syria's declared chemical weapons was shipped out of the country for destruction.[130] By 18 August 2014, all toxic chemicals were destroyed aboard the US naval vessel MV Cape Ray.[131]

Nine months after the attack, there is evidence that mothers from the affected areas are giving birth to children with defects and as stillborn.[132][133]

Evidence

Witness statements and victim symptoms

Syrian human rights lawyer Razan Zaitouneh, who was present in Eastern Ghouta, stated, "Hours [after the shelling], we started to visit the medical points in Ghouta to where injured were removed, and we couldn't believe our eyes. I haven't seen such death in my whole life. People were lying on the ground in hallways, on roadsides, in hundreds."[134] Several medics working in Ghouta reported the administration of large quantities of atropine, a common antidote for nerve agent toxicity, to treat victims.[135][136]

Doctors Without Borders said the three hospitals it supports in Eastern Ghouta reported receiving roughly 3,600 patients with "neurotoxic symptoms" over less than three hours during the early morning of 21 August. Of those, 355 died.[137] The Local Coordination Committees of Syria claimed that of the 1,338 victims, 1,000 were in Zamalka, of which 600 bodies were transferred to medical points in other towns and 400 remained at a Zamalka medical center.[10] Some of the fatalities were rebel fighters.[138] The deadliness of the attack is believed to have been increased due to civilians reacting to the chemical attack as if it was typical government bombardment. For conventional artillery and rocket attacks, residents usually went to the basements of buildings, where in this case the heavier-than-air sarin sank into these below-ground, poorly ventilated areas.[139] Some of the victims died while sleeping.[81]

Abu Omar of the Free Syrian Army told The Guardian that the rockets involved in the attack were unusual because "you could hear the sound of the rocket in the air but you could not hear any sound of explosion" and no obvious damage to buildings occurred.[140] Human Rights Watch's witnesses reported "symptoms and delivery methods consistent with the use of chemical nerve agents."[18] Activists and local residents contacted by The Guardian said that "the remains of 20 rockets [thought to have been carrying neurotoxic gas] were found in the affected areas. Many [remained] mostly intact, suggesting that they did not detonate on impact and potentially dispersed gas before hitting the ground."[141]

Child frothing at the mouth.
A child in Ghouta froths from the mouth, a medical condition "associated with exposure to nerve agents such as Sarin."[142][143]

Doctors Without Borders also reported seeing a "large number of victims arriving with symptoms including convulsions, excessive saliva, pinpoint pupils, blurred vision and respiratory distress."[144] Symptoms reported by Ghouta residents and doctors to Human Rights Watch included "suffocation, muscle spasms and frothing at the mouth."[18]

Witness statements to The Guardian about symptoms included "people who were sleeping in their homes [who] died in their beds," headaches and nausea, "foam coming out of [victims'] mouths and noses," a "smell something like vinegar and rotten eggs," suffocation, "bodies [that] were turning blue," a "smell like cooking gas" and redness and itching of the eyes.[140] Richard Spencer of The Telegraph summarised witness statements, stating, "The poison ... may have killed hundreds, but it has left twitching, fainting, confused but compelling survivors."[145]

On 22 August, the Center for Documentation of Violations in Syria published numerous testimonies. It summarised doctors' and paramedics' descriptions of the symptoms as "vomiting, foamy salivation, severe agitation, [pinpoint] pupils, redness of the eyes, dyspnea, neurological convulsions, respiratory and heart failure, blood out of the nose and mouth and, in some cases, hallucinations and memory loss".[146]

Analysis of symptoms

Dr. Amesh Adalja, a senior associate for the Center for Biosecurity at the University of Pittsburgh Medical Center, said the reported symptoms are a textbook case of nerve-agent poisoning.[144]

Médecins Sans Frontières Director of Operations Bart Janssens stated that MSF "can neither scientifically confirm the cause of these symptoms nor establish who is responsible for the attack. However, the reported symptoms of the patients, in addition to the epidemiological pattern of the events – characterised by the massive influx of patients in a short period of time, the origin of the patients, and the contamination of medical and first aid workers – strongly indicate mass exposure to a neurotoxic agent."[4]

Gwyn Winfield, Editorial Director at CBRNe World, analysed some videos from the day of the attack and wrote on the magazine's website: "It is difficult to define [an] agent by the signs and symptoms. Clearly respiratory distress, some nerve spasms and a half hearted washdown (involving water and bare hands?!), but it could equally be a riot control agent as a [chemical warfare agent]."[147]

Rockets

A RPU-14 multiple rocket launcher, of a type that may have launched M-14 munitions found by UN inspectors on 26 August at a site in Moadamiyah.[148]

Human Rights Watch reported that two types of rockets were used: in Western Ghouta, a 140mm rocket made in the Soviet Union in 1967 and exported to Syria;[1](p5) and in Eastern Ghouta, a 330mm rocket of unknown origin.[1](p9) HRW also reported that at the time of the attack, Syrian rebels were not known to be in possession of the rockets used.[1](p20)[149]

Seymour Hersh has suggested that the 330mm rockets may have been produced locally, and with a limited range.[150] Blogger Eliot Higgins has looked at the munitions linked to the attack and analysed footage of the putative launchers inside government territory.[151]

According to a study published in January 2014 by Theodore Postol and Richard Lloyd, of the Massachusetts Institute of Technology, the rockets used in the attack had a range of about two kilometers, indicating the munitions could not have been fired from the 'heart' or from the Eastern edge of the Syrian Government Controlled Area shown in the Intelligence Map published by the White House on 30 August 2013.[84][152][153] A response from Higgins and Kaszeta included an observation that the Russian-language news site ANNA News had posted videos showing a Syrian government military operation running from June to August 2013 to clear positions between Jobar and Qaboun, a strip of land about 2 km away from the 21 August impact sites.[154] MIT Professor Theodore Postol contacted Dan Kaszeta and asked him how he came to the conclusion that Hexamine was the "smoking gun" regarding the alleged culpability of the Syrian Government. Åke Sellström told Postol that indeed "the presence of hexamine may mean that this substance was used as scavanger for protons when producing sarin" but that it was a common substance and not conclusive evidence implicating the Syrian government.[155]

Many of the munitions and their fragments had been moved; however, in two cases, the UN could identify the likely launch azimuths.[156] Triangulating rocket trajectories suggests that the origin of the attack may have been within government or rebel-held territory. Consideration of missile ranges influences calculations as to whether rockets originated from the government or rebel-held regions.[150][157]

Communications

Two purported intercepts of communications that appeared to implicate the Syrian government received prominent media coverage. One was a phone call allegedly between Syrian officials which Israel's Unit 8200 was said to have intercepted and passed to the US.[158] The other was a phone call which the German Bundesnachrichtendienst said it had intercepted, between a high-ranking representative of Hezbollah and the Iranian embassy, in which the purported Hezbollah official said that poison gas had been used and that Assad's order to attack with chemical weapons had been a strategic error.[159][160]

On 29 August the Associated Press reported that, according to two U.S. intelligence officials and two other U.S. officials, the U.S. intercept was a conversation between "low-level" Syrian officials with no direct link to the upper echelons of the government or military.[161]

The Bild am Sonntag newspaper subsequently reported that German intelligence indicated that Assad had likely not ordered the attacks.[162] According to Bild, "intelligence interception specialists" relying on communications intercepted by the German vessel Oker said that Syrian military commanders had repeatedly been asking permission to launch chemical attacks for around four months, with permission always being denied from the presidential palace. The sources concluded that 21 August attack had probably not been approved by Bashar al-Assad.[162][163][164]

Video

Murad Abu Bilal, Khaled Naddaf and other Center for Documentation of Violations in Syria and Local Coordination Committees of Syria (LCC) media staff went to Zamalka soon after the attacks to film and obtain other documentary evidence. Almost all the journalists died from inhalation of the neurotoxins, except Murad Abu Bilal, who was the only Zamalka LCC media member to survive.[165][166] The videos were published on YouTube, attracting world-wide media attention.[167]

Experts who have analysed the first video said it shows the strongest evidence yet consistent with the use of a lethal toxic agent. Visible symptoms reportedly included rolling eyes, foaming at the mouth, and tremors. There was at least one image of a child suffering miosis, the pin-point pupil effect associated with the nerve agent Sarin, a powerful neurotoxin reportedly used before in Syria. Ralph Trapp, a former scientist at the Organisation for the Prohibition of Chemical Weapons, said the footage showed what a chemical weapons attack on a civilian area would look like, and went on to note "This is one of the first videos I've seen from Syria where the numbers start to make sense. If you have a gas attack you would expect large numbers of people, children and adults, to be affected, particularly if it's in a built-up area."[167]

Some experts, among them Jean Pascal Zanders, initially stated that evidence that sarin was used, as claimed by pro-rebel sources, was still lacking and highlighted the lack of second-hand contaminations typically associated with use of weapons-grade nerve agents: "I remain sceptical that it was a nerve agent like sarin. I would have expected to see more convulsions," he said. "The other thing that seems inconsistent with sarin is that, given the footage of first responders treating victims without proper protective equipment, you would expect to see considerable secondary casualties from contamination – which does not appear to be evident." However, after Zanders saw footage imminently after the attack, he changed his mind, saying: "The video footage and pictures this time are of a far better quality. You can clearly see the typical signs of asphyxiation, including a pinkish blueish tinge to the skin colour. There is one image of an adult woman where you can see the tell-tale blackish mark around her mouth, all of which suggests death from asphyxiation."[167] Zanders however cautioned that these symptoms covered a range of neurotoxicants, including some available for civilian use as pest control agents, and said that until the UN reported its analysis of samples, "I can't make a judgement.. I have to keep an open mind."[168]

According to a report by The Daily Telegraph, "videos uploaded to YouTube by activists showed rows of motionless bodies and medics attending to patients apparently in the grip of seizures. In one piece of footage, a young boy appeared to be foaming at the mouth while convulsing."[92]

Hamish de Bretton-Gordon, a former commander of British Chemical and Biological counterterrorism forces,[169] told BBC that the images were very similar to previous incidents he had witnessed, although he could not verify the footage.[170]

Allegations of false flag attack

The timing of the attacks prompted some U.S. intelligence officials to speculate they were meant to draw western intervention,[171] a concept dismissed by others.[172][173][174] In December 2013 Seymour Hersh wrote that in the days before and after the attack, sensors notifying U.S. intelligence agencies of Syrian chemical weapons deployment did not activate, and intelligence briefings shown to the U.S. president contained no information about an impending government chemical weapons attack.[150] Publicly, the U.S. government cited classified intercepts of communications it said were between Syrian officials, unavailable to the public, which they state prove Syrian government forces carried out the chemical attack.[11] Criticizing what they called a misleading presentation of intelligence, a former senior U.S. intelligence official quoted by Seymour Hersh said the transcript actually included intercepts from many months prior to the attack, collated to make them appear related to the Ghouta attacks.[150]

In April 2014 Hersh wrote an article proposing the attacks were committed by Al-Qaeda affiliate Al-Nusra Front, whom Hersh writes were supplied with sarin by Turkey.[175][176] Hersh's argument received some support,[177][178] but was dismissed by other commentators.[179][180] The US and Turkish governments denied the accuracy of Hersh's article.[181] On October 20, 2015, Republican People's Party deputy Eren Erdem stated that documents from a Turkish government investigation showed that ISIL and affiliated groups received help from Turkish intelligence to carry out the Ghouta chemical attack.[182][183]

Foreign government assessments

According to public statements, intelligence agencies in Israel,[184] the United Kingdom,[185] the United States,[11] France,[186] Turkey,[187] and Germany[188] concluded that the Syrian government was most likely responsible for the attacks. Western intelligence agencies agreed that video evidence is consistent with the use of a nerve agent, such as sarin. Laboratory tests showed traces of sarin, in blood and hair samples collected from emergency workers who responded to the attacks.[189]

Russia said there was no evidence tying the Syrian government to the attack and that it was likely carried out by an opposition group.[190]

France

On 2 September, the French government published a nine-page intelligence report blaming the Syrian government for the Ghouta attacks.[2][69][191] An unnamed French government official said that the analysis was carried out by the Directorate-General for External Security (DGSE) and Direction du renseignement militaire (DRM) based on satellite and video images, on-the-ground sources, and samples collected from two April attacks.[192] The report said analysis of samples collected from attacks in Saraqeb and Jobar in April 2013 had confirmed the use of sarin.[69]

The Guardian reported that French intelligence had images that showed rocket attacks on opposition neighborhoods from government-controlled areas to the east and west of Damascus. The report said that the government later launched conventional bombing of those neighborhoods in order to destroy evidence of a chemical attack.[193] Based on analysis of 47 videos, the report said at least 281 fatalities occurred. Using other sources and extrapolation a chemical attack model estimated the total number of death at approximately 1,500.[2]

Germany

The Bundesnachrichtendienst said it intercepted a phone call between a Hezbollah official and the Iranian Embassy in which the Hezbollah representative criticised Assad's decision to attack with poison gas, apparently confirming its use by the Syrian government.[159][160] German newspaper Der Spiegel reported on 3 September that BND President Gerhard Schindler told them that based on the agency's evidence, Germany now shared the United Kingdom, United States, and France's view that the attacks were carried out by the Syrian government. However, they also said the attack may have been much more potent than intended, speculating that there may have been an error in mixing the chemical weapons used.[194][195]

Israel

Without going into detail, Israeli Intelligence Minister Yuval Steinitz said on 22 August 2013 that Israel's intelligence assessment was that the Syrian government used chemical weapons in the Damascus area.[184] Defense Minister Moshe Ya'alon said the Syrian government had already used chemical weapons against the rebels on a smaller scale multiple times prior to the Ghouta attacks.[196] Fox News reported that Unit 8200 helped provide intelligence to the United States, Israel's closest international ally, implicating the Syrian government in the attacks.[197] Prime Minister Benjamin Netanyahu said at the General debate of the sixty-eighth session of the United Nations General Assembly that Syrian government used the chemical weapons against its own people.[198]

Russia

Russian officials said that there was no proof that the government of Syria had a hand in the chemical attacks. Russian Foreign Minister Sergei Lavrov described the American, British and French intelligence reports as "unconvincing"[199] and said at a joint news conference with his French counterpart Laurent Fabius after the release of the United Nations report in mid-September that he continued to believe the rebels carried out the attack.[190] Russian President Vladimir Putin said he wanted to see evidence that would make it "obvious" who used chemical weapons in Ghouta.[200]

In a commentary published in The New York Times on 11 September 2013, Putin wrote that "there is every reason to believe [poison gas] was used not by the Syrian Army, but by opposition forces, to provoke intervention by their powerful foreign patrons,".[38] Lavrov said on 18 September that "new evidence" given to Russia by the Syrian government would be forthcoming.[201]

Turkey

The Turkish government-run Anadolu Agency published an unconfirmed report on 30 August 2013, pointing to the Syrian 155th Missile Brigade and the 4th Armored Division as the perpetrators of the two attacks. It said the attack had involved 15 to 20 missiles with chemical warheads at around 02:45 on 21 August, targeting residential areas between Douma and Zamalka in Eastern Ghouta. It claimed that the 155th Missile Brigade had used 9K52 Luna-M missiles, M600 missiles, or both, fired from Kufeyte, while other rockets with a 15- to 70-kilometer range were fired by the 4th Armored Division from Mount Qasioun. The agency did not explain its source.[202]

United Kingdom

A report on the attacks by the United Kingdom's Joint Intelligence Committee (JIC) was published on 29 August 2013 prior to a vote on intervention by the House of Commons of the United Kingdom. The report said at least 350 people were killed and that it was "highly likely" that the attacks had been carried out by the Syrian government, resting in part on the firm view that the Syrian opposition was not capable of carrying out a chemical weapons attack on this scale, and on the JIC view that the Syrian government had used chemical weapons in the Syrian civil war on a small scale on 14 previous occasions.[3] Analysis of the Ghouta attacks themselves was based largely on reviewing video footage and publicly available witness evidence. The report conceded problems with motivation for the attacks, saying there was "no obvious political or military trigger for regime use of CW on an apparently larger scale now."[87][203][204][205] British officials said they believe the Syrian military used chemical weapons, including the nerve agent sarin, on a small scale against the opposition on at least 14 times prior to the Ghouta attacks and described "a clear pattern of regime use" of the nerve agent since 2012.[206]

The report was met with substantial scepticism in the British media, with the Daily Mail explicitly comparing it with the "dodgy dossier" the UK government had published in 2003 prior to the Iraq War.[207] A vote in the House of Commons to approve UK participation in military action against Syria was narrowly rejected, with some MPs arguing that the case for Syrian government culpability was not sufficiently strong to justify approving action.[208][209] Prime Minister David Cameron himself had been forced to concede that "in the end there is no 100 percent certainty about who is responsible."[210][211]

United States

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The map of "Areas of Influence" and "Areas Reportedly affected by the 21 August Chemical Attack" that was published by the White House on 30 August 2013.[11]

A controversial "US government assessment of the Ghouta attacks" was published by the White House on 30 August 2013, with a longer classified version made available to members of Congress. The report blamed the chemical attacks on the Syrian government, saying rockets containing a nerve agent were fired from government-held territory into neighborhoods in the early morning, impacting at least 12 locations. It stated 1,429 people were killed, including at least 426 children. It dismissed the possibility that evidence supporting the US government's conclusion could have been manufactured by the opposition, stating it "does not have the capability" to fabricate videos, eyewitness accounts, and other information. The report also said that the US believed Syrian officials directed the attacks, based on "intercepted communications."[11] A major element, as reported by news media, was an intercepted telephone call between a Syrian Ministry of Defense official and a Syrian 155th Brigade chemical weapons unit commander in which the former demanded answers for the attacks.[212] According to some reports, this phone intercept was provided to the U.S. by Israeli Intelligence Corps Unit 8200.[158]

The U.S. government assessment suggested a motive for the attack, describing it as "a desperate effort to push back rebels from several areas in the capital's densely packed eastern suburbs." The report then states that evidence suggests "the high civilian death toll surprised and panicked senior Syrian officials, who called off the attack and then tried to cover it up."[213] Secretary of State John Kerry later announced that hair, blood, soil, and cloth samples collected from the attack sites had tested positive for sarin or its immediate breakdown products.[214][215]

At least three members of Congress, including at least one member of President Barack Obama's Democratic Party, expressed skepticism about the US intelligence report, calling the evidence circumstantial and thin.[216][217][218][219] Obama's request that Congress authorize military force was not put to a vote of either the House of Representatives or the Senate, and the president ultimately admitted that "I wouldn't say I'm confident" that he could convince Congress to support strikes against Syria.[220]

Democratic Party Representative Alan Grayson offered some details regarding the classified report, which he described as 12 pages long, and criticized both the four-page public summary and the classified report. Grayson said the unclassified summary relied on "intercepted telephone calls, 'social media' postings and the like, but not one of these is actually quoted or attached … (As to whether the classified summary is the same, I couldn't possibly comment, but again, draw your own conclusion.)" Grayson cited as a problematic example the intercepted phone call between a Syrian Ministry of Defense official and the Syrian 155th Brigade, the transcript of which was not provided in the classified report, leaving Grayson unable to judge the accuracy of a report in The Daily Caller that the call's implications had been misrepresented in the report.[218][219]

The AP quoted anonymous US intelligence officials as saying that the evidence presented in the report linking Assad to the attack was "not a slam dunk."[161] Jeffrey Goldberg also reported that James Clapper, the Director of National Intelligence, personally told President Obama that the case for the Syrian government's responsibility was strong but not a "slam dunk."[221] The AP later characterized the evidence released by the administration as circumstantial and said the government had denied its requests for more direct evidence, including satellite imagery and communications intercepts cited in the government assessment.[171]

IPS news analyst Gareth Porter questioned why the report was released by the White House as a "government assessment" as opposed being released by the Office of the Director of National Intelligence as an "intelligence community assessment." Porter quoted former intelligence officials who said the report was "evidently an administration document" and who also suggested evidence was "cherry-picked" to support the conclusion that the Syrian government carried out the attacks.[222]

On 9 October, a US spokesman stated the administration lacks the "irrefutable, beyond-a-reasonable-doubt evidence" some American voters are seeking but that a "common-sense test" implicates Assad.[223] The U.S. publicly stated there was no "reliable" evidence that the opposition had access to chemical weapons, although Seymour Hersh reported that U.S. intelligence agencies privately assessed some rebel factions to be capable of sarin production.[150]

Legal status

Attack

At the time of the attack, Syria was not a member of the Chemical Weapons Convention. However, Human Rights Watch argues that the Ghouta chemical attack was illegal under a different international agreement:

Syria is a party to the 1925 Geneva Gas protocol, which bans the use in war of asphyxiating, poisonous or other gases, and of all analogous liquids, materials or devices. The use of chemical weapons is also prohibited as a matter of customary international humanitarian law, or the laws of war. The prohibition on the use of chemical weapons applies to all armed conflicts, including so-called non-international armed conflicts such as the current fighting in Syria. The International Criminal Tribunal for the former Yugoslavia, in the Tadic case, stated "there undisputedly emerged a general consensus in the international community on the principle that the use of [chemical] weapons is also prohibited in internal armed conflicts."[1](p21)

International Criminal Court referral

Human Rights Watch stated that the UN Security Council should refer the Syria situation to the International Criminal Court (ICC) "to ensure accountability for all war crimes and crimes against humanity."[136] Amnesty International also said that the Syria situation should be referred to the ICC because "the best way for the United States to signal its abhorrence for war crimes and crimes against humanity and to promote justice in Syria, would be to reaffirm its support for the Rome Statute establishing the International Criminal Court."[224] However, as the amendment to the Rome Statute of the International Criminal Court explicitly making it a war crime to use chemical weapons in an internal conflict has not been ratified by any major state nor Syria, the legal situation is complex and reliant on the attack being a part of a wider war crime.[225]

Reactions

Domestic

Information Minister Omran al-Zoubi was quoted by the official state news agency, Syrian Arab News Agency (SANA), as saying that the government did not and would not use such weapons, if in fact they even existed. Al-Zoubi said, "everything that has been said is absurd, primitive, illogical and fabricated. What we say is what we mean: there is no use of such things (chemical weapons) at all, at least not by the Syrian army or the Syrian state, and it's easy to prove and it is not that complicated."[226] SANA called the reports of chemical attacks as "untrue and designed to derail the ongoing UN inquiry." A Syrian military official appeared on state television denouncing the reports as "a desperate opposition attempt to make up for rebel defeats on the ground."[80] Deputy Foreign Minister Faisal Mekdad declared it a tactic by the rebels to turn around the civil war which he said "they were losing" and that, though the government had admitted to having stocks of chemical weapons, stated they would never be used "inside Syria".[227] Democratic Union Party leader Salih Muslim said he doubted that the Syrian government carried out the chemical attack.[228]

The National Coalition called the attack a "coup de grace that kills all hopes for a political solution in Syria."[229] In a statement on Facebook, the Coventry-based Syrian Observatory for Human Rights, an anti-government activist network, blamed the attack on the Syrian military and said of the incident that "we assure the world that silence and inaction in the face of such gross and large-scale war crimes, committed in this instance by the Syrian regime, will only embolden the criminals to continue in this path. The international community is thus complicit in these crimes because of its [polarisation], silence and inability to work on a settlement that would lead to the end of the daily bloodshed in Syria."[230]

International

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The international community condemned the attacks. United States President Barack Obama said the US military should strike targets in Syria to retaliate for the government's purported use of chemical weapons, a proposal publicly supported by French President François Hollande, but condemned by Russia and Iran.[231][232] The Arab League stated it would support military action against Syria in the event of UN support, though member states Algeria, Egypt, Iraq, Lebanon, and Tunisia opposed it.[233]

At the end of August, the House of Commons of the United Kingdom voted against military intervention in Syria.[234] In early September, the United States Congress began debating a proposed authorisation to use military force, although votes on the resolution were indefinitely postponed amid opposition from many legislators[235] and tentative agreement between Obama and Russian President Vladimir Putin on an alternative proposal, under which Syria would declare and surrender its chemical weapons to be destroyed under international supervision.[236]

In contrast to the positions of their governments, polls in early September indicated that most people in the US, UK, Germany and France opposed military intervention in Syria.[237][238][239][240][241] One poll indicated that 50% of Americans could support military intervention with cruise missiles only, "meant to destroy military units and infrastructure that have been used to carry out chemical attacks."[242] In a survey of American military personnel, around 75% said they opposed air strikes on Syria, with 80% saying an attack would not be "in the U.S. national interest".[243] Meanwhile, a Russian poll suggested that most Russians supported neither side in the conflict, with less than 10% saying they supported Assad.[244]

See also

Notes

  1. In their report Attacks on Ghouta, Human Rights Watch states: "Witness statements and information including GPS locations of rockets found in the area provided by local activists, as well as satellite imagery locations that match the location in the videos, have allowed Human Rights Watch to confirm at least four strike sites in Zamalka where at least eight 330mm rockets struck on August 21. This is unlikely to be a complete account of the number of rockets used in the attack."[1](p7) A map labeled "Map of the 330mm chemical rocket impact locations in Zamalka neighborhood" shows 12 sites.[1](pVI) The dimensions of the impact area was found by comparing the Human Rights Watch map to a scaled satellite image.

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 Lua error in package.lua at line 80: module 'strict' not found. Web version
  2. 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 Lua error in package.lua at line 80: module 'strict' not found.
  4. 4.0 4.1 4.2 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. 9.0 9.1 Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 11.2 11.3 11.4 Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 17.3 17.4 17.5 17.6 17.7 17.8 Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 Lua error in package.lua at line 80: module 'strict' not found.
  19. 19.0 19.1 19.2 Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. 21.0 21.1 21.2 Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found.
  24. 24.0 24.1 24.2 Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.
  30. 30.0 30.1 30.2 Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. 38.0 38.1 Lua error in package.lua at line 80: module 'strict' not found.
  39. 39.0 39.1 Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. 50.0 50.1 Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. 56.0 56.1 56.2 56.3 56.4 56.5 Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. 60.0 60.1 Lua error in package.lua at line 80: module 'strict' not found.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. Lua error in package.lua at line 80: module 'strict' not found.
  69. 69.0 69.1 69.2 69.3 69.4 Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found. Final version dated 18 July 2013 found on this page. A/HRC/23/58
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. 80.0 80.1 80.2 Lua error in package.lua at line 80: module 'strict' not found.
  81. 81.0 81.1 81.2 Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. 84.0 84.1 Lua error in package.lua at line 80: module 'strict' not found. HTML version
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. Lua error in package.lua at line 80: module 'strict' not found.
  87. 87.0 87.1 Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Lua error in package.lua at line 80: module 'strict' not found.
  91. 91.0 91.1 Lua error in package.lua at line 80: module 'strict' not found.
  92. 92.0 92.1 Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found. Original Russian version
  98. 98.0 98.1 Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. 102.0 102.1 Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. 104.0 104.1 Lua error in package.lua at line 80: module 'strict' not found.
  105. BBC, 26 August 2013, Syria crisis: UN inspectors' convoy hit by sniper fire
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. 107.0 107.1 107.2 Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. 111.0 111.1 111.2 Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. Foroutan's work was reviewed in Neurology in 2004 by a US Army chemical weapons expert, and described as "the only firsthand clinical descriptions of battlefield nerve agent casualties in the world literature". – Sharmine Narwani and Radwan Mortada, mideastshuffle.com, 1 October 2010, CW Expert Opinion on the UN Report on Syria
  122. http://edc.sbmu.ac.ir/uploads/Comments-un-report-on-syria-1.pdf
  123. 123.0 123.1 Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. Lua error in package.lua at line 80: module 'strict' not found.
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. 136.0 136.1 Lua error in package.lua at line 80: module 'strict' not found.
  137. Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. 140.0 140.1 Lua error in package.lua at line 80: module 'strict' not found.
  141. Lua error in package.lua at line 80: module 'strict' not found.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. 144.0 144.1 Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Joe Pappalardo, Popular Mechanics, 17 September 2013, The Story of Syria's Chemical Artillery
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. 150.0 150.1 150.2 150.3 150.4 Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. 158.0 158.1 Lua error in package.lua at line 80: module 'strict' not found.
  159. 159.0 159.1 Lua error in package.lua at line 80: module 'strict' not found.
  160. 160.0 160.1 Lua error in package.lua at line 80: module 'strict' not found.
  161. 161.0 161.1 Lua error in package.lua at line 80: module 'strict' not found.
  162. 162.0 162.1 Lua error in package.lua at line 80: module 'strict' not found.
  163. Martin S. Lambeck, Kayhan Özgenc and Burkhard Uhlenbroich, Bild am Sonntag, 8 September 2013, Assad-Kommandeure wollten seit Monaten Giftgas einsetzen
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. 167.0 167.1 167.2 Lua error in package.lua at line 80: module 'strict' not found.
  168. Huffington Post, 30 August 2013, Syria: Chemical Weapons Expert Jean Pascal Zanders Says Gas Might Not Be Sarin, Urges Caution
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. 171.0 171.1 Lua error in package.lua at line 80: module 'strict' not found.
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.
  175. Lua error in package.lua at line 80: module 'strict' not found.
  176. Lua error in package.lua at line 80: module 'strict' not found.
  177. Lua error in package.lua at line 80: module 'strict' not found.
  178. Lua error in package.lua at line 80: module 'strict' not found.
  179. Lua error in package.lua at line 80: module 'strict' not found.
  180. Lua error in package.lua at line 80: module 'strict' not found.
  181. Lua error in package.lua at line 80: module 'strict' not found.
  182. Lua error in package.lua at line 80: module 'strict' not found.
  183. Lua error in package.lua at line 80: module 'strict' not found.
  184. 184.0 184.1 Lua error in package.lua at line 80: module 'strict' not found.
  185. Lua error in package.lua at line 80: module 'strict' not found.
  186. Lua error in package.lua at line 80: module 'strict' not found.
  187. Lua error in package.lua at line 80: module 'strict' not found.
  188. Lua error in package.lua at line 80: module 'strict' not found.
  189. Lua error in package.lua at line 80: module 'strict' not found.
  190. 190.0 190.1 Lua error in package.lua at line 80: module 'strict' not found.
  191. Lua error in package.lua at line 80: module 'strict' not found.
  192. Lua error in package.lua at line 80: module 'strict' not found.
  193. Lua error in package.lua at line 80: module 'strict' not found.
  194. Matthias Gebauer, Der Spiegel, 3 September 2013, Gas Attack: Germany Offers Clue in Search for Truth in Syria
  195. Lua error in package.lua at line 80: module 'strict' not found.
  196. Lua error in package.lua at line 80: module 'strict' not found.
  197. Lua error in package.lua at line 80: module 'strict' not found.
  198. Lua error in package.lua at line 80: module 'strict' not found.
  199. Lua error in package.lua at line 80: module 'strict' not found.
  200. Lua error in package.lua at line 80: module 'strict' not found.
  201. Lua error in package.lua at line 80: module 'strict' not found.
  202. Lua error in package.lua at line 80: module 'strict' not found.
  203. Lua error in package.lua at line 80: module 'strict' not found.
  204. Lua error in package.lua at line 80: module 'strict' not found.
  205. Lua error in package.lua at line 80: module 'strict' not found.
  206. Lua error in package.lua at line 80: module 'strict' not found.
  207. Daily Mail, 30 August 2013, Intelligence report backing Cameron's case for Syria strikes has echoes of 'dodgy dossiers' from Blair era
  208. The Guardian, 30 August 2013, Blow to Cameron's authority as MPs rule out British assault on Syria
  209. Lua error in package.lua at line 80: module 'strict' not found.
  210. Associated Press, 29 August 2013, UK Prime Minister Cameron loses Syria war vote,
  211. Lua error in package.lua at line 80: module 'strict' not found.
  212. Lua error in package.lua at line 80: module 'strict' not found.
  213. Lua error in package.lua at line 80: module 'strict' not found.
  214. Lua error in package.lua at line 80: module 'strict' not found.
  215. Lua error in package.lua at line 80: module 'strict' not found.
  216. Lua error in package.lua at line 80: module 'strict' not found.
  217. Lua error in package.lua at line 80: module 'strict' not found.
  218. 218.0 218.1 Lua error in package.lua at line 80: module 'strict' not found.
  219. 219.0 219.1 Lua error in package.lua at line 80: module 'strict' not found.
  220. Lua error in package.lua at line 80: module 'strict' not found.
  221. Lua error in package.lua at line 80: module 'strict' not found.
  222. Lua error in package.lua at line 80: module 'strict' not found.
  223. Lua error in package.lua at line 80: module 'strict' not found.
  224. Lua error in package.lua at line 80: module 'strict' not found.
  225. Lua error in package.lua at line 80: module 'strict' not found.
  226. Lua error in package.lua at line 80: module 'strict' not found.
  227. Lua error in package.lua at line 80: module 'strict' not found.
  228. Lua error in package.lua at line 80: module 'strict' not found.
  229. Lua error in package.lua at line 80: module 'strict' not found.
  230. Lua error in package.lua at line 80: module 'strict' not found.
  231. Lua error in package.lua at line 80: module 'strict' not found.
  232. Lua error in package.lua at line 80: module 'strict' not found.
  233. Lua error in package.lua at line 80: module 'strict' not found.
  234. Lua error in package.lua at line 80: module 'strict' not found.
  235. Lua error in package.lua at line 80: module 'strict' not found.
  236. Lua error in package.lua at line 80: module 'strict' not found.
  237. Lua error in package.lua at line 80: module 'strict' not found.
  238. Lua error in package.lua at line 80: module 'strict' not found.
  239. Lua error in package.lua at line 80: module 'strict' not found.
  240. Lua error in package.lua at line 80: module 'strict' not found.
  241. Lua error in package.lua at line 80: module 'strict' not found.
  242. Lua error in package.lua at line 80: module 'strict' not found.
  243. Lua error in package.lua at line 80: module 'strict' not found.
  244. Lua error in package.lua at line 80: module 'strict' not found.

External links

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.