STARS Tips/Tricks

Pro tip: if you aren't a weak controller who needs PTL's for every single plane turned on but occasionally you want to see if you've got a good initial vector, you can have the PTL's turned off but the setting turned all the way up to 5.0 and then use multi function R and slew to turn on the PTL for an individual plane. Repeat the process to turn it back off.
 
Pro tip: if you aren't a weak controller who needs PTL's for every single plane turned on but occasionally you want to see if you've got a good initial vector, you can have the PTL's turned off but the setting turned all the way up to 5.0 and then use multi function R and slew to turn on the PTL for an individual plane. Repeat the process to turn it back off.
This works for any target as well. Though use PTLs or history. I hate not being able to tell what a plane is doing at a quick glance.
 
Pro tip: if you aren't a weak controller who needs PTL's for every single plane turned on but occasionally you want to see if you've got a good initial vector, you can have the PTL's turned off but the setting turned all the way up to 5.0 and then use multi function R and slew to turn on the PTL for an individual plane. Repeat the process to turn it back off.
I use this to put PTLs on VFR targets to help call traffic.

MultiFunc Z slew on a target will give you tons of info... most of which I don't understand but shows the present track of your target.
 
Multi Func Modify Y, splat, space, call sign, splat splat, space, backlash, F9, slew enter...... I’m sure it does something... STARs and their stupid codes.
 
*F then slew enter enter (double click) to get the nearest fix.
To change the callsign (tagged up and owned by you): *N12345 slew enter. Instead of MultiFunc Mod.
To give a current track a new IFR beacon code: MultiFunc, Mod, +, slew enter. For VFR same thing, except the / VFR key.
 
Not sure if you need A/C type in the H pad as well.
Seems reasonable. It also seems reasonable you'd need the altitude in the +000 scratchpad too. But I'm just a tower flower. Just watch the tracon guys do it a lot. before i got kicked out that is.
 
If a tag is on local VFR code if you have a 3 letter destination on the Y pad you can F9 enter and it will spit out a NAS FP. Not sure if you need A/C type in the H pad as well.
I think it's F9, splat, alt, slew-enter. Not sure if putting a requested altitude on the tag would make it so you don't need to type it in again.
 
I think it's F9, splat, alt, slew-enter. Not sure if putting a requested altitude on the tag would make it so you don't need to type it in again.
++### puts the requested altitude in the datablock.
F9 slew enter will generate a NAS code with the datablock altitude in the NAS plan.
I've never tried your way, so I have no idea.
 
++### puts the requested altitude in the datablock.
F9 slew enter will generate a NAS code with the datablock altitude in the NAS plan.
I've never tried your way, so I have no idea.
Will they stay on that local code or does F9 generate a new code from the centers bank?
 
*F then slew enter enter (double click) to get the nearest fix.
To change the callsign (tagged up and owned by you): *N12345 slew enter. Instead of MultiFunc Mod.
To give a current track a new IFR beacon code: MultiFunc, Mod, +, slew enter. For VFR same thing, except the / VFR key.
Call sign thing doesn't work like that on our stars without multi func modify. Pretty sure some facility I worked at before did though.
 
Back
Top Bottom