I had a squawk here from a (real) King Air pilot because on an ILS approach, our glideslope indicator doesn't become active/in-range until about 7-8 miles out. Beyond this range the indicator just stays centered at zero. With a standard 3 degree glide slope, 7 miles out equates to about 2000' AGL, outside of this range the FlightGear glideslope does nothing.
I see our database lists the GS ranges at 10nm usually. However, our code seems to be clamping the range to something significantly less than that. I've been poking around in navdb.cxx and navradio.cxx but haven't been able to connect all the dots yet. I don't have personal knowledge of what is correct, but this change to glideslope range impacts our ability to practice ILS approaches and I have a current King Air pilot complaining about the behavior. Pulling out some old approach plates for KMSP here I see a 14nm distance and 5000' MSL entry altitude (4000'+ AGL) referenced in the approach to 30R. Is 7-8 miles a realistic range for the glide slope? Is my King Air pilot contact smoking something? Thanks, Curt. -- Curtis Olson: http://baron.flightgear.org/~curt/
------------------------------------------------------------------------------ This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
