I have been flying FS9 since it came out but only recently really looked at the GPS. When flying several pre-planned flights between UK airfields using the FS9 flight planner, I have found that the GPS always indicates zero ETE with some 1 - 3 miles to run to the airfield waypoint [overhead the airfield - I assume]. I have tried this on both stock [MS]airfields and add-ons such as Gary Simmons series. In every case the same - the GPS ETE clicks over to zero with a few miles to run. to the overhead.Grateful if anyone could explain???

I suspect that the GPS is using an anticipation mode to the next waypoint. It calculates the ETE until it reaches a certain distance to the waypoint and then proceeds to the next waypoint in the flightplan.One thing the GPS does is start a turn to the next waypoint prior to being on-top the waypoint. This anticipation makes sure the aircraft is not too far off the heading for the next waypoint.I would look at the FPL page to see if the flightplan has moved the magenta line so the arrow now points to the next waypoint.If you are interested Garmin has a 182 page document detailing the actions of the Garmin 500 Series GPS. You might also find something in the FS2004 Learning Center, GPS.In real life , the ETE is calculated manually based on winds aloft, aircraft speed, etc., prior to takeoff and recorded on the flight log. Once takeoff is made, the time is noted. The time is then calculated for Estimated Time of Arrival (ETA) to the first waypoint, Takeoff time + ETE = ETA. Actual time of Arrival (ATA) and Actual time Enroute (ATE) are then calculated when the waypoint is reached.The GPS does all this internally, but the FAA, AOPA, and other flying orginations recommend following the basics learned during PPL training, i.e. Pilotage and Dead Reckoning, in case all the electronics sources fail.W. Sieffert

GPS measures slant range. Includes altitude component. 5,280ft = 1 mile. Thats probably why. Allcott

I have done more research and found the following:1. The ETE always hits zero at one minute flight tome to the destination eg: Maule at 120 kts low level - GPS goes to zero ETE with 2 miles to go. Hunter at 480 kts low level - GPS goes to zero ETE with 8 miles to go! [no slant range issue here]2. The GPS timing must be using the MS "hh.mm.ss" system but with the seconds removed.3. Thus when the GPS clicks over to 00.00; it is really saying "00.00.59" and then counts down from 59 seconds which we cannot see.Good old MS! But seriously, I think their system as engineered in the FS9 GPS gives a problem to some add-ons. I have just installed the Apollo series - which comes with the Maule package - it is a super package for GA flying but cannot give accurate ETE. It uses the FS9 GPS output and all systems work as advertyised except for ETE which just seems to fall over once you start the aircraft moving.

Hi Jerooum,you may consider these GPS instead:www.reality-xp.comHope this helps!