APDL and Timezones...
I have had a few questions lately regarding the Time Zone
functions/settings of our program. Setting time zones up correctly
can be a fairly simple task, but setting them up incorrectly
will create a host of problems that will yield less than desirable
results. It is very important to set up the different time zone
functions correctly so that the many different internal calculations
of our program will function correctly, enabling a more accurate
"picture" of each situation unique to different pilot groups.
Therefore I will attempt to “break it down” for you. The following
is a discussion of the different time zone settings and functions.
The discussion is broken down into two sections, Time Zone Settings
Explained and Examples. At the end of the initial discussion
section, you will find specific examples that should help you
apply these settings more accurately to your specific situation.
I hope you find it useful.
Time Zone Settings
Explained
Daylight Saving Time begins for most of the United States
at 2 a.m. on the first Sunday of April. Time reverts to standard
time at 2 a.m. on the last Sunday of October. In the U.S., each
time zone switches at a different time. In the European Union,
Summer Time begins and ends at 1 am Universal Time (Greenwich
Mean Time). It starts the last Sunday in March, and ends the
last Sunday in October. In the EU, all time zones change at
the same moment.
I have included this chart to help you figure out when DST
Begins and ends:
United States
DST Begins
At 2:00 a.m. Local:
2003 April 6
2004 April 4
2005 April 3
2006 April 2
2007 April 1
DST Ends
At 2:00 a.m. Local:
2003 October 26
2004 October 31
2005 October 30
2006 October 29
2007 October 28
European Union
Summertime Period Begins
At 1:00 a.m. UT:
2003 March 30
2004 March 28
2005 March 27
2006 March 26
2007 March 25
Summertime Period Ends
At 1:00 a.m. UT:
2003 October 26
2004 October 31
2005 October 30
2006 October 29
2007 October 28
Sounds complex huh? It is. That is why our program has been
designed so that once set up correctly, you will only have to
make one (1) change to one (1) setting at the start and end
of daylight savings time. That’s it! All you have to do is ensure
that the initial time zone settings are correct. They will only
have to be set up once, and never again. Our program will do
the rest.
PREFERENCES:
It is important to set up your user defined preferences correctly.
These preferences are the settings that control look and feel
of the program, as well as how it performs a myriad of internal
calculations. These preferences are found by tapping on (Options)(Preferences).
I will walk you through all of them that have an effect on Time
Zones and a few that do not, yet are important.
(Options)(Preferences)(General):
Use Popup Lists? Although this setting will not affect
time zone calculations or functions, I recommend setting this
to “Yes”. It will make entering information and using the program
in general, easier.
Use Datebook? Although this setting will not affect
time zone calculations or functions, setting it to yes will
enable your individual flights to be viewed in the Datebook
program in your Palm device. After you have all of your time
zone settings set up correctly, you will be able to view your
trips in your Datebook correctly.
Airport Domicile? This setting is very important and
must be set correctly. The default airport is LGA. You will
need to enter the three letter identifier of your specific domicile
airport. This setting is what the program will look at for per-diem,
among other calculations.
YTD Starting Hours? Enter the hours you have accumulated
since Jan 1 of the current year. Enter the value in aviation
(1/10th) time. This allows the program an accurate picture of
your cumulative yearly hours. It is important that this number
be as correct as possible as it will affect different functions
of the program such as FAR 121 flight time limitations.
End of duty offset? Enter your contractual duty off
time from the last leg flown in minutes. This number is usually
15, (15 minutes), but depending on your specific airline contract,
it may be more or less. This number is important for per diem
calculations as well as the duty and rest requirement functions
of the program.
(Options)(Preferences)(Timezone Settings)
Now we get to the meat and potatoes of Time Zone calculations…..
Domicile’s Time Zone? This setting should be set to
your Domicile’s Time Zone for when daylight savings is
NOT IN EFFECT. Once set, this setting will never need
to be adjusted again, whether or not daylight savings is in
effect.
Logbook Time Zone? WARNING:
DO NOT CHANGE THE TIME ZONE ONCE YOU HAVE STARTED ENTERING INFORMATION.
If you have already started entering information, leave this
setting as is, even if it is wrong. Changing it after you have
entered information will have adverse affects on internal time
calculations.
The "Logbook Time Zone" is the time zone we store all your
flight times in. The software needs a reference point, which
is why we put the warning message up. If you have kept all your
previous logbook data in UTC-6, for example, then I suggest
leaving it set to UTC-6.
If you have not yet entered any data this setting should
usually be set to your domiciles time zone for when daylight
savings is NOT IN EFFECT. Once set, this setting
will never need to be adjusted again, whether or not daylight
savings is in effect.
Import Schedules in? This setting is company specific.
Most users will find that their company prints their schedules
in local time. Find out what time zone your company prints your
schedule in and enter it accordingly.
Daylight Savings is in Effect This setting is probably
the single most important setting when it comes to setting up
your time zone information. It is the only setting that
will need to be changed each April and October (See chart above
for specific times & dates). Place a checkmark in the box when
Daylight Savings is in Effect, and remove the checkmark when
DST is no longer in effect.
(Options)(Airport Lists)
This is the section that you will edit, add, or delete airports
in your programs airport data base. I have found that many users
that have had problems with time zones and time computations,
have either one or more airports set up incorrectly. Set up
each airport carefully in order for your time computations to
work correctly.
To add an airport simply tap the “Add” button on the (Airport
Lists) page. When you do you will see a new page pop up titled
“Add Airport”.
• (Airport): The first line will be for the three
letter identifier for the airport that you want to add. I.E.
Atlanta = ATL.
• (Conus) The second line is for the CONUS/OCONUS
rate for this city. Visit
www.irs.gov
to get the current rate. Enter it, if desired, in dollars and
cents format. I.E. 2.50 = $2.50.
• (Time Zone) - Select the appropriate time zone.
This setting is VERY IMPORTANT. It should be set to the airports
Time Zone for when daylight savings is NOT IN EFFECT.
Once set, this setting will never need to be adjusted again,
whether or not daylight savings is in effect.
• (Apply Daylight Savings) – This checkbox is commonly
misused. Place a check mark in the box if the airport you are
adding complies with daylight savings time. Most airports do,
but some do not. Important: Do NOT uncheck this box in April
& October (U.S.) or March & October (EU). I.E. Leave it checked
all year long. It simply tells the program to include this airport
in time computations requiring the addition or subtraction of
one (1) hour each time daylight savings goes into or out of
effect twice a year.
EXAMPLES:
Example #1:
My domicile time zone is ATL (Atlanta) and is currently UTC-4,
but in October (See chart above) Standard Time will go into
effect and change my domicile’s time zone to UTC-5. What setting
should I set in (Options)(Preferences)(Timezone Settings) “Domicile’s
Time Zone?”
Set this to the time zone for when
daylight savings is NOT IN EFFECT. I.E. UTC-5.
Example #2:
I have my Logbook Time Zone set to UTC. I would really like
it set to my domicile’s time zone of UTC-5. I see that you have
a warning against changing it. What adverse affects will I see
if I change it now that I have already entered data into my
program?
For those of you that have it set
incorrectly and must see it displayed correctly, if you do change
your (Logbook Time Zone) your previous data (prior to changing
the time zone) when viewed using (Zulu) or (Local) time picker
on the logpage will be incorrect. The data itself, when viewed
using the (Logbook) time zone will be correct. There is no effect
to crew rest/required rest or totals. In other words, if you
change this setting after data has already been entered, old
data will only be viewed correctly when viewed with the (Logbook)
time zone. Again, I suggest leaving it alone if you have already
entered data.
Helpful Hints:
Daylight Savings Time can be confusing. The following tips
will help you to make a smooth transition to and from daylight
savings time. If you have correctly set up your time zone settings
by following the above instructions, you will only have to make
ONE (1) change to the program each time daylight savings
goes into or out of effect.
Helpful Hint #1: This one change is found in (Options)(Preferences)(Timezone
Settings). It is the last one at the bottom of the page. It
is a checkbox that says “Daylight Savings is in Effect”. To
reiterate, place a checkmark in the box when Daylight Savings
is in Effect, and remove the checkmark when DST is no longer
in effect.
Helpful Hint #2: Always enter the time zone for a
specific airport as if DST was NOT in effect, EVEN IF IT IS.
Helpful Hint #3: Remember to place a checkmark in
the box that says, “Apply Daylight Savings” when adding a new
airport, if the airport complies with DST. Once this check mark
is there, LEAVE IT no matter if daylight savings is in effect
or not
|