Meetups & fleet policies
Coordinate squadron events and apply organization-wide operating rules where the plan supports them.
Education and Enterprise organizations can coordinate meetups such as practice sessions, race days, and build workshops. Eligible organizations can also apply policy controls to keep fleet rules consistent.
Meetups
Organization admins create an event with its agenda and timing. Members can RSVP attending or declined, then log a flight from the meetup context after the event so the session is tied back to the team's activity.
Meetups are planning records. They do not replace the flight session, safety checklist, or any required operational approval.
Fleet-wide policies
Where the organization's plan includes policy controls, administrators can enable rules such as:
- Lock profile settings: callsign, bio, or weekly goal cannot be changed by pilots while the policy is active.
- Require a pre-flight checklist: a flight cannot be logged until the required checklist is complete.
- Enforce a minimum firmware version: an airframe below the organization's approved floor cannot be used for the protected workflow.
- Lock team inventory: pilots cannot modify shared hanger inventory while the policy is active.
These controls are enforced for the organization rather than merely hidden in the interface. The Policy status view shows pilots which rules are active and why an action is unavailable.
Policy controls are not a substitute for a pilot's judgment or local aviation requirements. They make the organization's chosen workflow consistent.