I have not stopped over at P4T in years, but I thought I would stop in this evening to see the discussion on this particular issue. Low-and-behold, ole CPT Bob is once again bringing me into this thing finding my last comments "interesting", but asserting that I'm a "flip-flopper".
So, to clarify a point which most folks at JREF pretty much already know. I follow facts and data. In the beginning, I may be limited on both and reach tentative conclusions which I will later revise once more facts and data are available. Interesting that CPT Bob calls this "flip-flopping" since where I come from this is called the
scientific method.
When I make ANY conclusion regarding ANY phenomena, my first course of action is to prove myself wrong. If I am able to do that, then I have no problem revising my conclusions. Everyone here at JREF is aware that I am not a subscriber to the "official story", but there is not really any margin for error for what happened to AAL77 on 9/11. There are anomalies in the NTSB record and FDR which I have spent years attempting to understand and have turned to some pretty darn talented and knowledgeable people in that effort. The only real mistake I made in that venture was using the "experts" at P4T early on in my work.
It is obvious from reading the thread at P4T, CPT Bob really has no clue what Warren is talking about. He keeps trying to make the issue at hand a function of the aircraft or aircraft system when it is not that at all. So let me help CPT Bob along since he does not seem to understand the issue.
The coding at issue is created by the FDR, not the flight systems. Experience has taught me that when I come across a "00" or "FF" in a raw file, to look at the context because often these are used as default values (much like 0 or 1 can be in binary). In this case, the coding is used to properly extract the original serial bit stream by the software doing the extraction. I find it particularly interesting that the anomaly occurs during the final frames and in the context of having a file myself with a modified date/time before the FDR was actually recovered certainly raises the question in my mind of tampering by the NTSB.
That is purely speculation and I don't have one iota of evidence to back it up. But if I was a conspiracy minded person, it would certainly be within reason to conclude that the 'NWO' was playing games with people like CPT Bob and P4T. Open up the file, replace the code corrections with some 'default' value for the end of flight leading to erroneous CSV outputs, read-outs and 3D animations. Distribute it to the public knowing that some 'tin foil' hat individual will pick up on the irregularities and out of sheer ignorance come up with all kinds of crazy theories about planes flying over the Pentagon, etc.
Of course mind you that is merely speculation on my part. Speculation is a wonderful thing but in the end it must be supported by something beyond just my imagination. So no CPT Bob, that is not my 'theory'. I'm man enough to say categorically that I have no idea what created the issue in this instance. All that matters to me is that Warren has identified the code error and developed a method for circumventing it so that we can use the data. Since the data he has extracted matches data from independent sources (eyewitness accounts, radar from 6 different sites and 2 independent sources, ATC records, physical damage) we can conclude that we now have a rather complete reconstruction of the final seconds of flight for AAL77.
Again, great job Warren and I for one greatly appreciate your efforts.
