Simulator time is logbook time too. Jetlog logs it as a first-class entry, not a bolt-on note. Recurrents, an LPC/OPC, an LOE, a type-rating course: all of it sits in the same list, sorted by date alongside your line flying.
Creating an FSTD entry
Tap ＋ as usual and set the entry type to Simulator (FSTD). From there the form adjusts to fit:
- Device: the simulator/FSTD identifier instead of an aircraft registration, so your sim hours don’t get mixed into your aircraft fleet list.
- Exercise type: recurrent, LPC, OPC, LOE, type rating, or a plain training session, so your records show what kind of session it was.
- Crew and instructor/examiner: the same people picker you use for real flights; add your examiner once and reuse them.
- Times and duration: session start/end rather than off-blocks/on-blocks, since a simulator session doesn’t have a taxi phase.
Why it’s worth logging properly
Recording a session as its own entry type, rather than jammed into a real-flight entry, means your reports, currency views, and totals tell the two apart correctly: sim hours land in your overall totals where your regulator expects them, without inflating your real-flight sector count or route map. It also means AI logbook scanning can pick up a session when you photograph old paper pages, recognizing it as a simulator record rather than a flight with a fictitious route.
Remote sign-off works here too
An LPC/OPC or LOE almost always needs an examiner’s signature. Send the same one-time remote sign-off link you’d use for a flight; no app or account required on the examiner’s side.
Next
See Logging your first flight next, or read How automatic flight tracking works if your airline is live-tracked.
