Users can create multiple regulatory sets for Part 91, Part 121, Part 135 and EASA flights. Regulatory sets can be set on the trip and leg level. Rest, duty and block time limitations can be setup to ensure crews are compliant across all areas. Users can also manage hard days off and landing currency all from one place.

Configure Regulatory Set 

  1. On the Main Navigation go to Crew Records > Regulatory Sets
  2. Click Create New
  3. Enter the name of the regulatory set, select the appropriate regulation and Save
  4. Click Edit on the created regulatory set
  5. Enter base rest and base rest threshold values. The base rest is the minimum amount and the base rest threshold is the hourly value the base rest needs to be checked within. For example, base rest is 10 hours and the base rest threshold is 24 hours. 
  6. If applicable, set the number of PIC requirements
  7. Enter the required crew quantity
  8. Enter the applicable values for excessive rest warning
  9. Tab to the Experience tab
  10. Click Add New to add experience requirements and save
  11. Tab to the Time Off tab and add any applicable time off requirements the operations needs to track

Rest, flight time and duty time limitation checks can be added to the same regulatory set. When applied to a trip, all limitations will be checked.

Here is an example of a complete regulatory set for 135.247 and 135.267.

The experience section of the regulatory set allows an operation to configure crew member experience checks with regards to takeoffs and landings. Operations are able to add experience requirements for PIC and/or SIC position. Take it a step further and track alternate night currency values. This check looks for log entries, flight events in the personnel profile and any T/O and landings logged through a flight log. 

Time Off:
The time off section of the regulatory set allows an operation to configure crew member time off compliance checks with regards to defining if no activity is or is not considered and the ability to designate whether specific event types and/or duty/event categories should count toward "time off." This section is primarily used by Canadian operations, but if other operations want to track additional time off, this is the area to configure it.

Here is an example of a CAR 700 (equivalent to FAR 135) time off requirement of 3 days in 17 days. Once setup when a crew member is assigned to a trip and the regulatory set CAR 700 is selected, the crew member is checked for compliance on each "time off" requirement setup (in this example, there is one). Note: Type can either be hours or days while duration can be days or quarters. 

This example is set to include activity in the check (personnel events scheduled for the crew members). The last setting to the time off settings allows the operation to select which event types and duty categories count toward the time off setting. 

Confirm Trip Complies

  1. Access the trip and set the regulatory set. Regulatory sets can be set on the trip or leg level. When set on the trip level, all legs are reviewed to comply with all parameters (i.e. limitations, experiences) set in the regulatory set. 

Setting a regulatory set on the leg level allows operations to differ limitations where needed. This can be useful when a Part 135 trip ends and the last leg doesn't need to comply with Part 135 regulations. On the overview page, next to each leg is the regulatory and regulatory set options. The leg level regulatory set only needs to be changed if a specific leg needs to comply with different parameters (i.e. Rest, Duty, Flight Time, etc.).  

The results of the compliance check will display within the Trip Snapshot > Crew Section. Additional setting options are available (Global > Trip > Settings), if the "Run Crew Conflict Checks when Added to Trip" option is set to yes, the crew conflicts will display as the crew is added to the trip (be sure to select the regulatory set first). 

Did this answer your question?