Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Interestingly there are 7 hours of logged Inmarsat Classic Aero mobile handshake data from (IIRC) the "smart engine" telemetry.

The logged transmission round trip GroundStation -> Sat -> Aircraft -> Sat -> GroundStation provided an non unique "arc of travel" across the globe that was used by Australia to narrow the search area to a truckload of ocean floor that was substantially smaller than the entire planet.

The archived versions of the logs saved by the Malaysian gov are:

https://web.archive.org/web/20160304040818/http://www.dca.go...

Alternating sat routing would have given a more definitive fix and removed the ambiguity.



Many have lost trust in the WSPR data and Inmarsat pings. (Example: https://twitter.com/JustXAshton/status/1699535126663688544)

Your source conveniently omits weird data in the logs that start at 18:39:55UTC (a bunch of zeros, like something errored out).

Satellite pings switch to IOR at 15:59UTC and never change back to POR despite the plane flying east towards it. Going east until 17:21 UTC the plane should have pinged POR but doesn't


That's the archive.org mirror of the openly declared edited from raw logs version released by Malaysia .. so not "my source" which, back in the day, were the raw logs from ground stations.

The specific issue I have with hyper focused attention on these specific logs and hoorah about "weird data" is that I haven't seen much in the way of properly comparative analysis of a super set of broad fleet Inmarsat logs ... these in general are the trailing edge of quality data, riddled with nuls, semi handshakes, line noise, etc.

Transponders are for positioning, black boxes for logging important flight data, diagnostic interfaces for mechanics in hangers ... and component level Inmarsat .. pretty much not more than a curiousity of "because we can" that's occasionally useful when a properly formed messages truly indicates an inflight issue.

Ping routing and ping times were never meant to be consistent nor used for gross "half-LORAN" positioning .. this is all happenstance after event signal engineering hack work.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: