First off I just want to say that this is a great product and as long as I'm using MSFS, RC4 or later will always be on. As a real world controller, MS ATC has always annoyed me. Anyways, my question. I've read the manual and understand that under the General Options button I can choose under "Holding" 1. Off 2. Weather or 3. On. I've had "On" selected for my last 2 flights (LAX-IAH) and (IAH-MKE) and both times I wasn't given any holding instructions or options for delay vectors or anything. Instead I was told to start my descent at 200nm from the airport and by 120nm I'm already down to 15,000 and still on my published course. I use FSBuild to make my flight plans and I always fly either the PMDG 737-800 or PMDG 747-400. For these two flights I was using the 737. Am I doing something wrong or did I just have bad luck with my last two flights? Thanks for any comments.Shaun HarperUSN Air Intercept Control Supervisor

had to check the code for that oneis the last checkpoint a vor? it has to be for holding set to on, to trigger a holdand the last checkpoint (a vor) has to be within 10 miles of the arrival airportjd

JD,Thanks for the fast reply. The answer is no. I just checked both flight plans and the closest VOR to the airports was like 40nm or something like that. On the LAX-IAH flight plan I had a fix (not a VOR) 6nm from the aiport. So, if I understand correctly, I must have a VOR within 10nm for the hold feature to work? Thanks again.v/rShaun Harper

yep. i can't tell you to fly on radials of ndbs or intersections. and if it isn't within 10 miles of the airport, you might encroach into approach airspace as part of your holding patternjd

>yep. i can't tell you to fly on radials of ndbs or>intersections. and if it isn't within 10 miles of the airport,>you might encroach into approach airspace as part of your>holding patternIt doesn't seem likely to have many VORs within 10nm of an airport that would be on an approach path. Would a VOR nearly co-located with the airport work? For exmaple my post on the hold at SNS inbound to KOAK. How about putting on the feature wish list the ability to hold at any published STAR hold? Not sure if the databases document hold points but...Or maybe a RC menu request to hold at next waypoint or a hold at a random waypoint.Or a hold at a DME off any VOR that should be within range - perhaps on a radial offset from the airway if the problem is conficts with other inbound traffic. Or the VOR-DME hold could be close in where you'd like it to be, it would just be an offset from the previous VOR instead of at/off of the next VOR.I'm just full of it.... er full of em! :-roll

forward 'em to [email protected] - it might be implementedjd