Why WTC 7 Wasn't Destroyed Using Controlled Demolition on 9/11

Today I am going to go into just a couple pieces of evidence that disproves the claims that WTC 7 was destroyed using controlled demolition.The clip below describes what Dr Judy Wood calls Lather, which was pouring from only one side of WTC 7 throughout the day on 9/11.After hearing what she says, is your mind blown? Mine was, it makes complete sense.Lather Pouring from One Face of Building 7When you can see that Building 7 was slowly disintegrating from the inside, then when you watch it’s silent, freefall collapse, it becomes easier to see that just the shell of the building was left.In order for a building to freefall symmetrically, then the supporting columns need to have been removed. This was happening throughout the day until there was no longer anything supporting or holding up the outer shell of Building 7 and it fell straight to the ground.Now watch the below clip, and notice the lack of explosions prior to collapse, and how quickly and quietly it fell.Did you notice that there were no sounds of explosions that would be easily heard if controlled demolition had destroyed the building. The clip below is of a conventional controlled demolition. Another piece of evidence to support the fact that WTC 7 had been disintegrating and the dust had been pouring from the building up into the sky all day, is the seismic recordings. The clip below explains this.Building 7 was a 47 storey building, and the seismic recording only showed a 2 storey building had hit the ground?? The debris pile of WTC 7The sudden loss of support, lack of explosive sounds just before collapse, the symmetrical collapse, seismic data and the lack of debris (which you can see in the image above), all support that Building 7 turned to dust.The well known theories of Controlled demolition, thermite and mini nukes cannot explain the seismic data, quiet collapse and lack of debris.Leave a commentShare

🔐 Cryptographic Verification

�� CONTENT HASHES: SHA-256: 475a07a7a39c751af0897e35fb6262936560e6797e5940348b9a16e782c02cda BLAKE2b: 5bcdc993102a1da41bfc43265fd63f29d34ccd26b003f0f4248790ae7a29d428 MD5: fe3f7fcbfd3da656bff50614467ce91a �� TITLE HASHES: SHA-256: e1d040925c51b275298143bcf4d50b52d2ae3f29e30142115b7517818a60ef7f BLAKE2b: 656ac27a2beb1b3f7aa0c93699a5bab805a119d6be1596e72ff371f326b39250 MD5: 6dcc6e29c33e5e895d6e676573ccb07f �� INTEGRITY HASHES: SHA-256: 031ff274de578a3ba0e966c3b565120e9ff02fa8765fac38e89f12bd28c47297 BLAKE2b: 3db1bac55258e10e4f9fe957167f0e13621789bcdca0d989dd4a51627a259a4e MD5: 93c4e574e2a038cc231a264a06d7aa92

Archived with ArcHive - Client-side cryptographic archival system