Digital aircraft technical log: import your QTB

The technical log (QTB) is the register of the aircraft: every flight with date, crew, route, times and meter readings. If it is still on paper or in a spreadsheet, you can bring it into AVIOFILE: every flight joins the history of the aircraft and the people named in it get a request to confirm theirs.

Before you start

You need to be able to record flights and edit everybody's flights on the aircraft: the administrator and the instructor have it, a co-owner only if it is granted. Without it, the Import the technical log button does not appear.
A file can be Excel, CSV, Word or a PDF with text. Photos and scans are not read: if the log only exists on paper, type it in.
Flights already included in the aircraft counters are recorded as historical: they join the history and the statistics of the aircraft, but do not change counters or due dates.
Nothing is written until you confirm from the preview.

Import from a file

Open the aircraft, go to the Tech log tab and tap Import the technical log.
Leave File, tap Choose files and select the log (or its sheets): up to 20 files.
Tap Read the log and wait: the reading goes on if you leave, and you find the import again under OPEN IMPORTS.

Type in the paper log

In the same screen tap Type in, then Start typing.
Write one row at a time as on paper: Date, From, To, Pilot in command, Instructor and Student (free text), the times, the meters Hobbs start and Hobbs end, the landings, the fuel and the Remarks.
The return key of the keyboard moves to the next field. Add a row creates a new one that takes the date, the arrival airport and the final meter of the row above.

When you are done tap See the preview.

Check the preview

In Review the technical log you see how many flights go in, which are Already registered (they are not imported twice) and the Rows with errors, to fix or leave out.

Aircraft counters: the values before and after the import. With Which flights move the counters choose Automatic (flights already included in the counters are historical), All or None.
Automatic corrections: the app fixes small things, for example the meter start taken from the flight before. Tap Undo and the value written in the log comes back.
Defects: the defects written in the log. By default nothing is opened; with the switch you choose which ones to open as a squawk on the aircraft, and tapping the row sets the severity.
Rows: tap a row to fix it, leave it out or, if it is a duplicate, Import anyway. If you typed the log in, Edit in the transcription takes you back to the grid.
Technical flights: when the log writes "VOLO TECNICO" where the pilot goes, the row becomes a technical flight with no person and carries the notice Technical flight, pilot not named. Open it and tap Say who flew it to write the name: the flight stays technical and the name appears among the People, where you link it to a member like the others. If you leave it empty the flight goes in without a pilot and stays among the aircraft's technical flights to assign (see Log a flight).
Organizations: a name like "AEROCLUB" or "Alfa School" is not a person: the row carries the notice This looks like an organization, not a person: it stays an outside name (you can still link it by hand).

Link the people

In People you see the names written in the log and the person suggested. Only people already linked to you for this aircraft are suggested: members and co-owners.

If more people match, the name stays to decide: tap it and choose, or search among the linked people.
Keep it as an external name leaves the name written on the flight, with no account.
Back to the suggestion undoes a choice of yours.

Import

Tap Import N flights and confirm. The summary says how many flights go in, how many move the counters and how many people will receive the request to confirm.
If The people changed appears, nothing was written: somebody is now linked differently from before. Check People again and import again.
Importing the same log twice creates no duplicates.

Flights to confirm

Anyone named in a flight recorded by somebody else, from an imported log or by hand, finds it on the Home and at the top of the Logbook, in both Flights and Totals (N flights to confirm), and in Flights to confirm. Until they accept it, the flight is not in their logbook, totals or charges.

Accept brings the flight into the logbook; Accept all accepts them all together.
Reject asks for a reason: whoever recorded the flight and whoever manages the aircraft read it. The flight stays on the aircraft with the name written in the log.
If you do not answer, the flight is accepted on its own after a few days: under the flight you see the date.
When a school or a club records your lesson or rental, you only choose whether to keep it in your logbook: Save in logbook or Don't save (the reason is optional). The charge is already made.

Disputed flights

Whoever manages the aircraft finds the rejected flights under Disputed flights (in the aircraft menu, and in the organization settings under MANAGEMENT), with the reason. Put back to confirm offers the flight to the person again; Leave as external name closes it leaving the name written.

Frequently asked questions

Why is a flight «Historical»?

Because its meter is already included in the aircraft's: counting it again would double the airframe hours and every check by hours would look overdue.

Can I undo an import that was already applied?

No, but each flight can be edited or voided from its detail. An import still open is dropped with Discard this import.