Malaysia Airlines Flight 370

Malaysia Airlines Flight 370

9M-MRO, the aircraft that disappeared, shown here on departure in 2011
Disappearance
Date	8 March 2014 (2014-03-08)
Summary	Cause unknown, some debris found
Site	Southern Indian Ocean (presumed)
Aircraft
Aircraft type	Boeing 777-200ER
Operator	Malaysia Airlines
IATA flight No.	MH370
ICAO flight No.	MAS370
Call sign	MALAYSIAN 370
Registration	9M-MRO
Flight origin	Kuala Lumpur International Airport, Sepang, Malaysia
Destination	Beijing Capital International Airport, Chaoyang-Shunyi District, China
Occupants	239
Passengers	227
Crew	12
Fatalities	239 (presumed)
Survivors	0 (presumed)

Malaysia Airlines Flight 370 was a scheduled international passenger flight operated by Malaysia Airlines that disappeared on 8 March 2014 while flying from Kuala Lumpur International Airport, Malaysia, to its destination, Beijing Capital International Airport in China.^[1] Commonly referred to as MH370, Flight 370, or Flight MH370, the flight was also marketed as China Southern Airlines Flight 748 (CZ748/CSN748) through a codeshare.^[1] The crew of the Boeing 777-200ER aircraft last communicated with air traffic control (ATC) around 38 minutes after takeoff when the flight was over the South China Sea. The aircraft was lost from ATC radar screens minutes later, but was tracked by military radar for another hour, deviating westwards from its planned flight path, crossing the Malay Peninsula and Andaman Sea. It left radar range 200 nautical miles (370 km) northwest of Penang Island in northwestern Malaysia. With all 227 passengers and 12 crew aboard presumed dead, the disappearance of Flight 370 was the deadliest incident involving a Boeing 777 and the deadliest incident of Malaysia Airlines' history, until it was surpassed in both regards by Malaysia Airlines Flight 17 four months later. The combined loss caused significant financial problems for Malaysia Airlines, which was renationalised by the Malaysian government in December 2014.

The search for the missing airplane, which became the most costly in aviation history, emphasized initially the South China and Andaman seas, before analysis of the aircraft's automated communications with an Inmarsat satellite identified a possible crash site somewhere in the southern Indian Ocean. The lack of official information in the days immediately after the disappearance prompted fierce criticism from the Chinese public, particularly from relatives of the passengers; most on board Flight 370 were of Chinese origin. Several pieces of marine debris confirmed to be from the aircraft washed ashore in the western Indian Ocean during 2015 and 2016. After a three-year search across 120,000 square kilometres (46,000 sq mi) of ocean failed to locate the aircraft, the Joint Agency Coordination Centre heading the operation suspended their activities in January 2017. A second search launched in January 2018 by the private contractor Ocean Infinity also ended without success after six months.

The disappearance of Flight 370 has been dubbed one of the greatest aviation mysteries of all time. Relying mostly on analysis of data from the Inmarsat satellite with which the aircraft last communicated, the Australian Transport Safety Bureau proposed initially that a hypoxia event was the most likely cause given the available evidence, although there has not been any consensus concerning this theory among investigators. At various stages of the investigation, possible hijacking scenarios were considered, including crew involvement, and suspicion of the airplane's cargo manifest; many unofficial theories have also been proposed by the media. The Malaysian Ministry of Transport's final report from July 2018 was inconclusive, but highlighted Malaysian air traffic controllers' failures to attempt to communicate with the aircraft shortly after its disappearance. In the absence of a definitive cause of the disappearance, safety recommendations and regulations of the air transport industry, citing Flight 370, have been intended mostly to prevent a repetition of the circumstances associated with the loss. These include increased battery life on underwater locator beacons, lengthening of recording times on flight data recorders and cockpit voice recorders, and new standards for aircraft position reporting over open ocean.

Timeline[edit]

The aircraft, a Boeing 777-200ER operated by Malaysia Airlines, last made voice contact with air traffic control at 01:19 MYT, 8 March (17:19 UTC, 7 March) when it was over the South China Sea, less than an hour after takeoff. It disappeared from air traffic controllers' radar screens at 01:22 MYT, but was still tracked on military radar as it deviated westwards from its planned flight path and crossed the Malay Peninsula, until it left the range at 02:22 while over the Andaman Sea, 200 nautical miles (370 km) northwest of the island of Penang in northwestern Malaysia. The aircraft was carrying 12 Malaysian crew members and 227 passengers from 15 nations. The multinational search effort for the aircraft was the most expensive aviation search of history.^[2][3][4] The search began in the Gulf of Thailand and the South China Sea, where the aircraft's signal was last detected on secondary surveillance radar, and was soon extended to the Strait of Malacca and Andaman Sea. Analysis of satellite communications between the aircraft and Inmarsat's satellite communications network concluded that the flight continued until at least 08:19 and flew south into the southern Indian Ocean, although the precise location cannot be determined. Australia assumed charge of the search on 17 March when the search began to emphasize the southern Indian Ocean. On 24 March, the Malaysian government noted that the final location determined by the satellite communication is far from any possible landing sites, and concluded that "Flight MH370 ended in the southern Indian Ocean."^[5] From October 2014 to January 2017, a comprehensive survey of 120,000 km² (46,000 sq mi) of sea floor about 1,800 km (1,100 mi) southwest of Perth, Western Australia yielded no evidence of the aircraft. Several pieces of marine debris found on the coast of Africa and on Indian Ocean islands off the coast of Africa—the first discovered on 29 July 2015 on Réunion—have been confirmed as pieces of Flight 370.^[6][7][8][9] The bulk of the aircraft has not been located, prompting many theories about its disappearance.

On 22 January 2018, a search by private U.S. marine company Ocean Infinity began in the search zone around 35°36′S 92°48′E / 35.6°S 92.8°E / -35.6; 92.8 (CSIRO crash area), the most likely crash site according to the drift study published in 2017.^[10][11][12]

In a previous search attempt, Malaysia had established the Joint Investigation Team (JIT) to investigate the incident, working with foreign aviation authorities and experts. Malaysia released a final report concerning Flight 370 in October 2017. Neither the crew nor the aircraft's communication systems relayed a distress signal, indications of bad weather, or technical problems before the aircraft vanished. Two passengers travelling on stolen passports were investigated, but eliminated as suspects. Malaysian police have identified the captain as the prime suspect if human intervention was the cause of the disappearance, after clearing all others on the flight of suspicion over possible motives. Power was lost to the aircraft's satellite data unit (SDU) at some point between 01:07 and 02:03; the SDU logged onto Inmarsat's satellite communication network at 02:25—three minutes after the aircraft left the range of radar. Based on analysis of the satellite communications, the aircraft turned south after passing north of Sumatra and the flight continued for six hours with little deviation in its track, ending when its fuel was exhausted.

With the loss of all 239 aboard, Flight 370 is the second-deadliest incident involving a Boeing 777 and the second-deadliest incident of Malaysia Airlines' history, second to Flight 17 in both categories. Malaysia Airlines was struggling financially, a problem that was exacerbated by a decrease of ticket sales after the disappearance of Flight 370 and the downing of Flight 17; the airline was re-nationalised by the end of 2014. The Malaysian government received significant criticism, especially from China, for failing to disclose information promptly during the early weeks of the search. Flight 370's disappearance brought to public attention the limits of aircraft tracking and flight recorders, including the limited battery life of Underwater Locator Beacons raised about four years earlier—but never mandated—following the loss of Air France Flight 447. In response to Flight 370's disappearance, the International Civil Aviation Organization (ICAO) adopted new standards for aircraft position reporting over open ocean, extended recording time for cockpit voice recorders, and, starting from 2020, will require new aircraft designs to have a means to recover the flight recorders, or the information they contain, before they sink into the water.

Aircraft[edit]

Flight deck of 9M-MRO in April 2004

Economy Class Seats (2004)

Business Class Seats (2004)

Flight 370 was operated with a Boeing 777-2H6ER,^[a] serial number 28420, registration 9M-MRO. It was the 404th Boeing 777 produced,^[14] first flown on 14 May 2002, and was delivered new to Malaysia Airlines on 31 May 2002. The aircraft was powered by two Rolls-Royce Trent 892 engines^[14] and configured to carry 282 passengers in total capacity.^[15] It had accumulated 53,471.6 hours and 7,526 cycles (takeoffs and landings) in service^[16]:22 and had not previously been involved in any major incidents,^[17] though a minor incident while taxiing at Shanghai Pudong International Airport in August 2012 resulted in a broken wing tip.^[18][19] Its last maintenance "A check" was carried out on 23 February 2014.^[20] The aircraft was in compliance with all applicable Airworthiness Directives for the airframe and engines.^[16]:27 A replenishment of the crew oxygen system was performed on 7 March 2014, a routine maintenance task; an examination of this procedure found nothing unusual.^[16]:27

The Boeing 777 was introduced in 1994 and has an excellent safety record.^{[21][22][better source needed]} Since its first commercial flight in June 1995, the type has suffered only five other hull losses: British Airways Flight 38 in 2008; a cockpit fire in a parked EgyptAir Flight 667 at Cairo International Airport in 2011;^[23][24] the crash of Asiana Airlines Flight 214 in 2013, in which three people died; Malaysia Airlines Flight 17, which was shot down over Ukraine killing all 298 people aboard in July 2014;^[25][26] and in August 2016, the sixth Boeing 777 hull-loss occurred, when Emirates Flight 521 crashed while landing and began burning at Dubai Airport.^[27]

Passengers and crew[edit]

Malaysia Airlines released the names and nationalities of the 227 passengers and 12 crew members, based on the flight manifest, later modified to include two Iranian passengers traveling on stolen passports.^[28]

Crew[edit]

All 12 crew members, two pilots and 10 cabin staff, were Malaysian citizens.^[28]

• The pilot in command was 53-year-old Captain Zaharie Ahmad Shah from Penang. He joined Malaysia Airlines as a cadet pilot in 1981 and, after training and receiving his commercial pilot's licence, became a Second Officer with the airline in 1983. Zaharie was promoted to Captain of Boeing 737-400 in 1991, Captain of Airbus A330-300 in 1996, and to Captain of Boeing 777-200 in 1998. He had been a Type Rating Instructor and Type Rating Examiner since 2007 and had 18,365 hours of flying experience.^{[16]:13[32][33]}
• The co-pilot was 27-year-old First Officer Fariq Abdul Hamid. He joined Malaysia Airlines as a cadet pilot in 2007 and became a Second Officer on Boeing 737-400 aircraft. He was promoted to First Officer of Boeing 737-400 aircraft in 2010 and later transitioned to Airbus A330-300 aircraft in 2012. In November 2013, he began training as First Officer of Boeing 777-200 aircraft. Flight 370 was his final training flight and he was scheduled to be examined on his next flight. Fariq had 2,763 hours of flying experience.^{[16]:14[34][35]}

Passengers[edit]

Of the 227 passengers, 152 were Chinese citizens, including a group of 19 artists with six family members and four staff returning from a calligraphy exhibition of their work in Kuala Lumpur; 38 passengers were Malaysian. The remaining passengers were from 13 different countries.^[28][36] Twenty passengers—12 of whom were from Malaysia and eight from China—were employees of Freescale Semiconductor.^[37][38]

By a 2007 agreement with Malaysia Airlines, Tzu Chi—an international Buddhist organisation—immediately sent specially trained teams to Beijing and Malaysia to give emotional assistance to passengers' families.^[39][40] The airline also sent its own team of caregivers and volunteers^[41] and agreed to bear the expense of bringing family members of the passengers to Kuala Lumpur and providing them with accommodation, medical care, and counselling.^[42] Altogether, 115 family members of the Chinese passengers flew to Kuala Lumpur.^[43] Some other family members chose to remain in China, fearing they would feel too isolated in Malaysia.^[44]

Flight and disappearance[edit]

Known flight path taken by Flight 370 (red), derived from primary (military) and secondary (ATC) radar data.

Flight 370 was a scheduled flight in the early morning of 8 March 2014 from Kuala Lumpur, Malaysia, to Beijing, China. It was one of two daily flights operated by Malaysia Airlines from its hub at Kuala Lumpur International Airport (KLIA) to Beijing Capital International Airport—scheduled to depart at 00:35 local time (MYT; UTC+08:00) and arrive at 06:30 local time (CST; UTC+08:00).^[45][46] On board were 227 passengers, 10 cabin crew, 2 pilots, and 14,296 kg (31,517 lb) of cargo.^{[16]:1, 12, 30}

The planned flight duration was 5 hours and 34 minutes, which would consume an estimated 37,200 kg (82,000 lb) of jet fuel.^{[16]:1, 30} The aircraft carried 49,100 kilograms (108,200 lb) of fuel, including reserves, allowing an endurance of 7 hours and 31 minutes.^{[16]:1, 30} The extra fuel was enough to divert to alternate airports—Jinan Yaoqiang International Airport and Hangzhou Xiaoshan International Airport—which would require 4,800 kg (10,600 lb) or 10,700 kg (23,600 lb), respectively, to reach from Beijing.^[16]:30

Departure[edit]

At 00:42 MYT, Flight 370 took off from runway 32R,^[16]:1 and was cleared by air traffic control (ATC) to climb to flight level 180^[e]—approximately 18,000 feet (5,500 m)—on a direct path to navigational waypoint IGARI (located at 6°56′12″N 103°35′6″E / 6.93667°N 103.58500°E / 6.93667; 103.58500 (Waypoint IGARI)). Voice analysis has determined that the First Officer communicated with ATC while the flight was on the ground and that the Captain communicated with ATC after departure.^[16]:21 Shortly after departure, the flight was transferred from the airport's ATC to "Lumpur Radar" air traffic control on frequency 132.6 MHz. ATC over peninsular Malaysia and adjacent waters is provided by the Kuala Lumpur Area Control Centre (ACC); Lumpur Radar is the name of the frequency used for en route air traffic.^[47] At 00:46, Lumpur Radar cleared Flight 370 to flight level 350^[e]—approximately 35,000 ft (10,700 m). At 01:01, Flight 370's crew reported to Lumpur Radar that they had reached flight level 350, which they confirmed again at 01:08.^{[16]:1–2[48]}

Communication lost[edit]

External video

ATC conversations with Flight 370 Audio recordings of conversations between ATC and Flight 370 from pre-departure to final contact (00:25–01:19).

The aircraft's final automated position report and last transmission, using the Aircraft Communications Addressing and Reporting System (ACARS) protocol, was sent at 01:06 MYT;^{[49]:2[50][51]:36} among the data provided in the message was total fuel remaining—43,800 kg (96,600 lb).^[52]:9 The final verbal signal to air traffic control occurred at 01:19:30, when Captain Shah^[16]:21 acknowledged a transition from Lumpur Radar to Ho Chi Minh ACC:^{[f][16]:2[48][53]}

Lumpur Radar: "Malaysian three seven zero, contact Ho Chi Minh one two zero decimal nine. Good night."

Flight 370: "Good night. Malaysian three seven zero."

The crew was expected to signal air traffic control in Ho Chi Minh City as the aircraft passed into Vietnamese airspace, just north of the point where contact was lost.^[54][55] The captain of another aircraft attempted to signal the crew of Flight 370 "just after [01:30]"^[56] using the international distress frequency to relay Vietnamese air traffic control's request for the crew to contact them; the captain said he was able to establish communication, but only heard "mumbling" and static.^[56] Calls made to Flight 370's cockpit at 02:39 and 07:13 were unanswered but acknowledged by the aircraft's satellite data unit.^{[49]:18[51]:40}

Radar[edit]

Data from Malaysian military radar showing Flight 370 (green) crossing the Strait of Malacca and Andaman Sea to where it was last detected by radar. The left of the two segments of the flight track follows air route N571 between waypoints VAMPI and MEKAR; the white circle appears to highlight a section where the aircraft was not tracked by radar.

At 01:20:31 MYT, Flight 370 was observed on radar at the Kuala Lumpur ACC as it passed the navigational waypoint IGARI (6°56′12″N 103°35′6″E / 6.93667°N 103.58500°E / 6.93667; 103.58500 (Waypoint IGARI)) in the Gulf of Thailand; five seconds later, the Mode-S symbol disappeared from radar screens.^[16]:2 At 01:21:13, Flight 370 disappeared from the radar screen at Kuala Lumpur ACC and was lost about the same time on radar at Ho Chi Minh ACC, which reported that the aircraft was at the nearby waypoint BITOD.^[16]:2[48] Air traffic control uses secondary radar, which relies on a signal emitted by a transponder on each aircraft; therefore, the transponder was no longer functioning on Flight 370 after 01:21. The final transponder data indicated that the aircraft was flying at its assigned cruise altitude of flight level 350^[e] and was travelling at 471 knots (872 km/h; 542 mph) true airspeed.^[57] There were few clouds around this point, and no rain or lightning nearby.^[16]:33–36 Later analysis estimated that Flight 370 had 41,500 kg (91,500 lb) of fuel when it disappeared from secondary radar.^[16]:30

At the time that the transponder stopped functioning, military radar showed Flight 370 turning right, but then^[16]:3 beginning a left turn to a southwesterly direction.^[16]:3 From 01:30:35 until 01:35, military radar showed Flight 370 at 35,700 ft (10,900 m)^[g] on a 231° magnetic heading, with a ground speed of 496 knots (919 km/h; 571 mph).^[16]:3 Flight 370 continued across the Malay Peninsula, fluctuating between 31,000 and 33,000 ft (9,400 and 10,100 m) in altitude.^[16]:3 A civilian primary radar at Sultan Ismail Petra Airport with a 60 nmi (110 km; 69 mi) range made four detections of an unidentified aircraft between 01:30:37 and 01:52:35; the tracks of the unidentified aircraft are "consistent with those of the military data".^{[h][16]:3–4} At 01:52, Flight 370 was detected passing just south of the island of Penang. From there, the aircraft flew across the Strait of Malacca, passing close to the waypoint VAMPI, and Pulau Perak at 02:03, after which it flew along air route N571 to waypoints MEKAR, NILAM, and possibly IGOGU.^{[49]:3, 38} The last known radar detection, from a point near the limits of Malaysian military radar, was at 02:22, 10 nmi (19 km; 12 mi) after passing waypoint MEKAR^{[16]:3, 7} (which is 237 nmi (439 km; 273 mi) from Penang) and 247.3 nmi (458.0 km; 284.6 mi) northwest of Penang airport at an altitude of 29,500 ft (9,000 m).^[58][59]

Countries were reluctant to release information collected from military radar because of sensitivity about revealing their capabilities. Indonesia has an early-warning radar system, but its air traffic control radar did not register any aircraft with the transponder code used by Flight 370, despite the aircraft possibly having flown near, or over, the northern tip of Sumatra.^[16]:4[48] Indonesian military radar tracked Flight 370 earlier when en route to waypoint IGARI before the transponder is thought to have been turned off, but did not provide information on whether it was detected afterwards.^[16]:4[60] Thailand and Vietnam also detected Flight 370 on radar before the transponder stopped working. The radar position symbols for the transponder code used by Flight 370 vanished after the transponder is thought to have been turned off.^[16]:4–5 Thai military radar detected an aircraft that might have been Flight 370, but it is not known what time the last radar contact was made. The signal did not include identifying data.^[61] The flight was also not detected by Australia's conventional^[62] or its long-range JORN over-the-horizon radar system, which has an official range of 3,000 km, the latter not being in operation on the night of the disappearance.^[63]

Satellite communication resumes[edit]

At 02:25 MYT, the aircraft's satellite communication system sent a "log-on request" message—the first message since the ACARS transmission at 01:07—which was relayed by satellite to a ground station, both operated by satellite telecommunications company Inmarsat. After logging on to the network, the satellite data unit aboard the aircraft responded to hourly status requests from Inmarsat and two ground-to-aircraft telephone calls, at 02:39 and 07:13, which were unanswered by the cockpit.^[49]:18[51] The final status request and aircraft acknowledgement occurred at 08:10, about 1 hour and 40 minutes after it was scheduled to arrive in Beijing. The aircraft sent a log-on request at 08:19:29, which was followed, after a response from the ground station, by a "log-on acknowledgement" message at 08:19:37. The log-on acknowledgement is the last piece of data available from Flight 370. The aircraft did not respond to a status request from Inmarsat at 09:15.^{[49][51][64][65]}

Response by air traffic control[edit]

Flight Information Regions in the vicinity of where Flight 370 disappeared from secondary radar. Kuala Lumpur ACC provides ATC services for two routes, located within FIR Singapore, between Malaysia and Vietnam. (Air routes are depicted as roughly 5 nmi / 8–10 km wide, but vary in width, with some as wide as 20 nmi / 35–40 km.)

At 01:38 MYT, Ho Chi Minh Area Control Centre (ACC) contacted Kuala Lumpur Area Control Centre to query the whereabouts of Flight 370 and informed them that they had not established verbal communication with Flight 370, which was last detected by radar at waypoint BITOD. The two centres exchanged four more calls during the next 20 minutes with no new information.^[48][66]

At 02:03, Kuala Lumpur ACC relayed to Ho Chi Minh ACC information received from Malaysia Airlines' operations centre that Flight 370 was in Cambodian airspace. Ho Chi Minh ACC contacted Kuala Lumpur ACC twice in the following eight minutes asking for confirmation that Flight 370 was in Cambodian airspace.^[48] At 02:15, the watch supervisor at Kuala Lumpur ACC queried Malaysia Airlines' operations centre, which said that it could exchange signals with Flight 370 and that Flight 370 was in Cambodian airspace.^[66] Kuala Lumpur ACC contacted Ho Chi Minh ACC to ask whether the planned flight path for Flight 370 passed through Cambodian airspace. Ho Chi Minh ACC responded that Flight 370 was not supposed to enter Cambodian airspace and that they had already contacted Phnom Penh ACC (which controls Cambodian airspace), which had no communication with Flight 370.^[48] Kuala Lumpur ACC contacted Malaysia Airlines' operations centre at 02:34, inquiring about the communication status with Flight 370, and were informed that Flight 370 was in a normal condition based on a signal download and that it was located at 14°54′N 109°15′E / 14.900°N 109.250°E / 14.900; 109.250.^[48][66] Later, another Malaysia Airlines aircraft (Flight 386 bound for Shanghai) attempted, at the request of Ho Chi Minh ACC, to contact Flight 370 on the Lumpur Radar frequency – the frequency on which Flight 370 last made contact with Malaysian air traffic control – and on emergency frequencies. The attempt was unsuccessful.^[48][67]

At 03:30, Malaysia Airlines' operations centre informed Kuala Lumpur ACC that the locations it had provided earlier were "based on flight projection and not reliable for aircraft positioning."^[48] Over the next hour, Kuala Lumpur ACC contacted Ho Chi Minh ACC asking whether they had signalled Chinese air traffic control. At 05:09, Singapore ACC was queried for information about Flight 370. At 05:20, an undisclosed official contacted Kuala Lumpur ACC requesting information about Flight 370; he opined that, based on known information, "MH370 never left Malaysian airspace."^[48]

The watch supervisor at Kuala Lumpur ACC activated the Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) at 05:30, more than four hours after communication was lost with Flight 370.^[66] The ARCC is a command post at an Area Control Centre that coordinates search-and-rescue activities when an aircraft is lost.

Presumed loss[edit]

Malaysia Airlines issued a media statement at 07:24 MYT, one hour after the scheduled arrival time of the flight at Beijing, stating that communication with the flight had been lost by Malaysian ATC at 02:40 and that the government had initiated search-and-rescue operations;^[68] the time when contact was lost was later corrected to 01:21.^[68] Neither the crew nor the aircraft's communication systems relayed a distress signal, indications of bad weather, or technical problems before the aircraft vanished from radar screens.^[69]

On 24 March, Malaysian Prime Minister Najib Razak appeared before media at 22:00 local time to give a statement regarding Flight 370, during which he announced that he had been briefed by the Air Accidents Investigation Branch that it and Inmarsat (the satellite data provider) had concluded that the airliner's last position before it disappeared was in the southern Indian Ocean. As there were no places there where it could have landed, the aircraft must therefore have crashed into the sea.^[70]

Just before Najib spoke at 22:00 MYT, an emergency meeting was called in Beijing for relatives of Flight 370 passengers.^[70] Malaysia Airlines announced that Flight 370 was assumed lost with no survivors. It notified most of the families in person or via telephone, and some received an SMS (in English and Chinese) informing them that it was likely that the aircraft had crashed with no survivors.^{[5][70][71][72]}

On 29 January 2015, the Director General of the Department of Civil Aviation Malaysia, Azharuddin Abdul Rahman, announced that the status of Flight 370 would be changed to an "accident", in accordance with the Chicago Convention on International Civil Aviation, and that all passengers and crew are presumed to have lost their lives.^[73]

If the official assumption is confirmed, Flight 370 was at the time of its disappearance the deadliest aviation incident in the history of Malaysian Airlines, surpassing the 1977 hijacking and crash of Malaysian Airline System Flight 653 that killed all 100 passengers and crew aboard, and the deadliest involving a Boeing 777, surpassing Asiana Airlines Flight 214 (3 fatalities).^[21][22] In both of those categories, Flight 370 was surpassed 131 days later by Malaysia Airlines Flight 17, another Boeing 777-200ER, which was shot down on 17 July 2014, killing all 298 people aboard.^[25]

Reported sightings[edit]

The news media reported several sightings of an aircraft fitting the description of the missing Boeing 777. For example, on 19 March 2014, CNN reported that witnesses, including fishermen, an oil rig worker and people on the Kuda Huvadhoo atoll in the Maldives saw the missing airliner. A fisherman claimed to have seen an unusually-low-flying aircraft off the coast of Kota Bharu; while an oil-rig worker 186 miles (299 km) southeast of Vung Tau claimed he saw a "burning object" in the sky that morning, a claim credible enough for the Vietnamese authorities to send a search-and-rescue mission; and Indonesian fishermen reported witnessing an aircraft crash near the Malacca Straits.^[74] Two days later, the London-based Daily Mail reported that "a Malaysian woman on a flight across the Indian Ocean claimed to have seen an aircraft in the water near the Andaman Islands on the day the jet disappeared".^[75] Three months later, The Daily Telegraph reported that a British woman sailing in the Indian Ocean claimed to have seen an aircraft afire.^[76]

Search[edit]

ADV Ocean Shield deploys the Bluefin-21 autonomous underwater vehicle, which conducted the seafloor sonar survey from 14 April to 28 May.

A search-and-rescue effort was launched in southeast Asia soon after the aircraft's disappearance. Following initial analysis of communications between the aircraft and a satellite, the surface search was moved to the southern Indian Ocean one week after the aircraft's disappearance. Between 18 March and 28 April, nineteen vessels and 345 sorties by military aircraft searched over 4,600,000 km² (1,800,000 sq mi).^[77] The final phase of the search was a bathymetric survey and sonar search of the sea floor, about 1,800 kilometres (970 nmi; 1,100 mi) southwest of Perth, Western Australia.^[78] With effect from 30 March 2014, the search was coordinated by the Joint Agency Coordination Centre (JACC), an Australian government agency established specifically to co-ordinate the search effort to locate and recover Flight 370, which primarily involved the Malaysian, Chinese, and Australian governments.^[79]

On 17 January 2017, the official search for Flight 370, which had proved to be the most expensive search operation of aviation history,^[80][81] was suspended after yielding no evidence of the aircraft apart from some marine debris on the coast of Africa.^{[82][83][84][85]} The final ATSB report, published on 3 October 2017, stated that the underwater search for the aircraft, as of 30 June 2017^[update], had cost a total of US$155 million: the underwater search accounted for 86% of this amount, bathymetry 10% and programme management 4%; Malaysia supported 58% of the total cost, Australia 32%, and China 10%.^[86] The report also concluded that the location where the aircraft went down had been narrowed to 25,000 km², by using satellite images and debris drift analysis.^[87][88]

In January 2018, a private U.S. company named Ocean Infinity resumed the search for MH370 in the narrowed 25,000 km² (9,700 sq mi) area using the Norwegian ship Seabed Constructor.^{[89][90][91][92]} The planned search area of site 1, where the search began, was 33,012 km² (12,746 sq mi), while the extended search area covered a further 48,500 km² (18,700 sq mi).^[91] By the end of May 2018, the vessel had searched over 112,000 km² (43,000 sq mi) of the area using eight autonomous underwater vehicles (AUVs).^[93][94] The contract with the Malaysian government ended soon thereafter and the search was concluded without success on 9 June 2018.^[95]

Southeast Asia[edit]

The initial search area in Southeast Asia

The Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) was activated at 05:30 MYT—four hours after communication was lost with the aircraft—to co-ordinate search and rescue efforts.^[66] Search efforts began in the Gulf of Thailand and South China Sea. On the second day of the search, Malaysian officials said that radar recordings indicated Flight 370 may have turned around; the search zone was expanded to include part of the Strait of Malacca.^[96] On 12 March, the chief of the Royal Malaysian Air Force announced that an unidentified aircraft—believed to be Flight 370—had travelled across the Malay peninsula and was last sighted on military radar 370 km (200 nmi; 230 mi) northwest of the island of Penang; search efforts were subsequently increased in the Andaman Sea and Bay of Bengal.^[59]

Records of signals sent between the aircraft and a communications satellite over the Indian Ocean revealed that the aircraft had continued flying for almost six hours after its final sighting on Malaysian military radar. Initial analysis of these communications determined that Flight 370 was along one of two arcs—equidistant from the satellite—when its last signal was sent; the same day this analysis was disclosed publicly, 15 March, authorities announced they would abandon search efforts in the South China Sea, Gulf of Thailand, and Strait of Malacca to emphasize their efforts on the two corridors. The northern arc—from northern Thailand to Kazakhstan—was soon discounted as the aircraft would have had to pass through heavily militarised airspace and those countries claimed their military radar would have detected an unidentified aircraft entering their airspace.^[97][98][99]

Southern Indian Ocean[edit]

The shifting search zones for Flight 370 in the Southern Indian Ocean. The inset shows the path taken by the vessel ADV Ocean Shield operating a towed pinger locator, acoustic detections, and the sonar search. The underwater phase (both the wide area search and priority area) is shown in pink.

The emphasis of the search was shifted to the Southern Indian Ocean west of Australia and within Australia's aeronautical and maritime Search and Rescue regions that extend to 75°E longitude.^[100][101] Accordingly, on 17 March, Australia agreed to manage the search in the southern locus from Sumatra to the southern Indian Ocean.^[102][103]

Initial search[edit]

From 18–27 March 2014 the search effort focused on a 305,000 km² (118,000 sq mi) area about 2,600 km (1,400 nmi; 1,600 mi) southwest of Perth,^[104] that Australian Prime Minister Tony Abbott said is "as close to nowhere as it's possible to be" and which is renowned for its strong winds, inhospitable climate, hostile seas, and deep ocean floors.^[105][106] Satellite imagery of the region was analysed; several objects of interest and two possible debris fields were identified on images made between 16–26 March. None of these possible objects were found by aircraft or ships.^[107]

Revised estimates of the radar track and the aircraft's remaining fuel led to a move of the search 1,100 km (590 nmi; 680 mi) northeast of the previous area on 28 March,^{[108][109][110]} which was followed by another shift on 4 April.^[111][112] Between 2 and 17 April an effort was made to detect the underwater locator beacons (ULBs; informally known as "pingers") attached to the aircraft's flight recorders, whose batteries were expected to expire around 7 April.^[113][114] Australian naval cutter ADV Ocean Shield equipped with a towed pinger locator (TPL); China's Haixun 01 equipped with a hand-held hydrophone; and the Royal Navy's HMS Echo equipped with a hull-mounted hydrophone; were utilised in the search.^{[49]:11–12[115][113][116][117]} Operators considered it a shot in the dark,^[118] when comparing the vast search area with the fact that a TPL could only search up to 130 km² (50 sq mi) per day.^[118] Between 4–8 April several acoustic detections were made that were close to the frequency and rhythm of the sound emitted by the flight recorders' ULBs; analysis of the acoustic detections determined that, although unlikely, the detections could have come from a damaged ULB.^[49]:13 A sonar search of the sea-floor near the detections was carried out between 14 April and 28 May without any sign of Flight 370.^[49]:14 In a March 2015 report, it was revealed that the calendar life of the battery for the ULB attached to Flight 370's flight data recorder had expired in December 2012 and may not have been as capable.^[119][120]

Underwater search[edit]

Wikimedia Commons has media related to: Search for Malaysia Airlines Flight 370 (category)

In late June 2014, details of the next phase of the search were announced;^[121] officials have called this phase the "underwater search", despite the previous seafloor sonar survey.^[122] Continued refinement of the analysis of Flight 370's satellite communications identified a "wide area search" along the arc where Flight 370 was located when it last communicated with the satellite. The priority search area was in the southern extent of the wide area search.^[123] Some of the equipment used for the underwater search is known to be most effective when towed 200 m (650 ft) above the seafloor at the end of a 9.7 km (6 mi) cable.^[124] Available bathymetric data for this region was of poor resolution, thus necessitating a bathymetric survey of the search area before the underwater phase began.^[125] Commencing in May, the bathymetric survey charted around 208,000 km² (80,000 sq mi) of seafloor through 17 December 2014, when it was suspended so that the ship conducting the survey could be mobilised in the underwater search.^[126]

The governments of Malaysia, China, and Australia agreed to thoroughly search 120,000 km² (46,000 sq mi) of seafloor.^[127] This phase of the search, which began on 6 October 2014,^[123] used three vessels equipped with towed deep-water vehicles that use side-scan sonar, multi-beam echo sounders, and video cameras to locate and identify aircraft debris.^[128] A fourth vessel participated in the search between January–May 2015, using an AUV to search areas that could not be effectively searched using equipment on the other vessels.^{[129][130][131]} Following the discovery of the flaperon on Réunion, the Australian Transport Safety Bureau (ATSB) reviewed its drift calculations for debris from the aircraft and, according to the JACC, was satisfied that the search area was still the most likely crash site.^[132] Reverse drift modelling of the debris, to determine its origin after 16 months, also supported the underwater search area, although reverse drift modelling is very imprecise over long periods.^[132] On 17 January 2017, the three countries jointly announced the suspension of the search for Flight 370.^[82][133]

2018 search[edit]

On 17 October 2017, Malaysia received proposals from three companies, including Dutch-based Fugro and U.S.-based Ocean Infinity, offering to continue the search for the aircraft.^[134] In January 2018, Ocean Infinity announced that it was planning to resume the search in the narrowed 25,000 km² (9,700 sq mi) area. The attempt was approved by the Malaysian government, provided payment would be made only if the wreckage was found.^[89][90] Ocean Infinity chartered the Norwegian ship Seabed Constructor to perform the search.^[92]

Later that month it was reported that the tracking system had detected the vessel reaching the search zone on 21 January, and it started moving to 35°36′S 92°48′E / 35.6°S 92.8°E / -35.6; 92.8 (CSIRO crash area), the most likely crash site according to the drift study by the Commonwealth Scientific and Industrial Research Organisation.^[10] The planned search area of site 1, where the search began, was 33,012 km² (12,746 sq mi), while the extended area covered a further 48,500 km² (18,700 sq mi).^[91] In April, a report by Ocean Infinity revealed that site 4, further northeast along the 7th arc, had been added to the search plan.^[135] As of 29 May 2018^[update], the vessel had searched over 112,000 km² (43,000 sq mi) of the area using eight AUVs;^[93][94] all areas of site 1 (including areas beyond the originally planned search area of site 1), site 2, and site 3 had been searched.^[136] The final phase of the search was conducted in site 4 in May 2018^[136] "before the weather limits Ocean Infinity's ability to continue working this year."^[137] Malaysia's new Transport Minister, Loke Siew Fook, announced on 23 May 2018 that the search for MH370 would conclude at the end of that month,^[138] and Ocean Infinity confirmed on 31 May that the contract with the Malaysian government had ended.^[139][140] On 9 June 2018, it was reported that the search itself had ended.^[95] Ocean floor mapping data collected during the search have been donated to the Nippon Foundation-GEBCO Seabed 2030 Project to be incorporated into the global map of the ocean floor.^[141][142]

Marine debris[edit]

As of October 2017^[update], twenty pieces of debris believed to be from 9M-MRO had been recovered from beaches in the western Indian Ocean.^[143][144] On 16 August 2017, the Australian Transport Safety Bureau released two reports: an analysis of a 23 March 2014 satellite imagery, two weeks after MH370 disappeared, classifying 12 objects in the ocean as "probably man-made",^[145] and a drift study of the recovered objects by the Commonwealth Scientific and Industrial Research Organisation, identifying the crash area "with unprecedented precision and certainty", at 35°36′S 92°48′E / 35.6°S 92.8°E / -35.6; 92.8 (CSIRO crash area), northeast of the main 120,000 km² (46,000 sq mi) underwater search zone.^[146][147]

Flaperon[edit]

Boeing 777 flaperon

Location of flaperon discovery relative to Flight 370's flight path and the main search area.

Currents within the Indian Ocean

The first item of debris identified as coming from Flight 370 was the starboard flaperon (a trailing edge control surface).^{[148][149][150]} It was discovered at the end of July 2015 on a beach in Saint-André, on Réunion, an island in the western Indian Ocean, about 4,000 km (2,200 nmi; 2,500 mi) west of the underwater search area.^[151] It was transported from Réunion—an overseas department of France—to Toulouse, where it was examined by France's civil aviation accident investigation agency, the Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation Civile (BEA), and a French defence ministry laboratory.^[151] Malaysia sent investigators to both Réunion and Toulouse.^[151][152] On 3 September, French officials announced that serial numbers found on internal components of the flaperon link it "with certainty"^[153] to Flight 370. These serial numbers were retrieved via borescope.^{[153][154][155][156][157]}

After discovery of the flaperon, French police performed a search of the waters around Réunion for additional debris,^{[151][158][159]} and came across a damaged suitcase which might be associated with Flight 370.^{[160][needs update]} The location is consistent with models of debris dispersal 16 months after an origin in the current search area, off the west coast of Australia.^{[132][151][161][162]} A Chinese water bottle and an Indonesian cleaning product were found in the same area.^[163][164]

France also conducted an aerial search for possible marine debris around the island, searching an area 120 by 40 km (75 by 25 mi) along the east coast of Réunion.^[159] Foot patrols along beaches to search for debris were also planned.^[165] Malaysia asked authorities in neighbouring states to be on alert for marine debris which could be from an aircraft.^[166] On 14 August, it was announced that no debris that could be related to Flight 370 had been found at sea off Réunion, but that some had been found on land.^[167] Air and sea searches for debris ended on 17 August.^[168]

Parts from the right stabiliser and right wing[edit]

In late February 2016, an object (with a stencilled text "NO STEP" on it) was found off the coast of Mozambique; early photographic analysis suggested it could have come from the aircraft's horizontal stabiliser or the leading edges of the wings.^[6] It was found by Blaine Gibson^[169] on a sandbank in the Mozambique Channel, between Mozambique in eastern Africa and Madagascar; and in the same part of the southern Indian Ocean where the flaperon had been found the previous July.^[170][171] The fragment was sent to Australia where experts identified it as almost certainly a horizontal stabiliser panel from MH370.^[172][173]

In December 2015, Liam Lotter found a grey piece of debris on a beach in southern Mozambique, but only after reading in March 2016 about Gibson's find—some 300 km (190 mi) from his find—did his family alert authorities.^[169] It was flown to Australia for analysis. It carried a stencilled code 676EB, which identified it as part of a Boeing 777 flap track fairing,^[6][174] and the style in which the lettering was painted onto the fairing matched stencils used by Malaysia Airlines, making it almost certain that the part came from 9M-MRO.^{[169][6][8][7][175][9]}

The location where both pieces were retrieved was found to be consistent with the drift model performed by CSIRO,^[7] further corroborating they could have come from Flight 370.

Other debris[edit]

On 7 March 2016, more debris, possibly from the aircraft, was found on the island of Réunion. Ab Aziz Kaprawi, Malaysia's Deputy Transport Minister, said that "an unidentified grey item with a blue border", might be linked to Flight 370. Both Malaysian and Australian authorities, co-ordinating the search in the South Indian Ocean, sent teams to verify whether the debris was from the missing aircraft.^[176][177]

On 21 March 2016, South African archaeologist Neels Kruger found a grey piece of debris on a beach near Mossel Bay, South Africa that has an unmistakable partial logo of Rolls Royce, the manufacturer of the engines of the missing aircraft.^[178] An acknowledgement of a possible part of an engine cowling was made by the Malaysian Ministry of Transport.^[179] An additional piece of possible debris, suggested to have come from the interior of the aircraft, was found on the island of Rodrigues, Mauritius, in late March and was to be examined by Australian authorities.^[180] On 11 May 2016, the authority determined that these two pieces of debris were "almost certainly" from Flight 370.^[181]

Flap and further search[edit]

On 24 June 2016, the Australian Transport Minister, Darren Chester, said that a piece of aircraft debris had been found on Pemba Island, off the coast of Tanzania.^[182] It was handed over to the authorities so that experts from Malaysia could determine whether it was part of the aircraft.^[183] The Australian government released photos of the piece, believed to be an outboard flap from one of the aircraft's wings, on 20 July.^[184] On 15 September, Malaysia's transport ministry confirmed that the debris came from the missing aircraft.^[185]

On 21 November 2016, families of the victims announced that they would search for debris in Madagascar, during December.^[186] On 30 November 2018, five pieces of debris recovered between December 2016 and August 2018 on the coast of Madagascar, and believed by relatives of those on board to be from the doomed plane, were handed to Malaysian Transport Minister Anthony Loke.^[187]

Investigation[edit]

This section needs to be updated. Please update this article to reflect recent events or newly available information. (May 2018)

Final report from Malaysia[edit]

This section contains too-lengthy quotations for an encyclopedic entry. Please help improve the article by presenting facts as a neutrally-worded summary with appropriate citations. Consider transferring direct quotations to Wikiquote. (August 2018)

The final report from the Malaysian Ministry of Transport on the disappearance was released on 30 July 2018.^[188] It did not provide new information concerning the fate of the airplane, but did indicate errors made by Malaysian air traffic controllers in their limited efforts in attempting to communicate with the aircraft.^[189][190] Following the reports of air traffic controllers failings, the Chairman of the Civil Aviation Authority of Malaysia, Azharuddin Abdul Rahman, resigned on 31 July 2018.^{[191][192][193]} As of 2018^[update], France is the only country that continues the investigation (by its Air Transport Gendarmerie) and intends to verify all the technical data transmitted, especially those provided by Inmarsat.^[194]

Section 3.2, Conclusion, of the final report states:

Evidence shows that Flight MH370 diverted from the Filed Flight Plan route. The aircraft's transponder signal ceased for reasons that could not be established and was then no longer visible on the ATC radar display. The changes in the aircraft flight path after the aircraft passed waypoint IGARI were captured by both civilian and military radars. These changes, evidently seen as turning slightly to the right first and then to the left and flying across the Peninsular Malaysia, followed by a right turn south of Penang Island to the north-west and a subsequent (unrecorded) turn towards the Southern Indian Ocean, are difficult to attribute to anomalous system issues alone. It could not be established whether the aircraft was flown by anyone other than the pilots. Later flight simulator trials established that the turn back was likely made while the aircraft was under manual control and not the autopilot.

KL ATSC operation was normal with no significant observation until the handover to Viet Nam ATC. Being the accepting unit, HCM ACC did not notify the transferring unit (KL ATSC) when two-way communication was not established with MH370 within five minutes of the estimated time of the transfer of control point (Establishment of Communications, page 11 of Operational LOA between DCA Malaysia and Vietnam Air Traffic Management effective 1 November 2001). Likewise, KL ATSC should have taken action to contact HCM ACC, instead, relied on position information of the aircraft provided by MAS Flight Operations. By this time, the aircraft had left the range of radars visible to the KL ATSC. It is noted that about one minute elapsed from the last transmission from MH370 and the SSR being lost from the radar display. The Air Traffic Controllers of both Centres did not initiate the various emergency phases as required then, thereby delaying the activation of the alerting and Search and Rescue operations.

The PIC and FO held valid airman licences and medical certification. There is no evidence to suggest that the PIC and FO experienced recent changes or difficulties in personal relationships or that there were any conflicts or problems between them. All the flight and cabin crew were certified fit to fly and were within duty-time limits at the time of the flight and were adequately rested. There had been no financial stress or impending insolvency, recent or additional insurance coverage purchased or recent behavioural changes for the crew. The radio-telephony communications conducted by the PIC and the FO with the Air Traffic Controllers conformed to the routine procedure and no evidence of anxiety or stress was detected in the communications.

The aircraft maintenance records indicated that the aircraft was equipped and maintained in accordance with existing regulations and approved procedures, except for the instance of the SSFDR ULB battery which had expired. The aircraft had a valid Certificate of Airworthiness and was airworthy when released for the flight and there was no record or report of any defect or malfunction in the aircraft that could have contributed to the event. Although it cannot be conclusively ruled out that an aircraft or system malfunction was a cause, based on the limited evidence available, it is more likely that the loss of communications (VHF and HF communications, ACARS, SATCOM and Transponder) prior to the diversion is due to the systems being manually turned off or power interrupted to them or additionally in the case of VHF and HF, not used, whether with intent or otherwise. No ELT signal from the aircraft was reported by the Search and Rescue agencies or any other aircraft. The SATCOM data indicated that the aircraft was airborne for more than 7 hours suggesting that the autopilot was probably functioning, at least in the basic modes, for the aircraft to be flown for such a long duration. This in turn suggests that the air and inertial data were probably available to the autopilot system and/or the crew. The inter-dependency of operation of the various aircraft systems suggests that significant parts of the aircraft electrical power system were likely to be functioning throughout the flight. The analysis of the relevant aircraft systems taking into account the route followed by the aircraft and the height at which it flew, constrained by its performance and range capability, does not suggest a mechanical problem with the aircraft's airframe, control systems, fuel or engines.

Except for the first report, the ACARS reports normally sent every 30 minutes by the SATCOM system were not received. Data from the last seven SATCOM 'handshakes' were used to help establish the approximate path of the aircraft over the Indian Ocean. The initial log-on request and the hourly pings have been termed as 'handshakes'. SATCOM transmissions indicated that a link was available from 1825 UTC on 07 March 2014 to 0011 UTC on 08 March 2014 although not used for any voice, ACARS or other data services apart from two unanswered ground-to-air telephone calls. Two log-ons, at 1825 UTC (07 March 2014) and 0019 UTC (08 March 2014), were initiated by the aircraft most likely due to power interruptions to the SATCOM avionics. The power interruption leading up to 1825 UTC was probably due to power bus cycling, the reason for it being unknown. The power interruption leading up to 0019 UTC was probably due to low fuel at this time resulting in the loss of both engines and their respective generators. There was probably enough fuel for the APU to start up and run long enough for its generator to power the SATCOM avionics to initiate a log-on request.

To date, the main wreckage of MH370 has still not been found despite a 4-year search in the South Indian Ocean. However, items of debris possibly from MH370, have been found as far north as the eastern coast of Tanzania and far south as the eastern coast of South Africa. This is in addition to several islands and island nations off the east coast of the African continent. Of these, the flaperon, a part of the right outboard flap and a section of the left outboard flap were confirmed to be from MH370. A few other pieces of debris were determined to be almost certain from MH370 which included some cabin interior items. Damage examination on the recovered part of the right outboard flap, together with the damage found on the right flaperon has led to the conclusion that the right outboard flap was most likely in the retracted position and the right flaperon was probably at, or close to, the neutral position at the time they separated from the wing. Recovery of the cabin interior debris suggests that the aircraft was likely to have broken up. However, there is insufficient information to determine if the aircraft broke up in the air or during impact with the ocean. Apart from the above, no other information about in-flight emergencies, aircraft configuration or impact could be inferred from the nature and damage of the debris.

MH370 did not carry any cargo classified as dangerous goods. Two cargo items of interest (the Lithium ion Batteries and Mangosteens) which were carried on MH370 had also been transported via scheduled flights on MAS before and after the event. These items were packed and loaded according to standard operating procedures.

As a result of the identified issues, the investigation has issued safety recommendations to enhance the safety of the aviation system. The recommendations made address the Malaysian and foreign air traffic surveillance systems, cargo scanning, flight crew medical and training records, reporting and following-up of crew mental health, flight-following system, development of a Quick Reference for Operations Control and ELT effectiveness.

It should be recognised that there is a significant lack of evidence available to the Team to determine with any certainty the reasons that the aircraft diverted from its filed flight plan route. However, the change in flight path likely resulted from manual inputs. The lack of evidence includes the exact location and disposition of the main aircraft wreckage and the evidence that it could provide, the information recorded on the Flight Data Recorder, Cockpit Voice Recorder and other recording devices on the aircraft and the absence of any aircraft voice or data transmissions that could indicate why the aircraft flew to the Southern Indian Ocean.

Without the benefit of the examination of the aircraft wreckage and recorded flight data information, the investigation was unable to identify any plausible aircraft or systems failure mode that would lead to the observed systems deactivation, diversion from the filed flight plan route and the subsequent flight path taken by the aircraft. However, the same lack of evidence precluded the investigation from definitely eliminating that possibility. The possibility of intervention by a third party cannot be excluded either.

The disappearance of MH370 and the search effort are unprecedented in commercial aviation history. Improvements must be undertaken to ensure that this type of event is identified as soon as possible, and mechanisms are in place to track an aircraft that is not following its filed flight plan for any reason.

In recent years, several States have expended significant amounts of funds and resources searching for missing commercial aircraft in remote oceanic locations, including AF447 and MH370. In this technological epoch, the international aviation community needs to provide assurance to the travelling public that the location of current-generation commercial aircraft is always known. It is unacceptable to do otherwise.

In conclusion, the Team is unable to determine the real cause for the disappearance of MH370.

International participation[edit]

Malaysia set up a Joint Investigation Team (JIT), consisting of specialists from Malaysia, China, the U.K., the U.S., and France,^[49]:1[195] led according to ICAO standards by "an independent investigator in charge".^{[196][197][198]} The team consists of an airworthiness group, an operations group, and a medical and human factors group. The airworthiness group will examine issues related to maintenance records, structures, and systems of the aircraft. The operations group will review flight recorders, operations, and meteorology. The medical and human factors group will investigate psychological, pathological, and survival factors.^[199] Malaysia also announced, on 6 April, that it had set up three ministerial committees—a Next of Kin Committee, a committee to organise the formation of the Joint Investigation Team, and a committee responsible for Malaysian assets deployed in the search effort.^[199] The criminal investigation is being led by the Royal Malaysia Police,^[73]:9 assisted by Interpol and other relevant international law enforcement authorities.^[200][201]

On 17 March, Australia took control for co-ordinating search, rescue, and recovery operations. For the following six weeks, the Australian Maritime Safety Authority (AMSA) and ATSB worked to determine the search area, correlating information with the JIT and other government and academic sources, while the Joint Agency Coordination Centre (JACC) coordinated the search efforts. Following the fourth phase of the search, the ATSB took responsibility for defining the search area. In May, the search strategy working group was established by the ATSB to determine the most likely position on the aircraft at the 00:19 UTC (08:19 MYT) satellite transmission. The group included aircraft and satellite experts from: Air Accidents Investigation Branch (UK), Boeing (US), Defence Science and Technology Group^[i] (Australia), Department of Civil Aviation (Malaysia), Inmarsat (UK), National Transportation Safety Board (US), and Thales (UK).^{[49]:1[203][204]}

The Malaysian Ministry of Transport issued an interim report entitled "Factual Information: Safety Information for MH370" on 8 March 2015. As suggested by the report's title, it focused on providing factual information and not analysis of possible causes of the disappearance.^[205] A brief update statement was provided in March 2016 regarding the status of the investigation.^[206] The final ATSB report was published 3 October 2017.^[86]

Analysis of satellite communication[edit]

The communications between Flight 370 and the satellite communication network operated by Inmarsat, which were relayed by the Inmarsat-3 F1 satellite, provide the only significant clues to the location of Flight 370 after disappearing from Malaysian military radar at 02:22 MYT. These communications have also been used to deduce possible in-flight events (see next section). The investigative team was challenged with reconstructing the flight path of Flight 370 from a limited set of transmissions with no explicit information about the aircraft's location, heading, or speed.^{[49]:16–17[207]}

Background[edit]

A depiction of an Inmarsat-3 series satellite. Flight 370 was in contact with Inmarsat-3 F1 (also known as "IOR" for Indian Ocean Region).

Aeronautical satellite communication (SATCOM) systems are used to transmit messages from the aircraft cockpit, as well as automated messages from on-board systems using the ACARS communications protocol, but may also be used to transmit FANS and ATN messages and provide voice, fax and data links^[208] using other protocols.^{[207][209][210]} The aircraft's satellite data unit (SDU) is used to send and receive signals with the satellite communications network; it operates independently from other aircraft equipment that communicate through the SATCOM system, many using the ACARS protocol. Signals from the SDU are relayed by a satellite, which simply changes the signal's frequency, and then received by a ground station, which processes the signal and, if applicable, routes it to its destination (e.g., Malaysia Airlines' operations centre); signals to the aircraft are sent in reverse order. When the SDU is powered on and attempts to connect with the Inmarsat network, it transmits a log-on request, which the ground station acknowledges.^[49]:17[210] This is, in part, to determine that the SDU belongs to an active service subscriber and also used to determine which satellite should be used to transmit messages to the SDU.^[210] After connecting, if a ground station has not received any contact from a terminal for one hour,^[j] the ground station will transmit a "log-on interrogation" message, informally referred to as a "ping";^[49]:18 an active terminal responds automatically. The entire process of interrogating the terminal is referred to as a "handshake".^[64][211]

Communications from 02:25 to 08:19 MYT[edit]

Although the ACARS data link on Flight 370 stopped functioning between 01:07 and 02:03 MYT (most likely around the same time the plane lost contact by secondary radar),^[51]:36 the SDU remained operative.^[49] After last contact by primary radar west of Malaysia, the following events were recorded in the log of Inmarsat's ground station at Perth, Western Australia (all times are MYT/UTC+8):^{[49]:18[51][k]}

• 02:25:27 – First handshake ("log-on request" initiated by aircraft)
• 02:39:52 – Ground to aircraft telephone call, acknowledged by SDU, unanswered
• 03:41:00 – Second handshake (initiated by ground station)
• 04:41:02 – Third handshake (initiated by ground station)
• 05:41:24 – Fourth handshake (initiated by ground station)
• 06:41:19 – Fifth handshake (initiated by ground station)
• 07:13:58 – Ground to aircraft telephone call, acknowledged by SDU, unanswered
• 08:10:58 – Sixth handshake (initiated by ground station)
• 08:19:29 – Seventh handshake (initiated by aircraft); widely reported as a "partial handshake'", consisting of the following two transmissions:^[51]

• 08:19:29.416 – "log-on request" message transmitted by aircraft (seventh "partial" handshake)
• 08:19:37.443 – "log-on acknowledge" message transmitted by aircraft (last transmission received from Flight 370)

The aircraft did not respond to a ping at 09:15.^[51]

Deductions[edit]

A few deductions can be made from the satellite communications. The first is that the aircraft remained operational until at least 08:19 MYT—seven hours after final contact was made with air traffic control over the South China Sea. The varying burst frequency offset (BFO) values indicate the aircraft was moving at speed. The aircraft's SDU needs location and track information to keep its antenna pointed towards the satellite, so it can also be deduced that the aircraft's navigation system was operational.^[212]:4

Since the aircraft did not respond to a ping at 09:15, it can be concluded that at some point between 08:19 and 09:15, the aircraft lost the ability to communicate with the ground station.^{[64][65][211]} The log-on message sent from the aircraft at 08:19:29 was "log-on request".^[49]:22 There are only a few reasons the SDU would transmit a log-on request, such as a power interruption, software failure, loss of critical systems providing input to the SDU, or a loss of the link due to the aircraft's attitude.^[49]:22 Investigators consider the most likely reason to be that it was sent during power-up after an electrical outage.^[49]:33 At 08:19, the aircraft had been airborne for 7 h 38 min; the typical Kuala Lumpur-Beijing flight is 5​¹⁄₂ hours, so fuel exhaustion was likely.^{[49]:33[49]:33[213]} In the event of fuel exhaustion and engine flame-out, which would eliminate power to the SDU, the aircraft's ram air turbine (RAT) would deploy, providing power to some instruments and flight controls, including the SDU.^[49]:33 Approximately 90 seconds after the 02:25 handshake—also a log-on request—communications from the aircraft's inflight entertainment system were recorded in the ground station log. Similar messages would be expected following the 08:19 handshake, but none were received, supporting the fuel-exhaustion scenario.^[49]:22

Analysis[edit]

A heat map indicating the probable location of missing Flight 370 based on a Bayesian method analysis of possible flight paths by Australia's Defence Science and Technology Group.^[214]

Two parameters associated with these transmissions that were recorded in a log at the ground station were key to the investigation:

• Burst time offset (BTO) – the time difference between when a signal is sent from the ground station and when the response is received. This measure is proportional to twice the distance from the ground station via the satellite to the aircraft and includes the time that the SDU takes between receiving and responding to the message and time between reception and processing at the ground station. This measure was analysed to determine the distance between the satellite and the aircraft at the time each of the seven handshakes occurred, and thereby defining seven circles on the Earth's surface the points on whose circumference are equidistant from the satellite at the calculated distance. Those circles were then reduced to arcs by eliminating those parts of each circle that lay outside the aircraft's range.^{[49]:18[212]:4–6}
• Burst frequency offset (BFO) – the difference between the expected and received frequency of transmissions. The difference is caused by Doppler shifts as the signals travelled from the aircraft to the satellite to the ground station; the frequency translations made in the satellite and at the ground station; a small, constant error (bias) in the SDU that results from drift and ageing; and compensation applied by the SDU to counter the Doppler shift on the uplink. This measure was analysed to determine the aircraft's speed and heading, but multiple combinations of speed and heading can be valid solutions.^{[49]:18[212]:9–11}

By combining the distance between the aircraft and satellite, speed, and heading with aircraft performance constraints (e.g. fuel consumption, possible speeds and altitudes), investigators generated candidate paths that were analysed separately by two methods. The first assumed the aircraft was flying on one of the three autopilot modes (two are further affected by whether the navigation system used magnetic north or true north as a reference), calculated the BTO and BFO values along these routes, and compared them with the values recorded from Flight 370. The second method generated paths which had the aircraft's speed and heading adjusted at the time of each handshake to minimise the difference between the calculated BFO of the path and the values recorded from Flight 370.^{[49]:18, 25–28[52]:10–11} A probability distribution for each method at the BTO arc of the sixth handshake of the two methods was created and then compared; 80% of the highest probability paths for both analyses combined intersect the BTO arc of the sixth handshake between 32.5°S and 38.1°S, which can be extrapolated to 33.5°S and 38.3°S along the BTO arc of the seventh handshake.^[52]:12

Possible in-flight events[edit]

Power interruption[edit]

The SATCOM link functioned normally from pre-flight (beginning at 00:00 MYT) until it responded to a ground-to-air ACARS message with an acknowledge message at 01:07. Ground-to-air ACARS messages continued to be transmitted to Flight 370 until Inmarsat's network sent multiple "Request for Acknowledge" messages at 02:03, without a response from the aircraft. At some time between 01:07 and 02:03, power was lost to the SDU. At 02:25, the aircraft's SDU sent a "log-on request".^{[49]:22[51]:36–39} It is not common for a log-on request to be made in-flight, but it could occur for multiple reasons. An analysis of the characteristics and timing of these requests suggest a power interruption in-flight is the most likely culprit.^[49]:33[215] As the power interruption was not due to engine flame-out, per ATSB, it may have been the result of manually switching off the aircraft's electrical system.^[49]:33

Unresponsive crew or hypoxia[edit]

An analysis by the ATSB comparing the evidence available for Flight 370 with three categories of accidents—an in-flight upset (e.g., stall), a glide event (e.g., engine failure, fuel exhaustion), and an unresponsive crew or hypoxia event—concluded that an unresponsive crew or hypoxia event "best fit the available evidence"^[49]:34 for the five-hour period of the flight as it travelled south over the Indian Ocean without communication or significant deviations in its track,^[49]:34 likely on autopilot.^[216][217] No consensus exists among investigators on the unresponsive crew or hypoxia theory.^[218] If no control inputs were made following flameout and the disengagement of autopilot, the aircraft would likely have entered a spiral dive^[49]:33 and entered the ocean within 20 nmi (37 km; 23 mi) of the flameout and disengagement of autopilot.^[49]:35 The analysis of the flaperon showed that the landing flaps were not extended, supporting the spiral dive at high speed theory.^[219] In May 2018, the ATSB again asserted that the flight was not in control when it crashed, its spokesperson adding that "We have quite a bit of data to tell us that the aircraft, if it was being controlled at the end, it wasn't very successfully being controlled." This was in reaction to speculation by Canadian former air crash investigator Larry Vance in his recent book that the cause was pilot suicide.^[220]

Possible causes of disappearance[edit]

Passenger involvement[edit]

Two men boarded Flight 370 with stolen passports, which raised suspicion in the immediate aftermath of its disappearance.^[221][222] The passports, one Austrian and one Italian, were reported stolen in Thailand within the preceding two years.^[221] Interpol stated that both passports were listed on its database of lost and stolen passports and that no check had been made against its database.^[223][224] Malaysia's Home Minister, Ahmad Zahid Hamidi, criticised his country's immigration officials for failing to stop the passengers travelling with the stolen European passports.^[224] The two one-way tickets purchased for the holders of the stolen passports were booked through China Southern Airlines.^[221] It was reported that an Iranian had ordered the cheapest tickets to Europe via telephone in Bangkok, Thailand, and paid by cash.^[225][226] The two passengers were later identified as Iranian men, one aged 19 and the other 29, who had entered Malaysia on 28 February using valid Iranian passports. The Secretary General of Interpol said the organisation was "inclined to conclude that it was not a terrorist incident".^[31] The two men were believed to be asylum seekers.^[227][228]

United States and Malaysian officials were reviewing the backgrounds of every passenger named on the manifest.^[36] On 18 March, the Chinese government announced that it had checked all of the Chinese citizens on the aircraft and ruled out the possibility that any were involved in "destruction or terror attacks".^[229] One passenger who worked as a flight engineer for a Swiss jet charter company was briefly suspected as a potential hijacker because he was thought to have the relevant skill set.^[230]

Crew involvement[edit]

U.S. intelligence officers believe the most likely explanation was that someone in the cockpit of Flight 370 re-programmed the aircraft's autopilot to travel south across the Indian Ocean.^[231][232] Police searched the homes of the pilots and seized financial records for all 12 crew members, including bank statements, credit card bills and mortgage documents.^[233][234] On 2 April 2014, Malaysia's Police Inspector-General said that more than 170 interviews had been conducted as part of Malaysia's criminal investigation, including interviews with family members of the pilots and crew.^[235][236]

Media reports have claimed that Malaysian police have identified Captain Shah as the prime suspect if human intervention is proven to be the cause of Flight 370's disappearance.^{[237][238][239][240]} The United States' Federal Bureau of Investigation (FBI) reconstructed the deleted data from Captain Shah's home flight simulator; a Malaysian government spokesman indicated that "nothing sinister"^[241] had been found on it.^[241][242] The preliminary report issued by Malaysia in March 2015 stated that there was "no evidence of recent or imminent significant financial transactions carried out"^[16]:20 by any of the pilots or crew and that analysis of the behaviour of the pilots on CCTV showed "no significant behavioural changes".^[16]

In 2016 a leaked American document stated that a route on the pilot's home flight simulator closely matching the projected flight over the Indian Ocean was found during the FBI analysis of the hard drive of the computer used for the flight simulator.^[243] This was later confirmed by the ATSB, although it stressed that this did not prove the pilot's involvement.^[244] It was similarly confirmed by the Malaysian government.^[245]

In 2018 the sister of the pilot said the safety investigation report on MH370 showed "nothing negative"^[246] about the pilot flying the plane.^{[247][248][249]} According to the report, "There were seven 'manually programmed' waypoint coordinates, that when connected together, will create a flight path from KLIA to an area south of the Indian Ocean through the Andaman Sea. But a forensic report concluded there were no unusual activities other than game-related flight simulations." They were dated 3 February 2014 but could have originated from different files.^[250]

Cargo[edit]

Flight 370 was carrying 10,806 kg (23,823 lb) of cargo, of which four ULDs of mangosteens and 221 kg (487 lb) of lithium-ion batteries are of interest, according to Malaysian investigators.^{[16]:103, 108–109} The four ULDs of mangosteens were loaded into the aft cargo bay of the aircraft.^[16]:106 The lithium-ion batteries were divided among two pallets in the forward cargo bay and one pallet placed in the rear of the aft cargo bay.^[16]:106

The lithium-ion batteries were contained in a 2,453 kg (5,408 lb) consignment being transported between Motorola Solutions facilities in Bayan Lepas, Malaysia, and Tianjin, China; the rest of the consignment consisted of walkie-talkie chargers and accessories.^[16]:103 The batteries were assembled on 7 March and transported to the Penang Cargo Complex to be transported by MASkargo—Malaysia Airlines' cargo subsidiary—to be loaded onto a lorry to transport it to Kuala Lumpur International Airport and onwards by air to Beijing.^[16]:104 At the Penang Cargo Complex, the consignment was inspected by MASkargo employees and Malaysian customs officials, but did not go through a security screening before the truck was sealed for transfer to the airport.^[16]:104 The consignment did not go through any additional inspections at Kuala Lumpur International Airport before it was loaded onto Flight 370.^[16]:104 Because the batteries were packaged in accordance with IATA guidelines,^[l] they were not regulated as dangerous goods.^[16]:106 Lithium-ion batteries can cause intense fires if they overheat and ignite, which has led to strict regulations on their transport aboard aircraft.^[251][252] A fire fuelled by lithium-ion batteries caused the crash of UPS Airlines Flight 6, and lithium-ion batteries are suspected to have caused a fire which resulted in the crash of Asiana Airlines Flight 991; both were cargo aircraft.^{[252][253][254]} Some airlines have stopped carrying bulk shipments of lithium-ion batteries on passenger aircraft, citing safety concerns.^[252][253]

A 4,566 kg (10,066 lb) consignment of mangosteens was aboard Flight 370.^[16]:107 The mangosteens were loaded into four ULDs at Kuala Lumpur International Airport, and inspected by officials from Malaysia's Federal Agriculture Marketing Authority before being loaded onto Flight 370.^[16]:108 According to the head of Malaysian police, Khalid Abu Bakar, the people who handled the mangosteens and the Chinese importers were questioned to rule out sabotage.^[255]

Aftermath[edit]

Information sharing[edit]

Public communication from Malaysian officials regarding the loss of the flight was initially beset with confusion.^[m] The Malaysian government and the airline released imprecise, incomplete, and sometimes inaccurate information, with civilian officials sometimes contradicting military leaders.^[269] Malaysian officials were criticised for such persistent release of contradictory information, most notably regarding the last location and time of contact with the aircraft.^[270]

Although Malaysia's acting Transport Minister Hishammuddin Hussein, who is also the country's Defence Minister, denied the existence of problems between the participating countries, academics said that because of regional conflicts, there were genuine trust issues involved in co-operation and sharing intelligence, and that these were hampering the search.^[271][272] International relations experts said entrenched rivalries over sovereignty, security, intelligence, and national interests made meaningful multilateral co-operation very difficult.^[271][272] A Chinese academic made the observation that the parties were searching independently; thus it was not a multilateral search effort.^[272] The Guardian noted the Vietnamese permission given for Chinese aircraft to overfly its airspace as a positive sign of co-operation.^[272] Vietnam temporarily scaled back its search operations after the country's Deputy Transport Minister cited a lack of communication from Malaysian officials despite requests for more information.^[273] China, through the official Xinhua News Agency, said that the Malaysian government ought to take charge and conduct the operation with greater transparency, a point echoed by the Chinese Foreign Ministry days later.^[271][274]

Malaysia had initially declined to release raw data from its military radar, deeming the information "too sensitive",^[271] but later acceded.^[271][272] Defence experts suggested that giving others access to radar information could be sensitive on a military level, for example: "The rate at which they can take the picture can also reveal how good the radar system is."^[271] One suggested that some countries could already have had radar data on the aircraft, but were reluctant to share any information that could potentially reveal their defence capabilities and compromise their own security.^[271] Similarly, submarines patrolling the South China Sea might have information in the event of a water impact, and sharing such information could reveal their locations and listening capabilities.^[275]

Criticism was also levelled at the delay of the search efforts. On 11 March, three days after the aircraft disappeared, British satellite company Inmarsat (or its partner, SITA) had provided officials with data suggesting the aircraft was nowhere near the areas in the Gulf of Thailand and the South China Sea being searched at that time, and may have diverted its course through a southern or northern corridor. This information was publicly acknowledged and released by Najib only on 15 March in a press conference.^[207][276] Explaining why information about satellite signals had not been made available earlier, Malaysia Airlines said that the raw satellite signals needed to be verified and analysed "so that their significance could be properly understood" before it could publicly confirm their existence.^[68] Hishammuddin said that Malaysian and US investigators had immediately discussed the Inmarsat data upon receiving them on 12 March, and on two occasions, both groups agreed that it needed further processing and sent the data to the US twice for this purpose. Data analysis was completed on 14 March: by then, the AAIB had independently arrived at the same conclusion.^[277]

In June 2014, relatives of passengers on Flight 370 began a crowdfunding campaign on Indiegogo to raise US$100,000—with an ultimate goal of raising US$5 million—as a reward to encourage anyone who knows the location of Flight 370 or the cause of its disappearance to reveal what they know.^[278][279] The campaign, which ended 8 August 2014, raised US$100,516 from 1007 contributors.^[278]

Malaysia Airlines[edit]

A month after the disappearance, Malaysia Airlines' chief executive Ahmad Jauhari Yahya acknowledged that ticket sales had declined but failed to provide specific details. This may have partially resulted from the suspension of the airline's advertising campaigns following the disappearance. Ahmad stated in an interview with the Wall Street Journal that the airline's "primary focus...is that we do take care of the families in terms of their emotional needs and also their financial needs. It is important that we provide answers for them. It is important that the world has answers, as well."^[280] In further remarks, Ahmad said he was not sure when the airline could start repairing its image, but that the airline was adequately insured to cover the financial loss stemming from Flight 370's disappearance.^[280][281] In China, where the majority of passengers were from, bookings on Malaysia Airlines were down 60% in March.^[282]

Malaysia Airlines retired the Flight 370 (MH370) flight number and replaced it with Flight 318 (MH318) beginning 14 March. This follows a common practice among airlines to rename flights following notorious accidents.^[283][284] The flight—Malaysia Airline's second daily flight to Beijing—was later suspended beginning 2 May; according to insiders, this was due to lack of demand.^[46][285]

Malaysia Airlines was given US$110 million from insurers in March 2014 to cover initial payments to passengers' families and the search effort.^[286] In May, remarks from lead reinsurer of the flight, Allianz, indicated the insured market loss on Flight 370, including the search, was about US$350 million.^[287][288]

Financial troubles[edit]

At the time of Flight 370's disappearance, Malaysia Airlines was struggling to cut costs to compete with a wave of new, low-cost carriers in the region. In the previous three years, Malaysia Airlines had booked losses of: RM1.17 billion (US$356 million) in 2013, RM433 million in 2012, and RM2.5 billion in 2011.^[280] Malaysia Airlines lost RM443.4 million (US$137.4 million) in the first quarter of 2014 (January–March).^[281] The second quarter—the first full quarter in the aftermath of Flight 370's disappearance—saw a loss of RM307.04 million (US$97.6 million), which represented a 75-percent increase over losses from the second quarter of 2013.^[289] Industry analysts expected Malaysia Airlines to lose further market share and face a challenging environment to stand out from competitors while addressing its financial plight.^[280] The company's stock, down as much as 20 percent following the disappearance of Flight 370, had fallen 80% over the previous five years, which contrasted with a rise in the Malaysian stock market of about 80% over the same period.^[282]

Many analysts and the media suggested that Malaysia Airlines would need to rebrand and repair its image and/or require government assistance to return to profitability.^{[290][291][292][293][294]} The loss of Flight 17 in July greatly exacerbated Malaysia Airline's financial problems. The combined effect on consumer confidence of the loss of Flight 370 and Flight 17, and the airline's poor financial performance, led Khazanah Nasional—the majority shareholder (69.37%)^[295] and a Malaysian state-run investment arm—to announce on 8 August its plan to purchase the remainder of the airline, thereby renationalising it.^{[296][297][298]}

Compensation for passengers' next-of-kin[edit]

Lack of evidence in determining the cause of Flight 370's disappearance, even physical evidence that the aircraft crashed, raises many issues regarding responsibility for the accident and payments made by insurance agencies.^[299] Under the Montreal Convention, it is the carrier's responsibility to prove lack of fault in an accident and each passenger's next-of-kin are automatically entitled, regardless of fault, to a payment of approximately US$175,000^[n] from the airline's insurance company—a total of nearly US$40 million for the 227 passengers on board.^[299]

Malaysia Airlines would still be vulnerable to civil lawsuits from passengers' families.^[299] Compensation awarded (or settlements reached out-of-court) during civil trials will likely vary widely among passengers based on country of the court. An American court could likely award upwards of US$8–10 million, while Chinese courts would likely award a small fraction of that.^[300][301] Despite the announcement that Flight 370 ended in the southern Indian Ocean, it was not until 29 January 2015 that the Malaysian government officially declared Flight 370 an accident with no survivors, a move that would allow compensation claims to be made.^[302] The first lawsuit related to the disappearance was filed in October 2014—before Flight 370 was declared an accident—on behalf of two Malaysian boys whose father was a passenger,^[o] for negligence in failing to contact the aircraft soon after it was lost and for breach of contract for failing to bring the passenger to his destination.^[305] Additional lawsuits against Malaysia Airlines have been filed in China and Malaysia.^[306]

Malaysia Airlines offered ex gratia condolence payments soon after the disappearance. In China, families of passengers were offered ¥31,000 (about US$5,000) "comfort money";^[307] but some families rejected the offer.^[308] It was also reported that Malaysian relatives received only $2,000.^[308] In June, Malaysia's deputy Foreign Minister Hamzah Zainuddin said that families of seven passengers received $50,000 advance compensation from Malaysia Airlines,^[309] but that full payout would come after the aircraft was found or officially declared lost^[310] (which later occurred in January 2015).^[302]

Malaysia[edit]

Messages for MH370 at a bookshop in Malaysia

Air force experts raised questions and the Malaysian opposition leveled criticisms about the state of Malaysia's air force and radar capabilities. Many criticised the failure of the Royal Malaysian Air Force to identify and respond to an unidentified aircraft (later determined to be Flight 370) flying through Malaysian airspace.^{[311][312][313][314]} The Malaysian military became aware of the unidentified aircraft only after reviewing radar recordings several hours after the flight's disappearance.^[313] The failure to recognise and react to the unidentified aircraft was a security breach, and was also a missed opportunity to intercept Flight 370 and prevent the time-consuming and expensive search operation.^[313][314]

The Malaysian Prime Minister, Najib Razak, responded to criticism of his government in an opinion piece published in The Wall Street Journal in which he acknowledged mistakes had been made, and said time would show that Malaysia had done its best, had helped co-ordinate the search, and would continue to support.^[315] Najib went on to emphasise the need for the aviation industry to "not only learn the lessons of MH370 but implement them," saying in closing that "the world learned from [Air France Flight 447] but didn't act. The same mistake must not be made again."^[315]

Opposition leader Anwar Ibrahim criticised the Malaysian government regarding its response to Flight 370's disappearance and the military's response when Flight 370 turned back over the Malay Peninsula; he called for an international committee to take charge of the investigation "to save the image of the country and to save the country."^[316] Malaysian authorities have accused Anwar—who was jailed on contentious charges the day before Flight 370 disappeared—of politicising the crisis. Flight 370's captain was a supporter of Anwar and the two knew each other.^[316]

Questioned about why Malaysia did not scramble fighter jets to intercept the aircraft as it tracked back across the Malay Peninsula, Defence Minister Hishammuddin Hussein noted that it was deemed a commercial aircraft and was not hostile, remarking: "If you're not going to shoot it down, what's the point of sending [a fighter jet] up?"^[317]

The response to the crisis and lack of transparency in the response brought attention to the state of media in Malaysia. After decades of having tight control of media, during which government officials were accustomed to passing over issues without scrutiny or accountability, Malaysia was suddenly thrust to the forefront of global media and unable to adjust to demands for transparency.^[318]

On the second anniversary of the disappearance, 8 March 2016, Najib said that he was hopeful that the missing Flight 370 would be found. The Malaysian Parliament observed a moment of silence to mark the anniversary. Najib said that the search had been "the most challenging in aviation history", but that he remained committed to completing it.^[319]

China[edit]

Chinese Deputy Foreign Minister Xie Hangsheng reacted sceptically to the conclusion by the Malaysian government that the aircraft had gone down with no survivors, demanding on 24 March 2014 "all the relevant information and evidence about the satellite data analysis", and said that the Malaysian government must "finish all the work including search and rescue."^[320][321] The following day, Chinese president Xi Jinping sent a special envoy to Kuala Lumpur to consult with the Malaysian government over the missing aircraft.^[322]

Relatives of passengers[edit]

On 25 March 2014, around two hundred family members of the Chinese passengers protested outside the Malaysian embassy in Beijing.^[323][324] Relatives who had arrived in Kuala Lumpur after the announcement continued with their protest, accusing Malaysia of hiding the truth and harbouring a murderer. They also wanted an apology for the Malaysian government's poor initial handling of the disaster and its "premature" conclusion of loss, drawn without physical evidence.^[325] An op-ed for China Daily said that Malaysia was not wholly to be blamed for its poor handling of such a "bizarre"^[326] and "unprecedented crisis,"^[326] and appealed to Chinese people not to allow emotions to prevail over evidence and rationality.^[326] The Chinese ambassador to Malaysia defended the Malaysian government's response, stating that the relatives' "radical and irresponsible opinions do not represent the views of Chinese people and the Chinese government".^[327] The ambassador also strongly criticised Western media for having "published false news, stoked conflict and even spread rumours"^[328] to the detriment of relatives and of Sino–Malaysian relations.^[328] On the other hand, a US Department of Defense official criticised China for what he perceived as providing apparently false leads that detracted from the search effort and wasted time and resources.^[329][330]

On 7 March 2016, the day before the second anniversary of the disappearance, twelve Chinese families with relatives on board the missing aircraft filed a lawsuit in Beijing, one day before the deadline for pursuing litigation against the carrier. In Kuala Lumpur, lawyer Ganesan Nethi reported that he had filed a joint lawsuit on behalf of the families of 32 passengers on 3 March 2016, explaining that most were Chinese, along with an American and a few Indians.^[331]

Boycotts[edit]

Some Chinese boycotted all things Malaysian, including holidays and singers, in protest of Malaysia's handling of the Flight 370 investigation.^[332][333] Bookings on Malaysia Airlines from China, where the majority of passengers were from, were down 60% in March.^[282] In late March, several major Chinese ticketing agencies—eLong, LY.com, Qunar and Mango—discontinued the sale of airline tickets to Malaysia^[332][334] and several large Chinese travel agencies reported a 50-percent drop in tourists compared to the same period the year before.^[285] China was the third largest source of visitors to Malaysia prior to Flight 370's disappearance, accounting for 1.79 million tourists in 2013.^[285] One market analyst predicted a 20–40% drop in Chinese tourists to Malaysia, resulting in a loss of 4–8 billion yuan (RM2.1–4.2 billion; US$0.65–1.3 billion).^[285][335]

The boycotts were largely led or supported by celebrities.^[285][336] Film star Chen Kun posted a message to Weibo—where he had 70 million followers—stating that he would be boycotting Malaysia until its government told the truth.^[285] The post was shared over 70,000 times and drew over 30,000 comments.^[285] Over 337,000 people retweeted a tweet from TV host Meng Fei, that said he would join the boycott.^[285]

China and Malaysia had previously nominated 2014 to be the "Malaysia–China Friendship Year" to celebrate 40 years of diplomatic relations between the two countries.^[334]

Air transport industry[edit]

The fact that, in a digitally-connected world, a modern aircraft could disappear was met with surprise and disbelief by the public. While changes in the aviation industry often take years to be implemented, airlines and air transport authorities responded swiftly to take action on several measures to reduce the likelihood of a similar incident.^{[337][338][339][340]}

Aircraft tracking[edit]

The International Air Transport Association (IATA)—an industry trade organisation representing over 240 airlines (representing 84% of global air traffic)—and the International Civil Aviation Organization (ICAO)—the United Nations' civil aviation body—began working on implementing new measures to track aircraft in flight in real time.^[341] The IATA created a task force (which included several outside stakeholders)^[341] to define a minimal set of requirements that any tracking system must meet, allowing airlines to decide the best solution to track their aircraft. The IATA's task force planned to come up with several short-, medium-, and long-term solutions to ensure that information is provided in a timely manner to support search, rescue, and recovery activities in the wake of an aircraft accident.^[342] The task force was expected to provide a report to the ICAO on 30 September 2014, but on that day said that the report would be delayed, citing the need for further clarification on some issues.^[343][344] In December 2014, the IATA task force recommended that, within 12 months, airlines track commercial aircraft in no longer than 15-minute intervals. The IATA itself did not support the deadline, which it believed could not be met by all airlines, but the proposed standard had the support of the ICAO. Although the ICAO can set standards, it has no legal authority and such standards must be adopted by member states.^[345][346]

In 2016, the ICAO adopted a standard that, by November 2018, all aircraft over open ocean report their position every 15 minutes.^[347] In March, the ICAO approved an amendment to the Chicago Convention requiring new aircraft manufactured after 1 January 2021 to have autonomous tracking devices which could send location information at least once per minute in distress circumstances.^[347][348]

In May 2014, Inmarsat said that it would offer its tracking service for free to all aircraft equipped with an Inmarsat satellite connection (which amounts to nearly all commercial airliners).^[349] Inmarsat also changed the time period for handshakes with its terminals from one hour to 15 minutes.^[212]:2

Transponders[edit]

There was a call for automated transponders after the 11 September 2001 terrorist attacks; no changes were made, as aviation experts preferred flexible control, in case of malfunctions or electrical emergencies.^[350] In the wake of Flight 370, the air transport industry was still resistant to the installation of automated transponders, which would likely entail significant costs. Pilots also criticised changes of this kind, insisting on the need to cut power to equipment in the event of a fire. Nonetheless, new types of tamper-proof circuit breakers were being considered.^[339]

Flight recorders[edit]

Detection of the acoustic signal from the ULBs must be made below the thermocline and within a maximum range, under nominal conditions, of 2,000–3,000 m (6,600–9,800 ft). With a ULB battery life of 30–40 days, searching for the important flight recorders is very difficult without precise coordinates of the location the aircraft entered the water.

The frenzied search for the flight recorders in early April 2014, due to the 30-day battery life of the underwater locator beacons (ULBs) attached to them, brought attention to the limitations of the ULBs.^[p][351] The distance the signal from the ULBs can be detected from is 2,000–3,000 m (6,600–9,800 ft), or 4,500 m (14,800 ft) under favourable conditions.^[49]:11 Even if the flight recorders are located, the cockpit voice recorder memory has capacity to store only two hours of data, continuously recording over the oldest data. This length complies with regulations and it is usually only data from the last section of a flight that are needed to determine the cause of an accident. The events which caused Flight 370 to divert from its course and disappear happened more than two hours before the flight ended.^[352] Given these limitations and the importance of the data stored on flight recorders, Flight 370 has brought attention to new technologies that enable data streaming to the ground.^[353][354]

A call to increase the battery life of ULBs was once again made after the unsuccessful initial search in 2009 for the flight recorders on Air France Flight 447, which were not located until 2011. A formal recommendation that the ULB design be upgraded to offer a longer battery life or to make the recorders ejectable had been included in the final report of the board of inquiry into the loss of South African Airways Flight 295 over the Indian Ocean in 1987; the ICAO made such a recommendation in 2014, with implementation by 2018.^[353] The European Aviation Safety Agency (EASA) issued new regulations requiring that the transmitting time of ULBs fitted to aircraft flight recorders be increased from 30 to 90 days. The agency proposed a new underwater locator beacon with a greater transmitting range to be fitted to aircraft flying over oceans.^[342] In June 2015, Dukane, a manufacturer of underwater locator beacons, began selling beacons with a 90-day battery life.^[355]

In March 2016, the ICAO adopted several amendments to the Chicago Convention to address issues raised by Flight 370's disappearance. For aircraft manufactured after 2020, cockpit voice recorders will be required to record at least 25 hours of data, so that they record all phases of a flight.^[347][348] Aircraft designs approved after 2020 will need to have a means to recover the flight recorders, or the information they contain, before the recorders sink below water. This provision is performance-based so that it can be accomplished by different techniques, such as streaming flight recorder data from aircraft in distress or using flight recorders which eject from aircraft and float on the water's surface.^[347][348] The new regulations will not require modifications to existing aircraft.^[347]

Safety recommendations[edit]

In January 2015, the US National Transportation Safety Board cited Flight 370 and Air France Flight 447 when it issued eight safety recommendations^[q] related to locating aircraft wreckage in remote or underwater locations; and repeated recommendations for a crash-protected cockpit image recorder and tamper-resistant flight recorders and transponders.^[356][357]

In popular culture[edit]

The disappearance of Malaysia Airlines Flight 370 has been described as "one of the biggest mysteries in modern aviation history".^[358][359]

Several documentaries have been produced about the flight. The Smithsonian Channel aired a one-hour documentary about the flight on 6 April 2014, titled Malaysia 370: The Plane That Vanished.^[360][361] The Discovery Channel broadcast a one-hour documentary about Flight 370 on 16 April 2014 titled Flight 370: The Missing Links.^[362][363]

An episode of the television documentary series Horizon titled "Where is Flight MH370?" was broadcast on 17 June 2014 on BBC Two. The programme, narrated by Amanda Drew, documents how the aircraft disappeared, what experts believe happened to it, and how the search has unfolded. The programme also examines new technologies such as flight recorder streaming and automatic dependent surveillance – broadcast (ADS-B), which may help prevent similar disappearances in the future. It concludes by noting that Ocean Shield had spent two months searching 850 km² (330 sq mi) of ocean, but that it had searched far to the north of the Inmarsat "hotspot" on the final arc, at approximately 28 degrees south, where the aircraft was most likely to have crashed.^[364] On 8 October 2014, a modified version of the Horizon programme was broadcast in the US by PBS as an episode of NOVΛ, titled "Why Planes Vanish", with a different narrator.^{[365][366][367]}

The first fictional account of the mystery was Scott Maka's MH370: A Novella, published three months after the aircraft's disappearance.^[368]

The aviation disaster documentary television series Mayday (also known as Air Crash Investigation or Air Emergency) produced an episode on the disaster, titled "Malaysia 370: What Happened?". In the UK, it aired on the first anniversary of Flight 370's disappearance, 8 March 2015.^[369] The television series Drain the Oceans, which airs on the National Geographic channel, highlighted the disaster, the methods used in the search and potential discoveries in August 2018.^[370]

Panopoly is doing a podcast story loosely based on the disappearance of Malaysia Airlines Flight 370 called "Passenger List" and will feature the voice of Kelly Marie Tran as the lead character.^[371]

Jeff Rake, creator of the NBC show Manifest, said that the show only made it to air because of the MH370 disappearance.^[372]

See also[edit]

• List of accidents and incidents involving commercial aircraft
• List of missing aircraft
• List of unrecovered flight recorders

Notes[edit]

References[edit]