Hello all! And a big howdy to dMole! I am wondering whether the following has any merit and would appreciate some collective input.
Remember the LOOK Video? http://pilotsfor911truth.org/forum//index....showtopic=15017
The radar return dots continuing past the Pentagon and over the Potomac drew some notice and comment. I've been burning a hole in my monitor looking at the DCA Radar Video that it came from as well as DCA Radar Data Files released by the FAA in September 2008. It seems that they contain further information suggesting that this might not be just an artifact but rather an actual something continuing on its way (hint , , hint).
For a couple of months I've been working with a .csv data file for the DCA Radar.1 I understand it to be a processed file meaning that the FAA released a raw data file which the recipient had to run through a filtering program to create a more workable file format (similar to the FDR data). Most importantly, the latitude, longitude, azimuth and distance data in the raw file is somehow encoded in a way that makes it meaningless and useless. The processing converts the code into a common and useful format for geographic positions.
The processed file was posted on the recipient's website in .txt format and I downloaded it. The first stop was the obviously interesting last minute or so of timestamped positional data, all of which was conveniently labeled "AAL77" in the comma space for the beacon code. Searching with "Find" made it easy to extract that data from the massive file into a new very short and to the point .txt file, and rearrange it in a way that is hopefully easier to read and use. Here is that file: http://www.orbitfiles.com/download/id3928537524.html
Note the stamped times of each of the returns and that that the last one is at 13:37:46 for the purpose of comparing it to this next file.
Curious about the underlying raw file, yesterday I returned to download it. 2
Again it was easy to put the last minute or so of data into a new and handier .txt file, further assisted the fact that the relevant returns were labeled "LOOK". Here is that file:
http://www.orbitfiles.com/download/id3928536743.html Here's what I saw.
1. In general, the final AA77 data in the raw file differs materially from the processed file.
2. The final raw file return is at about 13:38:12 or about 26 seconds after the last one recorded in the processed file.
3. The last sweep in the processed file is 492 timed at 13:37:46 but the raw file has returns for six more sweeps up to number 498 at about 13:38:12.
4. The time stamps for the returns in the raw file up to number 492 are spaced in between the returns in the processed file with the raw file return for 492 timed at 13:37:43, 492 in the processed file at 13:37:46, and 493 in the raw file at 13:37:48.
5. The bulk of the data for sweeps 493 to 498 in the raw file suggest an object in continuing motion. The speed stays the same at 376 and the heading changes from 70 to 72. Just about all of the positional data changes progressively and apparently to the northeast; the only exceptions being Xv and Yv which stay the same. I am trying to figure out how to decode the positional data into conventional formats and can't plot this data until I do.
6. It seems possible that the processing of data in both files was prematurely terminated.
Please give this stuff a look and critique.
1. The whole thing can be downloaded here: http://www.aal77.com/faa/faa09122008/fadar...adar%20data.exe
2. Same as note 1: http://www.aal77.com/faa/faa09122008/fadar...a%20Dca9-11.txt