Here is the raw FR24 data. If mh370 turned to the right on hdg 40 at 1:21, st what time did the left turn seen by military radar occur?
Following is all the ADS
-B data i could gather from 1642 to 1721 UTC
255 cue points with time, altitude and speed data (and discontinued lat/long, climb rate and squawk data).
- "FR24 Gr" = FlightRadar24 graph (MH370 - Malaysia Airlines - Flight history - Flightradar24). The raw figures (time, alt & speed) for the 185 cue points of the FR24 graph are included in the page's source code, all i had to do was grab them and translate them in the right units.
- "FR24 Pn" = FlightRadar24 "pinned" page (same url). The data you get each time you press the FWD button. Adds location and heading to some of the 185 "FR24 Gr" points.
" = Google Earth. For the first "FR24 Pn" points (just after takeoff, in the 327° straight line), i got the lat and long data from Google Earth. Presumably it can be done with every other "FR24 Pn" cue point, that's why i marked their missing lat/long data with a "*"
- "FR24 Pb" = FlightRadar24 "playback" page (Flightradar24.com - Live flight tracker!). Oddly enough, the points are not the same as in the "pinned" page. And these ones also include the climb rate, the squawk and the data feeder (registered ADS
-B receiver which the data came from)
" = FlightAware data (Registre de suivi des vols ? MAS370 ? 08-03-2014 ? WMKK / KUL
- ZBAA / PEK
? FlightAware). No squawk data on this one, and some minor discrepancies when compared to FR24 heading and velocity data.
" = PlaneFinder. 3 additional cue points, still better than nothing.
Once all this data collected, i ordered them by growing altitude until FL350, and adjusted the remaining cue points, based on their timestamp (feel free to interpolate the points where seconds are replaced by XX).
-B feeder;Data Source