Merged Discussion of femr's video data analysis

I raised this point earlier. Additionally, the FOD destruction of turbine blades could have affected the dynamics.
Yes. Two forces that could be involved in changing direction coming from rotational momentum and precession.

The engine has already separated from rest of aircraft - whether initially still attached to pylon or sheared off pylon. It starts to get seriously bashed around BUT if the engine is still spooling at high revs and gets FODded it slows/seizes/stalls. So we have rapid transfer of rotational momentum to the exterior normally non rotating parts of engine plus whatever fairings, mounts, bits of pylon are still attached. So the whole mass starts rotating - whilst it is ploughing thru the interior of the building. Anything spinning through such a mess bound to leverage itself some changes of direction..

...And I haven't mentioned precession - yet. :)

...Or simple "bump and bounce" deflections. :confused:


BTW ..since engine separation is a feature of aircraft crashes I though beachnut could well have experience which is relevant.
 
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 minimize 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?

In pilot training, I was going straight up, we hit zero speed straight up; twin engine jet (thrust to weight less than 1). The aircraft stopped, and we were looking straight up; then the aircraft fell to straight down, no turning, no twisting, straight down.

When we speed up or slow down in a jet, there was no adverse yaw - we would go faster straight. When we cut the engines, we go straight, slower.

The engines would liberate parts during impact. The front fan is going kind of slow, maybe 2500 rpm, not as fast as the rest of the engine. When you crash, you cut the engines prior to impact - put out the fire, hope for the best - (bold face procedure - memorize).

Ironically, the engine could bounce off the core columns and be deflected... etc

No need to make fun of NIST's model, there is no way to model this stuff to match reality - that is why it is called a model.

The engine's strongest hold on the airframe is along the longitudinal axis. Straight ahead. Any side forces of major magnitude, and your engine might depart; lateral junk. Pitch, engine is happy, lateral upset, engine might leave. You could take some kids and rock the engine off sideways; kind of dumb, but that is the weakness; we don't fly sideways. In an upset or extreme upset, you could sling engines off.

http://speakingeagles.com/wp-content/uploads/2011/08/Kevin-Sweeney-KC135-with-engines-blown-off1.jpg
Lateral upset.
 
In pilot training, I was going straight up, we hit zero speed straight up; twin engine jet (thrust to weight less than 1). The aircraft stopped, and we were looking straight up; then the aircraft fell to straight down, no turning, no twisting, straight down.
My closest experience was in a Macchi trainer. My friend - also Army Reserve - went for a flight and the pilot showed him "stall turns". My pilot was kinder on my stomach - so I've never "been there - done that". Even 1hour of gentle stuff was hard on my stomach as a ground grunt from the "walk around in a green suit" branch of the military.
...When we speed up or slow down in a jet, there was no adverse yaw - we would go faster straight. When we cut the engines, we go straight, slower. ..
Got that thanks. I know that it wasn't so with the big piston engines of the WW2 single engine fighters. Doing a bit of Googling and it seems that fan counter rotating relative to turbine is used for dynamic minimising of gyro effects in modern jets. Plus multi engines are inherently self cancelling for those torque and gyro effects. BUT the engine we are talking about had become disconnected from rest of aircraft so gyro and deceleration torque would be back in full effect.
...The engines would liberate parts during impact. The front fan is going kind of slow, maybe 2500 rpm, not as fast as the rest of the engine. ...
Understood - and likely to be the first bit to fail in a WTC style crash. Leaving the turbine and arse end of the engine still rotating - tho how long it would stay at speed anyones guess with so much FOD. BUT any rotational balancing of fan v turbine lost which is back to where I got with my questions. We are dealing with a free flying isolated engine plus seriously damaged.
When you crash, you cut the engines prior to impact - put out the fire, hope for the best - (bold face procedure - memorize).
Sure I comprehend the place of IA's as trained reflex before you have time to think actions followed by SOP's where you (may) have time for the check lists. But 9/11 wasn't trained pilots interested in fire prevention or damage minimisation.
...Ironically, the engine could bounce off the core columns and be deflected... etc
Sure - there are multiple possibilities. But the overriding aspect being that the starb'd engine wasn't on line for core plus it was a concentrated large mass which would plough through office partitions - unlikely that it would meet much that could do a lot of deflecting. But on the face of the evidence it had deflected whilst passing through the tower. So the musing/speculation is about what could have caused the deflection -- not the near certain fact that there was deflection.
...No need to make fun of NIST's model,...
I'm not. Doesn't mean I shouldn't look at the limits of what they intended to model.
... there is no way to model this stuff to match reality - that is why it is called a model.
Correct - and I do understand models plus their limitations etc. Both physical models and abstracted analytical/mathematical models - virtual models.
...The engine's strongest hold on the airframe is along the longitudinal axis. Straight ahead. Any side forces of major magnitude, and your engine might depart; lateral junk. Pitch, engine is happy, lateral upset, engine might leave. You could take some kids and rock the engine off sideways; kind of dumb, but that is the weakness; we don't fly sideways. In an upset or extreme upset, you could sling engines off.
Actually I understand those aspects. Also that engines/pylons would be designed break away before whatever impact starts to pull bits of wing off..... The only aspect I don't know - and it may vary with aircraft types - is whether they plan for engine off pylon OR engine plus pylon off wing as the desired separation. I suspect pylon off wing (EDIT: I see that your picture shows pylon off wing.) but... Makes no difference for this current debate.
Thanks for the pic -- KC135....mmmm - not yours I trust. ;)

And thanks for the info.
 
If the simulation is good enough, they shouldn't need to "tweak it".

That's a rather silly thing to say. It cannot have escaped your attention that we've been discussing for years what counts as "good enough."

Other than me QUOTING IT about 3 HOURS ago... :covereyes

I doubt I need to explain that relying on your statement in #3198 would, by definition, not involve reading #3202. But who knows?

At any rate, you didn't respond to my point. The range 13-17 degrees in Table 7-4 doesn't depend either on the video analysis (summarized in Table 7-3) or any assumptions about the trajectory of the starboard engine. It's a simple point, and I'm not sure what your issue with it is, since you haven't stated one.
 
That's a rather silly thing to say. It cannot have escaped your attention that we've been discussing for years what counts as "good enough."
Perhaps if the impact parameters had been more correct, then subsequent simulation behaviour would have been more accurate.

There's no good excuse for the gross inaccuracies in impact parameters.

I, a lowly nameless forum poster, have repeatedly shown how poor NIST measurements were, and how simple methods such as the rotoscoping presented provide the means for much more accurate results.

For the NIST video based analysis of trajectory to come out at 19 +/- 6 degrees is nonsense.

Can you imagine that range on a rotoscope view ?


Not good enough.

The range 13-17 degrees...
...is wrong.
 
...And I haven't mentioned precession - yet. :)

...Or simple "bump and bounce" deflections. :confused:

Let's not forget the rather large explosion, though timing may come into play there.

Let's not also forget that the point here is determination of accurate trajectory and orientation of the aircraft.

In NIST's own words...

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

..resulting in them setting lateral trajectory to 13 degrees.

The simplest of cross-checks, looking at where the engine landed, shows that decision to be, at best, flawed.

I find it "odd" that those speaking of "good enoughism" seem to have no issue with the extreme lengths to which NIST created an accurate model...
502079026.png

...of the entire structure, but accept gross errors in the trajectory and orientation which the aircraft model was slammed into the tower.

The two "levels of detail" and "desired accuracy" just don't fit together.


Boys with toys.
 
Let's not forget the rather large explosion, though timing may come into play there...
Yes to both. Overall my purpose in the last few posts has been two fold:
1) let's see if we can get some reality into our speculations as to what mechanisms were in play - it wasn't a simple matter of geometry devoid of any complicating dynamic processes. AND
2) Identify the massive blind spot of the inherent presumption that the last ~7o happened at the exit wall independent of any other deflection processes.
...Let's not also forget that the point here is determination of accurate trajectory and orientation of the aircraft...
Yes - "When you are up to your arse in alligators it is easy to forget..." ;)

You are right that such should be the current objective. And even that one has fog around - apparently from avoiding lèse-majesté.

BUT if I was a cynic - may the gods forbid - I would also ask why the thread focus changed from WTC7 measurement accuracy. ;)

...In NIST's own words...

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

..resulting in them setting lateral trajectory to 13 degrees....
AND the inbuilt faulty presumption that all that ~7o occurs at or leaving the exit hole. Something which I have identified in those words, which I suggest is ludicrous and which no-one here seems to want to address. Then your way of saying the same thing:
...The simplest of cross-checks, looking at where the engine landed, shows that decision to be, at best, flawed.
whether said your way or said my way it is a disjoint in the logic.
...I find it "odd" that those speaking of "good enoughism" seem to have no issue with the extreme lengths to which NIST created an accurate model...
[qimg]http://femr2.ucoz.com/_ph/2/2/502079026.png[/qimg]
...of the entire structure, but accept gross errors in the trajectory and orientation which the aircraft model was slammed into the tower.
...which is the same foggy thinking which has been with claims in this thread for at least some months. "are the measurements good enough" MUST relate to a defined purpose and therefore to the person who has a purpose. Which naturally includes NIST for whatever their purpose was but also anyone else here trying to use measurements for their own purpose which may be different to NIST.
...The two "levels of detail" and "desired accuracy" just don't fit together...
Yes
...Boys with toys.
Hard to avoid that conclusion even for me in my usual "let's be generous mode" :rolleyes:
 
Let's not forget the rather large explosion, though timing may come into play there.

We should not. Although it was likely well after the engine exited the building. For a fuel to explode it needs time to mix with air. The engine was not going to wait for this to happen. ;)
 
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

Based on simulations that showed little deflection of the engine sections by the office contents the relatively straight path of the engine through the building was used to decide between the impact angles that best fit the observed damage to the exterior of the building.


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.

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".

If the NIST trajectory is right you need a 6-7 ° deflection, if you go with Femr2's trajectory you need double that deflection.
 
Based on simulations that showed little deflection of the engine sections by the office contents the relatively straight path of the engine through the building was used to decide between the impact angles that best fit the observed damage to the exterior of the building.
Which comment restates the NIST position including its inbuilt source of probable error - the reliance on the assumption of a linear transit through the building. However don't overlook the main point which femr was making and which I have also made - the exit trajectory shows additional deflection which is significant.

Put simply the NIST assumed impact trajectory is derived by backwards extrapolation of a presumed transit path through the building AND the assumption that the transit path was linear - no significant deflections.

However the point which NIST overlooked, and which much discussion here is overlooking, is the significance of the accepted fact that there was a total deflection of 20o shown by the exit and fall to ground trajectory.

As Reactor Drone correctly points out:
...If the NIST trajectory is right you need a 6-7 ° deflection, if you go with Femr2's trajectory you need double that deflection.
Now let's get a proper focus on that true statement. The key issue IMO is not that the NIST and femr findings differ. The key point is that BOTH of them show a deflection. So we can, at least briefly, get away from the NIST v femr comparisons. They both say there was an additional deflection. And AFAICS no one here is denying that fact of additional; deflection.

So what caused that deflection? More importantly, what impact does it have on the NIST assumptions about the linear transit path and the extrapolated impact trajectory which NIST based on it?

I suggest that it is fatal to the NIST hypothesis and here is why.

If NIST is correct that the transit through tower path was linear it inevitably follows that the extra deflection MUST have resulted from the penetration of the perimeter at the exit point. And that is true whether we take the 6-7° needed by NIST OR the double that needed by femr. So the NIST v femr differences are irrelevant to what follows.

Now members may agree or disagree that the extra deflection occurred at the exit point but it doesn't matter. There are two options and NIST was wrong whichever option we follow. Here's why for both:

1) If members hold the view that that such a step deflection could not occur at the exit point then it must have originated inside the building during transit - and that kills the NIST assumption of "linear transit".

Alternatively;
2) If members claim that such a step deflection could occur on exit then a similar step deflection would equally plausibly have occurred on initial impact entry. And that kills the legitimacy of the NIST "backwards projecting" the transit path to become impact trajectory.

So that puts the NIST position out of consideration and the discussion is simplified to comparisons of femr's measurements versus other members measurements.
 
Last edited:
Now members may agree or disagree that the extra deflection occurred at the exit point but it doesn't matter. There are two options and NIST was wrong whichever option we follow. Here's why for both:

1) If members hold the view that that such a step deflection could not occur at the exit point then it must have originated inside the building during transit - and that kills the NIST assumption of "linear transit".

Alternatively;
2) If members claim that such a step deflection could occur on exit then a similar step deflection would equally plausibly have occurred on initial impact entry. And that kills the legitimacy of the NIST "backwards projecting" the transit path to become impact trajectory.

So that puts the NIST position out of consideration and the discussion is simplified to comparisons of femr's measurements versus other members measurements.

As far as point 2 goes, the engine fragment is travelling much slower on exit than it was on entry so a deflection would be more likely on leaving than on entering. You also have a 200 ft path through the building vs another thousand plus feet once it leaves so a minor deflection of a high speed object within the building may be barely noticeable but a lower speed deflection with aerodynamic and rotational forces during the fall will give you a more noticeable angle.
 
Last edited:
As far as point 2 goes, the engine fragment is travelling much slower on exit than it was on entry so a deflection would be more likely on leaving than on entering. You also have a 200 ft path through the building vs another thousand plus feet once it leaves so a minor deflection of a high speed object within the building may be barely noticeable but a lower speed deflection with aerodynamic and rotational forces during the fall will give you a more noticeable angle.
Interesting comments but I will not follow the side tracks at this stage - unless you want to build them into an argument for a different explanation - presumably an argument that NIST was right to counter my explanation as to why NIST was wrong.

Meanwhile let's see if anyone else cares to take up my argument and either tries to expand on it or to counter it.
 
Which comment restates the NIST position including its inbuilt source of probable error - the reliance on the assumption of a linear transit through the building.

It seems to me that this line trivializes the difference between femr2 and NIST, unhelpfully.

femr2's point estimate of the orientation -- and, at least by implication, the trajectory -- is outside NIST's range of possible trajectories based on video analysis (Table 7-3), which carries forward into subsequent estimates. If femr2 is correct (which seems plausible to me), then the engine helps NIST to choose the least wrong of its estimates.

I don't think femr2 has rebutted NIST's proposition of a 3-degree difference between orientation and trajectory. It seems possible that trajectory 9 degrees clockwise / orientation 6 degrees clockwise fits the impact pattern as well as the 13/10 and 17/14 scenarios that NIST depicts.

I'm curious whether it's possible to do decent mockups that can be freely distributed, but I don't have an ETA for even wrong results. Of course I'm not sure how much one should care about these 4 degrees -- but if NIST's video analysis set the trajectory at 19 plus-or-minus 6, and the true value is close to 9, that's interesting even if not cosmically important.
 
It seems to me that this line trivializes the difference between femr2 and NIST, unhelpfully...
Not so Mark. you seem to be taking bits of sentences out of context and missing the whole argument that my post presented.

First the "this line" you refer to does not mention the difference between femr2 and NIST so it cannot trivialise that difference. But lets look at what I really said which was this paragraph:
Which comment restates the NIST position including its inbuilt source of probable error - the reliance on the assumption of a linear transit through the building. However don't overlook the main point which femr was making and which I have also made - the exit trajectory shows additional deflection which is significant....
..and the following two paragraphs reinforced my key point which you are overlooking. That key point is the significance of the exit trajectory which was the main focus of my post. I even flagged it as "the main point".

In context the bit you did quote was nothing more than an initial recognition of two facts. Both facts had already been identified by Reactor drone in this:
Based on simulations that showed little deflection of the engine sections by the office contents the relatively straight path of the engine through the building was used to decide between the impact angles that best fit the observed damage to the exterior of the building.
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? Let me be specific. Is Reactor drone accurately representing the NIST baseline assumption? I think he is. what do you say?

The second fact I referred to - it was implied by Rector drone and I made it explicit - is my claim that if the straight line assumption is wrong then NIST's work based on that assumption is wrong. Agree or not Mark? That if NIST's assumption of "relatively straight path" is wrong their other conclusions will be wrong?

And the last issue with your opening comment is a process mistake. I have not made any reference to femr2 or the difference between femr2 and NIST in the statement that you criticise. Therefore my statement cannot "trivialise the difference between femr2 and NIST". And that it "seems" to do so to you is an error of perception/interpretation.

Now the key point of my reasoned post which you overlooked was that "the exit trajectory shows additional deflection which is significant...." and I explained in succinct logical argument why I claim that it was significant. Your further comments in your post - interesting though they could be - do not address my reasoned argument.

Put simply my conclusion is that the significant change of direction revealed by the exit trajectory shows that NIST's reasoning was wrong. And I identified two possible scenarios - both of which show NIST as wrong.

So the legitimate path for you to criticise my post is to either show my logic in treating the two options was flawed OR to provide a third option.

And, BTW, the only point where the difference femr2 v NIST touches on my argument is in the reality that both femr2 and NIST acknowledge a significant deflection with the exit trajectory. Despite the difference in their numbers all that matters for my argument is that they are in agreement that there was such a deflection. Not its magnitude.
 
Last edited:
Based on simulations that showed little deflection of the engine sections by the office contents
Whilst not from the WTC2 simulation, perhaps this "insight" into engine fragment behaviour during simulation should be pause for thought...
391096442.png


the relatively straight path of the engine through the building was used to decide between the impact angles that best fit the observed damage to the exterior of the building
Who knows what the actual path was ?

What is known, is that it was likely NOT "relatively straight".

If the NIST trajectory is right you need a 6-7 ° deflection, if you go with Femr2's trajectory you need double that deflection.
Which means nothing.

Oh, and lookie see...

239964416.png


Measure the north angles.

More NIST inconsistency. Who knows how they oriented the towers... :boggled:
 
So that puts the NIST position out of consideration and the discussion is simplified to comparisons of femr's measurements versus other members measurements.

There are a few "key" points to bear in mind when evaluating the NIST data (which will likely get longer as folk continue to "discuss")...

  • 20 degree angle of engine ground location
  • 15 degree RADAR based approach vector for several kilometers prior to final manouvers
  • NIST video based analysis results of 19 +/- 6 degrees
  • NIST decision to set trajectory to 13 degrees by flawed reasoning
  • Results from others, such as achimspok and myself (I would use "I" there, but grammar would imply some form of collaboration, which there was not. Two separate studies)
  • Numerous orientation/trajectory combinations allow a match to observable impact profile
  • NIST based their findings on motion of the aircraft before impact. Late manouvers imply constant change in trajectory and orientation, reducing useful timespan of video data to that just prior to and during impact. Values determined with early data are bound to be wrong.
  • No detectable drift/slew between aircraft nose and tail can be found during impact, implying minimal/insignificant/no difference between orientation and trajectory

...etc...
 
I don't think femr2 has rebutted NIST's proposition of a 3-degree difference between orientation and trajectory.
The problem is lack of data.

As the trajectory and orientation were constantly changing as the aircraft approached the tower, the later trajectory and orientation are determined, the more accurate the values are likely to be.

NIST looked at data pretty darn early, and their video methods produce clearly wrong results (19 +/- 6 is ridiculous given radar approach vector of 15)

There's no detectable drift/slew between nose and tail entry points.

Whilst that doesn't imply "zero" difference, it does imply it's quite small.

It seems possible that trajectory 9 degrees clockwise / orientation 6 degrees clockwise fits the impact pattern as well as the 13/10 and 17/14 scenarios that NIST depicts.
Multiple combos exist which match impact pattern.

I'm curious whether it's possible to do decent mockups that can be freely distributed
What do you mean ?
 
Last edited:
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? Let me be specific. Is Reactor drone accurately representing the NIST baseline assumption? I think he is. what do you say?

The second fact I referred to - it was implied by Rector drone and I made it explicit - is my claim that if the straight line assumption is wrong then NIST's work based on that assumption is wrong. Agree or not Mark? That if NIST's assumption of "relatively straight path" is wrong their other conclusions will be wrong?


I wouldn't use the word assumption since it was a conclusion based on modelled behaviour.

Put simply my conclusion is that the significant change of direction revealed by the exit trajectory shows that NIST's reasoning was wrong. And I identified two possible scenarios - both of which show NIST as wrong.

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.

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.
 
There are a few "key" points to bear in mind when evaluating the NIST data (which will likely get longer as folk continue to "discuss")...
As you will appreciate I understand hat there are many factors.

But the key aspect as you identify is that "folk will continue to discuss" -- round in circles with an underlying meteorological objective -- and foggy confusion continuing.

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......

So I decide to lift the game to reasoned argument - and take out the points one by one - starting with the easiest target - the faulty "reasoning" behind the 13o assumption. Naturally once the premise assumption is removed the 13o is out of contention. Much to the regret of any NISTophiles who may be concerned about lèse majesté.

So far my attempted shift to reasoned argument instead of discussion is having limited success. But Reactor drone had offered one point worthy of reasoned rebuttal - twice actually - in the claim that going faster changes the nature of the mechanism. I'll get back to that - at least he is prepared to counter argue so we have some basis for progress.
 

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