Before Pilots/FIs can record their flights in FlightLog a user with editor rights (or a technician with B1 qualification) must initialise the aircraft by manually saving the first FlightLog.
In Frontend choose FlightLog and select the aircraft from the list. You will be prompted for the Access Key (copy / paste from the aircraft form). After saving the Access Key you may have to select the aircraft again from the list.
The access key is stored as cookie on the current computer, and must be set on each client computer for each aircraft to which the client should have access to.
The FlightAssistant will open automatically. Upload the necessary Board Documents here.
Exit from the assistant to show the FlightLog form.
In the FlightLog form, the flight time, landings and other counters set in the Aircraft init-values are shown in the carry over fields.
Now you can create the first Release to Service (RS) to set the type, flight time, date and tolerances of the ‚Next Part-145 inspection‘.
Signing the Release to Service (RS) marks it as completed.
Your aircraft is now ready to fly!
Start the FlightAssistant to record a flight on the same day, OR sign ‚NAME / SIGN-OFF PIC / FI‘ in the FlightLog form to mark the FlightLog as completed – the next user will be presented with a new FlightLog with the correct date.