Keeping flight and simulator records clear in Army Flight Logbook

Identify the record type at the beginning

Before entering activity, determine whether the source describes an aircraft flight or a simulator session. Preserve that distinction throughout your review. Similar-looking dates and time fields do not make two record types interchangeable.

The official Army Flight Logbook release notes discuss flight and simulator records separately, including changes to simulator entry and reporting.

Compare the entry with its own source

Check the session date, recorded duration, and device or aircraft-related fields against the supporting material. If a source field does not map clearly to an available field, ask for clarification. A guessed mapping can create a plausible-looking entry that is difficult to interpret later.

Read the report’s scope

Before using a total, confirm which record types it includes and whether they are displayed separately. Do not manually combine categories unless that is appropriate for the question being answered. For requirement credit or official reporting, use the applicable guidance from your unit rather than an assumption based on the app’s presentation.

Use a simple exception list

Keep unresolved questions in a review list: source reference, record type, field in question, and who can clarify it. Resolve those questions before treating the affected summary as final. That approach preserves useful history while keeping uncertainty visible instead of hiding it inside a total.