Overview

The Flight Audit feature is a comprehensive validation tool that checks all your flight entries for potential logging errors and inconsistencies in 16 different areas. It helps ensure your logbook meets professional and regulatory standards by identifying discrepancies that might otherwise go unnoticed.

Important: The audit process is non-destructive - it only reviews and highlights potential issues without making any changes to your flight data.

Getting Started

Running an Audit

1. Navigate to the Flight Audit section in Logger

2. Click "Run Audit" to begin the process

3. Review the results and make changes if required (you can do so directly in audit view)

Audit Settings

Use the gear icon (⚙️) to access audit settings where you can customise which checks are performed. There are 16 different audit scopes, you can switch off those which do not apply to your logging requirements.

Understanding Audit Results

The audit checks for various types of logging inconsistencies and presents them as warnings. There can be multiple warnings presented for one flight.

• Audit Overview: Shows total amount of warnings and flights with warnings

• Detected Warnings: Show present warning types. Tapping on the warning will filter the warnings by type

  
  

When you open the warning bar, you will be presented with more information:

• Icon: Visual indicator for quick identification

• Explanation: Short information about the warning

  
  

Reviewing Results

1. You may see many warnings when you run the flight audit for the first time. In some cases, one issue can cause multiple warnings. In the above example, missing crew causes 2 warnings (SELF is not assigned to flight and Missing Crew).

2. Fixing one issue will often silence many other warnings (e.g. marking aircraft type as multi-pilot will silence all warnings associated with multi-crew logging across all your flights for that aircraft type)

3. After making necessary changes, re-run the audit to verify fixes

4. If an audit warning doesn't apply to your needs, switch it off in the audit settings

Audit Warning Types

Time-Related Warnings

Flight Time Longer Than Block Time

• What it checks: Ensures flight time doesn't exceed block time

• Applies to: All entry types

• Why it matters: Flight time should not exceed block time

Function Time Longer Than Block Time

• What it checks: Validates that PIC, SIC, DUAL, Instructor, NIGHT, IMC, and other function times don't exceed block time

• Applies to: Flight entries only

• Why it matters: Individual function times cannot be greater than the total time duration

Function Time Doesn't Match Block Time

• What it checks: Ensures function times (PIC, SIC, DUAL, etc.) either match block time or are empty

• Applies to: Flight entries only

• Why it matters: In most cases, function times should equal block time when logged

Missing Block Times

• What it checks: Verifies that Out, In, or Total Block time fields are completed

• Applies to: Flight entries only

• Why it matters: Missing times may signal logging omission

Missing Function Time

• What it checks: Identifies entries with block time but no corresponding function time

• Applies to: Flight, simulator, and duty entries

• Why it matters: Normally at least one function time is logged per flight

Aircraft Warnings

Engine Type Mismatch

• What it checks: Verifies SE/ME time matches the aircraft's engine configuration

• Applies to: Flight entries only

• Why it matters: Single-engine time should only be logged for SE aircraft, multi-engine time for ME aircraft

Multi-Crew Mismatch

• What it checks: Ensures multi-crew time aligns with aircraft type designation

• Applies to: Flight entries only

• Why it matters: Multi-crew time should only be logged on aircraft that are multi-pilot

SIC Time on Non-Multi-Crew Aircraft

• What it checks: Flags SIC time logged on single-pilot aircraft

• Applies to: Flight entries only

• Why it matters: SIC time is only valid on multi-pilot aircraft

Missing Aircraft

• What it checks: Verifies aircraft or aircraft type is assigned to the entry

• Applies to: Flight, simulator, and other duty entries

• Why it matters: Aircraft information is required for proper categorisation and totalling

Crew Warnings

Missing Crew Information

• What it checks: Ensures a PIC is always assigned (and SIC when multi-crew time is logged)

• Applies to: Flight entries only

• Why it matters: PIC should be assigned on all flights. SIC should also be logged when in multi-crew environment

SELF is not assigned to flight

• What it checks: Verifies you are assigned to at least one pilot position

• Applies to: Flight, simulator, and other duty entries

• Why it matters: You should be assigned to the flight to determine your position

Pilot Function Mismatch

• What it checks: Ensures PIC/SIC time is only logged when you're in the corresponding position

• Applies to: All entry types

• Why it matters: You can only log time for positions you actually occupied

Operational Warnings

PF Without Landings / PM With Landings

• What it checks: Validates landing records match Pilot Flying designation

• Applies to: Flight and other duty entries

• Why it matters: The pilot flying should log landings; the pilot monitoring should not

PICUS Time When Not PF

• What it checks: Ensures PICUS (Pilot-in-Command Under Supervision) time is only logged when designated as PF

• Applies to: All entry types

• Why it matters: PICUS time requires acting as the pilot flying under supervision (applies only to some regulations)

Data Integrity Warnings

Entry Type Mismatch

• What it checks: Identifies fields that don't correspond to the selected entry type

• Applies to: All entry types

• Details: Lists specific fields causing the warning

• Why it matters: Only relevant fields should be populated for each entry type (e.g. no sim time when entry type is marked as flight)

Missing Airport Information

• What it checks: Verifies departure and arrival airports are specified

• Applies to: Flight and deadhead entries

• Why it matters: Departure and arrival airports are required to be filled out by most regulators

Important Notes

• Regulatory Compliance: Flight logging practices vary by country and operation type. Always ensure compliance with your local aviation authority requirements.

• Personal Standards: Some warnings might be acceptable based on your specific logging practices or operational requirements.

• Regular Auditing: Run audits regularly, especially before official logbook reviews or checkrides.

• Backup Your Data: Always maintain backups of your logbook before making bulk corrections.