Flight Data Expert Confirmation: No Evidence Linking Fdr Data To American 77, FDR Data Exceeds Capabilities Of A 757, Does Not Support Impact Rating Options

[rob balsamo]

Flight Data Expert Confirmation: No Evidence Linking FDR Data to American 77
FDR Data Exceeds Capabilities Of A 757, Does Not Support Impact With Pentagon

(PilotsFor911Truth.org) - Flight Data Recorder Expert Dennis Cimino has confirmed that the data being provided through the Freedom Of Information Act (FOIA) by the National Transportation Safety Board (NTSB) is missing crucial information, which according to Dennis, should be present and link the data to a specific aircraft and fleet. The NTSB provided three sets of data through the FOIA for what they claim is from American 77, N644AA. A csv file, an animation reconstruction and a raw data file. Rob Balsamo of Pilots For 9/11 Truth along with numerous other aviation experts, including trained Aircraft Accident Investigators have analyzed these files and determined they do not support an impact with the Pentagon. The data also exceeds the design limitations and capabilities of a standard 757 by a wide margin. This is based on data, precedent and numerous verified experts, including those who have actual flight time in the aircraft reportedly used for the 9/11 attacks (See - "Flight Of American 77", "9/11: Attack On The Pentagon" and "9/11: World Trade Center Attack" at Pilotsfor911Truth.org for full detailed analysis and interviews).

One file in particular, the compressed binary raw file alleged to be a direct data dump from the Flight Data Recorder, was recently analyzed by an alleged computer expert. He has claimed to decode 4 more seconds worth of data, above and beyond the NTSB decode, although the "additional" data has not been verified by anyone. The claim was made that the reason the NTSB did not decode this "additional" data is because the software used by the NTSB, along with the software used by the manufacturer of the FDR (L3 Communications), has an alleged "bug". If correct, this has grave consequences for Flight Safety as Flight Data is used in the promotion of safe flight through changes in regulation and procedure. The NTSB and L3 have been contacted, along with an Aviation Safety Report being filed with NASA. There hasn't been any reply confirming such a "bug".

A paper was recently published by the mentioned computer "expert" along with an alleged Chemist as the authors. They claim the extra 4 seconds support an impact with the Pentagon. They base this claim on a Radio Altimeter parameter in which the NTSB has listed as "Not Working or Unconfirmed" in the NTSB FDR Report(1). When cross-checked with the "Working and Confirmed" Primary Altimeter True Altitude data, the aircraft is still too high to hit the Pentagon(2). This can only mean that the Radio Altimeter was measuring from an object above ground level.

Radio Altimeters do not guarantee measurement from the ground. The device measures whatever object you are flying over within a certain range (a building, trees... etc). The tracking capability of the Radio altimeter is 330 feet per second, or a little under 200 knots(3). According to the data, the aircraft was traveling at a speed of 460-480 knots. Well outside the limits of the Radio Altimeter tracking capability, not to mention well outside the capabilities of a standard 757.

It is interesting that the authors, editors and Journal in which the above mentioned paper is published is highly critical and skeptical of the National Institute Of Standards And Technology (NIST) data and reports with respect to the collapse of the World Trade Center, yet is now attempting to use unverified data from another government agency to support the government story regarding a Pentagon impact. Motives are even more puzzling especially when the NTSB data in fact does not support an impact while exceeding the performance limitations and capabilities of a standard 757 as set by the manufacturer based on wind tunnel and flight testing, by a wide margin. This is also corroborated by precedent. It is also clear the paper was not reviewed by any aviation expert prior to publish, as it is littered with speculation and gross errors. For more information regarding this paper and the numerous errors it contains, please see the discussion at the Pilots For 9/11 Truth Forum(4).

FDR Expert Dennis Cimino further goes on to state:

[I]t just all comes down to two data fields being zeroed out. no tickee, no laundry. without those, there can... never be any linkage of the FDR to an 'N' number in the F.A.A. registry. not because the 'N' number is in the AC ID field, but the AC ID FIELD number is directly traceable to an N-Number in the F.A.A. registry, and the FLEET ID shows which carrier it went to.

[T]hose missing, that [data] could come from anywhere...


[N]obody flies boxes with that data zero'ed out or missing. without this data in the CPM [Crash Protected Memory], in the preamble, there can be no linkage to an aircraft N-Number.

I saw that on the first look.... the test person who extracted that data should have seen the NO ACFT ID and NO FLEET ID and said; "oh, this is such bullshit" and then asked his supervisor why they were asking him to decode BULLSHIT.

Dennis Cimino experience and qualifications:

Electrical Engineer
Commercial Pilot Rating, since 1981
Navy Combat Systems Specialist: RADAR, ECM, cryptographic communications
Flight Data Recorder Engineer Smiths Aerospace
BA-609, IDARS, Military and Commercial
Millimeter wave RADAR and countermeasures expert since 1973
Two patents held for Doppler RADAR ( Kavouras ):
long pulsewidth RADAR droop compensation network,
and wave guide arc detection for high powered RADAR

Further confirmation that there isn't any evidence linking the FDR data to "American 77", tail number N644AA is discussed here:

Can The Govt Get Their Story Straight? - Location Of Flight Data Recorder

Lies, Conflicting Reports, Cover-Up's - Location of American 77 Flight Data Recorder - Part II

9/11 Aircraft 'black Box' Serial Numbers Mysteriously Absent

Interview With Flight Data Recorder Expert

So, if the data is not from N644AA, does not support an impact at the Pentagon, and in fact exceeds the capabilities and performance of a standard 757, what caused the damage at the Pentagon? That is exactly what Pilots For 9/11 Truth are trying figure out and the reason there needs to be a new and truly independent investigation. Some wish to ignore this data, some without expertise attempt to analyze it while attempting to say, "nothing to see here folks, move along..". Please write your Congressional Representatives and Senators. Call into talk shows, tell them there is a growing list of aviation professionals who question the government version of events on 9/11. Tell them the data being provided through the FOIA does not support the government story.

Founded in August 2006, Pilots For 9/11 Truth is a growing organization of aviation professionals from around the globe. The organization has analyzed Data provided by the National Transportation Safety Board (NTSB) for the Pentagon Attack, the events in Shanksville, PA and the World Trade Center Attack. The data does not support the government story. The NTSB/FBI refuse to comment. Pilots For 9/11 Truth do not offer theory or point blame at this point in time. However, there is a growing mountain of conflicting information and data in which government agencies and officials refuse to acknowledge. Pilots For 9/11 Truth Core member list continues to grow.

http://pilotsfor911truth.org/core.html for full member list.

http://pilotsfor911truth.org/join to join.

(1) http://www.ntsb.gov/info/AAL77_fdr.pdf
(2) http://pilotsfor911truth.org/forum/index.p...&p=10778240
(3) http://www.rockwellcollins.com/ecat/at/LRA-900.html
(4) http://pilotsfor911truth.org/forum/index.php?showtopic=20960

[wstutt]

Hi Dennis Cimino,

I have now decoded the FLEET IDENT and A/C NUMBER parameters from the FDR data according to the generic Boeing data frame layout 757-3B. When they are interpreted as unsigned integers they have values of 1 and 35 respectively. Although they were not in the text preamble of the file where you were expecting to find them, do you think they could be used to identify the aircraft? They do not appear to me to be a tail number, however if I understand you correctly, you were not expecting them to be a tail number.

I see from Rob Balsamo's list of your credentials that you have experience with Doppler RADAR. It has been suggested that since at least one make and model of radio altimeter that is used to measure an aircraft's height above the ground and that has been used in 757s has a specified tracking capability of 330 feet per second that such a radio altimeter would not work correctly if the aircraft in which it is installed has a speed faster than 330 feet per second. I do not immediately see a reason why this would be so. However, I could see how the Doppler effect would impact the accuracy of the radio altimeter if the distance between the aircraft and the ground is rapidly changing.

Would the tracking capability of the radio altimeter be referring to the speed of the aircraft as has been suggested or to the rate of change of the height of the aircraft above the ground? If it is the former, could you explain why or cite a reference where I can read about it?

Warren Stutt.

[Dennis Cimino]

<br />Hi Dennis Cimino,<br /><br />I have now decoded the FLEET IDENT and A/C NUMBER parameters from the FDR data according to the generic Boeing data frame layout 757-3B. When they are interpreted as unsigned integers they have values of 1 and 35 respectively. Although they were not in the text preamble of the file where you were expecting to find them, do you think they could be used to identify the aircraft? They do not appear to me to be a tail number, however if I understand you correctly, you were not expecting them to be a tail number.<br /><br />I see from Rob Balsamo's list of your credentials that you have experience with Doppler RADAR. It has been suggested that since at least one make and model of radio altimeter that is used to measure an aircraft's height above the ground and that has been used in 757s has a specified tracking capability of 330 feet per second that such a radio altimeter would not work correctly if the aircraft in which it is installed has a speed faster than 330 feet per second. I do not immediately see a reason why this would be so. However, I could see how the Doppler effect would impact the accuracy of the radio altimeter if the distance between the aircraft and the ground is rapidly changing.<br /><br />Would the tracking capability of the radio altimeter be referring to the speed of the aircraft as has been suggested or to the rate of change of the height of the aircraft above the ground? If it is the former, could you explain why or cite a reference where I can read about it?<br /><br />Warren Stutt.<br />

<br /><br /><br />


Mr. Stutts:

I now have to define your entire 'work product' as utter and total BULLSHIT. You had about 4 days to come up with a better bullshit story than this one, and to propose that AC ID and FLEET ID are buried in the flight parameter stream after the preamble, where it always always always is, is so beyond the pale and absurd, that it's now not conjecture that you're a COIN OP (counterintelligence) from either the U.S. government, or the mossad, but you're actually a very badly managed one, to float this shit.

You failed to address any of the incongruencies I published about the entire event, not even one of them. Now, as a non pilot, I don't expect you to try to understand how the entire thing is absurdity from the very start to assert that an 80 ton plane went thru the 'cat door' at the Pentagon, and didn't leave any wreckage till the F.B.I. began to seed it later that morning with the Buga, Colombia jungle weathered wreckage. I can understand that, as you would have no way to explain the lack of aircraft upset during a violent and ugly hijacking, and also, the Altimeter setting in the NTSB fabricated crap in one of their products, because they were so sloppy they failed to both see it and understand it's importance here, in that this, as well as the no aircraft upset, and the lack of rudder inputs, while not on A/P., and the impossible pullout from the dive, all were so impossible that only in a child's game could any of this hokey shit be believable.

So now I have to say for the record you guys are a COIN OP for the people who did this. I gave you the benefit of the doubt to prove you were not a bullshit mill for Sunstein's cognitive infiltration network of zio prostitutes for Israel, and you totally blew that gig here.

I tell you what. Go sell this to the National Enquirer. They might print your dissertation. But no meaningful and relevant aviation based analysis validates any of your turd feed here, because virtuallly all of your stuff has borne itself out to be so absurd that even the Enquirer would probably balk at publishing your disinformation.

I'm sorry, Mr. Stutts, but you unmasked yourself with this total, utter bullshit today. And we didn't even have to do it for you, you did it yourself.

[wstutt]

Dennis Cimino,

<br /><br /><br />


Mr. Stutts:

I now have to define your entire 'work product' as utter and total BULLSHIT. You had about 4 days to come up with a better bullshit story than this one, and to propose that AC ID and FLEET ID are buried in the flight parameter stream after the preamble, where it always always always is, is so beyond the pale and absurd, that it's now not conjecture that you're a COIN OP (counterintelligence) from either the U.S. government, or the mossad, but you're actually a very badly managed one, to float this shit.

Let me get this straight. I find the AC ID and FLEET ID in a different part of the file from where you were looking, so they are BS?

You failed to address any of the incongruencies I published about the entire event, not even one of them. Now, as a non pilot, I don't expect you to try to understand how the entire thing is absurdity from the very start to assert that an 80 ton plane went thru the 'cat door' at the Pentagon, and didn't leave any wreckage till the F.B.I. began to seed it later that morning with the Buga, Colombia jungle weathered wreckage. I can understand that, as you would have no way to explain the lack of aircraft upset during a violent and ugly hijacking, and also, the Altimeter setting in the NTSB fabricated crap in one of their products, because they were so sloppy they failed to both see it and understand it's importance here, in that this, as well as the no aircraft upset, and the lack of rudder inputs, while not on A/P., and the impossible pullout from the dive, all were so impossible that only in a child's game could any of this hokey shit be believable.

Regarding the impossible pullout from the dive, are you referring to the 10.14G calculation? Have you checked it?

As regards the other incongruences, I am not a pilot as you said.

So now I have to say for the record you guys are a COIN OP for the people who did this. I gave you the benefit of the doubt to prove you were not a bullshit mill for Sunstein's cognitive infiltration network of zio prostitutes for Israel, and you totally blew that gig here.

I tell you what. Go sell this to the National Enquirer. They might print your dissertation. But no meaningful and relevant aviation based analysis validates any of your turd feed here, because virtuallly all of your stuff has borne itself out to be so absurd that even the Enquirer would probably balk at publishing your disinformation.

<snip>

Are you saying that my decoder program does not actually decode the FDR file? If so, prove it.

Warren.