Does anyone have any evidence that CIT interviewed many more than 13 people and some of those people interviewed by CIT saw the plane on the SoC?
Warren.
-
Security incident: ISF was recently accessed by intruders. Please change your password, and change it anywhere else you used it. Read more
AA77 FDR Data, Explained
- Thread starter Anti-sophist
- Start date
-
- Tags
- aa77 flight data recorder
Does anyone have any evidence that CIT interviewed many more than 13 people and some of those people interviewed by CIT saw the plane on the SoC?
Warren.
I watched their videos and the witnesses they used pointed to the Soc. It was funny. Like Ranke and the other dolt are not capable of knowing north and south.
Ask them yourself - they'll tell you they interviewed dozens of people. Makes you wonder why those dozens aren't featured witnesses, doesn't it?
Caustic Logic
Illuminator
- Joined
- Apr 24, 2007
- Messages
- 4,494
If you have a few minutes:
http://frustratingfraud.blogspot.com/2008/03/roughshod-over-suspicious-ones.html
http://frustratingfraud.blogspot.com/2008/04/joel-sucherman-noc-witness.html
http://frustratingfraud.blogspot.com/2008/02/ladies-of-13th-and-poe.html
http://frustratingfraud.blogspot.com/2008/08/south-path-impact-documented.html
http://frustratingfraud.blogspot.com/2007/03/video-review-pentacon.html
Thanks Caustic Logic, that is the sort of information I was looking for.
Warren.
Ironic you can't ask Craig for fear of being banned at p4t for asking questions that are rational. The paranoid nut case, or DVD salesman Balsamo would ban you for researching 911.
How is your FDR research coming?
Very well, thank you beachnut.
I recently started work on the FDR file again and was delighted to find that there is a pattern to the Huffman codes that are used that make them much easier to find than I thought. I am now much more confident of being able to decompress the FDR file and then decode it.
I obtained the data frame layouts from the NTSB using a FOIA request. They are on my web site. Decompressing the FDR file has been the main hurdle for me.
I'll post findings when I have them.
Warren.
I was reading some past posts. This was a great post for summarizing Balsamo's work.That's a pretty mild claim for Balsamo. After scrupulously reviewing the FDR data, he posited that the Pentagon was attacked by a MOAB dropped from that C-130, while flight 77 skimmed over the Pentagon, made a "hard left," and "escaped" up the Potomac! That's right: a MOAB. I don't recall the people in front of the Pentagon, who watched flight 77 hit it, mistaking it for a MOAB, or of the entire Pentagon and surrounding area being laid to waste by high explosives.
In Balsamo's scenario, the minimum turn radius of flight 77 at 2.5 g and 60-degree bank, beginning at 460 kts, would have put it directly over downtown Washington, D.C., the Washington Mall, and the White House. A "north of Citgo" flightpath makes this "escape up the Potomac" fantasy even more ridiculous...if such a thing is possible.
Why is it that a former pilot has so much trouble grasping such fundamental concepts? Oh, that's right.
So far Balsamo has only found this many pilots dumber than himself on 911. http://pilotsfor911truth.org/core.html (less than 110) Why do people fall for the moronic implications of delusions Balsamo offers?
A p4t source offered a more complete data decode that was missing a second that the NTSB included in their files of selected FDR parameters. Depending on the software, there are data blocks that do not readily decoded from the compressed data for a variety of reasons. If p4t decoders ever answered why their decode was missing a second the NTSB had, I missed it.
Note the NTSB data includes data not in the p4t source. NTSB file.
The altitude and airspeed in yellow. In the p4t source decode the next second is missing. p4t decode.
Data expected to be retrieved from the FDR can be missing for many reasons. Differences in decoding software or methods can produce different data sets.
There can be information in the FDR not presented in software decodes. The proof is the data I have from two different sources decoded from the same FDR data shown above. When you develop software to present your data, when the program fails to decode due to software limitations or errors you can fix the software after studying the problem at hand.
Flight 77 impacted the Pentagon and the FDR was found in the Pentgon. There is no doubt 77 impacted the Pentagon. The files presented by the NTSB of data decoded from the FDR does not mean there is was not more data in the FDR. Proof of this point is the missing data from the p4t decode. Why is the p4t decode missing a second the NTSB has? Don't expect Balsamo to figure this out.
Wow! Warren is working through 19,944 lines of descriptors for 1110 parameters to decode/decompress the FDR. A thesis project plus.
http://warrenstutt.com/NTSBFOIARequest2-1-09/CDROM/757-3b_1.TXT This is one of the files he works with to decode the FDR.
Last edited:
Thanks for the kind words again beachnut. I have written and tested my new FDR decoder program and am now working on the documentation to put on my web site. I'll announce it here and at P4T when it is ready. This should hopefully be in the next day or two.
My program only decodes a few parameters at this point. I will be open to suggestions on other parameters that people are interested in seeing.
Warren.
The data stored includes who is keying which VHF radio control on the aircraft. Example: in the case of Flight 93 you can see the moment the terrorist keys the VHF radio and talks on Center frequency. Then you can get the tape of the FAA and hear the terrorist sitting the left seat talking on the VHF radio. The FDR can be a nightmare for you if you are trying to hide what you did.
The final true track would be interesting. NAVtrackangletrue in other decodes (a77.2_complete.csv, column NF) and Track Angle True (DEG) in the NTSB decode (column LO). It may be a derived parameter by taking the true heading and apply the drift angle.
My new program to decode AAL77's raw FDR file is now ready.
I am making it available for download along with it's source code and some output files from the program.
You can read more about it here
It decodes almost 4 more seconds of data than what appears at the end of the NTSB CSV file.
I welcome suggestions for any more parameters you would like decoded or any other features you would like added.
I will also be discussing this on Pilots for 911 Truth at http://pilotsfor911truth.org/forum/index.php?showtopic=18239 as well as here.
Thanks beachnut, I'll add the TRACK ANGLE TRUE, VHF LEFT KEYING, VHF RIGHT KEYING and VHF CENTER KEYING parameters to the next release.
Warren.
I am making it available for download along with it's source code and some output files from the program.
You can read more about it here
It decodes almost 4 more seconds of data than what appears at the end of the NTSB CSV file.
I welcome suggestions for any more parameters you would like decoded or any other features you would like added.
I will also be discussing this on Pilots for 911 Truth at http://pilotsfor911truth.org/forum/index.php?showtopic=18239 as well as here.
Thanks beachnut, I'll add the TRACK ANGLE TRUE, VHF LEFT KEYING, VHF RIGHT KEYING and VHF CENTER KEYING parameters to the next release.
Warren.
Dave Rogers
Bandaged ice that stampedes inexpensively through
Ouch. Isn't that, on its own, more or less a death blow to any flyover theory based on the FDR data?
Dave
One cannot kill what is already dead... 
But it is consistent with our earlier claims, i.e. why the FDR record seemed to end several seconds before impact. Plenty of people claimed that it was "impossible" for various contrived reasons, but these new data demonstrate conclusively that our suspicion was not only reasonable, it appears to be correct.
Good work, Warren. Looking forward to the rest.
But it is consistent with our earlier claims, i.e. why the FDR record seemed to end several seconds before impact. Plenty of people claimed that it was "impossible" for various contrived reasons, but these new data demonstrate conclusively that our suspicion was not only reasonable, it appears to be correct.
Good work, Warren. Looking forward to the rest.
Thank you Warren, I appreciate all of your hard work on this. I'll have a look at the numbers a bit later. I'm particularly curious to see the radar altitude 1 second from end of data. That may quell PfT's "too high to hit the light poles" notion.
W.D.Clinger
Philosopher
Thank you, Warren. You have made a major contribution here.
Those theories never made a lick of sense. If the flight data recorder found within the Pentagon came from the plane that hit the Pentagon, then that plane didn't fly over the Pentagon no matter what its FDR data say. Otherwise the discovery of the FDR within the Pentagon would be more than passing strange, and any theory constructed from its data would be just as suspect as its presence within the Pentagon.
By recovering four more seconds, Warren has confirmed the missing seconds that John Farmer and others had deduced.
The vertical accelerations tell quite a story. You can see the beginning of the final descent in subframe 151364, ranging from .613g to .757g. You can see the plane starting to pull out of the descent around subframe 151366, increasing from .982g to as much as 2.264g in subframe 151367 and continuing through the last vertical deceleration recorded, 1.945g. As should be expected from an unskilled pilot, those g-loads are a little higher than would be needed for a smooth descent.
I see that Rob Balsamo is already trying to spin the new data: "Still too high to hit the pentagon." Indeed, he's trying to talk to us from his own private forum. Here, Rob, are some calculations that may help you to comprehend the new data:
http://www.ccs.neu.edu/home/will/Music/Jokes/Balsamo/balsamo2.html
Will
Those theories never made a lick of sense. If the flight data recorder found within the Pentagon came from the plane that hit the Pentagon, then that plane didn't fly over the Pentagon no matter what its FDR data say. Otherwise the discovery of the FDR within the Pentagon would be more than passing strange, and any theory constructed from its data would be just as suspect as its presence within the Pentagon.
By recovering four more seconds, Warren has confirmed the missing seconds that John Farmer and others had deduced.
The vertical accelerations tell quite a story. You can see the beginning of the final descent in subframe 151364, ranging from .613g to .757g. You can see the plane starting to pull out of the descent around subframe 151366, increasing from .982g to as much as 2.264g in subframe 151367 and continuing through the last vertical deceleration recorded, 1.945g. As should be expected from an unskilled pilot, those g-loads are a little higher than would be needed for a smooth descent.
I see that Rob Balsamo is already trying to spin the new data: "Still too high to hit the pentagon." Indeed, he's trying to talk to us from his own private forum. Here, Rob, are some calculations that may help you to comprehend the new data:
http://www.ccs.neu.edu/home/will/Music/Jokes/Balsamo/balsamo2.html
Will
And ideas on why the decoder from p4t failed to get the final 5 seconds and the NTSB did not get the last 4 seconds? Could it be the Sync Lost?
The p4t truthNAZI will think the final data is the impact point. He will draw a photo of Flight 77 going over the Pentagon and vanishing in thin air and imply the MIB did it.
That was a lot of work; I think the p4t decode was made with lifted software, not an original effort. Good work.
... cool. The things "poor truthNAZI Balsamo" does not understand in math can fill volumes; you could do a thesis on his errors. Oops, you did.
He still has problems with DME, the only values stored in the FDR are x.0, x.25, x.5, x.75 and he has no clue what this means with regard to accuracy to recreate where 77 is (let alone the sample rate of .25 hz). And when you throw in the errors due to DME itself he melts down. No wonder he never will fly heavy jets.
Last edited:
As far as the NTSB decode goes, yes, it could simply be that their software did not decode incomplete frames. The frame with the almost 4 seconds of extra data has only 1007 of 1020 * 12 bit words.
As far as Undertow's Readout 2 goes, he said on his web site:
I can see that indeed, for the ends of the sections of compressed data represented by the rows of #ERROR in rows 29, 47 and 74 in a77.2_complete.csv, only the last incomplete subframe has not been decoded, but at the end of a77.2_complete.csv, the last 4 complete subframes as well as the last incomplete subframe have not been decoded. I don't know the reason for this. BTW, subframe number 146102 in my program corresponds to the beginning of a77.2_complete.csv. I could produce a decode starting at that point if you like.
Warren.
Thanks and also thanks R.Mackey and W.D.Clinger.
Warren.