It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Some features of ATS will be disabled while you continue to use an ad-blocker.
QUOTE (23investigator @ Jan 3 2012, 01:26 AM) *
Dear Mr Ciminio.
Thank you again, for the extra effort you have made, to clarify matters.
Does the FDR information you have analyzed, suggest to you, that the aircraft the FDR was mounted in, had two engines?
From Dennis -
To Robert S:
“ from what I see in the data stream that was released by the N.T.S.B., the evidence supports that this data was heavily modified using a bench unit, using ground power in a lab, and does not reflect normal twin engine start sequencing and generator’s going on line, before every FLIGHT data segment loaded into it. In addition, I want to point out that the header data erasure signifies that this record was written to by a BENCH UNIT ON GROUND POWER, and that in layperson’s terms, means that it disqualifies the data entirely because during extraction post crash, the WRITE ENABLE JUMPER on the BENCH UNIT used for the post mortem data extraction for this unit, was in place, and
in-fact, nobody would ever jumper those two pins on the FDR for extraction, and furthermore, the software in the extraction rack WARNS YOU that you are about to perform a WRITE to the CPM. Now, I don’t know what L-3 people were thinking, but
if they were trusted to do the extraction without at least ONE trusted witness from the
N.T.S.B. who would not look the other way and allow a WRITE to take place on that data record in the CPM module, and that a checklist that made damned sure that WRITE operation was NOT POSSIBLE UNDER ANY CIRCUMSTANCES before beginning,
Then something was terribly wrong with the lack of adherence to proper protocols and
Procedures for data extraction from a CRASH UNIT memory module or tape unit.
Having said this, it is CLEAR beyond any reasonable doubt that the CPM module was written to by a bench unit, which ‘erased’ the header data that may have existed for the actual aircraft the unit was removed from. As you are well aware, the unit that this CPM came out of was most likely destroyed to the point where it might have been board level tested, but here again, the A/C ID and FLEET ID reside in NV RAM in that unit, and if the board itself with the chip intact had not been destroyed on impact, which I have reason to believe it was not, that data in NV RAM that is what initializes the CPM and puts the header data on the record in the very beginning of the file in a place that will not be written again but is on every power up, rechecked for CHECKSUM validity, was not part of the record we got from the N.T.S.B. because the data analysis does not stop with the CPM record, but includes, and I do mean, INCLUDES, the ERROR MAP FROM THE NV MEMORY in the FDR as well as this A/C ID and FLEET ID data. There is no record from the N.T.S.B. in their paperwork for this FDR that cites this, and that is a major red flag. Every component (as well as it’s SERIAL NUMBER) would have been also compared with the build list on file at L-3 for that particular unit. Yet, we don’t even have any report on the condition of the internal circuit boards which would be part of a comprehensive POST CRASH analysis for ANY FDR being examined for crash data. This is not only ridiculous, it’s indicative of a probable ‘cover up’ because of the lack of completeness in the forensic ‘autopsy’ if you will, of the subassemblies of that FDR after it was allegedly recovered ‘twice’ on two different occasions, at the Pentagon, once near the entry hole and also deep in the building under an INTACT PILOTS CREW SEAT. J
I went a bit long in the explanation but I wanted you to know that from what I can see, the data record in this FDR record is ALTERED due to this missing A/C ID, and the very peculiar and very suspicious bootstrapping sequences in this record that do not reflect TWIN ENGINE startups and generators going on line, are evident in this data record.
The engine start sequences are NOT decoded by the FDR decoding process post crash, but they tell as important of a story as the actual decoded HUFFMAN data in the file itself. For those who speculated in prior #ty commentary about my assertions, with the; “well then, why didn’t it show up in the NTSB recreation??” and the simple answer to that is that the N.T.S.B. recreations never show any analysis about the PRIOR FLIGHTS and the ENGINE STARTS seen in the bootstrapping going on in the data writes to the file as the recorder begins to record and reboot because of those.
Secondarily, the N.T.S.B.’s recreation doesn’t match the .CSV data released that was a derivative of the same memory file. How can this be? We know this is a fact because of the way the FL-180 descent reset is shown but not present in the .CSV file, and honest to dog here, there is no excuse for that disparity to exist. IF the N.T.S.B. truly did a faithful and honest recreation of the flight based solely on the DATA extracted, which the .CSV file would have revealed, then there would be absolutely NO DIFFERENCES between the two products. So which one is it? The N.T.S.B. got sloppy when doing the recreation and did NOT use the data derived from the decoded unit’s data, or was one of these two Records altered for some unknown reason. We know that the altimeter reset is the bone of contention in Pandora’s Black Box: FLT 77, and that’s not because we misread the .CSV file.
In any case, two things here: One, the WRITE ENABLE ( LT : jumper cable ) is not needed to dump the CPM memory file from ANY CRASH PROTECTED MEMORY MODULE, and clearly it had to have been in place to ERASE the A/C ID and FLEET ID data in the header.
These two fields are checked in the all up CHECKSUM during power up and would show on both E.I.C.A.S. CDU’s in the cockpit, a FDR FAIL if they were missing on any of the last flights of N644AA.
The government can make all the sorry excuses they want, and John Farmer can whine all he wants about ‘no header’ and **** like that, bug jesus ****** Christ, he has no ****** clue what he’s talking about with regard to FDR data, and he should stay the **** out of the argument if he has no idea clearly what he is stating. EVERY data file has a header,
Which in essence tells the system how to deal with the file. In the case of FDR’s, it is BIT CHECKED ON EVERY SINGLE POWER UP of the unit, and if the unit on N644AA had a malfunction in NV RAM that wiped that data, the box would have reported itself as INVALID and that means a ‘no pushback’ for damned sure.
The one thing most ***** in the J-REF forum don't realize is that WRITE ENABLE is never ever ever done on a CRASH memory extraction, ever.
And second, I wanted to clarify something here:
The main control circuit board with the processor and the NV RAM and hence the FIRMWARE the box had loaded into it, would have been analyzed and the A/C and FLEET ID data would have been extracted from that and presented to us in the final report.
It was not.
I saw no documentary evidence that reflected that the box was so destroyed that it pre-empted the removal of the MAIN PROCESSOR CARD and the NV RAM DATA and BIT ERROR MAP then checked to determine what the box state was on the LAST FLIGHT, as NV RAM would not be written to and erased regardless of the WRITE ENABLE to the CPM module data.
That box, if it is still intact, and the parts not destroyed by the government, STILL HAS within it, in that one circuit the A/C ID and the FLEET ID, and the BIT ERROR MAP.
Those are crucial pieces of evidence. And why they are not cited in the final report on that FDR is beyond me. The post mortem on the box would include matchups of serial numbers, and if board were destroyed, it's unlikely the chips on them would be so wrecked they couldn't be piggy backed and then read by a technician to get that data out.
So, I hope I answered your questions, Robert. Thanks for asking.”
As for AA 77's FDR: numbers which would qualify as serial numbers (Stutt didn't find aircraft ID in FDR data preambles from other flights either) were indeed found inside the FDR data and Legge mentions this on his website, addressing known ************** Rob Balsamo's complaints:
2. The data file is missing crucial information (aircraft ID) from the preamble.
If true, would it matter? Warren Stutt has files from a number of authentic flights, none of which contain the aircraft ID in the preamble. Apparently it does not matter. Furthermore Warren has now decoded some more columns of data and has found the plane ID. It is aircraft 35, fleet 1. This information has been passed to PFT. As some members of PFT work for American Airlines perhaps they will be able to check whether the ID in the file corresponds with AA77. They show no signs of being interested in this useful work.
Then, later as they got closer in, they did something puzzling for a crew of neophyte hijackers. On their way down through Flight Level 180, or 18 thousand feet, they magically, without having listened to the ATIS or automated terminal information service, broadcast from Dulles International Airport that morning, these guys somehow knew the barometric pressure reported on that automated broadcast though no controller passed that information to them, and they set that in the Kollsman window on BOTH of the cockpit altimeters, simultaneously. That’s not only clairvoyant, that’s SYNCHRONIZED knob twisting going on there, by any pilot’s
standards. Machine precision out of hijackers turning two knobs at the same time in perfect, instantaneous fashion, is extremely unlikely for these guys, yet that was exactly what took place when both the hijacker and his co-hijacker buddy, who must have gotten VERY lucky to pick those barometric pressure numbers for DCA that morning out of their asses, because they had no way of knowing them otherwise…as no radio in the cockpit was tuned to the ATIS frequency, as that is recorded in the FDR data and not reflected in the data the N.T.S.B. released from that plane’s Flight Data Recorder. Notwithstanding the absurdity of this kind of coordinated crew work, it really ranks as one of the most glaring issues of the morning because the crew could not have known those numbers they put into both altimeters via the Kollsman setting knobs that morning on their descent. They could NOT know them nor could they have so precisely guessed them.
Dennis : And then they did something quite unusual. They were able to penetrate that highly protected airspace without the proper MODE 4A military I.F.F. response, and no communications with ATC of any kind, no clearance issued of any kind, and they flew a nice leisurely 330 degree turn after passing right past the White House, the more desirable high value target, than their intended Pentagon target could ever dream to be. After they completed the turn, they managed to accelerate the aircraft well beyond 150 knots faster than it could ever possibly fly at that altitude, even full throttle.
They did this without touching the rudder pedals for even one moment after their hijacking of the plane several minutes earlier, too! Needless to say, to perform a coordinated turn as the N.T.S.B. flight data recorder data shows, they would have had to use rudder inputs, but they never touched the aircraft rudders once during their entire time in the cockpit after they slid under the crack below the cockpit door to gain entry. Was this because neither of them had legs? They walked onto the plane and did not require wheelchairs, so is it not a little strange or odd they never ever once touched the rudder pedals in that plane?
After careful analysis of the flight data recorder stuff provided to us by the N.T.S.B., in their
recreation, we see the fact the rudders and the yoke were not moved nor did the autopilot
disengage while the crew fought for their very lives in that cockpit. And, at no other time did
the rudders ever get so much as a passing foot kick. At the very least, these guys would have
probably inadvertently tested them a bit with their feet, yet they never touched them. And to do the nice 330 degree turn into the building, they would have absolutely NEEDED TO USE THE RUDDER to carry this out in what is called COORDINATED FLIGHT without slipping or skidding the plane in three dimensional space that morning. We know they flew a perfectly coordinated turn because the data the N.T.S.B. released to us shows us that. To do this, the rudders would have absolutely, beyond all reasonable doubt, been needed to accomplish this. No accomplished pilot could do that ‘flat footed’ with his or her feet not on the rudders. Impressive performance here, execution of coordinated high G turns without rudders used at all by the hijackers.
Dennis : the no disengage of the autopilot doesn’t work for me, as the crew would have kicked the rudders and the yokes and the autopilot would have disengaged during any STRUGGLE to take the plane over.
And for the rudders to be static and non moving for the rest of the flight, except for small deflections attributable to ‘air loads’ or deflection by the relative air movement against them, the rudders were for all practical purposes, ‘dead’ meaning the hijackers legs were not working, or both hijackers exercised EXTREME body control and kept their feet off of those pedals. And they executed a 330 degree COORDINATED turn without slipping or skidding the plane, at an impossible 465 knots airspeed, when an accelerated stall most assuredly would have been the likely result of such a course of action on their part. We know the rudders worked on the climb-out as Burlingame used them to compensate for thrust related yaw on takeoff, and that’s reflected in the FDR data record. After the hijackers took over, the rudders might just as well have been dead weights down there under their feet, because they simply were never again used. Why? Or more appropriately is ‘How?’ with regard to the total lack of rudders by the hijackers, while maintaining COORDINATED FLIGHT?????
Dennis Leahy 28th August 2012 14:01 : -snip-
However, since you're unable to take the time to back-up your assertions right now, and since Dennis Cimino (after spending 10,000 hours already) is ready to debate any specifics in that article and show that not only is his data solid but that he is competent to make the statements in the article, well, I'd recommend an unqualified public apology.
Bill Ryan :
3) Here is information I can contribute which I'm as sure as I can be is reliable.
a) In April 2010 I met and interviewed a young lady who, as a US Army medical trainee, ended up in the room where and when the decision was made to shoot down Flight 93. She witnessed the executive decision when it was made by conference call. The full account (including an interview with her in her own unaltered voice) is here. Elizabeth Nelson is not her real name.
What's interesting about this first-hand witness report is that the decision to shoot down the plane was made by senior military personnel who knew nothing of the 'inside job'. They were following military "by-the-book' protocol. Flight 93 was not responding to communications (the transponders had been turned off), and was entering restricted airspace.
The authorities could have come clean about the whole Flight 93 incident, but instead chose to invent the entire "Let's Roll" story -- which was a fabrication (see below).
b) The important Project Camelot witness, Henry Deacon (real name Arthur Neumann) who was a very gifted electronics engineer, and who Kerry Cassidy and I got to know personally over hundreds of hours of meetings and conversation, told us that he had worked personally on the guidance system for the two aircraft that were steered into the twin towers by remote control override. His account is here:
The control signals were relayed from a third aircraft that has become known by 9/11 researchers as "the white plane". There were software modifications that permitted the two target planes to make maneuvers beyond their regular flight characteristics. The planes were guided remotely from thousands of miles away. ('Henry' told us where the control center was, but we pledged not to reveal his workplace.)
Henry knew nothing about the 'hijackers', what happened at the Pentagon or Shanksville, what happened to the passengers, or any other logistics. As usual, everything was highly compartmentalized. He did confirm that no phone calls were made from any of the planes, and that all that theater was fabricated and dramatized.
The interesting part of Henry's experience (for me) was that at his place of work, everyone there was briefed several hours before the incident about what was going to be on the news later that day. They were told [my glib paraphrase]: "Don't worry -- this is just one of our projects."
Henry was appalled when he heard that, and realized for the first time what he'd been working on. Black projects engineers are always just told the design and functional specs for a device to be created, and never told what it would be used for. No need to know.
For the next several hours, he debated with himself whether to sabotage the operation. He was in a position to do that: he could have reprogrammed the software so that the planes would miss their targets. The price he would have paid was that his sabotage would certainly quickly have been identified -- after the event -- and he would have spent the rest of his life in military jail, or worse.
He chose to do nothing. He now lives with that. None of us in the free world are gifted to know from our experience what immense dilemmas and conflicts good people, working on the inside, are subjected to.
For Henry's background and for a transcript of our first interview, please click here.
A few months later, we published this update, which was a compilation of further information from ongoing communications we had received.
Both should ideally be read carefully before studying the further compilation which follows here.
Click here for an important new statement (December 2007)
Dennis Cimino (after spending 10,000 hours already) is ready to debate any specifics in that article and show that not only is his data solid but that he is competent to make the statements in the article
And since when does another country hold 'hearings' on a US event?