HELP for the definition of the POINTS and ROUTE (Navigation Box)
 This page will help you determine the best way to build your ROUTE definition for your cross-country flight.
A ROUTE is defined as a succession of at least two POINTS.
POINTS can be simply defined by their name (ICAO or text), but the syntax can be more complex if you want to use all the features of JpRNavMaster, for example, specifying FL or Altitude, En route points, or explicit Region or Country codes.
The following documentation is a summary of the most typical cases you will meet while defining your ROUTE.
The basic syntax which consists in merely entering a route with ICAO CODES ¹ or NAMES on successive lines is appropriate for most of the cases.
The syntax with subfields (using ".") is reserved for tricky cases.
¹ IATA (3 letters) codes are NOT accepted
Default REGION selection (except for "Flash" version, default="L")
This selection gives the system an indication to narrow the scope of the search.
It is only used when specifying NAMES or when duplicate NAVAID CODES are specified (same Navaid code in different countries). You should normally set this selection to your most often used Region, eg: E for UK and northern Europe.
To do so, just select a Region in the Default Region combo box.
Note: you can easily display all the Countries corresponding to the selected Region just by clicking on the [Countries] button.
NEW: You can add comment lines at any point of your route
(as many lines as you want)
EGJJ$Fire: 121.6$GND: Summer only
On the SAME line

Comments BEHIND dollar sign 		► Will add two lines for this step on your Flight Log:
Fire: 121.6
GND: Summer only

and also (handy on departure or arrival):
$PARAM or $P to reserve room to note the Parameters (Rwy, QNH, ...)
$ATIS or $A to reserve room to note an ATIS
1) Simple and Standard Format for the ROUTE
(fastest response time)
EGKA
SFD
EGMD		 ► Defines a ROUTE with ICAO codes from Shoreham AD to Lydd AD via the SFD VOR
2) Entering ROUTE Points by  NAME
The system searches in the database points containing the indicated string of characters. Duplicates can be found.
Note: Format 1) and 2) can be mixed
shoreham
Seaford
Lydd

london
lydd


► Defines a ROUTE from Shoreham AD to Lydd AD via the Seaford VOR


► Defines a ROUTE from London AD to Lydd AD
Proposes multiple choices for London and retains directly Lydd (as it is a unique Name as an AD).
Note that to retain The Lydd VOR, you should indicate Lydd.N instead (see below subfield syntax for more details)
3) Defining a POINT with FL/Alt. and / or "En route" code
Syntax: Code or Name!FLxx or xxxxFt!AD or NavAid CODE
Only FL:
EGKA!FL25 or EGKA!25

Only Altitude
EGKA!2500Ft or
EGKA!2500

Only En route CODE:
EGKA!!SFD

FL/ALt AND En route Pt:
EGKA!FL25!SFD or
EGKA!25!SFD

 ► Field #1: Code ou Name as usual
► Field #2: will display the Flight Level (FL) or the Altitude (Ft). If only a digit is specified, the system will use FL if less than 250, Ft otherwise.
► Field #3: "en route" code, will display in the Flight Log the Name and frequencies corresponding to this code.

Remark: if the QDR/Distance check box of the main form is ticked, an additional line in the flight log will indicate the QDR and the distance from the en route point (and the QDM as well).
If Field #3 does not match any data base CODE, the text will be displayed as a comment in the right part of the flight log (60 char. maximum).
Remarks on the Search engine:
A First search is done assuming that a CODE is entered.
If nothing is found, subsequent searches are done by NAME
Successive searches are done on the 6 TYPES OF POINT existing in the DataBase and in this order:
Airport, Navaids, Visual Reporting Point,
Microlight Airfields, WayPoint, Town and cities (France only)
The search stops as soon as at least one point is found.
The following syntax allows to narrow the search by precising the COUNTRY and or the POINT TYPE
(and even the french  "Departement" or States (US) for certain types of point).
4.1) POINT format with 2 subfields
Syntax: Country code.NAME or CODE.
 This format is usable with all TYPES OF POINT.
For the two following formats, the system try to guess which to use by analyzing the contain of the fields.
LF.RBT

EG.SFD
EB.St-Hubert 		► Rambouillet VOR, and not the RBT Navaid in
   Morocco (GM) which exists with the same code.
► Seaford VOR in UK
► Airfield of St-Hubert en Belgium.
4.2 Format POINT with 2 subfields
Syntax: NAME or CODE.TYPE OF POINT.
 Meaning of the suffix TYPE OF POINT:
A=Airport, N=Navaid, P=Visual Reporting Point,
U=Microlight airfield, V=Town or City(in France), W=WayPoint.
SHOREHAM.A
SFD.N
Pontoise.P

Vigneux.U
Beauvais.V
MERUE.W 		► Shoreham Airport
► Seaford Navaid (SFD code)
► Visual Reporting Points for Pontoise
   (they will all be displayed)
► Microlight airfield of Vigneux
► City of Beauvais (not the airport, nor the VOR)
► MERUE Waypoint
4.3) Format POINT with 3 subfields
Syntax: REGION/COUNTRY.NAME or CODE.TYPE OF POINT.
 This syntax allows to specify a search in a REGION or a COUNTRY and a TYPE OF POINT.
EG.SFD.N
E.London
 		► Seaford Navaid, in the EG country (UK)
► Name of an airport containing London and located
    in the E REGION.
4.4) Format POINT with 2 or 3 subfields + DEPARTEMENT or State in the suffix
Syntax: Country Code.Name or Code.Point Type + Département The code of the "departement" (or states for US) is indicated BEHIND the type of point. This more comprehensive syntax allows to specify a "departement" or an US state when searchnig a point.
 Warning: it only works for FRANCE and United States
and for A, U and V type POINT only.
Avignon.A30




LF.Beaumont.U82


city.Aut


 		► Specifies that you are searching for an airport containing the string of characters "Avignon", in the département of the GARD (N° 30).
Will retrieve Avignon Pujault but NOT Avignon Caumont (dept N° 84)

► Will search in FRANCE for a microlight aircraft airfield containing the string Beaumont and in the departement 82. Retrieves "Beaumont de Lomagne".

► Will search for a Airport name containing the string "city" in the State UTAH (UT).
Will actually propose Cedar City rgnl and Salt Lake City Intl and retains one of them for the navigation (changeable).
5) Specific ROUTE definition when crossing a border:
If successive countries of route points are situated in the same REGION, no ambiguity. Ex: points in France (LF), then in Spain (LE), Italy (LI) etc...
However, if successive points are located in different countries AND the points does not explicitely determines the country, then you must prefix the point with the REGION CODE. See some examples below.
LFPT
EBSU 		Will allways works, Region code can be retrieved by analyzing the code (L, B).
LFPT
Shoreham
LFPT
SFD 		The second step does not indicate explicitely in which country or Region is located (even though you can guess it!)
- Will NOT work if default region is  "L"
- Will work if the default region is "E" (use the scrolling Region List to change default Region)
LFPT
EG.Shoreham

 LFPT
EG.SFD

DPE
E.SFD

LFPT
EG.SFD
Shoreham

LFPT
EBSU
Oostende 		Assuming default region is "L"
All these routes are correctly specified.
All border crossing are explicitely specified by a Country or a Region prefix, or by an 4 letters ICAO code.
Note also that the system keeps in memory the last Region or Country used. There is no need to prefix all successive points for a cross country flight continuing in the same country.
6) Use of  "Jokers" (wild characters):
Standard Jokers are authorized for all fields, but are generally useful only for the Name field (not for prefixes and suffixes).


Toulouse B%


St-?al
 		Jokers % or * = begins or ends with...
Jokers _ or ? replace just ONE character

► Will propose Toulouse Blagnac and Toulouse Bourg St Bernard, one of them taken by default (but changeable)
► Will propose St-Galmier and St-Valéry (for the "L" Region), one of them being taken by default.
Your own points can be added in JpRNavMaster:
Just fill this form!