Already supported:

Sabre, Airline solutions, Crew Trac, Flica, Air Canada, British Airways, United, South West, Cathay, Kuwait Airways, Monarch, Onurair, Ryanair, West Jet, Dragonair, AirTran, Air Wisconin, America West/US Airways, ASA, Compass, gojet, Freedom, Frontier, jetBlue, Mesa, Midwest, North American, Republic, Spirit, TSA, Virgin America, Continental, Express Jet, Alaska, American Airlines, American Eagle, WinBid 7

Now supported with LogTen Pro Mac 5.5.x (Free update for LogTen Pro 5 users):

Aegean Airlines, Aer Lingus, AeroLogic Airlines, AIMS, Air Arabia, Air Austral, Air France/KLM, Air Greenland, Air New Zealand, Air Nostrum, AirBerlin, AirBlatic, Alitalia, ASA, Britair, British Midland, Bueling Airlines, Cargolux Airlines, CityJet Airlines, CRS/Kronos, Delta Airlines, Easy Jet, Emirates, Etihad Airways, Eurofly Airlines, FedEx, Fly Niki, Flyglobespan Airline, Gulf Air, Hamburg International (TUIFLY), Horizon, Iberia Airlines, ICS, Indigo, Indigo Airlines, Jet Roster, Jet2 Airways, Jetstar Airways, Lan Airlines Chile, Lan Argentina, LOT Polish Airlines, Lufthansa, Martinair, Meridiana Airlines, Nordic TUIfly, Norwegian Air, Norwegian Air Shuttle, PrivatAir, PSA Airlines, Qantas, Qatar Airways, RM Rostering System, SAA Airlines, SAS, Scandinavian Airlines, SkyWest, Sunwing Airlines, TAP Portugal, Thomas Cook, Tiger Airways Singapore, Transavia, Tyrolean Airways, UPS, Wizz Air.

• Open your schedule
• Open each trip you would like to import
• Copy all the information in the trip screen
• Paste it into the schedule importer in LogTen Pro.
• Click Continue, verify the data looks correct and is going where you want it, then hit Import!

• Enter the Tracey system on BA’s intranet
• Open a month’s roster in the CrewLink section of the intranet.
• Copy your entire month’s roster
  - You cannot load a month’s schedule for a month that has already past
• Paste it into the schedule importer in LogTen Pro.
• Click Continue, verify the data looks correct and is going where you want it, then hit Import!

• Open your schedule by hovering over the ‘Schedule’ menu at the top right of the screen
• Click on “mySchedule”
• Copy EVERYTHING on the page
• Paste it into the schedule importer in LogTen Pro.
• Click Continue, verify the data looks correct and is going where you want it, then hit Import!

• Select the month you wish to import under the “Schedules” folder in the “Crewmember Menu” to the far left
• When the schedule displays select “FFDO format” under “Schedule Options”.
  - Select the “Include Deadheads” checkbox if you wish to include deadheads.
• Copy the entire schedule that is displayed
• Paste it into the schedule importer in LogTen Pro.
• Click Continue, verify the data looks correct and is going where you want it, then hit Import!

What to Send Us

FlightLevel 2000 or later
To find your FlightLevel files, look in C:\Program Files\FlightLevelXXXX\Flights where the “XXXX” is the version of Flight Level, probably 2003. Zip up and send us the whole “Flights” folder (it should contain your “.dbf” files).

SkyLog Pro version 5.x
For SkyLog Pro send us your backup file, which should have the .bck extension.

Come fly the [user] friendly skies!

In LogTen Pro 5 you can manage a database of airports. When you enter a From or To value for a flight it looks for a match in the airport database (the Airports tab of the Resource Manager). If it doesn’t find one it will search the internal database of over 27,000 airports worldwide, if it finds a match it will create a new entry in your airports list in the Resource Manager and copy the data from the internal database, if the field is STILL not found it will simply create a new empty entry in your airports list and set it’s ICAO ID to whatever you entered in the “From” or “To” field.

The “From” and “To” fields are much more than just a few characters, it’s a link to a specific airport that allows LogTen Pro to do things like calculate the distance of your flights, instantly change how your “From” and “To” fields are displayed (in the Preferences you can select from ICAO, IATA, or Name) as well as a reverse relationship to every flight that uses it so that you can look at a particular airport and instantly see how many arriving and departing flights you have.

From and To airports should always be a single airport identifier. Route information should be entered in the “Route” field.

Many pilots like to record a days flying as a single entry, and it is not uncommon to see a sequence of sectors in the “From” or “To” field. For example on a flight from Denver International Airport to Seattle’s SeaTac Airport via Los Angeles International and Phoenix Sky Harbour you might see something like this in the “From” field: KDEN-KPHX-KLAX and then KSEA in the “To” field. As you may have already guessed from the first paragraph, this will result in a new airport being created in your list with the ICAO ID of “KDEN-KPHX-KLAX”: not good. So the next time you go to enter a flight to KPHX, you’ll get “KDEN-KPHX-KLAX” auto entered because it found a match!

So the way it was designed, you would enter the starting point, and the end point, and then enter route information in the route field. Note that at any time you can choose “Get Airport Data” under the Manage menu to fill in missing data from the internal database where available. This means if you’ve got an airport with just and ID, such as KDEN, running this command will look up KDEN in the internal database and fill in the IATA, the Name, Lat, Lon, City, State, Country etc if the information is available.

What if I Already Entered My Data This Way?

If you’ve got a bunch of data entered in this fashion, and you need to clean it up, the best thing to do is export your flights to tab delimited file, then open it in a spreadsheet application like MS Excel for cleanup. Here you can create a calculated field to just grab the first identifier from your list of fields (“From” in our example above) and make a new, single identifier, “From” field. Then you can import your data back into a new empty file in LogTen Pro importing the old from information into the “Route” field and your new “cleansed” from information into the “From” field.

Enter a flight with totals for each aircraft type

To enter past totals just create one or more flights and enter the total times you’d like to use as starting points, you can set the date to whatever you like (probably the date of the last flight included in the total would make sense). You can decide how much detail you want, e.g. you simply enter one flight and set the appropriate totals (1139 PIC, 874 Night, etc.) or you could add a separate flight for each aircraft type to be more precise.

A Note About Times Like Jet, and Multi-Engine Land…

Because LogTen Pro automatically tracks time by type, such as Multi-Engine, Jet, etc, if you want these totals to be correct It’s important to specify the correct type for your balance forward entries. Because we’re just concerned with Engine Type, Category and Class you can simply create some generic types that cover all Jet, Multi-Engine Land, Airplane…

If You Use Reports That Display Each Type of Time as Day and Night…

If you plan to use reports that break time down into day and night, such as the Canadian or South African reports, then when you enter a balance forward you should make a separate entry for each type of time. E.g. one for your PIC/P1 totals (including night), one for SIC/P2, one for Dual, etc. Otherwise the reports will see PIC, SIC, Dual and Night all on the same flight and it will be unable to calculate the day/night totals correctly.

Importing Your Data…

Open your old logbook and export your data to a tab delimited or CSV text file. If your data is on a PC, then you can usually just email the exported file to yourself so you can get it on your Mac.

Now open LogTen Pro, and select “File->Import From File… -> Flights” under the File menu. A standard Open Panel will appear, here’s where you select the file you exported from your old logbook software. Select the file and click Open.

The LogTen Pro import sheet will open, displaying a table. On the right you’ll most likely see a a list of repeating “Do Not Import” items, and on the left the column headings from your data. To import your data you go down the list, and for each item click the “Do Not Import” (they’re menus) and select the appropriate item. e.g. if the first item in your data is “Date”, then you would select “Trip -> Date” from the menu next to the cell where “Date” appears in your data. You can use the left and right arrow at the bottom to page through your data to verify it’s going to the right place.

Make sure you map the aircraft type

If you haven’t already I highly recommend you read this article about how LogTen Pro manages aircraft before proceeding. It is important that the aircraft type (usualy a concatenation of make and model such as B752 for the Boeing 757-200 or C-172 for the Cessna 172) be mapped correctly, as LogTen Pro wants to have only a single entry for each aircraft type and it then links every aircraft of that type to the same aircraft type entry. This is a huge time saver and enables many features down the road.

When you’ve got everything identified correctly, click “Import”, and LogTen Pro will import all your data, and create the necessary relationships between flights and aircraft, crew, airports etc. so you can take advantage of all the great features in LogTen Pro.

Notes specific to Logbook Pro Users

We highly recommend using Logbook Pro’s option to export to Excel, then saving the CSV file from Excel as this can eliminate possible issues if any of your fields, such as Remarks, contain commas.

Route data

Logbook Pro does not track your “from” and “to” airports separately but simply provides a route. When importing make sure you map the route data from Logbook Pro to the “Route” field in LogTen Pro, otherwise you’ll end up with multi-aiport “route” information in your “from” and “to fields which will not be useful.

Times (Such as Departure and Arrival Times)

If you are importing clock times, such as departure and arrival or block times you should check the data exported by Logbook Pro as it may be formatted hh.mm. If this is the case it will not import into LogTen Pro correctly (unless your time format in System Preferencs is set to that).

You need to either reformat those columns in a program like Excel to use hh:mm (note the colon rather than the decimal) before importing. Alternatively you could modify your systems time format to hh.mm in System Preferences -> International -> Formats.

LogTen Pro 5 automatically updates your data file. The first time you start up your logbook with version 5, a window will pop up for a few seconds telling you that your data is being updated to the latest model, and you’re off and running!

Upgrading from 2.x

First of all, don’t worry, LogTen Pro 3, 4 & 5 do not touch LogTen 2.x data in any way. If you’ve upgraded to LogTen Pro 3.0 and you’re not seeing your data, chances are you were not running the latest version of LogTen (2.7.12) prior to updating.

LogTen Pro 3.0 automatically imports data from LogTen 2.7.12. If you did not have 2.7.12, you can download it here.

Just fire it up, make sure you have “All Flights” selected on the left, and then quit. Now launch LogTen Pro 4, and if you haven’t saved a document yet it will open an empty one and automatically import your data from LogTen 2.x. If you HAVE saved a document in LogTen Pro 3 or 4, then simply create a new logbook under the File menu and it should automatically import.

(If for any reason the import does not begin automatically, the file exported by LogTen 2.7.12 is located in your home folder at ~/Library/Application Support/LogTen/LogTenData.txt. You can open a new document in LogTen Pro 3 or 4 and select Import -> Flights under the File menu, then select this file and choose import.)

All this is necessary because LogTen Pro 3 and 4 use a new data architecture (Apple’s CoreData framework) to provide dramatic speed and reliability improvements, thus it cannot read the old data files. LogTen 2.7.12 exports a special file that LogTen Pro 3 and 4 can import.