Types available in the Aerodromes library. The seven built-in types (airport, airfield, helipad, field, mountain, elisuperficie, campo volo) carry their own map symbol and logic: their label can be edited but they cannot be deleted. Types you add use the generic symbol (airfield circle) and follow the “Airfields” overlay toggle on the planner. A type in use cannot be deleted.

Managed catalog of the aerodrome data sources: it constrains the Source select in the aerodrome editor and feeds the library filter. Imports register their own sources automatically; a source in use cannot be deleted.

Fuel options offered as checkboxes on each aerodrome (with per-option note). A fuel type in use cannot be deleted.

Fire fighting category options for aerodromes. A category in use cannot be deleted.

Route kinds (direct, mid way, bad weather, alternate) and nav point kinds carry their own symbology and logic, so they are defined in the application — ask a developer change to extend them.

Each helicopter defines its performance and pricing. Request IDs use the format YYMMDD-SERIAL, where SERIAL is the progressive request number within the year.

Types and variants operated by the company, from the EASA “Type Rating and endorsement list — Helicopter”. Variants in the same cell only require familiarisation training between each other; separate rows within a type require difference training.

Aircraft accepted or being processed for training under the Karen SA ATO approval (OM-ATO Preliminary information). Each row is an Aircraft Relationship: classification (complexity · supplying party · AOC-listed) determines the Regulatory Route and the ATO Operational Configuration. The ATO Aircraft List derives from the relationships with status Current.

Value lists used by the ATO module documents.