Hello all!

After flying the 777 for almost a year, I recently noticed that my custom waypoints were being 'ignored'.

I have, for as long as I've flown the 777, successfully entered multiple custom waypoints in the (example) format: " JSV034/20 " ('JSV' being a VOR, '034' the bearing and '20' the distance.)

 

Since I installed SP1C, the FMC will accept custom waypoint entry only once, but then if I decide to insert another, it is simply 'ignored'. (without the display of "INVALID ENTRY" or anything like that).

Note: I have tried this entry into the LEGS page, RTE page and FIX page. and still experience the same problem.

 

Any help or advice on this problem will be greatly appreciated!

 

Thanks in advance

 

Clayton

The only time I have a problem with custom waypoint entry is if the leg in connected to a VECTORS leg as in a STAR. Otherwise, I've not run into this problem.

 

 

Since I installed SP1C, the FMC will accept custom waypoint entry only once, but then if I decide to insert another, it is simply 'ignored'. (without the display of "INVALID ENTRY" or anything like that).
Note: I have tried this entry into the LEGS page, RTE page and FIX page. and still experience the same problem.

 

I haven't seen this, along with Dan. Can you provide a specific, step-by-step example of what you're doing?

I have encountered the vectors in a STAR rule, but this time it was during a SID. (Could that be the problem?)

 

I entered the waypoint in the format as shown in the original post, in order to comply with a SID. Without having pressed EXEC I realised I had made a small error and tried to correct it by a re-entry. This is when my entry was ignored.

 

I find it interesting how the FMC will allow one entry but even if it is deleted, a second will be ignored.

 

Thanks for the replies!

Clayton

 

 

I have encountered the vectors in a STAR rule, but this time it was during a SID. (Could that be the problem?)

 

What "rule?"

 

Any time you do things around (VECTORS) entries, there will be some difficulty, but it depends on what you're doing. Doesn't matter if it's SID or STAR.

 

 

 

I find it interesting how the FMC will allow one entry but even if it is deleted, a second will be ignored.

 

I'm not entirely sure this is the case.

 

Please give us step-by-step instructions of what you were attempting to do. My bet is that you're just trying to do something that isn't allowed in the first place.

 

(For the record, you should NOT be entering expected vectors as legs on the FMC - fly them in HDG SEL.)

 

What "rule?"

I was referring to: (I didn't know how else to explain) 

should NOT be entering expected vectors as legs on the FMC - fly them in HDG SEL.)

-Which I know very well so that is not a problem, but here's what I did:

 

Parked at UUDD, expected to depart RW14L and fly DK14L departure. 'DK14L' was not available in the FMC - as it was shown on an outdated chart that I had. So I decided to follow the chart and manually enter the missing info-Which consisted only of:

climb on 136* track, Right turn at DMD 4.9 DME on to a bearing of 214*, to the DK NDB.

I selected the departure runway, then selected the closest "DK" SID to the one I was to follow, and added the 'DMD 4.9 DME' waypoint into the FMC. Realising I made a small error, I deleted it and attempted to re-enter it EXACTLY how and where it was before. This time, it was not accepted. So I had to fly the SID manually- ignoring the FD with VOR on the ND selected.

 

Note: I have not updated my FMS data in a while, so some procedures may have changed.

 

I hope this bit of info helps.

Thanks for all the help

Clayton

I would have flown HDG SEL 136 (you sure instructions were fly 'track' and not fly 'heading?'), used FIX to put a 5 nm circle around DMD, and placed the first fix in the FMS as DK.  I'm not sure you are able to enter tenths of miles, and maybe that is the obstacle.

you sure instructions were fly 'track' and not fly 'heading?'

Strangely enough, definitely track

 

 I'm not sure you are able to enter tenths of miles, and maybe that is the obstacle.

 

Aha! You've caught me! I must've firstly entered distance '/5' , then tried to change it to '/4.9' - My fault!

 

Thanks to everyone for their help, and apologies for my ignorance!

 

 

Strangely enough, definitely track

 

I mean...let's be real...there was a video that went around the aviation community the other day where people in that area of the world got out of the plane and pushed it back to assist the tug because it was all iced in...

 

I don't think there's anything standard about the place, so I'm not at all surprised by the use of track.

 

 

 

Thanks to everyone for their help, and apologies for my ignorance!

 

Glad you got that sorted. I'd planned on jumping into the sim to see what happened when I did it, but hadn't gotten around to it.