FliteLX Manual

 

Welcome to the manual of the FliteLX FTDR application. This is a dynamic document that will be updated periodically.

Since the FliteLX application is a rather large project, it is highly recommended to read the manual carefully in order to understand the happenings behind the scenes. It is divided into the following sections:

Components - A short glimpse of the subparts of the FliteLX FTDR application.

Tutorial - A walk-around through all pages and menus of the handheld part of the application.

Checklists - All proceedings for the desktop part of the FliteLX application, i.e. the Excel sheets, written for people accustomed to the use of step-by-step checklists.

Reference - An in-depth explanation of some selected topics for users who want to learn more than just the basics.

 


Components

These are the files of the FliteLX FTDR application:

'FliteLX.prc' - The application program file that has to be installed on the Palm device. It can be downloaded from the FliteLX section of this web site; fill out the Order form to get a registration key. Refer to your handheld's manual for a description of the program installation process.

'FliteLX.xls' - The Excel workbook required to fully use all features of FliteLX - see Tutorial. Download the latest version from the FliteLX section of this web site.

'Airports.pdb' - The airport database file used by FliteLX. It is not required but will provide you with helpful information concerning the airports you are flying to, if installed. Download the latest version from the FliteLX section of this web site. - The information contained in the 'Airports.pdb' file has been received from Swiss International Air Lines Flight Dispatch. As it is not possible for an individual to issue regular updates in order to guarantee the integrity of this data, you have to consider it as non-operational.

'Schedule.pdb' - This is the Swiss International Air Lines timetable database file that belongs to the FlitePilot application, but is referred to by FliteLX FTDR. It is not required, but it eases the manual entry of flights, if installed. FliteLX will lookup a flight number and fills out the scheduled times and departure/arrival airports. Download this application and its databases on the respective section of this web site.

 


Tutorial

Setup

On first startup of the application, FliteLX prompts for some data required by its subparts. Please fill out the particulars form, press the 'Next Step' button, fill out the licence expiry form and finally the two pages of the FTDR setup. The fields are self-explanatory, but an online help is always available by tapping on the small 'i' in the top right corner of the screen. This is valid throughout the whole application.
All data entered during the setup process may be changed later on via the respective FliteLX menu items.
Please note that you must use the decimal character '.' or ',' according to the settings of your Palm device ('System', 'Prefs', 'Formats' / 'System', 'Einstellen', 'Formate').


The 'Plan', 'Log' and 'FTDR' pages

By tapping on the register tabs on the lower part of the screen you can navigate between the three main pages: The 'Plan' page, the 'Log' page and the 'FTDR' page. Each screen displays the active date in the top right corner, besides the beforehand mentioned small 'i' to get access to a context help page. You can change the date by tapping on the underlined text and selecting it on the form that pops up, or by pushing your Palm device's 'Up/Down' hard buttons to decrement or increment.
The large Swiss International Air Lines logo overhead serves as a shortcut to invoke the menu, i.e. it provides the same functionality as the menu button left of the Graffiti area.
There are some buttons on the bottom, righthand of the register tabs: The small Swiss International Air Lines logo that links to a general information page indicating the version number of the application, the phone receiver, the departing aircraft and the weight measure symbols. The latter three provide a direct access to the FlitePilot, the InFlite and the FliteERJ resp. FliteS20 applications if installed. Those programs on the other hand have an arrow button at the bottom right corner of the screen to return to the main FliteLX application.
But now to three main screens of FliteLX:

The 'Plan' page displays the duties of a single day in a similar way as they appear on your duty plan. The duty text can be modified like any text fields in other Palm applications. Please read the corresponding section in the Reference  at the end of this document to learn more about valid duty names; in general, keep on using the names as they appear on your duty plan. Tap on an empty area on the screen to let the application 'accept' and process the duty text.
The departure and arrival airports are entered on a page that pops up when you tap on that cell. You can enter both three letter IATA or four letter ICAO codes. Besides that this page displays the data of the 'Airports.pdb' database if installed.
The scheduled times finally are entered on an extended time selection form similar to the one known from the datebook application. However, you have the possibility to enter an empty time span. Note that it is as well possible to enter the time using Graffiti here, besides selecting it from the lists.

The 'Log' page is a flight log where you can enter data corresponding to the legs defined on the plan page. Note that the departure and arrival airports are the same as the respective fields on the 'Plan' page. The following data can be stored attached to each leg: Off and on chocks times, the IFR duration, a flag if you have been pilot flying (PF) on that leg or not, a note with any textual information you would like to add, the aircraft immatriculation and type, and the cockpit as well as the cabin crew identifier codes. The last four items are displayed in the top left corner of the screen for the currently selected leg. A leg is selected as long as an arrow is visible leftmost in the table. You can select another leg either by tapping in the first column with the arrow, or by selecting any other table cell of a leg. Note that if you leave one of these four fields empty, the data of the preceeding leg is valid implicitly - this way it is not necessary to enter the data for all legs but only for the first one and e.g. after aircraft crew changes if any.
With the 'IFR' column you have the possibility to log the actual instrument time if you decide to do so. After entering the off and on chocks times, tap on the 'IFR' cell and select any duration - only the time span and not the start and end times are logged.
Refer to the section on application preferences in order to learn more about how to enter off chocks and on chocks time simply by pressing one of the hard keys.

The 'FTDR' page finally represents a single day, or a line respectively, of the official FTDR sheet. The data that is entered here will appear exactly the same way on the Excel FTDR sheet later on. As soon as the 'Sync' button near the Swiss International Air Lines logo is pushed, the data from the previous two pages is compiled and the FTDR page is filled out accordingly. Note that you have to push 'Sync' explicitely; modifications on the 'Plan' or the 'Log' pages are not carried over automatically - that is, the flight plan and log are independent from the FTDR.
You have the possibility to change the FTDR data manually. The fields are self-explanatory, the flags 'Split', 'Night' and 'N/S' correspond to the columns on the FTDR form, as well as the 'Ldg', 'Block', '150/170 hrs', '2000 hrs' and 'Expense hrs'. By pushing the dotted box below 'Additional exp' you can enter the values for the backside of the FTDR form. The three dots at the bottom right corner of the screen, marked with 'N', may be tapped on in order to attach a note to the FTDR data. This note will as well appear on the backside of the FTDR sheet.
Please note that the 'Sync' algorithm is not always correct as there are many ambiguities that are hard to identify. Always check the produced FTDR page, especially in case of non-standard duties like positionings or instruction.


The menu

The menu on the three main pages features four menu bars: The FliteLX menu, the 'Record' menu, the 'Edit' menu and the 'Options' menu. As discussed, you get access to the menu by either tapping on the menu button to the left of the Graffiti area, or by hitting the large Swiss International Air Lines logo.
As on every Palm application, some menu items feature a direct access via shortcuts. Those items are marked with the corresponding Graffiti stroke and its shortcut letter. Read more about menu shortcuts in the manual of your Palm handheld.

The FliteLX menu features an access to the setup pages that have been mentioned during the Setup discussion. The licence expiry dates are updated during the download of the electronic duty plan if you decide to do so. Read more about that in a later section.
Note that the application will check if there are some records before the date of entry if that value has been modified on the 'FTDR Setup' page. You may want to let FliteLX delete them after changing it.

The 'Record' menu deals with the creation, modification and deletion of records. You can add a new leg by selecting the respective menu item, or if you tap just below the last leg on the 'Plan' or 'Log' pages. Both ways will add an empty leg at the end of the list, however, as soon as its departure time has been changed, the legs are sorted accordingly. You can delete the selected leg, i.e. the leg with the arrow, attach a note to that leg or delete any note. 'Delete Day Record...' deletes the data from the 'Plan' and 'Log' pages if one of these two pages is active, or the data from the 'FTDR' page if that screen is active. This is due to the fact that plan/log and the FTDR data are stored in two separate databases. The Reference part of this document will reveal more details on that.
To finish this paragraph, the 'Purge...' and 'Beam Day Record' menu items are used to purge old data or to beam the data of the active day to another Palm device via infrared. These commands however are not yet implemented at the time being.

The 'Edit' menu bar is the same as in every other standard Palm application and is explained in your Palm handheld manual.

The 'Options' menu bar finally features the application preferences, explained in the next section, a lookup function to search for data in all databases (not yet implemented), the registration form and the same 'About' box that is accessible via the small Swiss International Air Lines logo at the bottom of each main screen.


The application preferences

Data entry, Chock entry key: Here you can dedicate one of the four main hard keys of your Palm device to enter the next empty chocks time. Note that this feature is only available as long as the FliteLX pplication is active, so that the default functionality of the key remains the same once again outside the FliteLX application. The device itself however may be turned off, but as soon as you press the dedicated key, the displayed date jumps to the actual day and the next empty chocks time is set to the current time in UTC. Whereas it is not necessary that the 'Log' page is active, it is recommended to do so in order to being able to check the entered time.
Link to built-in applications, Date book: When this option is enabled, events in the Palm datebook application are generated when the next duty plan is installed. You can trigger the generation of check-in alerts.
Link to built-in applications, Expiry reminders: Expiry reminders are generated either in the datebook or in the do do list, as soon as you change one of the licence expiry dates and leave the 'Licence Expiry' form (menu 'FliteLX').

 


Checklist This section provides a checklist to be used on the desktop part of the FliteLX FTDR application, i.e. the Excel workbook named 'FliteLX.xls', which is divided into several sheets:

'Plan' - A tool to convert the 'duty-plan.pdf' file into a 'Plan.pdb' database. This file can be downloaded to the Palm device in order to have the flight duties available without having to enter them manually - refer to the Electronic duty plan download section later on.

'FTDRfront', 'FTDRback' - The official FTDR sheet where the data logged on the 'FTDR' page of the Palm application will be transferred to - refer to Producing the FTDR form.

'Flightlog' - A flight log with a layout similar to the JAR Pilot Logbook of the Swiss FOCA. The data logged on the 'Log' page of the Palm application will be transferred to this sheet - refer to the Producing the flight log section.

'Wish' - A crew wish form that will be filled out according to the particulars data entered in the Palm application - refer to 'Producing a Crew Wish form.


General

Three important points about the Excel sheets:

- The Excel sheet macros read the backup copies of the Palm databases which are made during each HotSync process. So it is crucial that you perform a HotSync prior to using one of the sheets in order to have the most recent Palm data available on your PC.

- Furthermore, you have to locate your database backup directory with the files named 'FTDR-FLTE.pdb' (all FTDR specific data) and 'PlanLog-FLTE.pdb' (the flight log). Start your Palm desktop application and have a look at 'Tools - Options - General - Data directory' ('Extras - Optionen - Allgemein - Datenverzeichnis') - don't change it. This is your Palm backup directory where the backup files are stored in a subdirectory for each user that synchronizes with the computer. Supposed the data directory path is 'C:\Palm', then the files we are looking for are in the directory 'C:\Palm\YourName\Backup'. - Alternatively, you can use the Windows Explorer 'Find Files' function to locate the file directly. On the Macintosh (not yet supported), use 'Sherlock' to locate the files: 'Finder', 'Ablage', 'Finden...'. - Once located, the backup directory path will then be written on the 'Help' sheet. When you save the sheet now, you won't have to do all this again next month.

- As the sheets are read-only, they are protected by default. If you have to modify a sheet for whatever reason, you have to unprotect it first. The password is 'flite'. Note however that any change made on the Excel sheets will not be updated on the Palm databases. This is especially important to know concerning the FTDR and the flight log sheets.


Electronic duty plan download

Besides entering the flights manually into the Palm application, there is a way to download the electronically issued duty plan. Use the 'Plan' page of the 'FliteLX.xls' Excel workbook to generate a database file containing the duty plan to be downloaded onto your handheld. The subsequent checklist describes the process of creating the 'Plan.pdb' file. Once installed, the file is read on the next startup of the FliteLX application. FliteLX then updates its own databases with the new duty plan, generates events in the standard Palm datebook application if that option has been enabled, and finally deletes the 'Plan.pdb' file since it is not needed anymore.
The expiry dates are updated according to the dates on the duty plan. If FliteLX reads a date unequal to the date that is stored, it prompts if the date shall be updated.
Never install a new 'Plan.pdb' file while there is still an unloaded duty plan on the Palm since the latter will be overwritten on a subsequent HotSync.


Old LISLINE Duty Plans

The process to generate the 'Plan.pdb' file for the download of your duty plan is not yet optimized. The Acrobat reader file format (PDF) of the duty plan we get is not predestined to being converted, the detour via the clipboard is only a workaround. Note that due to the file format it is as well only possible to decode a single page duty plan. It will be necessary to append the second page manually as a workaround.
Once we get our duty plan in a more suited file format, the generation of the 'Plan.pdb' file will be more straight forward.

Checklist

1. On the Palm, select the application preferences 'Link to built-in applications': 'Date book' and 'Check-in alerts' (menu 'Options', 'Preferences...') if wanted. This has to be done prior to the installation of the 'Plan.pdb' file.

2. On the desktop PC, open the 'duty-plan.pdf' file that has been issued by the Swiss International Air Lines flight planning department.

3. In the Acrobat reader, by pressing 'V', assure that the text select tool is active. This is confirmed when the mouse cursor shape is a vertical bar and no hand, no magnifying glass and no crosshairs symbol.

4. Now select the duty plan text, beginning at (including) 'Period:', until the very end of the text, and press 'Ctrl-C' to copy the selection into the clipboard.

5. Open the Excel 'Plan' sheet and activate the 'Get' button.

6. Check the decoded duty plan and expiry dates accurately.

This is the critical step. You can modify your duty plan directly on the sheet. Please note that the LIS abbreviations according general PIH must be used. You can leave the expiry dates blank. However, all legs must be in sequence without any intermediate blank legs because the generation of the duty plan file stops at the first blank line, i.e. a line without a date in the first column. It is important that each column contains only specific data, e.g. a date in the first column and no text in the 'Sched' time columns. - Please check especially days with special, non-standard notes on your duty plan. - Refer to chapter The 'Sync' Algorithm to learn more about the supported abbreviations and codes.
The 'Note' column is relevant for datebook events only if their generation has been enabled - the note will be attached to the datebook entry.

7. Press the 'Write' button. Select a place where to store the 'Plan.pdb' file. The file can be deleted after its installation, so an obvious place to store it would be the desktop.
By pressing 'Write', the following three error messages can occur:
- "Non-numeric schedule times": The indicated line contains letters in the 'Sched' columns'. This can happen if there were non-standard notes on the duty plan. Please go back to step 6 of this checklist and manually correct the line.
- "Numeric airport identifiers" : Same as above, but the 'Dep' or 'Arr' column contains a number instead of letters.
- "More than six legs defined": A particular date contains more than six entries. Delete a non-relevant line, e.g. a note.

8. Double-click on that file and perform a HotSync operation. This transfers the duty plan onto your Palm device.

9. Whenever you start FliteLX on your Palm handheld next time, the duty plan will be installed.

10. Delete the 'Plan.pdb' file, and press the 'Clear' button on the Excel sheet to clear the page. Once the 'Plan.pdb' file has been installed on your Palm handheld, it is not necessary to save the Excel sheet or to keep the 'Plan.pdb' file.


New PBS Duty Plans

Checklist

1. On the Palm, select the application preferences 'Link to built-in applications': 'Date book' and 'Check-in alerts' (menu 'Options', 'Preferences...') if wanted. This has to be done prior to the installation of the 'Plan.pdb' file.

2. On the desktop PC, open your PBS schedule in a browser window as follows: Go to the 'Crew Link' homepage and take the 'Fast Link' to the 'PBS BI' (bidder interface). The left column now displays a 'Schedule' section where you have to select the respective month and press the 'View...' button. A new window with your schedule then pops up.
Note: Do not take the 'CDA2002' fast link as the CDA format is not supported by FliteLX.

3. Copy the whole PBS duty pland into the clipboard by pressing Ctrl-A followed by Ctrl-C.

5. Open the Excel 'Plan' sheet and activate the 'Get PBS' button.

6. Check the decoded duty plan and expiry dates accurately.

This is the critical step. You can modify your duty plan directly on the sheet. Please note that the abbreviations according general PIH must be used. You can leave the expiry dates blank. However, all legs must be in sequence without any intermediate blank legs because the generation of the duty plan file stops at the first blank line, i.e. a line without a date in the first column. It is important that each column contains only specific data, e.g. a date in the first column and no text in the 'Sched' time columns. - Please check especially days with special, non-standard notes on your duty plan. - Refer to chapter The 'Sync' Algorithm to learn more about the supported abbreviations and codes.
The 'Note' column is relevant for datebook events only if their generation has been enabled - the note will be attached to the datebook entry.
Note: PBS duty plans are issued in Swiss local time. During import, the schedule times are converted into UTC as the FliteLX application expects them so. However, only the Swiss time zone is handled correctly during this conversion. Other time zones (e.g. UK) have to be adjusted manually.

7. Press the 'Write' button. Select a place where to store the 'Plan.pdb' file. The file can be deleted after its installation, so an obvious place to store it would be the desktop.
By pressing 'Write', the following three error messages can occur:
- "Non-numeric schedule times": The indicated line contains letters in the 'Sched' columns'. This can happen if there were non-standard notes on the duty plan. Please go back to step 6 of this checklist and manually correct the line.
- "Numeric airport identifiers" : Same as above, but the 'Dep' or 'Arr' column contains a number instead of letters.
- "More than six legs defined": A particular date contains more than six entries. Delete a non-relevant line, e.g. a note.

8. Double-click on that file and perform a HotSync operation. This transfers the duty plan onto your Palm device.

9. Whenever you start FliteLX on your Palm handheld next time, the duty plan will be installed.

10. Delete the 'Plan.pdb' file, and press the 'Clear' button on the Excel sheet to clear the page. Once the 'Plan.pdb' file has been installed on your Palm handheld, it is not necessary to save the Excel sheet or to keep the 'Plan.pdb' file.


Producing the FTDR form

The 'FTDRfront' and the 'FTDRback' sheets will display the data from the 'FTDR' page of the Palm application. Once filled out, do not try to modify the cells directly on the sheet - it is necessary that the data is updated on the Palm device. The numbers to be carried over are compiled from the Palm database and not from the sheets.
The new FTDR form 2004 ('FTDR04front' and 'FTDR04back') will as well be filled out when you follow the checklist:

Checklist

1. Perform a HotSync operation.

2. Select the desired year and month and press the 'Sync' button.

If you do this for the first time or the Palm database backup file is not set, you must locate the 'FTDR-FLTE.pdb' file. Refer to General

3. Print the 'FTDRfront' and the 'FTDRback' sheets using the standard 'Print...' command of Excel. Sign the sheet before filing.

4. Store the filled out FTDR sheets. Press the 'Save' button and store a copy of the sheet. Only the 'FTDRfront' and the 'FTDRback' pages will be stored, with a name like 'FTDR 3LC YYYY-MM.xls'.

5. Press the 'Clear' button on the Excel sheet to clear the pages.


Producing the flight log

The 'Flightlog' sheet of the 'FliteLX.xls' Excel workbook will be used to generate a flight log out of the Palm handheld database in a way similar to a JAR pilot logbook.
Please note that the use of the FliteLX logbook function is not certified by the respective authorities. It is a handy tool to print out the logged flights, to calculate the sums of a month and the night flight time, but its use doesn't release you from maintaining a conventional flight log.

Checklist

1. Perform a HotSync operation.

2. Enter a 'Forward until' date into cell 'D2' (DD.MM.YYYY) - chose a date at the end of a month. Then enter your flight hours forwards until and including that 'Forward until' date into row #2, as in the following example:

Forwards.

The 'Forward until' date does not necessarily have to correspond with the 'Date of Entry' of the FliteLX application. During step 3 of this checklist, record times after that date but before the sheet date will be cumulated and forwarded accordingly. Flight log records older than that date won't be listed in the log.

3. Select the desired year and month and press the 'Sync' button.
Now the sheet is filled out accordingly.

If you do this for the first time or the Palm database backup file is not set, you must locate the 'PlanLog-FLTE.pdb' file. Refer to General.

4. Print the 'Flightlog' sheet using the standard 'Print...' command of Excel.

5. Store the filled out flight log. Press the 'Save' button and store a copy of the sheet. Only the 'Flightlog' page will be stored, with a name like 'Log 3LC YYYY-MM.xls'.

6. Press the 'Clear' button on the Excel sheet to clear the page.


Producing a Crew Wish form

The 'Wish' sheet is an easy way to print out a Crew Wish form with a filled out header.

Checklist

1. Press the 'Sync' button. This fills out the header of the form.

If you do this for the first time or the Palm database backup file is not set, you must locate the 'FTDR-FLTE.pdb' file. Refer to General.

2. Fill out the desired crew wishes

3. Print the 'Wish' sheet on yellow paper using the standard 'Print...' command of Excel. Sign the sheet before filing.

4. Press the 'Clear' button on the Excel sheet to clear the page.

 


Reference

UTC / local time

Generally, the times on the 'Plan' and the 'Log' pages are in UTC, while the 'FTDR' page is in Swiss local time (OM-A, 7.6.2.1).
When you press the 'Now' button on the time select form invoked from the 'Log' page, the system time in UTC is given, as long as the Palm system time is set in Swiss local time.
The generated datebook events are in local time, i.e. UTC+2h from last Sunday in March, 0100 until last Sunday in October, 0300; UTC+1h otherwise.
The calculation of the window of circadian low (WOCL) according OM-A 7.2.10.1 to identify a night duty when synchronizing the FTDR page. Only Swiss local time is implemented however.


The FliteLX databases

It may be important to note that the FliteLX application handles two databases: The plan/log database ('PlanLog-FLTE.pdb'), with the record fields that can be accessed on the 'Plan' and the 'Log' pages, and the FTDR database ('FTDR-FLTE.pdb'), represented by the 'FTDR' page. During each HotSync operation, both databases are backed up on your desktop PC. Those two backup files are read by the 'FliteLX.xls' Excel sheets when producing the FTDR form, the flight log or the Crew Wish form.
The fact that the two databases are independent (the only link between them is made when pressing the 'Sync' button on the Palm 'FTDR' page) means as well that it is possible to use the flight logbook and the FTDR features separately; if only the FTDR sheet is used, it is not necessary to update the flight log and vice versa. If you decide only to use FliteLX for FTDR purposes, download your duty plan and perform a 'Sync' even without having entered chocks times in the flight log. Then simply enter the total block times, the number of landings and the C/O times.


Manually entering flights

Besides the electronic download of your duty plan, you can enter flights manually, e.g. when you are called out of reserve, received a change, or simply didn't download the duty plan.
As soon as a flight number has been entered and stored (e.g. by tapping on some empty area on the 'Plan' page), the system tries to locate the schedule database of the FlitePilot application ('Schedule.pdb'). FliteLX looks up the flight number and fills out the 'Dep', 'Sched' and 'Arr' fields accordingly. Flight numbers with varying times on different weekdays are supported.
If the schedule database is not installed, FliteLX searches through its own plan/log database as a second priority and checks if that flight is already stored there.
Note that it is possible to enter the flight number without the prefix 'LX' - the application will automatically append it as soon as you tap on an empty area on the screen.
For return legs to 'ZRH', 'BSL', 'GVA' and 'LUG', another entry help is implemented: When you add a leg after an existing one, the flight number of the preceding is increased and FliteLX tries to find the corresponding data according to the procedure described above. If it was not possible to locate the flight number, the 'Dep' and 'Arr' fields of the preceding flights are copied and swapped, the 'Sched' times however remain blank.


Which duty descriptions are recognized as flight duties?

A leg is considered as being a flight duty when the chocks times entry is enabled. This is the case when either the duty text is empty or contains digits but no substring like 'DH/', 'SBB', 'TRAIN', 'EPR', 'GR', 'CHK', 'LPC', 'OPC', 'ASS' (assisting in simulator) or a capital 'R' followed by digits (reserve duties).

Private, non-commercial flights are logged by entering a leg without a flight number / duty description. These flights won't be synchronized when pressing 'Sync' on the FTDR page. This feature however is not yet supported by the flight log Excel sheet.


The 'Sync' Algorithm

The 'Sync' button on the FTDR page compiles the plan/log data to an entry for the FTDR database. Please adhere to the following guidelines:

- The C/I begins 60 minutes prior to a flight duty (see previous chapter) for all aircraft types except MD80 (75 minutes), 30 minutes prior DH/POS (except for train POS where the departure time of the train counts), 75 minutes prior to a simulator session, and 90 minutes prior to VIP flights ('VIP' leg).

- The C/O is 30 minutes after on chocks, 60 minutes after a simulator session, and equal to the arrival time for positionings.

- Off days do not have to be synchronized (but they may) because a day without an FTDR database entry is considered as an off day. However, when you decide to log them in the FTDR database, they must have one of the following duty texts: 'OFF', 'B-OFF', '----', '---', or '-' (without quotation marks; case insensitive).

- Reserve days however require an FTDR entry. The same is valid for vacation or military days or similar:

- Vacation days: 'VAC', 'VAR', 'V', 'Vacation', or 'Ferien'.

- Military days: 'MTY', 'MIL', 'Military', 'Militaer', or 'WK'.

- Sickness days: 'SICK', 'K', 'Krank', 'Accident', or 'Unfall'.

- Split duties: The algorithm only recognizes a split duty when the name of the first leg is 'SPLIT'. This is exactly what is generated when the crew plan file is downloaded.

- A 'N/S' is generated if the arrival airport of the last leg of the day is unequal the crew base from the 'Particulars' form. So this field has to be set accordingly.

- Instruction days must have an 'I ' preceding the duty text on the 'FTDR' page. This can be entered manually on the 'FTDR' page itself or by means of a leg called 'INSTR' on the 'Plan' page. This will produce that leading 'I ' on the FTDR duty text once 'Sync' is pressed.

- Simulator duties are recognized when they either contain one of the substrings 'CHK', 'LPC' or 'OPC', or when a leg called 'SIM' is at the beginning of the 'Plan'. The latter is valid throughout the whole current day.

- Layover days ('LAYOVER'), EPRs ('EPRxxxx'), office days ('OFC'), meetings ('MEET') and FEROP days ('FEROP') are recognized and will generate the respective time spans on the 'FTDR' page upon pressing 'Sync'.


The Flight Log

There are three happenings behind the scenes that have to be mentioned concerning the current implementation of the flight log:

- Whenever you have selected the 'CMD' position on the FliteLX 'Particulars' page, all flight times will be logged as 'PIC' hours; they will appear in the 'Copi' column if 'F/O' is selected respectively.

- Night time and landings are calculated according to the HR* tables of the Swiss VFR AIP Vol 2, issue of year 2002. This is only a rough estimate as the exact duration of the night depends on the geographical location.

- The 'IFR' hours correspond to the 'IFR' hours from the 'Log' page on the Palm. However, the application on the Palm stores them in a decimal format (e.g. '1.2') while the Excel flight log displays them as hours and minutes. This may lead to discrepancies as the example '1.2' ranges from '1:09' up to '1:14'. The current implementation simply multiplies the decimal number with six minutes, i.e. '1.2' will be written as '1:12'. The only exception is when the IFR time equals the rounded block time; in that case the IFR time will have the same amount of minutes as the block time span.

 


Back.

 


Last modified 2004 Aug 05
Copyright © 2000-2005 Christoph Regli