RNAV vectors

Stan Prevost wrote:

"Sam Spade" wrote in message
...

The pilot can go to OBS mode and select FRZZN as the active waypoint, then
select bearing 002 mag to FRZZN.



You don't have to use OBS mode, at least on the GNS430. Use DIRECT TO, then
set the course. This way draws a line on the map, OBS doesn't.



That won't work with the GNS400/500 series. Doing it the way I describe
will provide a course line. I don't have a clue about the 480. ;-)

"Sam Spade" wrote in message
...
Stan Prevost wrote:

"Sam Spade" wrote in message
...

The pilot can go to OBS mode and select FRZZN as the active waypoint,
then select bearing 002 mag to FRZZN.



You don't have to use OBS mode, at least on the GNS430. Use DIRECT TO,
then set the course. This way draws a line on the map, OBS doesn't.



That won't work with the GNS400/500 series. Doing it the way I describe
will provide a course line. I don't have a clue about the 480. ;-)

Works on my 430s, and works on the 430 simulator/trainer. But on the sim, I
also got the magenta line using OBS mode, didn't think I could. Don't
remember what caused me to believe that.

In article ,
Sam Spade wrote:

Stan Prevost wrote:

"Sam Spade" wrote in message
...

The pilot can go to OBS mode and select FRZZN as the active waypoint, then
select bearing 002 mag to FRZZN.



You don't have to use OBS mode, at least on the GNS430. Use DIRECT TO,
then
set the course. This way draws a line on the map, OBS doesn't.



That won't work with the GNS400/500 series. Doing it the way I describe
will provide a course line. I don't have a clue about the 480. ;-)

On the 480, I would hit the VTF soft key (assuming I've already got the
approach loaded with some arbitrary IAF selected). At that point, the box
would create a segment from [a point 50(*) miles 182 degrees from FRZZN] to
FRZZN, make that the active leg (i.e. draw it in magenta on the map), and
go into suspend mode. Assuming I was given a good vector, flew it
correctly, and had sufficient fuel, I would eventually intercept that
segment. At that time the box would automagically come out of suspend
mode. When I reached FRZZN, it would sequence to FRZZN-MAP36 being the
active leg.

(*) I think it's 50 miles. Could be something else, but it's long enough
that it's never been an issue for me.

"Roy Smith" wrote in message
...

On the 480, I would hit the VTF soft key (assuming I've already got the
approach loaded with some arbitrary IAF selected). At that point, the box
would create a segment from [a point 50(*) miles 182 degrees from FRZZN]
to
FRZZN, make that the active leg (i.e. draw it in magenta on the map), and
go into suspend mode. Assuming I was given a good vector, flew it
correctly, and had sufficient fuel, I would eventually intercept that
segment. At that time the box would automagically come out of suspend
mode. When I reached FRZZN, it would sequence to FRZZN-MAP36 being the
active leg.

(*) I think it's 50 miles. Could be something else, but it's long enough
that it's never been an issue for me.

Roy, apparently VTF works much differently on the 480 than the 430 and
sounds correctly implemented. On the 430, VTF doesn't work properly on a
dogleg approach. It sets up for the dogleg intermediate segment rather than
the extended final course. Have you checked the 480 for a dogleg, such as

http://www.naco.faa.gov/d-tpp/0612/05924VDB.PDF
or
http://www.naco.faa.gov/d-tpp/0612/06712R23.PDF ?

Stan Prevost wrote:


Roy, apparently VTF works much differently on the 480 than the 430 and
sounds correctly implemented. On the 430, VTF doesn't work properly on a
dogleg approach. It sets up for the dogleg intermediate segment rather than
the extended final course. Have you checked the 480 for a dogleg, such as

It seems to me to work correctly. Using your example of KEKX RNAV 23,
if I select VTF, as you say, I get a track line of 270 magnetic to
JEXUD. That would be the correct course to intercept for vectors to
"final."

The issue is FAA terminology that is predicated on the ILS case.

"Sam Spade" wrote in message
...
Stan Prevost wrote:


On the 430, VTF doesn't work properly on a
dogleg approach. It sets up for the dogleg intermediate segment rather
than the extended final course.


It seems to me to work correctly. Using your example of KEKX RNAV 23, if
I select VTF, as you say, I get a track line of 270 magnetic to JEXUD.
That would be the correct course to intercept for vectors to "final."

The issue is FAA terminology that is predicated on the ILS case.

It works the way that we pilots would usually prefer that it work, but the
problem is that the 7110.65 used in conjunction with the definitions in the
P/CG, doesn't allow for controllers issuing vectors to an approach other
than to the final approach course as defined in the P/CG, and this results
in some controllers doing it one way and others doing it another way, and
pilots never know (except through local experience) what a controller
intends if s/he says Vectors To Final. The manual should be revised to
allow vectors to an intermediate dogleg segment. Maybe an ASRS report will
get the concern into the system.

Stan Prevost wrote:

It works the way that we pilots would usually prefer that it work, but the
problem is that the 7110.65 used in conjunction with the definitions in the
P/CG, doesn't allow for controllers issuing vectors to an approach other
than to the final approach course as defined in the P/CG, and this results
in some controllers doing it one way and others doing it another way, and
pilots never know (except through local experience) what a controller
intends if s/he says Vectors To Final. The manual should be revised to
allow vectors to an intermediate dogleg segment. Maybe an ASRS report will
get the concern into the system.


The only effective way to get it addressed is for a user group (such as
AOPA) to submit it to ATPAC (Air Traffic Control Advisory Committee).

But, according to the FAA ATO chiefs, vectors can be given to final only
where the final approach course is on the video map. And, they claim
that is done only with ILS approaches that are in an area with adequate
radar coverage. So, I presume those chiefs would say it is a non--issue
if submitted to ATPAC.

"Sam Spade" wrote in message
...

Stan Prevost wrote:

It works the way that we pilots would usually prefer that it work, but
the problem is that the 7110.65 used in conjunction with the definitions
in the P/CG, doesn't allow for controllers issuing vectors to an approach
other than to the final approach course as defined in the P/CG, and this
results in some controllers doing it one way and others doing it another
way, and pilots never know (except through local experience) what a
controller intends if s/he says Vectors To Final. The manual should be
revised to allow vectors to an intermediate dogleg segment. Maybe an
ASRS report will get the concern into the system.

The only effective way to get it addressed is for a user group (such as
AOPA) to submit it to ATPAC (Air Traffic Control Advisory Committee).

But, according to the FAA ATO chiefs, vectors can be given to final only
where the final approach course is on the video map. And, they claim that
is done only with ILS approaches that are in an area with adequate radar
coverage. So, I presume those chiefs would say it is a non--issue if
submitted to ATPAC.


The full rule (almost) is given in 7110.65R, excerpted below. As to policy
for what goes on the scope, I have no idea. I have been told that it is
decided locally for each facility.

They can hide their heads in the sand and pretend that vectors are given
only to ILS approaches, but it is everyday practice for vectors to be given
to NPAs also.


5-9-1. VECTORS TO FINAL APPROACH COURSE

Except as provided in para 7-4-2, Vectors for Visual Approach, vector
arriving aircraft to intercept the final approach course:

a. At least 2 miles outside the approach gate unless one of the
following exists:

1. When the reported ceiling is at least 500 feet above the MVA/MIA
and the visibility is at least 3 miles (report may be a PIREP if no weather
is reported for the airport), aircraft may be vectored to intercept the
final approach course closer than 2 miles outside the approach gate but no
closer than the approach gate.

2. If specifically requested by the pilot, aircraft may be vectored to
intercept the final approach course inside the approach gate but no closer
than the final approach fix.

EXCEPTION. Conditions 1 and 2 above do not apply to RNAV aircraft
being vectored for a GPS or RNAV approach.

b. For a precision approach, at an altitude not above the
glideslope/glidepath or below the minimum glideslope intercept altitude
specified on the approach procedure chart.

c. For a nonprecision approach, at an altitude which will allow
descent in accordance with the published procedure.

NOTE-
A pilot request for an "evaluation approach," or a "coupled approach,"
or use of a similar term, indicates the pilot desires the application of
subparas a and b.

d. EN ROUTE. The following provisions are required before an aircraft
may be vectored to the final approach course:

1. The approach gate and a line (solid or broken), depicting the final
approach course starting at or passing through the approach gate and
extending away from the airport, be displayed on the radar scope; for a
precision approach, the line length shall extend at least the maximum range
of the localizer; for a nonprecision approach, the line length shall extend
at least 10NM outside the approach gate; and

2. The maximum range selected on the radar display is 150 NM; or

3. An adjacent radar display is set at 125 NM or less, configured for
the approach in use, and is utilized for the vector to the final approach
course.

4. If unable to comply with subparas 1, 2, or 3 above, issue the
clearance in accordance with para 4-8-1, Approach Clearance.

REFERENCE-
FAAO 7110.65, Approach Clearance, Para 4-8-1.
FAAO 7110.65, Final Approach Course Interception, Para 5-9-2.

Stan Prevost wrote:


Roy, apparently VTF works much differently on the 480 than the 430 and
sounds correctly implemented. On the 430, VTF doesn't work properly on a
dogleg approach. It sets up for the dogleg intermediate segment rather than
the extended final course. Have you checked the 480 for a dogleg, such as

http://www.naco.faa.gov/d-tpp/0612/05924VDB.PDF
or
http://www.naco.faa.gov/d-tpp/0612/06712R23.PDF ?




The VTF on the 480 seems to work the same way. it extends the
dogleg (the R-250 off RQZ).

"Ron Natalie" wrote in message
...
Stan Prevost wrote:


Roy, apparently VTF works much differently on the 480 than the 430 and
sounds correctly implemented. On the 430, VTF doesn't work properly on a
dogleg approach. It sets up for the dogleg intermediate segment rather
than the extended final course. Have you checked the 480 for a dogleg,
such as

http://www.naco.faa.gov/d-tpp/0612/05924VDB.PDF
or
http://www.naco.faa.gov/d-tpp/0612/06712R23.PDF ?




The VTF on the 480 seems to work the same way. it extends the
dogleg (the R-250 off RQZ).

Thanks, Ron. I have been wondering how that worked in the 480.