If you set up a route in your FMC and do everything else like INIT REF etc go to your HOLD page enter a NDB or waypoint near you and place it in the square boxes. This NDB or waypoint can't be PART OF THE ROUTE. Now you should get a message saying HOLD AT EDN. Try go to the legs page and it should say PROGRAM PIN ERROR. And your LEGS page is blank except <FMC and <REQ>

Not one person???

Perhaps the experts are too busy right now?

But surely someone can confirm there FMC does this too?

Hi Vernon,

 

I've just tried it. It didn't work intuitively, so then I looked in the FCOM to find out how it should be done.   After it shows HOLD AT XXXXX in the scratchpad you have to line select that into the required sequence in the LEGS page. Then it will show the MOD RTE HOLD page, which you can adjust the entry with. Then execute and it's active.

 

Even when I was doing it wrong it never showed PROGRAM PIN ERROR or wiped the route as you experienced.

Thanks kevin for your time not alot of people like that !!!

No problem. I learned something too so it was time well spent.

Cheers kevin

I'm not saying you haven't found a problem Vernon, and I can't remember trying what you describe in either the ngx or the real plane so I can't verify behavior. But the reason I don't think I've done it before is because I can't envision why I'd want to enter a hold at a fix I'm not already navigating to. In the real world, holding clearances are issued like "Legacy 105, cleared direct BTG, hold as published..." etc. So even if it's a fix not currently on your route, it just makes sense to punch it in and get flying in the proper direction first, and THEN worry about setting up the hold... at a fix that is now on your route. I'm not saying there isn't someone out there that does it a different way, but that kinda makes the most sense.

 

So even if it is a sim problem, maybe it's self-correcting. Just get navigating towards the fix first, then enter the hold?

Hi andrew it was my EOSID holding point. I'm currently hammering non normals on takeoff

Ahh ok that does make sense, yeah we have a different system that auto populates the EO Sid if necessary so I've never built a hold at a fix I wasn't navigating to. So I'm no help here, sorry...