For flying clubs and shared-ownership groups.

You are between three and six pilots who own an aircraft together, or a small flying club whose members fly the aircraft they manage. Airworth is built for that shape. Not for fleets where the operator doesn’t fly. Not for flight schools.

Multi-seat pricing built for ≤6 members

Pricing during early access is free. When pricing lands, the multi-seat structure will be built around groups of up to six members — that is the unit of analysis we design around. Roles, recordkeeping, document hygiene, expense splitting — all sized for the small group, not the enterprise fleet.

We will tell you the price before any charge. No payment information is collected today.

One aircraft, many pilots, one reference

The shared-ownership multiplier problem is real. Three co-owners means three logbooks getting out of sync, three spreadsheets of expenses, three different opinions on which AD applies. Airworth Hangar gives the aircraft a single canonical record — the reference everyone defers to.

Component times update from whichever co-owner logged the last flight. Maintenance compliance recorded by one is visible to all. The 727-document service-document catalog applies to the aircraft once, not per-co-owner.

Roles: airworthiness lead, treasurer, members (when shipped)

Today: invite a co-owner to a single aircraft works (early access). Roles with separate read/write scopes — airworthiness lead, treasurer, members — are coming soon, not yet shipped. We say so plainly because pilots cross-check. Several read-paths for shared data (oil samples, expenses, documents, today-feed, endorsements, GDPR export) are still being closed for invited co-owners.

The schema for clubs (clubs, club_aircraft, club_memberships, club_checkouts, bookings) is in place; the application layer for booking and billing is on the roadmap and not yet usable. We do not market club booking as available today.

If you want the document-discipline foundation now, see the aircraft document organization guide for shared ownership.

Hangar for the aircraft, Flights for the trips

Two separate products, sharing one identity:

• Airworth Hangar — the aircraft side. Airworthiness, components, ARC, ADs, expenses, document vault.
• Airworth Flights — the trip side. Multi-leg planning with co-pilots and passengers, NOTAM filtering, weather briefings, Trip companions.

You can use one without the other. Most clubs will want both, with the airworthiness lead living in Hangar and the social trip planning living in Flights.

EU clubs that are also DTOs/ATOs — read this

If your club operates as a Declared Training Organisation (DTO) or Approved Training Organisation (ATO) in addition to private flying, the boundary is functional, not entity-type. We build for groups managing aircraft they fly themselves. We do not build for training operations where the operator is not a pilot of the fleet.

In practice this means: if your DTO/ATO uses Airworth for the same aircraft your members fly privately, we are happy to have you on the waitlist. We will tag you for product-fit triage and will not pretend Hangar’s roadmap covers training-currency tracking, because it doesn’t.

Join the waitlist

Or email us about clubs directly if you want to talk through fit before signing up.

FAQ

How many members does this work for? Designed for ≤6. The schema and the role model are dimensioned for small groups; we are not building enterprise multi-tenant SaaS.

Can the treasurer see expenses without seeing flight logs? That separation is part of the role-based access roadmap, not yet shipped. Today, an invited co-owner sees most of the aircraft data; full role-scoping is coming soon.

What about club booking? The clubs/bookings schema is in the database. The application layer (booking API, booking UI, billing view) is on the roadmap. Not usable today; we will not pretend otherwise.

Where is shared-ownership data stored? EU edge by default, in line with the transparency page and privacy policy.