Hokulele
Deleterious Slab of Damnation
You lost me. ;(
He was making a visual joke that the Maya cartoon should have shown half a plane for the entire flight to match the witness testimony more closely.
(At least, that is how I read it.)
You lost me. ;(
You lost me. ;(
Like I have said repeatedly about those cartoonists, incompetence in, incompetence out.
And in case you ever need to know this (I can't think why, but someone may need this information), last I knew, QuickBird satellite imagery has an average error of about 15 meters. It may be better in the Washington area, but I would have to send someone an e-mail to find out for sure. I think even the best areas are still about 4 meters off. Sure, if you are simply looking for landmarks, 15 meters will get you close enough, but if you are trying to make any kind of accurate calculation, get it surveyed.
And just for A W Smith, the high-end GPS units ($15,000 +) are typically accurate to 0.6 meters, the mass market ones will generally be around 5 meters, depending on your view of the sky and how many satellites are available. With post-processing, survey-grade instruments can get down to sub-centimeter accuracy.
... but: I wonder how quantifiable the error induced happens to be from Google's need to distort images of a curved surface (the earth, of course) in order to stich together all those series of flat-projected images. I have no idea where even to begin reading about that (save for quickie Googlewhacks with the obvious search terms). But of course, there will be issues matching edges of photos. Of course, they'll have to discard quite a bit of area in a photograph due to barrel distortion induced by the lenses of the cameras involved, but still... my point is that there must be some error inherent in that stitching together, and I'm just casually pondering how measurable it is.With your hero's being CIT and Balsamo almost everything has you stumped. Balsamo with 2,223 gs of stupid math, and CIT with moronic lies you are a prime suspect when it comes to being gullible, naive, susceptible, credulous, easy to fool, and trusting total dolts. You are still stumped.
I was looking for an academic answer. To fly a True Course we correct for winds to give us a true heading. If you could do math and aero, you could add details which I will let you mess up more? You gave me the moron answer and added stupid.
Next, the stupid…
Do you check anything the morons at p4t dish out?... Based on the physics of flight, if you keep the wings level and yaw the airplane with the rudder, the thrust then has a lateral component to the flight path and will supply the necessary horizontal force, and a turn results. Got physics?
*snipped meandering rant*
The only path there is went through the light poles hitting the generator and inflicting the damage witnessed on 9/11/2001. Unless you can show how that all was faked all you're doing is typing practice.
Can you show how this physical evidence was faked?
Both those images are watermarked by Google Earth. What "software" did he use to verify the positional accuracy of those image overlays and pin placement?
From the complete decode of data supplied p4t years ago, Warren decode the final 5 seconds Balsamo has been hiding from the world so he can sell idiotic delusions on DVD.
The final points come from the navigation system no Flight 77 and the errors range from 200 feet to 2,000 feet; 605 feet on good day.
[qimg]http://i286.photobucket.com/albums/ll116/tjkb/1CITFRAUDexposed.jpg[/qimg]
mudlark calls this the official flight path.
These push pins are from the FDR sampled from the navigation system with at best expected 605 feet accuracy. Errors of over 600 feet can be expected, at takeoff errors were over 2,000 feet.
So these push pins define a path with an error budget from 600 feet to 2,000 feet.
No surprise here as the no math team of CIT and Balsamo have pushed mudlark out the door with no clues.
Yes the real flight path of 77 is within 600 to 2,000 feet of these push pins, with the headings the most accurate part of the deal. Headings are kind of good, and very close to being accurate. I say +-1 to 2 degrees.
Thanks mudlark for exposing your lack of knowledge on another science aspect of your delusions.
The FDR describes the real flight path on 911, when you understand the errors in each value stored in the FDR, you can make rational conclusion about the Flight path.
So we have a description but mudlark has help from idiots who can't grasp what the FDR has in it. They have no clue about flying.
So these push pins define a path with an error budget from 600 feet to 2,000 feet.
Originally Posted by Reactor drone
Just out of interest, how high above the ground is the virtual camera in those photos, how far away from the window is it and how tall are the windows?
ETA- also what lens are you using?
Too low, too close and too tall. But, what would that matter?![]()
"We heard a big sound and then I just look out like this (bends down to look out window, up at the sky)"
"I could just see a big black wing"
Did I miss mudlark's reply providing us with the "NOC flight path over and away from the Pentagon?"
I think that would be O'Rale?They got a big Hispanic population up there in Ireland?
I never knew the Mexican Mafia had an Irish accent.
Orale.
What answer? You never answered my question in the first place, that's the point.
So he saw the right wing and the fuselage fly this entire path?
[qimg]http://lh4.ggpht.com/_MSV5A_kgZ98/S4VFbMGqZ4I/AAAAAAAABIE/0qY9XFGzW3A/s576/paik.JPG[/qimg]
Just tell me if you think he witnessed the majority of the flightpath he drew?
That's a totally different issue than what I'm asking about.
Since someone brought up a straight-line path, I thought this image might prove useful to the discussion.
[qimg]http://zoesflight.com/files/straight.jpg[/qimg]
I have labeled the track angle at the appropriate data points and connected them with at straight line. It becomes obvious that the final positional marker is clearly not on the straight line path, so some type of in-flight correction was definitely in play. It also shows that what I said before in regards to the model being shifted slightly to the south relative to the final 3 DCA radar returns is consistent with the markers as well. The plane would have had to be a 100 feet or so further north to avoid the over-the-road structure.
Now this image illustrates the Google Earth errors that Hokulele has patiently been trying to explain to some individuals.
[qimg]http://zoesflight.com/files/topo_error.jpg[/qimg]
Although slight, there is a clear shift in the marker positions and the straight line reference (unchanged in the two) when satellite images from 2001 and 2010 are interchanged.
So yes YouTube generation, there are errors associated with the GE positioning. I know that really hurts, but that is why it is impossible to reconstruct the exact actual path down to feet. From the GE imagery, my resultant model does appear slightly south of where the actual flight path was, but that is why I used the last 3 DCA radar returns to estimate the error range. I gave that error band earlier. I was wondering then why the plane was so high on the northern limit of that range, but thankfully mudlark helped clarify that the Sun was actually lower in azimuth, thus reducing those altitudes to within what I had expected to see. Thanks for the help mudlap, I mean mudlark.
williamseger said:That's a stupid question. (on asking where he believes the SOC path is) Draw a line from where the plane hit the Pentagon back through where it knocked down the the lightpoles, and you've got it.
I guess I'll just need to keep repeating this until it sinks in: My drawing does not show any "trajectory." It's a scale drawing that shows Paik's approximate vertical field of view out that window. In the interview video, Paik points out that window at about a 35o angle to indicate where he saw the plane. From that video, I estimate that he could not possibly have seen upward at more than a 45o angle. I have indicated those two angles in my drawing. Are you with me so far?
"We heard a big sound and then I just look out like this (bends down to look out window, up at the sky)"
Originally Posted by mudlark
Now look at the MAP Paik drew.
I have. He drew a path that crosses over his parking lot, perhaps 30 feet SSE of that window.
Originally Posted by mudlark
Now look at topography of the area. In this instance the position of Paik´s shop in relation to the 200ft+ Sheraton Hotel..
Which is completely irrelevant to the point of my drawing. Please try to focus on Paik's vertical field of view out that window.
Now it's my turn to call your attention to Paik's map: He has the plane flying over the Annex building after passing over his parking lot. That building is about 70 feet tall. Are you still with me?
But there isn't any "depiction of the NOC plane's trajectory" or any other "trajectory" in my drawing. I have one depiction of the plane directly over Paik's head and at the bare minimum altitude if would need to clear the Annex building (even if it were in level flight at that point, which it wasn't), which simply shows that if the plane had really passed there, then Paik wouldn't have seen it. I have a couple of other arbitrary depictions that are not any attempt to indicate a particular flight path or trajectory, but rather a simple fact of geometry: For Paik to have seen the wing and fuselage out that window, the plane must have been at least as far SSE of that window as it was above the ground. If the 35o angle he is pointing to in that video is reasonably accurate, then it was even farther away than it's altitude. I've lost count of how many times I've said that now
Originally Posted by mudlark
His map reinforces the inaccuracy of your interpretation of the trajectory and DISTANCE from his POV.
He clearly places the plane over his front yard where he described only the right wing as being visible
And there's the point that you seem to be determined to not understand. If the plane was on the path he drew on the map, maybe 30 feet SSE of that window, and he was looking up at a 45o angle or less, then the plane would have been at an altitude of 30 feet or less. If the plane had been anywhere near that low, there is no way it could have cleared the Annex building. QED, Paik's map CANNOT be accurate, unless he lied about seeing the fuselage. Get it now? Either Paik's map is wrong, or he didn't see the plane. Which would you like to go with?
Originally Posted by mudlark
Your "SOC plane"...how relative is it to the actual proposed SOC path?
The left wing of your "SOC plane" closest to the "NOC plane" is actually overlapping the wing of the "NOC plane"
The furthest "SOC" plane
Just WHERE do YOU believe SOC actually was??
That's a stupid question. Draw a line from where the plane hit the Pentagon back through where it knocked down the the lightpoles, and you've got it. You seem to have forgotten that you're supposed to be proving that's not right. Paik's inaccurate map certainly doesn't do it, nor does what he said he saw out that window, not does Balsamo's graphic.
Ok, so if it was somewhere around 350 to 400 feet up, no more than 430 feet up, then that would be about the angle he pointed, wouldn't it. You've supposed to be proving that's not the case.
No, I'm not "placing" the 260 ft away. My drawing simply concerns the angle at which Paik viewed the plane and what that implies. The entire problem is that neither you nor I nor Paik can use that angle alone to "place" the plane. But what my drawing shows is that Paik's placement on the map can't be right. And if it's wrong, it's meaningless.
Originally Posted by mudlark
The scale of the Navy Annex to Paik´s shop?
The Navy Annex is 4 stories tall @69ft.
You have Paik´s shop scaled to 6mm.
You have the Navy Annex scaled to 7cm.
Are you really trying to say that the Navy Annex is almost TWELVE times taller than the shop??
Doesn't make a bit of difference, since the important feature is that Paik couldn't have seen more than about 45o up. That and the rest of your post are irrelevant, since you still didn't seem to understand what I was getting at. I do hope this helped.
I´m trying to determine exactly WHERE the SOC path is according to the posters here from BEFORE the Navy Annex through to the VDOT Tower.
Do you have a preferred choice DGM? Or are you just happy to go with the flow and agree with anything put forward by any poster mentioned above?
A planes course can change without a heading change; aircraft fly in air; air moves. BUT...How much a course change would you experience with a less than a tenth of degree change over 5 seconds. ...
I am not the one who needs help with math, you said a 1.3 heading change was 0.1 degree. ? lol (nk)How much would the course change flying your desk in a 0.1 degree change over 5 seconds. lol (jk) .
Wrong. True course last 5 seconds.It HAD to be in a straight line to line up with the physical damage.
You never presented the math for your NoC flight path; no surprise you announce, “No math needed”.No "math" needed for the points I´m making just honesty and logic.