Aircraft document organization for shared-ownership groups.

Practical playbook for the small ownership group of two to six. Not legal or regulatory guidance. The audit-trail expectations described here track current EASA practice for non-commercial Part-ML operation; verify against your aircraft’s actual regime before relying on them.

A single owner with a single aircraft can run on willpower and a folder. A group of three can run on willpower for about six months, after which the documents go out of sync, the maintenance log drifts from reality, and the next ARC review surfaces problems nobody had noticed. The fix is not more willpower; it’s a shared system of record with a small amount of role discipline.

The four document categories every owner needs

Strip away the regime-specific paperwork and four categories cover most of what an owner actually has to keep:

1. Airworthiness records — AMP, ARC certificate, AD compliance evidence, maintenance entries, work orders.
2. Aircraft data — TCDS, weight and balance, equipment list, AFM/POH, current placards.
3. Operations records — flight log entries, fuel/oil consumption, defects/squawks.
4. Administrative — registration, insurance certificate, hangar/tie-down agreements, club bylaws.

The shared-ownership question is which of these are append-only (anyone adds, no one deletes), which are versioned (the latest is the source of truth, prior versions retained for audit), and which are static-but-reviewed (the equipment list rarely changes but should be checked at every ARC).

The shared-ownership multiplier problem

With a single owner, the worst case is “I forgot to write something down.” With three co-owners, the failure modes multiply: I logged a flight in my own paper book and didn’t sync; you ordered an oil change and signed the receipt but didn’t enter it; she had a magneto issue last month and noted it in a text message; he doesn’t know that the prop was overhauled in March.

The structural fix is append-only shared state. Every flight logged once, in one place, by whoever flew it. Every maintenance event logged once, with a photo of the receipt. Every defect noted, even if it’s “intermittent uncommanded yaw at climb power, investigating.” Hangar’s data model is built around this; co-owner invite ships today (early access), with full role-scoped reads coming.

The spreadsheet equivalent works for a while. The breaking point is usually around year two, when the second ARC renewal exposes how much state is in the heads of co-owners rather than in the document.

Roles: airworthiness lead, treasurer, members

For groups bigger than two, designate roles. They don’t need to be formal; they do need to be agreed.

Airworthiness lead. Owns the AMP, the ARC schedule, the AD compliance status, the relationship with the maintenance organisation. The person whose phone rings if an inspector calls.

Treasurer. Owns the cost ledger, the insurance renewal, the hangar/tie-down payment, the contributions accounting. The person who sends the year-end statement.

Members. Log their own flights, log their own pilot-owner maintenance, raise defects, contribute to costs. Do not need to know everything the lead and treasurer know; do need read-access to the dashboard and the ability to see component times before they fly.

Hangar’s role-scoped multi-user is on the roadmap, not yet shipped today. The full read/write scoping (treasurer sees expenses without seeing every flight log entry, etc.) is coming. In the interim, the workflow is: invited co-owners can read most aircraft data; sensitive separations (financial vs operational) sit on the airworthiness lead and treasurer informally.

Naming conventions and version control

For a folder full of PDFs, agree on a naming convention before anyone uploads anything. A credible default:

YYYY-MM-DD__category__short-description__author.pdf

Examples:

• 2026-04-15__arc__ec-zzz-arc-2026-2027__casa-aerodynamics.pdf
• 2026-03-20__maintenance__oil-change-tach-1247__pilot-owner-jcs.pdf
• 2026-02-01__insurance__hull-and-liability-policy-renewal__broker.pdf
• 2026-01-10__amp__amp-revision-3__camo.pdf

The leading date sorts chronologically. The category lets the airworthiness lead grep for everything maintenance-related. The author tells you who to ask when there’s a question.

Versioning: never overwrite a prior version. amp-revision-2 and amp-revision-3 both stay. The current version is the highest revision number; the old versions are the audit trail.

Where the originals live

Some documents have meaningful “originals” with wet signatures:

• The ARC certificate with the inspector’s signature and stamp.
• Maintenance release with certifying staff signature.
• Aircraft logbook with cumulative entries.
• Insurance certificate (sometimes; depends on broker).

Hangar can hold scanned copies in the document vault (auto-populated from upload, with the doc-type taxonomy that matters for the regime). The wet-signature originals live in a folder with the airworthiness lead, ideally in fireproof storage. Take a photo of the location when you take the original; that photo lives in Hangar so anyone can find the wet original on demand.

Audit trail expectations under EASA

For Part-ML self-managed operation, the inspector at ARC review expects: the AMP (declared or approved), the maintenance records since the last ARC, the AD compliance status, the component time tracking, and the flight log evidence supporting the maintenance triggers. The expectation is “show me,” not “tell me.”

What an inspector looks for is consistency: the dashboard says component X has 234 hours since overhaul; the work order from the overhaul should be findable; the work order’s date should align with the flight log entries that brought the component to 234. If a flight is in the log but not on the airframe hours, or vice versa, that’s a finding.

For a deeper recordkeeping reference, including how this differs from FAR Part 91, see EASA vs FAA maintenance recordkeeping.

Onboarding a new co-owner

A practical onboarding sequence when adding a fourth member to a three-member group:

1. Read-access first. Give them dashboard access for two weeks before any operational role. They learn the aircraft’s status, the open items, the upcoming ARC date, the cost trajectory.
2. Pilot documents. Verify licence, medical, currency. For shared insurance, verify they’re added to the policy.
3. Aircraft check-out flights. Two with the airworthiness lead, two more solo with debrief. Standard club practice; works for a co-ownership group too.
4. Co-ownership agreement update. Whatever document governs the group (LLC operating agreement, partnership deed, club membership) gets updated. Hangar holds a scanned copy in the admin folder.
5. Activate write access. They can now log flights, raise defects, and (if a pilot-owner) log pilot-owner maintenance. They cannot accept ARC issuance or close out maintenance — that stays with the lead.

Off-boarding a departing co-owner

The mirror sequence:

1. Lock write access on the agreed exit date. Read access can stay for a transition period.
2. Reconcile the cost ledger. Departing co-owner pays or receives their share according to the agreement.
3. Insurance update. Remove from the named-pilot list; verify with the broker.
4. Logbook continuity. Their logged flights stay in the aircraft logbook (it’s the aircraft’s history, not theirs); their personal logbook holds their flights for them.
5. Document export. GDPR allows them to request a copy of their personal data; Hangar’s GDPR self-service export covers this. Aircraft data stays with the aircraft.

For more on the surrounding ownership question, see Airworth for flying clubs and shared-ownership groups and the Hangar product page for the aircraft side. The ARC renewal checklist is the next read for what an inspector will actually ask for.