> Just out of curiosity, what is the shuttle's approach speed, and can
> it recover from a stall?
>
> David
I recall reading that initial flights landed at about 205 mph. This page:
http://www-pao.ksc.nasa.gov/kscpao/nasafact/count3slf.htm
says that the landing speed is typically now 213 to 226
Jon Berndt writes:
> Actually, I meant the pre-flare, which occurs at about 1800 ft. agl. This
> brings the glideslope from about 20 to less than 2 degrees. That's where
> he clobbered me. He was toying with me. The operators had some sense of
> humour...
Just out of curiosity, what is the s
> Jon S Berndt writes:
>
> > Just as I flared during the last landing he gave me a 100 knot
> > tailwind. If there would have been a black box, it would have
> > gotten from me only a "What the ... !" before I pancaked in.
>
> If you were flaring, you were probably close enough to the ground to
Jon S Berndt writes:
> Just as I flared during the last landing he gave me a 100 knot
> tailwind. If there would have been a black box, it would have
> gotten from me only a "What the ... !" before I pancaked in.
If you were flaring, you were probably close enough to the ground to
survive (i.
On Mon, 8 Jul 2002 16:54:12 -0500 (CDT)
"Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
>However, we would also need to be able to turn off the auto-failure
>generation module and allow an instructor (or a script) have complete
>control over the failures. This way an instructor could use the sim
Andy Ross writes:
> This could actually be done with minimal C++ code. Picture a "failure
> manager" that walks a property tree under "/failures". For each
> child, it reads a "mtbf-sec" property and sets the "working" boolean
> with a random probability that corresponds to the failure rate. Th
Curtis L. Olson wrote:
> But to your other point, I agree that we should start looking into
> failure modes. This is one big un-addressed issue. I could make up a
> list of interesting failure modes if anyone was interested.
This could actually be done with minimal C++ code. Picture a "failure
Curtis L. Olson writes:
> I've never, ever seen this problem (and I'm not lying my butt off
> about this like some software vendors I currently have to deal with.)
> But if you observe this happening again, you might double check that
> you didn't inadvertantly activate the wing leveler or he
David Megginson writes:
> I was testing some aero changes by flying in mouse mode (which is
> easier than pulling out the yoke and clamping it onto my desk) when
> something went wrong -- suddenly, the mouse would no longer control
> the ailerons, though it still controlled the elevators. I was o
I was testing some aero changes by flying in mouse mode (which is
easier than pulling out the yoke and clamping it onto my desk) when
something went wrong -- suddenly, the mouse would no longer control
the ailerons, though it still controlled the elevators. I was off
from the runway and heading f
10 matches
Mail list logo
