Timeline/NIO-SIO/0819:29 MYT

MH370 DECODED
Jump to navigation Jump to search

Event Summary

08:19:29 MYT Saturday, 8 March 2014

Return to Timeline

SATCOM Log-On, initiated from the aircraft terminal. This is the seventh ‘handshake’.

  1. For there to have been a Log-On at this time, there must have been a prior loss of the SATCOM link. This link loss must have occurred at some time after 0010:58, when the SATCOM responded to a Log-On interrogation.
  2. This Log-On request suggests that whatever caused the SATCOM link loss to occur had been reversed.


Event Details

  1. Safety Investigation Report MH370/01/2018 Satellite Ground Station Logs - Key Observations

    SATCOM Log-On, initiated from the aircraft terminal. This is the seventh ‘handshake’.

    1. For there to have been a Log-On at this time, there must have been a prior loss of the SATCOM link. This link loss must have occurred at some time after 0010:58, when the SATCOM responded to a Log-On interrogation.
    2. This Log-On request suggests that whatever caused the SATCOM link loss to occur had been reversed.



Notes

  1. Source: Safety Investigation Report MH370/01/2018 2.4.4 Aircraft Systems Analysis

    The SATCOM handshake data indicated that the aircraft was airborne for approximately 7 hours, 37 minutes (Take-off: 0042 MYT to Last SATCOM Handshake: 0819 MYT). That the aircraft flew quite some distance over a long period suggests that it flew at high altitude. Refer to the aircraft performance section in Section 1.6.9.

  2. Source: Safety Investigation Report MH370/01/2018 2.5.1 Summary of Key Observations of the SATCOM Ground Station Logs

    5) During the two in-flight Log-Ons at 1825 and 0019, the GES recorded abnormal frequency offsets for four burst transmissions from the SATCOM. After extensive analysis, the following explanations have emerged. The 1825 Log-On Request had a non-zero BER and could therefore have been logged at the Ground station with a BFO measurement error suggesting that the BFO figure may not be reliable.

    a) 1825 Log-On Acknowledge - Most likely due to the power-on drift of the SDU Oven Controlled Crystal Oscillator (OCXO), thus endorsing the belief that the 1825 Log-On was preceded by a lengthy power interrupt.

    b) 0019 Log-On Request - Could have been due to uncompensated vertical velocity, indicating that the aircraft was likely to be descending at this time. Alternatively, it could have been due to the OCXO warm up drift, or it could have been due to a combination of uncompensated vertical velocity and OCXO warm up drift.

    c) 0019 Log-On Acknowledge - Could have been due to uncompensated vertical velocity, indicating that the aircraft was likely to be descending at this time. Alternatively, it could have been due to the OCXO warm up drift, or it could have been due to a combination of uncompensated vertical velocity and OCXO warm up drift.

    d) It has not been possible to attribute specific correction values to the 1825 Log-On Acknowledge and 0019 Log-on Request and Log-On Acknowledge BFOs, so it was excluded from the Doppler calculations undertaken by the Aircraft Flight Path/Performance Subgroup. In the case of the 1825 Log-On Acknowledge, the following subsequent bursts were used instead, as the frequency is more stable at these times:

    i) 1828:05.904 Data-3 R-Channel burst.

    ii) 1828:14.905 Data-3 R-Channel burst.

    6) There is no indication of the SATCOM link being manually Logged Off from the cockpit (via a Multi-function Control Display Unit [MCDU]). Such activity would have been captured in the GES logs, but it was not.

    7) No Data-2 Aircraft Communications Addressing and Reporting System (ACARS) traffic was observed after 1707 on 07 March 2014.

    8) The IFE equipment set up two ground connections over SATCOM (for the SMS e-mail application and Built-In Test Equipment (BITE) application) after the SATCOM re-established the link at 1825 on 07 March 2014 (normal), but not after the SATCOM re-established the link at 0019 on 08 March 2014 (abnormal). In the 0019 case, it is possible that the IFE was no longer powered, or failed, or that the IFE and/or the SATCOM became inoperative before the connections could be set up. At no time during the flight was any user data sent over the link by means of the SMS/e-mail application.