Malaysia Airlines Flight 370

Malaysia Airlines Flight 370

9M-MRO, the aircraft involved in the incident, photographed in 2011
Incident summary
Date	8 March 2014
Summary	Missing, search ongoing; one flaperon found
Site	Southern Indian Ocean (presumed)
Passengers	227
Crew	12
Fatalities	239 (all, presumed)[lower-alpha 1]
Aircraft type	Boeing 777-200ER
Operator	Malaysia Airlines
Registration	9M-MRO
Flight origin	Kuala Lumpur International Airport
Destination	Beijing Capital International Airport

Malaysia Airlines Flight 370
Search (JACC)  · Timeline Satellite communications analysis Unofficial disappearance theories
See also: List of aerial disappearances

Malaysia Airlines Flight 370 (MH370/MAS370)^{[lower-alpha 2]} was a scheduled international passenger flight that disappeared on 8 March 2014, while flying from Kuala Lumpur International Airport near Kuala Lumpur, Malaysia, to Beijing Capital International Airport in Beijing, China. The flight 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. The aircraft disappeared from air traffic controllers' radar screens at 01:22 MYT.^[3] Malaysian military radar continued to track the aircraft as it deviated from its planned flight path and crossed the Malay Peninsula. It left the range of Malaysian military radar at 02:22 while over the Andaman Sea, 200 nautical miles (370 km) northwest of Penang in northwestern Malaysia.^[4]:3[5] The aircraft, a Boeing 777-200ER, was carrying 12 Malaysian crew members and 227 passengers from 15 nations.^[3]

A multinational search effort 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^[6][7] extended to the Strait of Malacca and Andaman Sea.^[8][9][10] 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.^[11][12][13] Australia took charge of the search effort on 17 March, when the search shifted to the southern Indian Ocean.^[14] On 24 March 2014, 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."^{[11][12][13][15]} The current phase of the search is a comprehensive search of the seafloor about 1,800 kilometres (970 nmi) southwest of Perth, Western Australia, which began in October 2014.^[16][17][18] Despite the largest and most expensive search in aviation history,^{[19][20][21][22]} nothing was found of the aircraft until 29 July 2015, when a piece of marine debris, later confirmed to be a flaperon from Flight 370, was found on Réunion Island.^{[23][24][25][26]} The bulk of the aircraft has still not been located, prompting many theories about its disappearance.

Malaysia established the Joint Investigation Team (JIT) to investigate the incident, working with foreign aviation authorities and experts.^[4]:1 Neither the crew nor the aircraft's communication systems relayed a distress signal, indications of bad weather, or technical problems before the aircraft vanished.^[27] Two passengers travelling on stolen passports were initially suspected in the disappearance, but they were later determined to be asylum seekers and it has been ruled out that they were terrorists.^[28][29][30] Malaysian police have identified the Captain as the prime suspect if human intervention was the cause of the disappearance, after clearing all other passengers of any suspicious motives.^[31] 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.^[4]:22 Based on analysis of the satellite communications, the aircraft turned south after passing north of Sumatra and flew for five hours with little deviation in its track, ending when fuel was exhausted.^{[4]:34[32][33][34]}

If the presumed loss of all on board is confirmed, Flight 370 would be the second deadliest incident involving a Boeing 777 and the second deadliest incident in Malaysia Airlines' history, behind Flight 17.^[35][36][37] Malaysia Airlines was struggling financially, a problem which was exacerbated by a decline in ticket sales after Flight 370 disappeared and before the crash of Flight 17; the airline was renationalised by the end of 2014. The Malaysian government received significant criticism, especially from China, for failing to disclose information in a timely manner during the early weeks of the search. Flight 370's disappearance brought to the public's attention the limits of aircraft tracking and flight recorders, including several issues raised four years earlier—but never mandated—following the loss of Air France Flight 447. A task force set up by the International Air Transport Association, with the support of the International Civil Aviation Organization, proposed a new standard that commercial aircraft must report their position every 15 minutes by December 2015.^[38][39] The Malaysian Ministry of Transport issued an interim report on 8 March 2015.^[40][41]

Disappearance

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 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).^[42][43] On board Flight 370 were 227 passengers, 10 cabin crew, two pilots (a captain and a first officer), and 14,296 kg (31,517 lb) of cargo.^{[40]:1, 12, 30}

The planned flight duration was 5 hours, 34 minutes, which would consume an estimated 37,200 kg (82,000 lb) of jet A-1 fuel.^{[40]:1, 30} The aircraft carried 49,100 kilograms (108,200 lb) of jet fuel, including reserves, which allowed an endurance of 7 hours, 31 minutes.^{[40]: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.^[40]:30

Departure

At 00:42 MYT, Flight 370 took off from runway 32R,^[40]:1 and was cleared by air traffic control (ATC) to climb to flight level 180^{[lower-alpha 3]}—approximately 18,000 feet (5,500 m)—on a direct path to navigational waypoint IGARI (located at 6° 56' 12N 103° 35' 6E). 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.^[40]: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.^[44] At 00:46, Lumpur Radar cleared Flight 370 to flight level 350^{[lower-alpha 3]}—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.^{[40]:1–2[45]}

Communication lost

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:07 MYT;^{[4]:2[46][47]:36} among the data provided in the message was total fuel remaining—43,800 kg (96,600 lb).^[48]:9 The final verbal contact with air traffic control occurred at 01:19:30, when Captain Shah^[40]:21 acknowledged a send-off by Lumpur Radar to Ho Chi Minh ACC:^{[lower-alpha 4][40]:2[45][49]}

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.^[50][51] The captain of another aircraft attempted to reach the crew of Flight 370 "just after [01:30]"^[52] 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 only heard "mumbling" and static.^[52] Calls made to Flight 370's cockpit at 02:39 and 07:13 were unanswered but acknowledged by the aircraft's satellite data unit.^{[4]:18[47]:40}

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.^[40]: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 claims that the aircraft was at the nearby waypoint BITOD.^[40]:2[45] Air traffic control uses secondary radar, which relies on a signal emitted by a transponder on aircraft; therefore, the transponder was no longer functioning on Flight 370 after 01:21. The final data from the transponder indicated that the aircraft was flying at its assigned cruise altitude of flight level 350^{[lower-alpha 3]} and was travelling at 471 knots (872 km/h; 542 mph) true airspeed.^[53] There were few clouds around this point and no rain or lightning nearby.^[40]:33–36 Later analysis estimated that Flight 370 had 41,500 kg (91,500 lb) of fuel when it disappeared from secondary radar.^[40]:30

At the time that the transponder stopped functioning—01:21:13—military radar showed Flight 370 turning right, but "almost immediately"^[40]:3 the aircraft began a left turn to a southwesterly direction.^[40]:3 From 01:30:35–01:35, military radar showed Flight 370 at 35,700 ft (10,900 m)^{[lower-alpha 5]} on a 231° magnetic heading, with a ground speed of 496 knots (919 km/h; 571 mph).^[40]:3 Flight 370 continued across the Malay Peninsula, fluctuating between 31,000–33,000 ft (9,400–10,100 m) in altitude.^[40]: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."^{[lower-alpha 6][40]:3–4} At 01:52, Flight 370 was detected passing just south of Penang Island. From there, the aircraft flew across the Strait of Malacca to, or close to, the waypoint VAMPI, passing over Pulau Perak at 02:03, after which it flew along air route N571 to waypoints MEKAR, NILAM, and possibly IGOGU.^{[4]:3, 38} The last known location, from and near the limits of Malaysian military radar, was at 02:22, 10 nmi (19 km; 12 mi) after passing waypoint MEKAR^{[40]:3, 7} and 200 nmi (370 km; 230 mi) northwest of Penang at an altitude of 29,500 ft (9,000 m).^[54][55]

Countries were reluctant to release information that they may have collected from military radar in the region where Flight 370 disappeared because of sensitivity about revealing military radar 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.^[45][40]:4 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.^[40]:4[56] 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. ^[40]:4–5 Thai military detected a plane that might have been Flight 370, but it isn't known whether it was, or what time the last radar contact was made. The radar signal did not include identifying data such as flight number.^[57] No radar contact was detected by Australia, including the 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.^[58]

Satellite communication resumes

At 02:25 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—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 and 07:13, which went unanswered by the cockpit.^[4]:18[47] The final status request and aircraft acknowledgement occurred at 08:10. 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.^{[4][47][59][60]}

Response by air traffic control

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 contact with Flight 370, which was last detected by radar at waypoint BITOD. The two centres exchanged four more calls over the next 20 minutes with no new information.^[45][61]

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.^[45] 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.^[61] 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 contact with Flight 370.^[45] 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′00″N 109°15′00″E / 14.90000°N 109.25000°E / 14.90000; 109.25000.^[45][61] Later, another Malaysia Airlines aircraft, Flight 386 bound for Shanghai, at the request of Ho Chi Minh ACC, attempted 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.^[45][62]

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."^[45] Over the next hour, Kuala Lumpur ACC contacted Ho Chi Minh ACC asking whether they had contacted Chinese air traffic control. At 05:09, Singapore ACC was queried for information about Flight 370. At 05: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."^[45]

The watch supervisor at Kuala Lumpur ACC activated the Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) at 05:30, over four hours after communication was lost with Flight 370.^[61] 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 time of the flight at Beijing, stating that contact with the flight had been lost by Malaysian ATC at 02:40 and that the government had initiated search and rescue operations;^[3] the time when contact was lost was later corrected to 01:21.^[3] 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.^[27]

Timeline of disappearance

Flight time elapsed (HH:MM)	Time		Event
	MYT	UTC
1:52 prior	7 March		Captain Zaharie Ahmad Shah[3][63] signs in for duty.[40]:1
	22:50	14:50
1:28 prior	23:15	15:15	First Officer Fariq Abdul Hamid[3][63] signs in for duty.[40]:1
00:42 prior	8 March	16:00	The aircraft's SDU logs onto the Inmarsat satellite communication network.[47]:3
	00:00
00:13 prior	00:27	16:27	ATC gives Flight 370 clearance to pushback from the gate.[40]:1
00:01:23 prior	00:40:37	16:40:37	ATC gives Flight 370 clearance to take off.[40]:1
00:00	00:42	16:42	Flight 370 takes off from runway 32R at Kuala Lumpur International Airport.[40]:1
00:01	00:42:53	16:42:53	ATC gives Flight 370 clearance to climb to Flight Level 180, approximately 18,000 ft (5,500 m)[lower-alpha 3] and proceed directly to waypoint IGARI.[40]:1
00:04	00:46:39	16:46:39	Flight 370 is transferred from the airport's ATC to Lumpur Radar ATC.[40]:2 Both the airport and Lumpur Radar ATC are based at the Kuala Lumpur Area Control Centre (KL ACC).[40]:87–95
00:05	00:46:58	16:46:58	ATC gives Flight 370 clearance to climb to Flight Level 250; approximately 25,000 feet (7,600 metres).[40]:2
00:08	00:50:08	16:50:08	ATC gives Flight 370 clearance to climb to Flight Level 350; approximately 35,000 feet (11,000 metres).[40]:2
00:19	01:01:17	17:01:17	The captain[lower-alpha 7] informs ATC that Flight 370 has reached Flight Level 350.[40]:2
00:25	01:07:48	17:07:48	The final data transmission from Flight 370 using the ACARS protocol is made.[40]:1[47]:36
00:25–01:22	01:07:48–02:03:41	17:07:48–18:03:41	The satellite communication link is lost sometime during this period.[47]:36
00:25	01:07:56	17:07:56	The captain confirms that Flight 370 is flying at Flight Level 350.[40]:2
00:37	01:19:30	17:19:30	KL ACC instructs the crew to contact Ho Chi Minh ACC (HCM ACC). The aircraft passes waypoint IGARI as the captain replies, "Good night. Malaysian three seven zero." This is the final voice contact with Flight 370.[40]:2
00:39	01:21:13	17:21:13	The position symbol of Flight 370 disappears from KL ACC radar, indicating the aircraft's transponder is no longer functioning.[40]:2 Malaysian military radar continues to track the aircraft, which "almost immediately"[40]:3 begins a turn to the left until it is travelling in a south-westerly direction.[40]:3
00:48	01:30	17:30	Voice contact is attempted by another aircraft at the request of HCM ACC; mumbling and radio static are heard in reply.[52]
00:55	01:37	17:37	An expected half-hourly ACARS data transmission is not received.[46]
00:56	01:39	17:38	HCM ACC contacts KL ACC to inquire about Flight 370. HCM ACC says verbal contact was not established and Flight 370 disappeared from its radar screens near waypoint BITOD. KL ACC responds that Flight 370 did not return to its frequency after passing waypoint IGARI.[40]:2[45]
01:04	01:46	17:46	HCM ACC contacts KL ACC and informs them that radar contact with Flight 370 was established near IGARI but lost near BITOD and that verbal contact was never established.[45]
01:15	01:57	17:57	HCM ACC informs KL ACC there was no contact with Flight 370, despite attempts on many frequencies and aircraft in the vicinity.[45]
01:21	02:03:41	18:03:41	Malaysia Airlines dispatch centre sends a message to the cockpit instructing the pilots to contact Vietnam ATC, to which there is no response.[64] A ground-to-aircraft ACARS data request, transmitted from the ground station multiple times between 02:03–02:05, is not acknowledged by the aircraft's satellite data unit.[47]:36–39
01:21	02:03:48	18:03:48	KL ACC contacts HCM ACC and relays information from Malaysia Airlines' operations centre that Flight 370 is in Cambodian airspace.[45]
01:33	02:15	18:15	KL ACC queries Malaysia Airlines' operations centre, which replies that it is able to exchange signals with Flight 370, which is in Cambodian airspace.[45]
01:36	02:18	18:18	KL ACC contacts HCM ACC asking them whether 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; Cambodia had no information about, or contact with, Flight 370.[45]
01:40	02:22	18:22	The last primary radar contact is made by the Malaysian military, 200 nautical miles (370 km; 230 mi) north-west of Penang, 6°49′38″N 97°43′15″E / 6.82722°N 97.72083°E / 6.82722; 97.72083 (Last primary radar contact, 8 March)[4]:3
01:43	02:25	18:25	A "log-on request" is sent by the aircraft on its satellite communication link to the Inmarsat satellite communications network. The link is re-established after being lost for between 22 and 68 minutes.[4]:18[47]:39 This communication is sometimes erroneously referred to as the first hourly "handshake" after the flight's disappearing from radar.[59][65]
01:52	02:34	18:34	KL ACC queries Malaysia Airlines' operations centre about communication status with Flight 370, but it is not sure whether a message sent to Flight 370 was successful.[45]
01:53	02:35	18:35	Malaysia Airlines' operations centre informs KL ACC that Flight 370 is in a normal condition based on signals from the aircraft located at 14°54′00″N 109°15′00″E / 14.90000°N 109.25000°E / 14.90000; 109.25000 (Northern Vietnam) at 18:33 UTC. KL ACC relays this information to HCM ACC.[45]
01:57	02:39	18:39	A ground-to-aircraft telephone call, via the aircraft's satellite link, goes unanswered.[4]:18[47]:40
02:48	03:30	19:30	Malaysia Airlines' operations centre informs KL ACC that position information was based on flight projection and is not reliable for aircraft tracking. Between 03:30 and 04:25, KL and HCM ACCs query Chinese air traffic control.[45]
02:59	03:41	19:41	Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[47]:40
03:59	04:41	20:41	Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[47]:40
04:27	05:09	21:09	Singapore ACC queried for information about Flight 370.[45]
04:59	05:41	21:41	Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[47]:40
05:48	06:30	22:30	Flight 370 misses its scheduled arrival at Beijing Capital International Airport.
05:50	06:32	22:32	The Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) is activated.[40]:2
05:59	06:41	22:41	Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[47]:40
06:31	07:13	23:13	A ground-to-aircraft telephone call placed by Malaysia Airlines,[64] via the aircraft's satellite link, goes unanswered.[4]:18[47]:40
06:42	07:24	23:24	Malaysia Airlines issues a press statement announcing that Flight 370 is missing.[3]
07:29	08:11	8 March	The last successful automated hourly handshake is made with the Inmarsat satellite communication network.[47]:41[59]
		00:11
07:37	08:19:29	00:19:29	The aircraft sends a "log-on request" (sometimes referred to as a "partial handshake") to the satellite.[66][67] Investigators believe this follows a power failure between the time the engines stopped due to fuel exhaustion and the emergency power generator starting.[4]:18, 33[47]:41
07:37	08:19:37	00:19:37	Following a response from the ground station, the aircraft replies with a "log-on acknowledgement" message at 08:19:37.443. This is the final transmission received from Flight 370.[4]:18[47]:41
08:33	09:15	01:15	The aircraft does not respond to an hourly, automated handshake attempt.[47]:41[59]

Reported sightings

The news media reported several sightings of an aircraft that fit the description of the missing aircraft. For example, on 19 March 2014, CNN reported that "several people on the ground or at sea claimed they saw Malaysia Airlines Flight 370 before it went missing after its post-midnight takeoff from Kuala Lumpur on March 8. The purported eyewitnesses include fishermen, an oil rig worker and islanders in the Kuda Huvadhoo atoll in the Maldives. Some even alleged they saw it crash. While none of their claims have been substantiated, their assertions added to the ongoing mystery of the missing Boeing 777 and the 239 people aboard."^[68]

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."^[69] Three months later, the London Telegraph reported that "a British woman sailing with her husband across the Indian Ocean from India to Thailand has claimed she may have seen the missing Malaysia Airlines plane on fire. Katherine Tee, 41, was on night watch on March 7–8 but said she did not report the sighting until Sunday because she was having marital problems and thought she was losing her mind."^[70]

Presumed loss

On 24 March, Malaysian Prime Minister Najib Razak appeared before media at 22:00 local time to give a short statement regarding Flight 370, during which he announced:

This evening I was briefed by representatives from the UK Air Accidents Investigation Branch. They informed me that Inmarsat, the UK company that provided the satellite data which indicated the northern and southern corridors, has been performing further calculations on the data. 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.^[15]

Just before Najib spoke at 22:00 MYT, an emergency meeting was called in Beijing for relatives of Flight 370 passengers.^[15] 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 (in English and Chinese):^[15]

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.^[11][12][13]

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:^[1]

We have concluded that the aircraft exhausted its fuel over a defined area of the southern Indian Ocean, and that the aircraft is located on the sea floor close to that defined area. This is a remote location, far from any possible landing sites. It is also an area with adverse sea conditions with known depths of more than 6,000 metres. After 327 days...and based on all available data as well as circumstances mentioned earlier, survivability in the defined area is highly unlikely....On behalf of the Government of Malaysia, we officially declare Malaysia Airlines flight MH370 an accident in accordance with the Standards of Annexes 12 and 13 to the Chicago Convention and that all 239 of the passengers and crew onboard MH370 are presumed to have lost their lives.^[1]

If the official assumption is confirmed, Flight 370 was the deadliest aviation incident in the history of Malaysia Airlines at the time of its disappearance, 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).^[35][36] 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.^[37]

Debris discovered

On 29 July 2015, airliner marine debris was found 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.^[71] The object had a stenciled internal marking "657 BB," consistent with the code for a portion of a right wing flaperon (a trailing edge control surface) from a Boeing 777.^[23][72] The following day, a damaged suitcase was found which may be associated with Flight 370.^[73] 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.^{[71][74][75][76]} On 31 July, a Chinese water bottle and an Indonesian cleaning product were found in the same area.^[77][78] There have been many claims that additional debris had been found on Réunion which may have come from Flight 370, but none appears to have come from an aircraft as of 5 August.^[75][79]

The first object to be found was transported from Réunion—an overseas department of France—to Toulouse, for examination 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.^[71] Malaysia sent investigators to both Réunion and Toulouse.^[71][80] French police conducted a search of the waters around Réunion for additional debris.^[71]

On 2 August, Malaysian officials confirmed that the object was a flaperon from a Boeing 777 aircraft and that the verification was made with investigators from France, Malaysia, Boeing, and the US National Transportation Safety Board (NTSB).^[81] Three days later, the Prime Minister of Malaysia announced that the discovered flaperon was confirmed to be from Flight 370; French officials only stated that there was a "very high probability"^[82] that the object was from Flight 370.^[82][83][84] On 3 September, French officials announced that serial numbers found on the flaperon link it "with certainty"^[85] to Flight 370. This serial number was retrieved via borescope.^[85][86][87]

• 

  Boeing 777 flaperon

• 

  Location of found debris relative to Flight 370's flight path and the current search area

• 

  Currents within the Indian Ocean

Search

A search and rescue effort was launched soon after the aircraft's disappearance in Southeast Asia. However, the following week, analysis of communications between the aircraft and a satellite determined that the aircraft had continued flying for several hours and that the final transmission from the aircraft was made over the Southern Indian Ocean, west of Australia. The surface search in the southern Indian Ocean between 18 March and 28 April searched over 4,600,000 square kilometres (1,800,000 sq mi) and involved 19 vessels and 345 search sorties by military aircraft.^[88] The current phase of the search is a bathymetric survey and sonar search of the seafloor, about 1,800 kilometres (970 nmi; 1,100 mi) southwest of Perth, Australia.^[16] Since 30 March 2014, the search has been 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 involves the Malaysian, Chinese, and Australian governments.^[89]

The search for Flight 370 is the most expensive search operation in aviation history.^{[19][20][90][91]} In June 2014, Time estimated that the total search effort to that point had cost approximately US$70 million.^[92] The tender for the underwater search is AU$52 million (US$43 million or €35 million)—shared by Australia and Malaysia—for 12 months, but would differ if found in more or less time.^[17]

Southeast Asia

The Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) was activated at 05:30 MYT—four hours after communication was lost with Flight 370—to co-ordinate search and rescue efforts.^[61] Search efforts began in the Gulf of Thailand and South China Sea. On the second day of the search, Malaysian officials revealed that radar recordings indicated Flight 370 may have turned around; the search zone was expanded to include part of the Strait of Malacca.^[93] 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 Penang Island; search efforts were subsequently increased in the Andaman Sea and Bay of Bengal.^[55]

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 publicly disclosed, 15 March, authorities announced they would abandon search efforts in the South China Sea, Gulf of Thailand, and Strait of Malacca to focus 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.^[94][95][96]

Southern Indian Ocean

The focus of the search shifted to the Southern Indian Ocean west of Australia and within Australia's concurrent aeronautical and maritime Search and Rescue regions that extend to 75°E longitude.^[97][98] Accordingly, on 17 March, Australia agreed to lead the search in the southern locus from Sumatra to the southern Indian Ocean.^[14][99]

Initial search

From 18–27 March, the search effort focused on a 305,000 km² (118,000 sq mi) area about 2,600 km (1,400 nmi; 1,600 mi) south-west of Perth^[100] 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.^[101][102] Satellite imagery of the region was analysed; several objects of interest and two possible debris fields were identified on images captured between 16–26 March. None of these possible objects were found by aircraft or ships.^[103]

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) north-east of the previous area on 28 March,^{[104][105][106]} which was followed by another shift on 4 April.^[107][108] An intense effort began to locate 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.^[109][110] Two ships equipped with towed pinger locators (TPLs) and a submarine equipped with a hull-mounted acoustic system^[4]:11–12 began searching for pings along a 240-kilometre (150 mi) seabed line believed to be the Flight 370 impact area.^{[109][111][112]} Operators considered it a shot in the dark,^[113] when comparing the vast search area with the fact that a TPL could only search up to 130 km² (50 sq mi) per day.^[113] 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.^[4]: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.^[4]:14 In a March 2015 report, it was revealed that 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.^[114][115]

Underwater search

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

In late June, details of the next phase of the search were announced;^[116] officials have called this phase the "underwater search", despite the previous seafloor sonar survey.^[18] Continued refinement of 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 within the wide area search is in its southern extent.^[117] Some of the equipment to be used for the underwater search operates best when towed 200 m (650 ft) above the seafloor at the end of a 10 km (6 mi) cable.^[118] Available bathymetric data for this region was of poor resolution, thus necessitating a bathymetric survey of the search area before the underwater phase began.^[119] 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 for the ship conducting the survey to be mobilised in the underwater search.^[120]

The underwater phase of the search, which began on 6 October 2014,^[117] uses three vessels equipped with towed deep water vehicles, which use side-scan sonar, multi-beam echo sounders, and video cameras to locate and identify aircraft debris.^[121] A fourth vessel participated in the search between January–May 2015; it had an autonomous underwater vehicle (AUV) to search areas which cannot be effectively searched by equipment on the other vessels.^{[122][123][124]} The governments of Malaysia, China, and Australia have agreed to thoroughly search 120,000 km² (46,000 sq mi) of seafloor.^[125] As of 27 January 2016, over 85,000 km² (33,000 sq mi) of seafloor have been searched during the underwater phase of the search and the current phase is expected to be completed around the middle of 2016.^[126]

Following the discovery of the flaperon on Réunion, the ATSB reviewed their drift calculations for debris from the aircraft and, according to the JACC, they are "satisfied that the discovery of the flaperon at La Réunion ... is consistent with the current underwater search area in the southern Indian Ocean."^[75] Reverse drift modelling of the debris, to determine its origin after 16 months, also supports the current underwater search area, although reverse drift modelling is very imprecise over long periods of time.^[75]

Marine debris

A week after the discovery of a flaperon from Flight 370 on a beach on Réunion, France announced plans for an aerial search for possible marine debris around the island. On 7 August 2015, France began searching an area 120 km (75 mi) by 40 km (25 mi) along the east coast of Réunion.^[82] Foot patrols for debris along beaches were also planned.^[79] Malaysia asked authorities in neighboring states to be on alert for marine debris which could be from an aircraft.^[127] 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.^[128] Air and sea searches for debris ended on 17 August.^[129]

Aircraft

Wikimedia Commons has media related to aircraft 9M-MRO.

Flight 370 was operated with a Boeing 777-2H6ER,^{[lower-alpha 8]} serial number 28420, registration 9M-MRO. It was the 404th Boeing 777 produced,^[131] 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^[131] and configured to carry 282 passengers.^[132] It had accumulated 53,471.6 hours and 7,526 cycles in service^[40]:22 and had not previously been involved in any major incidents,^[133] though a minor incident while taxiing at Shanghai Pudong International Airport in August 2012 resulted in a broken wing tip.^[134][135] Its last maintenance "A check" was carried out on 23 February 2014.^[136] The aircraft was in compliance with all applicable Airworthiness Directives for the airframe and engines.^[40]: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.^[40]:27

The Boeing 777 was introduced in 1994 and is generally regarded by aviation experts as having a safety record that is one of the best of any commercial aircraft.^[35][36] Since its first commercial flight in June 1995, there have been only four other serious incidents involving hull-loss: British Airways Flight 38 in 2008; a cockpit fire in a parked EgyptAir Flight 667 at Cairo International Airport in 2011;^[137][138] the crash of 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.^[37][139]

Passengers and crew

People on board by nationality

Nationality	No.
Australia	6
Canada	2
China	152
France	4
Hong Kong[lower-alpha 9]	1
India[141]	5
Indonesia	7
Iran[lower-alpha 10]	2
Malaysia[lower-alpha 11]	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.^[142]

Crew

All 12 crew members were Malaysian citizens. Two pilots were among the crew:^[143]

• 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 the 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.^{[40]:13[143][144]}
• 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 on 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.^{[40]:14[145][146]}

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.^[147] Twenty passengers—12 of whom were from Malaysia and eight from China—were employees of Freescale Semiconductor.^[148][149]

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.^[150][151] The airline also sent its own team of caregivers and volunteers^[152] 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.^[153] Altogether, 115 family members of the Chinese passengers flew to Kuala Lumpur.^[154] Some other family members chose to remain in China, fearing they would feel too isolated in Malaysia.^[155]

Investigation

International participation

Malaysia set up a Joint Investigation Team (JIT), composed of specialists from Malaysia, Australia, China, the UK, the US, and France,^[4]:1[156] led according to ICAO standards by "an independent investigator in charge".^{[157][158][159]} 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.^[160] 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.^[160] The criminal investigation is being led by the Royal Malaysia Police,^[1]:9 assisted by Interpol and other relevant international law enforcement authorities.^[161][162]

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 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 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^{[lower-alpha 12]} (Australia), Department of Civil Aviation (Malaysia), Inmarsat (UK), National Transportation Safety Board (US), and Thales (UK).^{[4]:1[164][165]}

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.^[166]

Analysis of satellite communication

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.^{[4]:16–17[65]}

Background

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^[167] using other protocols.^{[65][168][169]} The aircraft's satellite data unit (SDU) is used to send and receive signals with the satellite communications network; it operates independently of 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.^[4]:17[169] 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.^[169] After connecting, if a ground station has not received any contact from a terminal for one hour,^{[lower-alpha 13]} the ground station will transmit a "log-on interrogation" message—informally referred to as a "ping";^[4]:18 an active terminal responds automatically. The entire process of interrogating the terminal is referred to as a 'handshake'.^[59][170]

Communications from 02:25 to 08:19 MYT

Although the ACARS data link on Flight 370 stopped functioning between 01:07 and 02:03 MYT,^[47]:36 the SDU remained operable.^[4] 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):^{[4]:18[47][lower-alpha 14]}

• 02:25:27 – First handshake – a 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 two transmissions:^[47]

• 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.^[47]

Deductions

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.^[171]: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.^{[59][60][170]} The log-on message sent from the aircraft at 08:19:29 was "log-on request".^[4]: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.^[4]:22 Investigators consider the most likely reason to be that it was sent during power-up after an electrical outage.^[4]:33 At 08:19, the aircraft had been airborne for 7 h 38 min; the typical Kuala Lumpur-Beijing flight is 5¹⁄₂ hours and fuel exhaustion was likely.^{[4]:33[4]:33[172]} 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.^[4]: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 starvation scenario.^[4]:22

Analysis

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 can be analysed to determine the distance between the satellite and the aircraft and results in a ring on the Earth's surface that is equidistant from the satellite at the calculated distance, which can be reduced to arcs by eliminating parts of the rings outside the aircraft's range.^{[4]:18[171]: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 aging; and compensation applied by the SDU to counter the Doppler shift on the uplink. This measure can be analysed to determine the aircraft's speed and heading, but multiple combinations of speed and heading can be valid solutions.^{[4]:18[171]: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.^{[4]:18, 25–28[174]: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 percent 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.^[174]:12

Possible in-flight events

Power interruption

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".^{[4]:22[47]: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.^[4]:33[175] 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.^[4]:33

Unresponsive crew or hypoxia

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 starvation), and an unresponsive crew or hypoxia event—concluded that an unresponsive crew or hypoxia event "best fit the available evidence"^[4]: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,^[4]:34 likely on autopilot.^[32][33][34] There is no consensus among investigators on the unresponsive crew or hypoxia theory.^[32] If no control inputs were made following flameout and the disengagement of autopilot, the aircraft would likely have entered a spiral dive^[4]:33 and entered the ocean within 20 nmi (37 km; 23 mi) of the flameout and disengagement of autopilot.^[4]:35

Possible causes of disappearance

Passenger involvement

Two men boarded Flight 370 with stolen passports, which raised suspicion in the immediate aftermath of its disappearance.^[176][177] The passports, one Austrian and one Italian, were reported stolen in Thailand within the preceding two years.^[176] 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.^[178][179] 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.^[179] The two one-way tickets purchased for the holders of the stolen passports were booked through China Southern Airlines.^[176] It was reported that an Iranian had ordered the cheapest tickets to Europe via telephone in Bangkok, Thailand, and paid in cash.^[180][181] 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 organization was "inclined to conclude that it was not a terrorist incident".^[28] The two men were believed to be asylum seekers.^[29][30]

United States and Malaysian officials were reviewing the backgrounds of every passenger named on the manifest.^[147] 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.^[182] 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.^[183]

Crew involvement

Investigators believe someone in the cockpit of Flight 370 re-programmed the aircraft's autopilot before it travelled south across the Indian Ocean.^[184][185] 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.^[186][187] 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.^[188][189]

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.^{[31][190][191][192]} The United States' Federal Bureau of Investigation reconstructed the deleted data from Captain Shah's home flight simulator; a Malaysian government spokesman indicated that "nothing sinister"^[193] had been found on it.^[193][194] The preliminary report issued by Malaysia in March 2015 states that there was "no evidence of recent or imminent significant financial transactions carried out"^[40]:20 by any of the pilots or crew and that analysis of the behaviour of the pilots on CCTV showed "no significant behavioural changes".^[40]:21

Cargo

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.^{[40]:103, 108–109} The four ULDs of mangosteens were loaded into the aft cargo bay of the aircraft.^[40]: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.^[40]:106

There were 221 kg (487 lb) of lithium-ion batteries contained within 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.^[40]:103 The lithium-ion 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 truck to transport it to Kuala Lumpur International Airport and onwards by air to Beijing.^[40]: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.^[40]:104 The consignment did not go through any additional inspections at Kuala Lumpur International Airport before it was loaded onto Flight 370.^[40]:104 Because the lithium-ion batteries were packaged in accordance with IATA guidelines,^{[lower-alpha 15]} they were not regulated as dangerous goods.^[40]:106 Lithium-ion batteries can cause intense fires if they overheat and ignite, which has led to strict regulations on their transport aboard aircraft.^[195][196] A fire fueled 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.^{[196][197][198]} Some airlines have stopped carrying bulk shipments of lithium-ion batteries on passenger aircraft, citing safety concerns.^[196][197]

A 4,566 kg (10,066 lb) consignment of mangosteens was aboard Flight 370, over half of which was harvested in Muar, Malaysia and the remainder from Sumatra, Indonesia.^[40]:107 The mangosteens were packaged in plastic baskets containing 8–9 kg (18–20 lb) of mangosteens and covered with a water-soaked sponge to preserve their freshness.^[40]:108 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.^[40]:108 According to the head of Malaysian police, Inspector-General Tan Sir Khalid Abu Bakar, the people who handled the mangosteens and the Chinese importers were questioned to rule out sabotage.^[199][200]

Aftermath

Information sharing

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

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

Malaysia had initially declined to release raw data from its military radar, deeming the information "too sensitive,"^[216] but later acceded.^[216][217] 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."^[216] 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.^[216] 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.^[220]

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.^[65][221] 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.^[3] 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.^[222]

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.^[223][224] The campaign, which ended 8 August 2014, raised US$100,516 from 1007 contributors.^[223]

Malaysia Airlines

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 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."^[225] 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.^[225][226] In China, where the majority of passengers were from, bookings on Malaysia Airlines were down 60 percent in March.^[227]

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.^[228][229] 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.^[43][230]

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

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.^[225] Malaysia Airlines lost RM443.4 million (US$137.4 million) in the first quarter of 2014 (January–March).^[226] 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.^[234] 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.^[225] The company's stock, down as much as 20 percent following the disappearance of Flight 370, had fallen 80 percent over the previous five years, which contrasts with a rise in the Malaysian stock market of about 80 percent over the same period.^[227]

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.^{[235][236][237][238][239]} The loss of Flight 17 in July greatly exacerbated Malaysia Airline's financial problems. The combined effect on consumer confidence of the loss of Flights 370 and 17 and the airline's poor financial performance led Khazanah Nasional—the majority shareholder (69.37 percent)^[240] and a Malaysian state-run investment arm—to announce on 8 August its plan to purchase the remainder of the airline, thereby renationalising it.^{[241][242][243]}

Compensation for passengers' next-of-kin

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.^[244] 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^{[lower-alpha 17]} from the airline's insurance company—a total of nearly US$40 million for the 227 passengers on board.^[244]

Malaysia Airlines would still be vulnerable to civil lawsuits from passengers' families.^[244] 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.^{[245][246][247]} 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.^[248] 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,^{[lower-alpha 18]} 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.^[251]

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";^[252] but some families rejected the offer.^[253] It was also reported that Malaysian relatives received only $2,000.^[253] In June, Malaysia's deputy Foreign Minister Hamzah Zainuddin said that families of seven passengers received $50,000 advance compensation from Malaysia Airlines,^[254] but that full payout would come after the aircraft is found or officially declared lost^[255] (which later occurred in January 2015).^[248]

Malaysia

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. 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 has been criticised by many.^{[256][257][258][259]} The Malaysian military became aware of the unidentified flight only after reviewing radar recordings several hours after Flight 370's disappearance.^[258] Not only was the failure to recognise and react to the unidentified aircraft a security blunder, it was also a missed opportunity to intercept Flight 370 and prevent the time-consuming and expensive search operation.^[258][259]

Malaysian Prime Minister Najib Razak responded to criticism of his government in an opinion piece published in the The Wall Street Journal:

Without physical evidence, or a clear explanation for why this happened, peoples' attention has naturally focused on the authorities—and Malaysia has borne the brunt of the criticism. In the passage of time, I believe Malaysia will be credited for doing its best under near-impossible circumstances. It is no small feat for a country the size of ours to overcome diplomatic and military sensitivities and bring 26 different countries together to conduct one of the world's largest peacetime search operations. But we didn't get everything right...the response time should and will be investigated...I pledge that Malaysia will keep searching for the plane for as long as it takes.

— Malaysian Prime Minister Najib Razak, Malaysia's Lessons From the Vanished Airplane (The Wall Street Journal, 13 May 2014)^[260]

In the opinion piece, Najib goes 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."^[260]

Opposition leader Anwar Ibrahim strongly 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 has called for an international committee to take charge of the investigation "to save the image of the country and to save the country."^[261] 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.^[261]

Malaysia's Defence and Transport Minister Hishammuddin Hussein—a central figure in the search and investigation of Flight 370 and active on Twitter—was criticised for responding to/retweeting a tweet by a Malaysian journalist: "Right u are:) @IsmailAmsyar: #MH370 is a blessing in disguise 4 all of us. I understand now d [sic] beauty of unity & sweetness of having each other."^[262] The remarks were viewed as insensitive to the victims' families. Both tweets were removed.^[262][263] Questioned why Malaysia did not scramble fighter jets to intercept the aircraft as it tracked back across the Malay Peninsula, he 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?"^[264]

The poor response to the crisis and lack of transparency in the response has 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. Confronted by a foreign journalist about the slow response and conflicting information, Defence and Transport Minister Hishammuddin Hussein responded that he had received "a lot of feedback saying we’ve been very responsible in our actions...it’s very irresponsible of you to say that."^[265]

China

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 "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."^[67][266] The following day, 25 March, Chinese president Xi Jinping sent a special envoy to Kuala Lumpur to consult with the Malaysian government over the missing aircraft.^[267]

Relatives of passengers

On 25 March, around two hundred family members of the Chinese passengers protested outside the Malaysian embassy in Beijing.^[268][269] 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.^[270] However, it was also reported that some of the missing passengers were still visible on Tencent QQ, and some passengers' phones could be called though with no response.^[271] An op-ed for China Daily said that Malaysia was not wholly to be blamed for its poor handling of such a "bizarre"^[272] and "unprecedented crisis,"^[272] and appealed to Chinese people not to allow emotions to prevail over evidence and rationality.^[272] 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".^[273] The ambassador also strongly criticised Western media for having "published false news, stoked conflict and even spread rumours"^[274] to the detriment of relatives and of Sino–Malaysian relations.^[274] 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.^[275][276]

Boycotts

Some Chinese have boycotted all things Malaysian, including vacations and singers, in protest of Malaysia's handling of the Flight 370 investigation.^[277][278] Bookings on Malaysia Airlines from China, where the majority of passengers were from, were down 60 percent in March.^[227] In late March, several major Chinese ticketing agencies—ELong, LY.com, Qunar and Mango—discontinued sale of airline tickets to Malaysia^[277][279] and several large Chinese travel agencies reported a 50 percent drop in tourists compared to the same period the year before.^[230] China is the third largest source of visitors for Malaysia, accounting for 1.79 million tourists.^[230] One market analyst predicted a 20–40 percent 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).^[230][280]

The boycotts have largely been led or supported by celebrities.^[230][281] 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."^[230] The post was shared over 70,000 times and drew over 30,000 comments.^[230] 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."^[230]

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

Air transport industry

The fact that, in a digitally-connected world, a modern aircraft could disappear has been met with surprise and disbelief by the public; and while changes in the aviation industry often take years to be implemented, airlines and air transport authorities have responded swiftly to take action on several measures to prevent a similar incident from occurring.^{[282][283][284][285]}

Aircraft tracking

The International Air Transport Association—an industry trade organisation representing over 240 airlines (representing 84 percent of global air traffic)—and the International Civil Aviation Organization (ICAO)—the United Nations' civil aviation body—are working on implementing new measures to track aircraft in flight in real time.^[286] The IATA created a task force (which includes several outside stakeholders)^[286] to define a minimum 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 plans 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.^[287] 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.^[288][289] In December 2014, the IATA task force recommended that, within 12 months, airlines track commercial aircraft in no longer than 15-minute intervals, although it still has not released its report and full details of proposed changes. The IATA itself did not support the deadline, which it believes cannot be met by all airlines, but the proposed standard has 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.^[38][39]

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

Transponders

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.^[291] In the wake of Flight 370, the air transport industry is still resistant to the installation of automated transponders, which would likely entail significant costs. Pilots have 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 are being considered.^[284]

Flight recorders

The frenzied search for the flight recorders in early April, due to the 30-day battery life of the underwater locator beacons (ULBs) attached to them, brought attention to the limitations of the ULBs.^{[lower-alpha 19][292]} Not only is the battery life of the ULBs limited, but the nominal distance at which the signal from the ULBs can be detected is 2,000–3,000 m (6,600–9,800 ft), up to 4,500 m (14,800 ft) under favourable conditions.^[4]: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 is 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.^[293] 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.^[294][295]

A call to increase the battery life of ULBs was made after the unsuccessful initial search in 2009 for the flight recorders on Air France Flight 447, which were not located until 2011. The ICAO did not make such a recommendation until 2014, with implementation by 2018.^[294] The European Aviation Safety Agency has stated its new regulations require that the transmitting time of ULBs fitted to aircraft flight recorders must range from 30 to 90 days. The agency proposed a new underwater locator beacon with a larger transmitting range to be fitted to aircraft flying over oceans.^[287]

Safety recommendations

In January 2015, the US NTSB cited Flight 370 and Air France Flight 447 when it issued eight safety recommendations^{[lower-alpha 20]} 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.^[296][297]

Timeline of events

8 March 2014

Flight 370 disappears after departing Kuala Lumpur at 00:41 MYT (16:41 UTC, 7 March). A search and rescue effort is launched in the South China Sea and Gulf of Thailand.^[298]

10 March

Malaysia's military announces that Flight 370 may have turned back and flown west towards Malaysia. The search is expanded to include the Strait of Malacca.^[93]

12 March

Malaysia announces that Flight 370 crossed the Malay Peninsula and was last spotted on military radar 200 nmi (370 km; 230 mi) northwest of Penang on Malaysia's west coast. The focus of the search is shifted to the Andaman Sea and Strait of Malacca.^[55][299]

15 March

Officials announce that communications between Flight 370 and a communications satellite operated by Inmarsat indicate it continued to fly for several more hours and was along one of two corridors at the time of its last communication.^[94]

18 March – 28 April

Aerial search of the southern Indian Ocean, west of Australia, is conducted.^[4][300]

24 March

Prime Minister of Malaysia announces that Flight 370 is presumed to have gone down in the southern Indian Ocean; Malaysia Airlines states to families that it assumes "beyond reasonable doubt" there are no survivors.^[301] 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.^[302]

30 March

The Joint Agency Coordination Centre is created to co-ordinate the multinational search effort.^[303]

2–14 April

An intense effort by several vessels and aircraft-deployed sonobuoys is made to detect underwater acoustic signals made by underwater locator beacons attached to the aircraft's data recorders. Several acoustic detections are made between 4–8 April.^[4]

14 April – 28 May

A sonar survey of 860 km² (330 sq mi) of seafloor near the 4–8 April acoustic detections is conducted, yielding no debris.^[4]

1 May

A preliminary report from Malaysia to the ICAO (dated 9 April 2014) is publicly released along with: copies of cargo manifest documents; audio recordings (and transcript) of communications between air traffic control and Flight 370; a log of actions taken by air traffic control (Kuala Lumpur ACC) in the hours after Flight 370 disappeared from their radar (01:38–06:14 MYT).^[45]

27 May

The data logs of satellite communications between Flight 370 and Inmarsat are released, following criticism over the way this data had been analysed and scepticism of whether Flight 370 really ended in the southern Indian Ocean.^[304]

Video tour of bathymetry data collected during the bathymetric survey.

May–December

A bathymetric survey is conducted in the region to be searched.

26 June

Plans for the next phase of the search (the "underwater search") are announced to the public in-depth for the first time and the Australian Transport Safety Bureau releases a report^[4] detailing the previous search efforts, analysis of satellite communications, methodology used to determine the new search area.^[305]

October 2014–ongoing

The underwater search began on 6 October and was expected to last up to 12 months. The search is conducted in areas where the bathymetric survey has been completed.^[306][307]

8 October

Officials announce that the priority area to be searched is further south of the area identified in the June ATSB report.^[117] The ATSB releases a report (a supplement to the June report) that details the methodology behind refinements to the analysis of satellite communications.^[48]

29 January 2015

The Malaysian government officially declares Flight 370 an accident, in accordance with Annexes 12 and 13 to the Chicago Convention, with no survivors.^[1]

8 March

The Malaysian Ministry of Transport publishes an interim report.^[40]

29 July

A right wing flaperon, which was later confirmed to be from Flight 370,^[308] was found on the beach of Réunion Island in the Indian Ocean, 16 months after Flight 370 disappeared.^[71]

In popular culture

The disappearance of Malaysia Airlines Flight 370 has been dubbed one of the greatest aviation mysteries of all time.^[309]

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.^[310][311] The Discovery Channel broadcast a one-hour documentary about Flight 370 on 16 April 2014 titled Flight 370: The Missing Links.^[312][313]

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 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.^[314] On 8 October 2014, a modified version of the Horizon programme was broadcast in the US by PBS as an episode of Nova, titled "Why Planes Vanish", with a different narrator.^{[315][316][317]}

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

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.^[319]

See also

• Accidents and incidents involving the Boeing 777 family
• Air safety
• List of accidents and incidents involving commercial aircraft
• List of aerial disappearances
• List of airline flights that required gliding
• List of unrecovered flight recorders
• Search for Malaysia Airlines Flight 370

Notes

References

External links

• Official website – maintained by the Malaysian government
• Joint Agency Coordination Centre (JACC)
• Accident description at the Aviation Safety Network
• ATSB investigation of Flight 370 – webpage of Australian Transport Safety Bureau's investigation (Investigation number: AE-2014-054; Investigation title: "Assistance to Malaysian Ministry of Transport in support of missing Malaysia Airlines flight MH370 on 7 March 2014 UTC")
• ICAO statement on the first anniversary of the Flight 370 disappearance

Reports

• MH 370 Preliminary Report – Preliminary report issued by the Malaysia Ministry of Transport. Dated 9 April 2014 and released publicly on 1 May 2014.
• Factual Information: Safety Investigation for MH370 – Interim report released 8 March 2015 (584 pages).
• MH370 – Definition of Underwater Search Areas (2014) – Report by the Australian Transport Safety Bureau, released 26 June 2014, and the most comprehensive report on Flight 370 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".
• MH370 – Definition of Underwater Search Areas (2015) – Report by the Australian Transport Safety Bureau, released 3 December 2015, covering the Bayesian method analysis made by Australia's Defence Science and Technology Group and other developments since mid-2014 in defining the search area.

Press releases / Media

• Australian Maritime Safety Authority
• Australian Transport Safety Bureau
• Malaysia Airlines
• Malaysian Ministry of Transport
• US Department of Defense

← 2013 Aviation accidents and incidents in 2014 (2014) 2015 → Jan 20   Romania Britten-Norman Islander Feb 11   Algerian Air Force C-130 crash Feb 16   Nepal Airlines Flight 183 Feb 17   748 Air Services HS 748 Feb 17   Ethiopian Airlines Flight 702 Mar 8   Malaysia Airlines Flight 370 Mar 13   Haughey Air AgustaWestland AW 139 May 17   Lao People's Liberation Army Air Force An-74 Jun 14   Ukrainian Air Force Ilyushin Il-76 Jun 23   Olsberg mid-air collision Jul 17   Malaysia Airlines Flight 17 Jul 23   TransAsia Airways Flight 222 Jul 24   Air Algérie Flight 5017 Aug 10   Sepahan Airlines Flight 5915 Aug 13   Santos Cessna Citation accident Sep 5   Socata TBM crash Oct 20   Falcon 50 Vnukovo ground collision Oct 29   Skyway Enterprises Flight 7101 Oct 30   Wichita King Air crash Oct 31   VSS Enterprise crash Nov 12   Armenian Mil Mi-24 shootdown Dec 28   Indonesia AirAsia Flight 8501

Malaysia Airlines History Malayan Airways Malaysia–Singapore Airlines Accidents and incidents MH653 (1977; 100 fatalities) MH684 (1983; no fatalities) MH2133 (1995; 34 fatalities) MH370 (2014; missing with 239 people · search · timeline · unofficial disappearance theories) MH17 (2014; 298 fatalities · reactions) Services Destinations Fleet Subsidiaries Firefly MASkargo MASwings