The “tracks” on those websites are created by civilian receivers that transmit info of planes they detect. There’s a huge margin of error, and a plane’s reported “position” can jump by dozens, if not a hundred, miles as it moves from one coverage area to another, particularly when it crosses a coastline. Not to mention, that’s a privately-run website, not some “official source”. All that video demonstrates is the imprecision of the websites track-generator algorithm.
Proof of what?
Variations in course are a normal thing for these tracking sites. The aircraft was en route to Beijing and its course...until near the last, was in accordance with that.
On the night it happened, I heard one report that the transponders from the aircraft itself showed an abrupt departure from course, slowing of speed, and abrupt drop in altitude of several hundred feet in the few seconds before the transponder went dead altogether.
IMHO, this is indicative of a catastrophic failure and disintegration of the aircraft at speed and at high altitude (35,000 ft).
If that indeed occurred...we are still not sure at all why it occurred. My own opinion is that it is more likely a human induced cause, and perhaps terrorism.
But until they find the flight and voice recorders, and can see some of the debris, we will not know enough to be sure.
It’s sitting in a hangar at Wright-Patterson. I can’t say any more.
Dude.... 0 feet .. 10,000,feet, 32,000 feet.. 0 feet...
Dude...
Here’s a good, but long, explanation of how sites like this actually work:
http://www.flightradar24.com/how-it-works
The missing plane is B772 9M-MRO
He's comparing it to flight plan of aircraft 9M-MRMQ which flew same route as MH370 (same flight number) the NEXT day.
The day after aircraft # 9M-MRE flew that route.
See: FlightRadar24 (Full flight history for Malaysia Airlines flight MH370).
March 8th statement from “Flightradar24” on their Facebook page:
The ADS-B transponder of an aircraft is transmitting data twice per second. FR24 saves data every 10-60 second depending on altitude. On cruising altitude data is normally saved once per 60 seconds. By analyzing all our databases and logs we have managed to recover about 2 signals per minute for the last 10 minutes.
The last location tracked by Flightradar24 is
Time UTC: 17:21:03
Lat: 6.97
Lon: 103.63
Alt: 35000
Speed: 471 knots
Heading: 40
Between 17:19 and 17:20 the aircraft was changing heading from 25 to 40 degrees, which is probably completely according to flight plan as MH370 on both 4 March and 8 March did the same at the same position. Last 2 signals are both showing that the aircraft is heading in direction 40 degrees.
Today there are reports in media that MH370 may have turned around. FR24 have not tracked this. This could have happened if the aircraft suddenly lost altitude as FR24 coverage in that area is limited to about 30000 feet.
FR24 have not tracked any emergency squawk alerts for flight MH370 before we lost coverage of the aircraft. Playback for flight MH370 is available on
http://www.flightradar24.com/data/flights/mh370#2d81a27
If you have questions about how Flightradar24 works, please read
http://www.flightradar24.com/how-it-works
The “fast” track aircraft and some of the other anomalies are probably just network traffic delay related; the aircraft do not speed up/slow down like that shown via the ATC/tower radar systems.
Also, no object goes from 35,000 ft. to zero ft. in one or two frame updates. This is another network traffic artifact.
I'll wait for the real investigators to do their job. These arm chair guys are a wast of my time.