The best site for 911 research

[femr2]

Yes that could cause it during the struggle or at anypoint changeing codes they could have accidentally hit the Mode C which would have stopped the altitude coding

Are you saying that transponder code mode C hit is separate to a mode C hit that would stop altitude coding ?

switching transponders could have caused an issue with the interogation of the transponder, and it could have missed an altitude as far as processing it for UAL175.

How long would the *outage* be expected to be ?

 

[femr2]

If you look at the Flight Explorer release, it shows the last 3 points of UAL175 all at 31 000 feet.

However the distance between the 3rd to last (8.47) and the 2nd to last (8.59) is only slightly more than the difference to the WTC impact point at 9.03. At least how I read it. It took 12 minutes to go from point A to point B, but only 4 minutes to go from point B to point C.

So this suggests either UAL175 massively accelerated to make its rendezvous or the 2nd to last point must be utterly wrong as well.

The FE image doesn't specifically state the final point time, so it's *unknown*.

Will re-check the penultimate point with RADES data. Can't remember how well it matched.

 

[little grey rabbit]

As to the beacon codes, the pilot of UAL175 knows that he has to disappear from the sky at a certain point, and allow flight N175F take his identity.
But he jumps the gun slightly, he changes from 1470 to 3020 before ghost flight N175F had started their beacon 3321. So you get a tiny stretch of 3020 (in green) but looks like less than a minute.

And then for UAL175 its a hey and a ho and a hey-nonny-nonny for Neuschwabenland

 

[little grey rabbit]

The FE image doesn't specifically state the final point time, so it's *unknown*.

Will re-check the penultimate point with RADES data. Can't remember how well it matched.

On the image you show it does.

However, I agree the data is probably fictional, as the point labeled 8.34 is anomalous again.

 

[DGM]

As to the beacon codes, the pilot of UAL175 knows that he has to disappear from the sky at a certain point, and allow flight N175F take his identity.
But he jumps the gun slightly, he changes from 1470 to 3020 before ghost flight N175F had started their beacon 3321. So you get a tiny stretch of 3020 (in green) but looks like less than a minute.

And then for UAL175 its a hey and a ho and a hey-nonny-nonny for Neuschwabenland

It's fun to view "evidence" in a vacuum with no regards for reality, isn't it.

 

[femr2]

On the image you show it does.

Which image ?

The FE flightpath image only states impact time. It doesn't display the point data itself.

 

[little grey rabbit]

Which image ?

The FE flightpath image only states impact time. It doesn't display the point data itself.

In the first image in post 135.

It has been annotated with 4 or 5 time points. These time points don't seem strongly anchored in reality. Quelle surprise when dealing with 911 data.

 

[little grey rabbit]

It's fun to view "evidence" in a vacuum with no regards for reality, isn't it.

It is, not as fun as crashing two military aircraft into tall buildings and blaming arabs, but its still up there and best of all, no one gets hurt!

 

[DGM]

It is, not as fun as crashing two military aircraft into tall buildings and blaming arabs, but its still up there and best of all, no one gets hurt!

Personally, I don't think that would be fun at all.

Why would you dream something like that up (maybe it's a sign of some deep seeded issue)?

 

[Bell]

Little Grey Rabbit, found this already?

Can someone provide the radar and FlightExplorer data that shows the path taken by the airplane that DID crash into WTC2? Since UA175 did not do that, and all...

 

[Oystein]

...
And then for UAL175 its a hey and a ho and a hey-nonny-nonny for Neuschwabenland

This is as clear as truther hypothesises go these days.
Thanks for the enlightment ^^

 

[Cheap Shot]

As to the beacon codes, the pilot of UAL175 knows that he has to disappear from the sky at a certain point, and allow flight N175F take his identity.
But he jumps the gun slightly, he changes from 1470 to 3020 before ghost flight N175F had started their beacon 3321. So you get a tiny stretch of 3020 (in green) but looks like less than a minute.

And then for UAL175 its a hey and a ho and a hey-nonny-nonny for Neuschwabenland

Now I know where you are from, the hole that Alice fell in.

 

[Cheap Shot]

Are you saying that transponder code mode C hit is separate to a mode C hit that would stop altitude coding ?


How long would the *outage* be expected to be ?

Mode C doesn't have a hit, but lots of things could casue a miss of the receiving the altitude for one radar hit or possibly two, one of them being changing codes.

The outage would normally only be one hit, about a 12 second sweep for ARSR's. Other issues come into play one of them being the sort box, I don't think that comes into play here, sort box issues are fairly known at each facility.

 

[Cheap Shot]

Because ARSR's operate ona 12 second sweep, you seem to get involved in it or how it works, if you don't have any data in HOST the center's computer Flight Explorer would show you a blank screen.

 

[Dave Rogers]

Sometimes, juxtaposition is all the debunking that's needed.

As to the beacon codes, the pilot of UAL175 knows that he has to disappear from the sky at a certain point, and allow flight N175F take his identity.
But he jumps the gun slightly, he changes from 1470 to 3020 before ghost flight N175F had started their beacon 3321. So you get a tiny stretch of 3020 (in green) but looks like less than a minute.

And then for UAL175 its a hey and a ho and a hey-nonny-nonny for Neuschwabenland

It has been annotated with 4 or 5 time points. These time points don't seem strongly anchored in reality.

Dave

 

[dafydd]

It is, not as fun as crashing two military aircraft into tall buildings and blaming arabs, but its still up there and best of all, no one gets hurt!

No wonder that I despise truthers.

 

[Dave Rogers]

No wonder that I despise truthers.

To be fair, they're not as bad as Holocaust deniers.

Oh, wait...

Dave

 

[Gord_in_Toronto]

Phew. Why?
I went back and read it twice to check if it contains a silly Stundie

Posts can be nominated as good posts. No Stundie involved. I thought you summed up the dichotomy quite nicely.

 

[LashL]

To be fair, they're not as bad as Holocaust deniers.

Oh, wait...

^^Nailed it in one.

 

[little grey rabbit]

Just returning to this fascinating subject.

I was looking at this picture again

Now the only footage I have seen of the plane striking the 2nd tower, it seems to come out of nowhere but flying relatively level, does its turn and strikes perpendicular with excellent penetration.

That was an incredible timing of the descent, to go from so high, plummet rapidly down so low and level off precisely to strike the WTC tower. Easy enough for a pre-programmed flight of course, but otherwise it must have been Allah himself directing the pilot.

I was reading wikipedia
http://en.wikipedia.org/wiki/United_Airlines_Flight_175
and it says

By 08:58, the plane was heading towards New York City and descended from an altitude of 28,500 feet over New Jersey. From the time, at approximately 08:58, when Shehhi completed the turn toward New York to the moment of impact, the plane went into a sustained power dive, descending more than 24,000 feet in 4 minutes 40 seconds, for an average rate of over 5,000 feet per minute.[13] New York Center air traffic controller Dave Bottiglia reported he and his colleagues "were counting down the altitudes, and they were descending, right at the end, at 10,000 feet per minute. That is absolutely unheard of for a commercial jet."[15]

It must have been dropping like an absolute stone.

Interesting one of the phone calls during this plummeting motion said

Peter Hanson made a second phone call to his father at 09:00:

“ It's getting bad, Dad. A stewardess was stabbed. They seem to have knives and Mace. They said they have a bomb. It's getting very bad on the plane. Passengers are throwing up and getting sick. The plane is making jerky movements. I don't think the pilot is flying the plane. I think we are going down. I think they intend to go to Chicago or someplace and fly into a building. Don't worry, Dad. If it happens, it'll be very fast....Oh my God... oh my God, oh my God."[15] ”

As the call abruptly ended, Hanson's father heard a woman screaming.[15]

Is this one of the calls that was actually recorded?

Because "making jerky movements" seems a rather odd description in the circumstances and "I think we are going down" at 9:00 would be verging on understatement.