Title: Flight Path Submission
Description: for criticism and review.
Description: for criticism and review.
Russell Pickering - October 12, 2006 05:00 AM (GMT)
This is the submission for the near "final" flight path that I have been working on in a trial and error mode. I am providing a link to the layered files so that anybody can download it and test it.
I am also going to provide links to each element of it with brief instructions so that you may also create it from scratch yourself. My goal here is to come to some consensus on its accuracy so that from it other evidence can be analyzed and tested.
There have been errors in my past efforts which have been correctly pointed out. I have tried corrections and posted explanations to no avail. So here it is for those dedicated enough to examine it critically.
A brief history of what this is founded on. JDX one night showed correctly that the flight path would possibly bring the right wing into contact with the VDOT mast which I found to be true if you started at the building and worked backwards.
In my examination of that I discovered damage to the side of that pole. I combined that with corresponding documentation from the VDOT that the glass in front of the camera lens on the camera that was mounted on the pole had been shattered. This documentation was in the form of an Internet article and an in person investigation. You can review that below and make any comments there you wish. Please keep this thread about a flight path graphic which you can download and examine or create from scratch yourself.
http://s15.invisionfree.com/Loose_Change_F...showtopic=15307
The most grievous error was my attempts to overlay the satellite image from 9-7-01 onto a current Google image. Even though it matches in certain respects it was always a little off. After trying to adjust it again I discovered that even though it was closer it was still way off in terms of what I believe is the "working forward" starting point, the VDOT camera mast. I don't know if the current and old satellite images are different resolutions or what. You can acquire the 9-7-01 satellite image in high resolution here: http://www.spaceimaging.com/gallery/9-11/#. Go to 09-07-01 and click on it. Then click where it says, "Download larger image (300 dpi)".
The reason I wanted that image as an overlay is so that we could have the generator and the other objects present on 9/11 in place. The way I have circumvented this issue is to overlay only that small portion of the 09-07-01 image onto a current Google image. The image portion I used is in the file you can download or you can get it from the above link and do it yourself.
The next problem was my attempts to line it up with the mast itself. Because of foreshortening and the angle of the satellite image there was some guesswork that led to errors as well. JDX pointed out the best thing to do was use the center of the base and treat the situation as flat. That worked.
The steps are like this:
1) Go to Google Earth and acquire the image area you want around the Pentagon.
2) Zoom in on the VDOT mast and go to the "tools" menu and then to "measure". Bring up the measuring tool. Select "path" and put a single red dot in the middle of the VDOT mast base. Then switch to the line tool. Find a relatively flat area like I did in the cloverleaf. Zooming in fairly tight and turning of the "terrain" feature is what Google recommends for the most accurate measurement. Make a line that represents the wingspan of a 757 - 124' 10". Close the measuring tool.
3) Then back out to the original area selected. Make sure you have true north as the orientation and save this image to your computer. In the download file I have provided the compass and the aircraft.
The compass can be acquired below and will need to be re sized and/or cropped for use. http://images.google.com/images?q=compass&...G=Search+Images
The aircraft can be acquired below and you can cut it out from this diagram. The aircraft cutout I have included is left large on purpose so that you can scale it to your own standards. http://www.airliners.net/info/stats.main?id=101
4) Open all of your elements in a photo program. I use Photoshop CS. Take the Google background and create a vertical guide. Ensure that you have the compass straight up and down as well as centered so that it represents true north as on the Google compass.
5) Then scale the aircraft to the wingspan measurement you created. Create a line using the line tool starting at 61.5 degrees through the reciprocal 241.5 degrees through the dead center of the compass. Center the aircraft on that line. Then move the aircraft so that the wingtip barely touches the VDOT camera mast. I added lines to represent the various parts of the aircraft. Do this by duplicating the line you created in the center of the compass so it is at the 61.5 degrees.
I added the lamp poles too. The best way to do this is to zoom in on Google Earth and locate each pole and then go back to your photo program and put a dot right at the base.
The following is what you should come up with. Download the one I made or create your own and critique it so that we can move forward with it.
Layered files: https://backup.filesanywhere.com/v.asp?v=%8...5Cb%A9%BA%AB%9C
For those that want to inspect the VDOT pole damage here is all of Jason Ingersoll's photos: https://backup.filesanywhere.com/v.asp?v=%8...%95%B2%A9%A3%A7
EDIT: The ones that pertain to the VDOT mast are 0412-0419 but the rest are very good for many other things.
I am also going to provide links to each element of it with brief instructions so that you may also create it from scratch yourself. My goal here is to come to some consensus on its accuracy so that from it other evidence can be analyzed and tested.
There have been errors in my past efforts which have been correctly pointed out. I have tried corrections and posted explanations to no avail. So here it is for those dedicated enough to examine it critically.
A brief history of what this is founded on. JDX one night showed correctly that the flight path would possibly bring the right wing into contact with the VDOT mast which I found to be true if you started at the building and worked backwards.
In my examination of that I discovered damage to the side of that pole. I combined that with corresponding documentation from the VDOT that the glass in front of the camera lens on the camera that was mounted on the pole had been shattered. This documentation was in the form of an Internet article and an in person investigation. You can review that below and make any comments there you wish. Please keep this thread about a flight path graphic which you can download and examine or create from scratch yourself.
http://s15.invisionfree.com/Loose_Change_F...showtopic=15307
The most grievous error was my attempts to overlay the satellite image from 9-7-01 onto a current Google image. Even though it matches in certain respects it was always a little off. After trying to adjust it again I discovered that even though it was closer it was still way off in terms of what I believe is the "working forward" starting point, the VDOT camera mast. I don't know if the current and old satellite images are different resolutions or what. You can acquire the 9-7-01 satellite image in high resolution here: http://www.spaceimaging.com/gallery/9-11/#. Go to 09-07-01 and click on it. Then click where it says, "Download larger image (300 dpi)".
The reason I wanted that image as an overlay is so that we could have the generator and the other objects present on 9/11 in place. The way I have circumvented this issue is to overlay only that small portion of the 09-07-01 image onto a current Google image. The image portion I used is in the file you can download or you can get it from the above link and do it yourself.
The next problem was my attempts to line it up with the mast itself. Because of foreshortening and the angle of the satellite image there was some guesswork that led to errors as well. JDX pointed out the best thing to do was use the center of the base and treat the situation as flat. That worked.
The steps are like this:
1) Go to Google Earth and acquire the image area you want around the Pentagon.
2) Zoom in on the VDOT mast and go to the "tools" menu and then to "measure". Bring up the measuring tool. Select "path" and put a single red dot in the middle of the VDOT mast base. Then switch to the line tool. Find a relatively flat area like I did in the cloverleaf. Zooming in fairly tight and turning of the "terrain" feature is what Google recommends for the most accurate measurement. Make a line that represents the wingspan of a 757 - 124' 10". Close the measuring tool.
3) Then back out to the original area selected. Make sure you have true north as the orientation and save this image to your computer. In the download file I have provided the compass and the aircraft.
The compass can be acquired below and will need to be re sized and/or cropped for use. http://images.google.com/images?q=compass&...G=Search+Images
The aircraft can be acquired below and you can cut it out from this diagram. The aircraft cutout I have included is left large on purpose so that you can scale it to your own standards. http://www.airliners.net/info/stats.main?id=101
4) Open all of your elements in a photo program. I use Photoshop CS. Take the Google background and create a vertical guide. Ensure that you have the compass straight up and down as well as centered so that it represents true north as on the Google compass.
5) Then scale the aircraft to the wingspan measurement you created. Create a line using the line tool starting at 61.5 degrees through the reciprocal 241.5 degrees through the dead center of the compass. Center the aircraft on that line. Then move the aircraft so that the wingtip barely touches the VDOT camera mast. I added lines to represent the various parts of the aircraft. Do this by duplicating the line you created in the center of the compass so it is at the 61.5 degrees.
I added the lamp poles too. The best way to do this is to zoom in on Google Earth and locate each pole and then go back to your photo program and put a dot right at the base.
The following is what you should come up with. Download the one I made or create your own and critique it so that we can move forward with it.
Layered files: https://backup.filesanywhere.com/v.asp?v=%8...5Cb%A9%BA%AB%9C
For those that want to inspect the VDOT pole damage here is all of Jason Ingersoll's photos: https://backup.filesanywhere.com/v.asp?v=%8...%95%B2%A9%A3%A7
EDIT: The ones that pertain to the VDOT mast are 0412-0419 but the rest are very good for many other things.
johndoeX - October 12, 2006 06:12 AM (GMT)
True course is still off a few degrees.
The impact hole doesnt match up with your first impact points. This new path is a few windows north.
If the Gen and impact hole lined up with the first, it no longer lines up with this final.
I dont see an American Airlines 757 hitting the building in any of your pictures/flight paths.
The impact hole doesnt match up with your first impact points. This new path is a few windows north.
If the Gen and impact hole lined up with the first, it no longer lines up with this final.
I dont see an American Airlines 757 hitting the building in any of your pictures/flight paths.
johndoeX - October 12, 2006 06:13 AM (GMT)
A reminder...
| QUOTE |
| Conclusion 1: The angle of approach, 42º, proposed by the Report, is impossible for a Boeing 757 because of the locations of the single hole in the fence and the intact overhead signs and lampposts on the motorway. The only possible trajectory is difficult to reconcile with the Report's information on the tilt of the aircraft at the moment of impact. |
| QUOTE |
| Conclusion 2: The Report is able to present no rational support for its claim that the right engine's hitting a generator might explain why the outermost part of the right wing never hit the wall of the Pentagon |
| QUOTE |
| Conclusion 3: The cable spools show that the builing could not have been hit by an aircraft with dimensions similar to those of a Boeing 757 at a vertical position indicated by the Report. |
| QUOTE |
| Conclusion 4: No support is forthcoming for the claim in the Report that the left engine hit something prior to making contact with the facade. Also no justification is given in the Report for the allegation that such a hit could even in principle explain why the outermost part of the left wing never hit the building. |
| QUOTE |
| Conclusion 5: The Report's description of the interaction of the aircraft with the second-floor slab has no physical credibility. |
| QUOTE |
| Conclusion 6: The impact damage to the facade on the right side of the entry point of the fuselage does not correspond to the size, shape and position of the alleged Boeing 757 presented in the Report. |
| QUOTE |
| Conclusion 7: The facade damage to the left of the entry point of the fuselage is not suggestive of an impact by a B-757. |
| QUOTE |
Conclusion 8: The absence of any kind of damage by the aircraft's tail excludes the possibility of a hit by a B-757. |
| QUOTE |
| Conclusion 9: The Report is not able to explain the hole in the inner wall of Ring C with the story of a crash of a Boeing 757 |
| QUOTE |
| Final Conclusion The Pentagon Building Performance Report by the American Society of Civil Engineers fails in its attempt to show that the structural damage caused to the Pentagon on Sept. 11, 2001 was caused by a crash by a Boeing 757 aircraft. Belief in the official B-757 story implies belief in physically impossible and inexplicable phenomena. More generally, no proof of the return of Flight 77 to the Washington area has been presented. On the contrary, e.g. any security camera recordings that would really show what hit the Pentagon have not been made public. (In May 2006, two series of still photos from security cameras were released, but they contain no evidence of a Boeing 757. See www.flight77.info and www.judicialwatch.org/flight77.shtml.) The most natural explanation for the numerous errors in the Report is that it is a part of the disinformation campaign by the US authorities - the purpose of which is to prevent the truth regarding 9/11 from being revealed and thus to protect the perpetrators of those atrocities. |
This last conclusion makes ALOT of sense. "Disinformation campaigns containing numerous errors."
This site does it the right way. They took a govt report and went from there.