Skip to main content

Veryon Tracking+ Engine Starts Custom Fields

  • Updated

 

Engine Starts Custom Fields

Engine start counts are not a built-in Tech Log utilisation value. They are captured using custom fields, which the integration maps to the Engine Starts life codes in Veryon Tracking+.

Custom fields must be created with exact key names. If a key does not match, the value will not synchronise.

 

Required custom fields

Create the following four custom fields on each applicable aircraft:

 

Field key

Tech Log location

Purpose

LH_ES

Postflight

Engine 1 starts recorded on a flight 

RH_ES

Postflight

Engine 2 starts recorded on a flight 

LH_ES_TU

Trip Update

Engine 1 starts recorded on a trip update

RH_ES_TU

Trip Update

Engine 2 starts recorded on a trip update

 

Naming rules

  • Keys are uppercase with underscores, exactly as written above. They are case-sensitive.

  • LH = Engine 1, RH = Engine 2.

  • The _TU suffix denotes the Trip Update variant. Both sets are required — Postflight fields do not apply to trip updates and vice versa.

  • Single-engine aircraft use Engine 1 (LH_ES / LH_ES_TU) only.

How to add them in Tech Log

  1. In the left-hand navigation bar, click Settings.

  2. Open Aircraft and select the registration you are configuring. Custom fields are configured per aircraft, so this must be repeated for every registration in scope.

  3. Open Custom Fields.

  4. Click Add Custom Field and configure:

    • Key — one of the four keys above, entered exactly.

    • Type — numeric (whole number).

    • View / Location — Postflight for LH_ES and RH_ES; Trip Update for LH_ES_TU and RH_ES_TU.

  5. Set the display label to something crew-friendly, e.g. "Engine Starts (LH)". The label is free text — only the key is used for mapping.

  6. Save, then repeat for the remaining fields.

  7. Confirm the fields appear on both the Postflight page and the Trip Update drawer for that aircraft.

Veryon Tracking+ prerequisites

The integration only sends a value when a matching life code exists on the registration in Veryon Tracking+. Life codes are matched on the triple (Life Code, Location, Position):

 

Tech Log field

Veryon Tracking+ life code

LH_ES / LH_ES_TU

(Engine Starts, 72-00, LH)

RH_ES / RH_ES_TU

(Engine Starts, 72-00, RH)

 

Before go-live, confirm with your Veryon Tracking+ administrator that both life codes exist on every in-scope registration. If a life code is missing, engine starts for that position will be silently skipped.

 

Behaviour and limitations

  • Blank means blank. If a custom field is left empty in Tech Log, nothing is sent for that position. The integration does not auto-populate or copy across from engine cycles.

  • Positions are independent. A missing RH_ES does not prevent LH_ES from syncing.

  • Engine starts vs engine cycles. These are separate values. Engine cycles come from the built-in per-engine utilisation fields; engine starts come only from these custom fields.

Related articles