12DEC03

PMDG Customer,

As a normal part of the product development cycle, PMDG has assembled a team of very dedicated
and knowledgeable individuals to assist us with testing and validation. In most products on the
market today, the Beta Team plays a key role ensuring product quality, fitness and form. Our Beta
Team has been hand picked to provide a broad range of flying, dispatch, systems, operational,
software and simulation experience in order to best represent the customer base while also add to
the overall expertise of the development process.

At PMDG, we place a tremendous amount of responsibility on our Beta Team, and we provide them
with virtually unfettered access to the entire PMDG development team for suggestions, assistance
and critical review of works in progress.

As a result of this process our testers occasionally produce work that will ultimately be of benefit to
the entire PMDG customer community. With this version of the PMDG 737, we have elected to
include work that was produced by our beta team as we felt their efforts were worthy of note- and of
significant benefit to the entire community.

Randy Smith has produced some artwork edits that we elected to include in the final panel design.
Randys has served to push the development team to make difficult visual fixes that we would not
otherwise have undertaken, sometimes by demonstrating the aesthetic appeal by making those
changes himself. Thank you Randy!

Terry Yingling was frustrated by the lack of SID/STARs available for use with the PMDG 737,
especially when we started advancing the capability of the FMC to include greater functionality. As a
result, Terry undertook to develop a method to produce and distribute nearly 1200 individual
SID/STAR combinations for use by the Beta Team during testing. As development continued, his
database became the de-facto database for all Beta Team members, and we have elected to include
it with the release version of the airplane as a starter set for all PMDG customers. To encourage
the user community to write more SID/STARs, Terry has written the following How To Guide that is
included as an appendix to our user manual. It is a fine tutorial that we hope all of you will use!

While PMDG will provide any needed support for this database, users should recognize that this
database is provided as the work of a PMDG Beta Tester and exists solely as a result of the
dedication of our entire Beta Test Team.

Please be sure to thank them for their support of this product, and the simming community!

The Development Team

Precision Manuals Development Group
http://www.precisionmanuals.com

1
 Making SIDs and STARs
For the PMDG 737NG 600/700
By
Terry Yingling
12 Dec 03

This is a tutorial I wrote for myself. Sometimes the best way Example: FIX DOPIE COLOCATED NRT 256 20
to learn something is to try and teach it. It works. This
tutorial is written for the beginner but hopefully have some This means you are defining a fix called DOPIE which is on
advanced stuff for the experts. I will take you through the the navaid NRT radial 256 and is 20 miles from NRT.
process of making Standard Instrument Departures (SID),
Standard Instrument Arrivals (STAR) and Instrument The second way to define a fix is:
Approach Procedures (IAP) as they apply to the PMDG
737NG, SU2 updated aircraft. Collectively SIDs, STARs and FIX NAME LATLON N/S DEG MIN E/W DEG MIN
IAPs are called procedures so when I say procedures I am
referring to any one or all of them. When you finish this This fix definition defines a point on the earth based on a
tutorial you should have the mental tools to create procedures latitude and longitude. NAME is the fix name ID. N/S and
or modify them. E/W are north or south latitude and east or west longitude.
The DEG is a integer degrees and the MIN is decimal minutes.
I. A few definitions
Example: FIX EAGER LATLON N 34 23.6 E 12 3.4
NAVAIDs A generic word that PMDG uses to refer to
radio navaids such as VORs, ADFs, DMEs, Localizers, This means you are defining a fix called EAGER at Latitude
Intersections and Fixes, etc. These navaids are listed in the 34 degrees, 23.6 minutes North by Longitude 12 degrees, 3.4
AIRAC data the PMDG 737NG and the 767 PIC use. minutes East.

FIXes Whenever you have to define a waypoint, or even a RNWS. This is simple. Just list the runways to be used at the
missing radio navaid, it is called a FIX. airport between the RNWS and ENDRNWS keywords. Make
sure though all runway numbers use two digits, like 05 and
GATEs These are the aircraft parking positions at the 09L.
airport terminal.
Example: RNWS
KEYWORD These are words the FMC looks for and reads RNW 19L
that define a command and let it know what to do. In the RNW 27
procedure command definitions below the keywords are ENDRNWS
written in uppercase bold lettering in this tutorial.
There are eight commands available to define a SID, STAR
[ ] Optional parts of a command are enclosed in brackets. or IAP route.
Do not include the brackets when writing procedures.
1. [DIRECT] NAVAID [OVERFLY] NAME [ALT] [SPEED
KTS]
II. Commands, The Building Blocks The optional keyword DIRECT is used to have the plane fly
direct to the NAVAID. NAME is a navaid ID or fix name.
FIXES. Fixes are user defined waypoints. Wherever you see ALT is an optional altitude and SPEED KTS is an optional
the word NAVAID in one of the following eight command airspeed in Kts. The keyword OVERFLY is optional. If not
definitions you can substitute the keyword FIX. There are used then this command defaults to fly-by. Most NAVAIDs
two ways to define fixes. Here is the syntax for one way. are fly-by but you should consider using OVERFLY anytime
you want to insure the plane goes over a waypoint or when
FIX NAME COLOCATED NAME RADIAL DISTANCE required by the procedure.

This definition defines a point on the earth based on a distance Examples: NAVAID OVERFLY RUP SPEED 250
and direction from a navaid or fix. The first NAME is FIX THY 3500 SPEED 230
generally a 5 letter, or less, fix name you make up. The DIRECT FIX ABC
NAME RADIAL DISTANCE is the navaid ID code, the radial
number the fix is on and the distance from that navaid in The first example simply means to fly-over navaid RUP
nautical miles. Radials can be used from fixes also so if you without any altitude considerations and at an airspeed of 250
use a fix just pretend it is a radio navaid. Kts.

2
The second example means to fly-by fix THY but arrive there In the first example the plane will fly a heading of 230 until
at 3500 feet and 230 Kts. the pilot receives further instructions from ATC.

The 3rd example has the plane fly direct to fix ABC. In the second example the plane will keep whatever heading it
already has until the pilot receives further instructions from
Fly-by means that the plane will fly toward the navaid or fix ATC.
but turn just before reaching it so it can intercept the course to
the next navaid or fix. Fly-over means the plane will fly over The third example make the plane follow a ground track or
the navaid or fix before it turns to the next waypoint. course of 134 degrees until the pilot receives further
instructions from ATC.
The DIRECT keyword needs a little explanation. But first,
how does the plane go from waypoint to waypoint? It does it The use of vectors has a gotsha. The plane will fly the
by the FMC calculating a course line between the waypoints. heading or track until it runs out of fuel unless the pilot enters
(See illustration below. Note flight path shown is under zero a direct to on line one in the routes page of the FMC and
wind conditions.) The FMC will then try to keep the plane on then executes it. There is no actual interaction with the flight
this course line. For example if you use a fly-over waypoint sim ATC.
the plane will fly over the waypoint (HANDL) and then not
only turn toward the next waypoint (BOOIE) but will extend 3. HDG UNTIL ALT [SPEED KTS] or
the turn so it can intercept and get back on the course line to KEEP HDG UNTIL ALT [SPEED KTS]
that next waypoint. (Example A) By contrast, when the
DIRECT keyword is used the FMC will ignore the course line Where HDG is a heading or track and ALT is an altitude. The
and just fly direct to the next waypoint. (Example B) SPEED KTS is an optional entry.

Example: HDG 210 UNTIL 3500 SPEED 230

KEEP HDG UNTIL 7000

The first example is a floating waypoint that is attained by

flying 210 degrees at 230 Kts and reaching 3500 feet altitude.

The second floating waypoint example says to keep whatever

heading the plane already has and fly that heading until
reaching 7000 feet.
Example A Example B
Fly-By Direct I might mention here that there is a limitation in the command
syntax which is that only AT altitude restrictions are
currently used in the commands. I fudge a little here though.
You could ignore altitude restrictions or fudge like I do. For a
2. HDG VECTORS restriction of between 3000 and 7000, I would average the two
altitudes and use AT 5000. I ignore the AT and Above and
This command simply tells the FMC to fly the plane on the the At and Below.
specified heading or track until the pilot executes a direct to
from the FMC. It is used to simulate getting ATC vectors. 4. HDG UNTIL ALT NOT BEFORE DIST FROM NAVAID
[SPEED KTS]
A few words about HDG. (This applies to all uses of HDG in
other commands below.) HDG can be one of four entries, Where HDG can be, as in 2 above, either a HDG XXX or
HDG degrees, KEEP HDG, TRK degrees and KEEP TRK. KEEP HDG or TRK or KEEP TRK. ALT is an altitude,
The first two use a heading in degrees and refer to the DIST is distance in NM from the navaid and NAVAID is a
magnetic heading the plane will fly. The second two use navaid or fix name. The SPEED KTS is an optional airspeed
degrees also but refer to the ground track or course the plane entry.
will follow.
Examples: HDG 120 UNTIL 3000 NOT BEFORE 15
Note: When using a HDG degrees or KEEP HDG the planes FROM FIX BIGGY SPEED 250
course will be changed by the wind direction and speed.
Using TRK degrees or KEEP TRK will keep the plane on a This defines a floating waypoint that is reached when flying a
course and correct for the wind affects. heading of 120 degrees at 250 Kts, reaching 3000 feet and the
aircraft is 15 NM from user defined fix BIGGY.
Examples: HDG 230 VECTORS
KEEP HDG VECTORS Note: If the altitude is reached before the distance constraint
TRK 134 VECTORS is reached the aircraft may continue to climb higher.

3
5. HDG UNTIL DIST FROM NAVAID [SPEED KTS] is a factor. It is possible that a south wind could push the
plane far enough north to make the intercept fail. Using TRK
Where HDG can be, as in 2 above. DIST is distance in NM instead or better yet, using the command NAVAID ABC
from the navaid and NAVAID is the navaid ID or a fix name. would be a better solution.
The SPEED KTS is an optional airspeed.

Examples: HDG 20 UNTIL 25 FROM NAVAID FFU

This defines a waypoint that is reached when flying a heading

of 20 degrees and the aircraft is 25 NM from navaid FFU.

6. HDG UNTIL RADIAL NUMBER TO/FROM NAVAID

[SPEED KTS]

Where, again, HDG can be either HDG degrees or KEEP

HDG or TRK degrees or KEEP TRK. NUMBER is the
radial number of the navaid or fix. SPEED KTS is an optional
airspeed entry. Use this command when you want the plane to The TO keyword is another option. Id guess its use just
fly-over the radial intersection point. Remember, as in all the depends on personal preference as the end result is the same as
commands, that the navaid does not have to be a radio navaid, using the FROM. For example the following two commands
it can be a fix. produce the same radial intersection.

The TO or FROM keywords can be confusing. If you think HDG 345 UNTIL RADIAL 90 TO NAVAID SGY
in terms of the real world definition of a radial you would use HDG 345 UNTIL RADIAL 270 FROM NAVAID SGY
the FROM keyword. For example:

HDG 345 UNTIL RADIAL 260 FROM NAVAID SGY

SPEED 200

This means that the plane, at 200 Kts, will fly over the point
where the flight path of heading of 345 crosses over the 260
radial of SGY.

Keep in mind that the course of the plane MUST cross over
the radial specified or you will not get an intercept. If for
example you are Southeast of VOR ABC, heading North and
you write the command to cross the 270 radial, you will get a
leg of many thousand miles because you could not fly over the
270 radial from your current location and heading.

Notice the radial number used with the TO keyword is the

reciprocal of the radial used with the FROM keyword. Use
whichever makes most sense to you.

7. HDG INTERCEPT RADIAL NUMBER TO/FROM

NAVAID [SPEED KTS]

Where again HDG can be either HDG degrees or KEEP

HDG or a track in degrees or KEEP TRK. NUMBER is the
radial number of the navaid or fix. The SPEED KTS is an
optional entry. Use this command when you want the plane to
fly-by or start turning toward the next waypoint just before the
radial intersection point is reached. The TO and FROM
keywords are used the same as the previous command (6)
above.

Another example would be if you used HDG 90 UNTIL Examples: HDG 350 INTERCEPT RADIAL 90 FROM
RADIAL 180 FROM NAVAID ABC. Lets presume your NAVAID RTY
previous waypoint was another NAVAID that happens to be
on the 270 radial of navaid ABC. It looks OK to use this KEEP TRK INTERCEPT RADIAL 145 TO
command however it could fail. Since HDG is used, the wind NAVAID WWE SPEED 210
4
The first example defines a waypoint which is reached when SIDS
flying a heading of 350 degrees and the 90 degree radial of SID SID_Name SID_Commands Runway_Commands
navaid RTY is intercepted. Enroute_Transition_Commands
ENDSIDS
The second example defines a waypoint that is reached by STARS
keeping the current track at 210 Kts and intercepting the 325 STAR STAR_Name STAR_Commands
degree radial of navaid WWE. (That tricky TO keyword) Enroute_Transition_Commands Runways
ENDSTARS
8. HOLD AT NAVAID NAME DIRECTION TURN
INBOUNDCOURSE NUMBER [ALT Ft] [SPEED APPROACHES
SPEED] [LEGDIST/LEGTIME NUMBER] APPROACH Name Approach_Commands Runway
Missed_Approach_Commands Transition_Commands
This command defines a holding pattern. The first NAME is ENDAPPROACHES
the navaid or fix name. The DIRECTION is LEFT or RIGHT
turns around the hold pattern. The second NUMBER is the fix GATES
inbound heading. ALT Ft is an optional altitude in feet. Gates List
SPEED KTS is an optional airspeed. LEGDIST/LEGTIME ENDGATES
NUMBER is optional. The NUMBER is either a distance in
NM or a time in minutes depending on the keyword. Use 1. The first section is for optional comments and starts a line
LEGDIST for a leg distance and LEGTIME for a timed leg. with two slashes, //. Everything on that line after the slashes
If this keyword is left blank the FMC will default to is a comment and is ignored by the FMC. There is no limit on
LEGTIME with one of two time values depending on the number of comment lines but dont go overboard. This
altitude. Above 14,000 feet, 1.5 minutes and if below 14,000 section can be omitted.
feet 1 minute.
2. FIXES This section lists all the user defined fixes that are
For example: used in the procedures. If a navaid is not in the AIRAC
database or the FMC finds a FIX keyword in the procedures it
HOLD AT NAVAID ROC RIGHT TURN then looks in this section so it can determine the fix location.
INBOUNDCOURSE 345 ALT 12000 SPEED 180 You have a choice of using FIX ENDFIXES or
LEGDIST 5 CUSTOMFIXES ENDCUSTOMFIXES. Use whichever
HOLD AT NAVAID QRT LEFT TURN you like. The ENDFIXES or ENDCUSTOMFIXES
INBOUNDCOURSE 145 LEGTIME 1 keyword lets the FMC know that it has reached the end of the
fixes definitions. This section can be empty but only if all
The first example creates a hold at navaid ROC which has an navaids used in the procedures can be found in the AIRAC
inbound course of 345 degrees. The hold is flown with right database and there are no user defined fixes.
turns at 180 Kts at 12000 Ft with a leg distance of 5 NM.
3. RNWS This section lists all the runways used in the
The second example creates a hold at navaid QRT with an procedures at the airport. The ENDRNWS keyword lets the
inbound course of 145 degrees. The hold is flown with left FMC that it has reached the end of the runways definitions.
turns and with 1 minute legs. This section is required.

III. The Basic Procedure File 4. SIDS This section contains all the SIDs for the airport.
The ENDSIDS keyword lets the FMC that it has reached the
There is one procedures file per airport. The procedures file is end of the SID definitions. This section can be empty if there
composed of six sections. Most sections can be empty but the are no SIDs.
keywords in bold lettering have to be there anyway (except for
the GATES section). Except for the comments section type 5. STARS This section contains all the STARs for the
everything in uppercase letters. The general layout is shown airport. The ENDSTARS keyword lets the FMC that it has
below. reached the end of the STAR definitions. This section can be
empty if there are no STARs.
// Airport ICAO code and name
// Author and date 6. APPROACHES This section contains all the IAPs for the
// Whatever else you want airport. The ENDAPPROACHES keyword lets the FMC
know that it has reached the end of the IAP definitions. This
FIXES or CUSTOMFIXES section can be empty if there are no IAPs.
Fixes Defined
ENDFIXES or ENDCUSTOMFIXES 7. GATES This section contains all the gate locations at the
airport. The ENDGATES keyword lets the FMC know that it
RNWS has reached the end of the gates definitions. This section can
Runways Used be omitted if there are no gates.
ENDRNWS
5
Once a procedures file is created it must be saved as a text file the commands that describe the transition. You must have at
using the airports ICAO as the file name with .TXT as the least one command in a runway transition. Id recommend
file extension. The file must be saved in the typing each runway transition on one line for ease of reading.
/PMDG/SIDSTARS folder within your flight sim folder.
NOTE: If there are no runway transitions in a SID the layout
Examples: KLAX.TXT of the common part and transition part is slightly different.
EDDM.TXT Essentially the common part becomes a runway transition.
Print the SID and SID_Name as usual but do not follow that
IV. Overview of Creating SIDs, STARs by the common part commands. Next put a list of all the
runways used by the SID and follow that by the commands
and Approaches that make up the common part of the SID. (See SIDs CIV5
and BAT2 below.)
The general steps are:
The last section is for the optional enroute transitions with
1. Type any comments you need. Dont forget the double each transition starting with the keyword TRANSITION.
slashes. This keyword is then followed by the commands that make up
the enroute transition. Id recommend typing each enroute
2. Type the FIXES section keywords. For now this section transition on one line also.
can be empty except for the two keywords. Fixes can be
defined after you try running the procedures thru the 737NG Hint: Do not duplicate any of the connecting waypoints
FMC. If a navaid can not be found the FMC will give you an between the three sections of a SID. For example, you do not
error message telling you what navaid it could not find. At need to have the first waypoint of the transition be the same as
this point you can then define that NAVAID as a fix and the last waypoint of the common route.
add it in. On the other hand if you know you are going to
make up a fix for a procedure that you are making, you can Example:
add it now. Once a fix is defined it is then used in a SID or
STAR using the keyword FIX. SIDS
SID CIV6C HDG 250 UNTIL 700 NAVAID BUB07 1700
It is also possible to use a fix in the definition of a collocated RNW 25L KEEP TRK UNTIL 800 NAVAID CIV
fix. For example say you want to define a collocated fix using RNW 25R HDG 253 UNTIL 600
another fix. If you do this make sure that the fix used in the TRANSITION BLH NAVAID PKE NAVAID BLH
collocated definition is defined before the collocated fix as SID CIV5
shown below. RNW 01 NAVAID DOU
SID BAT2
Example: FIXES RNW 19 RNW 21 NAVAID ERT
FIX XYZ LATLON N 44.0 23.3 E 12.0 45.9 TRANSITION HAN NAVAID JJH NAVAID HAN
FIX ABC COLLOCATED XYZ 233 23 ENDSIDS
ENDFIXES
5. Define the STARs in the STARS section. Define all the
3. List in the RNWS section all the runways the SIDs and STARs by stringing together the appropriate commands that
STARs will use. define the route waypoints required. Each STAR can be
composed of up to three parts. A common part, the enroute
Example: RNWS transitions part and a runway listing part.
RNW 27
RNW 09 The common part starts with the keyword STAR, the
ENDRNWS STAR_Name and then the commands that describe the legs of
the common part of the STAR. The common part must have
4. Define all SIDs in the SIDS section. Define all the SIDs by at least one waypoint. Id recommend typing the common
stringing together the appropriate commands that define the part on one line for ease of reading.
route waypoints required. Each SID can be composed of up to
three parts. A common part, the runway transition part and Next comes the enroute transitions section. This starts with
the enroute transitions part, in that order. the keyword TRANSITION, then the transition name and
finally the commands that describe the transition. Id
The common part starts with the keyword SID and the name recommend typing each enroute transition on its own line for
of the SID, then the commands that describe the legs of the ease of reading.
common part of the SID. The common part commands are
optional, but you must have the SID and SID_Name. The last section is a listing of runways used in the STAR and
it is optional. This list is similar to the RNWS ENDRNWS
Next comes a required runway transitions part which starts section in that it just lists all the runways being used. The
with keyword RNW followed by a listing of the runway(s) runways listed here will appear on the FMCs ARR PAGE on
used by the transition. This runway list is then followed by

6
the right side after the approaches list. Id recommend typing
all the runways on one line for ease of reading.

Note: If no runways are listed then the FMC will assume all
runways listed in the RNWS section are compatible with the
star.

Example:

STARS
STAR KOK3A NAVAID KOK NAVAID KERKY 7000
TRANSITION ERT NAVAID RTY FIX TRIAL NAVAID
OVERFLY ERT SPEED 250 NAVAID GHJ NAVAID
UIG 3000
RNW 02 RNW 07R
ENDSTARS

6. Define any IAPs. This is similar to defining a STAR. The

approach section is composed of, well, the approach procedure
and the missed approach procedure. The two parts are
separated by the runway number that the approach is for. The
runway number tells the FMC that the approach is done and
what follows is the missed approach procedure.

Example:

APPROACHES
APPROACH ILS23 NAVAID SDK NAVAID PAS RNW 23
KEEP HDG INTERCEPT RADIAL 90 FROM ABC
HOLD AT NAVAID SDF RIGHT TURN
INBOUNDCOURSE 120 ALT 4000 LEGDIST 5
APPROACH ILS05 NAVAID DFG FIX MAP RNW 05
TRANSITION NORTI FIX GABBY
ENDAPPROACHES

7. Define all gates. The GATES section is used so the pilot

can initialized the planes position when setting up the FMC.
This whole section is optional and may be omitted.

GATE NAME N/S DEG MIN E/W DEG MIN.

Where the NAME is the gate ID. N/S and E/W are north or
south latitude and east or west longitude. The DEG is degrees
and the MIN is decimal minutes.

Example:

GATES
GATE A1 N 47 27.2 E 8 33.7
GATE A2 N 47 27.3 E 8 33.7
ENDGATES

Thats about it for the rules. Lets put them into practice.

7
V. Making SIDs
Lets start making procedures. A procedure is created by
stringing together a series of commands. So lets get down to
business. I will illustrate each of the eight commands so you
can recognize them in a SID or STAR diagram. SIDs first.

I will use the runway 32 departure for the example, a tricky

one. We get to use three different commands with this one.

The turn left at SRQ 0.9 DME lends itself to using:

HDG UNTIL DIST FROM NAVAID [SPEED KTS]

The intercept can use:

HDG INTERCEPT RADIAL NUMBER TO/FROM

NAVAID [SPEED KTS]

One way the complete SID can be written is as follows.

FIXES
ENDFIXES
about 45 degrees so I used 250 degrees. 295 250 = 45
RNWS degree intercept angle. You could use some other angle.
RNW 32
ENDRNWS 2. Why did I use HDG 250 INTERCEPT RADIAL 295
FROM NAVAID SRQ instead of HDG 250 UNTIL
SIDS RADIAL 295 FROM NAVAID SRQ? Recall that one
SID SARASOTA1 command produces a fly-over and the other produces a fly-by
RNW 32 KEEP HDG UNTIL 0.9 FROM NAVAID SRQ result. For this waypoint a fly-over would have put the plane
HDG 250 INTERCEPT RADIAL 295 FROM NAVAID beyond the 295 radial when it turned to heading 295. In this
SRQ HDG 295 VECTORS case the best approximation would be to use a fly-by
ENDSIDS command so the plane would turn before it got to the actual
intersection point. This provides the best chance of getting
STARS close to the 295 radial track needed.
ENDSTARS
3. There is no command to track outbound or inbound on a
radial so the next best thing is to do a track as I did with the
This is one that is deceptively difficult to do accurately. A HDG VECTORS command. The problem is that it only
few things to point out. approximates the outbound course on the radial but, it is good
enough for simming. I used VECTORS because in the SID
1. In the command HDG 250 INTERCEPT RADIAL 295 Description for runway 32 it states to expect vectors once you
FROM NAVAID SRQ I use a heading of 250 degrees. are outbound on radial 295. If you wanted to get closer to
Where did I get that heading? Its not in the SID definition. actually tracking an outbound radial you would create a couple
Well, I made it up. I just wanted to intercept the radial at of fixes on the radial to fly between. The first fix about 2
miles from the intersection and on the radial and the second
maybe 15 miles out and also on the radial. Adjust the
distances to produce the desired result.

8
 Lets complicate things. You can see there is an altitude
restriction of FL200 min at D40 PAS (or D28 SPR) and at
D27 SPR. D40 PAS and D27 SPR dont look like fix names
but Im thinking they might be PAS40 and SPR27. We would
find out by writing the SID and trying it out in the FMC. Lets
do ARBOS3N like so:

FIXES
ENDFIXES

RNWS
RNW 05
ENDRNWS

SIDS
SID ARBOS1P
RNW 05 HDG 46 UNTIL 7000 NOTBEFORE 8 FROM
NAVAID GVA
TRANSITION ARBOS1P HDG 360 INTERCEPT
RADIAL 312 FROM NAVAID SPR NAVAID SIROD
NAVAID PA40 NAVAID ARBOS
TRANSITION ARBOS3N HDG 360 INTERCEPT
RADIAL 331 FROM NAVAID SPR NAVAID SPR27
NAVAID ARBOS
ENDSIDS

STARS
ENDSTARS

If it works, great, otherwise you will get an error message

about PAS40. You would then have to define a fix like so.

FIXES
FIX PAS40 COLOCATED PAS 02 40
FIX SPR27 COLOCATED SPR 331 27
ENDFIXES
I will use the ARBOS 1P departure on this chart. In the
description section you can see this SID has an additional RNWS
restriction right after takeoff, a not before. The HDG RNW 05
UNTIL ALT NOTBEFORE DIST FROM NAVAID was ENDRNWS
written for this sort of thing. So, this is how I would write the
SID. SIDS
SID ARBOS1P
SID ARBOS1P RNW 05 HDG 46 UNTIL 7000 NOTBEFORE 8 FROM
RNW 05 HDG 46 UNTIL 7000 NOTBEFORE 8 FROM NAVAID GVA
NAVAID GVA TRANSITION ARBOS1P HDG 360 INTERCEPT
TRANSITION ARBOS1P HDG 360 INTERCEPT RADIAL 312 FROM NAVAID SPR NAVAID SIROD
RADIAL 312 FROM NAVAID SPR NAVAID SIROD FIX PA40 20000 NAVAID ARBOS
NAVAID PA40 20000 NAVAID ARBOS TRANSITION ARBOS3N HDG 360 INTERCEPT
RADIAL 331 FROM NAVAID SPR FIX SPR27
20000 NAVAID ARBOS
I could have also written it as follows. ENDSIDS

SID ARBOS1P STARS

RNW 05 HDG 46 UNTIL 7000 NOTBEFORE 10.4 ENDSTARS
FROM NAVAID SPR
TRANSITION ARBOS1P HDG 360 INTERCEPT Note: If you continued to complete all the SIDs on the chart
RADIAL 312 FROM NAVAID SPR NAVAID SIROD you would have to include more runways in the RNWS
NAVAID PA40 20000 NAVAID ARBOS section.

9
Next is a SID that illustrates a problem in defining a waypoint.
Lets do POL 5R. Upon examining the SID we see that most
waypoints are easy enough to do but there are two, MCT D7
and MCT D8, that cause a problem. There is no command to
describe them. This means some FIXes have to be made. The
way that I handle this is to use a graphic flight planner
program to find the lat/long of those waypoints. I can then
create a couple of FIXes and away we go.

I happen to use an old program called NAV 3.1 by Ted

Wright. What is useful in this free program is that you can
right click and drag a line from point A to point B and have
the distance and course displayed to you. In the case for
MCT D7 it is a multi part process that Ill explain. MCT D8 is
on a course line of 345 degrees to XUMAT. To get this line
shown on the NAV 3.1 screen map I click on XUMAT and
drag a line down far enough it is below the MCT D3 right
turn. I then move the line left or right until a course of 165
degrees (reciprocal of 345 degrees) is shown. Then I release
the mouse key . This brings up a window that allows me to
create a waypoint, which I do. Why do this? Well, I now
have two waypoints I can use to make a course, or line, on the
map. I do this by adding the XUMAT and the user created
waypoint I just made to the flightplan. This causes the flight
planner to draw a line between the two waypoints. Now I
have the 345 degree course line drawn I can use as a reference.

My next step is to find where MCT D7 is on the course line.

To do this I click on the navaid MCT and drag out the line so The fixes could also have been written as COLOCATED as
the cursor is on the 345 degree course line. I move the cursor shown here if you prefer.
up and down the line until the distance shows as 7 miles.
Releasing the mouse key at this point brings up that waypoint FIXES
creation window again. This time I note the LAT/Long of the FIX MCT7 COLOCATED MCT 296 7
waypoint. This is the LAT/LONG I use to create a fix Ill call FIX MCT8 COLOCATED MCT 303 8
MCT7. I repeat the procedure to find the MCT D8 waypoint ENDFIXES
and there you have it. If you prefer you could also use the
COLOCATED type fix by reading the course when you have One other thing. Notice in this command I used a real world
the cursor over the waypoint desired. Here is the POL5R SID. fix called XUMAT as a real world radio navaid. Perhaps a
little confusing. Real world fixes are different from radio
FIXES navaids but in this command language a fix and a radio navaid
FIX MCT7 LATLON N 53 24.46 W 2 26.13 are interchangeable as a NAVAID.
FIX MCT8 LATLON N 53 25.78 W 2 26.99
ENDFIXES KEEP HDG INTERCEPT RADIAL 165 FROM NAVAID
XUMAT
RNWS
RNW 24R
ENDRNWS This was a SID that used an outside program to get help. I
wanted to illustrate this to show that there is more than one
SIDS way to do the job when the command language does not do
SID POL5R FIX MCT8 KEEP HDG INTERCEPT what you need it to.
RADIAL 221 FROM NAVAID POL TRK 41 UNTIL 16
FROM NAVAID POL KEEP TRK UNTIL 9 FROM
NAVAID POL 5000 NAVAID POL 5000
RNW 24R KEEP TRK UNTIL 757 KEEP TRK UNTIL 3
FROM NAVAID MCT KEEP HDG INTERCEPT
RADIAL 165 FROM NAVAID XUMAT FIX MCT7
2500
ENDSIDS

STARS
ENDSTARS
10
VI. Making STARs
Lets turn our attention to the STAR. I will use SWEED SIX STAR
at KCVG.

// KCVG - Cincinnati Northern Kent

// Created 9/9/2003 by Terry Yingling

FIXES
ENDFIXES

RNWS
RNW 36L
RNW 36R
RNW 27
RNW 09
RNW 18L
RNW 18R
ENDRNWS

SIDS
ENDSIDS

STARS
STAR SWEED6 NAVAID SWEED NAVAID COFCO NAVAID OBBAN 11000 NAVAID FLM NAVAID CVG
TRANSITION HNN NAVAID HNN NAVAID HIINZ
TRANSITION HVQ NAVAID HVQ NAVAID GARZO
TRANSITION HMV NAVAID HMV NAVAID PACKO NAVAID CHEDA NAVAID DRESR
TRANSITION VXV NAVAID VXV NAVAID ARTUR NAVAID CHEDA NAVAID DRESR
RNW 36R RNW 36L RNW 27 RNW 09 RNW 18L RNW 18R KEEP HDG VECTORS
ENDSTARS

These procedures were rather straight forward but there are a vectors to a navaid or radial from the end of the STAR. This
few things to discuss. This is a tutorial after all. is what happened here. The STAR has instructions to expect
vectors to the final approach course. One could fake the radar
1. To do the whole airport properly there actually would be vectors by developing a series of fixes simulating each vector
more procedures to add. Notice that I indent the runway and but that takes a lot of time and guesswork. In FS04 it might be
enroute transitions. I just think it reads better that way when best to just hand fly the plane because the flight sim ATC does
there are a bunch of procedures. not interact with the FMC.

2. A STARs landing route description (and a SIDs takeoff

description) can be very hard if not impossible to write 3. Notice where the runway listing is, right after all the
because of the lack of commands or that many require radar TRANSITIONs.

11
The above chart is for a STAR called JULIAN FOUR.

This STAR is straight forward with only five waypoints. So, //Airport ICAO
by looking through the commands available we see that //Date by Your Name
NAVAID NAME ALT can describe each of the waypoints
except one. How do you handle that x intersection between FIXES
PDZ and ARNES? It is not a NAVAID so it looks like a fix is FIX PDZ10 LATLON N 34 0.25 W 117 42.5.3
in order. Recall that a fix can be defined as a Lat-Long ENDFIXES
location and fortunately the coordinates of that x waypoint are
given so the fix would be written as: RNWS
RNW 05
FIX PDZ10 LATLON N 34 0.25 W 117 42.53 RNW 23
RNW 14
The fix name of PDZ10 I made up. The PDZ is the PDZ RNW 32
navaid and the 10 is the distance from PDZ to the x ENDRNWS
intersection.
SIDS
Another way to define this same fix is: ENDSIDS

FIX PDZ10 COLOCATED PDZ 285 10 STARS

STAR JULIAN4 NAVAID JLI NAVAID AMIGO 16000
With this knowledge we can write the STAR. Notice that I NAVAID PDZ FIX PDZ10 NAVAID ARNES 10000
had to complete the FIXES section. Without the FIXES RNW 05 RNW 23 RNW 14 RNW 32
section the FMC would have shown an error with FIX PDZ10. ENDSTARS
This is the complete procedure which would be saved as
KLAX.TXT

12
VII. Making IAPs
Now we are at the termination of a flight, the approach. The
approach procedure is written much like the common route
of a STAR. To write the procedure just start at the IAF and
proceed down the slope to the runway and back up through
the missed approach. Lets get on to some examples.

The approach plate to the right is straight forward so this is

what it looks like in procedure talk.

APPROACHES
APPROACH ILS22 NAVAID OVERFLY SADDL
NAVAID OVERFLY BRIDL RNW 22 KEEP TRK
UNTIL 2000 DIRECT NAVAID HYK 3000 HOLDAT
HYK RIGHT TURN INBOUNDCOURSE 304
HOLDTIME 1
ENDAPPROACHES

The thing to double check here is that you have the runway
number in there to denote the end of the approach and the
start of the missed approach procedure.

Also note that I put in altitude constraints and I used the

DIRECT keyword since the missed approach description
uses it.

Lastly, I used the keyword OVERFLY. This is probably

not necessary but it illustrates its use and insures the plane
is on course while going down hill.

13
Now we have a more interesting procedure to try. Easily
seen are a couple of arcs but we know that the command
language does not have arcs, yet anyway. So how do we do
this one? As Ive said before, we fake it. Fortunately the
fix creation command makes arcs rather easy to simulate.

Using the command

FIX NAME COLOCATED NAME RADIAL DISTANCE

it is easy though somewhat tedious to create arcs. You

know the navaid the arc is centered on. You know the entry
and exit radials and the distance the arc is from the navaid.
Thats the information you need to create an arc. To make
the arc you simply create a bunch of fixes along the arc
spaced about 15 degrees apart. You can use something
other than 15 degree if you desire though. I recommend
that each fix is named and numbered consecutively. Here is
what the FIXES section and the APPROACHES section
looks like for the plate to the right.

FIXES
FIX ARC1 COLOCATED CHS 219 12
FIX ARC2 COLOCATED CHS 234 12
FIX ARC3 COLOCATED CHS 249 12
FIX ARC4 COLOCATED CHS 264 12
FIX ARC5 COLOCATED CHS 279 12
FIX ARC6 COLOCATED CHS 294 12
FIX ARC7 COLOCATED CHS 309 12
FIX ARC8 COLOCATED CHS 324 12
FIX ARC9 COLOCATED CHS 333 12
FIX ARC10 COLOCATED CHS 55 12
FIX ARC11 COLOCATED CHS 40 12
FIX ARC12 COLOCATED CHS 25 12
FIX ARC13 COLOCATED CHS 10 12
FIX ARC14 COLOCATED CHS 355 12
FIX ARC15 COLOCATED CHS 343 12
ENDFIXES

APPROACHES
APPROACH ILS15 KEEP HDG INTERCEPT RADIAL 333 FROM ICHS NAVAID OVERFLY ASHLY RNW 15 KEEP
TRK 500 KEEP HDG INTERCEPT RADIAL 55 FROM WANDO HOLDAT WANDO RIGHT TURN
INBOUNDCOURSE 235 ALT 2000 HOLDTIME 1
TRANSITION ARC219 FIX ARC1 FIX ARC2 FIX ARC3 FIX ARC4 FIX ARC5 FIX ARC6 FIX ARC7 FIX ARC8 FIX ARC9
TRANSITION ARC55 FIX ARC10 FIX ARC11 FIX ARC12 FIX ARC13 FIX ARC14 FIX ARC15 FIX ARC9 1600
ENDAPPROACHES

This example shows a common problem, the IAP has, in this been a duplicate location and that would have been just one
case, two transitions, the arcs. To identify the transitions I more unnecessary thing for the FMC to read in.
called one ARC219 for the ILS to runway 15 using a right turn
in the arc and the other is ARC55 for the left turn arc. The You probably noticed that there is a procedure turn in the IAP.
numbers are the radials. You can call them something else if This is simple to do. Since the 737 FMC can not do procedure
you want. turns, we ignore it by not including it in the IAP.

Also note that ARC9 is used twice, once in each transition. I

could have created another ARC fix but it would have just

14
Here is an deceptive IAP so lets see what it looks like when its
described in 737 talk.

APPROACHES
APPROACH SPAR9 NAVAID SOLBA NAVAID BSN NAVAID
LARPO SPEED 220 NAVAID PON KEEP TRK
INTERCEPT RADIAL 358 FROM RBT KEEP TRK UNTIL
14 FROM RBT KEEP TRK INTERCEPT RADIAL 254
FROM NAVAID BT KEEP TRK UNTIL 27 FROM NAVAID
BT KEEP TRK INTERCEPT RADIAL 271 FROM NAVAID
VVE KEEP TRK UNTIL 7.7 FROM NAVAID VVE
KEEP TRK UNTIL 4.2 FROM NAVAID VVE RNW 09
KEEP TRK INTERCEPT RADIAL 303 FROM NAVAID OL
KEEP TRK INTERCEPT RADIAL 110 FROM NAVAID EVX
NAVAID EVX
ENDAPPROACHES

This one is really interesting to look at but not terribly difficult

to write except for the last three turns. The turns all suffer
from not starting the turn at the designated location. The last
left turn on to the final is particularly difficult to duplicate.
Heres the situation with the intercept command. When the
FMC receives an intercept command it extends its current
course line out until it intersects the designated radial.
Remember that the intercept command results in a fly-by
waypoint. So it then calculates the best location to start the
turn to intercept. This turn will always be before reaching that
intersection point. We do not know where that turn will be
nor can we designate when it will turn, only that we want a
turn, sometime.

The result of this is that, as written above, the FMC will

command a turn further out from BT 27 than desired. For
example, the last left turn on to the final. The plate says to
turn left at BT 27 but the problem is the intercept command
will not execute the turn at BT 27. The FMC will extend the
course line out from BT 27 until it intersects the 271 radial.
In this case the interception point is 13 miles away. Note
though that the plane will turn left before it reaches that
calculated intersection. This puts the turn farther out than
wanted. My way of fudging this particular turn is to make the
calculated intersection point closer to BT 27. If I changed the
command KEEP TRK INTERCEPT RADIAL 271 FROM
NAVAID VVE to TRK 210 INTERCEPT RADIAL 271
FROM NAVAID VVE the interception point becomes 4.2
miles instead of 13. I made the plane change to a course of
210 degrees before the interception point was calculated. This
moved the interception point closer and produces a turn more
like the plate depicts. Where did I get the HDG 210 from?
Trial and error. I knew I wanted something between 254 and
about 154 degrees so I plugged in some headings until one
worked OK. Nothing fancy, just brute force method.

You could do the same for the other two intercepts but I think
those are close enough to be OK.

15
VIII. Troubleshooting Hints NAVAID JFK HOLD AT NAVAID JFK RIGHT
TURN INBOUNDCOURSE 234
Here are some hints about correcting errors that the FMC yells
at you when you are loading the airport procedures. In general 3. When you select a STAR or SID and the initial waypoint of
the FMC will tell you what word is involved in the problem the STAR or last waypoint of the SID do not share the same
and the line number that problem is in. Some examples follow. terminal or initial waypoint respectively.

ERR AT GTH, LINE 14 This means that the name of GTH 4. When an intercept can not be executed because it is invalid.
was found but the FMC doesnt know if its a NAVAID or a
FIX. This usually can be repaired by finding the error, in this Another source of troubleshooting info is the LEGS page of
case, in line 14 of the procedures file and typing in NAVAID the FMC. Every now and again you might find a leg that is
or FIX in front of the GTH. If it was a FIX then you also have thousands of miles long. This is a hint that something went
to look in the FIXES section and see why that FIX is in error wrong. Usually this is caused by an INTERSECTION
or missing. command that could not intercept as asked to do. Suppose
you wanted to intercept the 90 radial and you are south west of
Err: rwy 14 unknown This is usually caused by a runway the navaid. You write the INTERCEPT command to use a
being defined in the RNWS section that the FMC can not find HDG of 360 degrees thinking it will intersect the 90 degree
in its runway database. You fix this by deleting all references radial. It doesnt. So what happens is that a course is drawn
to that runway and its reciprocal. IE RNW 14 and RNW that extends around the world until it does intersect and you
32. Delete in all sections that they appear in. get a weird distance. Double checking that headings will
produce the desired intersection will cure this sort of problem.
Err at 90, line 15 This message is telling you there is some Be careful when using KEEP HDG or KEEP TRK prior to
sort of error on line 15 and involves a 90. So go to that line an intersection command. If not sure of the direction the plane
number and look for a 90. The mistake will be right before is heading at the time this command is activated it could lead
that 90. Perhaps you left something out. to errors.

Err at SID, line 20 This is harder since it is telling you the More good stuff
SID has a problem. Go look at line number 20. It may be the
runway number is missing or wrong. Many portions of a procedure are the same as portions of
another procedure so when writing procedures use the cut and
For the next error lets say you have this fix defined. paste a lot to save typing time.

FIX DFT latlon N 34 5.7 E 22 34 I recommend that you write with word wrap off . This helps
in the readability. It also helps to indent the transitions.
Err at latlon, line 6 You get this error. Whats wrong? It
looks good. But wait a minute that latlon is the problem. It You probably wont but just to make sure, there is no need to
should be capitalized. Remember that keywords need to be type anything in bold font. I only used it here to help
capitalized or you will get an error. illustrate.

Err: SPZ unknown The problem is that that NAVAID I find it faster to troubleshoot procedures directly from FS04.
SPZ can not be found. Notice there is no line number given. I run the editor in the background. If I get an error when a
You will have to look for the name SPZ somewhere in the departure or arrival airport is loaded into the FMC I can switch
procedures. When you find it recheck the spelling. If spelling to the editor, load the airport, correct the error, save the
and syntax are OK then the NAVAID SPZ needs to be made change, go back to FS04, clear the error message and reload
a FIX SPZ. Define the fix in the FIXES section. Then in the airport in the FMC. Repeating as necessary until no more
the procedures section(s) change all references of NAVAID errors.
SPZ to FIX SPZ to clear the error. Now, obviously the
SPZ is an example. You would use whatever navaid ID is
needed. This concludes the tutorial. If you discover any
errors let me know at 737NG@hotpop.com so I can
INSRTD DISCON AFTER XXX - The FMC will insert a fix them. If you run up against a problem writing a
disconnect under the following conditions. Check the location
of XXX and the next waypoint for these conditions.
procedure not covered here let me know and
perhaps I can help plus use it as another example for
1. When the plane is told to fly to a waypoint and then have to all to benefit from.
turn more than 179 degrees to get to the next waypoint.
Good writing to all and please post your procedures
2. When the aircraft is told to go the same waypoint twice in a
row.
so others can have fun too.

Examples: NAVAID ABC NAVAID ABC Bye. Terry

16