[index] [month] [prev] [next] [thead-prev] [thread-next]

Looks to me like it works just fine. First, remember, in the flight levels
the actual height of the airplane goes up and down a significant amount.
Also, WAAS wasn't meant to improve anything enroute, but during the
approaches and close to the airports. And second, the accuracy will only be
enhanced with WAAS signals being received. To my understanding, besides a
few test areas, there are few WAAS signals being transmitted yet. Or did I
miss something while I was away recently?

"terpster" <aterpster@hotmail.com> wrote in message
news:3AF0579A.894CD1BB@hotmail.com...
> Now that I've used my Garmin 295 with WAAS enabled and disabled, I fail
> to see the value of WAAS, at least for the way I use my 295:
>
> 1. It slows down my road map significantly when I use it with MapSource
> in my car.
>
> 2. I used it on an airline flight from LAX to BWI and return. I didn't
> get any WAAS going over apparently because I was on the north side of
> the cabin. But, I had normal 3-D nav all the way from LAX to BWI with
> the usual 1,000-foot, or so, vertical elevation errors. Coming back, I
> was on the south side of the cabin and had 3-D WAAS the entire time.
> Our enroute altitude was Flight Level 350 (confirmed because the crew
> had ATC enabled on the entertainment system) and I read altitudes that
> varied from 35,900 to 36,100.
>
> So, in the flight levels, at least, WAAS doesn't do a thing to improve
> my 295's vertical accuracy.
>
> Fortunately, Garmin had the foresight to make WAAS a toggle.
>

View index by [date] [author] [subject]
Previous message: Re: Holding, ArleneDavis
Next message: Re: Holding, Norm Melick
Next message in thread: Re: More Garmin 295 WAAS, Marcelo Pacheco
Previous message in thread: Re: More Garmin 295 WAAS, Timothy M. Metzinger