Clear answers for shared-aircraft operations.

AirplaneHQ is a shared operations system for aircraft partnerships, owner groups, and small flying clubs. It connects scheduling, aircraft health, squawks, expenses, documents, digital logbooks, member access, notifications, and reporting.

It is designed for groups that jointly operate one or more aircraft and need more structure than a shared calendar and spreadsheets. It supports owners, administrators, maintenance managers, instructors, and members.

No. AirplaneHQ organizes information, calculations, evidence, and reminders. Owners, operators, pilots, and authorized maintenance professionals remain responsible for airworthiness, required inspections, recordkeeping, and regulatory compliance.

No. Preserve all records required by applicable law, regulation, operating rules, insurers, lenders, and partnership agreements. Digital copies and in-app logbooks are organizational tools unless your own qualified review establishes otherwise.

Yes. Authenticated workflows are available in the native iOS app as well as the web application. Public registration remains on the web.

Create an account, then accept an invitation sent to the same email address or request access using the exact partnership name or ID. An owner must approve a join request.

The core roles are Owner/Admin, Maintenance Manager, and Partner/Member. Aircraft-specific access and maintenance permissions add more precise control than the role alone.

Yes. Owners can separately control a member’s visibility, scheduling/operating access, and maintenance-management authority for each aircraft.

An owner can move the person to former members. Active access is disabled while historical reservations, expenses, flight logs, maintenance activity, and audit context remain available.

Yes. A user can switch between active partnerships. Data and permissions remain scoped to the selected partnership.

No. Ownership must be transferred or another active owner must be added first so the partnership is not left without an administrator.

AirplaneHQ checks overlapping reservations and configured rules when a reservation is created or changed. Access, aircraft availability, booking limits, buffers, qualifications, instructor rules, and maintenance blocks can all affect the result.

Yes. Supported recurring patterns create a linked series. Review the complete series before saving and edit or cancel with care.

Owners choose a partnership visibility policy. Depending on that policy and the viewer’s role, another member may see full details, the member only, or simply that the aircraft is busy.

Yes. Owners can identify instructors, define availability, configure instructional scheduling, and require an instructor where applicable.

Each member receives a private signed calendar-feed URL. It can be opened in Apple Calendar and must be protected like a password because anyone with the URL may be able to read the feed.

An eligible reservation can be used to create a flight log. The member records the flight date, destination, meter values, fuel and oil use where applicable, and an optional squawk.

Requirements can use calendar dates, aircraft meter hours, or both. Standard AVIATES items, VOR checks, component relationships, typical work, notification windows, and completion history add context.

Status calculations use the aircraft times recorded in AirplaneHQ. Alerts are only as current as those entries and should never replace physical records, required inspections, or professional judgment.

An owner or a member with the applicable maintenance authority can record completion. Permissions are checked in the context of the partnership and aircraft.

A squawk is a reported aircraft discrepancy or concern. It can be categorized by severity and status, assigned, discussed through notes, connected to a maintenance event, and closed with resolution details.

Yes. Installed components can carry serial and part information, installation details, condition, service limits, manual references, and links to maintenance requirements.

Projects organize improvements or non-routine work with priorities, status, member voting, comments, files, and aircraft context. They do not replace maintenance release or approval records.

The production configuration determines storage. AirplaneHQ supports private S3 object storage and local persistent storage. Each document records its backend and opaque storage key.

Yes. Documents can follow partnership, aircraft, maintenance, or more limited visibility rules where supported. Owners should review sensitive uploads and member access.

The original upload is preserved. Derived pages enter a review tray where an authorized user can preview, rotate, reorder, remove, and place them before committing them to the in-app logbook.

No. OCR and AI can extract text and propose evidence links, but suggestions remain pending until an authorized user reviews them. Accepting evidence still does not certify the source or determine compliance.

Only when optional AI enhancement is enabled and configured. Local OCR can operate without an API key. The production Privacy Policy and subprocessor disclosure should identify the actual provider configuration.

Yes. Authorized users can export the current active logbook as a PDF. Keep original source files and required official records independently.

AirplaneHQ uses recoverable archive/remove workflows for many logbook operations. Permanent deletion is restricted and may require removing connected evidence first.

No. It records expenses, calculates balances, suggests settlements, and records payments reported by members. Actual payment occurs outside AirplaneHQ.

An expense can be divided equally among selected members or use exact custom shares. Historical participants can remain associated with older expenses.

A recurring rule generates pending expenses on its configured schedule. An owner confirms the amount before the entry becomes part of active totals and settlements.

Closing a period preserves and locks the reviewed accounting history through the selected date. Confirm expenses and settlements before closing.

Yes. Authorized users can export expense data as CSV. Reports also summarize utilization, flight activity, aircraft totals, annual expenses, category mix, and member activity.

Passwords use adaptive one-way hashing. API tokens are generated as high-entropy secrets, stored as hashes, and rejected after expiration. Users must still protect devices, email accounts, and private links.

Production traffic should use HTTPS. The recommended S3 configuration uses server-side encryption and private access. Database and backup protections depend on the production providers and configuration.

Use the security contact on the Support or Security page. Do not send credentials, private calendar URLs, or full aircraft records in the initial message.

Contact support from the email associated with your account and identify the partnership. Ownership and authorization must be verified before sensitive account, export, or deletion requests are fulfilled.