Skip to content
Data and analysis of primary radar track of flight MH370
Python
Find file
New pull request
Latest commit 5d79f4b @kprostyakov Readme fixed
Failed to load latest commit information.
README.md Readme fixed
radar.py Track correction for altitude
utm.txt Track correction for altitude

README.md

MH370-radar

The plane radar track is based on points digitized from infamous Lido image (https://github.com/sladen/inmarsat-9m-mro/tree/master/radar) and also figures on p.29 and p.30 of Factual Information document. These track include 2 segments from Kota Bharu radar, 2 segments from Butterworth radar (both are fed to KL ATC), and also 2 segments from Western Hill military radar in Penang.

utm.txt lists digitized coordinates (UTM zone 47N) for all tracks along with time stamps inferred from text of FI and off Lido image. 10second coasting delay was substracted for track endpoints.

Altitude up to 17-40 is given as per text of FI (from Gong Kedak RMAF radar). Later altitude values are varied manually to decrease speed variation for segments close to KB and BW radars. This works because range is initially plotted without respect for plane altitude. If altitude is introduced, new track positions are pushed closer to radar, making segments longer and effect is strongest for closest points. Another constraint for radar flyby is cone of silence - for secant squared antennas the angle from horizon to cone is about 30deg. This means the plane was flying almost at maximum altitude over Penang.

Ground speed was found to increase to a/c maximum 3 times, just before climbs. The a/c left radar coverage at altitude close to operating ceiling at ground speed of 515 kts.

Something went wrong with that request. Please try again.