Built for the people who share the airplane—and the responsibility. See how it works

For small flying clubs

Structure for a growing roster—without enterprise overhead.

Coordinate multiple aircraft, member access, instructors, maintenance, documents, and reporting from one system.

What breaks down

Shared responsibility creates predictable friction.

01

Access differs by member and aircraft

A single role cannot express checkouts, operating access, maintenance responsibility, and instructor status.

02

More aircraft means more exceptions

Booking limits, qualifications, maintenance blocks, and document access need aircraft-level context.

03

Turnover can damage history

Removing a member should stop access without breaking old reservations, expenses, or activity records.

What changes

A partnership that can answer its own operational questions.

One connected system

Every workflow builds on the same aircraft and roster.

01Shared scheduling

Give every partner one clear calendar, then carry the reservation into the post-flight record.

02Aircraft health

See AVIATES context, maintenance requirements, components, squawks, events, and supporting records around the aircraft they affect.

03Records and logbooks

Find files uploaded anywhere in one library, and connect reviewed digital logbook evidence to the maintenance it supports.

04Partnership accounting

Choose who shares each cost, see every balance, follow suggested payments, and preserve the settle-up history.

05Members and access

Coordinate partnership roles, aircraft permissions, qualifications, and safe offboarding.

06Awareness and reporting

Use focused notifications and operational reporting to keep the partnership aligned.

For small flying clubs

Give the group a home base built around the airplane.

Start small: create the partnership, add one aircraft, and invite the first members.