• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

AA77 FDR Data, Explained

Looks like Turbofan has run away from this this thread.

Surprise, surprise, surprise!
 
Runaway? Everytime I'm gone for a little while poor Wildcat thinks I'm
running away. In fact, I do have other things happening in my life besides
proving you all wrong.

I figured the last two articles of proof would be enough to convince everyone,
but it seems we're going in circles again.

Let me ask you all of this:

If certain sensors are polled every second, or multiple times per second
with a time stamp reference, how do you conclude the propagation from
sensor to CPM is greater than 500 ms?

You do realize 500 ms is worst case, and the write times can and most
often are lower....correct?

With all the proof linked up here, I'm amazed you're still trying to find a reason
to believe the data transfer is much slower!

Once again Anti (and others), how do you figure the system is designed to
move data slower than 500 mseconds when sensors are being polled at one
second, or multiple times per second?
 
I'll just quote this bit:

Turbo:
Let me ask you all of this:

which is followed by totally pointless questions. Read up if you can gather the energy to lift your head from the table in front of you after banging it to shreds. I'll refrain from saying what I really think but I think you can read between the lines.

What is more conspicuous is the total avoidance of this absolutely marvellous summary from Wildcat:

Flight 77 disappears from radar screens, and is replaced by either a "smaller plane" or a missile, above it which flys a Boeing E-4B. Making impossibly tight turns at high speed no other airplane is capable of, the "smaller plane" or missile strikes the Pentagon, while the E4B flys over the Pentagon. Teams of conspirators immediately swoop down on the scene, tearing light poles out of the ground, sticking one in Lloyd England's cab. Other conspirators tear up tree branches, knock over construction equipment and material, fences, and marking poles where they figure Flight 77 would hit if it had actually taken the flight path they programmed into the FDR, which the crack team of conspirators also planted in the Pentagon. Other teams of conspirators spread airplane parts all over the lawn of the Pentagon, inside the Pentagon, and in the alley beyond the C-Ring. They blow a hole in the C-Ring with a wall breaching kit for good measure. At the same time, other conspirators go inside the burning Pentagon and plant the remains of the Flight 77 passengers and crew, which have been ground into hamburger a short time earlier when Flight 77 was diverted to some other airport where everyone on board was killed.

All of this was done in broad daylight in front of hundreds of witnesses - from people on their way to work, to Pentagon employees, to firemen, paramedics, and policemen arriving on the scene. And nobody notices!

But there was one problem - one of the doofuses at the NWO accidentally programmed the flight path of the decoy plane into the planted FDR instead of the fllight path they would officially claim for Flight 77. The NTSB ignores these discrepancies, because they are also in on the conspiracy.


Speaking only for myself, I don't give a toss what bollocks Turbo comes out with about FDR data analysed by the brain-dead until he addresses the above rather large stumbling blocks to his excuse for a theory. Jesus. even writing the word 'theory' when I respond to him ...I won't say.

Just answer it, Turbo.

And try not to reply with questions, because your questions are crap.

Just answer the plainly laid out scenario you've given us, which makes us all laugh at you.

Bananaman.
 
Last edited:
Runaway? Everytime I'm gone for a little while poor Wildcat thinks I'm
running away.
Sure you did! I notice you still haven't responded to my narrative post, not the other posts that show beyond a shadow of a doubt you don't understand how data gets from the sensors to the memory of the FDR.

In fact, I do have other things happening in my life besides
proving you all wrong.
Like starting your Fyziks 101 thread? Which proved, no surprise, you know as much about physics as you do about FDRs.

If certain sensors are polled every second, or multiple times per second
with a time stamp reference, how do you conclude the propagation from
sensor to CPM is greater than 500 ms?

You do realize 500 ms is worst case, and the write times can and most
often are lower....correct?

With all the proof linked up here, I'm amazed you're still trying to find a reason
to believe the data transfer is much slower!
The only thing amazing is there is not a single actual FDR expert on the entire planet who agrees with you, yet in your astounding arrogance and conceit you think they're all wrong, and you and the hacks from PfffT are correct.
 
Last edited:
I figured the last two articles of proof would be enough to convince everyone,
but it seems we're going in circles again.

Yes, you've further proven you are incapable of reading of they are telling you.

If certain sensors are polled every second, or multiple times per second
with a time stamp reference, how do you conclude the propagation from
sensor to CPM is greater than 500 ms?
Because the thing that is "polling" the sensors (the sensors are not "polled" at all, so this is just wrong) is not the same as the thing that is storing them. There is an intermediary called the DFDAU. His effect on the system is great and you have completely ignored his existence.

You do realize 500 ms is worst case, and the write times can and most
often are lower....correct?
Not from the sensor, it isn't. MAYBE from DFDAU it is.

With all the proof linked up here, I'm amazed you're still trying to find a reason
to believe the data transfer is much slower!
Please stop using the term "data transfer" because it belies a fundamental ignorance. Data isn't "transfered" from the sensor into the CPM. It is "transfered" to the DFDAU where it is buffered. It then waits for entry into a time-multiplexed bitstream. It then is "transfered" to the FDR. It is then compressed. It is then stored.

Each step above takes time and you have, at different times, taken different numbers for EACH of those and pretended it equals the entire thing.

Once again Anti (and others), how do you figure the system is designed to
move data slower than 500 mseconds when sensors are being polled at one
second, or multiple times per second?
Because "the system" doesn't poll anything multiple times per second. Certain elements in the system have different requirements and some of them do happen at regular intervals (like the DFDAU's sampling of it's digital buffer, for example. This is one part of the system you've ignorantly equated with the entire thing). The "system" is the sum of these requirements. I have already provided you the equation for this sum. All you've done is point to requirements of individual pieces of the system and then falsely claimed it applies to the whole system.

As it's clear from your pathetic attempts at "proof" that you do not understand the components of an FDR system. Maybe you need to look at that picture some more. My annotations are in red.


I also notice you've completely ignored my specific questions to you about whether you have the gall, seeing this picture, to STILL claim that the ARINC429 standard applies to the ENTIRE sensor to CPM system?
 
Last edited:
Still no word from L3 eh Turbo? Gosh if I was using experts, the first thing I would use it their endorsement. Otherwise ya know my car is certified for something like 30mpg but that sure never happens.
 
Because the thing that is "polling" the sensors (the sensors are not "polled" at all, so this is just wrong) is not the same as the thing that is storing them. There is an intermediary called the DFDAU. His effect on the system is great and you have completely ignored his existence.

No I have not, and I'm fully aware of the Data Acq. Unit. Maybe if you spent
more time on PFT, you would see that.

I'm also fully aware that the sensor is not plugged directly into the FDR,
and that some sort of analog to digital conversion occurs. :rolleyes:


Not from the sensor, it isn't. MAYBE from DFDAU it is.

Right...so the RAD ALT updates that occur every second are transposed
in time after the signal is processed through the DAU?

Does the DAU magically lengthen the time of the polling and then store
the data in the FDR's crash protected memory with the time stamps reading
RAD ALT at one second intervals? :boggled:

Do you even know what you're trying to spin here?

Please stop using the term "data transfer" because it belies a fundamental ignorance. Data isn't "transfered" from the sensor into the CPM. It is "transfered" to the DFDAU where it is buffered. It then waits for entry into a time-multiplexed bitstream. It then is "transfered" to the FDR. It is then compressed. It is then stored.

Gee, I didn't know I had to get so specific and mention the sensor, the wire,
the interface, the A/D conversion, the DAU, the cables between all of those
devices to the FDR...

Once again, spend more time looking at the overall picture instead of getting
too detailed for your own level of experience.

Afterall, you are the so called expert who posts the function of the system,
but doesn't know the t1-t5 timing? :rolleyes:

Still no answer to how the system is designed to read/write slower than
500 msec. when sensors are polled many times per second.

I also notice you've completely ignored my specific questions to you about whether you have the gall, seeing this picture, to STILL claim that the ARINC429 standard applies to the ENTIRE sensor to CPM system?
[/B]

I'll pick that apart later and show you how it works. I'm too busy right now
to draw stuff up. Maybe tomorrow night. Hang in there!

In the mean time, keep trying to figure out how this system is designed
with turtle -quick processing for these massively slow intruments in the cockpit
that read in 'near' real time.

I guess you too forgot it shares the same data bus, and power bus?
 
Last edited:
And still no word from L3 Turbo. Gosh, one might accidentally be lead to believe that all you did was read some specs form the web site on how things are meant to operate and without any kind of context. Gosh, I wonder what your mystery expert at L3 would have to say about that....
 
Maybe if you spent
more time on PFT, you would see that.

You're an
Edited by tim: 
Please remain civil.
I don't know how else to put it. Yep, pretty much got it right. You're an
Edited by tim: 
Please remain civil.
.

Gee, I didn't know I had to get so specific and mention the sensor, the wire,
the interface, the A/D conversion, the DAU, the cables between all of those
devices to the FDR...

There are so many things you don't know it's sad.

Edited by tim: 
Please remain civil.
Once again, spend more time looking at the overall picture instead of getting
too detailed for your own level of experience.

Er......where does one begin? You have the sheer nerve to talk about overall pictures. Which planet have you just been dropped off from?

You're an
Edited by tim: 
Please remain civil.
Turbo. Sorry, mods, but sometimes words are designed to be used accurately. Turbo is an
Edited by tim: 
Please remain civil.

Bananaman.

Name calling does not further your point of view. Please desist.
Replying to this modbox in thread will be off topic  Posted By: tim
 
Last edited by a moderator:
Mendacity
Googling up irrelevancy
to defend absurdity.

Turbofan really reminds me of LastChild
 
How about that narrative I popsted Turbofan? Feel free to post any corrections if needed, but your silence says it's pretty accurate, yes?
 
Turbofan is indeed running away.

Runaway? Everytime I'm gone for a little while poor Wildcat thinks I'm running away.

Well, it's certainly true. You have yet to provide any of the evidence I've asked for and you continue to defend CIT for refusing to provide key evidence at the Pentagon?

So, Turbofan, when are you going to STOP running away from the evidence?
 
How about that narrative I popsted Turbofan? Feel free to post any corrections if needed, but your silence says it's pretty accurate, yes?

This narrative,Turbo.

Actually, I'd like you to flesh out a bit more what you think happened at the Pentagon. Here's what we have so far, based on your posts:

Flight 77 disappears from radar screens, and is replaced by either a "smaller plane" or a missile, above it which flys a Boeing E-4B. Making impossibly tight turns at high speed no other airplane is capable of, the "smaller plane" or missile strikes the Pentagon, while the E4B flys over the Pentagon. Teams of conspirators immediately swoop down on the scene, tearing light poles out of the ground, sticking one in Lloyd England's cab. Other conspirators tear up tree branches, knock over construction equipment and material, fences, and marking poles where they figure Flight 77 would hit if it had actually taken the flight path they programmed into the FDR, which the crack team of conspirators also planted in the Pentagon. Other teams of conspirators spread airplane parts all over the lawn of the Pentagon, inside the Pentagon, and in the alley beyond the C-Ring. They blow a hole in the C-Ring with a wall breaching kit for good measure. At the same time, other conspirators go inside the burning Pentagon and plant the remains of the Flight 77 passengers and crew, which have been ground into hamburger a short time earlier when Flight 77 was diverted to some other airport where everyone on board was killed.

All of this was done in broad daylight in front of hundreds of witnesses - from people on their way to work, to Pentagon employees, to firemen, paramedics, and policemen arriving on the scene. And nobody notices!

But there was one problem - one of the doofuses at the NWO accidentally programmed the flight path of the decoy plane into the planted FDR instead of the fllight path they would officially claim for Flight 77. The NTSB ignores these discrepancies, because they are also in on the conspiracy.

Everything is going smoothly until the crack team of FDR experts and researchers at the PfffT files a FOIA request and the NTSB turns over the incorrect data. Now they have blown the whole scheme wide open!

Is this an accurate summary of what you believe happened Turbofan?

Yes or no ?
 
No I have not, and I'm fully aware of the Data Acq. Unit.

Yes, you can SAY that, but every time it comes for you to include it's effect in your calculations, it seems to go missing.

Does the DAU magically lengthen the time of the polling and then store
the data in the FDR's crash protected memory with the time stamps reading
RAD ALT at one second intervals?
I've explained no less then 15 times exactly how the DFDAU works and how time multiplexing works. Your inability to understand either is no longer my problem.

Afterall, you are the so called expert who posts the function of the system,
but doesn't know the t1-t5 timing?
Is this your pathetic attempt at turning my questions around on me because you can't answer them? You are the one making claim s. If you can't back them up, you lose.

Still no answer to how the system is designed to read/write slower than
500 msec. when sensors are polled many times per second.
Wow, look, there you go FORGETTING about the DFDAU again. Shocking. Your statement, by the way, is false. The "system" is not designed to do anything in 500ms. Certain parts of the system are designed to do certain things in 500ms, yes. When you ADD UP all the times of all the different parts, you get much more then 500ms. I've already showed you the equation. STILL WAITING for you add up those times.

What's really ****ing truly amazing is I gave you the exact equation about 15 pages ago. I've drawn you picture. And yet you are still completely and utterly incapable of making a list of the 5 times and give an estimate for each of them. If you actually knew what you were talking about, and could actually understand the data sheets (and tutorials, ha ha) that you were reading, you'd have done that 10 pages ago.
 
Last edited:
What's really ****ing truly amazing is I gave you the exact equation about 15 pages ago. I've drawn you picture. And yet you are still completely and utterly incapable of making a list of the 5 times and give an estimate for each of them. If you actually knew what you were talking about, and could actually understand the data sheets (and tutorials, ha ha) that you were reading, you'd have done that 10 pages ago.

Anti: As much as I, and others appreciate your input, these tripe swilling vagabonds have no clue. Read their prose.
Pilotsfor911truth.org does not make the claim that "No Boeing 757 hit the
Pentagon", we just beat around the same bush. We have analyzed the Flight Data Recorder data provided by the
NTSB, while not understanding any of it, as shown in our pathetic "analysis" of that data. We do not offer theory, but I bet you know what we're implying!

Again: Anti. Thank you!
 
No I have not, and I'm fully aware of the Data Acq. Unit. <snip>
I'll pick that apart later and show you how it works. I'm too busy right now
to draw stuff up. ?

Perhaps you missed this?
This is amazing. You pretending to teach me how these systems work by showing me marketing versions of tech sheets and tutorials for systems I used to spec out, buy, build, and test. I've never met a truther so completely ignorant and so completely arrogant in my life.

Or not!
 

Back
Top Bottom