This article explains how to view, create, and manage Crew Requirements and Requirement Groups in Portside Horizon.
These settings define the mandatory qualifications, certifications, and training events crew members must maintain to stay compliant with operational and regulatory standards.
From the main menu:
More → Crewmember → Crew Requirements
(Reference: Screenshot – Crew Requirements Page)
The Crew Requirements module allows administrators to:
Define medical, licensing, and training requirements.
Organize requirements into logical groups (e.g., Pilot in Command, Second in Command).
Set validity periods, due dates, and grace periods.
Control when and where requirements apply (e.g., by aircraft type rating).
This ensures the system can automatically track and alert for upcoming or expired crew qualifications.
The Crew Requirements page contains two main sections:
This section categorizes crew members by role or qualification level.
| Field | Description |
|---|---|
| Group Name | The title of the requirement group (e.g., Pilot in Command, Second in Command). |
| Person Groups | Defines which crew or user group the requirement applies to. |
| Note | Optional description or internal note for the group. |
Actions:
+ New Group – Add a new requirement group.
✏️ Edit / 🗑 Delete – Modify or remove existing groups.
Example:
Pilot in Command (PIC) group contains requirements such as ATP License, 1st Class Medical.
Second in Command (SIC) group may include 2nd Class Medical or Aircraft-Specific Training.
This section lists all individual qualifications or certifications required for crew.
| Column | Description |
|---|---|
| Name | Name of the requirement (e.g., 1st Class Medical, ATP License). |
| Legality | Category defining legal or operational compliance. |
| Type | The type of requirement (e.g., Medical, Assignment, Training). |
| Inactive | Marks a requirement as inactive (no longer enforced). |
| Required In | Defines where the requirement applies (None, TypeRating, or specific context). |
| Period / Units | The validity duration (e.g., 1 Year, 6 Months). |
| Due | When the requirement becomes due (DayBefore, EndOfMonth, None). |
| Grace Before / Grace After | Defines buffer time before or after expiry (in days, months, or years). |
| Airport | Optional field if requirement is tied to a specific location. |
Navigate to More → Crewmember → Crew Requirements.
Click + New Requirement.
Complete the fields:
Name: Enter the requirement title.
Legality: Select applicable compliance category (e.g., FlightRestriction, Assignment).
Type: Choose requirement type (e.g., Medical, Training).
Required In: Specify scope (None, TypeRating, etc.).
Period / Units: Define the validity period (e.g., 1 Year, 6 Months).
Due: Choose when it’s due (e.g., DayBefore, EndOfMonth).
Grace Before / After: Add any grace periods allowed.
Click Save.
Requirement | Legality | Type | Required In | Period | Due | Grace Periods |
| 1st Class Medical | Flight Restriction | Medical_1 | None | 1 Year | Day Before | None |
| 2nd Class Medical | Flight Restriction | Medical_2 | None | 1 Year | Day Before | None |
| ATP License | Assignment | License_ATP | None | N/A | None | None |
| Commercial Pilot Certificate | Assignment | License_Comm | None | N/A | None | None |
| Aircraft Specific Training | Assignment | Training_Aircraft | TypeRating | 6 Months | EndOfMonth | 1 Month |
| Pilot in Command (PIC) | Captains | 1st Class Medical, ATP License, Initial Training |
| Second in Command (SIC) | First Officers | 2nd Class Medical, Aircraft Specific Training |
| Sync Crew Requirements | Updates system data to ensure recent changes are applied across all crew records. |
| Export to Excel | Allows exporting all requirements and groups for reporting or review. |
| Inactive Toggle | Deactivates old requirements without deleting their historical data. |
Always link medical and license requirements to regulatory compliance categories (e.g., FlightRestriction).
Use consistent naming conventions for requirement types to support data imports and integrations.
Regularly sync crew requirements after any structural changes.
Maintain reasonable grace periods to prevent flight delays due to expired qualifications.
Keep inactive requirements instead of deleting them for historical tracking and audits.