Part 61 · Airman records
Auto-connecting flight time
When a flight or lesson is marked complete, the time posts to the right logbook bucket automatically based on the seat flown, so instruction given and received land where they belong without re-typing. Auto-posted rows dedupe against manual and imported entries. It replaces the end-of-day reconciliation between the schedule and the logbook.
Launching the first quarter of 2027.
Illustrative — every screen reflects your own data.
Who it's for
The CFI who doesn't want to re-type flight time at the end of a duty day and needs completed sessions to land in the right logbook bucket on their own.
What it replaces
The end-of-day reconciliation between the schedule and the logbook.
What auto-connecting flight time gives you
- Completed sessions post to the logbook by seat flown
- No re-typing at the end of a duty day
- Auto-posted rows dedupe against manual and imported entries
Completed sessions post by seat flown
When a CFI marks a flight or lesson complete, the time posts to the right 61.51 bucket automatically based on the seat flown — instruction given and received land where they belong without anyone re-typing at the end of a duty day. You mark a flight or lesson complete on the schedule and the time posts to the right logbook bucket on its own.
- Completed sessions post to the logbook by seat flown
- No re-typing at the end of a duty day
Auto-posted rows dedupe, so nothing double-counts
Because auto-posted rows dedupe against manual and imported entries, the same flight never shows up twice. The end-of-day reconciliation between the schedule and the logbook goes away — the schedule and the logbook are no longer two records to square up.
- Auto-posted rows dedupe against manual and imported entries
- No re-typing at the end of a duty day
How an operator uses this
When a CFI marks a flight or lesson complete, the time posts to the right 61.51 bucket automatically based on the seat flown — instruction given and received land where they belong without anyone re-typing at the end of a duty day. Because auto-posted rows dedupe against manual and imported entries, the same flight never shows up twice. It replaces the end-of-day reconciliation between the schedule and the logbook.
Illustrative — every screen reflects what's in your own data, nothing more.
How it works
Auto-connecting flight time, step by step
Mark a flight or lesson complete on the schedule.
The time posts to the right logbook bucket automatically, based on the seat flown.
Auto-posted rows dedupe against your manual and imported entries, so nothing double-counts.
Skip the end-of-day reconciliation between the schedule and the logbook.
Questions
Auto-connecting flight time — frequently asked
Do I have to re-enter flight time in the logbook?
No. When a flight or lesson is marked complete, the time posts to the right logbook bucket automatically based on the seat flown, so you don't double-enter at the end of the day.
Will an auto-posted flight collide with one I logged by hand?
No. Auto-posted rows dedupe against manual and imported entries, so the same flight never shows up twice.
Keep exploring
Other features in Part 61
61.51 digital logbook
Integer-tenths times, total / PIC / SIC / XC / night / instrument, with ForeFlight CSV in/out.
Deep diveEndorsement issuance
Per-trainee endorsement history with expiry and stored documents.
Deep diveCredentials vault
Certificates, ratings, and medicals with auto-expiry alerts.
Deep diveRecurrency dashboard
Flight reviews and currency on a Due-Soon timeline.
Deep diveLesson & checkride scheduling
One calendar for instruction and checkride bookings.
Deep diveIACRA 8710-1 pre-fill
Builds from training records; CSV export for the FAA system.
Deep diveEvery Part 61 workspace also includes the platform-wide backbone — logbook, credentials, compliance, reporting, and audit trail.
See the backboneSee auto-connecting flight time on your operation.
It's part of the Part 61 workspace. Request a demo or join the waitlist.