Merged Discussion of femr's video data analysis

"Believe" what you please.

I'm too old to do anything else. :D


The initial objective, as I've already said, was a response to claims that the Carmen Taylor and Hezarkhani footages were faked and from "impossible" viewpoints.
Such origins can be easily proven, regardless of what you "believe".

Understood (I read the thread). You can't deny the overtones of your initial work. (to add: You have certainly progressed from there)


Somehow I don't believe you're sincere. :p


:rolleyes: Been there, done that. RADES data stops short, and is of little use. Have looked in detail at behaviour during impact, and as I've said several times now...there's no detectable drift/slew during impact.

100 ton planes don't make sudden changes in direction.

Why are you going round in circles ?

No circles. Like I said. It really doesn't matter much to me.

Prove difference between orientation and trajectory with real-world data and imagery and I'll accept it of course.

I'd have to have a good reason for the effort. Does this fall into the purpose trap again?
 
I don't believe they assumed that. They did have a map of NYC after all.

Did they claim there was no deflection or is this something you derived from the data? I don't see it.



264038192.png


Although the lateral approach angle of UAL 175 had a nominal value of 15 degrees, additional observable information was used to define a most probable flight condition. Figure 7–13 shows the top view of WTC 2 with the engines and landing gear in their pre-impact location. Also shown is the projected trajectory of the starboard engine of UAL 175 with an initial lateral approach trajectory of 13° instead of 15°, assuming the engine was not significantly deflected as it passed through the building. With this lateral trajectory, the starboard engine would exit the tower at the northeast corner, consistent with the observables from video and photographic evidence.

It is possible that the tower structure and/or contents deflected the engine from its initial lateral trajectory. The global simulations described in Chapter 9 used a standard configuration for building contents similar to WTC 1. This configuration did not cause substantial deviation in the trajectory of the starboard engine. This lateral trajectory was, therefore, the most likely and was adopted for the global analyses.

...amongst other references.

What you "believe" and what you "see" or "don't see" is no excuse to not bother and at least TRY and check your facts out :(

NIST didn't set the trajectory based upon nailing the angles from video footage...instead they "Adopted" it based on a linear path from entry point to NE corner :rolleyes: ...ignoring the fact that the exit trajectory was 20 degree from tower normal :rolleyes: Top notch :eye-poppi
 
100 ton planes don't make sudden changes in direction.
Who said they did ?

I'd have to have a good reason for the effort. Does this fall into the purpose trap again?
I wouldn't choose to keep making false/unfounded/unresearched assertions based apparently upon "belief". I'd much rather have discussion where folk are "right" more often. Make "better" assertions.

Oh, and whilst I have it handy...
The lateral trajectory was not varied in these analyses so that the starboard engine trajectory was aligned with exiting the northeast corner of the tower
NCStar 1-2b p290.

You were saying ?
 
You might think they considered the flight path also. (as a modifier). We may never know. What would be important if any of this mattered.

I know, you don't want to go there.
 
There's quite a mixture of fact and speculation going on here.

And I think some of us have got a mismatch between our facts and our speculations. :rolleyes:

Try this, my $AU0.02 worth, to see if I've got it right.

Coming down from the big picture we have:
1a) Pro NIST arguments which are based on an assumption that the engine transited the building without deflection; versus
1b) femr and my contentions that deflections did occur. We come from slightly different directions ("pun" not intended :o) Femr stating in several ways that NIST's choice was "was not a great decision imo." Whilst I have posited multiple "bounce" impacts PLUS my recent speculation as to some engine spinning or gyroscopic factors as possible causes of deflection;

Now how or what could cause deflection remains speculation as to possibilities - dominated by factors of large mass and high velocity BUT the overriding fact IMO is:

2) The reality that the engine emerged from the building with a 20o change of direction.

Pause there and look at the relationship of that emergence trajectory with the two preceding options of 1a and 1b

IF the NIST and pro NIST arguments are correct - viz no deflection whilst transiting the building - it means that the final impact with the wall as it emerges causes the additional 7o making a total of 20o change of direction.

I find that necessary "single impact" cause of all deflection to be highly implausible.

Look what it requires:
A) no other impact on the engine whilst traversing inside the building has any effect on direction whatsoever; WHILST
B) The one single final impact causes a ~20o change of course. (EDIT: actually 20-13=7o change - thanks to femr pointing out that error. It doesn't change the argument I am presenting.)

Therefore it is more plausible that some factor or factors caused deflections inside the building during the transit of the building.

And, taking my attempt to separate facts from speculation a step further, it is highly probable fact that there was deflection during transit - whatever the causes.

And, whilst that claim is still "speculation", I suggest it is much closer to a realistic assessment of what happened than the NIST and related supporting speculations.

Final point - how can we legitimately ignore the exit trajectory and what caused the change of direction?

...instead they "Adopted" it based on a linear path from entry point to NE corner :rolleyes: ...ignoring the fact that the exit trajectory was 20 degree from tower normal :rolleyes: Top notch :eye-poppi
NIST ignored it - was that choice valid??? Possibly it was for their purposes - but let's not go there. It was not valid for this current discussion IMNSHO.
 
Last edited:
You might think they considered the flight path also. (as a modifier).

You're appearing to be trying to defend their poxy analysis.

An analysis that resulted in them stating lateral trajectory anywhere between 13 and 25 degrees, with the "finesse" of their video based analysis being 19 +/- 6 degrees. (And orientation 8 +/- 6 degrees).

Very poor. It is obvious that the rotoscoping methods provide a way to determine much more accurate values.

Bearing in mind that radar data shows the approach vector was around 15 degrees for the preceeding few kilometers prior to final manouvers...that their "video based analysis" came out at 19 degrees allows one to assess the quality of their "video based analysis" rather easily. It was crap.
 
Last edited:
IF the NIST and pro NIST arguments are correct - viz no deflection whilst transiting the building - it means that the final impact with the wall as it emerges causes the 20o change of direction.

Not actually true. The angle to the face of the building was 20 degrees. The change in angle was somewhere less.

Not that it matters because it was still ripping stuff up on it's way to that end.

This is another "to what purpose" argument. "femr2 (tries to)proves NIST wrong for the umtenth time". Past that. no idea.

It would be fun if someday he wrote up his work with a purpose in mind. :rolleyes:
 
In NIST context (enter at 13 exit at 20) that would be a 7 degree change.
Gotcha - thanks. Doesn't change the point I wanted to make - but I'll note the original post. My focus in writing was totally on the false concept that the exit change of direction can be ignored. It cannot in any reasoned assessment of what went on.
 
My focus in writing was totally on the false concept that the exit change of direction can be ignored. It cannot in any reasoned assessment of what went on.
Sure. NIST included photos and location details for the engine, so it's not as if they didn't know...they just chose to "put that to one side".
 
...It would be fun if someday he wrote up his work with a purpose in mind. :rolleyes:
Nah....

femr's purpose has always been clear - do the best measuring that he can.

Nearly all of the "prove femr wrong" fun has been based on attempts to attribute other purposes to femr. Which he has steadfastly withstood. Whilst bashing several hundred moles that have popped up. And in doing so his opponents have given us loads of examples of false logic to analyse and occasionally rebut.

"If it doesn't change impact and fire caused the collapse I'm not interested"
"How does that affect 19 terrorists and four planes?"
"You have no goal."
"Why is this topic in this sub forum?"
"What has this to do with conspiracy?"
...etc etc ad nauseam

..and I doubt that I need to attribute those multiple bits of irrelevancy to specific authors.

They are all familiar from repetition in the style of a "broken gramophone* record" (OK phonograph* for US folk.)

:runaway



* Younger members send PM and I will explain gramophone/phonograph. And the characteristic effect of a damaged groove which causes the sound to...causes the sound to...causes the sound to...causes the sound to...causes the sound to :teacher:
 
Last edited:
clap.gif

I have about 3feet linear shelf space of those round black things - in a couple of boxes in the garage. About two years back I bought a digital turntable which can directly write the files to USB memory. So far I've only tried one side of one record...."when the foeman bares his steel ta ran ta ra...."
 
Nah....

femr's purpose has always been clear - do .

... to...causes the sound to...causes the sound to...causes the sound to :teacher:
Best measuring? lol, it appeared the purpose was to make smooth curves. That takes care of the best measurements and makes them, "smoother". I thought it was comedy when the SG filter was used. And wondered why it was used, then realized it was googled (confirmed by Major Tom). What a bunch of BS.

The flight study has failed to include many variables. Not surprising from someone who calls papers of woo, technical, and gravity collapses labeled demolition. Attacking NIST (who needs NIST, 911 truth and femr2 do) and giving a pass to 911 truth.

"do the best measuring that he can", is not going to debunk crazy 911 truth claims, but it is the best he can do. I was interested when he will drop his inside job stuff, and CD. Will the best measuring do it?

How does best measuring relate to 911 conspiracy theories - the big picture? Got it; it is "the best measuring that he can". never-mind

Like the gramophone/phonograph; or practice for golf, and then a break through... Will this work put to rest the Major Tom conclusion that gravity collapses were an illusion?
 
...The flight study has failed to include many variables...
You got that bit right beachnut.

However a serious question - where I don't know the answer - way outside my range of experience and pure basic physics doesn't help me.

The question I raised a few posts back about rotational effects possibly causing/contributing to changes of direction. I am vaguely aware that some jet engines have counter rotating elements to minimise gyroscopic precession effects. So a question or two for the aircraft crash investigator - could precession OR rotational torques from a seizing engine be factors contributing to a change in trajectory? Or are they too small to be of any significance? Or too slow to impact given the brief time interval available?
 
Yet the angle between the NE corner and where it landed is 20 degrees...

And the simulated engine never even made it out the building.

Highly accurate then... :rolleyes:
Exactly.

There's no way they would get a damage matching the real one, no matter what angle they used.
 
Sure. NIST was wrong to assume it wasn't deflected.

OK, albeit not a very ambitious hypothesis.

Only had another 1400ft to travel afterwards...simulation should have indicated it pinging out of there at a rate of knots.

It's apparent that NIST didn't tweak the simulation to get the engine part to land at the corner of Church and Murray, or anywhere nearby. It's not so apparent that NIST should have done so -- although it would have been nice for the report at least to notice the apparent contradiction between Figure 7-13 and the final location of the engine.

Where it landed provides you with information to assess the NIST assumption that it was not deflected during its journey through the building, and their related decision to set trajectory of the aircraft based upon that, rather than upon checking the orientation at the moment of impact (their calculations beyond those decisions are based on earlier approach vector)

I think that is an erroneous characterization. As far as I can tell from the text, the exit point of the engine was used only to define a "most probable flight condition" within a trajectory range of 13 degrees to 17 degrees. And nobody relying on your comments would know that the NIST report actually states, "It is possible that the tower structure and/or contents deflected the engine from its initial lateral trajectory." Unless someone can offer an alternate explanation of how the engine part ended up where it did, "possible" should be upgraded to at least "very likely." But if that last part of the discussion were lopped off, you wouldn't be substantially more in agreement with NIST.
 
It's apparent that NIST didn't tweak the simulation to get the engine part to land at the corner of Church and Murray, or anywhere nearby. It's not so apparent that NIST should have done so -- although it would have been nice for the report at least to notice the apparent contradiction between Figure 7-13 and the final location of the engine.
If the simulation is good enough, they shouldn't need to "tweak it".

And nobody relying on your comments would know that the NIST report actually states, "It is possible that the tower structure and/or contents deflected the engine from its initial lateral trajectory."
Other than me QUOTING IT about 3 HOURS ago... :covereyes
 
... Unless someone can offer an alternate explanation of how the engine part ended up where it did, "possible" should be upgraded to at least "very likely."
Yes...which is my choice out of the dichotomy I posted recently. Your "very likely" == my "highly probable" IMO.

And I was being pseudo scientific with the "highly probable" when I meant "near [Aussie preferred adjective] certain" ;)
 
Last edited:
You got that bit right beachnut.

However a serious question - where I don't know the answer - way outside my range of experience and pure basic physics doesn't help me.

The question I raised a few posts back about rotational effects possibly causing/contributing to changes of direction. I am vaguely aware that some jet engines have counter rotating elements to minimise gyroscopic precession effects. So a question or two for the aircraft crash investigator - could precession OR rotational torques from a seizing engine be factors contributing to a change in trajectory? Or are they too small to be of any significance? Or too slow to impact given the brief time interval available?

I raised this point earlier. Additionally, the FOD destruction of turbine blades could have affected the dynamics.
 

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