Near freefal collapse speed

Centre of Gravity.
cg




I see the "near freefall" collapses of the towers are still seen by some as indication for a Controlled demolition.

i once believed the same.
But Gregory Urichs short paper about it and me watching several collapses compared to CD's convinced me, it is no indication at all.

most CD's do merely start a progressive collapse that is driven by gravity.

but we still see WTC being compared to CD videos.
have any truther done any work on this to show that the collapse speed can indicate a CD?
Truthers have no clue the big mover, the major energy source for destroying buildings with CD is gravity; E=mgh. Pretty much ends the debate, 911 truth is unable to think for themselves, does not take a study to figure out. 911 truth made it up as they went, now 911 truth is in reruns.
 
Last edited:
Wouldn't it be possible if there was an additional downward force?

Thought I read once that it seemed like the building as a whole provided that extra force by "pulling" a single point (that was being used by truthers) down after it first started collapsing.
Information.

Correct. You sound "surprised". May I suggest you check NIST's data for another portion of the building. Also over-g.


All manner of possible reasons, one being the trace point not being the CoG.

I suggest you read the "femr2 video data analysis" thread if you're "new" to WTC7 over-g discussion. Here is not really the place to re-hash it again.
Information and passive-aggressive condescension.
 
nitpick: my physics prof hated that term. Preferred "Center of Mass" as its more succinct, requiring no gravity field.
cg is used for aircraft. cg, it would be the center of mass

CoG is used for ...
The definition of a CoG is "the source of power that provides moral or physical strength, freedom of action, or will to act."http://en.wikipedia.org/wiki/Center_of_gravity_(military)#cite_note-1 DoD Dictionary of Military and Associated Terms. Joint Publication 1-02. 2008
 
How bizarre. The graph...
447669743.jpg

...shows displacement, and acceleration.

RHS axis acceleration (ft/s^2), LHS axis displacement (ft)

Explain your hissy fit tfk

Not "bizarre" in the slightest. Graphing is simply another thing about which you know just enough to be dangerous.

I understand your graph perfectly fine. Better than you, it would appear. (See last point below.)

I understand the little deception you play to hide scatter in the displacement data (setting the top of the displacement to 0 instead of +10, thereby hiding data excursions above the 0 axis.) You'd get smacked for this in any formal academic or professional setting.

I understand the simple error that you make in your legend (identifying the red line as "raw trace data". It ain't. It's filtered data.)

I understand the mistake that you make in setting the acceleration of gravity to -32.2 ft/sec^2 for all time. The graph is supposed to be comparing the acceleration that the north wall would have had if it collapsed at free fall. Well, it's acceleration would have been zero, not -32.2 ft/sec2, right up to the moment of release (t0). Which on your graph, was about 11.8 seconds or so. Before that time, the acceleration should be zero.

All of the above are little nits. Errors. Sloppiness. But nits, nonetheless.

Everyone who understands graphs knows exactly what I mean when I say that this is not a "displacement versus acceleration graph".

Everyone except you, it would seem.

Which leads to one of two possibilities:
1. Your puzzlement over my comment is genuine, and here is another place where, you may be completely wrong, but you're never in doubt.

or

2. You know exactly what is wrong with that label, but your ego prevents you from admitting a trivial, inconsequential error.

As far as knowing your own graph better than you … at least I can read it correctly.

Sabretooth asked:
Am I reading that graph right? Does it suggest falling faster than freefall for nearly 3 seconds?

And you replied:
Not quite. … About 1s.

Your graph shows >g acceleration for virtually the entire time between 12.75 & 14.3 seconds. With a momentary sub-g excursion around 13.75 seconds.

Last time I checked, 14.3 - 11.75 = 1.55 seconds. Drop .05 for the momentary excursion, and it is over-g for about 1.5 seconds.

Cripes... your own data.

I see you are continnuing to attempt to excuse your rambling personal attacks and hissy-fits based upon your chosen context shift.

"Rambling"??

My statement has been simple from the start.
"The data is the videos.
Calculations from the data are analysis."

10 words.
"Rambling" in the femr dictionary?

"Personal attack"??

I made no mention of you in those 10 words. The same definitions apply to everyone.

I'll say it again. You've simply made it clearer & clearer throughout this little spat.

You don't know the difference between data and analysis.

Why don't you try to define the crucial, functional difference between the two.

After you try (& fail), I'll explain it to you.

This should be good...
 
Last edited:
I understand the little deception you play to hide scatter in the displacement data (setting the top of the displacement to 0 instead of +10, thereby hiding data excursions above the 0 axis.)
ROFL. A close-up...


You will notice that all of the data in the time segment of the graph you are "questioning" is below the zero line in the graph above.

You will note that none of the data is anywhere near +10, nor is any of the data after the 3s mark above zero. You will not that the graph you are "questioning" does not start until the 11s mark.

Given that you have the data it is abundently clear that you are deliberately making up crap.

I understand the simple error that you make in your legend (identifying the red line as "raw trace data". It ain't. It's filtered data.)
ROFL. What filtering, tfk ? (There is a process applied to the data, which you should know, but I'd still class the data as raw.)

So, what filtering, tfk ? :)

I understand the mistake that you make in setting the acceleration of gravity to -32.2 ft/sec^2 for all time.
Not a mistake in the slightest. Believe it or not the "acceleration of gravity" is constant in a particular location, for all time (cosmic events notwithstanding) :rolleyes:

The reason for its inclusion should be obvious for anyone of modest intellect.

The graph is supposed to be comparing the acceleration that the north wall would have had if it collapsed at free fall.
Incorrect. The graph is showing the acceleration behaviour of the NW corner relative to the displacement curve of the NW corner.

North Wall ? ROFL. Have you not learned anything from previous discussions ? The data is for the NW corner, not the entire north wall. NIST make that same inept mistake when they assert their poor quality trace data applies to the entire north wall, not just the wandering point around the roofline area they traced.

Well, it's acceleration would have been zero, not -32.2 ft/sec2, right up to the moment of release (t0). Which on your graph, was about 11.8 seconds or so. Before that time, the acceleration should be zero.
ROFL. As indicated above, anyone with modest intellect should be able to determine the purpose of the "freefall" line.

All of the above are little nits. Errors. Sloppiness. But nits, nonetheless.
All of the above from you is nonsense.

You know exactly what is wrong with that label
ROFL. How very petty. Good back-pedal though :rolleyes:

Your graph shows >g acceleration for virtually the entire time between 12.75 & 14.3 seconds. With a momentary sub-g excursion around 13.75 seconds.
If you're applying zero error potential. I'd suggest 12.75s to 13.75s is a more reasonable over-g estimation.
 
Last edited:
"LMAO", indeed.

You're "graphically illiterate". And now you appear to have crossed a line that I hadn't seen you cross before: into fraudulence.

And for what? To win some stupid, insignificant point…?!



ROFL. A close-up...
43578164.jpg


You will notice that all of the data in the time segment of the graph you are "questioning" is below the zero line in the graph above.

You post this data as though the red line represents the same data posted in the previous graph.

And yet, it clearly is not.

That's fraudulent.

In the new graph, between 11.4 & 11.7 seconds, the data oscillates around a median of about -1.1 ft. Between 11.8 & 12.3, it oscillates around a median of about -0.8 ft.

And yet, in the graph under discussion, there is a clear & obvious red line shown between 11.8 seconds and 12.3 seconds (for the smaller absolute value), and no line between 11.4 & 11.7 sec (for the larger absolute value).

447669743.jpg


Computers don't make this sort of error.

If this were the same raw data, and the cause were merely pixel averaging, then the situation would have been reversed: a line between 11.4 & 11.7 sec, and no line between 11.8 & 12.3 sec.

The only explanation is that the original graph is filtered data and the graph that you posted as "a blow up of the same data" is either unfiltered, or differently filtered data.

In other words, it's not the same data, merely enlarged.

In other words, you chose to intentionally mislead, to not post a blow up of the same data, but to swap the data to win a debating point.

In other words, you lied.

Your credibility is in a uncontrolled dive.

You will note that none of the data is anywhere near +10, nor is any of the data after the 3s mark above zero.

You're illiterate.

Try reading what I wrote again. Feel free to mouth the words, if that helps. A dictionary might be a useful tool, as well.

Show me anywhere that I said the data reached +10. You won't find it. Because I never suggested it.

Now try setting the maximum value of your graph to 1, or 2, or 3, or 5, etc.
Then try setting it to +10.

Notice the difference in the vertical scale numbers.

Given that you have the data it is abundently clear that you are deliberately making up crap.

What is abundantly clear is that you are both graph illiterate & English illiterate.

I guess consistency could be considered an asset…

ROFL. What filtering, tfk ? (There is a process applied to the data, which you should know, but I'd still class the data as raw.)

You really look pretty damn stupid, rolling around on the floor after brain-dead comments like this.

A "process is applied to the data"…
Yeah, a process called "a filter".

Which means - BY DEFINITION - that the result is NOT "raw data".

So, what filtering, tfk ?

LoL. The filtering that you applied to the raw data, ya liar.

Not a mistake in the slightest. Believe it or not the "acceleration of gravity" is constant in a particular location, for all time (cosmic events notwithstanding)

Yup, G is a constant. Nobody with a double digit IQ has suggested otherwise. Ergo, it is single-digit IQ-worthy to publish that worthless little factoid.

An interesting & potentially meaningful point would be how some point on the building really fell compared to a point on a building that really fell at free fall.

But, then again, you & "meaningful" seldom cross paths, do ya.

The reason for its inclusion should be obvious for anyone of modest intellect.

Yep, it is abundantly clear.

You don't know how to present data in a meaningful manner.

You probably don't know how to generate a step function in Excel either.

North Wall ? ROFL. Have you not learned anything from previous discussions ? The data is for the NW corner, not the entire north wall.

Yeah, I (and just about everyone else) has learned that you are utterly incompetent at labeling your graphs. If someone doesn't understand your graphs because you don't label them, you've got nobody but yourself to blame. If you knew the slightest thing about publishing tech data, you'd know that.

Furthermore, have you not learned that people who DO understand chart & graphs & numbers & engineering (i.e., people who work with them professionally, on a daily basis, people like me) don't give a flying fart about your meaningless graphs.

Precisely because you are so abysmally incompetent at presenting anything. Augmented by the fact that you are so intentionally deceptive.

Your credibility fell at supersonic speed.

NIST make that same inept mistake when they assert their poor quality trace data applies to the entire north wall, not just the wandering point around the roofline area they traced.

You will, of course, present NIST's own words where they make this error.

Of course.

femr's intentional deceptive quote-mine said:
You know exactly what is wrong with that label
ROFL. How very petty. Good back-pedal though

Perfect example of your misquote, twisting words, aka "lying".

Meanwhile, the point of my post - that you don't what the hell a "displacement vs. acceleration" graph looks like.

Care to hazard a guess?

Or are you just going to dance, and dance, and dance…?
___

As to your ability to read your own data …

tfk said:
Your graph shows >g acceleration for virtually the entire time between 12.75 & 14.3 seconds. With a momentary sub-g excursion around 13.75 seconds.

If you're applying zero error potential. I'd suggest 12.75s to 13.75s is a more reasonable over-g estimation.

"… applying zero error potential" ??

"… APPLYING ZERO ERROR POTENTIAL"????

:dl: :dl: :dl:

Does that techno-gibberish sound all science-y to you?

I will HAPPILY accept this statement of yours as a demonstration of your ability to assess ANY technical issue.

The fundamental difference between what we are saying is that I said that your graph states over-g acceleration between 13.75 and 14.3 seconds.

And your claim that the over-g acceleration stops at 13.75 seconds.

447669743.jpg


Yup, I'll accept that as a demonstration of your ability to read graphs.

It's no wonder that your so totally incompetent at all of this.

Incompetent as a result of your "applying zero error potentials", no doubt…

:dl: :dl: :dl:
 
You're "graphically illiterate". And now you appear to have crossed a line that I hadn't seen you cross before: into fraudulence.
I'm afraid the problem is your own ineptitude and personal incredulity.

And for what? To win some stupid, insignificant point…?!
Oh, the irony...

You post this data as though the red line represents the same data posted in the previous graph.
It is the same data.

And yet, it clearly is not.
Incorrect.

That's fraudulent.
Incorrect. It is the same data.

In the new graph, between 11.4 & 11.7 seconds, the data oscillates around a median of about -1.1 ft. Between 11.8 & 12.3, it oscillates around a median of about -0.8 ft.

And yet, in the graph under discussion, there is a clear & obvious red line shown between 11.8 seconds and 12.3 seconds (for the smaller absolute value), and no line between 11.4 & 11.7 sec (for the larger absolute value).
The data is truncated to start at T0.

Computers don't make this sort of error.
It's not an error.

If this were the same raw data
It is.

and the cause were merely pixel averaging
It's not.

then the situation would have been reversed: a line between 11.4 & 11.7 sec, and no line between 11.8 & 12.3 sec.
Gibber.

The only explanation is that the original graph is filtered data and the graph that you posted as "a blow up of the same data" is either unfiltered, or differently filtered data.
Incorrect. It is the same data. You have the data :rolleyes:

In other words, it's not the same data, merely enlarged.
Incorrect. It is the same data.

In other words, you chose to intentionally mislead, to not post a blow up of the same data, but to swap the data to win a debating point.
Incorrect. It is the same data.

In other words, you lied.
Incorrect.

Your credibility is in a uncontrolled dive.
LMAO.

A "process is applied to the data"…
Yeah, a process called "a filter".
That's right, as I said, a process is applied (which you should know from prior discussion). As your memory seems rather flawed, I'll tell you...

Dejitter, via adjacent sample averaging. Applied to treat the alternate sample oscillation which results from joining two separate traces for each field of the interlaced frame together. Given that other views are Poly(10), Poly(50) and Savitzky-Golay smoothed, it's a trivial process and the data is still raw imo, how ever much of a hissy-fit you may have about that.

Which means - BY DEFINITION - that the result is NOT "raw data".
Yawn.

An interesting & potentially meaningful point would be how some point on the building really fell compared to a point on a building that really fell at free fall.
No, not interesting at all. And you produced such a graph several months ago. If I recall, there was some laughter at your step function graph :rolleyes:

Furthermore, have you not learned that people who DO understand chart & graphs & numbers & engineering (i.e., people who work with them professionally, on a daily basis, people like me) don't give a flying fart about your meaningless graphs.
Your inept errors aside, you appear to be doing a good impression of someone who DOES "give a flying fart about my graphs" :rolleyes:

You will, of course, present NIST's own words where they make this error.
Sure...

  • In Stage 1, the descent was slow and the acceleration was less than that of gravity. This stage corresponds to the initial buckling of the exterior columns in the lower stories of the north face, as seen in Figure 12–62. By 1.75 s, the north face had descended approximately 7 ft.
  • In Stage 2, the north face descended at gravitational acceleration, as exterior column buckling progressed and the columns provided negligible support to the upper portion of the north face. This free fall drop continued for approximately 8 stories (105 ft), the distance traveled between times t = 1.75 s and t = 4.0 s.
  • In Stage 3, the acceleration decreased somewhat as the upper portion of the north face encountered resistance from the collapsed structure and the debris pile below. Between 4.0 s and 5.4 s, the northwest corner fell an additional 130 ft.

Of course.

Meanwhile, the point of my post - that you don't what the hell a "displacement vs. acceleration" graph looks like.

Care to hazard a guess?
ROFL. I'd theorise it mayhap be one wot does not have a time axis, but then you'd have to be a particular brand of pedant to be making such a pointless quibble, really :rolleyes:

Or are you just going to dance, and dance, and dance…?
It's statements like this that really show your intellect, tfk. Dance ? To what ? :rolleyes:

your claim that the over-g acceleration stops at 13.75 seconds.
I think that's a reasonable assertion, sure. The graph is not 100% accurate you know. There's some noise and error in there. Did you not know that ? :rolleyes:
 
F2, it's ok to admit you're wrong from time to time. It makes you a better person.
 
F2, it's ok to admit you're wrong from time to time.
Is there some part of the post above you think is relevant to your statement ?

Whilst I'm here, a view of the data tfk is having a hissy-fit about and claiming that the zoomed-out view is showing a different dataset than the zoomed-in view...

499166077.gif


598144612.gif


(tfk has the actual data, so there's no excuse for his inept assertions)
 
F2, it's ok to admit you're wrong from time to time. It makes you a better person.
He's not actually wrong. His analysis of the data (that was the same as NIST's) was done for a different purpose. NIST was showing a trend (that they saw as unimportant) and femr2 was trying to extract more points to show he could do so. NIST did what they did to satisfy their need. femr2 did the same, extract more points. Who's better? Depends, do you want more points or a conclusion drawn from this.

As far as resolution from the data, femr2 has it all over NIST. If you go for conclusions, NIST actually has one, need i say more?
 
Let's keep the discussion civil please.
Replying to this modbox in thread will be off topic  Posted By: Gaspode
 
Some posts moved to AAH.

As previously stated please keep discussion civil. Or suspensions may follow. Thanks.
Replying to this modbox in thread will be off topic  Posted By: Gaspode
 
As civil as can be...

I agree that you did not swap the data sets.

But you did not post curves with the same data. Here are the two curves that you have stated repeatedly were the same data set.

picture.php


One has data between 11.4 & 11.8 seconds. The other one does not.

QED. They aren't the same data set.

As a result of your posting different data sets, but saying that they were the same, it APPEARED that you substituted data.

I accept that you did not.
___

Raw data vs. calculations.

The only true raw data available is pixels vs. frames, i.e., original videos. A reasonable argument can be made for pixels vs. time, since the frame rate is controlled so carefully.

All other data (including displacement, velocity & acceleration) are derived from analyses. As such, they are only as good, only as trustworthy as the analyses themselves. They can easily be wrong, especially when done by amateurs.

The fundamental difference between raw data and derived calculations is that all conclusions must be supported by the raw data.

Conclusions do not need to be supported by calculated quantities until those quantities have been proven to be accurate.
___

Reading your own graphs.

Here is the pertinent part of your acceleration vs time graph.

picture.php


Sabretooth looked at your graph and asked if it showed >G acceleration for "nearly 3 seconds".

You replied:
No. About 1s.

Regardless of any "creative" verbiage (such as "applying zero error potential"), citing the Over-G range as "~1 second" from this graph is a less than competent reply.

"About 1.5 seconds, between about 12.75 & 14.3 seconds" would have been a competent reply.
 
Last edited:
I have repeatedly given femr2 advice that more clearly labeling his charts would be more convincing (if convincing anyone of anything is his goal). He ignores my advice.

Seriously, what in the world could the following graphic accomplish? Who would post this and for what reason?
 

Attachments

  • Picture 7.jpg
    Picture 7.jpg
    30.1 KB · Views: 14
Reading your own graphs.

Here is the pertinent part of your acceleration vs time graph.

[qimg]http://www.internationalskeptics.com/forums/picture.php?albumid=638&pictureid=4935[/qimg]

Sabretooth looked at your graph and asked if it showed >G acceleration for "nearly 3 seconds".

You replied:


Regardless of any "creative" verbiage (such as "applying zero error potential"), citing the Over-G range as "~1 second" from this graph is a less than competent reply.

"About 1.5 seconds, between about 12.75 & 14.3 seconds" would have been a competent reply.

I misinterpreted what each line represented when I asked if it shows ~3 seconds over G.

Either way, it's over G for what I'd consider a significant period of time. I'm a bit lazy this morning...is this data directly from NIST?
 
No, the data was generated by femr.

The data is good.

The interpretation of the data is where the fur starts to fly.

I'll tell you mine. (Good luck at getting femr to tell you his.)

There is nothing the slightest bit surprising, imo, about this acceleration data. But there are a few things to remember.

This is not the acceleration "of the building". It is the acceleration of a point on the north wall. But since the wall did not break up on descent, it is a very close representation of the whole wall, too.

The meme that "free fall acceleration" means demolition is simply wrong when sloppily applied.

The meme that "faster than G acceleration is impossible" is simply wrong when sloppily applied.

The CG of an ISOLATED body cannot fall faster than G.

But there are two conditions in which pieces of a body can fall faster than G: 1) a rotating body, & 2) a body that is not isolated from other forces.

There are also a couple of other instances where a free falling body can appear to fall faster than G, because of poor data resolution, but that's not the case here.

If a large structure buckles near its base over a many floor segment (as WTC7 did), with the buckling resulting in fracturing of connections, then the portion of the structure above the buckled segment will fall very near to free fall. During the time that the buckled segment is folding, no segments of the structure need be destroyed. (It is the destruction of various segments that slows down the descent.)

Alignment is everything to a tall, slender column holding up a load. You can see this by taking a straw. Push straight downward on it, and it'll provide some significant resistance. Now put 3 or 4 creases in the straw. The creases represent fractured connections. Now the straw can offer virtually zero resistance. As soon as the segments get out of vertical alignment, the whole structure can carry no load, even tho each individual segment could hold as much as it did before. The segments can easily fold up without having to crush / collapse the individual segments. It is simply a different failure mode than "crush down".

This easily explains the "near g" portion of this fall.

The external walls of WTC7 were connected at hundreds of points to the interior of the building. The interior of the building began to fall earlier than the external wall. There is no doubt that the external wall was NOT an isolated body.

IMO, it is very highly probable, near certain, that internal segments of the building dragged down the external wall, either directly, or by having heavy debris fall onto some of the lower cross beams that remained connected to the external wall.

This explains the "over G" segment of the fall.

You'll have to get others' opinions from themselves. I'm tired of guessing the opinions of those who won't state them clearly.
 
Last edited:
No, the data was generated by femr.

The data is good.

The interpretation of the data is where the fur starts to fly.

I'll tell you mine. (Good luck at getting femr to tell you his.)

There is nothing the slightest bit surprising, imo, about this acceleration data. But there are a few things to remember.

This is not the acceleration "of the building". It is the acceleration of a point on the north wall. But since the wall did not break up on descent, it is a very close representation of the whole wall, too.

The meme that "free fall acceleration" means demolition is simply wrong when sloppily applied.

The meme that "faster than G acceleration is impossible" is simply wrong when sloppily applied.

The CG of an ISOLATED body cannot fall faster than G.

But there are two conditions in which pieces of a body can fall faster than G: 1) a rotating body, & 2) a body that is not isolated from other forces.

There are also a couple of other instances where a free falling body can appear to fall faster than G, because of poor data resolution, but that's not the case here.

If a large structure buckles near its base over a many floor segment (as WTC7 did), with the buckling resulting in fracturing of connections, then the portion of the structure above the buckled segment will fall very near to free fall. During the time that the buckled segment is folding, no segments of the structure need be destroyed. (It is the destruction of various segments that slows down the descent.)

Alignment is everything to a tall, slender column holding up a load. You can see this by taking a straw. Push straight downward on it, and it'll provide some significant resistance. Now put 3 or 4 creases in the straw. The creases represent fractured connections. Now the straw can offer virtually zero resistance. As soon as the segments get out of vertical alignment, the whole structure can carry no load, even tho each individual segment could hold as much as it did before. The segments can easily fold up without having to crush / collapse the individual segments. It is simply a different failure mode than "crush down".

This easily explains the "near g" portion of this fall.

The external walls of WTC7 were connected at hundreds of points to the interior of the building. The interior of the building began to fall earlier than the external wall. There is no doubt that the external wall was NOT an isolated body.

IMO, it is very highly probable, near certain, that internal segments of the building dragged down the external wall, either directly, or by having heavy debris fall onto some of the lower cross beams that remained connected to the external wall.

This explains the "over G" segment of the fall.

You'll have to get others' opinions from themselves. I'm tired of guessing the opinions of those who won't state them clearly.

That clears it up for me.

Here's my thing, though...why is there such a focus on the behavior of the building after critical failure? Why is this a "red flag" for truthers?

It was an obvious set of unique circumstance that brought down the WTC complex. WTC7 shows signs of probable collapse throughout the afternoon. You can see that the collapse did not initiate at the point where the north face started to descend...heck, the penthouse had disappeared from sight several seconds before the north face began moving downward.

Once that penthouse disappears, the investigation is over. Period. Nobody cares what happened after the building went critical.

It's like trying to predict the pattern of a house of cards falling...and it has nothing to do with why the cards fell.

I see like a math equation of sorts...

a + b + c + d / e2 + n2 = x

Normal people solve for x from a. Truthers are trying to solve x from n2 and ignoring the rest of the equation.
 
You can see that the collapse did not initiate at the point where the north face started to descend...heck, the penthouse had disappeared from sight several seconds before the north face began moving downward.

Exactly right.

This is exactly the point that I was making in this post regarding causes & effects.

Causes precede effects. NIST was supposed to find the causes of the collapses, and therefore their attention was focused on the events that led up to collapse initiation in all 3 buildings. The things that happened once the collapse got underway were irrelevant.

Once that penthouse disappears, the investigation is over. Period. Nobody cares what happened after the building went critical.

I agree with WTC 1&2, but for WTC7 would argue for extending the analysis several seconds beyond the EP collapse.

As soon as the WTC1 & 2 started to collapse, they were doomed. There is no way that the collapse was going to arrest. Bazant was right, no matter how much it cheeses off the truthers.

WTC7 was different. And this is why they had a bit of a problem figuring it out.

It was initially a mystery why the collapse of WTC7 progressed from merely local failure to global failure. In order to do that, they had to (& did) study the progression of failures that led to total collapse, which extended about 7 seconds beyond the collapse of the East Penthouse (EP).

If you look at the chart of the table of the various events, Table 12-2, NCSTAR1-9, vol 2, pg 599 (pdf pg 261), you'll find that the North Wall started to descend at about 6.9 seconds after t0. (Note t = 0 at the start of EP descent.)

This means that OBSERVABLE failures were happening for a total of almost 13 seconds (6 sec before start of collapse of EP + 6.9 seconds after) prior to the start of the collapse of the north face of the building.

Remember, START of north wall collapse = 6.9 seconds.

To relate this to the condition of the interior of the building, look at figures 12-52 thru 12-55. This shows the condition of the interior of the building between 2.5 & 6.5 seconds.

Total collapse is well underway by 2.5 seconds.
picture.php


By 4.5 seconds, the collapse has spread all the way to the west wall (on the upper floors).
picture.php


By 6.5 seconds, the whole interior of the building is well into collapse.
picture.php


About 1/2 second after this, the North wall begins to collapse.

In my opinion, total collapse was inevitable just as soon column 79 went unstable & buckled at about -1.0 seconds (1 second before start of EP descent). (I think it would also have collapsed if columns 80 or 81 had been the first to buckle.)

NIST suggests strong support for this conclusion in Section 12.4.5, where they looked at the results of a similar collapse initiation event (floor collapse) with reduced fire damage. There, column 79 did not buckle, and the building did not collapse.


tom
 
Last edited:
I have repeatedly given femr2 advice that more clearly labeling his charts would be more convincing (if convincing anyone of anything is his goal). He ignores my advice.

Seriously, what in the world could the following graphic accomplish? Who would post this and for what reason?

The same guy that created this:

 

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