• Quick note - the problem with Youtube videos not embedding on the forum appears to have been fixed, thanks to ZiprHead. If you do still see problems let me know.

9/11 on Google Earth

celestrin

Thinker
C
Joined
Jun 23, 2006
Messages
173
Here's the AA77 flight path rendering, using PfT's CSV file from aa77fdr.com and MikeW's CSV from 911myths.com. This will probably not be fully operational on anything older than GoogleEarth4. If it is going to work at all.

You mustn't unzip the file, just rename it by removing .zip extension.

PfT's flight path is accompanied with to scale B757 models, courtesy of Dan O., showing pitch, roll and true heading. Models are drawn every 15s for most of the flight, last 7 minutes (autopilot off, the loop manouver) are drawn every second. Models are not switched on as the kmz file loads. One has to manually check the folder "aa77fdr Flight Data" in the list view on the left to make them visible. Since these are models, not icons, one cannot click them to get additional info. There is a workaround, but it'll have to wait for the next implementation. For now, you have to open the folder and click each item as desired. Names show the time at which a particular location was reached.

Latitude, longitude, pitch, roll, true heading, mag heading, CAS, ground speed, track angle and accelerations were taken from the CSV as is, without modifications from my part. Altitude was crudely adjusted for weather, by adding 275ft to CSV pressure altitude data. Of course, under an asumption that PfT CSV's altitude is also pressure altitude as it is in MikeW's. Altitude was then converted to meters and presented in GE as absolute.

For the Comic Book Guys among you - additional 3m altitude were shaved off of flight path for aesthetic resons, so the flightpath stays below the plane models. The center of models is at actual CSV adjusted altitude, path is 3m lower. Popup balloons in GE show actual adjusted altitude. Plane models were gracefully donated by Dan O.

MikeW's CSV flight path is a basic rendering of Lat/Long data after some longitude correction. Since its geolocation resolution is much coarser (1 latitude minute as opposed to about 1 lat second resolution in the aa77fdr CSV), it didn't make sense to include plane models. Likewise, the altitude is taken directly from CSV, without any adjustments and is presented as relative to ground.

I have no idea as to the actual accuracy of lat/long data in either CSV file. Nor GEearth's, though I have a hunch it's more accurate than either FDR data appears to be. Obviously, the plane couldn't've had taken off half a mile south from the runway, as in aa77fdr.com data, let alone 20 miles west from it, as in 911myths data. However, I do believe that after the longitude correction is performed on 911myths version, they are both accurate to within a nautical mile.

But then again, I have no aerospace credentials what so ever. I'm just fascinated with GoogleEarth and I've been living on the outskirts of GIS realm for quite a few years, mainly through web based programing surrounding MapServer software. But no, I don't have any geographical credentials either.

Once again, thanks, Dan O.! Thanks, MikeW! Thanks also to Undertow, I guess (if my memory serves me right, he's the one who got the .fdr file and solicited help for data extraction).

Is there any demand for Pentagon eyewitnesses in GE?
 

Attachments

The best nav data on 77 would be up to 3000 feet off! There is data missing from the FDR. The FDR confirms 77 hitting the Pentagon. Darn, all those liars about DNA, witnesses and planted posts goes up like dustified memories from Judy and Uncle Fetzer.

Are there any truthers with any facts? no

OMG the data shows 77 was right on target to hit at the base of the Pentagon. Too bad PFT can not figure out simple flight path reconstruction and how to match the FDR with where the damaged data begins, therefore missing.

I ran myself down to 57 feet elevation in front of the Pentagon on GoogleEarth, and there is the distance is a jet coming for me, I have seen this before watching landings at the end of the runway. 77 is not very stable but it is an easy job hitting the biggest office building in the world.

Truthers have no ideas about how the FDR works or even what it stores. BTW there are two sets of NAV LAT and LONG stored in the FDR. The truthers show utter lack of knowledge about what they present.

To find the real position of flight 77 you have to use the heading data. The heading data is the most accurate data in the FDR. Pilots must have accurate heading. In the last seconds before impact flight 77 was on a magnetic heading of 70 degrees, and that did not vary more than a degree. When you actually take the data and run the heading back from the impact point witnessed on 9/11 you have the perfect fit with the FDR, witnesses, RADAR DATA tapes, physical evidence, impact damage, impact energy, etc. The impact energy matches the FDR speed for 77. The witnesses when analyzed all match the FDR motion; if the truthers tried they could tell everyone this. Dart even the Radar Data tapes match the FDR flight path. Now as you can see from the data the Lat and Long can not be used to slew the map with the actual aircraft position! The NAV data is only accurate to 3000 feet. Draw a 3000 foot circle around each dot you have and you have the probable position of flight 77 according to the FDR lat and long. Sorry the PFT have no clue or brains when it comes to the truth; PFT is also an ironic name for tall tale liars. Leaving out all the details about each data point from the FDR means you have no viable conclusion for an inside job and essential the PFT are trying to sell DVDs about 9/11 and make money.
 
Last edited:
:bigclap

Great job putting all of this together Celestrin.

Of course, under an asumption that PfT CSV's altitude is also pressure altitude as it is in MikeW's. Altitude was then converted to meters and presented in GE as absolute.
Click to expand...

You can try using PfTs radar altitude instead of PA. It doesnt need any form of correction and it measures altitude above ground level. We've had a discussion about the accuracy of the pneumatic data and how it very likley lags at very high vertical speeds and the fact that the B757 Air Data Computer as well as the Static system isn't calibrated for low-level high speed flight. The lagging is actually evident in PfTs data because corrected PA(corrected for barometric setting and referenced to sea level) is quite a bit higher than the radalt altitude.

I have no idea as to the actual accuracy of lat/long data in either CSV file. Nor GEearth's, though I have a hunch it's more accurate than either FDR data appears to be. Obviously, the plane couldn't've had taken off half a mile south from the runway, as in aa77fdr.com data, let alone 20 miles west from it, as in 911myths data. However, I do believe that after the longitude correction is performed on 911myths version, they are both accurate to within a nautical mile.
Click to expand...

I've made a few posts on this subject as well. The initial entry position for the Flight Management System {FMS} can be up to a mile off in both latitude and longitude, and on airplanes not fitted with GPS(almost all 757s built prior to '99) the initial position is entered via keypad. So its really not a surprise that the position @ IAD was 3000 ft off.

Surely johndoex, or some tr00fer, will claim that if one moves the path to match the departure runway and applies the same correction(ie 900m 015 degrees) to the end of the flight path, you have a plane north of the Citgo somewhere in the vicinity of Lagasses and Brooks alleged flightpath. But, this can't be the case because the FMS automatically tunes navaids and does a little trig and then applies a correction to the lat/long data. It does this fairly often. And this correction is usually "applied" in a smooth manner so that if the airplane is enagaged in LNAV(Lateral Navigation), in which the autopilot flies a path over predetermined waypoints, the airplane won't make an excessive, large correction since the waypoint has essentially moved as much as a mile. Thats also why you don't see a sudden shift in the flight path shortly after departure..

Is there any demand for Pentagon eyewitnesses in GE?
Click to expand...

Thanks for that as well!
 
This is going to get somebody a brand-new corner office in NWO headquarters! ;)
 
Can someone help me understand this? Right now, I barely know what field(s) I'm a layman in regarding this . . ..stuff. I'm also :blush: having a hard time renaming that file. When I right-click and hit rename, it doesn't show the .zip part!

If someone doesn't hold my hand and guide me through this, I'll be forced to assume that it's further NWO obfuscation through The Dark Arts. AND THE SATANISTS SHOVE IT RIGHT IN OUR FACES!!!
 
porch said:
Can someone help me understand this? Right now, I barely know what field(s) I'm a layman in regarding this . . ..stuff. I'm also :blush: having a hard time renaming that file. When I right-click and hit rename, it doesn't show the .zip part!

If someone doesn't hold my hand and guide me through this, I'll be forced to assume that it's further NWO obfuscation through The Dark Arts. AND THE SATANISTS SHOVE IT RIGHT IN OUR FACES!!!
Click to expand...


open windows explorer
click on tools
click on folder options
click on the view tab
Un check the box "hide extensions for known file types"
 
Excellent work, it is very interesting seeing it all laid out like that. This presentation of the flight path totally destroy's Lyte Trip's assertion that eyewitnesses could not have seen AA77 perform it's large turning procedure to burn off altitude. It would have been plainly visible from virtually anywhere.

Couple of things I noticed...

During some of the ascent and descent sections the aircraft nose doesn't appear to reflect the direction, and during the large turn the model of the aircraft is depicted in a port wing down bank, whereas it should be a starboard wing down bank. Could it be the pitch/roll positions are all backwards?

-Gumboot
 
Those are some pretty high quality photos of the Pentagon. Could someone please point out the anti-aircraft missile batteries for me?
 
Crikey, I wish I could run it. Sounds like great work! Thanks, guys.
 
So is that where the FDR data ends, about 1/2 mile SW of the Sheraton?

Also, I see Google Earth has a feature to "play" the file, but it does so from a fairly low altitude, and it doesn't have any way to start in the middle, that I can find, so you have to start out at Dulles. Am I missing something?
 
CurtC said:
So is that where the FDR data ends, about 1/2 mile SW of the Sheraton?
Click to expand...

It would appear so.

Also, I see Google Earth has a feature to "play" the file, but it does so from a fairly low altitude, and it doesn't have any way to start in the middle, that I can find, so you have to start out at Dulles. Am I missing something?
Click to expand...

AFAIK, the only thing you can do is uncheck the 'check-all' box labelled "aa77fdr Flight Data", and manually check the ones you want to see. Additionally you can speed up the fy-to and tour settings. Thats in the tools>options>touring menu. If you wanted to, you could also customize the individual "time plots" by right-clicking on the time and selecting properties and there should be an altitude option in there. I'm not sure but I don't think you can change all of them to a common value.

edit: On second thought, changing the altitude actually moves the object to that altitude. I'm pretty sure there is a setting for the viewing altitude, but I forgot where it is.

edit2: Fingered it out, you can change the viewing altitude by right-clicking the "time plot" > View > hit "reset" button and manually enter the altitude in the "range" field. I tried actually changing the "AA77 FDR CSV's (v2.5)" viewing range instead of doing the individual times, but it doesnt seem to have any effect.
 
Last edited:
You must log in or register to reply here.

Back
Top Bottom