29 July, 2007

911 - weird airplane hitting tower



Funny looking aeroplane, isn't it?

for more info go here:
http://u2r2h.blogspot.com/2006/08/911-tv-fakery.html


original video:




THIS RESEARCH IS MUST_READ!!
taken from http://www.acebaker.com/9-11/ABPlaneStudy/Chopper5Velocity2.html
please check there for an up-to-date version! Or go to:
http://911scholars.org/ because the stuffy professors are finally coming to realize the fact of TV fakery... and they find it, would you know, "disturbing".



Chopper 5 Composite

An analysis of the live WNYW (Fox 5) helicopter video of UA Flight 175 striking the World Trade Center

source Chopper 5 video excerpt (640 x 480 .mov)

full segment (320 x 240 .mov)

Abstract

The WNYW "Chopper 5" video of UA flight 175 flying into the World Trade Center which aired live on 9/11 must be a video composite. The moving plane image must have been recorded separately from the image of the twin towers.

Accoring to Newton's first law of motion, an approaching airliner flying through air will "keep on doing what it's doing". That is, the airplane is either travelling a constant speed, accelerating or decelerating. It cannot speed up and slow down repeatedly. Plotting velocity as a function of time, the approaching airplane must present a smooth line on the graph. Constant velocity would be a straight horizontal line.

The apparent velocity of a jetliner on video can be contaminated by various noise factors including atmospheric interference, video compression artifacts, and, most importantly, camera motion. Simply moving the camera while recording can cause any object to appear to speed up, slow down, stop, go backwards, etc. Being on a helicopter, and also being controlled by an operator, the chopper 5 camera is never still. Rather it moves around, mostly to the left, but also up, down, and to the right. These camera movements appear to be quite smooth, for the most part.

The raw video depicts rapid increases and decreases in velocity of up to 186 mph (a jagged line on the graph), which is assumed to be caused by some combination of noise factors, especially including camera movement, because atmospheric disturbances and video compression artifacts do not appear sufficient to explain the magnitude of such deviations.

Besides the moving airplane, this video contains stationary reference objects, the twin towers. Stabilizing the video effectively removes camera movement from the raw clip. If the variations in apparent velocity were caused by the observed camera movement, stabilization could only have the effect of reducing the apparent fluctuations in airplane velocity (straightening out the jagged line). However, the opposite occurs. Stabilizing the video has the effect of amplifying and randomizing the apparent velocity changes. The line on the graph becomes even more jagged. Other noise factors are judged to be insignificant, so these data are explained by camera motion on the plane, camera motion not present on the twin towers, thus not removed during the stabilization process.

After a 0.3 second disappearance inside the tower, what appears to be the nose of the aircraft exits the building, apparently now coming from behind the tower. Although travelling much slower than the approaching airplane, this "nose cone" also appears to accelerate and decelerate repeatedly. The stabilization process again fails to smooth out the jagged velocity data, and introduces a noticeable spike at frame #41.

Frame #7 shows evidence of having been edited and "painted" around the nose of the aircraft. All of the frames, including #7, show the area behind the engines to be more pink than the surrounding sky.

In an authentic video, these anomalies are not easily explained. However, they can be explained in terms of well-known video layering techniques. The simplest explanation for the data is that the airplane was recorded seperately from the towers, and had its background removed (sloppily on frame #7). This airplane recording had unstable camera motion which introduced the variations in velocity. The observed camera motion in the Chopper 5 twin towers video was negligable by comparison.

The analysis technique used here generates falsifiable predictions. If valid, the same technique used on authentic stabilized videos of comparable quality will produce stable velocity graph lines. Testing, I find that indeed comparable videos do produce very stable graph lines. These are presented as control cases, the predictions are not falsified, and serve to quantify the overall margin of error. Margin of error <>

Introduction

The planes of 9/11 remain a hotly controversial topic within the 9/11 truth movement. Even among those who all readily agree that 9/11 was an inside job, some think real planes were used, while others assert that the plane crashes witnessed by millions on tv were "video fakery".

The "Chopper 5" video aired live on 9/11. It is the live shot which came the closest to actually showing the impact of the plane into the tower, although it did not. In actuality, all of the live "plane impact" videos showed the plane disappearing behind the tower.

After analyzing various videos, researchers such as Gerard Holmgren, Rosalee Grable (aka the Webfairy), StillDiggin, CB_Brooklyn, Killtown and Morgan Reynolds have concluded that Boeing passenger aircraft did not strike the twin towers as widely reported. This is based upon several mutually supporting lines of evidence and reasoning:

  • In various videos, including the so-called "ghostplane" video, the Boeing 767 appears to penetrate the outer wall of the south tower effortlessly, without crashing, breaking, bending, twisting, or even slowing down (see Rajter 2006). Frames taken during the penetration show no damage to the aircraft at all, nor to the wall of the building (see Grable).
  • Two different videos appear to show flight 175 approaching from two decidedly different angles through 3D space. (see StillDiggin 2006)
  • In several videos, a brief bright flash appears at the tip of the aircraft nose, just prior to entering the building.
  • In the WNYW "Chopper 5" video, a wide angle shot fails to depict flight 175, at a time and place when flight 175 should be in the picture. (see StillDiggin 2006)
  • In the "Chopper 5" video, which aired live, what appears to be the nose of the airplane exits out the opposite (north) side of the south tower, at about the 89h floor, followed by a quick fade down to a black picture.
  • In at least one other video, which did not air live, a similar, silvery cone-shaped object appears to exit the north face of the building, at about the 89th floor, afterwards it is consumed by a flame. This flame is a distinctly yellower, lighter color than the other, more orange parts of the "fireball". (see StillDiggin 2006)
  • In another video, which did not air live, smoke exits the north face of the building, at about the 89th floor, and does not look at all like the nosecone of an aircraft. (see StillDiggin 2006)
  • In the Naudet brothers video, which is the only video to capture the north tower strike with any appreciable resolution, the object which strikes the tower does not appear to be the shape of a Boeing 767, and is not large enough to be a Boeing 767, and creates explosions in the pattern of an "N" rather than a straight line as would be expected. (see Grable)
  • Both towers exhibit a nearly "plane shaped" hole punched clear through the outer walls. It is argued that passenger aircraft, which are mostly lightweight aluminum, could not and would not penetrate the dense grid of steel columns and reinforced concrete floors so completely. Instead, it is thought that on impact a passenger aircraft would break up, large parts would bounce off and fall to the ground. Recall that Newton's third law of motion states that for every force there is an equal and opposite force. Whatever force is felt by the wall, would also be felt by the much weaker aircraft (see CB_Brooklyn).
  • Accepting the overall "inside job" hypothesis, powerful arguments have been advanced that the perpetrators would never risk using real planes (see Holmgren and Killtown).

Other researchers in the 9/11 truth movement have argued in favor of real planes. Steven Jones has opined that there is "hard evidence" to support real planes, and cites the "swaying of the tower", multiple videos, and eyewitnesses. Video engineer Eric Salter has authored a paper in support of real planes, published in Jones' Journal of 9/11 Studies. (see Salter 2006) This came after Salter's email debate on the subject with Gerard Holmgren (see Holmgren/Salter debates).

Premise

If real, flight 175 can be presumed to exhibit one of three velocity patterns as it approaches the tower:

  • holding a constant velocity (most likely)
  • accelerating
  • decelerating

Given Newton's first law of motion, it is simply not possible for an aircraft flying through air to speed up and then slow down within the short (Wikipedia on Newton). There would be no real-world mechanism to explain such behavior. Speeding up and slowing down repeatedly would be thoroughly ridiculous.

Plotting velocity as a function of time, a constant speed would appear as a straight horizontal line on the graph. Acceleration would appear as an upward sloping line, deceleration as a downward sloping line.

I shall rely on the following two facts to propel this investigation:

  • Any amount of camera motion at all is going to affect apparent velocity, by the exact amount, and in exactly the opposite direction as the camera movement.
  • Any such video containing camera motion, and also depicting objects known to be stationary, may be stabilized, and then anaylzed as if it had been recorded with no camera motion.

Objective

Analyze and interpret the velocity of UA flight 175 on approach to WTC2, and the nose cone-shaped "debris" which exited WTC2, as recorded by "Chopper 5".

Methods

Obtain Chopper 5 video in 640 x 480, 30 fps format, also obtain two control case airplane videos - one steady, the other with camera shake. Import videos into Image Ready and Photoshop. Increase image size 200%. Derive plane outline using magic wand tool on suitable frame(s). Position plane outline around plane in each video frame, going for best overall fit. Record velocity readings as change in apparent position from previous frame. Save as two copies.

Stabilize video on copy two, shifting each frame until edges of twin towers match vertical red lines. Record velocity readings as above, this time for stabilized video. Crop videos to include flight path and tower.

Create graph, velocity as a function of time, plotting raw data as blue, stabilized data as red.

Make general observations, noting apparent hierarchy of video elements. Offer discussion and conclusions, based on observations, reasoning, and knowledge of video production techniques. Hypothesize. Include discussion of measurement accuracy, frame rate, and any other relevant issues.

Frame Rate

The present study assumes a constant frame rate during recording. If the Chopper 5 video was not recorded with a constant frame rate, or if there are frames missing from the original recording, this entire paper may be dismissed. Specs for standard broadcast video in the U.S. are given by the NTSC (National Television Standards Committee). A video frame is 480 scan lines tall, and is captured in two passes of 240 scan lines each, first the "odd numbered" scan lines, then the "even numbered" scan lines. Each of these passes is known as a "field", and is recorded in 1/60 of a second. One odd numbered field is combined ("interlaced") with one even numbered field to make one video frame. These interlaced frames are then played at a rate of 30 frames per second. (Actually, 29.97 frames per second, but often referred to simply as 30).

Digital video can be played back at any frame rate. Conversion from NTSC standard to digital with a frame rate other than 30 fps will cause loss of some frames. Conversion to a frame rate of 20 per second, for instance, would involve discarding one out of every three frames.

The copy of the the Chopper 5 video used for this analysis is 640 x 480 pixels, and 30 fps. It was originally digitized from a VHS recording by video engineer Eric Salter, who has confirmed that there is no reason to suspect that any frames are missing, nor that the frame rate of the original recording was anything but stable. Even a single missing frame would cause the plane to move approximately 46 pixels, instead of the 23 that is typical. This doesn't happen, so missing frames are ruled out.

De-Interlacing

Converting NTSC video to digital requires de-interlacing. There are a few different ways this may be done. Making a frame out of each field results in twice the number of frames, each frame now being only 240 scan lines tall. To compensate for the resulting "squashed" appearance, the picture can be brought back up to height by simply repeating each line (line doubling). Software can also interpolate between lines. Since there are now twice as many frames, the frame rate would now be 60 fps. To play back the de-interlaced video at 30 fps, every other frame is discarded. Line doubling and interpolation is the de-interlace method used on Chopper 5, as confirmed by Salter. Note that interpolation is only present in the vertical dimension, and would have no effect on apparent horizontal velocity.

Alternatively, NTSC video may be deinterlaced by combining odd-even pairs into single frames. On any video with significant motion, this method produces a "double vision" effect, as two images recorded 1/60 of a second apart are now displayed simulaneously (see this for example). There are no double vision effects on Chopper 5.

Measurement Accuracy and Noise

The motion of a real plane travelling through air is smooth. Changes in velocity are gradual. Plotting velocity as a function of time, a real plane must present a smooth line on the graph. On video, any instability of the velocity must be attributed to "noise" of some sort.

The atmosphere can cause distortions in the apparent position of real objects, as light is reflected and refracted off of particulate matter in the air between subject and camera. This tends to cause wave-like ripples, apparently bending or stretching the subject. No such distortions are observed in the Chopper 5 video, the plane appears rigid. So this type of noise appears insignificant.

Converting video to digital can cause so-called "compression artifacts", as software attempts to reduce file size by making adjacent pixels the same color. This may cause errors when pixels are already simiar. In Chopper 5, the wing tips may reflect sunlight and become close to the color of the sky, and compression may make them the same color. Where contrast is sufficient, such as on the fuselage, tail, left engine, etc. compression would serve to make plane outline more distinct. Though it might erase wingtips, video compression would not tend to alter the overall size or position of the plane.

The most significant potential source of distorted velocity on any "hand held" camera shot is camera motion. Simply moving the camera around can cause the apparent velocity of any moving or stationary object to go crazy.

The smaller a moving object appears in the frame, the less resolution, and the less accurately velocity can be measured. To investigate the margin of error, I present two control cases.

Control Case - Steady Camera

Camera was positioned on tripod roughly 4 miles from the flightpath, approximating Chopper 5 conditions. Flightpath traverses the sky, perpendicular to the line of sight, then is occluded by a large building. Camera was steady. Analysis shows the apparent velocity to be very stable, never deviating by more than one pixel.

Control Case - Camera Shake

Camera was positioned as in previous control case. Camera was gently shaken during recording. Analysis of the raw video shows the apparent velocity to be highly unstable. After stabilizing the video to hold the building motionless, the apparent velocity becomes very stable, never deviating by more than one pixel.

Control Case - Camera Shake - Stabilized

Control Case - Camera Shake - Not Stabilized

These control case videos are comparable to, but of slightly worse quality than, the Chopper 5 video. Thus proof of concept is shown. The control cases demonstrate that apparent airplane velocity on authentic, stable videos at this magnification must be stable to within 1 pixel. Authentic videos of better quality must be even more stable than that.

Unit Conversions

Width of tower = 182 px = 208 feet

Scale = 1.14 feet/pixel

Distance from edge of picture to tower = 392 px = 446 feet

Nose travels from edge of picture to tower in 17 frames = 17/30 of a second

446 feet in 17/30 second = 788 feet / second = 537 mph

Largest variation in apparent velocity = 8 px/frame = 274 ft/sec. = 186 mph

Typical variation in apparent velocity = 5 px/frame = 182 ft/sec = 124 mph

Raw video, click thumbnail for large version


Observations - Raw Video

On first viewing, the video appears to be a typical news helicopter shot, albeit of an extraordinary news event. It originates from WNYW in New York, and is being fed to a local Channel 11 station on the west coast. It appears to be a live helicopter shot of the twin towers, with graphics overlays of the WNYW logo, Channel 11 logo, time, temperature, etc. Studying the Chopper 5 video reveals several curious observations.

The helicopter is over New Jersey, about 4 miles west of the twin towers. Already the "plane crash" at the twin towers is the news story of the year, but evidently the pilot is happy with his location, as the helicopter does not appear to be heading toward the towers at all. The full segment begins with a wide angle shot, then zooms in, almost all the way. After holding this zoom setting for a moment, the camera operator then zooms the rest of the way in. Within 3 frames of this final zoom, flight 175 enters the picture from the right side. This is quite a coincidence in timing. The actual plane impact is not visible, as the south (impact) face of the tower is angled slightly away from the camera. The plane disappears into the building with no apparent damage to itself or the tower, then appears to begin exiting from behind the tower on the opposite side. The video feed (but not the graphic overlay) fades to black very quickly after this.

On one particular frame, frame #7 in my study, the airplane appears to show clear signs of having been edited. Notice the "digital paint" around the nose.

Here is the same frame with brightness and contrast adjusted, and the editing becomes even more obvious. In fact, it appears that a portion of the fuselage, under the tip of the nose, was covered up. Also notice that the air behind the wings is considerably more pink than the background.

On approach, the plane appears to speed up and slow down repeatedly before hitting the tower. We know that the plane cannot speed up and slow down so quickly in reality, according to Newton's first law. However, the apparent changes in velocity could be explained by camera motion. In the Chopper 5 video, the plane travels from right to left, but during this time, the camera angle also pans from right to left, mostly, with a somewhat random action. This would have the effect of reducing the apparent velocity of the airplane, in a somewhat random fashion. Fortunately, the video contains fixed objects, the twin towers, so it is possible to stabilize the video, and then analyze it as if there had been no camera movement to contaminate the motion of the plane.

Stabilized video, click thumbnail for large version
Stabilized wireframe, click thumbnail for large version


Observations - Stabilized Video

Stabilizing the video amplified the instability of the airplane velocity.

The plane appears to speed up and slow down repeatedly. It varies from a maximum of 27 pixels/frame (629 mph) down to a minimum of 19 pixels/frame (443 mph). Upon hitting the tower, the plane appears to slow down drastically. Then, during the entry into the building, it appears to speed up just as drastically.

Following entry the plane disappears inside the tower. The disappearance lasts for 9 frames (.3 sec), after which what appears to be the nose of the airplane begins to exit the opposite side of the building, coming from behind the building. This event has become known as "Pinocchio's Nose".

Pinocchio's nose also appears to slow down and speed up. An initial velocity of 10 pixels/frame (233 mph) is measured, after which the nose decelerates down to 4 pixels/frame (93 mph). Then, it appears to accelerate back up to 8 pixels/frame (186 mph), decelerate again, and accelerate again.

There are two fade-out frames, the first being about 10% faded down, the second about 50% faded down to black. The second fade frame depicts the airplane nose-cone and an explosion flame. This flame appears in front of the airplane nose-cone. The fade-out frames are followed by many frames (about 1 second) of complete black. When the video fades back up to picture, no trace of the plane remains.


Conclusions and Discussion

The Chopper 5 video is a composite. The video of the plane must have been shot separately from the video of the twin towers. In both the raw and stabilized versions, the plane appears to accelerate and decelerate, repeatedly. This is an impossible feat in reality, and is explained as camera motion affecting the apparent velocity. This camera motion is present on the plane, and is amplified on the stabilized video which holds the towers motionless.

On a legitimate video, stabilizing the video frames could only serve to stabilize the motion of the plane, straightening out the jagged graph line, as in the camera shake control case. The fact that the opposite occurs is proof that the apparent motion of the plane was influenced by camera movement, camera movement not present on the twin towers. The camera motion on the twin towers was insignificant by comparison.

In a real crash, a plane could not possibly accelerate while entering the tower. Yet in this video, the plane appears to do just that.

"Official" sources state that what appears to be the exiting nose of the airplane is actually "debris". As an exercise, try to identify which ones are noses, and which are debris.

How the debris would form itself into a size and shape indistinguishable from the airplane nose is not clear. Exploding debris would not tend to converge toward a single point. In any event, whether debris or airplane nose cone, it appears to slow down, then speed up, slow down, and speed up again. Other than camera motion, there is no explanation for this behavior. Again, this must be camera motion separate from whatever motion was present in shooting the twin towers, as this motion has been removed from the video.

Frame #7 reveals tell-tale signs of having been "cut-and-pasted". The area around the nose of the aircraft is a different color than the sky, more pink, and pixels around the nose appear to have been altered in what looks to me like the swipe of a digital paintbrush. Perhaps this was an inadvertant mistake, perhaps it was a deliberate clue.

All the other frames have the same kinds of problems. I would venture to say that the plane was recorded on a day when the sky was considerably more pink than it was on 9/11. This subject warrants a study of its own.

CGI vs. Video

Due to the camera motion, the realistic blending of the airplane into the sky, and the sloppy photoshopping (particularly on frame #7), I do not believe this is a computer generated airplane, as others have suggested. Rather, I think it is real video of a real 767. I believe the masterminds of 9/11 chose crystal clear days to carry out their deeds for very important reasons: it is the easiest type of atmospheric condition to repeat, and the easiest on which to remove sky from video. (They may have required a crystal clear day on 9/11 for other reasons as well, see Judy Wood). I suspect that a real 767 was videotaped flying north and banking to the left, then leveling out, on a similar crystal clear day, at around 9 a.m.

On the video which eventually became the overlay for the Chopper 5 video, the plane entered the frame from the right, at around 24 pixels/frame. Camera unsteadiness caused the apparent velocity to fluctuate. The camera began tracking the plane, reducing the apparent velocity down to around 10 pixels/frame, as the plane began to level out. It is this phase that eventually became Pinocchio's Nose.

Multiple videos were made from multiple cameras by multiple camera operators, capturing the flight from a great number of different angles and distances, including helicopter shots from above. The backgrounds from these videos were removed, leaving just a plane flying against a transparency. These multiple videos became overlays for the many "amateur" videos which emerged later.

Locations were then scouted around the twin towers, locations with a view of the towers, which most closely approximated the viewing angles of the 767 flight already recorded. Overlaying the prepared flying plane images onto another video source (live or recorded) is easy, as the background has already been removed.

Chroma Key

It is also possible to remove a particular color from a video source in real time, and make that color become transparent. The technique is known as "chroma key", and has been standard TV studio trickery since the 1960's. One color (usually green or blue, but could theoretically be any color) is chosen as the "key". Two separate video images, A and B, are combined together, with A on top, and B underneath. Any area in video A which is the key color becomes transparent, revealing video B underneath. Everyone has seen chroma key overlay when the TV weathercaster appears to stand in front of a giant satellite map. In reality, she is standing in front of a well-lit green wall, and the satellite map is combined with the live camera shot in the control room.

Luminence Key

Similar in concept to chroma key, but differentiates on the basis of overall brightness instead of color value. Luminence key and chroma key can be used in concert for very specific object identification.

How Did They Create the Chopper 5 Shot?

In creating the illusion of a plane entering a tower, 3 video layers are required (not counting all the TV station logo graphics, which I ignore). The airplane needs to appear in front of the live video, then the world trade center tower needs to appear in front of that. This could have been done one of two ways, "old school" or "new school".

Hypothesis 1 - Old School

The airplane video on transparency "Layer B" is pre-recorded and waiting to go. Live video of the towers is split into two copies, "Layer A" and "Layer C". The sky color is selected as the key color, and Layer A is chroma keyed to remove the sky in real time. The three layers are combined, C on the bottom, B in the middle, and A on top. Thus the airplane is on top of the sky, yet underneath the twin tower.

A careful examination of the the exiting nose cone provides further evidence that this is a composite video, and does not depict an actual real life event. The west wall of the tower is facing us, and the tower is angled so that we can just see a bit of the north wall (to the left). The south wall (to the right) is angled slightly away from us. If the nose cone (or debris, or anything) exited the north (left) wall of the building, in passing it would eclipse our view of the northeast corner. This does not happen. Instead, the nose cone appears to slip out from behind the building, as we continue to see the northeast corner until the explosion flame comes out.

After the nose cone slips into view, smoke and then flame explode out of the building. I suspect this is a genuine explosion from within WTC2. The explosion appears to be in front of the nose. This requires the software to identify the smoke and flame as "keep". That is, the smoke and flame must not be too close to the same color as the sky, otherwise the software would remove the explosion from layer A, and it would appear behind the nose cone. The fade frame is instructive, clearly showing the the flame as being much more yellow than the sky. Also note the smoke as being much more grey, and much darker than the sky. Chroma and luminence keying would have had no problem keeping the flame while continuing to remove the sky from Layer A. The fact that the smoke is nearly the same color as the plane is irrelevant.

Hypothesis 2 - New School

As with hypothesis 1, the flying plane is pre-recorded, with background removed.

Computer software was used to model the twin tower, and mask it off dynamically in real time. The program uses "find edges" to identify the location of the tower in the picture. Again, the crystal clear weather on 9/11 is important, as there were high-contrast boundaries defining the shape of the towers. This, and the fact that the towers were essentially rectangular solids, makes for an easy shape to model.

This is similar technology to the "First and Ten" system by Sportvision that paints a virtual first down stripe on the football field. First introduced in 1998, the software contains a model of the field, is able to "key" on the color of the turf, "painting" the stripe only on the turf and not on the players. Most innovative, the system is able to follow the tilting, panning, and zooming of the camera, and to resize and move the first down stripe accordingly, in real time (see Sportvision site also "Lying with Pixels").

This technique would eliminate the need to chroma key the sky. Rather, it would model the location of the world trade center tower, and erase pixels in real time from the plane layer at all points corresponding to where the tower is.

However, it is not possible to know the shape of the explosion ahead of time. So, it would still require chroma key to identify the explosion, and erase the airplane accordingly, making the airplane appear behind the explosion. If this new school technique were used, it would have been easier to simply mask off the entire picture to the left of WTC2. This would have prevented the nose cone from ever appearing to exit the building. Yet, the nose cone does come out, apparently from behind the tower, just as it would if it were on a seperate video layer from the tower. For this reason, I prefer the "old school" hypothesis as having the greater explanatory power
Bookmark and Share
posted by u2r2h at Sunday, July 29, 2007

0 Comments:

Post a Comment

Links to this post:

Create a Link

<< Home

Locations of visitors to this page Politics Blogs - Blog Top Sites