Ukraine International Airlines Flight 752

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
Ukraine International Airlines Flight 752
File:UR-PSR (B738) at Ben Gurion Airport.jpg
UR-PSR, the aircraft involved in the incident, at Ben-Gurion Airport in October 2019
Shootdown summary
Date 8 January 2020 (2020-01-08)
Summary Struck by two surface-to-air missiles (Tor M-1) fired by the Islamic Revolutionary Guard Corps[1]
Site Shahriar County, Iran[2]
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 167
Crew 9
Fatalities 176[3]
Survivors 0
Aircraft type Boeing 737-8KV
Operator Ukraine International Airlines
Registration UR-PSR
Flight origin Imam Khomeini International Airport (Tehran, Iran)
Destination Boryspil International Airport (Kyiv, Ukraine)

Ukraine International Airlines Flight 752 (PS752/AUI752) was a scheduled international civilian passenger flight from Tehran to Kyiv, operated by Ukraine International Airlines. On 8 January 2020, the Boeing 737-800 flying the route was shot down by the Islamic Revolutionary Guard Corps (IRGC) shortly after takeoff,[4][5][6] killing all 176 passengers and crew aboard.

Missiles were fired at the aircraft by the IRGC amidst heightened tensions between Iran and the United States. The incident occurred five days after the United States carried out the assassination of Qasem Soleimani and some hours after Iran retaliated with Operation Martyr Soleimani, in which the IRGC fired dozens of ballistic missiles on American-led coalition forces; both the assassination and the missile strikes took place in Iraq.[7]

Iranian authorities initially denied having any responsibility for the aircraft's destruction, but investigations by various intelligence agencies from the Western world as well as by the Iranian public later revealed that it had been struck by two surface-to-air missiles. On 11 January 2020, the Iranian government admitted that the IRGC had targeted Flight 752 after mistakenly identifying it as an American cruise missile.[8] The announcement triggered another wave of Iranian anti-government protests (part of the larger 2019–2020 Iranian protests), with many Iranians calling for the removal or overthrowal of Ali Khamenei.[9]

Background

The disaster occurred amid a heightened political crisis in the Persian Gulf, four hours after the Iranian military launched retaliatory ballistic missile strikes towards U.S. military airbases in Iraq in response to the assassination of Major General Qasem Soleimani by the U.S.[10] The U.S. previously threatened Iran and was initially expected to retaliate for the Iranian attack.[11][12] Iran was on the highest state of defensive alert and, according to Commander of the Aerospace Force of the IRGC Amir Ali Hajizadeh, was "totally prepared for a full-fledged war".[7]

In response to the Iranian missile attack, the U.S. Federal Aviation Administration (FAA), in a notice to airmen (NOTAM), banned all American civil aircraft from flying over Iran, Iraq, the Gulf of Oman and the Persian Gulf.[13][14] Although the FAA NOTAMs are not binding on non-U.S. airlines, many airlines take them into consideration when making safety decisions, especially after the downing of Malaysia Airlines Flight 17 in 2014.[15][16][17] Several airlines, including Austrian Airlines,[18] Singapore Airlines,[19] KLM,[20] Air France,[21] Air India,[21] SriLankan Airlines,[22] Qantas[15] and Vietnam Airlines[23] began to reroute their flights. Other airlines, such as Lufthansa, Emirates, Flydubai, and Turkish Airlines cancelled some flights to airports in Iran and Iraq, making further operational changes as necessary.[17][24][25][26]

Aircraft

The aircraft was a Boeing 737-8KV,[lower-alpha 1] serial number 38124, registration UR-PSR. It was three-and-a-half years old when it was shot down, having first flown on 21 June 2016.[2] It was delivered to UIA on 19 July 2016, the first 737 Next Generation aircraft purchased by the airline.[27] The aircraft was well maintained, with the airline saying it had been inspected just two days before the crash.[28]

Flight and crash

Crash site is located in Iran
Crash site
Crash site
Approximate location of the crash site
File:Ukraine International Airlines Flight 752 flight path.svg
Ukraine International Airlines Flight 752 flight path <maplink text="Detailed map">{"type":"ExternalData","service":"page","title":"Ukraine International Airlines Flight 752 flight path.map","properties":{"stroke-width":6,"title":"Ukraine International Airlines Flight 752","stroke":"#ff0000"}}</maplink>
File:Ukraine International Airlines Flight 752 speed and altitude.svg
Speed and altitude of Ukraine International Airlines Flight 752

The flight was operated by Ukraine International Airlines, flag carrier and largest airline of Ukraine, on a scheduled flight from Iranian capital Tehran's Imam Khomeini International Airport to Boryspil International Airport in the Ukrainian capital, Kyiv. The aircraft was carrying 176 people, including nine crew members and fifteen children.[29]

Flight 752 took off from Runway 29R an hour behind schedule, at 06:12:08 local time (UTC+3:30), and was expected to land in Kyiv at 08:00 local time (UTC+2:00).[30][3] Between 06:14:17 and 06:14:45 the airplane turned from the take-off heading of 289° to heading 313°, following its regular route.[31][32]

According to the data, the last recorded altitude of the aircraft was 2,416 metres (7,925 ft) above mean sea level with a ground speed of 275 knots (509 km/h; 316 mph).[33] The airport is 1,007 metres (3,305 ft) above mean sea level and the terrain around Parand and the crash site lies approximately 125 metres (410 ft) higher at 1,134 metres (3,720 ft). The flight was climbing at just under 15 metres per second (3,000 ft/min) when the flight data recorder abruptly ended over the open ground near the northern end of Enqelab Eslami Boulevard in Parand.[31]

Analysis of several videos by The New York Times showed that the aircraft was hit almost immediately by the first of two short-range missiles (which knocked out its transponder) launched thirty seconds apart by the IRGC, and with the aircraft having maintained its track, by the second missile 23 seconds later, after which it veered right and could be seen on fire before disappearing from view.[32] Ukrainian investigators believed the pilots were killed instantly by shrapnel from the missile which exploded near the cockpit.[34] However, an analysis of the cockpit voice recorder indicated that for at least 19 seconds after the first missile strike, all three cockpit crew members continued to attempt to fly the aircraft, and there was no indication of injury or adverse health effects during that time.[35]

The final ADS-B data received was at 06:14:57, less than three minutes after departure,[31] after which the aircraft's track was recorded by primary radar only.[36]:9 Its last seconds were captured in several video recordings.[37][38][39] The aircraft crashed on a park and fields on the edge of the village of Khalajabad, 15 kilometres (9.3 mi; 8.1 nmi) north-west of the airport,[40] and about 16 kilometres (10 mi) ENE of the last missile strike, about six minutes after takeoff.[32][36]:9 There were no casualties on the ground.

Shortly after the crash, emergency responders arrived in 22 ambulances, four bus ambulances, and a helicopter, but intense fires prevented a rescue attempt. The wreckage was strewn over a wide area, with no survivors found at the crash site.[41] The aircraft was completely destroyed on impact.[42]

All 176 passengers and crew were killed.[43] It is the deadliest flight in terms of fatalities involving the Boeing 737 Next Generation fleet, and the second deadliest of the entire Boeing 737 family behind Lion Air Flight 610.[44]

Passengers and crew

People on board, based on Ukrainian official list[45][lower-alpha 2]
Nation Number
Iran[lower-alpha 3] 82
Canada[lower-alpha 4] 63
Ukraine[lower-alpha 5] 11
Sweden[lower-alpha 6] 10
Afghanistan[lower-alpha 7] 7
United Kingdom[lower-alpha 8] 3
Total 176
File:Ukraine International Airlines Flight 752 (9).jpg
Recovery operations, victims of Flight 752

There were 167 passengers and nine crew members on the flight.[51] According to Iranian officials, 146 passengers used Iranian passports to leave Iran, ten used Afghan passports, five used Canadian ones, four Swedish ones, and two used Ukrainian passports.[52] There is some disagreement with other sources over this accounting of nationalities, possibly due to some passengers being nationals of more than a single country.

According to Ukrainian foreign minister Vadym Prystaiko and a flight manifest released by UIA,[53] out of the 167 passengers, 82 were confirmed to be Iranian citizens, 63 were Canadian, three were British, four were Afghan, ten were Swedish, and three were German. Eleven Ukrainians were also on board, nine of them crew members.[43][47] The German Foreign Ministry denied any Germans were aboard;[54] the three people in question were Afghan nationals who lived in Germany as asylum seekers.[49] According to Iranian nationality law, the Iranian government considers dual citizens to be solely Iranian citizens.[55]

Of the 167 passengers, 138 were travelling to Canada via Ukraine.[56][57][58] Many of the Iranian Canadians were affiliated with Canadian universities, as students or academics who had travelled to Iran during the winter break. The crash was the largest loss of Canadian lives in aviation since the 1985 bombing of Air India Flight 182.[59] On January 15, 2020, Canadian Transport Minister Marc Garneau said 57 Canadians died in the crash.[60]

In addition to six flight attendants, the crew consisted of Captain Volodymyr Gaponenko (11,600 hours on Boeing 737 aircraft, including 5,500 hours as captain), instructor pilot Oleksiy Naumkin (12,000 hours on Boeing 737s, including 6,600 as captain), and first officer Serhiy Khomenko (7,600 hours on Boeing 737).[61]

Investigation

The Civil Aviation Organization of Iran (CAOI) reported shortly after the incident that a team of investigators had been sent to the crash site.[51] On the same day, the Ukrainian government said it would send experts to Tehran to assist with the investigation. President Volodymyr Zelensky instructed the Ukrainian General Prosecutor to open a criminal investigation into the crash.[62] The Ukrainian government sent 45 investigators to assist with the inquiry into the shootdown of the airliner.[63]

File:Ukraine Air Force Il-76 with a group of SAR and experts go to Iran.jpg
A Ukrainian Air Force Ilyushin Il-76 prepares to depart for Iran from the Boryspil International Airport with specialists from the National Bureau of Investigation of Civil Aviation and Incidents with the Civil Aviation Service, State Aviation Service, Ukraine International Airlines and from the General Inspectorate of the Ministry of Defense of Ukraine.

Under standard International Civil Aviation Organization (ICAO) rules, according to Annex 13 of the Chicago Convention, the United States National Transportation Safety Board (NTSB) would participate in the investigation, as they represented the state of the manufacturer of the aircraft. France's Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) would participate as representatives of the state of manufacture of the aircraft's engines (a U.S.–France joint venture) and Ukraine's Ministry of Infrastructure would participate as representatives of the state in which the aircraft was registered. Given that there were tensions between these nations and Iran as part of the 2019–2021 Persian Gulf crisis, it was not known how these investigative organizations would be involved, although it was reported that Iran had said American, French and Ukrainian authorities would be involved.[64]

The head of the commission for accidents in the CAOI said they received no emergency message from the aircraft before the crash.[65] It was reported that the aircraft's black boxes (the cockpit voice recorder (CVR) and flight data recorder (FDR)) had been recovered, but the CAOI said it was not clear to which country the recorders would be sent so the data could be analyzed.[66] The association said it would not hand over the black boxes to Boeing or to U.S. authorities.[67] On 9 January, the black boxes were reported, by Iranian investigators, to have been damaged and that some parts of their memory may have been lost.[68] Mary Schiavo, a former U.S. Department of Transportation inspector general, said no automated distress messages had been sent from the aircraft or by its crew.[69]

On 9 January, the Swedish Accident Investigation Authority and Transportation Safety Board of Canada (TSB) were officially invited by the investigation team to participate in the probe on the crash.[18] The NTSB,[70][71][72] Ukraine, and Boeing were also invited to participate in the investigation.[18] Due to American economic sanctions placed on Iran, U.S. investigators would need a special licence from the Treasury and the State Departments to travel there.[73][74][75]

On 9 January, media reports showed bulldozers being used to clear the crash site. Some aircraft investigation experts expressed concerns about disturbing and damaging the crash site before a thorough investigation could be conducted.[76] Iran denied bulldozing the evidence.[77] On 10 January, the Iranian government granted Ukrainian investigators permission to investigate the flight recorders and Ukrainian investigators visited the crash site,[78][79] with plans to download the recorders in Tehran.[80] On 14 January, the head of the TSB, Kathy Fox, said there were signs that Iran would allow the TSB to participate in the downloading and analysis of data from the airplane's flight data recorder and cockpit voice recorder.[81] On 23 January, the TSB announced that they had been invited by Iran to help with the flight recorders.[82]

On 2 February, Ukrainian public TV aired a leaked recording of the information exchange between the Iranian pilot of an Aseman Airlines flight and an Iranian air traffic controller. The pilot stated in Persian that he saw "a series of flares like that of a missile" and later an explosion.[83][84] Following the leak, Zelensky said the new evidence proved Iran was well aware from the very first moments that the Ukraine passenger airplane was brought down by a missile.[83] The following day Iran ceased co-operation with Ukraine in its investigation into the disaster.[85] Iran resumed co-operation on 15 February.[86] In the final report about the crash, Iranian authorities gave a more complete transcript of the communication.[84]

Flight data recorder and cockpit voice recorder

On 20 January, Iran asked for assistance from France and the United States to recover the data from the flight data recorder and cockpit voice recorder.[87] On 5 February, Canada urged Iran to send the recorders to France.[88] Iran denied the request.[89]

On 12 March, Iran agreed to hand over the recorders to Ukraine.[90] However, the COVID-19 pandemic delayed this action.[91][92][93] During this time, impatience began to mount from Ukraine, Canada, and ICAO.[94]

On 11 June, Iran announced that the flight recorders would be sent directly to the Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) in France.[95] Canadian officials urged Iran to complete this action "as soon as possible", citing the previous delays in handing over the recorders.[96] This statement was further reinforced 11 days later, when Iranian foreign minister Mohammad Javad Zarif commented on this intention during a phone call with Canadian foreign minister François-Philippe Champagne.[97]

On 20 July, the examination of the recorders started in Paris.[98]

Cause of the crash

File:Ukraine International Airlines Flight 752 (10).jpg
Wreckage of Flight 752, with part of an engine in the foreground, showing nozzle guide vanes

On 8 January, Iran's Road and Transportation Ministry released a statement that the aircraft burst into flames after a fire started in one of its engines, causing the pilot to lose control and crash into the ground.[99][62] The airline opined that pilot error was impossible to be cited as the cause of the crash as the pilots had exclusively been trained for the Tehran flights for years, noting that Tehran Airport was "not a simple airport".[100]

Iranian and Ukrainian government sources initially blamed mechanical issues aboard the aircraft for its crash.[45][101][102] The Ukrainian government later retracted its statement and said anything was possible, refusing to rule out that the aircraft was hit by a missile.[103] Zelensky said there should not be any speculation about the cause of the crash.[62]

On 9 January, U.S. intelligence and defence officials said they believed the aircraft had been shot down by an Iranian Tor missile (NATO reporting name SA-15 "Gauntlet"),[104] based on evidence from reconnaissance satellite imagery and radar data.[105][18] Ukrainian authorities said a shootdown was one of the "main working theories", while Iranian authorities denied this, stating that allegations of a missile hit were "psychological warfare".[106][107][108][109] British defence officials agreed with the American assessment of a shootdown.[108] Prime Minister of Canada Justin Trudeau said evidence from multiple sources, including Canadian intelligence, suggested the aircraft was shot down by an Iranian missile.[110] He added that "this may well have been unintentional".[105] Iranian media described it as "an American lie", "a wrongful scenario by CIA and the Pentagon", and "an attempt to prevent Boeing stock from a free fall".[111][112]

On 11 January, the Armed Forces of the Islamic Republic of Iran admitted they had shot down the airplane, having erroneously identified it as a hostile target.[113] According to an early IRGC statement, when the airplane seemed to head toward a "sensitive military centre" of the IRGC, controllers mistook it for a "hostile target" and shot it down.[114] Iran's Civil Aviation Organization disputed this timeline, arguing that the airplane was on the correct course all the time and there was no proven flight deviation.[115] The CAOI's viewpoint was also supported by a Radio Canada International article that used public ADS-B flight tracking data.[116][117] Iranian Brigadier general Amir Ali Hajizadeh of the IRGC Aerospace Defense said a missile operator in Bidganeh had acted independently, mistook the airplane for a U.S. cruise missile and shot it down. Hajizadeh also said the airplane was on-track and "made no mistake".[7][8]

Western experts had previously noted that Flight 752 was flying near several sensitive Iranian ballistic missile facilities, including the Shahid Modarres missile base at Bidganeh near Malard, which the Iranians could have believed would be targets of retaliation for their attack a few hours earlier.[118][119]

The flight had been delayed by more than an hour because the captain had decided to offload some luggage as the aircraft was over its certified takeoff weight.[120]

On 11 July 2020, the CAOI reported that Iran now blamed the missile strike that downed PS752 on "bad communication" and "poor alignment". According to the Iranians, the missile battery "had been relocated and was not properly reoriented" and the guilty parties did not include the higher-ranking chain of command officers.[121][122] On 20 July, Canadian foreign minister François-Philippe Champagne rejected the finding by the CAOI that "human error" caused the launch of the missiles which destroyed the aircraft: "It cannot just be the result of a human error. There is no circumstance under (which) a civilian aircraft can be downed just by the result of human error in this day and age... All the facts and circumstances point to more than just a human error, so certainly we will continue to pursue vigorously the investigation."[98]

Analyses based on social media

On 9 January, the Instagram account Rich Kids of Tehran published a video captioned: 'The actual footage from the moment the #Ukrainian flight was shot down by a Russian-made Tor-M1 missile just moments after takeoff from #Tehran's Airport '.[123] The video was published at the same time the Iranian authorities were claiming technical problems for the crash.[124][125] Qassem Biniaz, a spokesman for Iran's Road and Transportation Ministry, said the pilot "lost control of the plane" after a fire broke out in one of its engines, denying the Ukrainian plane was hit by a missile.[126][127][128]

On 9 January, a video was posted on a public Telegram channel showing what was, according to Bellingcat, apparently a mid-air explosion. The New York Times contacted the person who filmed the video and confirmed its authenticity. An investigation team from Bellingcat carried out an analysis of this video and geolocated it to a residential area in Parand, a suburb west of the airport.[129][130] Bellingcat also examined photos from an unknown source and said these images of a missile nose cone had yet to be verified, despite claims from several sources.[131] The Tor missile's warhead is located in its midsection, meaning its nose may not be destroyed in an explosion.[131] Similar photographs of fragments have been taken in eastern Ukraine, but none have been found to be the same as those attributed to the recent incident.[131]

USA Today reported that the firm IHS Markit reviewed photographs showing the guidance section of a missile and "assesses them to be credible".[132][133] Aviation monitoring group Opsgroup said: "We would recommend the starting assumption to be that this was a shootdown event, similar to MH17—until there is clear evidence to the contrary" asserting that photographs "show obvious projectile holes in the fuselage and a wing section".[134]

Subsequent developments

On 9 January, President Trump said the airplane "was flying in a pretty rough neighbourhood, and somebody could have made a mistake."[135] He said the U.S. had no involvement in the incident and that he did not believe a mechanical issue had anything to do with the crash.[135] U.S. intelligence sources informed U.S. media outlets they were "confident that Iran painted the Ukrainian airliner with radar and fired two surface to air missiles that brought down the aircraft."[136][137]

Also on 9 January, at a news conference in Ottawa, Canadian Prime Minister Justin Trudeau said the airliner was likely brought down by an Iranian missile, citing intelligence from Canadian and other sources, and said the incident "may well have been unintentional".[138]

On 10 January, during an interview with Sky News, Iran's ambassador to the United Kingdom, Hamid Baeidinejad, rejected video footage obtained by American media that showed bulldozers clearing the crash site as "absurd".[139] Baeidinejad further denied that an Iranian missile had brought down the airplane, and said that "[p]lane accidents are a very technical issue, I cannot judge, you cannot judge, reporters on the ground cannot judge. Nobody can judge. A foreign minister or a prime minister cannot judge on this issue."[140]

On 11 January, Iran admitted it had shot down the Ukrainian jet by "accident", the result of human error. General Amir Ali Hajizadeh, the head of the IRGC's Aerospace Force, said his unit accepts "full responsibility" for the shootdown. In an address broadcast by state television, he said that when he learned about the downing of the airplane, "I wished I was dead." Hajizadeh said that, with his forces on high alert, an officer mistook it for a hostile missile and made a "bad decision".[141][7][142]

On 14 January, the Rich Kids of Tehran Instagram account published a new video, showing two missiles hitting the aircraft.[143] The security camera footage, verified by The New York Times, shows two missiles, fired 30 seconds apart.[144] On 20 January, the Civil Aviation Organization of Iran also admitted that the country's IRGC had fired two Russian-made Tor-M1 missiles at the aircraft.[145][146]

On 8 January 2021, the first anniversary of the shootdown, Ukraine and several other countries made a joint statement calling on Iran for a thorough investigation and reiterated for them to prosecute anyone involved, and provide full compensation.[147][148][149]

Final report

On 17 March 2021, CAOI released the final report on the crash, which states the following:[84]

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

The air defense's launching two surface-to-air missiles at the flight PS752, UR-PSR aircraft, the detonation of the first missile warhead in proximity of the aircraft caused damage to the aircraft systems, and the intensification of damage led the aircraft to crash into the ground and explode instantly.

A contributing factor was: <templatestyles src="Template:Blockquote/styles.css" />

The mitigating measures and defense layers in risk management proved to be ineffective due to the occurrence of an unanticipated error in threat identifications, and ultimately failed to protect the flight safety against the threats caused by the alertness of defense forces.

Ukraine's Vice Prime Minister Dmytro Kuleba rejected the findings and criticized the report as "a collection of manipulations, the goal of which is not to establish the truth, but to whitewash the Islamic Republic of Iran."[150] The Transportation Safety Board of Canada also criticized the report, saying that it did not provide an exact reason to why the IRGC fired its missiles at Flight 752.[151]

Legal

On 10 August 2020, IRGC officer Gholamreza Soleimani, commander of Basij forces, said that Iran would not compensate Ukraine International Airlines for the shootdown because the "plane is insured by European companies in Ukraine and not by Iranian companies". The countries were expected to negotiate on compensation again in October.[152]

In February 2020, a proposed class action claim was filed in the Ontario Superior Court of Justice against Iran, Iranian Supreme Leader Ali Khamenei, and various branches of the Iranian military, among others.[153][154] Lawyers of the families of Canadian victims were seeking compensation of at least CA$1.1 billion.[155][156]

In April 2020, families of the victims formed The Association of Families of Flight PS752 Victims in Toronto, Ontario, Canada, to follow the case through legal avenue. The association's president and spokesman, Hamed Esmaeilion, said the association's aim is, "to bring the perpetrators of the crime to justice, including those who ordered it".[157][158] In July 2020, Esmaeilion was outraged that the ICAO had yet to condemn the incident, and pointed out that the ICAO needed only three months to adopt a unanimous resolution condemning in the strongest terms the destruction and alleged murders of Malaysia Airlines Flight MH17.[159]

On 30 December 2020, Iran unilaterally announced that it had allocated $150,000 for each victim's family. Ukraine was critical, stating that the compensation should be set through talks after establishing the causes of the crash, and that "the Ukrainian side expects from Iran a draft technical report on the circumstances of the aircraft shooting down".[160]

On 20 May 2021, Justice Belobaba of the Ontario Superior Court of Justice released a decision finding that "The shooting down of Flight 752 by the defendants (Islamic Republic of Iran) was an act of terrorism and constitutes "terrorist activity" under the SIA (State Immunity Act), the JVTA (Justice For Victims of Terrorism Act) and the provisions of the Criminal Code."[161] The defendants were not represented or in attendance in court and the case resulted in a default judgment. Iran's foreign ministry denounced the court's verdict as political, stating "This verdict has no basis and does not consist of any objective reasoning or documentation ... This behaviour of the Canadian judge, by following orders and political cliches, is shameful for a country which claims to follow the rule of law." Leah West, an assistant professor at the Norman Paterson School of International Affairs at Carleton University said that the "judge contorted the law by cherry-picking his way to finding the aircraft was destroyed in an act of terrorism." She concluded "While his motivations for doing all that may be noble, that's dangerous for the rule of law".[162] The lawyer for the plaintiffs indicated that, depending on the amounts awarded, he would move to have Iranian assets in Canada or internationally seized, including oil tankers.[163] As of 3 January 2022, the Ontario Superior Court has awarded more than C$107M to families of six victims after ruling the shootdown was "an intentional act of terrorism". It is unclear how any of the plaintiffs will collect their settlements from the government of Iran and legal experts have indicated that a diplomatic solution for compensation may be the only realistic route available, since Iran views the court ruling as illegitimate.[164][165]

Reactions

Air traffic

Ukraine International Airlines (UIA) suspended flights to Tehran indefinitely shortly after the incident, with flights after the day of the crash no longer available.[43] The suspension also complied with a prohibition issued by State Aviation Administration of Ukraine for flights in Iran's airspace for all Ukrainian registered aircraft.[166] Since the crash, additional airlines, Air Astana and SCAT Airlines also re-routed flights that overflew Iran.[167][168] This followed a recommendation by the Kazakhstan Ministry of Industry and Infrastructure Development, issued to Kazakhstani air companies after the crash, to avoid flying over Iran airspace and/or to cancel flights to Iran.[169] Air Canada rerouted its Toronto-Dubai flight to fly over Egypt and Saudi Arabia instead of Iraq.[170]

Iran

Government and IRGC

File:Commemoration of the victims of UIA Flight 752 2.jpg
Commemoration of the victims of the air crash in Iran

Iran declared 9 January a national day of mourning both for the victims of Flight 752 and for those killed in a stampede at Qasem Soleimani's funeral.[171]

On 11 January, the Iranian IRGC said they had shot down the aircraft after erroneously identifying it as a hostile target.[172] President Rouhani called the incident an "unforgivable mistake".[173] Foreign minister Mohammad Javad Zarif apologized for the disaster and added that the preliminary conclusion of the armed forces' internal investigation was "human error".[174]

On 17 January, Iranian Supreme Leader Ali Khamenei, in his first Friday sermon in eight years, referred to the incident as a bitter accident. His sermon came as public anger mounted against the government for their handling of the incident.[175]

In April, an Iranian MP, the spokesman for the Iranian parliament's legal and judicial committee, said the Iranian military "carried out their duties well", adding that "the movement of the plane was very suspicious" and that no arrests had been made in relation to the incident.[176][177]

Anti-government protests

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

File:Gathering and protest rally outside Amir Kabir University 2020-01-11 11.jpg
A gathering at Amirkabir University of Technology. Above flowers and lit candles a notice reads "What is the cost of lying?"

On 11 January, in response to the government's admission, thousands of protesters poured into the streets of Tehran and other Iranian cities such as Isfahan, Shiraz, Hamadan and Urmia.[178] Video clips on Twitter showed protesters in Tehran chanting "Death to the dictator", a reference to Supreme Leader Ali Khamenei.[179] In Tehran, hundreds of protesters took to the streets to vent anger at officials, calling them liars for having denied the shootdown. Protests took place outside at least two universities: students and protesters gathered at Sharif University, Amirkabir University and Hafez Overpass in Tehran, initially to pay respect to the victims. Protests turned angry in the evening. President Trump tweeted support for the protests.[180][181][182] The mourning Iranians called Qasem Soleimani a murderer and tore up pictures of him, shattering the appearance of national solidarity that had followed his death.[183][184][185][186][187][188]

On 12 January, in Tehran and in several other cities protesters chanted slogans against the leadership and clashed with security forces and Iran's Basiji Force firing tear gas at the protesters.[189] The protesters chanted that they needed more than just resignations, but prosecutions of those responsible as well.[190] Tehran residents told Reuters that police were out in force in the capital on 12 January, with dozens of protesters in Tehran chanting "They are lying that our enemy is America, our enemy is right here," and scores of demonstrators gathered in other cities.[191]

Amnesty International reported that on 11 and 12 January Iranian security forces used tear gas, pointed pellets and pepper spray against peaceful demonstrators.[192] On 13 January, the Los Angeles Times reported that Iranian security forces fired both live ammunition and tear gas to disperse demonstrators.[193]

Iran's exiled Crown Prince Reza Pahlavi said the Supreme Leader Ali Khamenei was responsible for the downing.[194] Iranian reformist newspaper Etemad ran the banner headline "Apologize and resign", and commented on the "people's demand" for the removal of those responsible for the shootdown.[195]

A Khamenei representative in the elite Revolutionary Guards told a gathering of Khamenei's representatives in Iranian universities that the Assembly of Experts, the clerical body that chose Khamenei, "... do not appoint the Supreme Leader, rather they discover him [...] In the Islamic system, the office and the legitimacy of the Supreme Leader comes from God, the Prophet and the Shi'ite Imams".[196]

Funerals

Iran's Radio Farda reported that according to Zeytoun (a Persian website based outside of Iran), Iranian intelligence agents forced families of the victims to give interviews on state TV, declaring their support for the Iranian government or else the government would not deliver the bodies of the victims.[197]

Iran's security forces were on alert not to let people turn funerals of the plane crash victims into demonstrations. Nevertheless, in some Iranian cities such as Isfahan and Sanandaj, participants in these funerals have shown their anger and shouted anti-government slogans.[198] The supreme leader Ali Khamenei praised the country's armed forces and described the protesters as those deceived by foreign media.[199]

Arrests

On 14 January 2020, Iran's judiciary announced that several arrests had been made over "the accidental shooting down of the aircraft". The spokesman, Gholamhossein Esmaili, did not name any suspect or say how many had been held.[200][201] In a televised speech, President Rouhani said the judiciary would assemble a special court with a high-ranking judge and tens of experts to oversee the investigation.[202] The same day, it was announced that Iranian authorities had arrested the person who had published a video of the aircraft being shot down.[203] An Iranian journalist based in London who initially posted the footage insisted his source was safe and that the Iranian authorities had arrested the wrong person.[204] According to Tasnim News Agency and the semi-official Fars News Agency, Iranian authorities were looking for the person(s) who distributed the video.[205]

On 6 April 2021, Iran indicted 10 officials over the shooting down of the aircraft. The outgoing military prosecutor for Tehran province said that "necessary decisions will be taken in court."[206]

Ukraine

File:IL76 Ukraine International Airlines Flight 752.jpg
Commemoration of the victims of the air crash in Iran at Kyiv Boryspil airport

President Zelenskyy expressed condolences to the relatives of the victims[207] and cut short his diplomatic visit in Oman. He later added that several aircraft had been prepared in Kyiv to travel to Tehran to transport the dead. He declared 9 January a national day of mourning, with Ukrainian flags flying at half-mast on government buildings. He also announced unscheduled inspections on every airliner in the country and asked Ukrainians to refrain from visiting Iran and Iraq for the time being.[208] On 11 January Zelenskyy said, "Ukraine insists on a full admission of guilt. We expect Iran to bring those responsible to justice, return the bodies, pay compensation and issue an official apology. The investigation must be full, open and continue without delays or obstacles."[209]

On 13 January, Ukraine's Foreign Minister, Vadym Prystaiko, said five of the countries that had citizens on board the airliner—Canada, Ukraine, Afghanistan, Sweden and the UK[210]—would meet in London on 16 January to discuss possible legal action.[81]

On 19 January, the bodies of 11 Ukrainian citizens, who died in the crash, were returned to Ukraine in a solemn ceremony at the Boryspil International Airport. The coffins, which were each draped in a Ukrainian flag, were carried one by one from a Ukrainian Il-76 military plane of the 25th Transport Aviation Brigade.[211] President Zelensky, Secretary of the National Security and Defense Council of Ukraine Oleksiy Danilov, Prime Minister Oleksiy Honcharuk, Chairman of the Verkhovna Rada Dmytro Razumkov, and other officials and military servicemen participated in the commemoration.[212]

Canada

With the large loss of Canadian life, Canadian Foreign Affairs Minister François-Philippe Champagne and Transport Minister Marc Garneau both expressed sympathy for the victims. Champagne announced that he was in touch with the Ukrainian government, and Garneau announced that Canada was offering assistance in the investigation.[213] Prime Minister Justin Trudeau insisted on transparency and justice for the families and loved ones of the victims.[209] On 14 January, Trudeau said tensions and escalation between Iran and the United States were responsible for the shootdown.[214][215] On 17 January, the Canadian government announced that it would provide CA$25,000 to the relatives of each of the 57 Canadian citizens and permanent residents who were killed in the crash. The funds were to help cover immediate needs, like funeral and travel expenses. However, Canadian Prime Minister Justin Trudeau also said that it holds Iran financially responsible.[216]

On 31 March 2020, Ralph Goodale was appointed as Special Advisor to the Government of Canada;[217] Goodale will "examine lessons learned" from Flight 752, Ethiopian Airlines Flight 302, Air India Flight 182 and other air disasters and "develop a framework to guide Canada's responses to international air disasters."[218]

On 23 December 2020, Trudeau announced that the Government of Canada will designate 8 January of every year as the National Day of Remembrance for Victims of Air Disasters.[219]

On 24 June 2021, an official report from Canada placed the blame on the downing of the plane on Iranian "recklessness, incompetence, and wanton disregard for human life".[220]

On 7 October 2022, Trudeau announced the Iranian regime, including the IRGC and its top leaders – more than 10,000 officers and senior members – would be listed as inadmissible to Canada for their engagement in terrorism and systemic and gross human rights violations.[221]

United Kingdom

Prime Minister Boris Johnson called for the repatriation of the bodies of the dead and pledged to work with Canada and Ukraine.[209]

Ambassador of the United Kingdom to Iran, Robert Macaire was arrested on 11 January 2020 during protests in Tehran but released shortly afterwards.[222][223] The ambassador was detained on suspicion that he had joined demonstrations against the government; he denied this and clarified that he had attended an event advertised as a vigil, to pay respects to the victims, and had left five minutes after people started chanting. The British government called his arrest a "flagrant violation of international law".[223] Macaire had been arrested 30 minutes after leaving the vigil he said he had attended, according to The Guardian.[224] The following day Macaire was summoned to the Ministry of Foreign Affairs, in order to explain his presence during the protest.[225] The U.S. has urged the Iranian government to issue the British ambassador a formal apology for disregarding his rights and to reiterate that all the rights of diplomats should be respected.[226]

In popular culture

Babak Payami's documentary film 752 Is Not a Number premiered at the 2022 Toronto International Film Festival.[227]

See also

Notes

  1. The aircraft was a Boeing 737-800 model; at the time the aircraft was built, Boeing assigned a unique code for each company that bought one of its aircraft, which was applied as an infix to the model number at the time the aircraft was built. Ukrainian International Airlines' code was "KV", hence "737-8KV" (see List of Boeing customer codes).
  2. The list is based on Ukrainian sources, with notes indicating confirmed deviations.
  3. According to Iranian officials, 146 passengers used an Iranian passport to leave Iran; some victims from Canada were Canadian-Iranian citizens.
  4. Canadian Foreign Affairs Minister said "the number of Canadian citizens believed to have been aboard the airplane is 57—not 63 as initially provided by Ukrainian authorities."[46] There is no corresponding source about the six people said not to be Canadian, so the table cannot be changed, as the total would not add up.
  5. Two passengers and nine crew members[43][47]
  6. According to the Swedish Minister for Foreign Affairs, seven Swedish citizens died on the flight.[48]
  7. The manifest initially released by UIA listed three Germans. These were subsequently identified as Afghans living in Germany as asylum seekers.[49]
  8. On 10 January, UK Prime Minister Boris Johnson confirmed four Britons died on the flight.[50] It is unknown at present, which country's passport the fourth Briton presented.

References

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  5. 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. 7.0 7.1 7.2 7.3 Lua error in package.lua at line 80: module 'strict' not found.
  8. 8.0 8.1 Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 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. 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. 15.0 15.1 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 Lua error in package.lua at line 80: module 'strict' not found.
  18. 18.0 18.1 18.2 18.3 Lua error in package.lua at line 80: module 'strict' not found.
  19. 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 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. Lua error in package.lua at line 80: module 'strict' not found.
  24. 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. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. 31.0 31.1 31.2 Lua error in package.lua at line 80: module 'strict' not found.
  32. 32.0 32.1 32.2 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. 36.0 36.1 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. Lua error in package.lua at line 80: module 'strict' not found.
  39. 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. 43.0 43.1 43.2 43.3 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. 45.0 45.1 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. 49.0 49.1 Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. 51.0 51.1 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. 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. 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. 62.0 62.1 62.2 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. 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.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  81. 81.0 81.1 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. 83.0 83.1 Lua error in package.lua at line 80: module 'strict' not found.
  84. 84.0 84.1 84.2 Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
    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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  92. 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.
  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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  105. 105.0 105.1 Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. 108.0 108.1 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. 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. "Iran admits shooting down Ukrainian airliner 'unintentionally'" Archived 11 January 2020 at the Wayback Machine, The Guardian, 11 January 2020.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. 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. 131.0 131.1 131.2 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. 135.0 135.1 Lua error in package.lua at line 80: module 'strict' not found.
  136. 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. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. 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. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. 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. 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. Iran: Scores injured as security forces use unlawful force to crush protest Archived 15 January 2020 at the Wayback Machines
  193. Lua error in package.lua at line 80: module 'strict' not found.
  194. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  208. Lua error in package.lua at line 80: module 'strict' not found.
  209. 209.0 209.1 209.2 Iran admits to shooting down Ukrainian plane in 'error' Archived 11 January 2020 at the Wayback Machine By LAURA KAYALI, Politico, 11 January 2020
  210. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  219. 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. 223.0 223.1 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. "TIFF announces Mary Harron's Salvador Dali biopic as closing night film". CBC News, August 10, 2022.

External links

Template:Aviation accidents and incidents in Iran