model math blows up, the lat/lon could be nan. Thus updateLocal() could potentially called with nan arguments if FlightGear is reiniting from a blown up state. This is a bug in FlightGear, but I've added a simple check to catch this so updateLocal() is robust if called under these circumstances.