Time:0029:33 MYT

MH370 DECODED
Jump to navigation Jump to search

Time:0029:33 MYT

0. Event Time and Type

Event Time:  00:29:33 MYT   Edit.

Note: The Event Time includes a link to the NS_Time page. See sample code below:-

<html><a href="/Time:NNNN UTC/MYT" target="_blank"> emsp;</a></html>NNNN MYT

Event Type: satcom acars   Edit.

Note: The colour scheme is defined by the Event Type.


1. Summary ..................................................................................................Edit

This summary will be transcluded onto the relevant Timeline page.

A status report for the Auxiliary Power Unit (APU) was generated by the Aircraft Condition Monitoring System (ACMS) which is interfaced with ACARS. The APU Report was then sent by ACARS over the satellite communications datalink.

The report stated the total APU cycles and hours were 15,699 cycles and 22,093 hours. APU hours for the previous flight was 4 hours.


Content below will be transcluded into the relevant Event Details Page.

2. Details .......................................................................................................Edit

  1. Safety Investigation Report MH370/01/2018 Appendix 1.9A


    Time
    16:29:33
    Trans
    46818489
    Direction
    Incoming Downlink
    AN
    9M-MRO
    FI
    MH0370
    Medium
    IOR2
    Machine
    MHKULKJACM001
    Raw DTG
    071629
    SMI
    DFD
    Application
    RELAY
    Status
    Normal
    Message Type
    B777 APU Report
    Source/Destination
    QXSXMXS

    QU DPCCAMH
    .QXSXMXS 071629
    DFD
    FI MH0370/AN 9M-MRO
    DT QXT IOR2 071629 D00A
    - MAS002A0     B777 APU OPS REPORT         332

    ACID FLT FM FLCT DATE GMT DPT DST
    MRO S370 PO 318 07/03/14 16:29:12 WMKK ZBAA
    SWID SFC
    316A-BSM-710-02 17911
    APU CYC APU TOT HRS APU PREV FLT HRS
    15699 22093 4




3. Notes .........................................................................................................Edit





Explanatory Notes
  1. Content for Timeline pages is transcluded from sub-pages for each relevant page in the Time namespace.
  2. See Help:Manual/Time and Timeline for explanatory notes and/or instructions.
  3. There is no content in this page; nothing is transcluded from this page. Do not add anything to this page.
  4. Transcluded sections from sub-pages and become content in the Timeline and Event Details pages.
  5. Use the sections above to check the content and check that links work correctly.
  6. The 'Edit" links open the sub-page for editing.
  7. From October 2023 a non-visible link placed before the Event Time links back to this page. This is included in the Summary on both the matching Timeline page and the Event details page. This provides a quick link to the source (in the NS_Time namespace).






This page contains references for events related to Flight MH370 which occurred at, or near, the time of 0029:33 MYT, Saturday, 8 March 2014.
Note: Malaysian Time (MYT) is Coordinated Universal Time (UTC) plus 8 hours.

Narrative

<section begin=Narrative />

00:29:33 MYT, 8 March 2014
ACARS: APU Report

A status report for the Auxiliary Power Unit (APU) was generated by the Aircraft Condition Monitoring System (ACMS) which is interfaced with ACARS. The APU Report was then sent by ACARS over the satellite communications datalink.

The report stated the total APU cycles and hours were 15,699 cycles and 22,093 hours. APU hours for the previous flight was 4 hours.

<section end=Narrative />


References
Item 1
RefID:Factual Information March 2015/1.9.4.1

1.9.4.1 ACARS Traffic Log

Data on aircraft APU is shown in Figure 1.9H below. APU report generated by ACMS sent via ACARS at 1629:33 UTC stated the total APU cycles and hours were 15,699 cycles and 22,093 hours. APU hours for the previous flight was 4 hours.

Figure 1.9H: APU Report


Engine take-off and climb reports transmitted via ACARS are explained in Section 1.6.3.8.

Engine parameter reports were transmitted to MAS and then to Rolls Royce for Engine Health Monitoring (EHM). Appendix 1.9A shows these data in coded form. The decoded data are shown in Appendix 1.6B.


Item 2
Transcript

{{#lst:Content:FI Appendix 1.9A/0029:33 MYT|Reference}} {{#lst:Content:FI Appendix 1.9A/0029:33 MYT|FullText}}

Notes