Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Question about phrasing navigation orders

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Question about phrasing navigation orders Page: [1]
Login
Message << Older Topic   Newer Topic >>
Question about phrasing navigation orders - 1/16/2016 12:35:06 AM   
Mgellis


Posts: 2054
Joined: 8/18/2007
Status: offline
Quick question...

When you direct a unit to a particular lat/long location, how should that be phrased in the briefing text or in special messages? Is it...

PROCEED TO 24°30'N, 162°15'W

or should it be phrased some other way?

Thanks.

Post #: 1
RE: Question about phrasing navigation orders - 1/16/2016 12:54:42 AM   
Rory Noonan

 

Posts: 2816
Joined: 12/18/2014
From: Brooklyn, NY
Status: offline
Proceed makes sense but doesn't imply anything else regarding speed or other actions on the way.

'Make best speed' 'Proceed with caution' etc would add more clarity to the commanders intent.

(in reply to Mgellis)
Post #: 2
RE: Question about phrasing navigation orders - 1/16/2016 1:00:08 AM   
Mgellis


Posts: 2054
Joined: 8/18/2007
Status: offline
What about the way the lat/long location is phrased? Is that the right way to do it? Thanks.


(in reply to Rory Noonan)
Post #: 3
RE: Question about phrasing navigation orders - 1/16/2016 1:01:59 AM   
ckfinite

 

Posts: 377
Joined: 7/20/2013
Status: offline
I'm happy with the lat/lon position, but I would strongly suggest putting in a marker/RP where you want the player to go. Otherwise it's too easy to forget/miss.

(in reply to Mgellis)
Post #: 4
RE: Question about phrasing navigation orders - 1/16/2016 2:36:14 AM   
Rory Noonan

 

Posts: 2816
Joined: 12/18/2014
From: Brooklyn, NY
Status: offline
Agreed, it's annoying when you miss or close a message and can't easily get hold of the (usually vital) position

(in reply to ckfinite)
Post #: 5
RE: Question about phrasing navigation orders - 1/16/2016 10:50:53 AM   
Gunner98

 

Posts: 5508
Joined: 4/29/2005
From: The Great White North!
Status: offline
Agree with the marker or Ref Point.

Generally, you would give the direction with a bit more info, baseline is to talk 'Unit, Task, Purpose' so that some thought or planning can be conducted by that unit.

So: Task Group xxxx, 'PROCEED TO 24°30'N, 162°15'W', [to/for/in order to] (intercept, rendezvous, show of force, conduct XXX task etc)

Whenever possible units shouldn't be directed to a pinpoint location unless it’s a single ship or small group of AC, that gives the subordinate commander some latitude to conduct the operation indicated with some degree of freedom. Using terms like: IVO (in vacinity of), area of, within XX miles/Km of, etc helps.


B

(in reply to Rory Noonan)
Post #: 6
RE: Question about phrasing navigation orders - 1/16/2016 11:19:17 AM   
Dysta


Posts: 1909
Joined: 8/8/2015
Status: offline
"All, move to 012987." *Beep Beep*

Yeah, I hardly ever heard a proper and simple orders for make units moving by radio communication.

(in reply to Gunner98)
Post #: 7
RE: Question about phrasing navigation orders - 1/23/2016 6:22:35 PM   
PaulCharl

 

Posts: 10
Joined: 1/22/2016
Status: offline
Generally, in the UK forces nav points are given "Eastings before Northings" so Longitude first, then Latitude, similarly with 6 or 8 digit map grid-references.

(in reply to Dysta)
Post #: 8
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Question about phrasing navigation orders Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

1.346