#MalaysiaAirlines #MH370 Remembered With Love & Respect, Compilation of Facts

Malaysia Airlines Flight 370

Malaysia Airlines Flight 370

The missing aircraft, 9M-MRO, in 2011
Incident summary
Date	8 March 2014
Summary	Missing
Site	Unknown
Passengers	227
Crew	12
Fatalities	239 (all, presumed)[a]
Survivors	0 (none, presumed)[a]
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

Malaysia Airlines Flight 370 (MH370/MAS370)^[b] 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 inBeijing, China. Flight 370 last made voice contact with air traffic control at 01:19 MYT (17:19 UTC, 7 March) when it was over theSouth China Sea, less than an hour after takeoff. The aircraft disappeared from air traffic controllers' radar screens at 01:21.^[3][4]Malaysian military radar continued to track Flight 370 as it deviated from its planned flight path and crossed the Malay Peninsula. Flight 370 left the range of Malaysian military radar at 02:22 while over the Andaman Sea, 200 nautical miles (370 km; 230 mi) northwest of Penang in northwestern Malaysia.^[5]:3[6] The aircraft, a Boeing 777-200ER, was carrying 12 Malaysian crew members and 227 passengers from 15 nations.^[7]

A multinational search effort began in the Gulf of Thailand and the South China Sea, where the flight's signal was lost onsecondary surveillance radar, and was soon^[8][9] extended to the Strait of Malacca and Andaman Sea.^[10][11][12] 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;^[13][14][15] Australia took charge of the search effort on 17 March, when the search shifted to the southern Indian Ocean.^[16] On 24 March 2014, the Malaysian government, noting that the final location determined by the satellite communication is far from any possible landing sites, concluded that "flight MH370 ended in the southern Indian Ocean."^{[13][14][15][17]} The current phase of the search is a comprehensive search of the seafloor about 1,800 kilometres (1,100 mi) southwest of Perth, Australia, which began in October 2014.^[18][19][20] Despite being the largest and most expensive search in aviation history,^{[21][22][23][24]} there has been no confirmation of any flight debris,^[25] resulting in speculations about its disappearance.

Malaysia established the Joint Investigation Team (JIT) to investigate the incident, working with foreign aviation authorities and experts.^[5]: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.^[26] Two passengers travelling on stolen passports were initially suspect in the disappearance, but they were later determined to be asylum seekers and terrorism has been ruled out.^[27][28][29] 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.^[30] 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.^[5]:22 Based on analysis of the satellite communications, the aircraft turned south after passing north of Sumatra and flew for five hours without communication and with little deviation in its track, suggesting that the aircraft was flying on autopilot without manual input from the cockpit and that Flight 370 may have experienced a hypoxia event, ending when fuel was exhausted.^{[5]:34[31][32][33]}

At the time of its disappearance, and if the presumed loss of all on board is confirmed, Flight 370 was the deadliest aviation incident in Malaysia Airlines' history and the deadliest involving a Boeing 777.^[34][35] It was surpassed in both regards 131 days later by the crash of another Malaysia Airlines Boeing 777—Flight 17—that was shot down over Ukraine.^[36] 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 taskforce set up by the International Air Transport Association, with the support of the International Civil Aviation Organization, proposed a new standard that, by December 2015, commercial aircraft report their position every 15 minutes.^[37][38]§

Disappearance[edit]

See also: Timeline of Malaysia Airlines Flight 370

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

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).^[39][40]

§Departure[edit]

At 00:41, Flight 370 took off from runway 32R,^[41] and was cleared by air traffic control (ATC) to climb to flight level 180^[c]—approximately 18,000 feet (5,500 m)—on a direct path to waypoint IGARI and transferred from the airport's air traffic control to "Lumpur Radar" air traffic control on frequency 132.6 MHz. Air traffic control over peninsular Malaysia and adjacent waters is provided by the Kuala Lumpur Area Control Center (ACC); Lumpur Radar is the name of the frequency used for en route air traffic.^[42] Lumpur Radar cleared Flight 370 to flight level 350^[c]—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.^[41]

§Communication lost[edit]

External media

Images
Transcript of ATC conversations with Flight 370 A transcript of conversations between ATC and Flight 370 from pre-departure to final contact (00:25 – 01:19).
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 message using the Aircraft Communications Addressing and Reporting System (ACARS) protocol was sent at 01:07;^{[5]:2[43][44]:36} among the data provided in the message was total fuel remaining—43,800 kg (96,600 lb).^[45]:9 The final verbal contact with air traffic control occurred at 01:19, when one of the aircraft's pilots acknowledged a send-off by Lumpur Radar to Ho Chi Minh ACC:^[d][41][46]

[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.^[47][48] The captain of another aircraft attempted to reach the crew of Flight 370 "just after [01:30]" using the international distress frequency to relay Vietnamese air traffic control's request for the crew to contact them; the captain said he was able to establish contact, but just heard "mumbling" and static.^[49] Calls made to Flight 370's cockpit at 02:39 and 07:13 were unanswered but acknowledged by the aircraft's satellite data unit.^{[5]:18[44]:40}

§Radar[edit]

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

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

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

Because of the sensitive nature of revealing military radar capabilities, countries in the region where Flight 370 disappeared have been reluctant to release information they may have collected from military radar. The only nation besides Malaysia to claim tracking Flight 370 is Thailand.^[56]Despite possibly flying near or over the northern tip of Sumatra,^[41] Indonesia—which has an early warning radar system—has publicly denied sighting Flight 370 on radar.^[56] 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.^[57]

§Satellite communication resumes[edit]

At 02:25, 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.^[5]:18[44] 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.^{[5][44][58][59]}

§Response by air traffic control[edit]

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

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

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.^[41] 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.^[60] Kuala Lumpur ACC contacted Ho Chi Minh ACC to query that the planned flight path for Flight 370 passed through Cambodian airspace. Ho Chi Minh ACC responded that Flight 370 was not supposed to enter Cambodian airspace and that they had already contacted Phnom Penh ACC (which controls Cambodian airspace), which had no contact with Flight 370.^[41] 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.^[41][60] Later, another Malaysia Airlines aircraft, Flight 386 bound for Shanghai was requested by Ho Chi Minh ACC to attempt to contact Flight 370 on the Lumpur Radar frequency—the frequency on which Flight 370 last made contact with Malaysian air traffic control—and on emergency frequencies, but without success.^[41][61]

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

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

Malaysia Airlines issued a media statement at 07:24, 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;^[62] the time when contact was lost was later corrected to 01:21.^[63] 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.^[26]

§Presumed loss[edit]

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

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

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.^[13][14][15]

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, at the time of its disappearance Flight 370 was the deadliest aviation incident in the history of Malaysia Airlines (surpassing the 1977 hijacking and crash of Malaysian Airline System Flight 653 that killed all 100 passengers and crew on board) and the deadliest involving a Boeing 777, surpassing Asiana Airlines Flight 214 (3 fatalities).^[34][35] In both of those categories, Flight 370 was surpassed just 131 days later by Malaysia Airlines Flight 17, another Boeing 777-200ER, which was shot down on 17 July 2014, killing all 298 persons aboard.^[36]

§Timeline of disappearance[edit]

This section lists events during Flight 370. For a timeline of events in the aftermath of its disappearance, see Timeline of Malaysia Airlines Flight 370

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

§Search[edit]

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

A search and rescue effort was launched soon after the aircraft's disappearance in Southeast Asia, but the following week, analysis of satellite communications between the aircraft and a communications satellite determined that the aircraft had continued flying for several hours and 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.^[70] The current phase of the search is a bathymetric survey and sonar search of the seafloor, about 1,800 kilometres (1,100 mi) southwest of Perth, Australia.^[18]

The search for Flight 370 is the most expensive search operation in aviation history,^{[21][22][71][72]} but has failed to locate any physical debris from the aircraft.^[25] In June 2014, Time estimated that the total search effort to that point had cost approximately US$70 million.^[73] 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.^[19]

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

§Southeast Asia[edit]

The initial search area in Southeast Asia

The Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC) was activated at 05:30—four hours after communication was lost with Flight 370—to co-ordinate search and rescue efforts.^[60] 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.^[75] 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 to pass through heavily militarised airspace and those countries claimed their military radar would have detected an unidentified aircraft entering their airspace.^[76][77][78]

§Southern Indian Ocean[edit]

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

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.^[79][80] Accordingly, on 17 March, Australia agreed to lead the search in the southern locus from Sumatra to the southern Indian Ocean.^[16][81]

§Initial search[edit]

From 18–27 March, the search effort focused on a 305,000 km² (118,000 sq mi) area about 2,600 km (1,600 mi) south-west of Perth^[82] 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.^[83][84] 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. However, none of these possible objects were found by aircraft or ships.^[85]

Revised estimates of the radar track and the aircraft's remaining fuel led to a move of the search 1,100 km (680 mi) north-east of the previous area on 28 March^[86][87][88] which was followed by another shift on 4 April.^[89][90] 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^[91][92] Two ships equipped with towed pinger locators (TPLs) and a submarine equipped with a hull-mounted acoustic system,^[5]:11–12 began searching for pings along a 240-kilometre (150 mi) seabed line believed to be the Flight 370 impact area.^[91][93][94] Operators considered it a shot in the dark,^[95] when comparing the vast search area with the fact that a TPL could only search up to 130 km² (50 sq mi) per day.^[95] 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.^[5]:13 A sonar search of the seafloor near the detections was carried out between 14 April and 28 May without any sign of Flight 370.^[5]:14

§Underwater search[edit]

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;^[96] officials have called this phase the "underwater search", despite the previous seafloor sonar survey.^[20] 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.^[97] Some of the equipment to be used for the underwater search operates best when towed 200 m (650 ft) above the seafloor and is towed at the end of a 10 km (6 mi) cable.^[98] Available bathymetric data for this region was of poor resolution, thus necessitating a bathymetric survey of the search area before the underwater phase began.^[99] Commencing in May, the bathymetric survey charted around 208,000 square kilometres (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.^[100]

The underwater phase of the search, which began on 6 October 2014,^[97] 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.^[101] A fourth vessel joined the search at the end of January 2015; it has an autonomous underwater vehicle (AUV) which can search areas which cannot be effectively searched by equipment on the other vessels.^[102][103] As of 25 February 2015, over 24,000 square kilometres (9,300 sq mi) of seafloor has been searched, which is about 40 percent of the priority search area; with no significant delays, the search of the priority search area will be completed around May 2015.^[104]

§Aircraft[edit]

Flightdeck of 9M-MRO in 2004.

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

Flight 370 was operated with a Boeing 777-2H6ER,^[e] serial number 28420, registration 9M-MRO. The 404th Boeing 777 produced,^[106] it first flew on 14 May 2002 and was delivered new to Malaysia Airlines on 31 May 2002. The aircraft was powered by two Rolls-Royce Trent 892 engines^[106] and configured to carry 282 passengers.^[107] It had accumulated 53,460 hours and 7,525 cycles in service^[108] and had not previously been involved in any major incidents,^[109] though a minor incident while taxiing at Shanghai Pudong International Airport in August 2012 resulted in a broken wingtip.^[110][111] Its last maintenance 'A' check was carried out on 23 February 2014.^[108]

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

§Passengers and crew[edit]

People on board by nationality

Nationality	No.
Australia	6
Canada	2
China	152
France	4
Hong Kong[f]	1
India[116]	5
Indonesia	7
Iran[g]	2
Malaysia[h]	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.^[117]

§Crew[edit]

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

• The captain was 53-year-old Zaharie Ahmad Shah from Penang; he joined Malaysia Airlines in 1981 and had 18,365 hours of flying experience.^[118] Zaharie was also an examiner qualified to conduct simulator tests for pilots.^[119]
• The first officer was 27-year-old Fariq Abdul Hamid, an employee of Malaysia Airlines since 2007, with 2,763 flying hours.^[120][121] This was Fariq's first flight as a fully qualified Boeing 777 first officer following the completion of his supervised transition to that type of aircraft.^[121]

§Passengers[edit]

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

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

§Investigation[edit]

§International participation[edit]

Malaysia set up a Joint Investigation Team (JIT), composed of specialists from Malaysia, Australia, China, the UK, the US, and France,^[5]:1[131] being led according to the ICAOstandards by "an independent investigator in charge".^{[132][133][134]} 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.^[135] 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.^[135] The criminal investigation is being led by the Royal Malaysia Police,^[1]:9 assisted by Interpol and other relevant international law enforcement authorities.^[136][137]

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) andAustralian Transport Safety Board (ATSB) worked to determine the search area, correlating information with the JIT and other government and academic sources, while the Joint Agency Coordination Center (JACC) coordinated the search efforts. Following the fourth phase of the search, the ATSB took responsibility for defining the search area. In May, the search strategy working group was established by the ATSB to determine the most likely position on the aircraft at the 00:19 UTC satellite transmission. The group included aircraft and satellite experts from: Air Accidents Investigation Branch (UK), Boeing (US), Defence Science and Technology Organisation (Australia), Department of Civil Aviation (Malaysia), Inmarsat (UK), National Transportation Safety Board (US), and Thales (UK).^{[5]:1[138][139]}

An interim statement regarding the progress of the investigation will be released around the one-year anniversary of the disappearance.^[1]:9

§Analysis of satellite communication[edit]

Main article: Analysis of Malaysia Airlines Flight 370 satellite communications

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. 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 location information about the aircraft's location, heading, or speed.^{[5]:16–17[66]}

§Background[edit]

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

Aeronautical satellite communication (SATCOM) systems are used to transmit messages from the aircraft cockpit as well as automated messages from on-board systems using the ACARS communications protocol, but may also be used to transmit FANS and ATNmessages and provide voice, fax and data links^[140] using other protocols.^{[66][141][142]} 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 which 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 Airline's 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 will transmit a log-on request, which the ground station acknowledges.^[5]:17[142] 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.^[142] After connecting, if a ground station has not received any contact from a terminal for one hour,^[i] the ground station will transmit a "log-on interrogation" message—informally referred to as a "ping";^[5]:18 an active terminal automatically responds. The entire process of interrogating the terminal is referred to as a 'handshake'.^[58][143]

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

Although the ACARS system on Flight 370 was disabled at 01:21, the SDU remained operable.^[5] After last contact by primary radar west of Malaysia, the following records were recorded in the log of Inmarsat's ground station at Perth, Western Australia (all times MYT/UTC+8):^{[5]:18[44][j]}

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

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

§Deductions[edit]

A few deductions can be made from the satellite communications. The first is that the aircraft remained operational until at least 08:19—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.^[144]: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.^{[58][59][143]} The log-on message sent from the aircraft at 08:19:29 was "log-on request".^[5]: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 aircraft attitude.^[5]:22 Investigators consider the most likely reason to be that they were sent during power-up after an electrical outage.^[5]: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.^{[5]:33[5]:33[145]} In the event of fuel exhaustion and engine flame-out—which would eliminate power to the SDU—the aircraft's ram air turbine would deploy, providing power to some instruments and flight controls, including the SDU.^[5]: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.^[5]:22

§Analysis[edit]

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 twice the distance from the ground station to 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.^{[5]:18[144]:4–6}
• Burst frequency offset (BFO) — the difference between the expected and received frequency of transmissions. The difference is caused by Doppler shift as the signals travelled from the aircraft to the satellite to the ground station; the frequency translations made in the satellite and at the ground station; a small, constant error (bias) in the SDU that results from drift and ageing; and compensation applied by the SDU to counter the Doppler shift on the uplink. This measure can be analysed to determine the aircraft's speed and heading, but multiple combinations of speed and heading can be valid solutions.^{[5]:18[144]:9–11}

By combining the distance between the aircraft and satellite, speed, and heading with aircraft performance constraints (eg. fuel consumption, possible speeds and altitudes), investigators generated candidate paths that were analysed separately by two methods. The first assumes 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) and calculates the BTO and BFO values along these routes and compares 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.^{[5]:18, 25–28[146]: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.^[146]:12

§Possible in-flight events[edit]

§Power interruption[edit]

The SATCOM link functioned normally from pre-flight (beginning at 00:00 MYT) until it responded to a ground-to-air ACARS message with an acknowledge message at 01:07. Ground-to-air ACARS messages continued to be transmitted to Flight 370 until Inmarsat's network sent multiple "Request for Acknowledge" messages at 02:03, without a response from the aircraft. At some time between 01:07 and 02:03, power was lost to the SDU. At 02:25, the aircraft's SDU sent a "log-on request".^{[5]:22[44]: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.^[5]:33[147] 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.^[5]:33

§Unresponsive crew or hypoxia[edit]

An analysis by the ATSB comparing the evidence available for Flight 370 with three categories of accidents—an in-flight upset (e.g., stall), a glide event (e.g., engine failure, fuel starvation), and an unresponsive crew or hypoxia event—concluded that an unresponsive crew or hypoxia event "best fit the available evidence"^[5]: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,^[5]:34 likely on autopilot.^[32][33][31] There is, however, no consensus among investigators on the unresponsive crew or hypoxia theory.^[31]

§Possible§

Passenger involvement[edit]

Two men identified on the passenger manifest, an Austrian and an Italian, had reported their passports stolen in 2012 and 2013, respectively.^[26][148] 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.^[149][150] 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.^[150] The two one-way tickets purchased for the holders of the stolen passports were booked through China Southern Airlines.^[151] It was reported that an Iranian had ordered the cheapest tickets to Europe via telephone in Bangkok, Thailand. The tickets were paid for in cash.^[152][153] The two passengers were later identified as Iranian men, one aged 19 and the other 29, who had entered Malaysia on 28 February using valid Iranian passports. The head of Interpol said the organisation was "inclined to conclude that it was not a terrorist incident".^[27] The two men were believed to be asylum seekers.^[28][29]

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

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

§Crew involvement[edit]

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

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

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

Investigators believe someone in the cockpit of Flight 370 re-programmed the aircraft's autopilot before it travelled south across the Indian Ocean, raising further suspicion the disappearance was caused by the captain or co-pilot.^[170] A hijacking by a pilot would not be without precedent, for example less than three weeks before Flight 370 disappeared—on 17 February 2014—Ethiopian Airlines Flight 702 was hijacked when the co-pilot locked the captain out of the cabin and diverted the aircraft to seek asylum in Switzerland.^[171][172]

§Cargo[edit]

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

§Claims of responsibility[edit]

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

§Aftermath[edit]

§Information sharing[edit]

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

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

Malaysia had initially declined to release raw data from its military radar, deeming the information "too sensitive,"^[199] but later acceded.^[199][200] Defence experts suggested that giving others access to radar information could be sensitive on a military level. As an example: "The rate at which they can take the picture can also reveal how good the radar system is."^[199] 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.^[199] 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.^[203]

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.^[66][204]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.^[205] 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.^[206]

§Malaysia Airlines[edit

A month after the disappearance, Malaysia Airlines' chief executive Ahmad Jauhari Yahya acknowledged that ticket sales had declined but failed to provide specific details. This may partially result from the suspension of the airline's advertisement 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."^[207] 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.^[207][208] In China, where the majority of passengers were from, bookings on Malaysia Airlines were down 60 percent in March.^[209]

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.^[210][211] 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.^[40][212]

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

The airline was criticised on social media for gaffes made during advertisements. In September 2014, the airline launched a contest "My Ultimate Bucket List" in Australia and New Zealand. Since a bucket list is a list of goals to accomplish before you die, many found it very distasteful for an airline which lost 537 people killed and missing in the previous six months.^[216] In November 2014, the airline tweeted "Want to go somewhere, but don't know where? Our Year-End Specials might just help! #keepflying"; the airline removed it and tweeted an apology after the public drew parallels to Flight 370.^[217][218]

§Financial troubles[edit]

At the time of Flight 370's disappearance, Malaysia Airlines was struggling to cut costs to compete with a wave of new, low-cost carriers in the region. In the previous three years, Malaysia Airlines had booked losses of: RM1.17 billion (US$356 million) in 2013, RM433 million in 2012, and RM2.5 billion in 2011.^[207] Malaysia Airlines lost RM443.4 million (US$137.4 million) in the first quarter of 2014 (January–March).^[208] 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.^[219] 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.^[207] 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.^[209]

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.^{[220][221][222][223][224]} The loss of Flight 17 in July greatly exacerbated Malaysia Airline's woes. The combined effect on consumer confidence of the loss of Flights 370 and 17 and the airline's poor financial performance led Khazanah Nasional—the majority shareholder (69.37 percent)^[225] and a Malaysian state-run investment arm—to announce on 8 August its plan to purchase the remainder of the airline, thereby renationalising it.^{[226][227][228]}

§Compensation for passengers' kin[edit]

Lack of evidence in determining the cause of Flight 370's disappearance, indeed even physical evidence that the aircraft crashed, raises many issues regarding responsibility for the accident and payments made by insurance agencies.^[229] 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^[l] from the airline's insurance company—a total of nearly US$40 million for the 227 passengers on board.^[229]

Malaysia Airlines would still be vulnerable to civil lawsuits from passengers' families.^[229] 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.^{[230][231][232]} 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.^[233] 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,^[m] 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.^[236]

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

§Malaysia[edit]

Messages of hope and prayer for MH370 at a bookstore in 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.^{[241][242][243][244]} The Malaysian military only became aware of the unidentified flight after reviewing radar recordings several hours after Flight 370's disappearance.^[243] 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.^[243][244]

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)^[245]

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

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

Malaysia's Defence and Transport Minister Hishammuddin Hussein—a central figure in the search an investigation of Flight 370 and active on Twitter—was criticised for responding/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 beauty of unity & sweetness of having each other."^[247] The remarks were viewed as insensitive to the victims' families. Both tweets were removed.^[247][248] 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?"^[249]

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

§China[edit]

Chinese Deputy Foreign Minister Xie Hangsheng reacted sceptically to the conclusion by the Malaysian government that the aircraft had gone down with no survivors, demanding "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."^[69][251]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;^[252]

§Relatives of passengers[edit]

On 25 March, around two hundred family members of the Chinese passengers protested outside the Malaysian embassy in Beijing.^[253][254] 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.^[255] An op-ed for China Daily said that Malaysia was not wholly to be blamed for its poor handling of such a "bizarre"^[256] and "unprecedented crisis,"^[256] and appealed to Chinese people not to allow emotions to prevail over evidence and rationality.^[256] 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".^[257] The ambassador also strongly criticised Western media for having "published false news, stoked conflict and even spread rumours"^[182] to the detriment of relatives and of Sino–Malaysian relations.^[182] 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.^[258][259]

§Boycotts[edit]

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

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

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

§Air transport industry[edit]

The fact that, in a digitally-connected world, a modern aircraft could simply 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.^{[265][266][267][268]}

§Aircraft tracking[edit]

See also: Future Air Navigation System § Surveillance improvements

The International Air Transport Association—an industry trade organisation representing over 240 airlines (representing 84 percent of global air traffic)—and the United Nation's civil aviation body—the International Civil Aviation Organization (ICAO)—are working on implementing new measures to track aircraft in flight in real time.^[269] The IATA created a taskforce (which includes several outside stakeholders)^[269] 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 taskforce 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.^[270] The taskforce 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.^[271][272] In December 2014, the IATA taskforce 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.^[37][38]

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).^[273] Inmarsat has also changed the time period for handshakes with their terminals from one hour to 15 minutes.^[144]:2

§Transponders[edit]

There was a call for automated transponders after the 11 September 2001 terrorist attacks; no changes were made as aviation experts preferred flexible control, in case of malfunctions or electrical emergencies.^[274] 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.^[267]

§Flight recorders[edit]

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

Further information: Search for Malaysia Airlines Flight 370 § Underwater locator beacons

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.^[n][275] 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 (1.2–1.9 mi), up to 4,500 m (2.8 mi) under favourable conditions.^[5]:11Even if the flight recorders are located, the cockpit voice recorder memory only has capacity to store 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. However, the events which caused Flight 370 to divert from its course and disappear happened more than two hours before the flight ended.^[276] Given these limitations and the importance of the data stored on flight recorders, Flight 370 has brought attention to new technologies that enable the data to be streamed to the ground.^{[277][278][279]}

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

§Safety recommendations[edit]

In January 2015, the US NTSB cited Flight 370 and Air France Flight 447 when it issued eight safety recommendations^[o] 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.^[280][281]

§Timeline of events[edit]

Main article: Timeline of Malaysia Airlines Flight 370

8 March

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

10 March

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

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][283]

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

18 March – 28 April

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

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

30 March

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

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

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 nil debris.^[5]

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

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

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^[5] detailing the previous search efforts, analysis of satellite communications, methodology used to determine the new search area.^[290]

October−ongoing

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

8 October

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

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]

Source: WIkipedia