GlideHQ: Gliding club software, in development.Built around a day at the airfield.

The intended operating flow follows a flight from the queue through launch, airborne and landed states to confirmation. A live board and flight history would use that shared record. The aim is to avoid making each volunteer reconstruct the same day's movements independently.

Member information, qualification records and training progress are part of the planned club workspace. Instructors would record lessons and sign-offs against training programmes. Those records are intended to inform authorised people, who remain responsible for deciding what a pilot may do.

The scope includes gliders, tugs, touring motor gliders and supporting equipment. Usage, inspections, documents and defects would sit alongside their operational records. Returning an aircraft or item to service requires the club's authorised process; software status alone cannot establish airworthiness.

Planned tariffs and flight charges link back to confirmed flying records, giving the treasurer a basis for member accounts. Training and aircraft usage can draw on the same event. Club charges remain distinct from any subscription the club might pay for the software.