Merged Discussion of femr's video data analysis

I wouldn't use the word assumption since it was a conclusion based on modelled behaviour.
Sooo... what other lateral trajectories did NIST simulate for WTC2 ? :D

Deflection behaviour of a complete engine assembly doing over 500mph is going to be different to an engine fragment doing 100mph
Sure, though the difference is "how much", not "nil vs not nil".

Bear in mind also that estimated velocity POST exit was around the 120mph mark, implying velocity a fair bit higher than the prior to exit.

Your values appear to be "influenced" by a desire to "favour" NISTs poor decisions.

To say that if an engine part could deflect on exit it must be able to deflect similarly on entry is faulty reasoning.
Who said similarly, with your inference ?

As Femr2 shows in the simulation in post #3235 the engine shows little initial deflection from the walls and floor until it has lost enough momentum to enable it to be deflected by the floor.
Say wha' ?

That diagram shows >20 degree vertical angle change within 0.05s
 
How many more times should either you or I point to the flawed reasoning underpinning that 13o figure? And have it ignored/missed/not understood? My patience shorter than yours......
It should be necessary only once...with the result being immediate affirmation from all participants that (unconfirmed) engine exit point does not validate the NIST trajectory at all and is also damaging to the validity of that trajectory.

The trajectory should be based on...the trajectory, measured as accurately as possible, not selected based upon faulty real world observation.

we have some basis for progress.
I'm sure the "exit hole strategy" will fade in time, to be replaced with some other objection.
 
Femr2, a few years back you had a very good animated GIF of the WTC2 impact and resulting fuel ignition from the same viewpoint as the linked images below:

http://femr2.ucoz.com/_ph/2/2/542891169.jpg

http://femr2.ucoz.com/_ph/2/2/70212609.jpg

http://femr2.ucoz.com/_ph/2/2/308882580.jpg


I can't find it on your website. It could help show the timing between impact and explosion and give a practical sense of aircraft velocity relative to fuel ignition timing. Do you have a link to that GIF?
Shall have a look.

The Scott Myers footage doesn't show the exit location, so I'm not sure how useful it would be.

Perhaps...
682848596.gif
 
I wouldn't use the word assumption since it was a conclusion based on modelled behaviour.
Sure - I'm not fussed about terminology on this matter. If we want to be pedantic it was an interim conclusion adopted as a premise on which NIST's conclusion of 13o is based.

However, terminological niceties aside, the key point is "if the straight line assumption is wrong then NIST's work based on that assumption is wrong".

Now thanks for your second point which goes to the reasoning of my explanation:
...It shows that your reasoning is wrong. Deflection behaviour of a complete engine assembly doing over 500mph is going to be different to an engine fragment doing 100mph. To say that if an engine part could deflect on exit it must be able to deflect similarly on entry is faulty reasoning...
There are two aspects why I disagree with your claim that my "reasoning is wrong". One is technical the other is the requirements for standard of proof/burden of proof. Set the proof issues aside at this stage - let's look at the technical.

My argument essentially rests on a premise that impact at entry and exit walls would follow similar mechanisms. You dispute this premise with "Deflection behaviour of a complete engine assembly doing over 500mph is going to be different to an engine fragment doing 100mph." (My emphasis.)

That statement is true BUT it depends on what you mean by "different". The results will be quantitatively different but not qualitatively different. The mechanisms of physics will be the same mechanisms. Despite all the detailed differences other than velocity the actual mechanisms for deflection will be the same.. Take any aspect you choose - lets say impact of a moving body on an inclined plane - deflection will still occur conforming to the same equations of motion. Qualitatively the same. The difference will be in the magnitude of the effects. Quantitatively different. If there is deflection at low speed the same mechanism acting at high speed may well cause less deflection for whatever reason of the maths BUT it will not be zero.

Your reasoning presumes that faster impacts will have zero deflection whilst slower impacts will have some deflection. So "zero" at high speed, "some" at low speed. That is not how the physics works. You could well be correct that it will be "more at low speed" BUT it will be "less at high speed" not "zero" And my reasoning only requires "some" whether it be more or less.

So, without attempting to identify every component of the impact interactions, some may be more at high speed, some may be less. The ones that are less may be very small BUT still not zero. And my argument only requires "not zero".

So that is the technical overview - the logical requirements for "proof" are more complex so I'll leave them for now.

And:
...As Femr2 shows in the simulation in post #3235 the engine shows little initial deflection from the walls and floor until it has lost enough momentum to enable it to be deflected by the floor.
That may well be true but it is not part of the reasoning I used and you are disputing.
 
Last edited:
It should be necessary only once...with the result being immediate affirmation from all participants that (unconfirmed) engine exit point does not validate the NIST trajectory at all and is also damaging to the validity of that trajectory.
We (you and I) are agreed on all three of those points...but....
....The trajectory should be based on...the trajectory, measured as accurately as possible, not selected based upon faulty real world observation...
Yup. you are preaching to the Choir...Bass section...it was the tenors who were flat....and the congregation may be listening. ;)
...I'm sure the "exit hole strategy" will fade in time...
I lack your patience so I chose euthanasia rather than palliative care.....:o

Certainly if we throw out the bits where NIST is wrong we may get a clearer playing field to discuss "femr's video data analysis". The question of your accuracy stands alone - your analyses are either accurate enough or not accurate enough independent of comparisons with NIST.
...to be replaced with some other objection.
That will depend on the weather - some combination of (concurrent) blue sky and foggy conditions I expect. :)
 
Last edited:
Don't bother. The one you just posted is better.
No worries.

This view from the Scott Myers footage may be useful for those under the belief that the aircraft orientation and trajectory were not coincident for all practical purposes...

694705985.gif
 
The first fact explicitly stated is that NIST based its work on the assumption of a "relatively straight path of the engine through the building" - true or not true Mark?

Not true, unless one chooses to ignore most of NIST's work. But why would one do that? I think it's silly.
 
Not true, unless one chooses to ignore most of NIST's work. But why would one do that? I think it's silly.

Same question to you that I asked Reactor Drone earlier...

What other lateral trajectories did NIST simulate for WTC2 ?

Lateral trajectory was a parameter NIST specifically did not vary.

The engine did not reach the NE corner in any simulation.

In the real world the engine, after smashing through the other side of the building, still had sufficient velocity to travel another 1400ft or so, estimated to be about 120mph.

In the real world the engine WILL have deen deflected within the building. Exactly how much and when cannot be determined, though imo ... many deflections during its journey from entry to exit.

What part of that "work" do you want to retain ?

Or, what "work" are you referring to ?
 
No worries.

This view from the Scott Myers footage may be useful for those under the belief that the aircraft orientation and trajectory were not coincident for all practical purposes...

694705985.gif

I can clearly see the path the wing tips trace is not the same direction the fuselage is pointed.

Screenshot2013-04-30at115138PM.png
 
Last edited:
I can clearly see the path the wing tips trace is not the same direction the fuselage is pointed.
An image to assist in accurate path placement...

490004667.png


The aircraft is banking.

The pertinent features are the nose and tail of the fuselage.

I'll post an image later showing the nose and tail paths.

http://i995.photobucket.com/albums/af74/waypastvne/Screenshot2013-04-30at115138PM.png[/qimg][/QUOTE]
Creating such an image without showing at least two images with multiple features indicated is pretty pointless.

The angle of your line is not particularly accurate, but that doesn't matter, as the trajectory of the aircraft does not depend upon your observed "path difference". Again, the aircraft is banking.


Welcome to the thread. I suggest thinking things through a little more before posting.
 
An image to assist in accurate path placement...



The aircraft is banking.

Again, the aircraft is banking.

I suggest thinking things through a little more before posting.

Did you notice I said wing tips.... plural...both wing tips track the same line.

No discernible roll in your gif.

The aircraft is not traveling the same direction it is pointed

Your new art work does indeed show the path the plane traveled. Now you need to lay the image of the plane over it and see if it's pointed the same direction.
 
Did you notice I said wing tips.... plural...
I did indeed, and also pointed out to you:

a) The aircraft is banking
b) Drawing a single line on a single image is rather pointless

both wing tips track the same line.
No, they do not.

Left wing path is roughly 1 degree greater than fuselage path.

Right wing path is roughly 1 degree lower than fuselage path.

Your new art work does indeed show the path the plane traveled.
It does not reveal the nose and tail paths clearly, which is why I said I'd post another image.

I created it so you had accurate information with which to look at wingtip behaviour.

Now you need to lay the image of the plane over it and see if it's pointed the same direction.
That's one way, sure. If you give it a whirl, please do so accurately.
 
I'll post an image later showing the nose and tail paths.

582171242.gif


Not a bad view at all. I suggest significant zooming...

You can see the reaction of the aircraft to impact.

Fuselage trajectory is coincident with orientation until impact, which causes a slight shift.
 
Last edited:
No, they do not.

Left wing path is roughly 1 degree greater than fuselage path.

Right wing path is roughly 1 degree lower than fuselage path.

I extended the path of the wingtip out 12"... accurately.

I extended the path of the bright highlight out 12"...accurately.

I measured the distance at one end ....accurately.

I measured the distance at the other end ...accurately.

I found no difference in the two accurate measurements.

Therefore it would be accurate to say that your 1 deg is not very accurate. If it was, I should be seeing about .21" of difference in the measurement
 
accurately
One of my favorite words :)

Therefore it would be accurate to say that your 1 deg is not very accurate.
You'd be right. Rounded off.

You want increased accuracy, fine...

NONE of the paths are exactly linear.

Both wingtips and the mid fuselage highlight experience a slight shift in direction upon impact of the nose.

There's always going to be difference of opinion on these angles given the lowish resolution.


The point being that such differences between fuselage and wingtips have nowt to do with fuselage trajectory in this context...and there is bound to be an effect from the impact reaction the animation reveals (for the first time ;) of about half a degree)

If it was, I should be seeing about .21" of difference in the measurement
See previous image.


Sooo...for others...

Thetrajectory follows orientation UNTIL contact between aircraft and building, which initiates a slight rotation (about half a degree by the time the aircraft is hidden) which would appear to be arounf the aircraft COG...so the tail does enter at the same location as the nose, but the aircraft has "twisted" a little.

Not a great surprise, but interesting to be able to see the reaction of the aircraft to impact.
 
Last edited:
Not true, unless one chooses to ignore most of NIST's work. But why would one do that? I think it's silly.
Mark I am trying to engage in reasoned discussion but I am finding that each of your successive posts gets more evasive and further out of context.

Taking your claims in series:
Not true,
You are responding to my statement (and Reactor drone's) that NIST adopted the 13o impact angle based on back tracing the engine path through the building and assuming that the transit through the building was (close enough) to linear. I find your denial of that fact astonishing. Despite femr2 and I disputing the validity of the NIST assumption over many months you are IIRC the first person to deny that it was the NIST assumption.
...unless one chooses to ignore most of NIST's work...
The issue under discussion was that portion of NIST's work that was IMO based on the assumption of a near enough to linear engine transit path. The remainder of NIST's work cannot change the issue of fact - Did NIST assume linear transit path? Your implicit claim that the answer is "No" will not stand scrutiny.
But why would one do that?...
(Where "that" is ignore NIST's other work.) Because we are not discussing NIST's other work. We are - or at least I am - attempting to construct focussed reasoned and legitimate explanations for a process of physical analysis. My specific focus through the series of posts being my claim that the NIST assumption of a linear transit path is not valid. If you are contending that:
a) NIST did not assume a linear transit path for the relevant part of NIST's work; OR
b) That somehow other apparently unrelated aspects of NISTs work changed the assumption of linear then please post the evidence and reasoning.
I think it's silly.
I think it is demonstrating the clarity of focus needed when selecting elements of factual evidence needed to support an argument and in the construction of such a reasoned argument utilising the evidentiary facts.
 
Same question to you that I asked Reactor Drone earlier...

What other lateral trajectories did NIST simulate for WTC2 ?

What on earth do any of NIST's simulations have to do with your analysis?

You're disputing NIST's video estimates; you're asserting that their entire range of lateral trajectories is wrong, regardless of what they considered most likely within that range.

Granted, this whole topic arguably is a derail from focusing on your WTC 7 analysis. Why not a derail from the derail?
 
Mark I am trying to engage in reasoned discussion but I am finding that each of your successive posts gets more evasive and further out of context.

My posts aren't moving, but the failure to communicate apparently is becoming more entrenched.

Taking your claims in series:
You are responding to my statement (and Reactor drone's) that NIST adopted the 13o impact angle based on back tracing the engine path through the building and assuming that the transit through the building was (close enough) to linear. I find your denial of that fact astonishing. Despite femr2 and I disputing the validity of the NIST assumption over many months you are IIRC the first person to deny that it was the NIST assumption.

I don't think it is possible to reconcile that representation with my posts -- which is perhaps part of why you construe them as becoming more evasive.

As the record shows, I was responding to your statement that "NIST based its work" on a particular assumption. What work are we discussing?

My point really is not so hard to understand. We have been discussing NIST's analysis of aircraft trajectory and orientation in comparison with femr2's. As I have pointed out several times, NIST defines ranges of estimates, then refines those ranges of estimates, then at the end chooses a point estimate as a basis for later simulations.

In femr2's view, NIST goes off the rails at the beginning of that process, laboring mightily to produce a range for trajectory that, although rather wide, nonetheless doesn't include the correct value.

A cursory glance at chapter 7 confirms that the specific choice of 13 degrees is a very small part of NIST's analysis of aircraft trajectory and orientation. At that point in the analysis, there is no choice NIST could have made -- at least no choice of point estimate! -- that femr2 would have agreed with.
 
What on earth do any of NIST's simulations have to do with your analysis?
I've mentioned implications of the NIST errors several times. Did you miss them ?

Continnued insistence from some members that the NIST values are correct, and femr2 is wrong... keeps NIST "on the slab".

You're disputing NIST's video estimates; you're asserting that their entire range of lateral trajectories is wrong, regardless of what they considered most likely within that range.
Correct. Build an extremely intricate model, then slam the aircraft model into the tower model in the wrong direction. Doh ! :rolleyes:
 
Last edited:

ISF - Join now!

Every member here is approved by hand. No bots, no spam, just people who care about evidence and honest debate.

Membership is free!

Create your free account

Back
Top Bottom