Logbooks

• Logbooks
• Create
• Edit
• Void
• Close

Logbooks

When you first sign up, you will have no logbooks created. This means, because there is no airframe logbook, the system does not know anything about your aircraft, and you basically cannot do anything in the system until you at least have an aircraft logbook set up. The first step is to create an airframe logbook!

Creating a Logbook

To create a logbook, go to Your Aircraft on the left hand side menu and, after the page loads, click the Logbooks button on the respective aircraft you wish to add a new logbook to.

{primary} Have multiple aircraft on the system? You will see them all on this page.

In the next screen, enter in a make/model, manufacture year, serial number, and number of engines. Click Create New Logbook. After you make the airframe logbook, you can then add subsequent logbooks like Engine, Propeller, APU, etc (the order in which you add them does not matter).

{info.fa-question} Not seeing your aircraft make/model? Don't worry, you can add it! The only thing we do require, however, is a real tail number because we no longer support aircraft still being built. Just type in the make/model you are looking for and then click
That model wasn't found. Want to add it?

{success.fa-cogs} Quickly and easily add tracking items right from the logbook page! Once a logbook is made, you can click Add Components/Overhaul Times to add tracking items to your aircraft. Depending on your aircraft, there may be a template set up for you already that you can optionally use.

{primary} Hint! If you are editing a logbook, you can quickly go back to the list of all your other aircraft by clicking the Aircraft circle:

Editing a Logbook

When editing a logbook, you may change the following details: Manufacturer Year and Serial Number. You may not, however, change the position or make/model. If you need to adjust those and do not wish to void the logbook (and start over), please contact us.

Voiding a Logbook

On a rare occasion, you may wish to void a logbook. This usually happens if you entered in the incorrect make/model to begin with and have caught it early enough that you will not lose much progress by voiding the logbook. Void logbooks will result in their underlying entries and tracking items being hidden from subsequent views.

{danger.fa-exclamation-triangle} Void logbooks will have their contents (maintenance entries and tracking items, for example) removed from subsequent views throughout the app! As far as the system is concerned, this is much like throwing out a paper logbook (except we won't delete data associated with void logbooks)!

Closing a Logbook

Sometimes you need to close a logbook. This usually happens when the component that the logbook refers to (for instance, an engine), is overhauled or remanufactured. If you close a logbook, the underlying entries and tracking items that were apart of that logbook will disappear from subsequent views.

{danger.fa-exclamation-triangle} Closed logbooks will have their contents (maintenance entries and tracking items, for example) removed from subsequent views throughout the app! Don't worry though, we won't delete the data associated with closed logbooks.