9/11 on Google Earth

[Orphia Nay]

Lyte, pardon the interruption.

If no plane hit the Pentagon, which FDR are you talking about? You stated that professionals from PfT have analyzed the FDR. How so, if no flight crashed?

I need the popcorn eating smilies.

Stop munching so loudly, I can't hear Lyte's reply.

 

[celestrin]

Thanks to SLOB's FOIA request and the acquired CSV files, here's the UA93 flight path for Google Earth 4. If the plane models appear turned/banked/rolled the wrong way, let me know, so that I can upload the inverted version as well. Or update GEarth to 4.0.2737 or later. It seems that some older GEarth versions have roll and pitch properties implemented backwards.

Don't take this as an accurate representation of UA93's flight. It's more a visualization aid for last hard banking manouvers and hitting the ground flying upside down.

In comparison with AA77 data, this set from NTSB does not provide any direct geographic location data. Even DME data is presented only with an accuracy not better than a whole nautical mile, while AA77's DME was presented with 0.1NM accuracy. The only accurate locations in UA93's flight path, that I'm aware of, are the crash site in Pennsylvania and probably the take off in Jersey.

I took the latitude and longitude of the crash site and calculated the path backwards, using ground speed and heading, calculated from drift, magnetic heading and magnetic declination. Calculations are not absolutely accurate, but it's enough for a visualization.

Also included is the final version of AA77 flight. It doesn't provide any new data or visuals, I'd just split the whole path into smaller sections, which can now be "played" individually, either from a top-down view (if played in the "3D models" folder) or by following the plane (if played in the "flight data" folder - that's the view used in the animation below). Since GEarth is not yet able to smoothly follow paths which extend above ground, the option of following the plane looks weird. I had also made plane models clickable and double click brings you to a view right behind the plane. Clickability only works when the "flight data" folder is selected/checked.

If you are annoyed by time display around the plane models, right click on the "flight data" folder, select "Properties", click "Style, color" tab, and select 0% opacity for "Label" property.

Here's the UA93 animation.

http://www.youtube.com/watch?v=a2BNQ3U7qEs

 

[beachnut]

Thanks to SLOB's FOIA request and the acquired CSV files, here's the UA93 flight path for Google Earth 4. If the plane models appear turned/banked/rolled the wrong way, let me know, so that I can upload the inverted version as well. Or update GEarth to 4.0.2737 or later. It seems that some older GEarth versions have roll and pitch properties implemented backwards.

In comparison with AA77 data, this set from NTSB does not provide any direct geographic location data. Even DME data is presented only with an accuracy not better than a whole nautical mile, while AA77's DME was presented with 0.1NM accuracy. The only accurate locations in UA93's flight path, that I'm aware of, are the crash site in Pennsylvania and probably the take off in Jersey.

I took the latitude and longitude of the crash site and calculated the path backwards, using ground speed and heading, calculated from drift, magnetic heading and magnetic declination. Calculations are not absolutely accurate, but it's enough for a visualization.

Also included is the final version of AA77 flight. It doesn't provide any new data or visuals, I'd just split the whole path into smaller sections, which can now be "played" individually, either from a top-down view (if played in the "3D models" folder) or by following the plane (if played in the "flight data" folder - that's the view used in the animation below). Since GEarth is not yet able to smoothly follow paths which extend above ground, the option of following the plane looks weird. I had also made plane models clickable and double click brings you to a view right behind the plane. Clickability only works when the "flight data" folder is selected/checked.

If you are annoyed by time display around the plane models, right click on the "flight data" folder, select "Properties", click "Style, color" tab, and select 0% opacity for "Label" property.

Here's the UA93 animation.

http://www.youtube.com/watch?v=a2BNQ3U7qEs

I thought the plane hit a in a different attitude, I did not have the raw data, I was looking at the graphs. It may be hard to figure out upside down with out following the data. But it looks good and fits as it would. Only truthers have problems with facts. Nice job.

The navigation data would not be good enough to get you closer than 1 or 2 to a few thousand feet to the impact zone. The best thing to do is start at the impact and go back like you did. I think that is what the Pentagon NTSB video was trying to do but they never worked on lining it up better. Because the navigation data does not give the resolution to place the aircrft on a map better than 1 to 2 or even a few thousand feet. Too bad PFT base their whole fraud on a video that is a "working copy" from the NTSB, from a FDR they say did not hit the Pentagon. Pilots for Truth define new standards of dumb logic.

 

[Kryptos]

The two cell phone calls happened at 9:58 am and lasted for ~1 1/2 minutes before they were dropped.

Here is where they took place, as the plane travelled at ~5,000 ft elevation over a smaller mountain ridge (elevations 1500-2000 ft), short of Laurel Hill Summit. Jarrah briefly got the plane back up to ~10,000 ft as it passed over the major mountain ridge, and then it crashed in Somerset County.

Don't have pictures of the smaller ridge (will get some next time I'm by there). But, cell phone towers are always placed at high points, on top of ridges, etc., as is the case at the top of Laurel Hill Summit.

• Higher resolution image of flight path
• Cell phone calls (kml file)
• Altitude profile

 

[Arkan_Wolfshade]

The two cell phone calls happened at 9:58 am and lasted for ~1 1/2 minutes before they were dropped.

Here is where they took place, as the plane travelled at ~5,000 ft elevation over a smaller mountain ridge (elevations 1500-2000 ft), short of Laurel Hill Summit. Jarrah briefly got the plane back up to ~10,000 ft as it passed over the major mountain ridge, and then it crashed in Somerset County.

Don't have pictures of the smaller ridge (will get some next time I'm by there). But, cell phone towers are always placed at high points, on top of ridges, etc., as is the case at the top of Laurel Hill Summit.

http://www.debunk911myths.org/uaflightpath-small.jpg

• Higher resolution image of flight path
• Cell phone calls (kml file)
• Altitude profile

Additionally, cell towers in low population density areas are stronger, as they are fewer and farther apart and handoffs between towers happen less frequently. One of the main problems in making cell calls from planes is the speed, the cell network is not set up to handle such rapid handoffs in succession.

 

[Kryptos]

Additionally, cell towers in low population density areas are stronger, as they are fewer and farther apart and handoffs between towers happen less frequently. One of the main problems in making cell calls from planes is the speed, the cell network is not set up to handle such rapid handoffs in succession.

Most certainly there is a cell tower on top of the smaller ridge, which could have serviced the entire calls. In addition to the spike in aircraft altitude, at that point, the calls tried to hand off to the Laurel Hill Summit tower. That's about how far spaced apart the towers are in this area. Due to speed and increased altitude of the aircraft, the calls were dropped.

 

[celestrin]

I thought the plane hit a in a different attitude
I thought it came in more along that road and perhaps somewhat shallower. Those nasty NWO falsifiers, always falsifying data in an unexpected way. Nobody expects the Spani... um, wait...

The navigation data would not be good enough to get you closer than 1 or 2 to a few thousand feet to the impact zone.
Yea. When I tried to calculate the entire flight path for AA77 from the take off, using only groundspeed and track angle (way back, when only MikeW's CSV was available), the plane overshot the Pentagon. I bet Lyte and Merc will get their panties in a twist after reading this. But then again, such crafty researchers as themselves surely know about this.

Here's a general aviation question - what do various accelerations, recorded in the FDR, actually mean? Are they relative to the plane's frame, or are they absolute (perhaps tied to gyro systems)? Does an upside down flying plane experience negative 1G vertical acceleration? More precisely - would FDR record NEG 1G, if the plane was flying level, but upside down?


The two cell phone calls happened at 9:58 am and lasted for ~1 1/2 minutes before they were dropped.
Yea, and in this light it's also interesting that the auto pilot was disengaged at about 10:00:28 and only then Jarrah manually started the last ascent. Just like if those evil NWO flight data recorder falsifiers wanted to give time for the revolt to start.

 

[Vincent Vega]

Here's some

crap, image wont show.