Timeline/Response/KL ARCC/0632 MYT

MH370 DECODED
Jump to navigation Jump to search

Event Summary

06:32:00 MYT Saturday, 8 March 2014

Return to Timeline

KL ARCC issued a DETRESFA message


Event Details

  1. Safety Investigation Report MH370/01/2018 1.18.1 SIR 2018:1 Factual Information/1.18/1.18.1/6 Chronology of Activities after Notification by HCM ACC ATC Activities after Notification by HCM ACC

    KL ARCC issued a DETRESFA message (Figure 1.18C [below]).

  2. Safety Investigation Report MH370/01/2018 2.2.7 Table 2.2C - Chronology of ATC Events following the Disappearance of MH370

    KL ARCC issued a DETRESFA message.


  3. Safety Investigation Report MH370/01/2018 1.18.1 Provision of Air Traffic Services and Areas of Responsibilities

    At 2232 UTC [0632 MYT] KL ARCC transmitted the first DETRESFA message. A total of 4 hours and 05 minutes had passed from the time the Distress Phase should have been declared.


  4. DETRESFA Message

    Figure 2.2P - DETRESFA Message sent over AFTN

    Figure 2.2P - DETRESFA Message sent over AFTN

    Source: DCA Malaysia


  5. For a transcript of the DETRESFA Message see DETRESFA Message Transcript






Notes

  1. KL ACC was responsible for the provision of alerting service for MH370.

    Safety Investigation Report MH370/01/2018 1.18.1 Provision of Air Traffic Services and Areas of Responsibilities

    The Team noted that MH370 was operating in the airspace delegated to KL ACC and the last air-ground radio contact was with KL ACC. MH370 did not contact Ho Chi Minh ACC and Ho Chi Minh ACC was unable to establish radio communication with MH370.
    Hence KL ACC shall be responsible for the provision of alerting service for MH370.

  2. Safety Investigation Report MH370/01/2018 1.18.1 Provision of Air Traffic Services and Areas of Responsibilities

    7) Activation of KL Aeronautical Rescue Coordination Centre

    KL ARCC was activated at 2130 UTC [0530 MYT]. The DETRESFA message was disseminated via the AFTN at 2232 UTC [0632 MYT], 01 hour and 02 minutes later. No activity was recorded in the RCC Logbook between 2130 UTC [0530 MYT] and 2232 UTC [0632 MYT].

  3. Inclusion of extracts from both Table 1.18E and Table 2.2C may appear to be duplication. However, the tables contain different events, and where the events are the same, the wording may be slightly different. Both versions are included for consistency.
  4. The context of Table 1.18E is the Factual Information in the Safety Investigation Report MH370/01/2018 and the context of Table 2.2C is the Analysis section.