Vectors to Final
- Tizi

- Feb 26
- 5 min read
"Turn left heading 130, maintain 2000 until establised cleared ILS 10 approach" -SAV ATC
Vectors to final (VTF) is a controller managed option to clear you onto an instrument approach procedure (IAP). This is not a charting transition, but it is considered - in navigation world - a transition for the approach. So for example, when you load an approach into your Garmin navigator, "vectors" will be an acceptable transition selection.
We talked about approach clearance types in this article, so please review vectors to final (VTF) over there real quick as well.
The point of VTF is to allow a controller to sequence traffic more easily onto an approach. ATC can see the "big picture" with many airplanes trying to do exactly what you want to do: land on the runway. As such, an initial approach fix (IAF) can be useful only when traffic allows. When things ramp up (i.e., the normality at KSAV), ATC will use any means possible to keep everyone under positive separation.
Vectors to final indicates a situation where the controller will give you vectors (i.e., headings) to intercept the final approach course (FAC). So in essence, they are aligning you up with an extended final. As such, your guidance should be to the Final Approach Fix (FAF). Remember the final approach segment of the approach that goes from the FAF to the missed approach point? Well, VTF makes that segment a lot longer by extending outward away from the airport.
Garmin SmartCharts (Data Driven Charts) does a good job at representing this on a chart. If you look below, the first image shows the RNAV Z 28 at KSAV with "all transitions" shown. Then, the second image, shows the same approach with "vectors" chosen as a transition. Notice the arrow that leads into the Intermediate Fix (IF), TELOE? All VTF is doing is making your final approach course longer. Even though your active waypoint will be SINBY (the FAF), Garmin will also include the intermediate fix for convenience, even though you will not sequence the waypoint.
All Transitions | Vectors to Final |
![]() | ![]() |
There are rules on how tvectors to final happen. Controllers are not allowed to vector you too close to the FAF because you need time to stabilize. Imagine trying to join your lateral path AND the glideslope at the same time! Insane! They still need to give you a short intermediate segment. The distance is actually two miles, assuming there are at least five miles from the missed approach point to the FAF. That is called the FAF gate. Now, this is more of an engineering level knowledge, but you might as well know!
When I brief an approach knowing that I will be on VTF, I always mention it. I'll say "we are on vectors to final, so I expect to intercept the final approach course ouside of the FAF, SINBY, at or above 1,800 ft".
Example Scenario
Let's take a look at this scenario using a Garmin GTN 750. This applies also to the GTN 650 series, but the larger screen helps to describe the concept in this article.
I'm flying form KAQX to KSAV on the following route: KAQX ALD V37.SAV KSAV. I'm on the last airway leg to SAV (TILLS to SAV), as shown in the image below. My active waypoint is SAV, 6.8 NM away.

The controller then tells me to "turn left heading 130, vectors for final, RNAV Z runway 28". I begin turning to my instructed heading (as shown in the image below) and now know that I will flying the RNAV Z 28 approach using vectors to final.

As the more perceptive of you probably realized by now, my guidance is useless. My flight plan still has me going to SAV, but I am clearly not going there anymore. I am instead being vectored to the final approach course of the RNAV Z 28 approach, as shown in the chart below. Note that the red line is an extended final approach course. I could be vectored to join that line anywhere (close or far). The blue curve outside of SINBY is a minimum vectoring spacing (so I don't get too close to the FAF - the gate, remember?), and the blue arrows depict ways in which the controller may give me headings (vectors) to intercept.

Ok, we now established that my guidance is usesless. My flight plan and my HSI are giving me directions to SAV, not SINBY. So this is the perfect time to activate vectors to final on the GTN. Notice in the table below how you load and activate the approach using VTF. On the left image, I choose "Vectors" as a Transition. When I click "Load Approach & Activate", the flight plan page comes (right image) up and shows me that I am now on an active leg to SINBY, the Final Approach Fix.
Procedure Loading Menu | Flight Plan after Procedure Activation |
![]() | ![]() |
My map will now depict the new flight plan modification, showing me a straight long line inbound to SINBY, but extending outbound.

Notice a few things:
SINBY is the active waypoint. That is the FAF. The active waypoint will always be the FAF.
The active leg (the magenta line) extends outbound for miles! This is because you don't really know how far out the controller will vector you to intercept the final approach course. Keep in mind that they may have multiple airplanes intercept at the same time, just far from one another!
TELOE, which is the intermediate fix, is still depicted. Why would an inactive waypoint be shown on the map?? Well, Garmin is smart. There are cases where the controller tries to vector you further away and then traffic gets to busy. He is always allowed to tell you to proceed "direct TELOE" to join the approach. TELOE is an initial approach fix (IAF), and a perfecly legal transition. If it weren't on the map (and in your flight plan), you would have to completely reload the approach to direct-to it. By placing it on the map and flight plan, Garmin avoids that headache "just in case" the controller changes their mind.
All you have to do now is follow the headings assigned to you and join the approach when you're told to by ATC. It's pretty easy, huh? Well, as always, we make it sound easy, and then all hell breaks lose in the air...
Approaching VTF on a right base | Intercepting VTF |
![]() | ![]() |










Comments