Dave, for all the approaches you listed, the GS elevation was 0 in the nav.dat.gz (with the exception of KBJC which was a different issue, but also fixed in cvs.)

Regards,

Curt.


Dave Perry wrote:

As I indicated in my other post, I checked the elevations in nav.dat.gz, and they
look correct.
I flew outbound (167 deg.) on the ILS at 6000 MSL for KGXY and the GS
stayed pegged low past DME 16 NM from the localizer. At 7000 MSL and DME 13 NM, the GS should have been above the aircraft
so the needle should be high. I then descended to 5000 MSL (virtually on the ground) and
the GS needle finally came off the lower limit.
Here is the GS entry from nav.dat.gz for this approach.
6 40.434344 -104.629642 4656 11030 300356.860 --- KGXY 34 GS
The TDZE is 4665 MSL for this approach and
the elevation entry is 4656 MSL. So this should be very close to correct
but the GS response is more than 2000 ft off.


There are two entries in the GS lines that I don't recognize. One is the number
at the beginning of the line. The other is 300356.860. But the other fields
look correct.


The problem is not the elevations in nav.dat.gz. Hope this discussion helps.

Thanks for all your hard work!
Dave


_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel



--
Curtis Olson http://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d



_______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to