It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by R_MackeyNote that the Comparator_Fail_FO have empty cells yet the others are recording a digit. The empty cells are due to perhaps a broken line between the sensor and the FDAU.
Originally posted by 911files
Originally posted by turbofan
My view on 9/11 remains the same as I am interested in well researched,
well documented evidence in order to remain honest in my studies.
[edit on 3-12-2009 by turbofan]
Found a 1 in that 42 hours worth of data yet?
Originally posted by turbofan
No, have you found any origin for that white smoke, or associated parameters in the FDR to prove light pole strikes?
Word 251 Assignments
Subframe
Bit # 1 2 3 4
1 Aft Cargo Door #1 Aft Cargo Door #2 Flight Deck Door Main Cargo Door
2 Aft Cargo Door Elect Access Door Fwd Cargo Door Fwd Access Door
3 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
4 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
5 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
6 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
7 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
8 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
9 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
10 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
11 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
12 Ind AOA Deg Ind AOA Deg Ind AOA Deg Ind AOA Deg
Originally posted by turbofan
I am no longer supporting the latest P4T claim as there is insufficient documentation to make a conclusive statement.
This does not mean that my view on previous FDR research changes;
simply the connection to FLT_DECK_DOOR cannot be confirmed at this
time.
When the proper manuals come available, I will reassess PilotforTruth's
position and post accordingly.
My view on 9/11 remains the same as I am interested in well researched,
well documented evidence in order to remain honest in my studies.
[edit on 3-12-2009 by turbofan]
It appears Tino Desideri/Turbofan has switch sides due to this latest article and is now bashing us (me personally) on ATS.
Here is an email sent to Tino regarding this fiasco if anyone has any questions.
Keep in mind, Tino attempted to delete his posts here. We dont delete posts. So he has been placed into the Guest category until he can perhaps cool down a bit. But instead it appears he wishes to make it worse on ATS.
Aircraft Accident Investigators have to perform guess work on all the attached parameters to determine whether the parameter was hooked up to record, or if it was showing its true state, according to your theory.
As for your posts that you now want deleted from our forum, are you telling me you didnt know the day you read my article that a zero can also mean a "place holder" as you now claim?
Are you also saying we should ignore this data and not hold the NTSB responsible for providing it showing a cockpit door indication closed?
Tino, we never claimed to have proof, nor have we claimed to have the data "confirmed". You claimed that, now you look like a fool so you're trying to save face.
The data conflicts with the govt story. We want to know why. You seem to want to make excuses for it.
(again, dont bother replying as you been blocked)
Originally posted by turbofan
reply to post by 767doctor
Thank you Jay,
It was pretty much a no brainer once I found out this press release was
based on a poor understanding of how the flight data is recorded, as well
as not having the proper manual to prove whether a connection was
made between the cockpit door and the FDAU (possibly via EICAS).
If you read the top of the page, it's clear he has no clue about how the
bit values are stored and how they make their way into an Excel spreadsheet.
This latest development does not mean that I am taking a new side on
the events of 9.11.01; it simply means I will not put my name behind
erroneous claims. I will back up all previous research done by P4T,
but I cannot tolerate the leader of a pilot organization issuing a press
release based on a gut feeling...and a bad one at that.
After many attempts of trying to explain why Mr. Balsamo was wrong,
he simply didn't wish to learn and cut me from the forum and blocked
my e-mails. He will not remove my posts which are associated to the
latest theory so therefore I must make it clear that I want no part of
an organization that chooses to make claims without providing their
members and the general public with proof.
There are far more valid anomalies with the FDR/Official story to worry
about in my opinion. Let's see if we can discuss them in a more civil
manner from this day forward (I can't see that lasting too long however! )
[edit on 3-12-2009 by turbofan]
And just as a reminder... (this was sent to Tino as well, several times, but he chose to ignore it)
....we have verified Warrens data for the last flight only, the alleged hijacking on Sept 11, it shows the door closed.
And if logic has any value, this would be the bit value recorded if the FLIGHT DECK DOOR parameter wasn't hooked up to the system so when a tech reviews the data, he can readily admit its not valid.
Originally posted by turbofan
YOu wanna talk RAD ALT., PA, DME, etc. FINE. That's a valid
arguement. FLT_DECK_DOOR is not!
Originally posted by 911files
Originally posted by turbofan
YOu wanna talk RAD ALT., PA, DME, etc. FINE. That's a valid
arguement. FLT_DECK_DOOR is not!
Actually, you can scratch DME off the list. For some reason, the P4T has different positional data than the Warren RO. Once the Warren RO is aligned with the radar and proper time, the DME values match accordingly.
Hi Rob,
Both the data frame layouts I received from the NTSB state that for both the COMPAR ENABLE F/O and COMPAR ENABLE CAPT parameters that 0 = ENABLE and 1 = DISABLE.
Since COMPAR_ENABLE_F_O is 1 (DISABLE) and COMPAR_ENABLE__CAPT is 0 (ENABLE), this could explain why COMPARATOR_FAIL_F_O is blank and COMPARATOR_FAIL_CAPT is not blank, respectively.
Both data frame layouts state that for the COMPARATOR FAIL CAPT parameter that 0 = NOT and 1 = FAIL. COMPARATOR_FAIL_CAPT is 1 (FAIL) as you said.
There are other columns in ReadOut2 that are blank however.
The columns in Readout2 that are blank are FTP, PRM, PPP, TIME, PATH, MENU, MYIP, DFDR, REMIP, UPLOAD, UPDFTP, OPTION, PROMPT, PPPNUM, QARFTP, PEERMRU, UPL_SRC, NETMASK, FTPPASS, STATION, PPPPASS, VERSION, PPPSNUM, PPPUSER, PPPDNUM, MACADDR, COMSPEC, MDM_INT, FTPUSER, FTPRADDR, FTPRUSER, FTPSADDR, FTPSPASS, MDM_PORT, MDM_RATE, FTPQUSER, FTPSUSER, RSYNCSRC, PPPSUSER, PPPSPASS, FTPQPASS, FTPQADDR, FTPRPASS, PPPDUSER, PPPDPASS, APiasmode, ReviewedBy, ALTradsign, CursorStart, InterpretedBy, CON_MODE_OPER, InvoiceNumber, IncidentDetails, SoftwareVersion, ACMS_S_W_P_N_CODE, COMPARATOR_FAIL_F_O, A_P_T_E__FLAP_POSITION_2 and ACType.
My program already decodes ACMS S/W P/N CODE, I don't know why it would be blank in ReadOut2.
Warren.
ETA: I hope this answer's Jefferson's questions as well.
Originally posted by turbofan
I look like a fool because YOU sent out a public statement saying the
hijack was impossible...but now YOU cannot prove it?