User guide

Try a sample before signing in

1. On the website, select Try a sample logbook.
2. Search or filter the fictional flights. Choose Summaries to see hours by aircraft, or View details for one entry.
3. Use Clear filters to restore the full list. Reloading the page resets your choices.

The sample is read-only and needs no sign-in or calendar connection. It cannot edit your logbook. If it will not load, select Try again; a successful retry moves the cursor to Search flights. The PDF link remains available if loading still fails. The sample PDF always contains the complete fictional period and separate opening totals, regardless of the screen filters.

First-time setup

1. Select Open logbook at the top of this guide. Sign in with an available service, or use your existing username and password. Use the method linked to your account.
2. Follow the setup prompts. Choose your type of flying and, if you wish, your pilot licence and usual aircraft or role.
3. For Air NZ flying, choose your work calendar. You can leave this until later.
4. Choose how to bring in previous flying: individual flights or opening totals.
5. Review your choices and finish setup.

Leave optional settings blank if they do not apply or you do not know the value yet.

Your aircraft list starts empty. Add your own aircraft in Settings → Aircraft types.

To repeat setup, open Settings → Run guided setup. To add previous flying later, choose Set up previous flying.

Find the right page

Use the header navigation on a computer or tablet. On a phone, use the bar at the bottom. The highlighted page is the one you are viewing.

Website, Privacy policy and User guide links open a separate tab. Your current entry stays in the app.

If a sign-in option is missing

1. Select Retry sign-in options if offered.
2. If it still fails, use another sign-in method already linked to your account, or try again later.

Retrying does not submit your username or password. Only configured services are offered.

Loading times

Settings → Loading times is shown only to beta-enabled accounts. It reports recent request times, not flight details or calendar names. Ordinary settings cannot enable beta access.

Check recorded expiry dates

1. Open Settings. Enter Medical valid through, Flight review valid through or Certified check expiry from the relevant record.
2. Select Save settings if you changed a date.
3. Check the date reminders in Summaries against your records.

Email and push reminders are not available yet. Calendar reminder downloads have been removed. If you previously imported a reminder file, its events remain in your calendar; remove or adjust them there. Changing a date in Good to Go does not update those events.

Enter hours correctly

For hours and minutes, use H:MM: two minute digits, from 00 to 59. Typed seconds are not accepted. A valid value converts to decimal hours when you leave the field or save.

Log Flight rounds hours to the nearest 0.05 hour. The entry editor and Air NZ Ground IF preserve decimal precision instead.

Entry checks

• A manually entered flight or simulator session must not exceed 24 hours.
• Opening totals and imported history may exceed 24 hours.
• Takeoffs, landings and approaches must be whole-number counts. Leave them blank if unknown.

If a field is marked invalid, correct it or clear it, then save again. The form keeps your other details.

Save several flights for later upload

Use Log Flight → Saved flights to keep reviewed flight copies in this browser until you are ready to upload them. A device draft, described below, is a separate copy of one unfinished form.

1. Enter a flight, open Saved flights and select Save flight for later.
2. Check the details, then select Save on device. The form clears after the browser copy is saved. Nothing has been logged yet.
3. When connected, choose Review flight → Upload flight. A confirmed result is marked Logged.
4. If a request takes too long, select Stop waiting. Waiting also stops automatically after about 20 seconds. The save may already have completed. Keep the copy and choose Check save result. This retries the same request safely. Reconnecting alone does not upload anything.
5. After checking the account logbook, use Remove copy → Remove device copy to remove an unwanted or confirmed browser copy. For Needs review, first check Logbook and select I have checked this flight in Logbook. Removing the browser copy does not delete a logged flight.

Up to 50 copies are kept for this account in this browser. They are unencrypted, can be lost if browser storage is cleared, and are removed at sign-out. Existing device drafts and timers are separate copies: check before using them again so you do not log the same flight twice. This preview does not support starting the app offline or automatic background uploads.

If the list changes in another tab or storage fails, retain useful details and select Reload saved flights. Keep uncertain copies until their save result has been checked.

Keep a device draft

A device draft is one saved copy of your unfinished form in this browser. It is not a logged flight.

1. Under Device draft, open the row if it is collapsed.
2. Select Save draft on device.
3. After making more changes, use Update device draft → Replace draft to update the copy.
4. To return to it, sign in to the same account, open Log Flight and select Restore draft.
5. Review the restored details, then select Save entry when ready to log the flight.

Restore replaces the current form. Save any different work first. To remove the browser copy, select Discard saved draft → Discard draft.

Optional saved flight shortcuts

A shortcut keeps reusable aircraft, registration, crew, route and role details. It does not store flight hours, counts or comments.

1. Open Settings → General → Saved flight shortcuts, enable it and select Save settings. Shortcuts are off by default.
2. In Log Flight, enter the details you want to reuse.
3. Open Saved flight shortcuts, enter a name and select Save current details as shortcut.
4. For a new flight, choose the shortcut and select Load shortcut.
5. Review the replacement, then select Load details. The cursor moves to Flight time. Enter the new flight's hours/counts and save when ready.

Loading keeps the chosen date, selects Simple and Day, and clears old hours, counts, comments, diversion and timer link. The separate timer stays. Check day/night, role and aircraft before saving. Save a device draft first to keep different work, or select Cancel to return to the shortcut button without replacing the form.

Select a shortcut to rename it, replace its details or remove it. Replacement/removal asks for confirmation. Turning the Settings switch off hides both saved shortcuts and last-flight tools, while keeping saved shortcuts for later.

Use the flight timer

1. In Log Flight, select Flight timer to open the timer window. New timers use block-to-block timing.
2. Select Start timer when moving off.
3. Select Stop timer when parked.
4. Select Log. Check or adjust the suggested hours and confirm that the form's hours may be replaced.
5. Select Load time into Log Flight. Check the date, aircraft, role, day/night and counts, then select Save entry.

Loading timer time does not save a flight. It replaces the form's hours and clears its activity counts; other details stay. Save a device draft first to keep different work.

Resume timer recovers an accidental stop. Time between Stop and Resume is excluded.

Closing the timer window keeps timing; its button shows the current status. Start/stop times use this device's local time zone and whole seconds.

Use an exported roster file

A calendar file ends in .ics. Use it to load a saved work roster without connecting the calendar account. It does not keep the roster up to date automatically.

1. Export your roster as an .ics file. Keep the original.
2. Enable Air NZ imports in Settings, then open Air NZ → Use a calendar file.
3. For repeating events, open Choose roster dates. Enter Roster start date and Roster end date, covering up to 366 days, including both dates. These use each event’s recorded calendar day. Leave both blank to keep all individual events.
4. Select the file under Calendar file (.ics). Alternatively, open Paste calendar text instead, paste the complete file and select Review pasted calendar.
5. Check the file name, dates, descriptions and counts. Daily and weekly series are expanded into individual occurrences. If you change the dates, select Review loaded calendar to check the same file again. Changing dates or pasted text clears the previous preview and confirmation.
6. Select the checkbox confirming the roster and unsaved Air NZ form may be replaced, then select Use reviewed roster.
7. Choose a flight, check its details and select Save entry when ready. Loading or reviewing a file never saves a flight.

Already logged flights are removed from the flight selector after loading the reviewed roster. The file stays in this page until you reload or sign out. Refresh flights rechecks saved matches; it does not fetch a newer file. To return to your connected calendar, select the replacement checkbox and Use connected calendar.

Import CrewCMS hours and crew

1. On Air NZ, choose your CrewCMS XLSX export. The file must be under 10 MB.
2. Review the proposed matches.
3. For an already matched entry, choose Yes to overwrite or No to keep it. Yes for All and No for All apply to the remaining choices.
4. Finish the review and merge the chosen updates.

If times are missing or invalid, correct the source file and upload it again. For formula cells, recalculate and save the workbook first. Choosing a replacement file clears the previous file's review.

Calendar privacy

Good to Go reads calendar events through its servers. Account controls separate users' data, but privileged operators can still access server-processed calendar information and stored logbook data. This is not an end-to-end encrypted service.

Selecting a work calendar limits the normal roster query; the provider's permission may cover other calendars. Read the Privacy policy before connecting.

You can revoke Google access in Google Account connections. This stops future access; it does not delete saved flights. Manual logging remains available.

Type flights beside a paper page

1. Choose Paper logbook: enter each flight, then expand Transcribe a paper page.
2. Enter a Paper reference (book and page), such as Book 1, page 24. This is added to each flight’s Comments.
3. Select Open page image, or select the paste box and paste a copied image. Use JPEG, PNG or WebP, up to 10 MB and 24 million pixels. Convert PDF or HEIC pages first.
4. Use Rotate left, Rotate right and Page zoom to read the page. Original view resets the view. Rotation does not change the image file. Open Focus on a page area and reading row to enlarge part of a page and keep your place.
5. Type one flight. Use decimal hours or H:MM, and leave unknown optional cells blank. Open Other recorded columns for additional hours and activity counts. Do not enter page-total rows or guess unreadable cells.
6. Select Keep flight in transcription. Repeat for each flight, up to 100. Use Edit flight … to correct a row, then Update transcription flight. Keep or clear the current flight fields before editing another row.
7. Check every row against the page, tick the confirmation and select Send to import review. This replaces the current import preview; it does not add flights.
8. Follow Import individual flights below: check the mapping, totals and duplicates, then confirm the import. If you change the transcription before importing, send it for review again.

To correct a flight already imported, edit it in Logbook. Re-sending changed rows can add another flight; it does not update the saved record.

Page images stay in this browser tab and are not uploaded or attached to flights. There is no handwriting recognition, automatic column detection or sticker removal. Keep the original page and signed records.

Stop and continue later

1. Keep or clear the current flight fields, then select Download transcription.
2. Check the file is in your downloads before leaving setup or refreshing. Nothing is saved automatically in this workspace.
3. To continue, select Load transcription and choose that JSON file, or expand Paste a transcription recovery file and paste its contents.
4. Check the replacement summary, then select Replace transcription. Open the original page image again.

The recovery file contains flight details and the paper reference, but no image. Store it privately. It is a working copy, not a logbook backup. A failed image or recovery-file read keeps your current work; correct the file and retry. Download blocked? Keep this page open, allow downloads and retry.

Import individual flights

1. Select Upload logbook file. Supported files: CSV, TSV or XLSX; up to 10 MB and 1,000 flights per import.
2. For a workbook, choose the worksheet. Select the header row (the row containing column names) and the date order used in the file, for example day/month/year.
3. Match each source column to a logbook field. The column position, such as XLSX column A/1, helps you find it. Ignore columns you do not need.
4. Check the sample rows, then select Check totals and duplicates.
5. Correct any errors. Compare the existing, added and final totals with your original logbook.
6. Tick the box confirming you checked the mapping, dates and totals against your original logbook. Select Import … entries; the button shows how many entries will be added.

Suggested mappings are a starting point. Check whether a column contains a crew name or hours, especially headings such as PIC, COP or SIC.

Mapped aircraft codes are added to your aircraft list. Review unknown engine classes and roles in Settings.

Reuse the same column mapping

1. After checking a mapping, select Download field mapping and keep the JSON file.
2. Upload the next logbook file and select its worksheet and header row.
3. Select Load field mapping and choose the saved mapping file.
4. Review the fields again, then run Check totals and duplicates.

Column headings must match exactly, including order, spaces and case. A different layout needs a new mapping. Loading a mapping does not import flights.

Keep a copy of the import review

Select Download review report before leaving setup. It saves the available mapping, errors, duplicate counts and checked totals to a JSON file.

The report helps investigate a problem. It is not a copy of your flights or proof that an import saved successfully. Check filenames and error text before sharing.

Save an import review for later

1. Open Settings → Set up previous flying and choose a file.
2. Review the mapping and run Check totals and duplicates where possible. A file error or duplicate-only result can also be saved.
3. Select Save review to history. Wait for Review saved. This saves a report to your account; it does not add flights.
4. To find it later, open Import history → Saved review reports. Select Load older reviews for earlier copies, or Download saved review for a JSON file.

If the save is not confirmed, retry the same button or select Download review report before leaving. To correct an import, choose the original file again and run a fresh check. Reports do not contain the flight rows needed to restore a logbook.

Save not confirmed describes an uncertain flight upload. Check Logbook and completed Import history before trying that upload again. A saved review is not an import receipt. Filenames, column headings, errors and checked totals can contain private information; check before sharing. Reports are saved only when you select the save button; older attempts are not backfilled.

Undo an import and start again

1. Open previous-flying setup and find Import history.
2. Select the batch, then Undo import.
3. Check the entry counts and flight/simulator hours to be removed.
4. Select Confirm undo.
5. Upload the corrected file and review it as a new import.

Undo excludes every entry in that batch, including entries you edited later. They remain available for recovery but leave totals and PDFs. Other batches, opening totals and aircraft choices stay unchanged.

Add aircraft types found in your saved records

1. Open Settings → Aircraft types.
2. Open Add types from my logbook. The list shows codes found in your saved records that are missing from My aircraft.
3. If needed, enter a code under Find a logbook type. Select Review beside the type you want.
4. Check Type code, enter a useful Name, then choose Engine class and an optional Default role. These are your choices; the app does not infer them from old flights.
5. Select Save aircraft. Wait for Aircraft saved. The type is now available for future flights and disappears from the suggestions.

No aircraft is added merely by opening the list or selecting Review. Existing and hidden types are not suggested again; edit them in My aircraft. Excluded records are not used. Record counts can include opening totals and simulator sessions; they are not flight counts.

If there are no matches, clear the search. If a type code cannot be added, correct the source record in Logbook, then return to Settings. If saving fails, keep the draft and retry. For Aircraft type changed, select Reload aircraft and review the current definition. Adding a type never rewrites historical flight hours or classifications.

Review activity for a month, year or aircraft

1. Open Summaries. Choose an Aircraft type, or keep All aircraft.
2. Open Activity report.
3. Choose Report grouping: Month, Year or Aircraft.
4. If required, enter Report from and Report through. Both dates are included. Select All report dates to remove the date limits. These dates apply to the activity report.
5. Read the flight and simulator record counts and hours. Open View … records beside a group to see the supporting dates, aircraft, route and times. Use Show more report groups or Show more supporting records when offered.
6. To keep a summary copy, select Download activity CSV. The file contains every matching group and the total, including groups not yet shown on screen.

Opening totals and excluded records are left out. Simulator hours stay separate from flight hours. Dates use the calendar day saved in each entry. Hours are decimal hours; totals are added before rounding to two decimal places for display. One saved record can contain both flight and simulator time.

A missing-time message means some records have blank or invalid time fields. Only usable hours are added; an explicit zero is kept as zero. Open the supporting records, then use Logbook to correct the entry. Records without a valid date appear under Date not recorded when all dates are shown; date limits omit them and show how many were left out.

If no activity appears, select All report dates and choose All aircraft. If the start date is after the end date, correct the dates. If a download is missing, check the browser’s downloads and try again. The activity CSV is a summary, not a complete logbook backup.

Check instrument activity

1. Enable Settings → Currencies → Show instrument currency and save.
2. Enter your certified instrument check date and, if known, its expiry.
3. Open Summaries → Details → Supporting instrument entries to inspect the evidence.

Instrument approaches count across aircraft types and roles. Instrument approaches is separate from Instrument check & hours; a missing check date does not stop recorded approaches from counting.

If something is missing, find the flight in Logbook and correct its hours or counts. Show more entries reveals the next group.

Add medical and flight-review reminders

1. In Settings → Currencies, enter Medical valid through and/or Flight review valid through.
2. Copy the applicable dates from your records, then select Save settings.
3. Check the reminders in Summaries. Clear a date and save to remove its reminder.

Green means more than seven days remain. Orange means seven days or less, including the entered date. Red means the date has passed. These are in-app reminders, not push or email notifications.

Check the source and scope

Summaries → Details includes CAA rule links and assessment limits. The app's counts include all roles; they do not establish PIC-only eligibility, instrument-system competence, approved simulator credit or operator alternatives.

The assessment date follows New Zealand time and updates when you return to the page. Reload to retrieve flights saved on another device.

Edit flight details

1. Open the saved entry in Logbook.
2. Change the required details. Expand the appropriate hours section if needed.
3. Review the changes and select Save.

Single-engine columns offer Dual and PIC. Co-pilot and command practice are multi-engine categories.

If you close an edited entry, Discard unsaved changes? asks whether to leave it. Choose Keep editing or Discard changes. This does not save edits across a browser reload or tab closure.

Review an earlier saved version

1. Open an entry and select View history.
2. Expand a dated change to compare its saved details.
3. Select Review before this change or Review saved details.
4. Check the proposed values, then select Load for review.
5. Review the entry form and select Save to keep those details.

Loading replaces unsaved edits in the form. Keep current edits cancels the replacement. Saving adds a new change; it does not erase earlier history.

History recovery changes flight details, not exclusion status. Use the separate restoration procedure above to bring an excluded flight back into totals.

Recover a flight-data JSON copy

Use a copy previously saved with Download flight data JSON. This restores current flight data into an empty logbook; it is not a complete account backup.

1. Open Settings → Recover flight-data JSON. Recovery requires an empty logbook, including no Do Not Log records.
2. Select Upload flight-data JSON, or Paste flight-data JSON → Read JSON copy. Check the separate flight, simulator, opening and excluded totals and review individual records.
3. Select Review recovery with server. Check every warning and the confirmation, then select Confirm recover flight data. Existing entries are never replaced.
4. If a result is unconfirmed, select Check recovery result. Retry the same confirmation while keeping the original copy. Stop waiting ends waiting; it does not cancel a recovery that the server may already have saved.
5. After confirmation, open the recovered logbook and verify its records. If saved data cannot reload, use Refresh saved data instead of submitting recovery again.

Version 1 copies only, up to 1,000 records, 10 MB source file and 2 MB recovery data. Recovery creates new record identities and retains recorded exclusions and at most one opening balance. It does not restore old change history, calendar links, import batches, settings, aircraft definitions or calendar connections. Current account settings stay unchanged. One successful recovery is allowed per account; use ordinary entry editing afterward. Keep original files and signed records.

Download recorded entry changes

Select Download account entry history for a JSON copy of recorded changes across the logbook. For one entry, use Download complete entry history in its history panel.

History downloads include old details, including changes to excluded/deleted entries. They ignore flight filters and PDF dates. Store them privately. They are separate from your current-flight CSV and are not a complete account backup or an automatic restore file.

Check a discount code

1. Enter the code on the pricing page.
2. Select Apply and read the result.

The current payment feature provides a quote only. No payment is taken and no account benefit is activated. If too many attempts are reported, wait 15 minutes; people on the same network share the limit.

“Saved”, but the screen did not refresh

Select Refresh saved data. This reads the saved result without repeating the import, opening-total save or undo. If it still fails, wait for the service to recover and retry.

Do not submit the operation again just to refresh the screen. If saving was never confirmed, check Logbook and Import history before retrying.

Import history will not load

Select Refresh import history. This only reloads the list and closes any open undo question. Select the batch again and review its current hours/counts before confirming an undo.

No recorded uploads yet appears only after a successful empty read. A failed read does not mean your history is empty.

“Data changed while loading”

1. Finish edits on other devices or tabs.
2. Reload the app, or use Refresh saved data if offered.
3. For an import or undo, review the new totals and confirm again.

Retrying a read does not change flights. The app stops an incomplete load rather than using it for totals or exports.

“Session changed”

Check which account is signed in, then reload to retrieve that account's data. If a history download stopped, start it again after signing in to the intended account.