Chronology/ATC Activities after Notification by HCM ACC

MH370 DECODED
Jump to navigation Jump to search

Chronology: ATC Activities after Notification by HCM ACC

This article presents extracts from the Safety Investigation Report MH370/01/2018 which have been selected because the content is a chronology of events related to Malaysia Airlines flight MH370.

Each event in this chronology has been linked to a Timeline Event in the main Timeline articles on this site. This provides a cross-link or check on the well known events.


Table 1.18E – ATC Activities after Notification by HCM ACC

No. Time Activities
1. 1739:03 UTC
(0139:03 MYT)
Ho Chi Minh ACC first enquired about MH370 and informed KL ACC that verbal contact was not established with MH370 and the radar target was last seen at BITOD.
2. 1741:22 UTC
(0141:22 MYT)
Ho Chi Minh enquired for information on MH370 and KL ACC informed HCM ACC that after waypoint IGARI, MH370 did not return to Lumpur Radar frequency.
3. 1741:23 UTC
(0141:23 MYT)
KL ACC Radar Controller made a “blind transmission” to MH370.
4. 1746:47 UTC
(0146:47 MYT)
HCM ACC queried about MH370 again, stating that radar contact was established over IGARI but there was no verbal contact. HCM ACC advised that the observed radar blip disappeared at waypoint BITOD. HCM ACC stated that efforts to establish communication were made by calling MH370 many times for more than twenty (20) minutes.
5. 1750:28 UTC
[0150:28 MYT]
(0150:27 MYT)
KL ACC queried HCM ACC if there had been any contact with MH370, HCM ACC’s reply was “negative”.
6. 1757:49 UTC
(0157:49 MYT)
HCM ACC informed KL ACC that there was officially no contact with MH370 until this time. Attempts on many frequencies and through other aircraft in the vicinity received no response from MH370.
7. 1803:48 UTC
(0203:48 MYT)
KL ACC queried HCM ACC on the status of MH370, HCM ACC confirmed there was no radar contact at this time and no verbal communication was established. KL ACC relayed the information received from Malaysia Airlines Operations that the aircraft was in the Cambodian airspace.
8. 1807:47 UTC
(0207:47 MYT)
HCM ACC queried for confirmation that MH370 was in Phnom Penh FIR as Phnom Penh did not have any information on MH370. KL ACC indicated it would check further with the supervisor.
9. 1812:15 UTC
(0212:15 MYT)
KL ACC informed HCM ACC that there was no update on the status of MH370.
10. 1815 UTC
(0215 MYT)
(No voice recording).
Extracted from the Watch Supervisor Log Book:
KL ATSC Watch Supervisor queried Malaysia Airlines Operations who informed that MH370 was able to exchange signals with the Flight Explorer.
11. 1818:50 UTC
(0218:50 MYT)
KL ACC queried if the flight plan routing of MH370 was supposed to enter Cambodian airspace. HCM ACC confirmed that the planned route was only through the Vietnamese airspace. HCM ACC had checked and Cambodia had advised that it had no information or contact with MH370. HCM ACC confirmed earlier information that radar contact was lost after BITOD and radio contact was never established. KL ACC queried if HCM ACC was taking Radio Failure action, but the query didn’t seem to be understood by the personnel. HCM ACC suggested KL ACC to call Malaysia Airlines Operations and was advised that it had already been done.
12. 1833:59 UTC
(0233:59 MYT)
KL ACC Radar Controller enquired with Malaysia Airlines Operations Centre about the communication status with MH370 but the personnel was unsure if the message went through successfully or not. Malaysia Airlines Operations Centre informed that the aircraft was still sending the movement message indicating it was somewhere in Vietnam and giving the last position as coordinates N14.90000 E109 15500 at time of 1833 UTC [0233 MYT].
13. 1834:56 UTC
(0234:56 MYT)
HCM ACC queried about the status of MH370 and was informed that the Watch Supervisor was talking to the Company at this time.
14. 1837:34 UTC
(0237:34 MYT)
KL ACC informed HCM ACC that MH370 was still flying and that the aircraft was continuing to send position reports to the airline, and relayed to HCM ACC the latitude and longitude as advised by Malaysian Airlines Operations.
15. 1853:48 UTC
(0253:48 MYT
MH386 which was enroute from KLIA to Shanghai and within HCM FIR was requested by HCM ACC to try to establish contact with MH370 on Lumpur Radar radio frequency. KL ACC then requested MH386 to try on emergency frequencies as well.
16. 1930 UTC
(0330 MYT)
(No voice recording).
Extracted from the Watch Supervisor Log Book:
MAS Operations Centre informed KL ACC that the flight tracker information was based on flight projection and was not reliable for aircraft positioning.
17. 1930:03 UTC
(0330:03 MYT)
KL ACC queried if HCM ACC had checked with next FIR Hainan.
18. 1948:52 UTC
(0348:52 MYT)
When KL ACC queried whether HCM ACC had checked with the Sanya FIR, HCM ACC informed KL ACC that there was no response until now. At 1956:13 UTC [0356:13 MYT] KL ACC queried Malaysia Airlines Operations for any latest information or contact with MH370.
See Note 1 below 1956:13 UTC
(0356:13 MYT)
At 1956:13 UTC [0356:13 MYT] KL ACC queried Malaysia Airlines Operations for any latest information or contact with MH370.
19. 2025:22 UTC
(0425:22 MYT)
HCM ACC Supervisor queried KL ACC on the last position that MH370 was in contact with KL ACC.
21. 2109:13 UTC
(0509:13 MYT
Singapore, on behalf of Hong Kong, enquired for information on MH370.
20. 2118:32 UTC
(0518:32 MYT)
When HCM ACC queried for information on MH370, KL ACC also queried if any information had been received from Hong Kong or Beijing.
22. 2120:16 UTC
(0520:16 MYT)
Capt. xxxx [name redacted] of MAS requested for information on MH370. He opined that based on known information, “MH370 never left Malaysian airspace”.
23. 2130 UTC
(0530 MYT)
Watch Supervisor activated the Kuala Lumpur Aeronautical Rescue Coordination Centre (ARCC).
24. 2141:20 UTC
(0541:20 MYT)
HCM ACC queried for any updates.
25. 2214:13 UTC
(0614:13 MYT)
KL ACC queried HCM ACC if SAR was activated.
26. 2232 UTC
(0632 MYT)
KL ARCC issued a DETRESFA message (Figure 1.18C [below]).

Table 1.18E – ATC Activities after Notification by HCM ACC
Source: Safety Investigation Report MH370/01/2018

Note 1: Event 18 contained two entries which have been split here as it seems likely to be a formatting error. The same events are separate in Table 2.2C.

Note 2: The sequence of Events 19, 20 and 21 have been changed based on the time of each event. The correct sequence was shown in Table 2.2C.


Source: Malaysian ICAO Annex 13 Safety Investigation Team for MH370, 02 July 2018, Safety Investigation Report MH370/01/2018