Nimblefeet is using an Advantage ADT database. Zip the following 4 files :

– aircraft.adt
– approach.adt
– crew.adt
– flight.adt

Most of the time these files are located here C:\Program Files\CKW4 (Windows XP) or C:\Users\%username%\AppData\Local\VirtualStore\Program Files\CKW4 (Windows Vista-7).

Send the entire Microsoft Access database file (named Mikelsoft_Crewlog_….mdb) for conversion.

Mikelsoft does not differentiate between Instructor and Examiner. When you are ‘CHCKER’ on the flight or in the simulator, these hours are imported as Instructor time.

Export flight records to a ( by preference TAB delimited ) CSV or TXT file, or send the entire database.

Aviatorsoft does not log or export Takeoff (Day/Night). After importing records from Aviatorsoft, use the multiselect function from CrewLounge PILOTLOG to generate Takeoff and Landing.

Send the DBF Database. The file is named something like yourname.dbf (e.g. branson.dbf).  ZIP all files !

We also need a screenshot of the flight list, as shown here !

Export flight records to a TXT file. We only need the FLIGHTLOG.TXT file and optionally also the Simulator records TXT file.

Airfields in the Stratosoft file are printed by their long name, instead of the unique ICAO or IATA identifier. Since there are 4 ”Sydney” airfields and 6 ”Denver” airfields worldwide, the name of the airport cannot be used as reference… You will have to replace all airfield names by the official ICAO or IATA code.Since we do not know on what Denver or Sydney airfield you have landed, we cannot do that step for you… The CrewLounge PILOTLOG Import Wizard comes with a semi-automatic ‘Airfield Look-up’ function that will assist you with this process.Flight hours in the Stratosoft export file are saved in the wrong time format. A flight departing at 13:45 is saved as 1:45 without mentioning PM. A total flight duration of 50 minutes is logged is 12:50 instead of 0:50. If you look at the TXT file, you will see it is contaminated with many 12:00 time fields… The CrewLounge PILOTLOG import wizard comes with extended clean-up logic to deal with this contamination. The results are satisfying but may fail in some cases (e.g. an afternoon flight is imported as a morning flight or a 12:30 hours long distance flight is reduced to a 30 minute flight…).

From the webportal, export your data to a TSV file (Tab Separated Version).

CrewLounge PILOTLOG does not cater for ROUTE entry. Read Note (*1) below !

#Plane information at the bottom of the TSV (or new CSV) file is not imported. You need to go through the Aircraft list on de Tables – Aircraft page and adjust all properties.

From the FlightCrew iLog iPhone app, export your data into a CSV file.

Approach Type is not imported because the data is spread over too many columns.

Export flight records to a ( by preference TAB delimited ) CSV or TXT file

The wizard imports approach data from the “other approach” column only. CrewLounge PILOTLOG does not import the many other approach fields, because the data is spread over too many columns.

Export your flight details from the desktop or iOS device, as follows :

– Menu (or Reports) > File > Export > Exporters
– Export Flights (tab)
– Generate Report ( “Save As… ” )

We need only the FLIGHTS file.

Or, you can submit the entire database, typically named ‘LogTenCoreDataStore.sql’ or similar. That will work too. File extension is then SQL or SQLITE.

Export flight records to a ( by preference TAB delimited ) CSV or TXT file.

The CSV file does not provide Aircraft Model information, so the import wizard will default all aircraft as Model X. You will have to edit all aircraft after import. Use the Multiselect function on the Tables page to mass edit all aircraft with a single click.

From the website pilotlog.co.uk download a back-up file. Rename the file from pilotlog.dat into pilotlog.zip. Unzip the file.

Inside the ZIP file, you find different files : Flights, Simulator, Previous Experience, Duties
Previous Experience and Duties cannot be imported into CrewLounge PILOTLOG because essential information is missing in those files. You can enter total hours for simulator and aircraft through the Tools – Previous Experience page in CrewLounge PILOTLOG.

Submit the Flights file for conversion. File extension must be CSV

The Simulator file shall be uploaded later. Do not upload both files together ! Instead, submit one file at a time and wait with the second request until you have received the first converted file from us !

Rosterlog is storing each flight day in a separate file.

ZIP all RLD files into a single archive file.

From the Skylog File dropdown menu, select “Export Flight Records” to export your flights to an Excel file.

Skylog generates separate files for Flights and for Simulator. Do not upload both files together ! Instead, submit one file at a time and wait with the second request until you have received the first converted file from us !

File extension must be XLS or XLSX.

From Xineo, export your data as HTML file.

We noticed some bugs in the HTML file, such wrong dates (1 month offset) and no airfields listed.

Export flight records to a ( by preference TAB delimited ) CSV or TXT file.Make sure all desired columns are included in the CSV file, such as Block Hours. You can change the columns in Zululog under Pilot Logbook -> Flight Preferences -> Flight Viewer Preferences.

CrewLounge PILOTLOG does not cater for ROUTE entry. Read Note (*1) below !