Malaysia Airlines Flight 17 - Biblioteka.sk

Upozornenie: Prezeranie týchto stránok je určené len pre návštevníkov nad 18 rokov!
Zásady ochrany osobných údajov.
Používaním tohto webu súhlasíte s uchovávaním cookies, ktoré slúžia na poskytovanie služieb, nastavenie reklám a analýzu návštevnosti. OK, súhlasím


Panta Rhei Doprava Zadarmo
...
...


A | B | C | D | E | F | G | H | CH | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9

Malaysia Airlines Flight 17
 ...

Malaysia Airlines Flight 17
9M-MRD, the aircraft involved, seen in 2011
Shootdown
Date17 July 2014 (2014-07-17);
9 years, 11 months ago
SummaryShot down by a Buk 9M38 surface-to-air missile transported from Russia on the day of the crash[1][2]
SiteNear Hrabove, Donetsk Oblast, Ukraine
48°08′18.1″N 38°38′21.3″E / 48.138361°N 38.639250°E / 48.138361; 38.639250[3]: 111 
Aircraft
Aircraft typeBoeing 777-200ER
OperatorMalaysia Airlines
IATA flight No.MH17
ICAO flight No.MAS17
Call signMalaysian 17
Registration9M-MRD
Flight originAmsterdam Airport Schiphol, Netherlands
DestinationKuala Lumpur International Airport, Malaysia
Occupants298
Passengers283
Crew15
Fatalities298
Survivors0

Malaysia Airlines Flight 17 (MH17/MAS17)[a] was a scheduled passenger flight from Amsterdam to Kuala Lumpur that was shot down by Russian-controlled forces[4][5][6][7] on 17 July 2014, while flying over eastern Ukraine. All 283 passengers and 15 crew were killed.[8] Contact with the aircraft, a Boeing 777-200ER, was lost when it was about 50 kilometres (31 mi; 27 nmi) from the Ukraine–Russia border, and wreckage from the aircraft fell near Hrabove in Donetsk Oblast, Ukraine, 40 km (25 mi; 22 nmi) from the border.[9] The shoot-down occurred during the war in Donbas over territory controlled by Russian separatist forces.[10]

The responsibility for investigation was delegated to the Dutch Safety Board (DSB) and the Dutch-led joint investigation team (JIT), which in 2016 reported that the airliner had been downed by a Buk surface-to-air missile launched from pro-Russian separatist-controlled territory in Ukraine.[3][11] The JIT found that the Buk originated from the 53rd Anti-Aircraft Missile Brigade of the Russian Federation[12][13] and had been transported from Russia on the day of the crash, fired from a field in a rebel-controlled area, and the launch system returned to Russia afterwards.[1][2][12]

The findings by the DSB and JIT were consistent with earlier claims by American and German intelligence sources[14][15] and claims by the Ukrainian government.[16] On the basis of the JIT's conclusions, the governments of the Netherlands and Australia held Russia responsible for the deployment of the Buk installation and began pursuing legal remedies in May 2018.[17][18] The Russian government denied involvement in the shooting down of the airplane,[13][19][20] and its account of how the aircraft was shot down has varied over time.[21] Coverage in Russian media has also differed from that in other countries.[22][23]

On 17 November 2022, following a trial in absentia in the Netherlands, two Russians and a Ukrainian separatist were found guilty of murdering all 298 people on board flight MH17. The Dutch court also ruled that Russia was in control of the separatist forces fighting in eastern Ukraine at the time.[4]

This was Malaysia Airlines' second aircraft loss during 2014, after the disappearance of Flight 370 four months prior on 8 March,[24] and is the deadliest airliner shoot-down incident to date.[25]

Aircraft

Flight 17, which was also marketed as KLM Flight 4103 (KL4103) through a codeshare agreement,[26] was operated with a Boeing 777-2H6ER,[b] serial number 28411, registration 9M-MRD.[3]: 30  The 84th Boeing 777 produced; it first flew on 17 July 1997, exactly 17 years before the incident, and was delivered new to Malaysia Airlines on 29 July 1997.[27] Powered by two Rolls-Royce Trent 892 engines and carrying 280 seats (33 business and 247 economy), the aircraft had recorded more than 76,300 hours in 11,430 cycles before the crash.[3]: 30  The aircraft was in an airworthy condition at departure.[3]: 31 

The Boeing 777, which entered commercial service on 7 June 1995, has one of the best safety records among commercial aircraft.[28] In June 2014, there were about 1,212 aircraft in service, with 340 more on order.[29]

Passengers and crew

People on board by nationality[3]: 27 
Nation Number
Australia 27
Belgium 4
Canada[c] 1
Germany[d] 4
Indonesia 12
Malaysia[e] 43
Netherlands[f] 193
New Zealand 1
Philippines 3
United Kingdom[g] 10
Total 298

The incident is the deadliest airliner shoot-down incident to date.[25] All 283 passengers and 15 crew died.[3]: 27  By 19 July, the airline had determined the nationalities of all 298 passengers and crew.[24]

The crew were all Malaysian, while over two-thirds (68%) of the passengers were Dutch. Most of the other passengers were Malaysians and Australians; the remainder were citizens of seven other countries.[3]: 27 

Among the passengers were delegates en route to the 20th International AIDS Conference in Melbourne, including Joep Lange, a former president of the International AIDS Society, which organised the conference.[32] Many initial reports had erroneously indicated that around 100 delegates to the conference were aboard, but this was later revised to six.[33] Also on board were Dutch Senator Willem Witteveen,[34] Australian author Liam Davison,[35] and Malaysian actress Shuba Jay.[36]

At least twenty family groups were on the aircraft, and eighty passengers were under the age of 18.[37][38]

The flight crew were captains Wan Amran Wan Hussin (49) and Eugene Choo Jin Leong (44), and first officers Ahmad Hakimi Hanapi (29) and Muhamad Firdaus Abdul Rahim (26). Captain Wan had a total of 13,239 flight hours, including 7,989 in Boeing 777s. Captain Choo had a total of 12,385 flight hours, including 7,303 in Boeing 777s. First Officer Ahmad had a total of 3,190 flight hours, including 227 in Boeing 777s. First Officer Muhamad Firdaus had a total of 4,058 flight hours, including 296 in Boeing 777s.[3][39][h]

Background

The armed conflict in Eastern Ukraine led some airlines to avoid eastern Ukrainian airspace in early March 2014 due to safety concerns.[41][42] In the months prior to 17 July, reports circulated in the media on the presence of weapons, including surface-to-air missiles, in the hands of the rebels that were fighting the Ukrainian government in eastern Ukraine.[43][44]

On 26 May, a spokesperson of the Ukrainian Armed Forces stated that a surface-to-air missile system that was being used by the rebels, near Donetsk airport, had been destroyed by a helicopter of the Ukrainian army. On 6 June 2014 The International New York Times reported that surface-to-air missiles had been seized from military bases. On 11 June, the newspaper Argumenty nedeli [ru; de] reported that a Buk-M1 missile launcher had been present in an area under the separatists' control. On 29 June the Russian news agencies reported that insurgents had obtained a Buk missile system after having taken control of Ukrainian military unit A-1402;[43][44] and the Donetsk People's Republic claimed possession of such a system in a since-deleted tweet.[43][45][46]

Such air defence systems cannot reliably identify and avoid civilian aircraft.[47][48] The Ukrainian authorities declared in the media that this system was not operational.[3]: 187–188  According to the subsequent statement of the Security Service of Ukraine, three Buk missile systems were located on militia-controlled territory at the time that Malaysia Airlines Boeing 777 was shot down. On the night following the downing of MH17, two Buk launcher vehicles, one of which carried three missiles, (out of a normal complement of four), was observed moving into Russia.[49][50][51]

Several aircraft from the Ukrainian Air Force were shot down in the months and days preceding the MH17 incident. On 14 June 2014, a Ukrainian Air Force Ilyushin Il-76 military transport was shot down on approach to Luhansk International Airport, with loss of nine crew members and forty troops.[3]: 183  On 14 July 2014, a Ukrainian Air Force An-26 transport aircraft flying at 6,500 m (21,300 ft) was shot down.[3]: 183  The militia reportedly claimed via social media that a Buk missile launcher, which they had previously seized and made operational, had been used to bring down the aircraft.[52] American officials later said evidence suggested the aircraft had been shot down from Russian territory.[53]

On 16 July, the Ministry of Defence of Ukraine reported that at about 13:00 local time "terrorists" used MANPADs against a Su-25 jet which was performing a flight mission in the ATO zone. According to the report, the airplane received minor damage and was forced to make a landing.[54][55][56] Later, the Ministry of Defence of Ukraine reported on the second Su-25 that was attacked on the same day at about 19:00 local time near the Ukrainian-Russian border in the area of Amvrosiivka.[57][58] According to the details reported by Ukraine's RNBO spokesperson Andriy Lysenko, the Ukrainian Su-25 was shot down by an R-27T medium range air-to-air missile fired by a MiG-29 jet from Russian territory while the Su-25 was at an altitude of 8,250 m.[3]: 185 [59] The Russian Defence Ministry said that the accusations were false.[60][61] In response to additional questions by the Dutch Safety Board, the Ukrainian authorities reported that a "provisional investigation" had revealed that the airplane had been shot down while flying at an altitude of 6,250 m. Ukrainian authorities also thought that the Su-25 could have been shot down with a Pantsir missile system from Russian territory, though they thought this less likely.[3]: 185 

On 17 July, an Associated Press journalist saw a Buk launcher in Snizhne, in Donetsk Oblast, 16 kilometres (10 mi) southeast of the crash site. The reporter also saw seven separatist tanks near the town.[62] Associated Press journalists reported that the Buk M-1 was operated by a man "with unfamiliar fatigues and a distinctive Russian accent" escorted by two civilian vehicles.[63] The battle around Savur-Mohyla has been suggested as the possible context within which the missile that brought down MH17 was fired, as separatists deployed increasingly sophisticated anti-aircraft weaponry in this battle, and had brought down several Ukrainian jets in July.[64]

In April, the International Civil Aviation Organization had warned governments that there was a risk to commercial passenger flights over south-eastern Ukraine.[3]: 217  The American Federal Aviation Administration issued restrictions on flights over Crimea, to the south of MH17's route, and advised airlines flying over some other parts of Ukraine to "exercise extreme caution". This warning did not include the MH17 crash region.[65][66] 37 airlines continued overflying eastern Ukraine and about 900 flights crossed the Donetsk region in the seven days before the Boeing 777 was shot down.[67] Russian air traffic controllers issued a notice effective 17 July at 00:00 with two conflicting altitude restrictions in the airspace in the adjacent area over Russia below 32,000 feet (9,800 m) and below 53,000 feet (16,000 m). Long-distance flights typically travel at altitudes of 33,000 to 44,000 feet,[68] so the second restriction would effectively close that airspace to civilian overflights, but the second restriction was not noted by the automated systems of Malaysian Airlines and the route was not changed. The reason given for the notice was "armed conflict in Ukraine". Russian authorities told the Dutch Safety Board the notice had been published "to create agreement with the adjoining Ukrainian airspace", but provided no clarification for the higher restriction.[69][70]

The airspace above Donetsk was managed by Ukraine. The Ukrainian authorities imposed restrictions for flights under 32,000 feet (9,800 m), but did not consider closing the airspace to civil aviation completely.[3]: 10 [71][72] As with other countries, Ukraine receives overflight fees for commercial aircraft that fly through their territory and this may have contributed to the continued availability of civilian flight paths through the conflict zone.[73][74] However, the Netherlands, where the main investigation was conducted, did not hold Ukraine accountable for not closing its airspace due to lack of evidence that it should have done so.[75]

Flight and shoot-down

Route of Malaysia Airlines Flight 17
Routes of Malaysia Airlines Flight 17 (MH17) and Singapore Airlines Flight 351 (SQ351), including airspace restrictions

On Thursday, 17 July 2014, Malaysia Airlines Flight 17 departed from Amsterdam Airport Schiphol Gate G3 at 12:13 CEST (10:13 UTC), thirteen minutes later than the scheduled departure time, and took off at 12:31 local time (10:31 UTC).[3]: 23  It was due to arrive at Kuala Lumpur International Airport at 06:10 MYT, Friday, 18 July (22:10 UTC, 17 July).[76]

Cruise

According to the original flight plan, MH17 was to fly over Ukraine at flight level 330 (33,000 feet or 10,060 metres) and then change to FL 350 around the Ukrainian city of Dnipropetrovsk. When it reached the area as planned, at 15:53 local time (12:53 UTC), Dnipropetrovsk Air Control (Dnipro Control) asked MH17 if they could climb to FL 350 as planned, and also to maintain separation from another flight, Singapore Airlines Flight 351 (SQ351), also at FL 330. The crew asked to remain at FL 330 and the air traffic controller approved this request, moving the other flight to FL 350. At 16:00 local time (13:00 UTC), the crew asked for a deviation of 20 nautical miles (37 km; 23 mi) to the left (north) off course, on airway L980, due to weather conditions. This request was also approved by Dnipro Control ATC. The crew then asked if they could climb to FL 340, which was rejected as this flight level was not available, so MH17 remained at FL 330. At 16:19 local time (13:19 UTC), Dnipro Control noticed that the flight was 3.6 nmi (6.7 km; 4.1 mi) north of the centreline of its approved airway and instructed MH17 to return to the track. At 16:19 local time (13:19 UTC), Dnipro Control contacted Russian ATC in Rostov-on-Don (RND Control) by telephone and requested clearance to transfer the flight to Russian airspace. After obtaining permission, Dnipro Control attempted to contact MH17 for handing them off to RND Control at 16:20 local time (13:20 UTC), but the aircraft did not respond. When MH17 did not respond to several calls, Dnipro Control contacted RND Control again to check if they could see the aircraft on their radar. RND Control confirmed that the airliner had disappeared.[8]

Shoot-down

Flight data recordings

The Dutch Safety Board reported that both the cockpit voice recorder (CVR) and the flight data recorder (FDR) stopped recording at 16:20:03 local time (13:20:03 UTC). The last FDR data indicates that the plane was at the position of 48.12715 N 38.52630538 E located west of the urban-type settlement Rozsypne (Розсипне), near Hrabove, heading east-southeast (ESE, 115°) at an altitude of 32,998 feet above sea level with a ground speed of 494 knots (915 km/h; 568 mph) and an indicated airspeed of 293 knots.[8][3]: 46–47 & 111  The flight recorders show no sign of warning or unusual occurrence prior to the end of their recordings, but two sound peaks are heard in the last 20 milliseconds of the CVR recording.[3]: 45 

Missile strike

At 16:20:03 local time (13:20:03 UTC), a Buk ground-to-air missile, which had been launched from an area southeast of the aircraft, detonated outside the airplane, just above and to the left of the cockpit.[3]: 142–147  The blast and fragments of the missile severely damaged the cockpit and instantly killed three crew members in it.[3]: 147–149, 139–141, 136  Evidence on the left engine intake ring and left wing tip suggests that the left wing and left engine had also picked up some shrapnel from the missile.[3]: 60, 136  An explosive decompression occurred, tearing the forward section of the aircraft into pieces, causing the middle and rear sections to tear into three sections and depressurizing the cabin.[3]: 150–152  The explosive decompression could have incapacitated most occupants of the aircraft before the crash, though investigators never ruled out the possibility that some were still conscious when the aircraft impacted the ground. Some occupants might have suffered serious injuries that contributed to their deaths before the crash.[3]: 165  The aircraft fell rapidly and continued disintegrating before impacting the ground.[3]: 54–55, 152–153 

In-flight breakup

Investigators were able to determine how the aircraft disintegrated and crashed.[3]: 149–163  The aircraft began disintegrating immediately after being struck by a missile.[3]: 160  Investigators believed that the disintegration of the forward section of the fuselage started between the left-side cockpit windows and the forward, left-exit door.[3]: 151  The cockpit section and the business class section of the aircraft began tearing into a number of pieces before the aircraft descended rapidly toward the ground.[3]: 150–152  During that period of time, the left engine intake ring had also fallen off the engine and fell in the same place as where some of these pieces fell.[3]: 54, 60, 162 

As the aircraft was falling, the instability and aerodynamic loads of the aircraft stressed its fuselage, resulting in further disintegration.[3]: 160  Shortly before crashing into the ground, the rear section of the fuselage, just behind where the two wings were attached to the fuselage, was separated from the middle portion of the fuselage.[3]: 152  At the same time, the two wing tips had fallen off from the wings of the aircraft.[3]: 161  The tail section, which was just behind the aft exit doors, was also separated from the rear section.[3]: 153  The pair of horizontal stabilizers and the vertical stabilizer were also separated from the tail section prior to impacting the ground.[3]: 161  The middle portion, including the two wings and two engines, eventually crashed into farmland and its large quantity of jet fuel exploded upon impact.[3]: 54–55, 76 

The positions of the aircraft wreckage suggest that the plane might have been upside down when the rear and middle sections disintegrated, and the middle portion probably crashed inverted while travelling rearward.[3]: 161–162  Investigators could not specify the exact time when each major section of the plane hit the ground. However, they estimated that the middle portion of the aircraft had impacted the ground within 1-1.5 minutes after the beginning of the in-flight breakup.[3]: 162 

Debris field

The mid-air disintegration had caused the seats, pieces of interior wall and floor, overhead compartments, and other interior structures of the aircraft to fall out of the plane. Some bodies, personal belongings, and other light objects had also fallen out of the plane. As the result of the disintegration, the debris of the plane landed in six different areas.[3]: 53 

In the investigation report, the position where the plane was struck by a missile is identified as the "last FDR point" because it is where the flight data recorder stopped recording. A few parts of the business class and cockpit sections landed on farm land far north of the last FDR point. The business class section and the left engine intake ring landed in the large residential area of Petropavlivka, northeast of the last FDR point. The cockpit and the forward cargo section, including the nose landing gear, landed on farm land far southeast of the last FDR point and southwest of the village of Rozsypne. The tail and the rear fuselage sections landed farther east of the last FDR point, while the middle portion of the aircraft landed at 48°8′17″N 38°38′20″E, just northeast of them.[3]: 54–55 

Most of the debris of the aircraft, which were the middle and rear sections, landed near southwest of the village of Hrabove, north of Torez (now also known as Chystiakove). The wreckage had spread over a 50 square kilometres (19 sq mi) area in Donetsk Oblast, eastern Ukraine.[3]: 53  The fireball on impact is believed to have been captured on video.[77] Photographs from the site of the crash show scattered pieces of broken fuselage and engine parts, bodies, and passports.[78] Some of the wreckage fell close to houses.[79] Dozens of bodies fell into crop fields, and some fell into houses.[80]

Nearby aircraft

Three other commercial aircraft were in the same area when the Malaysian airliner was shot down: Air India Flight 113 (AI113), a Boeing 787 en route from Delhi to Birmingham, EVA Air Flight 88 (BR88), a Boeing 777 en route from Paris to Taipei, and the closest aircraft, Singapore Airlines Flight 351 (SQ351), was 33 kilometres (21 mi) away, a Boeing 777 en route from Copenhagen to Singapore.[3]: 41 

Recovery of bodies

First arrival of bodies at Eindhoven Airport

A Ukraine Foreign Ministry representative said that the bodies found at the crash site would be taken to Kharkiv for identification, 270 kilometres (170 mi) to the north. By the day after the crash, 181 of the 298 bodies had been found.[81] Some were observed being placed in body bags and loaded onto trucks.[82][83][84]

Dutch Prime Minister Mark Rutte initially complained about looting of personal belongings from the dead and the careless handling of their bodies, but later stated they had been handled with more care than originally thought.[85][86][87] Other media complained that credit and debit cards were being looted,[88] and there were accusations that evidence at the crash site had been destroyed.[89][90] The Guardian noted that tales of looting seemed to be exaggerated, but the chaos at the crash site risked the accidental destruction of evidence which, the paper contended, journalists were contributing to.[91]

On 20 July, Ukrainian emergency workers, observed by armed pro-Russian separatists, began loading the remains of the passengers of MH17 into refrigerated railway wagons for transport and identification.[92]

On 21 July, pro-Russian rebels allowed Dutch investigators to examine the bodies. By this time, 272 bodies had been recovered, according to Ukrainian officials.[93] Remains left Torez on a train on the evening of 21 July, en route to Kharkiv to be flown to the Netherlands for identification.[94] On the same day, Malaysian Prime Minister Najib Razak announced that the Malaysian government had reached a tentative agreement to retrieve the remains of the Malaysians who died in the crash, following any necessary forensic work.[95]

Convoy of 40 hearses heading to Hilversum, Netherlands, while other traffic stopped

It was reported on 21 July that with 282 bodies and 87 body fragments found, there were still 16 bodies missing.[96] An agreement had been reached that the Netherlands would co-ordinate the identification effort. A train carrying the bodies arrived at the Malyshev Factory, Kharkiv on 22 July.[97] Dutch authorities stated that they found 200 bodies on the train when it arrived at Kharkhiv, leaving almost 100 unaccounted for.[98] In late July, the UK Metropolitan Police sent specialist officers to Ukraine to assist with the recovery, identification and repatriation of bodies.[99]

The first remains were flown to Eindhoven in the Netherlands on 23 July,[100] moved there with Dutch air force C-130 and Australian C-17 transport aircraft,[101][102] which landed at Eindhoven Airport just before 16:00 local time.[103] The day after, another 74 bodies arrived.[104] The examination and identification of the bodies was conducted at the Netherlands Army medical regiment training facility in Hilversum and was coordinated by a Dutch forensic team.[105]

On 1 August it was announced that a search and recovery mission, including about 80 forensic police specialists from the Netherlands, Malaysia and Australia, and led by Colonel Cornelis Kuijs of the Royal Marechaussee, would use drones, sniffer dogs, divers and satellite mapping to search for missing body parts at the crash site.[106][107] Australian officials had believed that as many as 80 bodies were still at the site,[108] but after some days of searching the international team had "found remains of only a few victims" and concluded that "the recovery effort undertaken by local authorities immediately after the crash was more thorough than initially thought."[87]

On 6 August the Dutch Prime Minister Mark Rutte announced that the recovery operation would be temporarily halted due to an upsurge in fighting around the crash site threatening the safety of crash investigators and recovery specialists, and that all international investigators and humanitarian forces conducting searches would leave the country leaving behind a small communications and liaison team.[109]

On 22 August the bodies of 20 Malaysians (of 43 killed in the incident) arrived in Malaysia.[110] The government announced a National Mourning Day, with a ceremony broadcast live on radio and television.[111]

On 9 October a spokesman for the Dutch national prosecutor's office stated that one victim had been found with an oxygen mask around his neck; a forensic investigation of the mask for fingerprints, saliva and DNA did not produce any results and it is therefore not known how or when the mask got around the neck of the victim.[3]: 99 

By 5 December 2014, the Dutch-led forensic team had identified the bodies of 292 out of 298 victims of the crash.[112] In February and April 2015 new remains were found on the site,[113][114] after which only two victims, both Dutch citizens, had not been identified.[114]

Aftermath

About 90 minutes after the incident, Ukraine closed all routes in Eastern Ukrainian airspace, at all altitudes.[3]: 101  The incident dramatically heightened fears about airliner shoot-downs,[115] leading to some airlines announcing they would avoid overflying conflict zones.

Shortly after the crash, it was announced that Malaysia Airlines would retire flight number MH17 and change the Amsterdam–Kuala Lumpur route to flight number MH19 beginning on 25 July 2014, with the outbound flight MH16 unchanged.[116][117] In association with the retirement of the Boeing 777 aircraft type from Malaysia Airlines' fleet, Malaysia Airlines ended its service to Amsterdam on 25 January 2016, opting to codeshare with KLM on the KUL-AMS route for the services instead.[118] Following the shootdown, shares in Malaysia Airlines dropped by nearly 16%.[119]

On 23 July 2014, two Ukrainian military jets were hit by missiles at the altitude of 17,000 feet (5,200 m) close to the area of the MH17 crash. According to the Ukrainian Security Council, preliminary information indicated that the missiles came from Russia.[120]

In July 2015, Malaysia proposed that the United Nations Security Council set up an international tribunal to prosecute those deemed responsible for the downing of the aircraft. The Malaysian resolution received the support of 11 of the 15 members in the council, with three abstentions. The resolution was vetoed by Russia.[121] The Russian government proposed an alternative draft resolution, which would not have set up a tribunal.[122][123][124][125][126]

Investigation

Two parallel investigations were led by the Dutch, one into the technical cause of the crash, and a separate criminal inquiry.[127] The technical report was released on 13 October 2015,[128] and the criminal investigation reported some of their findings in September 2016.[2][129] According to the Convention on International Civil Aviation, the country in which an aviation incident occurs is responsible for the investigation, but that country may delegate the investigation to another state; Ukraine has delegated the leadership of both investigations to the Netherlands.[130][131][132][133]

On-site investigation

In the hours following the crash, a meeting was convened of the Trilateral Contact Group. After they had held a video conference with representatives of insurgents affiliated with the Donetsk People's Republic (who controlled the area where the aircraft crashed), the rebels promised to "provide safe access and security guarantees" to "the national investigation commission" by co-operating with Ukrainian authorities and OSCE (Organization for Security and Co-operation in Europe) monitors.[134] During the first two days of investigation, the militants prevented the OSCE and the workers of Ukrainian Emergencies Ministry from freely working at the crash site. Andrei Purgin, a leader of the Donetsk People's Republic, declared later that "we will guarantee the safety of international experts on the scene as soon as Kiev concludes a ceasefire agreement".[135]

Dutch and Australian police at the crash site on 3 August 2014

By 18 July 2014, the flight data recorder and the cockpit voice recorder had been recovered by separatists,[136] and three days later were handed over to Malaysian officials in Donetsk.[3]: 44 [137] The voice recorder was damaged but there was no evidence that data had been tampered with.[3]: 45 

The National Bureau of Air Accidents Investigation of Ukraine, which led investigations, both off- and on-site, during the first days after the crash,[138] had by August 2014 delegated the investigation to the DSB because of the large number of Dutch passengers and the flight having originated in Amsterdam.[3]: 14 [139][140]

On 22 July 2014, a Malaysian team of 133 officials, search and recovery personnel, and forensics, technical and medical experts arrived in Ukraine.[93] Australia sent a 45-member panel headed by former Air Chief Marshal Angus Houston, who had earlier supervised the MH370 probe.[141] Approximately 200 special forces soldiers from Australia were also deployed to provide support for the JIT investigators.[142] The United Kingdom sent six investigators from the Air Accidents Investigation Branch (AAIB) and the UK Foreign Office sent extra consular staff to Ukraine.[99] It took until late July before the full international team could start working at the crash site,[143] under the leadership of the Dutch Ministry of Defence.[144]

On 30 July 2014, a Ukrainian representative said that pro-Russian rebels had mined approaches to the crash site and moved heavy artillery.[145]

On 6 August 2014, the experts left the crash site due to concerns about their safety.[146] In mid-September they unsuccessfully attempted to regain access to the site.[147][148] On 13 October 2014, a Dutch-Ukrainian team resumed recovery of victims' personal belongings.[149] In mid-November 2014, work was undertaken to remove part of the wreckage from the crash site. Earlier efforts by the recovery team to salvage the MH17 wreckage had been frustrated by disagreements with the local rebels.[150][151] The recovery operation took a week. The debris was transported to the Netherlands where investigators reconstructed parts of the aircraft.[152]

In August 2015, possible Buk missile launcher parts were found at the crash site by the Dutch-led joint investigation team (JIT).[153][154]

Cause of the crash

A mobile Buk surface-to-air missile launcher, similar to that used in the incident
External audio
audio icon Pro-Russian rebels discuss the shooting down of an aircraft Intercepted phone calls, verified with voice recognition by the U.S. National Security Agency,[155] between rebels discussing which rebel group shot down the aircraft and initial reports that it was a civilian aircraft. Audio (in Russian) released by the Security Service of Ukraine with English subtitles.[156][157]

Soon after the crash both American and Ukrainian officials said that a 9M38 series surface-to-air missile strike was the most likely cause.[158] If so, then the missile was fired from a mobile Soviet-designed Buk missile system (NATO reporting name: SA-11 "Gadfly"). At the time, Buk was the only surface-to-air missile system known to be deployed in the region that was capable of reaching the cruising altitude of commercial air traffic.[53][159][160][161][162][163] Such systems, unless they receive information from larger networks, have limited capacity to distinguish between military and civilian aircraft.[164][165][166]

According to defence analyst Reed Foster (from Jane's Information Group), the contour of the aluminium and the blistering of the paint around many of the holes on the aircraft fragments indicate that small, high-velocity fragments entered the aircraft externally, a damage pattern indicative of an SA-11.[167] Ballistics specialist Stephan Fruhling of the Australian National University's Strategic and Defence Studies Centre concurred with this, explaining that since it struck the cockpit rather than an engine it was probably a radar guided, rather than heat seeking, missile equipped with a proximity fuzed warhead such as an SA-11.[168]

Shortly after the crash, Igor Girkin, leader of the Donbas separatists, was reported to have posted on social media network VKontakte, taking credit for downing a Ukrainian An-26.[169][170][171] This news was repeated by channels in Russia, with LifeNews reporting "a new victory of Donetsk self-defence who shot down yet another Ukrainian airplane".[172] Russian news agency TASS also reported eyewitness accounts claiming that the Donbas militia had just shot down a Ukrainian An-26 military aircraft with a missile.[173] The separatists later denied involvement, saying they did not have the equipment or training to hit a target at that altitude.[174][175][176] Russian media also reported that Alexander Borodai called one of the Moscow media managers 40 minutes after the crash, saying that "likely we shot down a civilian airliner".[171]

Witnesses in Torez reported sightings on the day of the incident of what appeared to be a Buk missile launcher,[177] and AP journalists reported sightings of a Buk system in separatist controlled Snizhne.[63] The witness reports backed up photographs and videos which had been posted online, of the Buk launcher in rebel-held territory.[177]

On 19 July 2014, Vitaly Nayda, the chief of the Counter Intelligence Department of the Security Service of Ukraine (SBU), told a news conference, "We have compelling evidence that this terrorist act was committed with the help of the Russian Federation. We know clearly that the crew of this system were Russian citizens."[178][179][180] He cited what he said were recorded conversations in which separatists expressed satisfaction to Russian intelligence agents that they had brought down an aircraft.[181][182] One of the separatists acknowledged that the conversations had taken place, but denied that they were related to the crash of MH17 and blamed the Ukrainian government for shooting it down.[76][183][184] According to Nayda, a Buk launcher used in the shoot-down was moved back into Russia the night after the attack.[63] The SBU released another recording, which they said was of pro-Russian-separatist leader Igor Bezler being told of an approaching aircraft two minutes before MH17 was shot down. Bezler said the recording was real, but referred to a different incident.[185] The head of the SBU, Valentyn Nalyvaichenko, later claimed that rebels had intended to shoot down a Russian airliner in a false flag operation to give Russia a pretext to invade Ukraine, but shot down MH17 by mistake.[186][187][188]

Journalists from the Associated Press in Snizhne, Ukraine reported seeing a Buk M-1 enter the town operated by a man "with unfamiliar fatigues and a distinctive Russian accent" escorted by two civilian vehicles, which then moved off in the direction where the shoot-down later occurred. According to Ukrainian counterterrorism chief, Vitaly Nayda, after downing the airliner under separatist direction, the launcher's Russian crew quickly moved it back across the border into Russia.[63]

American officials said that satellite data from infrared sensors detected the explosion of Flight MH17.[189] American intelligence agencies said that analysis of the launch plume and trajectory suggested the missile was fired from an area near Torez and Snizhne.[53][160] The Daily Telegraph said: "The Telegraph's own inquiries suggest the missile, an SA-11 from a Buk mobile rocket launcher, was possibly fired from a cornfield about 19 kilometres (12 mi) to the south of the epicentre of the crash site."[161] Other sources suggest the missile was launched from the separatist-controlled town of Chernukhino.[190] Several other media outlets including The Guardian, The Washington Post and the Sydney Morning Herald, reported that the aircraft was believed to have been downed by a rebel-fired missile.[108][191][192]

On 28 July 2014, Ukrainian security official Andriy Lysenko announced, at a press conference, that black box recorder analysis had revealed that the aircraft had been brought down by shrapnel that caused "massive explosive decompression." Dutch officials were reported to be "stunned" by what they saw as a "premature announcement" and said that they had not provided this information.[193] Zdroj:https://en.wikipedia.org?pojem=Malaysia_Airlines_Flight_17
Text je dostupný za podmienok Creative Commons Attribution/Share-Alike License 3.0 Unported; prípadne za ďalších podmienok. Podrobnejšie informácie nájdete na stránke Podmienky použitia.








Text je dostupný za podmienok Creative Commons Attribution/Share-Alike License 3.0 Unported; prípadne za ďalších podmienok.
Podrobnejšie informácie nájdete na stránke Podmienky použitia.

Your browser doesn’t support the object tag.

www.astronomia.sk | www.biologia.sk | www.botanika.sk | www.dejiny.sk | www.economy.sk | www.elektrotechnika.sk | www.estetika.sk | www.farmakologia.sk | www.filozofia.sk | Fyzika | www.futurologia.sk | www.genetika.sk | www.chemia.sk | www.lingvistika.sk | www.politologia.sk | www.psychologia.sk | www.sexuologia.sk | www.sociologia.sk | www.veda.sk I www.zoologia.sk