The Aerolync Platform is modular. Each module focuses on one operational area, and most organisations use several modules together. This page gives you a complete overview of every module, who typically uses it, and how modules interact.
Everyday modules
These modules are used daily by most organisations.
Relations — The people directory. Every person in Aerolync (pilot, student, flight instructor, external contact) has a relation record. Relations is where you manage personal details, licences, subscriptions, finance, billing, account access, and flight instructor settings. Almost every other module references Relations data. See Relations.
Schedule — The booking and planning system. The day scheduler shows aircraft availability, flight instructor slots, and existing reservations on a visual timeline. Staff and app users create bookings here. See Schedule.
Fleet — Aircraft management. Each aircraft has a record with configuration, flight logs, defects, maintenance thresholds, schedule blocks, documents, rental settings, and owner information. Fleet data feeds into scheduling, billing, and operational monitoring. See Fleet.
Finance — The financial workspace. Transactions, in-app payments, wire transfer reconciliation, per-relation balances, and invoicing are all managed here. Finance receives data from bookings, flight logs, and payments. See Finance.
Drive — The document library. Shared documents are organised in folders with revision tracking, validity dates, and view history. Both platform and app users access Drive. See Drive.
Operational modules
These modules support active flight operations.
Flight Register — The official aerodrome movement register. Every departure, arrival, airfield opening, and closing is logged here. The register receives data from the Pilot App and supports manual entry and export. See Flight Register.
Flights — The live operational monitor. Shows the current status of active and recently completed flights. Use Flights to check who is in the air and to follow up on flights that need attention. See Flights.
Role-specific modules
These modules are used by specific roles or departments.
Flight Training — Full student training management. Track student progress from intake through course completion with gradings, exercise-based evaluation, flight hour tracking, and document management. Includes course template setup and TKI (Theory Knowledge Instruction) class management. See Flight Training.
Standardization — Flight instructor standardization tracking. Create standardization event types and record sessions with supervisor, participants, and remarks. Standardization history also appears in the flight instructor's relation record. See Standardization.
Aeromail — Bulk email communication. Create targeted mailings using a rich-text editor with attachments, target recipients by subscription, label, role, or individual selection, and monitor delivery results. See Aeromail.
Access Control — Physical access management through relays. Configure relay devices, set geofence and booking-based access rules, manage person-specific exceptions, and review access logs. See Access Control.
Flight Sales — Event-based commercial flight sales. Set up events with aircraft types, passenger capacity, time slots, and ticket tracking. Includes public booking links and event-day operational monitoring. See Flight Sales.
Kiosk — Self-service endpoint control. Activate or deactivate kiosk devices used at the airfield. See Kiosk.
Administration modules
Admin Dashboard — The starting screen for administrators. Provides quick-access shortcuts to all platform areas and an insights view with organisational trends and statistics. See Admin Dashboard.
Settings — Organisation-wide configuration. Controls aerodrome defaults, flight logger rules, scheduler behaviour, finance defaults, subscription types, relation labels and roles, Aeromail sender configuration, and email notification rules. Changes in Settings affect the entire organisation. See Settings.
How modules connect
Aerolync modules do not operate in isolation. Here are the most important connections:
Relations is the foundation. Almost every module references relation data. A booking in Schedule links to a relation. A flight log in Fleet bills to a relation. A training record in Flight Training belongs to a relation.
Schedule feeds into operations. When a booking starts and the pilot logs a departure in the app, the flight appears in Flights (live status) and Flight Register (movement register). When the flight ends, billing data flows into Finance and aircraft hours update in Fleet.
Fleet connects to everything operational. Aircraft availability affects Schedule. Defects can block scheduling. Flight logs update Hobbs meters and trigger maintenance warnings. Rental settings determine billing rates used in Finance.
Finance collects from multiple sources. Flight billing comes from Fleet flight logs. Payments come from the Pilot App or external sources. Wire transfers are reconciled manually. Invoices are generated from accumulated transactions.
Pilot App interaction
Several platform modules are directly influenced by what happens in the Pilot App:
- Relations — App users manage their own profile, licences, and preferences, which appear read-only in the platform Relations record
- Schedule — App users create, view, and cancel bookings that appear on the platform scheduler
- Fleet — App flight logging creates flight log entries, updates Hobbs meters, and can report defects
- Flights — App departures and arrivals update flight status in real time
- Flight Register — App-logged movements appear in the aerodrome register
- Finance — App payments and flight billing create finance transactions
- Drive — App users access the same documents available on the platform
- Access Control — App users trigger relay access from their device