Skip to content

Simulators and training devices

What this does

Sets up a simulator so its sessions stay out of your flight-time totals and the hours on its type, and land on the right row of an FAA 8710-1.

Before you start

  • A profile is open.
  • Choose your route. There are two ways to mark a session, and this guide is the thorough one. Giving the device a tail of its own in your Hangar, marked as a simulator, is what you want for a box you use regularly. For a single session, the flight-entry form’s Simulator / FTD session block does it in one field, and C1 covers that.
  • The aircraft type the device represents needs to be in your catalogue: a Boeing 737 simulator is a B737. Most types already are; if yours isn’t, add it first (→ E3). You don’t need a separate type for the simulator.

Steps

  1. Tap Aircraft in the navigation, then Add and Add Aircraft (→ E2).
  2. On the Identity tab, put the device’s own identifier in Registration or Fleet / Ship No. The simulator’s name is a perfectly good entry.
  3. In Aircraft Type, pick the real type the device represents, such as B737.
  4. Set Simulator Device to the class the device is qualified as: FFS, FTD, ATD, FNPT or BITD. Its helper text reads: Sessions in this device are kept out of your flight-time totals and out of the hours on its type. The type above is still the aircraft the device represents.
    Add Aircraft → Identity, type B737 picked, Simulator Device open, FFS / FTD / ATD / FNPT / BITD visible
  5. Set Qualification Level (optional), which appears beneath it once a class is set, to the level on the device’s own qualification certificate: Level A, B, C or D. A couple of currency rules read it (→ G5); leaving it at Not recorded is fine (see below).
    Add Aircraft → Identity, Simulator Device set to FFS, Qualification Level (optional) open showing Level A / B / C / D
    5 the Qualification Level dropdown — read by currency rules
  6. Tap Save. The tail’s card in the Hangar carries a chip reading SIM · FFS (or whichever class you set). It names the class only, never the level.
    A simulator tail's card in the Hangar carrying the SIM · FFS chip
  7. Log each session against that tail like any other flight (→ C1).

How to tell it worked

The tail’s card shows the SIM · chip, the session is in your logbook with its hours on the card, and your total time hasn’t moved. The type’s hours haven’t moved either: a B737 simulator adds nothing to your B737 hours in Aircraft Types or My Flown Types.

The hours don’t disappear. The flight card shows them and the FAA 8710-1 reads them. It’s only your flight-time totals that leave them out. On an FAA 8710-1 preview the session appears under FFS · Full Flight Simulator, FTD · Flight Training Device or ATD · Aviation Training Device, depending on the class you set (→ F5).

Marking a tail covers every session on it, including ones you logged before you marked it.

The qualification level shows nowhere on screen. Reopening the aircraft and finding it still set is the only confirmation here; its effect shows up on your currency card instead (→ G5).

If something goes wrong

What you seeWhyWhat to do
No SIM · chip on the tail’s cardThe device class didn’t save, or was set back to No — a real aircraftOpen the aircraft, and set Simulator Device on the Identity tab
BATD or AATD isn’t offeredNeither is a separate class anywhere in the app — both come under ATDUse ATD
Qualification Level (optional) isn’t thereSimulator Device isn’t set yetSet the device class first
The level has gone after you cleared the device classClearing the class clears the level with it — a level means nothing on a tail that isn’t a deviceSet the device class again, then the level
Add Aircraft Type has no Simulator Device fieldA simulator is marked on its tail now, not its type. A type is the real aircraftAdd the device as an aircraft, as above
You already set up a simulator as a type of its own, such as “B737 FFS”That still works, and the type keeps its Simulator Device fieldNothing. To move it to the new way, edit the tail: set its type to the real one and set Simulator Device there
The hours still show on the flight cardNormal. Sessions keep their time; only the totals leave them outNothing
A session is still in your total timeThat flight isn’t on the simulator tailOpen the flight and pick the simulator tail, or set a Device class on the flight itself
You set the tail back to a real aircraft on one device, and another device still shows it as a simulatorThat device hasn’t synced sinceSync it; setting the tail back reaches every device
A tail you marked as a simulator is back to a real aircraftAnother device edited the tail before it had received your mark, and its edit counts as setting it backSet Simulator Device again, then sync every device
Landings in the box didn’t make you landing-currentCurrency also goes by the device class, and a device session doesn’t countNothing. Fly the aircraft
You’re looking for somewhere to type simulator hours on the flight formIt’s there — the Simulator / FTD session block in the Training sectionUse it for a one-off, and set a class in the block’s Device class picker. For a device you fly often, use this guide’s tail route (→ C1)

Where these hours land

ClassOn the FAA 8710-1
FFSFFS · Full Flight Simulator
FTDFTD · Flight Training Device
ATDATD · Aviation Training Device
FNPTFTD, the nearest FAA equivalent
BITDFTD, the nearest FAA equivalent

FNPT and BITD are European (EASA) classes, and Form 8710-1 has no row for either. They print on the FTD row so that a device session never lands in Airplanes.

The long forms — Full Flight Simulator (FFS), Flight Training Device (FTD), Aviation Training Device (ATD) — also appear in the Previous Experience wizard, when you record simulator time flown before this logbook (→ B7).

What the qualification level is for

Nothing on the Hangar card or the flight card shows it, but a couple of currency rules read it. Canada counts a device toward instrument-approach currency only at Level B, C or D, and its sector-substitution rule asks more of a Level A device than of a Level B, C or D one. G5 has both rules; G2 has how a rule like that reaches your currency card (→ G5, G2).

Leave it unset and a session in the device is still credited, exactly as if the control weren’t there. Setting it only lets those two rules tell a compliant session from one they can’t check. It changes nothing about flights you’ve already logged.

The one field that sounds like this and isn’t

The flight-entry form’s Training section has Instrument (Simulated), and the name misleads. Instrument (Simulated) is hood or view-limiting-device time in a real aircraft. It’s flight time, it belongs in your totals, and it has nothing to do with simulators. Logging it doesn’t exclude anything, and shouldn’t.

The Simulator / FTD hours box in the same section sits with a Device class picker, and the class is the switch. Enter hours without choosing a class and the form warns you in red rather than accepting them quietly.

So: what keeps a session out of your totals is a device class — on its tail in the Hangar, on its type, or on the flight itself. Hours alone never do.