Skip to content

Aircraft and directory

Two libraries sit behind your logbook: the aircraft you fly, and the people, companies and airports your flights point at. Nothing in this area logs a flight, but your totals are counted through all of it. So a mistake made here doesn’t look like a mistake — it looks like a wrong number somewhere else.

Read E1 and E3 before you edit anything. The rest will be there when you need them.

GuideWhat it gets you
E1The HangarThe Aircraft screen, which is two lists and not one
E2Add an aircraftOne tail in the Hangar, correct first time
E3Aircraft types, and what editing one changesThe type/airframe relationship, and exactly which tails a type edit can correct. Read it before you fix a typo
E4Simulators and training devicesSessions that stay out of flight time and land on the right 8710 row
E5HUD configurationHead-up display hours, as a number you can see
E6The DirectoryPeople, Orgs and Airports, and where your own record lives
E7People and employment historyCrew records, and dates that quietly decide who your flights are attributed to
E8OrganizationsThe companies the logbook attributes hours to
E9AirportsA catalogue of 84,442 airports, narrowed to the ones you use
E10Find duplicates in the Hangar and DirectoryTwo records that are the same thing, collapsed into one, with the flights kept
E11Read one aircraft’s analyticsThe five views behind a Hangar card — where one tail has been, and what it’s worth to your career

Two things worth knowing first

The navigation label and the screen name differ. You tap Aircraft in the navigation, and the screen that opens is headed Aircraft Hangar, or Hangar on a window narrower than 800 pixels. Directory opens a screen headed Directory. This area uses the on-screen names throughout.

Nothing in this area is Pro-only. Every aircraft, person, organization and airport feature described here works on a free logbook.

Words this area introduces

Hangar — the list of individual aircraft you fly. One card per tail.

Airframe, or tail — one physical aircraft, identified by its registration or its fleet number. This is what you pick when you log a flight.

Type — the model an airframe is: a catalogue entry shared by every tail of that model, with its own tab, list and editor. Editing a type can correct the tails still following it, one field at a time (E3).

Designator — the ICAO code for a type: C172, B738. It isn’t unique.

Doc 8643 — the ICAO type catalogue that comes with the app: 10,020 entries covering 2,640 designators. Most types you need already exist.

Snapshot — a value copied onto a flight when it was saved, rather than looked up fresh every time. Every flight carries three: aircraft type, operator and owner. They don’t all behave the same way (E3).

Simulator device class — FFS, FTD or ATD, set on a type, or on a single session in the flight-entry form. A device class is the only thing that keeps a session out of your flight-time totals (E4).

HUD configuration — how a head-up display is fitted across the two crew seats of one airframe: None, Captain, or Captain + F/O.

Organization — any company in the logbook: airline, operator, flight school, manufacturer, owner. One list doing four different jobs.

Employment history — the dated jobs recorded on a person. On your own record, they decide which of your flights get attributed to an operator (E7).

Seeded — reference data that came with the app rather than created by you. Seeded airports can’t be deleted and can’t be merged away.

Set aside — in Find Duplicates, “file a copy in the Review queue and decide later”. It removes the record from where it was, and it isn’t an undo.

Self person — your own Directory record, badged YOU and pinned above the People list. It can’t be deleted (→ A9).