(c) 1999-2005 Scott M Baker, smbaker@forpilots.com
Purpose:
This program generates cross-country navigation logs for
pilots. Cross-country logs are sometimes time consuming and
require lengthly recalculation when wind conditions or other
factors change. XCPlan automates these tedious calculations and
generates a user-friendly, easy to read navigation log.
Table of Contents:
Quick Start:
The quick start instructions will get you going in a hurry if
you're computer literate. If not, jump down to the more detailed
instructions below.
- Load XCPlan by clicking on it's windows' icon
- If XCPlan already has an old Navigation Log loaded (i.e.
you've used it before), then you can use the
CheckPoints:Delete-All pull-down menu option to erase the
old flight plan.
- Press the <Add> button to set your departure point.
- For each enroute checkpoint, do the following:
- Press the <Add> button to bring up an
add-checkpoint dialog
- Enter the name of the checkpoint in the Checkpoint
Name field.
- If the bearing, altitude, true airspeed, or
magnetic variation has changed since the previous
checkpoint, then enter the new values. If these
items have not changed, then there is no need to
re-enter them -- XCPlan will automatically carry
over the previous ones.
- If you have Predicted Wind information
available, then enter it with your first
checkpoint. If you do not have wind data
available, then you can always leave it blank and
fill it in later.
- Press the <Aircraft> button and set aircraft
related information such as the fuel capacity and GPH.
- Press the <Print> button to print out your
navigation log!
Tutorial:
I'll introduce a simple cross country flight below and walk
you through all the steps necessary to create the navigation
logs. Some details about our flight:
- The departure is Tucson International Airport (TUS) and
the destination is Cochise County Airport (P33).
- We will fly an initial true course of 095 and altitude of
9500.
- Our true airspeed will be 75kts during the initial
climb-out to the first checkpoint, and 105kts to the
remaining checkpoints.
- First Checkpoint: Rincon Peak, 23 miles from TUS
- Second Checkpoint: Benson, 11 miles from Rincon Peak
- Third Checkpoint: I10xDrg, 11 miles from Benson
- Fourth Checkpoint: Ammon, 6 miles from I10xDrg
- At the Ammon checkpoint, we will make a course change to
015.
- Destination: Cochise, 13 miles from Ammon
- Our aircraft is a Cessna 172, holds 38.0 gallons of
usable fuel, and burns 9.0 gallons per hour
- The predicted winds are 240/17
Here are the steps necessary to enter the flight plan into
XCPlan. We'll assume you do not have wind information yet, and
will enter it later.
- Load XCPlan
- Select the "Checkpoints:Delete-All" pull-down
menu option to erase any previous navigational data (only
necessary if old nav-data is displayed)
- Press <Add> to enter the departure point
- Enter the departure name, "TUS"
- Since this is the departure point, there is no
other navigational data to enter at this time.
We'll enter the course when we fill in the first
checkpoint.
- Press <Add> to enter checkpoint #1, Rincon Peak
- Enter the checkpoint name, "Rincon
Peak"
- Set the Distance to "23"
- Set the True Course to 095
- Set the Altitude to 9500
- Set the True Airspeed to 75. (We're using 75kts
for climbout)
- Set Magnetic Variation to -12.
- Press <Ok> when you're finished. (If you
want to, you could also enter the wind
information into this screen, or you can wait
until step #10 below)
- Press <Add> to enter the second checkpoint
- Enter the checkpoint name, "Benson"
- Set Distance to "11"
- Set the True Airspeed to 105. (105kts is our
cruise TAS)
- All other parameters (TC, Altitude, Mag Var, etc)
are the same as for checkpoint #1, so we do not
need to enter any additional data here.
- Press <Ok> when you're finished.
- Press <Add> to enter the third checkpoint
- Enter the checkpoint name, "I10xDrg"
- Set Distance to "11"
- Press <Ok>
- Press <Add> for the fourth checkpoint
- Enter the checkpoint name, "Ammon"
- Set Distance to "6"
- Press <OK>
- Press <Add> for the fifth checkpoint
- Enter the checkpoint name, "Cochise"
- Set Distance to "13"
- Set True Course to "015". This is
because we have a course change for the final
leg.
- Press <OK>
- We've completed entering the Nav Data; Now it's time to
enter our aircraft data:
- Press the <Aircraft> button
- You may enter your name, n-number, and aircraft
type into the appropriate fields if desired.
- Enter "9.0" into the GPH field
- Enter "38.0" into the Full Fuel field.
- It's time to enter the wind information.
- Hilight the first enroute checkpoint (Rincon
Peak)
- Press the <Edit> button
- Enter the wind direction, "240"
- Enter the wind speed, "17"
- Press <Ok>
- Press <Print> to send the navigation log to the
printer!
Abbreviations Used:
ETE: Estimated Time Enroute. The estimated time it will take
to complete a leg in minutes.
ETA: Estimated Time of Arrival. The time at which you will
arrive at your destination.
GPH: Gallons Per Hour. The amount of fuel your aircraft burns.
GS: Ground Speed.
CH: Compass Header. The Magnetic Heading corrected for
deviation. This is the heading that you will fly!
MH: Magnetic Heading. The True Heading corrected for magnetic
variation.
TAS: True Airspeed.
TC: True Course. The course determined from using a plotter on
your sectional chart.
TH: True Heading. The True Course corrected for wind drift
WCA: Wind Correction Angle. The angle necessary to correct for
Wind Drift
Adding Checkpoints:
Checkpoint fields are divided into several different
categories:
- Required: These fields must be specified
with each checkpoint. There are only two of these,
checkpoint name and distance.
- Required on 1st enroute: True course,
weather information and magnetic variation must be
entered on your first enroute checkpoint. This is because
this information is necessary to compute compass
headings, ground speeds, and other computations. You may
optionally enter this information in other checkpoints as
necessary. For example, if your true course changes at
your fourth checkpoint, enter the new true course.
- Optional: Information specified as
optional is only used for your own reference and is not
used by the computations. This includes items such as VOR
navigational aids.
Below is a specific breakdown of each field:
- Checkpoint Name: (required)
The name of the checkpoint
for the current leg. The true course and altitude you
will enter below are the directions for navigating TO
this checkpoint.
- Distance: (required)
The distance to this checkpoint in
nautical miles from the previous checkpoint. This
distance is usually obtained by measurement on the
sectional chart using a navigation plotter/ruler.
- True Course: (required on 1st enroute checkpoint)
The
direction of flight from the previous checkpoint to this
checkpoint as measured clockwise from true north. This is
usually obtained by applying your plotter to the
sectional chart. True course does not
include corrections for magnetic variation, deviation, or
wind.
- Altitude: (optional)
Desired altitude for the current
leg. VFR altitudes should be odd+500 feet if you are
using an east magnetic course and even+500 feet if you
are using a west magnetic course.
- True Airspeed: (required on 1st enroute checkpoint)
The
speed of the aircraft relative to the surrounding air.
This may usually be obtained from a chart in the Pilot's
Operating Handbook (POH) of the aircraft you are flying.
- Weather: Wind Direction (required on 1st enroute
checkpoint)
This is the direction FROM which the wind
is blowing. This is usually obtained from a weather brief
or Winds Aloft forecast.
- Weather: Wind Speed: (required on 1st enroute checkpoint)
The
speed at which the wind is blowing in knots. As with the
previous item, this is normally obtained via a weather
brief or Winds Aloft forecast.
- Weather: Temperature (optional)
Outside air temperature
at your cruise altitude. Obtained from weather brief.
- VOR Navigation Settings (optional)
The VOR information
is solely for your own use. How you use it is up to you.
Four items are included: the frequency of the VOR,
bearing (radial), identifier, and To/From. The identifier
will automatically be translated into Morse Code when the
navigation log is printed.
- Magnetic Variation (required on 1st enroute checkpoint)
The
difference between True North and Magnetic North. This is
indicated on sectional charts by isogonic lines. Magnetic
variation is necessary to translate between true heading
and magnetic heading, and should entered with your first
enroute checkpoint.
It is possible that your flight may cross multiple
isogonic lines. In this case, you may enter the
additional variations with the other checkpoints as
necessary.
Variation should be rounded to the nearest degree --
do not include minutes or seconds.
Saving and Loading Cross Country
Plans:
You probably have many different xc plans, and it'd work out
to your benefit if you could save them for later retrieval. That
way, if you ever repeat a flight, you will have most of the
planning complete. XCPlan has the following capabilities:
- File:Save. This will save the current flight plan under
it's current name. The default name is
"default.flt" and this what will be used if you
do not use the Save As command below.
- File:Save As... This will let you choose a file name for
your flight plan and save it to that file name.
- File:Open. If you have previously saved a flight plan to
disk, then you may use this option to retrieve it.
Shareware Registration
XCPlan is distributed as shareware.
What does this mean?
- You can use the program for as long as you'd like to
evaluate it, completely free of charge.
- You may distribute it to friends.
- Once you have evaluated the software, you are expected to
pay a modest ($19.95) registration fee to the author
(Scott M. Baker). The registration fee compensates the
author for the time spent developing the software and
encourages him to continue future work.
So what is a good evaluation period? You'll have to let your
conscience be your guide. I'd put an estimate at about 5-10
flights. If you've used XCPlan for more than 10 flights to
generate your navigation logs, then you're probably using it and
not evaluating it!
Specifics of Registration:
You may pay your registration either online at my secure
credit card payment site (http://www.forpilots.com/register
or http://www.sb-software.com/credit).
Credit card payment is the fastest and easiest way to pay for
your registration. The site is secure, meaning that your credit
card number is encrypted to protect against theft. You may also
pay be check, money order, or cash to the address below:
SB-Software
c/o Scott Baker
2241 W Labriego
Tucson, Az 85741
Please include your Internet email address with
your registration. My normal procedure is to email
your registration information back to you at the address you
provide. If you do not have an email address, then I can send you
a reply through the US Postal Service, but that usually takes me
a bit longer (I prefer using email).
My shareware registrations are always good for
life. All versions of the software are covered -- past,
present, and future. You will only need to pay
once; If I release updates to the software, then you are
automatically covered.
Revision History
- Version 1.0
- Version 1.1
- Added ATIS, Ground, and UNICOM to field display
- Support to multi-line data in field display
- Fixed DeleteAll so it does not delete title
- Added reset button to add field list
- Added file:new command
- version 1.2
- update to new compiler
- misc cosmetic fixes
- Added register screen
- version 1.3
- finally gave the program its own icon
- misc cosmetic fixes
- Add help menu
- Fix some dialog size issues
About the Author:
Scott M Baker is an independent software consultant and
shareware programmer. He operates his own business, SB-Software,
which develops Internet-related and other special purpose
software. SB-Software may be found on the Internet at http://www.sb-software.com
(note the dash in sb-software). Mr. Baker also operates several
other websites, including an aviation related website, http://www.forpilots.com
where the latest version of XCPlan may be found.
Scott M. Baker received his Bachelor's and Master's degrees in
Computer Science from theUniversity of Arizona. Mr. Baker also
has a Private Pilot: Aircraft Single Engine Land certificate and
is a member of AOPA.