Can someone confirm this assumption about L/L CDU data entry?

[Bahger]

I had a bad time today failing to find targets at briefed lat/long coordinates. In each case, the coordinate, outputted from the ME, had been adapted by dividing the seconds value (i.e. the final value of each coordinate) by 60, as I believe the CDU will not accept seconds, only minutes and decimal fractions of minutes. In-flight I used the CDU WP page to copy the current WP, name the new one and enter the coordinates in L/L mode before switching to "Mission" with the nav mode rotary to cycle my new WPs in the HUD. They appeared, and seemed to be correctly placed, but I could not slave the TGP to them as usual and find the target nearby.

 

Am I forgetting something simple here?

[Fish]

Here's what i do

WP page,

WP option,

input LL (as called, add leading zero for longitude). on scratch pad, OSB 17 followed by osb16,

when detail is entered correctly, click the OSB9 to add as waypoint, (note the wp number first)

steerpoint switch to mission,

Hud soi, dms up/down to select the waypoint.

TAD, soi, zoom out, hook the marker,

DMS up long to make it spi.

 

(hope i included everyting)

[Frostiken]

I had this problem as well and as Fish I discovered that using the TAD worked. Even though I had the waypoint as my steerpoint and made the HUD the SOI, the TPod would only slew to the LAST SOI mark.

[Bahger]

ooohhhhh... So instead of expecting the TGP to slave to the mission point as it would to a markpoint or a flightplan waypoint, I should make the mission point the SPI in the TAD, i.e. "hook" it...?

 

(Fish, that would be TMS not DMS up long, right?)

[Frostiken]

You shouldn't have to hook anything, just put the cursor on it and TMS up.

 

 

 

 

I think.