Flight MH370/2014-03-08/02-25-34 MYT: Difference between revisions

MH370 DECODED
Jump to navigation Jump to search
m Text replacement - "</includeonly> <!-- End Chron Summary -->" to "</onlyinclude> <!-- End Chron Summary -->"
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Menu/Timeline/ANDS-NIO Current}}
<noinclude>‎  
[[Category:Andaman Sea to North Indian Ocean]]
<noinclude> ‎</noinclude>
{{ChronologyEventDetails
    |Day={{Day:1}}
    |Time={{Time:{{FULLPAGENAME}}/EventTime}}
    |EventType={{Time:{{FULLPAGENAME}}/EventType}}
    |Summary={{Time:{{FULLPAGENAME}}/Summary}}
    |EventDetails={{Time:{{FULLPAGENAME}}/Details}}
    |Notes={{Time:{{FULLPAGENAME}}/Notes}}
    |ReturnToTimelineLink=<html><a href="/Timeline/ANDS-NIO#022534" class="nav-btn return">Chronology</a></html>
}}
<noinclude>‎ </noinclude>
{{#seo:
{{#seo:
|title_mode=replace
|title_mode=replace
|title=Flight MH370 Event at 2014-03-07T18:25:34Z
|title=Flight MH370 Event at 2014-03-07T18:25:34Z
|description=SATCOM Log-On successfully completed; SATCOM link re-established for voice and Data Class 3. Abnormal Burst Frequency Offset (BFO) recorded, consistent with power interruption of the OCXO. No Flight ID transmitted during Log-On, indicating SDU had stopped receiving valid Flight ID from AIMS.
|description=SATCOM Log-On successfully completed; SATCOM link re-established for voice and Data Class 3. Abnormal Burst Frequency Offset (BFO) recorded, consistent with power interruption of the OCXO. No Flight ID transmitted during Log-On, indicating SDU had stopped receiving valid Flight ID from AIMS.
}}
}}</noinclude>
 
<onlyinclude> <!-- Start Chron Summary -->
<div class="chron air" id="#022534">
<p>8 March 2014 &nbsp; [[Flight MH370/2014-03-08/02-25-34 MYT|02:25:34 MYT]]</p>
<p>SATCOM Log-On successfully completed; SATCOM link re-established for voice and Data Class 3. Abnormal Burst Frequency Offset (BFO) recorded, consistent with power interruption of the OCXO. No Flight ID transmitted during Log-On, indicating SDU had stopped receiving valid Flight ID from AIMS.</p>


</div>
<noinclude> ‎
</onlyinclude> <!-- End Chron Summary -->
<noinclude> ‎</noinclude>
‎{{EventMetadata
‎{{EventMetadata
|FlightID=MH370
|FlightID=MH370
Line 40: Line 20:
|DataSource=Safety Investigation Report (2018)
|DataSource=Safety Investigation Report (2018)
|DataItems=1.9.4 / Table 1.9C (No. 10)
|DataItems=1.9.4 / Table 1.9C (No. 10)
}}
|ImageLink=Add Image Link
}}</noinclude>
 
<noinclude> ‎
{{ChronologyEventDetails
    |Day={{Day:1}}
    |Time={{Time:{{FULLPAGENAME}}/EventTime}}
    |EventType={{Time:{{FULLPAGENAME}}/EventType}}
    |Summary={{Time:{{FULLPAGENAME}}/Summary}}
    |EventDetails={{Time:{{FULLPAGENAME}}/Details}}
    |Notes={{Time:{{FULLPAGENAME}}/Notes}}
    |ReturnToTimelineLink=<html><a href="/Flight_MH370/Chronology/Phase_4#022534" class="nav-btn return">Chronology</a></html>
}}</noinclude>
 
{{ShortLine}}
<h5>The short summary below is transcluded into a relevant Chronology page.</h5>
<onlyinclude> <!-- Start Chron Summary -->
<div class="chron air" id="#022534">
<p>8 March 2014 &nbsp; [[Flight MH370/2014-03-08/02-25-34 MYT|02:25:34 MYT]]</p>
<p>SATCOM Log-On successfully completed; SATCOM link re-established for voice and Data Class 3. Abnormal Burst Frequency Offset (BFO) recorded, consistent with power interruption of the OCXO. No Flight ID transmitted during Log-On, indicating SDU had stopped receiving valid Flight ID from AIMS.</p>
</div>
</onlyinclude> <!-- End Chron Summary -->
 
 
[[Category:Andaman Sea to North Indian Ocean]]

Latest revision as of 03:22, 26 August 2026

Event Metadata

Flight ID MH370
Event Type air
Date and Time MYT 8 March 2014 02:25:34 MYT
Date and Time UTC 7 March 2014 18:25:34 UTC
Flight Phase Phase 5
Data Source Safety Investigation Report (2018) 1.9.4 / Table 1.9C (No. 10)
Date and Time ISO 8601 2014-03-07T18:25:34Z
ISO 8601 Description Flight MH370 Event at 2014-03-07T18:25:34Z

Add Image Link

Event Summary

02:25:34 MYT Saturday 8 March 2014

Chronology

The SATCOM link becomes available (for both voice and data - Class 3) once more and normal SATCOM operation resumes (except that there is no Data-2 ACARS traffic).

No Flight ID was sent to the GES during the Log-On. This implies that the SDU stopped receiving a valid Flight ID from the AIMS at sometime between 1642:04 and 1825:00.

The possible reasons for the link loss and the subsequent Log-On that took place at 1825:00 have been investigated and are detailed in Table 2.5A. There are many quite complicated scenarios that could have caused the 1825:00 Log-On. However, the most likely reason is a power interrupt to the SATCOM avionics, of a duration greater than 22 minutes (the time between events 7 and 9) and less than 78 minutes (the time between events 6 and 9).


Event Details

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

    SATCOM Log-On, successfully completed.

    1. The SATCOM link becomes available (for both voice and data - Class 3) once more and normal SATCOM operation resumes (except that there is no Data-2 ACARS traffic).
    2. No Flight ID was sent to the GES during the Log-On. This implies that the SDU stopped receiving a valid Flight ID from the AIMS at sometime between 1642:04 and 1825:00.
    3. The possible reasons for the link loss and the subsequent Log-On that took place at 1825:00 have been investigated and are detailed in Table 2.5A. There are many quite complicated scenarios that could have caused the 1825:00 Log-On. However, the most likely reason is a power interrupt to the SATCOM avionics, of a duration greater than 22 minutes (the time between events 7 and 9) and less than 78 minutes (the time between events 6 and 9).
    4. The GES recorded an abnormal BFO for the SATCOM Log-On Acknowledge transmissions (Sections 1.9.5 para. 5 and 2.5.3).
      • 1825:00 Log-On Acknowledge - Most likely due to the power-on drift of the Oven Controlled Crystal Oscillator (OCXO), thus endorsing the belief that the 1825:00 Log On was preceded by a lengthy power interrupt.

    An OCXO provides a stable reference frequency for the SDU Radio Frequency (RF) transmit and receive circuits and also for SDU modem timing. Within the OCXO, a regulated oven keeps the crystal at an almost constant temperature if the ambient temperature in the crown area is between the ranges -55oC up to above +70oC. The oven also contains extra electrical regulation and isolation to ensure frequency accuracy and stability. The OCXO includes an oven ready flag, which triggers the Log-On initiation when the OCXO reaches its operating temperature. Extensive laboratory testing has revealed that during warm up, the OCXO frequency may vary non-linearly with time, but then settles with almost negligible variation. At power-on, the OCXO can exhibit either a rising or falling frequency gradient, before decaying over time to its normal steady state value. The testing has indicated that reasonable stability (within 2Hz/minute) is typically reached by around five minutes after an initial peak or overshoot. The testing has also shown that there can still be a significant frequency offset at the time that the oven ready flag initiates the Log-On process, so the Log-On request, Log-On Acknowledge and subsequent data bursts can all exhibit significant frequency offsets.


Notes




The short summary below is transcluded into a relevant Chronology page.

8 March 2014   02:25:34 MYT

SATCOM Log-On successfully completed; SATCOM link re-established for voice and Data Class 3. Abnormal Burst Frequency Offset (BFO) recorded, consistent with power interruption of the OCXO. No Flight ID transmitted during Log-On, indicating SDU had stopped receiving valid Flight ID from AIMS.