Aircraft asset type

What it is

Aircraft is the asset type Syndik8 was built for first. It carries the assumptions of general aviation syndicate operation: usage is tracked by engine hours from the Hobbs meter, landings are counted for maintenance cycles, and airworthiness is computed from open squawks.

At launch, every new asset you add in a syndicate is created as an aircraft.

Who can use it

Owner and admin — add, edit, archive aircraft.
Member — see the asset, book it, log usage against it.

Where to find it

Syndicate → Assets → Add asset — creates an aircraft.
Route: /syndicates/:syndicateId/assets/new.
Existing aircraft appear under Syndicate → Assets and have a flight icon.

Fields / options

Built-in defaults

The aircraft type ships with this default config:

Config key	Default	What it controls
`usage_metric`	`hobbs_hours`	Usage is recorded in hours from the Hobbs (or equivalent) meter.
`track_landings`	`true`	Usage logs accept a landing count and a touch-and-go count per flight.
`requires_pilot_currency`	`true`	Pilot-currency awareness is surfaced in the UI (reporting; does not block bookings today).

Fields on an aircraft asset

When you add an aircraft, the create-asset form takes:

Field	Required?	Notes
Name	yes	Free text, up to 100 characters (for example “G-DEMO Cessna 172”).
Registration number	no	Aircraft registration — `G-DEMO`, `N12345`, etc. Up to 50 characters. Used for the import wizard’s asset matching.
Description	no	Free text, up to 500 characters.
Current meter reading	yes	Starting Hobbs value. `0` is accepted. Feeds previous-tacho pre-fill on the first logged flight.
Home airfield	no	Free-text ICAO code (uppercased automatically). Metadata only at launch.

Icon: the Material flight icon.

Behaviour rules

The add-asset flow creates aircraft only at launch. The create-asset screen submits every new asset as an aircraft regardless of what the underlying database supports. The other built-in types — boat, property, vehicle, generic — exist in the database and on the backend but are not exposed as options in the add-asset form today.
Registrations are matched case-insensitively and punctuation-agnostically. G-BBBN and GBBBN match the same aircraft when importing bookings from a CSV.
Usage is recorded in hours with up to two decimals. The usage log expects XXXX.X or XXXX.XX — the same shape a Hobbs drum shows.
Landings and touch-and-gos are per-log counts. They roll up to the asset’s current_landing_cycles figure for maintenance intervals measured in cycles.
Grounding squawks block confirmed bookings. An open grounding squawk marks the aircraft non-airworthy and moves affected confirmed bookings to suspended — see airworthiness rules.
Metadata accepts free-form extras. The app uses the metadata JSON object on the asset row to hold things like home airfield and initial usage; it is not a fixed schema.