Paul Tomblin wrote:

In a previous article, Sam Spade said:

Paul Tomblin wrote:

can't select this departure procedure. Is this a limitation of the
simulator, or does the 530 not allow you to select departure procedures if
they're classified as "vector"?


If it is purely a vector departure; i.e., "fly xxx heading for vectors
to en route fix" then the 530 won't have those. Why should it? All you
do is fly an initial heading for vectors.


Well, it's vectors to several specific courses - for instance the way I go
it's vectors to intercept the R-199 from YOW somewhere between ASHTN and
REEDO. So it would be useful to have the GPS put ASHTN and REEDO in the
procedure.


Garmin has no way of knowing which of many possible waypoints the vector
will take you to. So, you have to line select the waypoints and TF legs
appropriate to the vector. On the other hand, with a structured SID,
with very specific transitions, then Garmin has it all there; i.e., the
three elements: The SID, the runway, and the transition.

If a vector SID were to have structured, fix transitions published on
the source document, then Garmin would include those transitions in the
database.