It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
Originally posted by thesneakiod
reply to post by SLAYER69
Sorry, I only asked.
So what do you want to discuss about the first two? I can't tell by your posts if you believe the NPT.
Originally posted by SLAYER69
Originally posted by thesneakiod
reply to post by SLAYER69
Sorry, I only asked.
So what do you want to discuss about the first two? I can't tell by your posts if you believe the NPT.
No I don't believe in the NPT. It's ridiculous. As I stated earlier there is plenty of eye witnesses, plenty of video not to mention still photos!
It was covered live. This is just yet another example of people who were not there and only watched it on TV or later on youtube and listen to people who were also not there spin yarns about some tinfoil conspiracy made up in their moms basement!
Originally posted by Zaphod58
True airspeed was about 602 mph at 22,200 feet.
Originally posted by Zaphod58
0.86 at 22,000 is about 603 mph.
Originally posted by RockHound757
Now tell us what "Vne" was at 22,000 feet in terms of "mph".
The point being that while it DID break up from excessive speed, it ALSO broke up from excessive G forces from diving, then pulling up,
First of all, please reference Vmo/Mmo. Jets dont use Vne (well, not in this case at least).
You may also want to re-check the NTSB report on EA990 as "it" wasnt past "Vne" for "several minutes". Matter of fact, it was past "Vne" for approximately 30 seconds before losing all aircraft power indicating some type of structural failure. The continued uncontrollability effects witnessed by primary radar in a short period of time further indicates a broken airplane due to excessive speed and perhaps 2.4G (less than Transport Category G limits).
No one said it did. But, Manufacturers place limits on airspeed for a reason, and yes, it has alot to do with the health of all on board, not some arbitrary number.
First you agree it broke apart due to excessive speed, then you add G loads, now you say its due to impact? Make up your mind. It would also be nice if you could provide such a quote from the NTSB.
Obviously you missed this little tidbit...
Seven primary radar returns from the airplane were recorded during the second dive; the altitude estimates from these returns are subject to potentially large errors, which introduces significant uncertainty into the performance calculations during the second dive.
Originally posted by Zaphod58
At 25,000 feet Vmo/Mmo is 501mph/Mach 0.72.
UA175 wasn't in a near vertical dive,
and then pull up hard enough to zoom up 6,000 feet. UA175 was in a much shallower dive, with a much easier pull up at the end.
As noted Vmo/Mmo is 501mph/0.72 Mach.
EA990 exceeded Mach 0.86 (max operating speed) and was at 0.99 Mach at 0150:23.
The aircraft pulled up at 16,000 feet and at 0151:15 the second dive began and lasted until impact.
the altitude estimates from these returns are subject to potentially large errors, which introduces significant uncertainty into the performance calculations during the second dive
If you don't care about the "health of all on board" what does it matter if you exceed Vne for a short time?
The excessive speed was a contributing cause. Excessive speed, combined with G loads will cause an airframe to break apart.
During the SECOND DIVE. That means that it was intact at least up until the point that it stalled after pulling out of the dive. Which means that it successfully passed Vmo/Mmo and Vne and remained intact through pulling out of the dive, at those speeds.
Originally posted by Zaphod58
If Vmo is a constant
then how can it be as low as it is at 700 feet? If it's that low at sea level, then it has to be lower than the 0.86 until you reach cruising altitude.