Malaysia Airlines Flight 370

For the aircraft that was shot down over Ukraine, see Malaysia Airlines Flight 17.

Malaysia Airlines Flight 370

The missing aircraft, 9M-MRO, in 2011
Disappearance
Date	8 March 2014
Summary	Missing
Site	Unknown
Aircraft
Aircraft type	Boeing 777-200ER
Operator	Malaysia Airlines
Registration	9M-MRO
Flight origin	Kuala Lumpur International Airport
Destination	Beijing Capital International Airport
Passengers	227
Crew	12
Missing	239 (all)

Malaysia Airlines Flight 370 (MH370/MAS370) was a scheduled international passenger flight that disappeared on Saturday, 8 March 2014, while flying from Kuala Lumpur International Airport, Malaysia to Beijing Capital International Airport, People's Republic of China. Air traffic control received the aircraft's last message at 01:20 MYT (17:20 UTC, 7 March) when it was over the South China Sea, less than an hour after takeoff. It was last plotted by military radar at 02:15 over the Andaman Sea, 320 kilometres (200 mi) northwest of Penang state in northwestern Malaysia. At 07:24, Malaysia Airlines (MAS) reported the flight missing. The aircraft, a Boeing 777-200ER, was carrying 12 Malaysian crew members and 227 passengers from 15 nations.

A multinational search effort, which became the largest and most expensive in history, began in the Gulf of Thailand and the South China Sea, where the flight's signal was lost on secondary surveillance radar, and was soon extended to the Strait of Malacca and Andaman Sea. The focus of the search shifted to the southern part of the Indian Ocean, west of Australia. An analysis of possible flight paths was conducted, identifying a 60,000 km² (23,000 sq mi) search area, approximately 2,000 km (1,200 mi) west of Perth, Western Australia. The underwater search of this area began on 5 October 2014 and will last up to 12 months at a cost of A$60 million (approximately US$56 million or €41 million).

There has been no confirmation of any flight debris, and no crash site has been found, resulting in many unofficial theories about its disappearance. Analysis of these communications by multiple agencies has concluded that the flight ended in the southern Indian Ocean. On 24 March, the Malaysian government, noting that the final location determined by the satellite communication was far from any possible landing sites, concluded that "flight MH370 ended in the southern Indian Ocean."

At the time of its disappearance, and if the presumption of a loss of all lives aboard can be verified, MH370 would have been the deadliest aviation incident in the history of Malaysia Airlines and the deadliest involving a Boeing 777. MH370 was surpassed in both regards just 131 days later by the crash of another Malaysia Airlines Boeing 777, Flight 17, that was shot down over Ukraine on 17 July 2014, killing all 298 people aboard.

Disappearance

Known flight path taken by Flight 370 (yellow), derived from primary and secondary radar data, with select navigational waypoints and air routes.

External media
Images
Transcript of ATC conversations with Flight 370 A transcript of conversations between ATC and Flight 370 from pre-departure to final contact (12:25-1:19 MYT).
Video
ATC conversations with Flight 370 Audio recordings of conversations between ATC and Flight 370 from pre-departure to final contact (12:25-1:19 MYT).

Flight 370 was a scheduled red-eye flight in the early morning hours of 8 March 2014 from Kuala Lumpur, Malaysia to Beijing, China. It was one of two daily flights operated by Malaysia Airlines from their hub at Kuala Lumpur International Airport (KLIA; IATA code: KUL) to Beijing Capital International Airport (IATA code: PEK)—scheduled to depart at 00:35 local time (MYT; UTC+8:00) and arrive at 06:30 local time (CST; also UTC+8:00).

At 00:41 MYT, Flight 370 took off from runway 32R. Less than a minute after take off, Flight 370 was cleared by air traffic control (ATC) to climb to flight level 180—an altitude which corresponds to 18,000 feet (5,500 m) based on atmospheric pressure—on a direct path to waypoint IGARI and transferred from the airport's air traffic control to "Lumpur Radar" air traffic control on frequency 132.6 MHz. Air traffic control over peninsular Malaysia and adjacent waters is provided by the Kuala Lumpur Area Control Center (ACC); Lumpur Radar is the name of the frequency used for en route air traffic. Lumpur Radar cleared Flight 370 to flight level 350—35,000 ft (10,700 m) based on atmospheric pressure. At 1:01, Flight 370's crew reported to Lumpur Radar that they had reached flight level 350, which they confirmed again at 1:08.

Communication lost

The aircraft's final automated position report and last message using the Aircraft Communications Addressing and Reporting System (ACARS) protocol was sent at 01:07 MYT. The final verbal contact with air traffic control occurred at 1:19 MYT, when one of the aircraft's pilots acknowledged a send-off by Lumpur Radar to Ho Chi Minh ACC:

[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 contact air traffic control in Ho Chi Minh City as the aircraft passed into Vietnamese airspace, just north of the point where contact was lost. The captain of another aircraft attempted to reach the crew of Flight 370 "just after 1:30 am" 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 contact, but just heard "mumbling" and static. Calls made to Flight 370's cockpit at 02:39 MYT and 07:13 MYT were unanswered but acknowledged by the aircraft's satellite data unit.

Radar

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

At 1:21:04, Flight 370 was observed on radar at the Kuala Lumpur ACC as it passed the navigational waypoint IGARI in the Gulf of Thailand. At 1:21:13, Flight 370 disappeared from the radar screen at Kuala Lumpur and was lost about the same time on radar at Ho Chi Minh ACC, which claims the plane was at the nearby waypoint BITOD. Air traffic control uses secondary radar, which relies on a signal emitted by a transponder on aircraft; therefore, after 1:21 the transponder on Flight 370 was no longer functioning. The final data from the transponder indicated the plane was flying at its assigned cruise altitude of flight level 350 and was travelling at 471 knots (872 km/h; 542 mph) true airspeed.

The aircraft made a sharp turn westwards and headed towards a waypoint called VAMPI in the Strait of Malacca. Soon after the turn, military radar suggests the aircraft climbed to 45,000 ft (14,000 m)—above the aircraft's 43,100 ft (13,100 m) approved flight ceiling—then descended unevenly to 23,000 ft (7,000 m) as it approached Penang Island. A source close to the investigation told media that the aircraft descended as low as 12,000 feet (3,700 m). From there, the aircraft flew across the Strait of Malacca to or close to the waypoint VAMPI, after which the plane flew along air route N571 to waypoints MEKAR, NILAM, and possibly IGOGU. The last known location, from and near the limits of Malaysian military radar, was 200 nautical miles (370 km; 230 mi) northwest of Penang at an altitude of 29,500 ft (9,000 m).

Because of the sensitive nature of revealing military radar capabilities, countries in the region where Flight 370 disappeared have been reluctant to release information they may have collected from military radar. The only nation besides Malaysia to claim tracking Flight 370 is Thailand. Despite possibly flying near or over the northern tip of Sumatra, Indonesia—which has an early warning radar system—has publicly denied sighting Flight 370 on radar. No radar contact was detected by Australia, including their JORN over-the-horizon radar system, which was believed to be looking north to detect illegal migrants and not west over the Indian Ocean where Flight 370 is presumed to have flown based on satellite communications.

Satellite communication resumes

At 02:25:27 MYT, the aircraft's satellite communication system sent a 'log-on request' message—the first message on the system since the ACARS transmission at 01:07 MYT—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 phone calls, at 02:39 MYT and 07:13 MYT, which went unanswered by the cockpit. The final status request and aircraft acknowledgement occurred at 08:10 MYT. The aircraft sent a log-on request at 08:19:29 MYT which was followed, after a response from the ground station, by a 'log-on acknowledgement' message at 08:19:37 MYT. 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 MYT.

Response by air traffic control

Flight Information Regions in the vicinity of where Flight 370 disappeared from secondary radar. Kuala Lumpur ACC provides ATC services on two routes, located within FIR Singapore, between Malaysia and Vietnam.

At 1:30, the captain of another aircraft attempted to reach the crew of Flight 370 on the International distress frequency to relay Vietnamese air traffic control's request for Flight 370 to contact them; the captain said he was able to establish contact, but just heard "mumbling" and static. At 1:38, 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 contact with Flight 370, which last spotted by radar at waypoint BITOD. The two centres exchanged four more calls over the next 20 minutes with no new information.

At 2: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. At 2:15, the watch supervisor at Kuala Lumpur ACC queried Malaysia Airlines' operations centre, who said that they could exchange signals with Flight 370 and that Flight 370 was in Cambodian airspace. Kuala Lumpur ACC contacted Ho Chi Minh ACC to query that 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 contact with Flight 370. Kuala Lumpur ACC contacted Malaysia Airlines' operations centre at 2:34, inquiring about the communication status with Flight 370. The operations centre initially responded that they were unsure whether a message to the aircraft was sent successfully, but two minutes later said that Flight 370 was in a normal condition based on a signal download and that it was located at 14°54′00″ N, 109°15′00″E. Malaysia Airlines Flight 386 was requested by Ho Chi Minh ACC to attempt 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, but without success.

At 3:30, Malaysia Airlines' operations centre informed Kuala Lumpur ACC that the locations they had provided earlier were "based on flight projection and not reliable for aircraft positioning." Over the next hour, Kuala Lumpur ACC contacted Ho Chi Minh ACC asking whether they had contacted Chinese air traffic control. At 5:09, Singapore ACC was queried for information about Flight 370. At 5:20, an undisclosed official—identified in the preliminary report released by Malaysia as "Capt [name redacted]"—contacted Kuala Lumpur ACC requesting information about Flight 370; he opined that, based on known information, "MH370 never left Malaysian airspace."

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

Announcement of disappearance

Malaysia Airlines issued a media statement at 07:24 MYT, one hour after the scheduled arrival of the flight at Beijing, stating that contact with the flight had been lost by Malaysian ATC at 02:40 MYT; the time when contact was lost was later corrected to 1:21. Malaysia Airlines stated that the government had initiated search and rescue operations. 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.

Timeline of disappearance

Elapsed (HH:MM)	Time		Event
	MYT	UTC
00:00	8 March	7 March	Take-off from Kuala Lumpur International Airport
	00:41	16:41
00:20	01:01	17:01	Crew confirms altitude of 35,000 feet (11,000 m)
00:26	01:07	17:07	Last ACARS data transmission received; crew confirms altitude of 35,000 feet, a second time
00:26–1:22	01:07–2:03	17:07–18:03	Satellite communication link lost sometime during this period.
00:38	01:19	17:19	Last Malaysian ATC voice contact
00:40	01:21	17:21	Last secondary radar (transponder) contact at 6°55′15″N 103°34′43″E
00:41	01:22	17:22	Transponder and ADS-B no longer operating.
00:44	01:25	17:25	Aircraft deviated from planned route
00:49	01:30	17:30	Voice contact attempt by another aircraft, at request of Ho Chi Minh Area Control Centre (HCM ACC); mumbling and radio static heard in reply
00:56	01:37	17:37	Missed expected half-hourly ACARS data transmission
00:57	01:38	17:38	HCM ACC contacts Kuala Lumpur ACC (KL ACC) to enquire about Flight 370. HCM ACC tells them that verbal contact was not established and Flight 370 disappeared from their radar screens near BITOD waypoint. KL ACC responded that Flight 370 did not return to their frequency after passing waypoint IGARI.
01:05	01:46	17:46	HCM ACC contacts KL ACC again, inform them radar contact was established near IGARI, but lost near BITOD and that verbal contact was not established.
01:16	01:57	17:57	HCM ACC informs KL ACC that there was no contact with Flight 370, despite attempts on many frequencies and aircraft in the vicinity.
01:22	02:03	18:03	Malaysia Airlines dispatch center sent a message to the cockpit instructing pilots to contact Vietnam ATC, which was not responded to. A ground-to-aircraft ACARS data request, transmitted from the ground station multiple times between 02:03-02:05 MYT, was not acknowledged by the aircraft's satellite data unit.
01:22	02:03	18:03	KL ACC contacts HCM ACC and relays information from Malaysia Airlines' operations centre that Flight 370 is in Cambodian airspace.
01:34	02:15	18:15	KL ACC queries Malaysia Airlines' operations center, which replies that they are able to exchange signals with flight and it is in Cambodian airspace.
01:37	02:18	18:18	KL ACC contacts HCM ACC asking them if Flight 370 was supposed to enter Cambodian airspace. HCM ACC replies that Flight 370's planned route did not take it into Cambodian airspace and that they had checked and Cambodia had no information or contact with Flight 370.
01:41	02:22	18:22	Last primary radar contact by Malaysian military, 200 nautical miles (370 km; 230 mi) NW of Penang, 6°49′38″N 97°43′15″E
01:44	02:25	18:25	'Log-on request' sent by aircraft to satellite. Satellite communication link is reestablished after being lost for between 22–68 min. Sometimes referred to as the first hourly 'handshake' after disappearing from radar.
01:53	02:34	18:34	KL ACC queries Malaysia Airlines' operations centre about communication status with Flight 370, but they were not sure if a message sent to Flight 370 was successful or not.
01:54	02:35	18:35	Malaysia Airlines' operations centre informs KL ACC that Flight 370 is in a normal condition based on signals from the airplane and located at 14°54′00″N 109°15′00″E (Northern Vietnam) at 18:33 UTC. KL ACC relays this information to HCM ACC.
01:58	02:39	18:39	Ground-to-aircraft telephone call, via the aircraft's satellite link, went unanswered.
02:49	03:30	19:30	Malaysia Airlines' operations centre informs KL ACC that position information was based on flight projection and not reliable for aircraft tracking. Between 3:30-4:25, KL & HCM ACCs query Chinese air traffic control.
04:28	05:09	21:09	Singapore ACC queried for information about Flight 370.
04:49	05:30	21:30	Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) is activated.
05:49	06:30	22:30	Missed scheduled arrival at Beijing Capital International Airport (PEK)
06:32	07:13	23:13	Ground-to-aircraft telephone call placed by Malaysia Airlines, via the aircraft's satellite link, went unanswered.
06:43	07:24	23:24	Malaysia Airlines pronounces flight missing in statement released to media
07:30	08:11	8 March	Sixth and last successful automated hourly handshake with Inmarsat-3 F1
		00:11
07:38	08:19:29	00:19:29	Unexplained 'log-on request' sent by aircraft to satellite. Sometimes referred to as a 'partial handshake' transmitted by aircraft.
07:38	08:19:37	00:19:37	After the ground station responded to the log-on request, the aircraft replied with a 'log-on acknowledgement' transmission at 08:19:37.443 MYT. This is the last transmission received from MH370.
08:34	09:15	01:15	Aircraft did not respond to a scheduled, hourly handshake attempt by Inmarsat.

Presumed loss

Messages of hope and prayer for MH370 at a bookstore in Malaysia

On 24 March, Malaysian Prime Minister Najib Razak said,

Using a type of analysis never before used in an investigation of this sort... Inmarsat and the AAIB have concluded that MH370 flew along the southern corridor, and that its last position was in the middle of the Indian Ocean, west of Perth. This is a remote location, far from any possible landing sites. It is therefore with deep sadness and regret that I must inform you that, according to this new data, flight MH370 ended in the southern Indian Ocean.

Just before Najib spoke at 22:00 MYT, 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 the following SMS:

Malaysia Airlines deeply regrets that we have to assume beyond any reasonable doubt that MH370 has been lost and that none of those on board survived. As you will hear in the next hour from Malaysia's Prime Minister, we must now accept all evidence suggests the plane went down in the Southern Indian Ocean.

On 29 March, the Government of Malaysia and the AAIB stated that, in accordance with the protocols detailed in International Civil Aviation Organization (ICAO) Annex 13 concerning aircraft accident investigation, they would set up an international team to investigate the loss of the flight. On 30 March, Australian Prime Minister Tony Abbott announced the appointment of retired Australian Air Chief Marshal Angus Houston to head the Joint Agency Coordination Centre (JACC) to co-ordinate the search effort and closely co-operate with Malaysia, the responsible state under international law.

If the official assumption holds, at the time of its disappearance Flight 370 will have been the deadliest aviation incident in the history of Malaysia Airlines (surpassing the 1977 hijacking and crash of Malaysian Airline System Flight 653 that killed all 100 passengers and crew on board) and the deadliest involving a Boeing 777, surpassing Asiana Airlines Flight 214 (3 fatalities). In both of those categories, Flight 370 was surpassed just 131 days later by Malaysia Airlines Flight 17, another Boeing 777-200ER, which was presumed to be shot down on 17 July 2014, killing all 298 persons aboard. It would also be the second-deadliest incident in the Indian Ocean, behind Iran Air Flight 655; the 17th-deadliest incident worldwide; and the deadliest incident since the February 2003 crash of an Iranian military aircraft.

Search

Main article: Search for Malaysia Airlines Flight 370

The shifting search zones for Flight 370 from South China Sea and Strait of Malacca (lower right inset) to the underwater phase that began in October (pink).

On 13 March, White House Press Secretary Jay Carney said "an additional search area may be opened in the Indian Ocean based on some new information" and a senior official at The Pentagon told ABC News: "We have an indication the plane went down in the Indian Ocean." On 17 March, Australia agreed to lead the search in the southern locus from Sumatra to the southern Indian Ocean. This area, which Australian PM Tony Abbott described as "as close to nowhere as it's possible to be", is renowned for its strong winds, inhospitable climate, hostile seas, and deep ocean floors.

On 29 May the Australian Deputy Prime Minister, Warren Truss informed parliament that, beginning in August, after a new commercial operator for the search effort had been selected, the search would move into a new phase "that could take twelve months".

The Australian Transport Safety Bureau (ATSB) signed a contract with the Dutch deep sea survey company Fugro on 10 June to conduct a bathymetric survey of the seafloor in a new search area southwest of Australia (actual area wasn't publicly announced until 26 June, see below). The underwater search began on 6 October with the vessel GO Phoenix, which departed Jakarta on 24 September and calibrated its instruments before arriving in the search zone on 5 October. Fugro Discovery departed Perth on 18 October to join the search search.

International involvement

At the peak of the search effort and before the search was moved to the south Indian Ocean, 26 countries were involved in the search, contributing in aggregate nearly 60 ships and 50 aircraft. Australia, the United Kingdom, the United States, China, Japan, New Zealand, and South Korea assigned military and civilian ships and aircraft to the search. While not participating in the search itself, Sri Lanka gave permission for search aircraft to use its airspace. Malaysia deployed military fixed-wing aircraft and helicopters, and ships.

Within two days, the countries had already dispatched more than 34 aircraft and 40 ships to the area. Satellite imagery was also made available by Tomnod to the general public so they could help with the search through crowdsourcing efforts.

Aircraft

Flightdeck of 9M-MRO in 2004.

Flight 370 was operated with a Boeing 777-2H6ER, serial number 28420, registration 9M-MRO. The 404th Boeing 777 produced, it first flew 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, and configured to carry 282 passengers. 9M-MRO had accumulated 53,460 hours and 7,525 cycles in service, and had not previously been involved in any major incidents, though a minor incident while taxiing at Shanghai Pudong International Airport in August 2012 resulted in a broken wingtip. Its last maintenance 'A' check was carried out on 23 February 2014. The ADS-B on 9M-MRO was replaced with ADS-C In November 2013 to comply with FANS 1/A certification.

The Boeing 777, introduced in 1994, is generally regarded by aviation experts as having a safety record that is one of the best of any commercial aircraft. Since its first commercial flight in June 1995, there have been only four other serious accidents involving hull-loss: British Airways Flight 38 in 2008; a cockpit fire in a parked EgyptAir 777-200 at Cairo International Airport in 2011; Asiana Airlines Flight 214 in 2013, in which three people died, and Malaysia Airlines Flight 17 which was shot down over Ukraine with 298 people aboard in July 2014.

Passengers and crew

People on board by nationality

Nationality	No.
Australia	6
Canada	2
China	152
France	4
Hong Kong	1
India	5
Indonesia	7
Iran	2
Malaysia	50
Netherlands	1
New Zealand	2
Russia	1
Taiwan	1
Ukraine	2
United States	3
Total	239

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 travelling on stolen passports.

Crew

All 12 crew members were Malaysian citizens. Two pilots were among the crew:

• The captain was 53-year-old Zaharie Ahmad Shah from Penang; he joined Malaysia Airlines in 1981 and had 18,365 hours of flying experience. Zaharie was also an examiner qualified to conduct simulator tests for pilots.

• The first officer was 27-year-old Fariq Abdul Hamid, an employee of Malaysia Airlines since 2007, with 2,763 flying hours. This was Fariq's first flight as a fully qualified Boeing 777 first officer following the completion of his supervised transition to that type of aircraft.

Passengers

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. Twenty passengers—12 of whom were from Malaysia and 8 from China—were employees of Freescale Semiconductor.

Under a 2007 agreement with Malaysia Airlines, Tzu Chi – an international Buddhist organisation – immediately sent specially trained teams to Beijing and Malaysia to give emotional support to passengers' families. The airline also sent its own team of caregivers and volunteers and agreed to bear the expenses of bringing family members of the passengers to Kuala Lumpur and providing them with accommodation, medical care, and counselling. Altogether, 115 family members of the Chinese passengers flew to Kuala Lumpur. Some other family members chose to remain in China, fearing they would feel too isolated in Malaysia.

Compensation

The airline's offer of an ex gratia condolence payment of US$5,000 to the family of each passenger was initially rejected; the amounts were handed out to relatives on 12 March. It was also reported that Malaysian relatives only received $2,000. On 12 June, Malaysia's deputy Foreign Minister Hamzah Zainuddin said that families of seven passengers received $50,000 advance compensation from Malaysia Airlines, but that full payout would come after the aircraft is found or officially declared lost.

Lack of evidence in determining the cause of Flight 370's disappearance, indeed even physical evidence that the aircraft crashed, raises many issues regarding responsibility for the accident and payments made by insurance agencies. Under international aviation law, it is the carrier's responsibility to prove lack of fault in an accident. Under the Montreal Convention, each passenger's next-of-kin are automatically entitled, regardless of fault, to a payment of approximately US$175,000 from the airline's insurance company—a total of nearly US$40 million for the 227 passengers on board. Malaysia Airlines would still be vulnerable to civil lawsuits from passengers' families. Compensation awarded during or settled 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.

Investigation

International participation

Malaysia set up a Joint Investigation Team, composed of specialists from Malaysia, Australia, China, the UK, the US, and France, being led according to the ICAO standards by "an independent investigator in charge". 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.

Malaysia also announced, on 6 April, that it had set up three ministerial committees—a Next of Kin Committee, a committee to organize the formation of the Joint Investigation Team, and a committee responsible for Malaysian assets deployed in the search effort.

On 17 March, Australia took control for coordinating search, rescue, and recovery operations. For the following six weeks, the Australian Maritime Safety Authority (AMSA) and Australian Transport Safety Board (ATSB) worked to determine the search area, correlating information with the JIT and other government and academic sources, while the Joint Agency Coordination Center (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 satellite transmission. The group included aircraft and satellite experts from: Air Accidents Investigation Branch (UK), Boeing (US), Defence Science and Technology Organisation (Australia), Department of Civil Aviation (Malaysia), Inmarsat (UK), National Transportation Safety Board (US), and Thales (UK). The SSWG's efforts culminated in the formation of a new search area along the Broken Ridge and publication of a detailed report analysing factors bearing impact on the final location of the aircraft.

The investigation was also assisted by Interpol and other relevant international law enforcement authorities according to the Malaysian government.

Analysis of satellite communication

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).

The datalink for Malaysia Airline's avionics communications at the time of the incident was supplied by SITA, which contracted with Inmarsat to provide a satellite communication link using Inmarsat's Classic Aero service. 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 & ATN messages and provide voice, fax and data links using other protocols. An appropriate comparison of ACARS' relationship to the SATCOM system is that of a messaging application to a smartphone; the smartphone functions and will remain registered on a mobile phone network even if the messaging application is closed. The data/messages from the aircraft ("mobile terminal", with respect to the network) are transmitted by the aircraft's Satellite Data Unit (SDU) and relayed via satellite to a ground station, where they are routed to other communication networks to reach their destination. Messages may also be sent to the aircraft, in reverse order. The ground station keeps a log of transmissions and some data about them.

When the terminal tries to connect with the Inmarsat network, it will transmit a log-on request, which the ground station acknowledges. 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. After connecting, if a ground station hasn't received any contact from a terminal for one hour, the ground station will transmit a "log-on interrogation" message—informally referred to as a "ping"; an active terminal automatically responds. The entire process of interrogating the terminal is referred to as a 'handshake'.

Although the ACARS system on MH370 was disabled at 01:21 MYT (17:21 UTC, 7 March), the SDU remained operable. After last contact by primary radar west of Malaysia, the following records were recorded in the log of Inmarsat's ground station at Perth, Western Australia:

• 18:25:27 UTC – 1st handshake (initiated by MH370)
• 18:39:52 UTC – Ground to aircraft telephone call, acknowledged by SDU, unanswered
• 19:41:00 UTC – 2nd handshake (initiated by ground station)
• 20:41:02 UTC – 3rd handshake (initiated by ground station)
• 21:41:24 UTC – 4th handshake (initiated by ground station)
• 22:41:19 UTC – 5th handshake (initiated by ground station)
• 23:13:58 UTC – Ground to aircraft telephone call, acknowledged by SDU, unanswered
• 00:10:58 UTC – 6th handshake (initiated by ground station)
• 00:19:29 UTC – 7th handshake (initiated by MH370; widely reported as a 'partial handshake'), consisting of two transmissions:

• 00:19:29.416 UTC – 'log-on request' message transmitted by MH370 (7th 'partial' handshake)
• 00:19:37.443 UTC – 'log-on acknowledge' message transmitted by MH370, last transmission received from MH370

On 8 March, Inmarsat provided basic flight data relating to Flight 370 to SITA, which relayed information to Malaysia Airlines and investigators. On 9–10 March, Inmarsat engineers noted that the ground station log recorded pings from the aircraft for several hours after contact was lost with air traffic control. An analysis of the time difference between the transmission of the ping and the aircraft's response allowed Inmarsat to determine the aircraft's distance from the satellite resulted in the plotting of two arcs—referred to as the "northern corridor" and "southern corridor" where the aircraft may have been located at the time of its last complete handshake at 00:11 UTC.

Inmarsat conducted further analysis on the signals received during the handshakes, focusing on the frequency shift of the signal emitted from the aircraft compared with the actual frequency received, known as the burst frequency offset, using a baseline of earlier system data for the aircraft, satellite, and ground station. The burst frequency offset, caused by the Doppler effect, varies based on the aircraft's speed and whether it is moving towards or away from the satellite. Using an "innovative technique" that has "never before [been] used in an investigation of this sort", the team determined it could also use the burst frequency offset to determine the aircraft's speed and position along the identified arcs. Inmarsat cross-checked its methodology to known flight data from six Boeing 777 aircraft flying in various directions on the same day, and found a good match. Applying the technique to the handshake signals from Flight 370 gave results that correlated strongly with the expected and actual measurements of a southern trajectory over the Indian Ocean, but poorly with a northern trajectory. Further revised calculations to account for movements of the satellite relative to the earth allowed the northern corridor to be ruled out completely. This analysis was passed on to Malaysian authorities on 23 March. At 22:00 local time the next day, Prime Minister Najib cited this development to conclude that "Flight MH370 ended in the southern Indian Ocean."

The log-on message sent from the aircraft at 00:19:29 UTC was not immediately well understood. The 18:25 UTC handshake was also initiated by the aircraft. There are only a few reasons the SDU would transmit a log-on message, such as a power interruption, software failure, loss of critical systems providing input to the SDU, or a loss of the link due to aircraft attitude. Investigators consider the most likely reason to be that they were sent during power-up after an electrical outage. At 00:19, the aircraft had been airborne for 7 h 38 min; the typical Kuala Lumpur-Beijing flight is 51⁄2 hours and fuel exhaustion was likely. In the event of fuel exhaustion and engine flame-out, the aircraft's ram air turbine would deploy, providing power to various instruments and flight controls, including the SDU. Approximately 90 seconds after the 18:25 UTC handshake, communications from the aircraft's inflight entertainment system were recorded in the ground station log. Similar messages would be expected following the 00:19 UTC handshake but none were received, supporting the fuel starvation scenario.

Since the aircraft did not respond to a ping at 01:15 UTC, it was concluded that at some point between 00:11 UTC and 01:15 UTC, the aircraft lost the ability to communicate with the ground station, which Malaysia's Department of Civil Aviation noted was "consistent with the maximum endurance of the aircraft". The ATSB is "confident the seventh handshake represents the area where the aircraft ran out of fuel before entering the ocean."

Malaysian investigators set up an international working group, consisting of various agencies with experience in aircraft performance and satellite communications, to further analyse the signals between Flight 370 and the ground station, especially the signal at 00:19 UTC. These included representatives from the UK's Inmarsat, AAIB and Rolls-Royce; China's Civil Aviation Administration and Aircraft Accident Investigation Department; the US NTSB and FAA, and Malaysian authorities.

In an article published on 8 May several satellite experts questioned the analysis of satellite pings made by Inmarsat staff because the Doppler frequency shifts measured were apparently not properly corrected against the satellite's own drift (a periodic North-South oscillation of 3° every 24 hours). Without any additional data being released, the implication of this new analysis was that the northern portion of the Inmarsat satellite pings arc could not be ruled out. The Malaysian government released the satellite data three weeks later.

A peer-reviewed paper by Inmarsat scientists published in the Journal of Navigation in October 2014 provides a comprehensive account of the analysis applied to the satellite communications from Flight 370. Details of the methodology used to analyze the satellite communications were provided in the Australian Transport Safety Bureau's report MH370 – Definition of Underwater Search Areas, published in June, and a supplement released in October.

Analysis of hydroacoustic data

A source of evidence to assist in locating the final resting place of the aircraft is analysis of underwater sound recordings. If the aircraft hit the ocean hard, hydroacoustic recordings could have potentially recorded an impact event. Furthermore, the aircraft's flight data recorders were fitted with underwater 'pingers', which emit a detectable, pulsating acoustic signal that could have potentially led searchers to their locations.

Impact event

If Flight 370 had impacted the ocean hard, resulting underwater sounds could have been detected by hydrophones, given favourable circumstances. Sound waves can travel long distances in the ocean, but sounds that travel best are those that are reflected into the 'deep sound channel' usually found between 600–1200 m beneath the surface. Most of the sound generated by an aircraft impacting the ocean would travel straight down to the seabed, making it unlikely that any of these sounds would be reflected into the deep sound channel unless the seabed sloped. Sounds from pieces of the aircraft imploding at depth would be more likely to travel in the deep sound channel. "The combination of circumstances necessary to allow [detection of an ocean impact] would have to be very particular," according to Mark Prior, a seismic-acoustic specialist at the Comprehensive Nuclear-Test-Ban Treaty Organization, who also explains that "given the continuing uncertainty regarding the fate of MH370, underwater acoustic data still has the possibility of adding something to the search." When an Airbus A330 hit the Atlantic Ocean at speed of 152 kn (282 km/h; 175 mph), no data relating to the impact was detected in hydroacoustic recordings, even when analysed after the location of that aircraft was known. As with the analysis of the Inmarsat satellite data, the hydroacoustic analysis uses the data in a way very different from that originally intended.

External media
Images
Graphics produced by the Curtin University research team
Audio
Audio recording of the suspect acoustic signature

The Australian Transport Safety Bureau requested the Curtin University Centre for Marine Science and Technology (CMST) analyse these signals. Scientists from the Comprehensive Nuclear-Test-Ban Treaty Organization & Geoscience Australia have also been involved with the analysis. Available sources of hydroacoustic data were:

• The Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO), which operates a system of sensors to detect nuclear tests as part of their mission to ensure compliance with the Comprehensive Nuclear Test Ban Treaty. Data was analyzed from CTBTO hydrophones located south-west of Cape Leeuwin, Western Australia (HA01) and in the northern Indian Ocean. These stations have two hydrophones each, separated by several kilometers, allowing a bearing to be calculated for the source of noise to within 0.5°.
• Australia's Integrated Marine Observing System (IMOS). Data from an acoustic observatory 40 km west of Rottnest Island, Western Australia, near the Perth Canyon. IMOS stations have just one hydrophone each and therefore cannot provide a bearing on the source of the noise. Several IMOS recorders deployed in the Indian Ocean off northwestern Australia by CMST may have recorded data related to Flight 370. These recorders were not recovered as part of the investigation. These sensors record only five minutes out of every fifteen and are likely to be contaminated by noise from seismic surveys. CMST originally planned to recover the sensors in September or October, but now plan to make the trip in August.
• It is unclear what other sources of hydroacoustic data are available in the region. India & Pakistan operate submarine fleets, but the JACC claims they aren't aware of any hydrophones operated by those countries. The US Navy operated a vast array of hydrophones—the Sound Surveillance System (SOSUS)—during the Cold War to track submarines, which is believed to remain in operation. Asked if any SOSUS sensors are located in the Indian Ocean, a spokesman for the US Navy declined comment on the subject, noting that such information is classified.

Scientists from the CTBTO analysed their recordings soon after Flight 370 disappeared, finding nothing of interest. However, after the search for the flight shifted to the Indian Ocean, CMST collected recordings from the IMOS and found a clear acoustic signature just after 01:30 UTC on 8 March. This signature was also found, but difficult to discern from background noise, in the CTBTO recordings from HA01, likely because HA01 receives a lot of noise from the Southern Ocean & Antarctic coastline.

The CMST researchers believe that the most likely explanation of the hydroacoustic data is that they come from the same event, but unrelated to Flight 370. They note that "the characteristics of the [event's acoustic signals] are not unusual, it is only their arrival time and to some extent the direction from which they came that make them of interest." If the data relates to the same event, related to Flight 370, but the arc derived from analysis of the aircraft's satellite transmission is incorrect, then the most likely place to look for the aircraft would be along a line from HA01 at a bearing of 301.6° until that line reaches the Chagos-Laccadive Ridge (approximately 2.3°S, 73.7°E). In the latter possibility, if the acoustic recordings are from the impact of the aircraft with the ocean, they likely came from a location where water is less than 2000 m deep and the seabed slopes downwards towards the east or southeast; if they came from debris imploding at depth, the source location along this line is much less certain. The lead researcher of the CMST team, Dr.Alec Duncan, believes there's a slim chance—perhaps as low as 10 percent—that the acoustic event is related to Flight 370.

Underwater locator beacons

The aircraft's flight recorders were fitted with Dukane DK100 underwater acoustic beacons—also known as "underwater locator beacons" (ULBs) or "pingers"—which are activated by immersion in salt water and thereafter emit a 10 millisecond pulse every second at frequency of 37.5±1 kHz. The beacons are limited by battery life, providing a minimum of 30 days and have an estimated maximum life of 40 days, according to their manufacturer. The nominal distance at which these beacons can be detected is 2000–3000 metres. Because the flight recorders to which they are attached could provide valuable information in the investigation, an intense effort was made to detect the beacons' pings before their batteries expired.

The HMS Echo made one possible detection on 2 April—the same day the ship joined the search effort. The following day, following tests, the detection was dismissed as an artifact of the ship's sonar system. On the afternoon of 5 April Perth time, HMS Echo detected a signal lasting approximately 90 seconds. The second detection was made within 2 km from the first detection.

MV Haixun 01, operated by the Chinese Maritime Safety Administration, detected a signal at 37.5kHz pulsing once per second on 4 April and again on 5 April at a position 3 km west of the first detection. The HMS Echo was sent to the location of the MV Haixun 01 detections and determined that the detections were unlikely to originate from ULBs attached to the plane's black boxes due to the depth of the seafloor, surface noise, and the equipment used. A submarine sent to the location made no acoustic detections.

A Phoenix International TPL-25 owned by the US Navy. Two were loaned to the Royal Australian Navy and deployed from AVD Ocean Shield as part of the acoustic search.

ADV Ocean Shield was sent to the search area with two Phoenix International TPL-25 towed pinger locators (also known as "towfish"). Shortly after one of the towfish was deployed, while descending, an acoustic signal was detected at a frequency of 33kHz on 5 April. Further detections were made on 5 April and on 8 April, but none could be detected when the ship passed the same location on an opposing heading.

Independent analyses of the detections made by ADV Ocean Shield determined that the signals did not match the performance standards of the ULBs attached to the aircraft's black boxes. However, although unlikely, they noted that the signals could have originated from a damaged ULB.

Between 6-16 April, AP-3C Orion aircraft of the Royal Australian Air Force deployed sonobouys, which sank to a depth of 300m to detect the acoustic signature of the ULBs attached to the aircraft's black boxes. Sonobouy drops were carried out at locations along the calculated arc of the final satellite communication with Flight 370 where seafloor depths were considered favourable, near the MV Haixun 01 detections, and along the bearing determined by the Curtin University research team of a possible impact event. One AP-3C Orion sortie was capable of searching an area of 3,000 square kilometres (1,200 sq mi). No acoustic detections related to the ULBs attached to the aircraft's black boxes were made by the sonobouys.

Possible in-flight events

Power interruption

The SATCOM link functioned normally from pre-flight (beginning 16:00 UTC) until it responded to a ground-to-air ACARS message with an acknowledge message at 17:07 UTC. Ground-to-air ACARS messages continued to be transmitted to MH370 until Inmarsat's network sent multiple 'Request for Acknowledge' messages at 18:03 UTC, without a response from the aircraft. At some time between 17:07 & 18:03, power was lost to the SDU. At 18:25 UTC, the aircraft's SDU sent a 'log-on request'. It is not common for a log-on request to be made in-flight, which 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. As the power interruption was not due to engine flame-out, per ATSB, it may have been the result of manual switching off the aircraft's electrical system.

Unresponsive crew/hypoxia

An analysis by the Australian Transport Safety Bureau comparing the evidence available for MH370 with three categories of accidents—an in-flight upset (e.g. stall), a glide event (e.g. engine failure, fuel starvation), and an unresponsive crew/hypoxia event—concluded that an unresponsive crew or hypoxia event "best fit the available evidence" for the 5-hour period of the flight as it travelled south over the Indian Ocean without communication or significant deviations in its track, likely on autopilot. There is, however, no consensus among investigators on the unresponsive crew/hypoxia theory.

Possible causes of disappearance

See also: Malaysia Airlines Flight 370 unofficial disappearance theories

Passenger involvement

Two men identified on the passenger manifest, an Austrian and an Italian, had reported their passports stolen in 2012 and 2013, respectively. 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. Malaysia's Home Minister, Ahmad Zahid Hamidi, criticised his country's immigration officials for failing to stop the passengers travelling on the stolen European passports. The two one-way tickets purchased for the holders of the stolen passports were booked through China Southern Airlines. It was reported that an Iranian had ordered the cheapest tickets to Europe via telephone in Bangkok, Thailand. The tickets were paid for in cash. 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 head of Interpol said the organisation was "inclined to conclude that it was not a terrorist incident". The two men were believed to be asylum seekers.

United States and Malaysian officials were reviewing the backgrounds of every passenger named on the manifest. 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 potential hijackers.

One passenger who worked as a flight engineer for a Swiss jet charter company was briefly suspected as potential hijacker because he was thought to have the relevant skill set.

Crew involvement

Police searched the homes of the pilot and co-pilot, on suspicion that those in the cockpit had been responsible for the aircraft's disappearance. The United States' Federal Bureau of Investigation reconstructed the deleted data from the pilot's home flight simulator and a Malaysian government spokesman indicated that "nothing sinister" had been found on it. On 2 April Khalid Abu Bakar, Malaysia's Police Inspector-General, said that as part of its ongoing criminal investigation, more than 170 interviews had been conducted, including with family members of the pilots and crew. Investigators seized financial records for all 12 crew members, including bank statements, credit card bills and mortgage documents.

Shortly after Flight 370's disappearance, media reports revealed that Captain Zaharie Ahmad Shah's wife and three children moved out of his house the day before the disappearance and a friend claimed that Capt. Shah was seeing another woman and the relationship with that other woman was also in trouble. Claims of domestic problems have been denied by Capt. Shah's family. A fellow pilot and long-time associate of Capt. Shah stated the captain was "terribly upset" that his marriage was falling apart. Police were also investigating reports that Capt. Shah received a two-minute phone call prior to the flight's departure from an unidentified woman using a mobile phone number obtained with a false identity. Furthermore, Capt. Shah was also a supporter of Malaysian opposition politician Anwar Ibrahim, who was sentenced to jail on 7 March after an earlier acquittal on sodomy charges was overturned in a move viewed as politically motivated.

On 23 June, an official Malaysian police investigation into the disappearance of Malaysia Airlines flight 370 identified the captain as the prime suspect if it is proven human intervention was involved. Contradicting an earlier statement about data from Capt. Shah's flight simulator, The Sunday Times reported that among deleted flight paths performed on the flight simulator investigators found a flight path into the Southern Ocean where the plane landed on an island with a small runway. Investigators noted strange behaviour by Capt. Shah from conducting 170 interviews—namely, that the captain had made no social or professional plans for after 8 March, when Flight 370 disappeared. News reports about the captain's lack of social plans and flight simulator exercises cite results of the police enquiry into the pilots, which have been shared with some of the investigation team but haven't been released publicly.

Investigators believe someone in the cockpit of MH370 re-programmed the plane's autopilot before it traveled south across the Indian Ocean, raising further suspicion the disappearance was a mass atrocity committed by the captain or copilot. A hijacking by a pilot would not be without precedent, as less than three weeks before Flight 370 disappeared—on 17 February 2014—Ethiopian Airlines Flight 702 was hijacked when the co-pilot locked the captain out of the cabin and diverted the aircraft to seek asylum in Switzerland.

Cargo

On 17 March, MAS chief executive, Ahmad Jauhari Yahya, indicated that the aircraft was carrying only three to four tonnes/tons of mangosteens and said that nothing it transported was dangerous. Three days later, he also confirmed that potentially flammable batteries, identified as lithium-ion, were on board, adding that all cargo was "packed as recommended by the ICAO", checked several times, and deemed to meet regulations. The cargo manifest released on 1 May had revealed two air waybills (AWBs) for lithium-ion batteries with a total consignment weight of 221 kg. Three other AWBs weighing 2,232 kg were declared as radio accessories and chargers, but an MAS representative said he was not permitted to provide additional information. Khalid Abu Bakar, Malaysia's Police Inspector-General, said that the provenance and destination of all cargo, including the mangosteens and in-flight meals, were being investigated to rule out sabotage as a cause.

Claims of responsibility

On 9 March 2014, members of the Chinese news media received an open letter that claimed to be from the leader of the Chinese Martyrs Brigade, a previously unknown group. The letter claimed that the loss of flight MH370 was in retaliation for the Chinese government's response to the knife attacks at Kunming railway station on 1 March 2014 and part of the wider separatist campaign against Chinese control over Xinjiang province. The letter also listed unspecified grievances against the Malaysian government. The letter's claim was dismissed as fraudulent based on its lack of detail regarding the fate of MH370 and the fact that the name "Chinese Martyrs Brigade" appeared inconsistent with Uyghur separatist groups which describe themselves as "East Turkestan" and "Islamic" rather than "Chinese".

Criticism and response

Information sharing

Public communication from Malaysian officials regarding the loss of the flight was initially beset with confusion. The New York Times wrote that the Malaysian government and the airline released imprecise, incomplete, and sometimes inaccurate information, with civilian officials sometimes contradicting military leaders. Malaysian officials were also criticised after the persistent release of contradictory information, most notably regarding the last point and time of contact with the aircraft.

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. International relations experts said entrenched rivalries over sovereignty, security, intelligence, and national interests made meaningful multilateral co-operation very difficult. A Chinese academic made the observation that the parties were searching independently, thus it was not a multilateral search effort. However, The Guardian noted the Vietnamese permission given for Chinese aircraft to overfly its airspace as a positive sign of co-operation. 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. 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.

Malaysia had initially declined to release raw data from its military radar, deeming the information "too sensitive", but later acceded. Defence experts suggested that giving others access to radar information could be sensitive on a military level. As an example: "The rate at which they can take the picture can also reveal how good the radar system is." 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. 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. This is quite plausible, given how quickly the US redirected USS Kidd to begin searching the Indian Ocean, even as other search assets were then still focused on searching previous search areas.

Criticism was also levelled at the delay of the search efforts. On 11 March, three days after the aircraft disappeared, British satellite company Inmarsat had provided officials (or its partner, SITA) 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 only publicly acknowledged and released by Najib on 15 March in a press conference. 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. Hishammuddin said 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.

Criticism of Malaysian government

Questions and criticisms were raised by air force experts and the Malaysian opposition about the current state of Malaysia's air force and radar capabilities. Opposition leader Anwar Ibrahim said it was impossible and unacceptable that the country's advanced British radar system and military readiness had not been triggered by such a diverted flight.

Malaysia Airlines

See also: Malaysia Airlines § 2014 aircraft losses

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 partially result from the suspension of the airline's advertisement campaigns following the disappearance. Mr. 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." In further remarks, Mr. Ahmad said he wasn't 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. In China, where the majority of passengers were from, bookings on Malaysia Airlines were down 60% in March.

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. 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.

Malaysia Airlines was given US$110 million from insurers in March 2014 to cover initial payments to passengers' families and the search effort. 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.

Financial troubles

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. Malaysia Airlines lost RM443.4 million (US$137.4 million) in the first quarter of 2014 (January–March). The second quarter—the first in the aftermath of Flight 370's disappearance—saw a loss of RM307.04 million (US$97.6 million), which represented a 75% increase over losses from the second-quarter of 2013. Industry analysts expect Malaysia Airlines to lose further market share and face a challenging environment to stand out from competitors while addressing their financial plight. The company's stock, down as much as 20% following the disappearance of Flight 370, had fallen 80% over the previous five years, which contrasts with a rise in the Malaysian stock market of about 80% over the same period.

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. The loss of Flight 17 in July greatly exacerbated Malaysia Airline's woes. The combined effect on consumer confidence of the loss of Flights 370 & 17 and the airline's poor financial performance led Khazanah Nasional—the majority shareholder (69.37%) and a Malaysian state-run investment arm—to announce on 8 August its plan to purchase the remainder of the airline, thereby renationalising it.

China

On 24 March, Chinese Deputy Foreign Minister Xie Hangsheng reacted sceptically to the conclusion by the Malaysian government that the aircraft had gone down with no survivors. Xie demanded "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."

On 25 March, Chinese president Xi Jinping said he was sending a special envoy to Kuala Lumpur to consult with the Malaysian government over the missing aircraft. The same day, around two hundred family members of the Chinese passengers protested outside the Malaysian embassy in Beijing. Relatives who had arrived in Kuala Lumpur after the announcement continued with their protest, accusing Malaysia of hiding the truth and harbouring the 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. An op-ed for China Daily said that Malaysia was not wholly to be blamed for its poor handling of such a "bizarre and unprecedented crisis", and appealed to Chinese people not to allow emotions to prevail over evidence and rationality. The Chinese ambassador to Malaysia rebuked the "radical and irresponsible opinions" of the Chinese relatives, and said that they "[did] not represent the views of Chinese people and the Chinese government". The ambassador also strongly criticised Western media for having "published false news, stoked conflict and even spread rumours" to the detriment of relatives and of Sino–Malaysian relations. On the other hand, a US Department of Defense official criticized China for what he perceived as providing apparently false leads that detracted from the search effort and wasted time and resources.

Boycotts

Chinese have boycotted most things Malaysian, including vacations and singers, in protest of Malaysia's handling of the Flight 370 investigation. Bookings on Malaysia Airlines from China, where the majority of passengers were from, were down 60% in March . In late March, several major Chinese ticketing agencies—ELong, LY.com, Qunar and Mango—banned sale of airline tickets to Malaysia and several large Chinese travel agencies reported a 50% drop in tourists compared to the same period the year before. China is the third largest source of visitors for Malaysia, accounting for 1.79 million tourists. 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$650 million-1.3 billion).

The boycotts have largely been led or supported by celebrities. Film star Chen Kun posted a message to Weibo—where he has 70 million followers—stating: "I...will start a boycott from my inner heart on any commercials and travel relating to Malaysia. This will last...until the Malaysian government takes down their clown-like mask and tells the truth." The post was shared over 70,000 times and drew over 30,000 comments. Over 337,000 people retweeted a tweet from TV host Meng Fei, which said "I’ve never been to Malaysia and I do not plan to go there in the future. If you feel the same, please retweet this message."

Ironically, China & Malaysia had dubbed 2014 to be the "Malaysia-China Friendship Year" to celebrate 40 years of diplomatic relations between the two countries.

Air transport authorities

In June 2014 the International Air Transport Association said it was working on implementing new measures to track aircraft in flight in real time. A special panel was considering a range of options including the production of equipment especially designed to ensure real time tracking. There was a call for automated transponders after the attacks of 11 September 2001; no changes were made as aviation experts preferred flexible control, in case of malfunctions or electrical emergencies. It was expected to provide a report to the International Civil Aviation Organization on 30 September 2014, but on that day said that the report would be delayed citing the need for further clarification on some issues.

In May 2014, Inmarsat said it would offer its tracking service for free to all aircraft equipped with an Inmarsat satellite connection and announced a service that will allow the transmitting of black box data to expert when an aircraft goes missing. Inmarsat has also changed the time period for handshakes with their terminals from one hour to 15 minutes.

In August 2014, Deutsche Welle questioned various aviation safety organisations on measures they are hoping to implement to avoid another aircraft loss such as that of MH370. The European Aviation Safety Agency said its new regulations say that the transmitting time of underwater locating devices fitted to aircraft must range from 30–90 days. The agency proposed a new underwater locating device with a larger transmitting range to be fitted to aircraft flying over oceans.

Timeline of events

Date (UTC)	Category	Event
7 March	Media	Department of Civil Aviation (DCA) Malaysia and Malaysia Airlines confirm Subang Air Traffic Control outside Kuala Lumpur lost contact with Malaysia Airlines Flight 370 on 8 March 2014 at 02:40 local time (on 7 March 2014 at 18:40 UTC), later corrected to 01:30 local time (17:30 UTC) located at 6°33′05″N 103°20′39″E
	Search	Malaysian and Vietnamese authorities jointly searching in the Gulf of Thailand area; China dispatches two maritime rescue ships to the South China Sea.
8 March	Search	An international search and rescue mission mobilised, focusing on Gulf of Thailand. Natuna Islands archipelago and South China Sea. Malaysia, Vietnam, China, Singapore and Indonesia.
	Media	Malaysia Airlines releases passenger manifest of Malaysia Airlines Flight 370.
		Two men from Austria and Italy, listed among the passengers on Flight 370, are not in fact on board. Officials in both countries say that each had his passport stolen.
9 March	Search	The search zone expanded, to include areas in the Strait of Malacca as military radar tracking indicates aircraft might have turned west from its flight plan and flight path.
	Investigation	INTERPOL confirms that at least two passengers are found to have been travelling on stolen passports registered in its databases.
10 March	Search	Ten Chinese satellites deployed in the search. Oil slicks on the surface of the South China Sea test negative for jet fuel.
	Media	Malaysia Airlines announces it will give US$5,000 to the relatives of each passenger.
11 March	Investigation	INTERPOL says that two false identities are not linked to the disappearance.
	Media	China activates the International Charter on Space and Major Disasters.
12 March	Search	Chinese satellite images of possible debris from Flight 370 in the South China Sea at 6.7°N 105.63°E / 6.7; 105.63 (Possible debris, 12 March) released, but surface search finds no wreckage. Malaysian government receives Inmarsat info that Flight 370 pinged for hours after ACARS went off-line.
	Media	Chinese government criticises Malaysia for inadequate answers regarding Flight 370.
	Investigation	Royal Malaysian Air Force chief says that an aircraft plotted on military radar crossed the Malay Peninsula after changing course, towards a waypoint called GIVAL at 2:15 local time (18:15 UTC, 7 March), 200 miles (320 km) northwest of Penang Island off Malaysia's west coast. It followed standard aviation corridors. Search and rescue efforts being stepped up in Andaman Sea and Bay of Bengal.
14 March	Investigation	Investigation concludes that Flight 370 was still under human control after it lost ground control contact.
	Media	MAS retires the MH370/MH371 flight number pair.
15 March	Search	New phase of multi-national search and rescue operations within two areas in the northern and southern "corridors". Twenty-six countries involved, among the northern corridor countries are Kazakhstan, Turkmenistan, China, Thailand, including South China Sea and Gulf of Thailand. The southern corridor covers Indonesia, Australia, and the Indian Ocean.
		India continues search for Malaysia Airlines Flight 370; Malaysia ends hunt in South China Sea.
	Investigation	Malaysian police search the homes of both of the aircraft's pilots.
16 March	Search	Twenty-five countries are involved in the search. India ends its search in the Andaman Sea and Bay of Bengal.
17 March	Search	Search area reported by Malaysian authorities to be 2,000,000 square miles (5,200,000 km2), as a belt beneath the last possible arc position stretching from Kazakhstan over Indonesia to the southern part of the Indian Ocean. Australia pledges to lead a search from Sumatra to the southern Indian Ocean.
18 March	Search	China starts a search operation in its own territory. Australia conducts an aerial search through waters West and North of Cocos Islands and Christmas Island (close to Indonesia). Australia also conducts its first aerial search of the southern Indian Ocean, roughly 3,000 kilometres (1,900 mi) southwest of Perth.
19 March	Search	Australia searches the southern Indian Ocean with three aircraft and three merchant ships, transiting through a slightly revised search area of 305,000 square kilometres (118,000 sq mi) about 2,600 kilometres (1,600 mi) southwest of Perth.
20 March	Media	Prime Minister of Australia, Tony Abbott, told parliament that the "new and credible information" had emerged from expert analysis of satellite imagery.
	Search	Five aircraft and a fourth (merchant) ship are dispatched to 44°03′02″S 91°13′27″E.
22 March	Search	Chinese satellite image taken on 18 March shows a possible object measuring 22.5 by 13 metres (74 by 43 ft) at 44°57′30″S 90°13′40″E, approximately 3,170 kilometres (1,970 mi) west of Perth and 120 kilometres (75 mi) from the earlier sighting, but did not confirm the object's nature.
24 March	Media	Prime Minister of Malaysia announces that Flight 370 is assumed to have gone down in the southern Indian Ocean; Malaysia Airlines states to families that it assumes "beyond reasonable doubt" there are no survivors.
	Search	Search area narrowed to the southern part of the Indian Ocean west and southwest of Australia. The northern search corridor (northwest of Malaysia) and the northern half of the southern search corridor (the waters between Indonesia and Australia) are definitively ruled out. An Australian search aircraft spots two objects at sea, 1,550 miles (2,490 km) southwest of Perth.
26 March	Search	French satellite images captured on 23 March show 122 possible pieces of debris at 44°41′24″S 90°25′19.20″E, 44°41′38.45″S 90°29′31.20″E and 44°40′10.20″S 90°36′25.20″E.
	Media	UK Air Accidents Investigation Branch (AAIB) heads a team of investigators from other states as part of an international effort supporting the Malaysian authorities in accordance with the International Civil Aviation Organization (ICAO) code.
27 March	Search	The search area narrows to roughly 76,000 square kilometres (29,000 sq mi). Thai satellite images, captured 24–26 March show floating objects 200 kilometres (120 mi) south of the French observations. Five ships from Australia and China are engaged.
28 March	Search	Search shifts to a new 319,000-square-kilometre (123,000 sq mi) area 1,100 kilometres (680 mi) northeast of the previous search area.
29 March	Media	Malaysia announces that an international panel will be formed under United Nations protocols to investigate the Flight 370 incident.
30 March	Media	Prime Minister of Australia announces newly formed Joint Agency Coordination Centre (JACC) headed by Angus Houston. Military air crew from Australia, China, Japan, Malaysia, New Zealand, South Korea, and the United States are actively engaged.
5 April	Search	Chinese patrol ship Haixun 01 detects a pulse signal at 25°S 101°E. Ocean Shield also picks up two longer lasting signals.
8 April	Search	Ocean Shield picks up two further signals 3,500 metres deep, close to those of 5 April.
10 April	Search	Another signal is acquired by a sonobuoy deployed near the Ocean Shield signal acquisitions. JACC declares the contact unlikely to be related to Flight 370. Hydrographic survey ship HMS Echo arrives on scene to provide advanced computer analysis of Ocean Shield collected sonar data and to measure the thermoclines in the area to predict the trajectory of the detected pings.
14 April	Search	An oil slick is found 5.5 km from the estimated location of the pings by Ocean Shield. Ocean Shield ceases towed passive sonar operations; the AUV Bluefin-21 is deployed with side-scan sonar to search for wreckage on the ocean floor, but its mission is automatically aborted on reaching its maximum operating depth.
15 April	Search	Bluefin-21 resumes scanning after its abortive initial mission.
18 April	Search	The oil slick discovered four days earlier is determined by an Australian laboratory analysis not to be related to Flight 370.
24 April	Search	Debris consisting of riveted metal sheets washes up on the Western Australian coast. This is later confirmed to be unrelated to Flight 370.
28 April	Search	PM Abbott and Angus Houston of JACC announce that a larger area of the ocean floor would now be searched and there would be a suspension of the aerial search due to the likelihood that any wreckage would have sunk.
5 May	Search	The US Navy extends contract for Bluefin-21 by four weeks.
12 May	Search	Searchers say two of the four 'pings' they thought were from flight recorder ULBs may not have been from the flight recorder.
22 May	Search	Bluefin-21 resumes search after repair.
27 May	Media	Inmarsat satellite data released.
28 May	Search	Final Bluefin mission completed with nothing found in the area of the supposed pings heard on 5 April; a day later Australian Transport Safety Bureau rules out area as final resting place of MH370.
4 June	Search	Australian researchers release recording of an underwater sound that could have been that of MH370 hitting the water.
12 June	Media	A Malaysian minister announces that families of the missing passengers will receive $50,000 per person as an interim compensation.
17 June	Search	Inmarsat states that it has pinpointed the most likely end of MH370 in an unsearched area of the Southern Indian Ocean.
20 June	Search	Australian Transport Safety Bureau (ATSB) announces that a new search will concentrate on the area identified by Inmarsat, south of the previous search site.
24 June	Media	British director of commercial operations for Malaysia Airlines, Hugh Dunleavy says that he believes MH370 ended somewhere in the Southern Indian Ocean but warns that the search operation could take decades.
26 June	Search	Australia announced a new search area of up to 60,000 km2 (23,000 sq mi) in the southern Indian Ocean, based on a report by the ATSB. A bathymetric survey, already underway, of the region will take around three months to complete; the new underwater search is expected to begin in August. Australia & Malaysia are working on a Memorandum of Understanding to cover financial and co-operation arrangements for search and recovery activities.
	Investigation	Among other details, the ATSB report concluded that an unresponsive crew or hypoxia event "best fit the available evidence" for the 5-hour period of the flight as it travelled south over the Indian Ocean, likely on autopilot.
6 July	Search	Malaysian Defense minister Hishammuddin Hussein announces that Malaysia will be deploying more ships and equipment to assist in the search.
17 July	Search	Malaysia Airlines Flight 17 (MH17), flying from Amsterdam to Kuala Lumpur crashes in Ukraine. A Malaysian minister says this will not affect the search for MH370.
21 July	Search	The head of the JACC, who is co-ordinating the search effort for MH370, is sent to Ukraine to oversee the recovery of the remains of the passengers of MH17.
6 August	Search	Australia awards Fugro a AU$50 million contract to conduct a search of 60,000 km2 of seafloor near Broken Ridge starting in September. They will be assisted by one Chinese & four Malaysian vessels.
14 August	Media	A couple is arrested after taking ₤20,059 from the HSBC bank accounts of MH370 passengers.
20 September	Search	Zhu Kezhen finished bathymetric survey operations and began return passage to China.
6 October	Search	The fifth phase of the search begins. GO Phoenix, which left port at Jakarta on 24 September, begins work about 1800 km west of Western Australia.
23 October	Search	Fugro Discovery commenced search operations.
26 October	Search	Fugro Equator ends its bathymetric survey operations and commenced passage to Fremantle, where it will be refitted and mobilized to join GO Phoenix and Fugro Discover in the underwater search. Over 150,000 square kilometres (58,000 sq mi) of seafloor have been surveyed. If necessary, bathymetric survey operations may recommence in the future.

In popular culture

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. The Discovery Channel broadcast a one-hour documentary about MH370 on 16 April 2014 titled Flight 370: The Missing Links.

An episode of the television documentary series Horizon entitled 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 fate Flight MH370 has been compared to that of the fictional TV Series Lost.

The program also examines such new technologies as black box streaming and ADSB, which may help prevent similar disappearances in the future. It concludes by noting that Ocean Shield had spent two months searching 850 square kilometres (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. On 8 October 2014, a modified version of the Horizon program was broadcast in the US by PBS as an episode of Nova, entitled Why Planes Vanish and with different narrator.

The first fictional account of the mystery was Scott Maka's MH370: A Novella, published on the three-month anniversary of the aircraft's disappearance.

See also

• List of aerial disappearances
• List of airline flights that required gliding
• List of unrecovered flight recorders

External links

• Accident description at the Aviation Safety Network
• MH 370 Preliminary Report – Preliminary report issued by the Malaysia Ministry of Transport. Dated 9 April 2014 and released publicly on 1 May 2014.
• MH370 – Definition of Underwater Search Areas – Report by the Australian Transport Safety Bureau, released 26 June 2014, and the most comprehensive report on MH370 publicly released at that time. The report focuses on defining the search area for the fifth phase, but in doing so provides a comprehensive overview/examination of satellite data, the failed searches, and possible "end-of-flight scenarios".
• ATSB investigation of Flight 370 - Webpage of Australian Transport Safety Bureau's investigation (Investigation number: AE-2014-054; Investigation title: "Technical assistance to the Department of Civil Aviation Malaysia in support of missing Malaysia Airlines flight MH370 on 7 March 2014 UTC")

Press releases

• Australian Maritime Safety Authority Original briefings and charts for the search in the Australian area. Includes MP3 and MP4 videos of Media Briefings. From 1 April 2014, communication regarding the MH370 search were issued by the Joint Agency Coordination Centre (JACC). The AMSA site does however include all charts, including those after 1 April.
• Australian Transport Safety Bureau
• Joint Agency Coordination Centre (JACC)
• Malaysia Airlines
• Prime Minister of Malaysia.
• Malaysian Ministry of Transport: Press Statements and Briefings from the Prime Minister, Minister of Defence and acting Minister of Transport, Director General of the Department of Civil Aviation and Director General of Immigration. Includes transcripts of questions and answers not available on other external links.
• US Department of Defense – MH370: news & photos regarding MH370 from the US Department of Defense (content is in the public domain)
• "Boeing 777-200 – Flight MH 370 – Malaysia Airlines" (Archive). Bureau d'Enquêtes et d'Analyses pour la Sécurité de l'Aviation Civile.