Merged Discussion of femr's video data analysis

... , because femr2's curves of unknown provenance and poor accuracy are inadequate to support his claim.

Wish there was some supporting documentation in support of the "filter". I can't believe super filter guys don't know who Maybeck is; the filter guy, can't explain the filter. Google U, 100 percent graduation rates.

Lack of progress, stuck on a minor point. I suspect not setting goals, a contributing factor.

Funny, MT googled up some SG papers. Have a great weekend.
 
I only ask about the orientation because the layout in your draft only really matches if the WTC buildings are 31° off north and then it matches very well with all buildings and observer locations matching. Obviously, if that is the orientaion in the final 3d environment it would effectively add 4° to any aircraft orientation with respect to the buildings which were, of course, 27° off north. This would put your figure much closer to the lower bounds of the NIST baseline orientation.

Not claiming to know anything about this topic, I note that NCSTAR 1, p. 38, fn. 7 to chapter 3, states, "Plan North was approximately 29 degrees clockwise from True North." NCSTAR 1-2B, p. 161, similarly states that "Structure north is approximately 29° clockwise from True North." ?

Also, can you clarify what is being matched with what?
 
Aircraft orientation with respect to the direction of travel is relevant.
Of course. Sideslip is not a term I was familiar with.

Misinterpreted the definition :)

Modify as you please, though I would point out that careful inspection of the video record reveals no motion deviating from orientation during impact (NIST trajectory errors are a separate study). It's not going to make a huge difference. But please stop using your inappropriate viewing method. There are plenty 3D modeling packages available if you don't want to shell out for the likes of 3DSMax.
 
Last edited:
Aircraft orientation with respect to the direction of travel is relevant. If the aircraft was approaching the WTC at 13° but was yawed 13° to the left(i.e sideslipping to the right) it would appear to be 90° to the surface at the point of impact.

Therefore if you're trying to visually match the aircraft it needs to be oriented where it's pointing rather than where it's going.
I'm a bit confused by this argument (in it entirety). Predicting what happened in the building by using a still of the plane just before impact is actually a little silly. The plane is not traveling in the direction it's pointing (I'm sure Beechnut will agree here). :confused:
 
I'm a bit confused by this argument (in it entirety). Predicting what happened in the building by using a still of the plane just before impact is actually a little silly. The plane is not traveling in the direction it's pointing (I'm sure Beechnut will agree here). :confused:
Obviously this static analysis can only identify issues with the NIST orientation, not the trajectory, though of course it is an important part of the process of determining more correct impact parameters.

However, trajectory has also been looked at and errors identified.

NIST has quite slight difference between the orientation and trajectory.

Analysis reveals trajectory parameters to be almost indistinguishable from orientation...the aircraft is going at quite a rate of knots after all, and as the trajectory obviously changed quite significantly mere moments before impact, determining trajectory from earlier motion (as NIST did) produces erronious results.

There's very little difference between trajectory and orientation for UAL175 impact.

Estimating the effect of using more correct impact parameters is not really within the scope of this thread, but suffice to say...
image083.gif

...it is probable that the first two core column rows from the East would be affected quite differently than was the case within the NIST simulation with their differing impact parameters.
 
Obviously this static analysis can only identify issues with the NIST orientation, not the trajectory, though of course it is an important part of the process of determining more correct impact parameters.

However, trajectory has also been looked at and errors identified.

NIST has quite slight difference between the orientation and trajectory.

Analysis reveals trajectory parameters to be almost indistinguishable from orientation...the aircraft is going at quite a rate of knots after all, and as the trajectory obviously changed quite significantly mere moments before impact, determining trajectory from earlier motion (as NIST did) produces erronious results.

There's very little difference between trajectory and orientation for UAL175 impact.

Estimating the effect of using more correct impact parameters is not really within the scope of this thread, but suffice to say...
[qimg]http://femr2.ucoz.com/draft175_files/image083.gif[/qimg]
...it is probable that the first two core column rows from the East would be affected quite differently than was the case within the NIST simulation with their differing impact parameters.
How does this compare to a plot of the flight path through the building?

The orientation of the plane would only change the section of the plane as it hit the building.

What is the angle of the flight path (as seen in video and radar) to the face of the building?
 
Last edited:
You've a problem (within the scope of this thread) right there...
No, I really DON'T.

The decision by NIST to artificially force their trajectory based almost solely upon (a grey) assertion of the engine exiting at a particular location was one of their particularly poor decisions.

(Dem boyz Ne'r played pool :()

Vertical angle != 0. Guaranteed to alter engine trajectory. (*)

* If the impact vertical angle had NOT affected trajectory, the exit storey would have been quite different. (I would say QED here, but, meh...)

Staircase. Guaranteed to alter trajectory.

All manner of other factors (and obstacles). Guaranteed to alter trajectory.

Do you have a trajectory analysis of the exiting engine?
Sure. Wiggly line between where it entered and where it actually exited.

(Don't even consider an exploding aircraft at any point in time, sending stuff off in random directions)


Aircraft impact orientation can be verified. Speculation about engine pathway is simply speculation.

The odds on it actually following impact orientation are about zero.


I really don't have a problem "right there".
 
(Don't even consider an exploding aircraft at any point in time, sending stuff off in random directions)

Actually, considering the mass of the engine, you might want to look at this as to determine the actual impact trajectory.

The flight path represents the path of the planes center of mass.
 
Last edited:
Actually, considering the mass of the engine, you might want to look at this as to determine the actual impact trajectory.

The flight path represents the path of the planes center of mass.

I wonder how much an effect the spin of the engine turbine itself has on the trajectory. I imagine the spin creates a moment of inertia matrix that resists a change in path away from the spin axis, however as the blades shred due to the FOD that could be thrown all out of whack.
 
I wonder how much an effect the spin of the engine turbine itself has on the trajectory. I imagine the spin creates a moment of inertia matrix that resists a change in path away from the spin axis, however as the blades shred due to the FOD that could be thrown all out of whack.
The time could be too short but I'm not losing sleep over it.

And, of course, said engine had a pristine clear path through the building. (err....not?)
 
No, I really DON'T.
Given that the thread topic is your video data analysis and AFAIK you haven't measured engine trajectory...it is straining the friendship to assert that you, femr2, have a problem.
...Vertical angle != 0. Guaranteed to alter engine trajectory. (*)

* If the impact vertical angle had NOT affected trajectory, the exit storey would have been quite different. (I would say QED here, but, meh...)
thumbup.gif

...Sure. Wiggly line between where it entered and where it actually exited...
Actually I doubt "wiggly" but fun terminology aside I agree with your point. My speculation would be a significant trajectory change at engine/wing separation then progressive diverging as the engine plays its part in bulldozing of offices and contents. Since it is heavy (dense - high momentum behind compact frontal area) it would likely get a relatively clear path through whilst lighter bits of air plane get more caught up in the general accumulation and movement of debris. There - everyone else wants a free speculation so I've had mine. :D
...(Don't even consider an exploding aircraft at any point in time, sending stuff off in random directions)...
It's been a source of persisting astonishment over the years to see how many people seem to forget that one.
...The odds on it actually following impact orientation are about zero.
That is probably the only safe speculation.

...I really don't have a problem "right there".
Two issues there viz:
1) What is the problem? AND
2) Why should it be "yours"?

Maybe because your name is in the thread title. But if that is the basis of allocating problems surely it makes more sense to say "tfk has a problem". ;)

(OK - [/EndFun][Re-engage Serious Mode] :rolleyes:
 
Given that the thread topic is your video data analysis and AFAIK you haven't measured engine trajectory...it is straining the friendship to assert that you, femr2, have a problem.
Error in NIST orientation is, as far as I'm concerned, already proved.

It's just a non-point.

IF the engine exited at the NE corner (which is not certain by any mark, and likely to be a bit further to the West by quick looks at the impact videos) it MUST have been deflected to some extent as the aircraft did NOT impact as suggested by NIST.
 
Error in NIST orientation is, as far as I'm concerned, already proved.

It's just a non-point.

IF the engine exited at the NE corner (which is not certain by any mark, and likely to be a bit further to the West by quick looks at the impact videos) it MUST have been deflected to some extent as the aircraft did NOT impact as suggested by NIST.

More NISTpicking I see.
 
* If the impact vertical angle had NOT affected trajectory, the exit storey would have been quite different. (I would say QED here, but, meh...)
I agree that friction with a floor alone could have changed the trajectory. ETA: Like a rugby ball could on friction/rebound with the floor.


IF the engine exited at the NE corner (which is not certain by any mark, and likely to be a bit further to the West by quick looks at the impact videos) it MUST have been deflected to some extent as the aircraft did NOT impact as suggested by NIST.
I don't see any other hole the engine could have exited through.
 
Last edited:
I don't see any other hole the engine could have exited through.

Shouldn't be hard to find fairly high resolution imagery of that corner region to check...and the engine fragment is only about 2ft wide, so it could have come through many-a-hole nearby.

Did you check the angle between the location the engine ended up and the NW corner of WTC2 ? (Hint: It's ~20 degrees clockwise from WTC orientation, quite different to the NIST chosen 13 degrees.)

This is all pretty irrelevant anyway. There's no doubt, imo, that the NIST impact parameters are off, and no doubt that the engine had to be deflected during its journey from entry to exit of WTC2, one way or another.

The assumption that it did not and such "confirmed" the validity of their impact paramaters was, as I suggested, one of the poorer NIST decisions.
 
Last edited:
What is the angle of the flight path (as seen in video and radar) to the face of the building?
My bold.

Radar data cannot be used, as it does not have enough fidelity, and more specifically datapoint frequency is far too low to capture the last-moment manouvers which the aircraft undertook.

As I said, the difference between orientation and trajectory is very slight indeed (and so very difficult to determine, again, because of the last-moment aircraft manouvers).

I did not detect horizontal drift in entry point during impact from nose to tail. A small amount of vertical drift may have been present. Would have to search the piling system.
 
Last edited:
More NISTpicking I see.

It seems to me that the main topic of this thread -- which femr2 didn't start -- is the accuracy of femr2's video analyses vis-a-vis NIST's. (Initially it focused on WTC 7; recently it has jumped to WTC 2; I haven't reviewed the intervening 3000 posts over 2 1/2 years to follow all the twists, turns, and derails.) It's fine to think that this isn't a consequential topic, but I don't think femr2 should be faulted for holding up his end of the technical discussion.
 
How does this compare to a plot of the flight path through the building?

The orientation of the plane would only change the section of the plane as it hit the building.

What is the angle of the flight path (as seen in video and radar) to the face of the building?
The RADAR data supports up to a 20 degree angle at impact. Too bad the FDR was lost. If the pilot was able to do a turn, he could make the angle 6 to 10 degrees the other direction. Doubt the pilot had a clue what to do, he almost drifted off target, did not correct for drift, and was not a pilot, but a failed murderer who hated Americans - a loser - like 911 truth followers.

The ironic part, this issue will NOT change reality. Is is another goal free exercise. There will be no inside job, no CD, Ross and Kuttler papers remained failed.

Where a plane is pointed, is not where it is going - was there any aero included in this goal free study? Poor femr2 has been making up nonsenses about NIST for years, with no goal, no conclusions, and will not change reality; fire and impacts destroyed the WTC complex. Full up models beat the goal free attack NIST for no reason nonsense. NIST got the speed wrong, which is a squared term in this impact stuff; much more important than orientation; which can be seen clearly by looking at the other impact. Wait, having the speed wrong doesn't change 911. Darn.


Modeling the impact does nothing to change what happened, and as seen, is of no use to the people doing the study, No purpose, no goal. Not related to 911 truth silly claims. How can it be used to debunk 911 truth claims?
 
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