How it works
Start with the schedule. Let every step improve the next.
AirplaneHQ follows the way a partnership actually works: plan the airplane, record what happened, keep maintenance current, preserve the evidence, and settle shared costs.
Operating loopContext carries forward
PlanFlyRecordLearn
01
Partnership + aircraft
Set the foundation
Create the partnership, establish the aircraft identity and current time, then decide who can see and do what.
- Booking and visibility settings
- Member roles and aircraft access
- Qualifications and maintenance authority
- Standard record folders
02
Schedule
Plan shared use
Members reserve within the context of availability, access, qualifications, instructors, buffers, and partnership rules.
- Calendar and list views
- Recurring reservations
- Instructor coordination
- Maintenance blocks and private feeds
03
Operate + log
Close the flight loop
After the reservation, record the flight so current aircraft time can inform maintenance, reporting, and the next handoff.
- Reservation-linked flight logs
- Tach and Hobbs validation
- Fuel and oil context
- Squawk reporting
04
Maintain
Coordinate aircraft health
See AVIATES context, track date and meter limits, group work into service events, and preserve a completion history for every item.
- Calendar and meter limits
- AVIATES context
- Events, projects, and components
- Coming-due awareness
05
Records + logbooks
Keep the source attached
Files uploaded anywhere are available in Records, while reviewed logbook pages can link directly to the maintenance they support.
- Automatically connected documents
- Visibility and versions
- Review-first imports
- Page and region evidence
06
Expenses + reporting
Settle without the spreadsheet
Choose who shares each cost, review recurring expenses, follow suggested payments, and close the period with its history intact.
- Receipts and selected participants
- Recurring expenses
- Suggested settlements
- Utilization and cost reporting
The operating principle
Make the next decision easier to verify.
Each completed workflow leaves useful context for the next: a reservation becomes a flight log; a meter update informs maintenance; a completion carries its evidence; an expense carries its receipt; an access change preserves history.
Start with one aircraft
You do not need to migrate everything in a day.
Create the partnership, establish current aircraft context, invite the roster, and bring records in as the workflow needs them.