Why Can't We Find MH370 ?
Video Statistics and Information
Channel: Curious Droid
Views: 2,278,658
Rating: 4.8984814 out of 5
Keywords: paul shillito, curious droid, mh370, astb, ntsb, malaysian mh370, missing plane, why cant we find mh370, boeing 777, inmarsat, malaysia airlines, flight mh370, side scan sonar, multibeam sonar, ocean infinity, seabed constructor
Id: mxsfIlZlpV8
Channel Id: undefined
Length: 18min 5sec (1085 seconds)
Published: Thu Aug 27 2020
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
Someone will find it one day like the titanic at the bottom of the Atlantic
So many inaccuracies. SMH.
Misunderstands ACARS. Erroneous attribution of CAPTIO's comments to RAeS.
Only 18 minutes sunk.
This is a very good review video.
However, they seem to have adopted many of France's/MH370-Captio's theories, and they are not giving IG's efforts equal consideration. Thus some of the specific data interpretations, such as (1) proposed RAT deployment at IGARI, and (2) proposed water ditch damage to the flaperon, are hotly contested. Also I am not a big fan of Captio's Xmas Island theory anymore.
I agree with premise that MH370 *might* be found with $Billion dollar search including re-analysis of the data.
I also agree in Malaysia, saving face is the main societal consideration, and so that means we probably leave MH370 on the ocean floor. Maybe a small search, Malaysia bowing to pressure.
Current search has no help from Malaysia and does make simplifying assumptions such as straight flight, crash near Arc7, basically resting in a "findable" spot. We have not yet even searched the search area bounded by simplifying assumptions, let alone the less simple case of "active" pilot possibilities, which are huge in area and potentially magnitudes worse in search-difficulty, if MH370 was possibly downed in a hard to find terrain location of extreme depths.
Who was on that jet that important for it to be covered up this good? There's footage of this on board one of Elons starlink satellites I'm sure, assuming they really do TRIP(time-reversed infrared photography).
u/Gysbreght thanks for sharing your radar analysis. I did the same analysis back when ALSM shared the (updated) data with sufficiently precise timestamps. As the investigators discovered, calculating point-to-point speed produces a horrible amount of noise in derived speed and course. You need to calculate SOG/COG across 4,8,10 data points to get a smoother picture. Because the range data is highly accurate, the main noise problem is coming from the radar's azimuth data. If you smooth that (which is entirely defensible since it is impossible for the a/c to jig around every 4s) you can then obtain an exceptionally smooth speed derivation. Smoothing speed and azimuth in this way only really works for straight-ish sections, so more difficult to apply during the turn after clearing the west coast of peninsular Malaysia. Nonetheless, my final conclusion was that:
So one hypothesis consistent with observed speeds and speed variations is that the transit was flown at M0.87/FL340 until clearing the west coast, then reduced to M0.84 /FL340.
There remains the puzzle of arriving at Arc1 around 100s early. If you model it at M0.84 from the 1802 LKP the steady diminution in tailwind scrubs about 20s of that, but you still arrive ~80s too early (if memory serves). Implying either an offset between the timebase of the radar and the satellite datasets, or a jig to the right (the so-called SLOP), or throw out LIDO data and presume a slow-down/different trajectory towards Arc1.
Closer inspection of LIDO suggests to me that the trace up to 1802 (in fact slightly after*) is the Butterworth datasource because the position datapoints are so much denser (sweep period 4s) and the squiggles look the same. While the military radar has 10s period. I haven't simulated 10s spacing on position points to test this hypothesis but would be interesting to try and match it up against LIDO. It it does match, that would a) be a sort of validation of the data b) derive the corresponding timestamp for the majority of LIDO datapoints with illegible timestamp labels. Would be an interesting exercise to try if I can find the time.
*speculative: slightly after might reflect "coasted" datapoints that are on the radar record but discarded from the version shared with ALSM.
Food for thought.
Radar Kota Bharu cumulative increments track distance versus time, resulting groundspeeds shown in the chart:
https://www.dropbox.com/s/t069eyanlbmkrtb/Radar_cumulative_vs_time.pdf?dl=0
Food for thought (2)
https://www.dropbox.com/s/a42nh6wcpb32evj/MH370_Analysis_Civil_Radar.pdf?dl=0
Edited 20-10-19 (incorrect figure 6 corrected to figure 9)
The autopilot is off from the "Air Turn Back" until the end of primary radar at Pulau Perak at 18:01:59 UTC.
The civil radar at Kota Bharu and Butterworth provides accurate and detailed data. Military is can be accurate be can be sometimes error. The civil radar data groundspeed from 420 kt increased to 520 - 540 kts at the time entered the "Cone of Silence" at radar at Kota Bharu. The groundspeed then decreases to 500 kt, increases again to about 540 kt, then again at 500 kt at end the radar data near Pulau Perak.
https://www.dropbox.com/s/23lfowgnomrcpad/MilitaryRadar_SafetyInvestigationRept.pdf?dl=0
https://www.dropbox.com/s/kjvf7ic6j32hb7u/Civil_and_Bayes_Groundspeeds.pdf?dl=0
Posted by u/pigdead 8 months ago
Visualisation of MH370 radar data back across Malaysia
Filtered course data over a slope 15 points:
https://www.dropbox.com/s/d7su8cn6ojyzeao/15-point%20slope%20course%20Kota%20Bharu%20radar.pdf?dl=0