Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
Christian Mayer writes: > > For the first, I was taught to look at the intended landing spot > > and, being aware of the windscreen, see whether that spot is > > stationary relative to the windscreen. If so, you are on track > > toward that spot. Try to see and feel this before worrying about > > _which_ glide slope you're on. It seems to work quite well. > > That's the same technique that sailors are using to figure out if they > are on collision course. And WWII fighter pilots, for that matter. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
[EMAIL PROTECTED] wrote: > > There are two aspects to being "on the glide slope". First, are you on _any_ path >that ends up at the beginning of the runway? Second, are you on the _intended_ glide >slope? > > For the first, I was taught to look at the intended landing spot and, being aware of >the windscreen, see whether that spot is stationary relative to the windscreen. If >so, you are on track toward that spot. Try to see and feel this before worrying >about _which_ glide slope you're on. It seems to work quite well. That's the same technique that sailors are using to figure out if they are on collision course. That that works can be proofen with basic geometry (intercept theorems, if the dictionary is correct...) CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
[EMAIL PROTECTED] writes: > For the second aspect, as David (I think) said, I was taught to > recognise the "on-screen geometry" of the runway, mainly the angle > of its edges. That works well in getting used to your home > airfield, and after gaining experience there, you will be > comfortable enough to adjust for unknown runways by picking up more > than one cue at a time. (I remember thinking "runway looking good > ... looking good ... oh, airspeed! quick! ... that's better > ... that's better ... oh, where's the runway gone?". Maybe not > literally, but that's what it felt like. That sounds very, very familiar. Losing the Iron Grip Of Death on the yoke helped a lot, since I could feel what the pitch was doing even when I wasn't staring at the ASI. > I stopped flying after getting a PPL, and never really reached the > comfortable stage. So please don't trust my tips and advice too > much.) Since you still have your PPL, you might consider taking a checkride (and updating your medical, if necessary) then trying again. I have been uncomfortable and nervous through much of my training, but I found that three things helped a lot: 1. Encouragement from the other FGFS developers and users. 2. Hours of practice on FlightGear with a proper USB yoke and rudder pedals (the JSBSim C172 handling is so close now that it's eerie: if I'm 5 kt too fast on approach in the real C172, I tend to be 5 kt too fast on approach in fgfs under the same conditions). One evening I did over 40 approaches in rapid succession using the forecast conditions from the TAF, then nailed my first solo the next morning. 3. Reading, rereading, and rerereading http://www.monmouth.com/~jsd/how/htm/ All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: Landing hints (was re: [Flightgear-devel] New A-4/jet panel instruments)
There are two aspects to being "on the glide slope". First, are you on _any_ path that ends up at the beginning of the runway? Second, are you on the _intended_ glide slope? For the first, I was taught to look at the intended landing spot and, being aware of the windscreen, see whether that spot is stationary relative to the windscreen. If so, you are on track toward that spot. Try to see and feel this before worrying about _which_ glide slope you're on. It seems to work quite well. (Or perhaps you've already got this part OK; I wasn't sure from you're description.) For the second aspect, as David (I think) said, I was taught to recognise the "on-screen geometry" of the runway, mainly the angle of its edges. That works well in getting used to your home airfield, and after gaining experience there, you will be comfortable enough to adjust for unknown runways by picking up more than one cue at a time. (I remember thinking "runway looking good ... looking good ... oh, airspeed! quick! ... that's better ... that's better ... oh, where's the runway gone?". Maybe not literally, but that's what it felt like. I stopped flying after getting a PPL, and never really reached the comfortable stage. So please don't trust my tips and advice too much.) - Julian > from:Andy Ross <[EMAIL PROTECTED]> > > David Megginson wrote: > > Andy Ross wrote: > > > Judging glide slope is still difficult, and will remain so until we > > > get some kind of approach slope lighting (VASI/PAPI/FLOLS, whatever) > > > implementation working. > > > > Speaking as someone who has just learned this stuff, I'll assert > > that estimating a glide path and extended centerline is not that > > tricky in good VFR conditions when the runway is level (sloping > > runways cause all kinds of misery). > > Heh, I hear what you're saying, but can't quite *do* it. This is one > of those techniques that I understand in my head, but just can't get > right in practice. In the cessna, I can sort of get by because the > throttle is much more responsive. But in the jet, the engine spools > more slowly and there's just too much going on. By the time I force > myself to decide whether I'm too low, I've either gotten way too slow > and am about to die, or have overcorrected on the throttle and am > balooning way above the glide slope. > > Practice, practice, practice. The velocity vector in the HUD has been > a crutch, I think. Gimme a week or so, and maybe a set of AoA > indexers, and I'll probably be OK. :) > > Andy > ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
