Thành viên:Flyplanevn27/nháp1

Elapsed (HH:MM) Time Event
MYT UTC
1:52 prior 7 March Captain Zaharie Ahmad Shah[1][2] signs in for duty.[3]:1
22:50 14:50
1:28 prior 23:15 15:15 First Officer Fariq Abdul Hamid[1][2] signs in for duty.[3]:1
00:42 prior 8 March 16:00 The aircraft's SDU logs onto the Inmarsat satellite communication network.[4]:3
00:00
00:13 prior 00:27 16:27 ATC gives Flight 370 clearance to push back from the gate.[3]:1
00:01:23 prior 00:40:37 16:40:37 ATC gives Flight 370 clearance to take off.[3]:1
00:00 00:42 16:42 Flight 370 takes off from runway 32R at Kuala Lumpur International Airport.[3]: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)[a] and proceed directly to waypoint IGARI.[3]:1
00:04 00:46:39 16:46:39 Flight 370 is transferred from the airport's ATC to Lumpur Radar ATC.[3]:2 Both the airport and Lumpur Radar ATC are based at the Kuala Lumpur Area Control Centre (KL ACC).[3]:87–95
00:05 00:46:58 16:46:58 ATC gives Flight 370 clearance to climb to Flight Level 250; approximately 25.000 foot (7.600 mét).[3]:2
00:08 00:50:08 16:50:08 ATC gives Flight 370 clearance to climb to Flight Level 350; approximately 35.000 foot (11.000 mét).[3]:2
00:19 01:01:17 17:01:17 The captain[b] informs ATC that Flight 370 has reached Flight Level 350.[3]:2
00:25 01:07:48 17:07:48 The final data transmission from Flight 370 using the ACARS protocol is made.[3]:1[4]: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.[4]:36
00:25 01:07:56 17:07:56 The captain confirms that Flight 370 is flying at Flight Level 350.[3]: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.[3]: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.[3]:2 Malaysian military radar continues to track the aircraft, which "almost immediately"[3]:3 begins a turn to the left until it is travelling in a south-westerly direction.[3]: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.[5]
00:55 01:37 17:37 An expected half-hourly ACARS data transmission is not received.[6]
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.[3]:2[7]
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.[7]
01:10 01:52 17:52 Flight 370 reached the southern end of Penang Island. First Officer Fariq Abdul Hamid's cellphone registered with a cell tower below, though no other data was transmitted. Flight 370 then turned towards northwest along the Strait of Malacca.[8]
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.[7]
01:21 02:03:41 18:03:41 Malaysia Airlines dispatch centre sends a message to the cockpit instructing pilots to contact Vietnam ATC, to which there is no response.[9] 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.[4]: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.[7]
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.[7]
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.[7]
01:40 02:22 18:22 The last primary radar contact is made by the Malaysian military, 200 hải lý (370 km; 230 mi) north-west of Penang, 6°49′38″B 97°43′15″Đ / 6,82722°B 97,72083°Đ / 6.82722; 97.72083 (Last primary radar contact, 8 March)[10]: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]:39[10]:18 This communication is sometimes erroneously referred to as the first hourly "handshake" after the flight's disappearing from radar.[11][12]
01:52 02:34 18:34 KL ACC queries Malaysia Airlines' operations centre about communication status with Flight 370, but it was not sure whether a message sent to Flight 370 was successful.[7]
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′0″B 109°15′0″Đ / 14,9°B 109,25°Đ / 14.90000; 109.25000 (Northern Vietnam) at 18:33 UTC. KL ACC relays this information to HCM ACC.[7]
01:57 02:39 18:39 A ground-to-aircraft telephone call, via the aircraft's satellite link, goes unanswered.[4]:40[10]:18
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.[7]
02:59 03:41 19:41 Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[4]:40
03:59 04:41 20:41 Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[4]:40
04:27 05:09 21:09 Singapore ACC queried for information about Flight 370.[7]
04:59 05:41 21:41 Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[4]: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.[3]:2
05:59 06:41 22:41 Hourly, automated handshake between the aircraft and the Inmarsat satellite communication network.[4]:40
06:31 07:13 23:13 A ground-to-aircraft telephone call placed by Malaysia Airlines,[9] via the aircraft's satellite link, goes unanswered.[4]:40[10]:18
06:42 07:24 23:24 Malaysia Airlines issues a press statement announcing that Flight 370 is missing.[1]
07:29 08:11 8 March The last successful automated hourly handshake is made with the Inmarsat satellite communication network.[4]:41[11]
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.[13][14] Investigators believe this follows a power failure between the time the engines stopping due to fuel exhaustion and the emergency power generator starting.[4]:41[10]:18, 33
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]:41[10]:18
08:33 09:15 01:15 The aircraft does not respond to an hourly, automated handshake attempt.[4]:41[11]
  1. ^ a b c Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên MAS press statements 8–17 March
  2. ^ a b Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên FurtherConfusion
  3. ^ a b c d e f g h i j k l m n o p q r s t Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên Interim report-March 2015
  4. ^ a b c d e f g h i j k l m n o Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên Ground log
  5. ^ “Pilot: I established contact with plane”. New Straits Times. 9 tháng 3 năm 2014. Truy cập ngày 17 tháng 3 năm 2014.
  6. ^ “MH370 PC live updates / 530 17th March”. Out of Control Videos. Bản gốc lưu trữ ngày 17 tháng 3 năm 2014. Truy cập ngày 16 tháng 7 năm 2014. Timing of ACARS deactivation unclear. Last ACARS message at 01:07 was not necessarily point at which system was turned off
  7. ^ a b c d e f g h i j “Documents: Preliminary report on missing Malaysia Airlines Flight 370”. Malaysia Department of Civil Aviation. Truy cập ngày 22 tháng 10 năm 2014 – qua CNN.
  8. ^ Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên Atlantic Investigation
  9. ^ a b Watson, Ivan (29 tháng 4 năm 2014). “MH370: Plane audio recording played in public for first time to Chinese families”. CNN. Truy cập ngày 14 tháng 7 năm 2014. At 2:03 a.m. local time on March 8, the operational dispatch centre of Malaysia Airlines sent a message to the cockpit instructing the pilot to contact ground control in Vietnam, said Sayid Ruzaimi Syed Aris, an official with Malaysia's aviation authority...MH370 did not respond to the message...'At 7:13,' Sayid said, Malaysia Airlines tried to 'make a voice call to the aircraft, but no pickup.'
  10. ^ a b c d e f Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên ATSB
  11. ^ a b c Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên Inmarsat(26 March)
  12. ^ Lỗi chú thích: Thẻ <ref> sai; không có nội dung trong thẻ ref có tên Telegraph-delays
  13. ^ “Missing Malaysia plane: What we know”. BBC News. 1 tháng 5 năm 2014. Truy cập ngày 8 tháng 5 năm 2014.
  14. ^ Keith Bradsher; Edward Wong; Thomas Fuller. “Malaysia Releases Details of Last Contact With Missing Plane”. The New York Times. Truy cập ngày 25 tháng 3 năm 2014.


Lỗi chú thích: Đã tìm thấy thẻ <ref> với tên nhóm “lower-alpha”, nhưng không tìm thấy thẻ tương ứng <references group="lower-alpha"/> tương ứng, hoặc thẻ đóng </ref> bị thiếu