A aviation & planes forum. AviationBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Instrument Flight Rules
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

RNAV vectors



 
 
Thread Tools Display Modes
  #1  
Old December 18th 06, 12:30 AM posted to rec.aviation.ifr
Stan Prevost
external usenet poster
 
Posts: 118
Default RNAV vectors


"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.



  #2  
Old December 18th 06, 12:52 AM posted to rec.aviation.ifr
Sam Spade
external usenet poster
 
Posts: 1,326
Default 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. ;-)
  #3  
Old December 18th 06, 01:33 AM posted to rec.aviation.ifr
Stan Prevost
external usenet poster
 
Posts: 118
Default RNAV vectors


"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.





  #4  
Old December 18th 06, 01:43 AM posted to rec.aviation.ifr
Roy Smith
external usenet poster
 
Posts: 478
Default RNAV vectors

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.
  #5  
Old December 18th 06, 02:00 PM posted to rec.aviation.ifr
Stan Prevost
external usenet poster
 
Posts: 118
Default RNAV vectors


"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 ?



  #6  
Old December 18th 06, 03:03 PM posted to rec.aviation.ifr
Sam Spade
external usenet poster
 
Posts: 1,326
Default RNAV vectors

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.
  #7  
Old December 18th 06, 03:19 PM posted to rec.aviation.ifr
Stan Prevost
external usenet poster
 
Posts: 118
Default RNAV vectors


"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.



  #8  
Old December 18th 06, 03:43 PM posted to rec.aviation.ifr
Sam Spade
external usenet poster
 
Posts: 1,326
Default RNAV vectors


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.
  #9  
Old December 18th 06, 03:08 PM posted to rec.aviation.ifr
Ron Natalie
external usenet poster
 
Posts: 1,175
Default RNAV vectors

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).
  #10  
Old December 18th 06, 03:20 PM posted to rec.aviation.ifr
Stan Prevost
external usenet poster
 
Posts: 118
Default RNAV vectors


"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.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Contact Approach -- WX reporting [email protected] Instrument Flight Rules 64 December 22nd 06 01:43 PM
RNAV Operations in FS2004 Rookie Instrument Flight Rules 2 November 29th 06 11:51 PM
RNAV approaches Kevin Chandler Instrument Flight Rules 3 September 18th 03 06:00 PM
RNAV approaches Kevin Chandler Piloting 3 September 18th 03 06:00 PM
Slam dunk into Janesville Steven P. McNicoll Piloting 0 July 31st 03 01:08 AM


All times are GMT +1. The time now is 07:57 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.