It is suggested to read Regulatory Sets: Setup before this article.
This article will detail Regulatory Set information on:
- Limitation setup;
- Limitation adjustments;
- Experience setup;
- Time Off setup; and
- other features.
Limitations defines the requirements and/or limitations of flight and rest activities for crew members with a number of available scenarios and conditions to be considered which might change those requirements.
Select the type of flight/duty/rest activity to be considered for the requirement.
A limitation requirement may be applied to crew members in the PIC and SIC positions (pilots) by selecting the Yes toggle button. If No is selected, this will also apply to ACM and Attendant positions.
The condition is applied to the limit number.
Enter the condition limit/minimum number for the type selected. Decimal values are accepted, but only in .5 increments.
This is a conditional field that will appear for when certain types are selected. For some duration selections, the frequency box will appear to enter a numerical value. Other duration selections are variable based on the crew member's activity. For example, the Flight Duty Period will consider each flight duty period logged for a crew member regardless of length.
This is a conditional field that will appear for when certain duration options are selected. For example if Hours is selected as duration, the frequency field will appear to specify the number of hours. Decimal values are accepted, but only in .5 increments.
Limitation adjustments are an element of the limitation requirements. It allows to add additional conditions which might affect the limit or frequency. Adjustments are applied in order from the top down.
In this example, the limitation for Pre Duty Rest is at least 11 hours. Then, if duty time for the flight duty period is between 12 and 15 hours, replace the Pre Duty Rest with 12 hours. Next, if the Pre Duty Rest is more than 15 hours replace the Pre Duty Rest to 14 hours. Finally, replace with 33 hours of Pre Duty Rest when the Time Zone Difference for the prior duty period is between 5 and 9. Time zones are calculated based on the zone, not on the local offset. Furthermore, the departure location time zone is not included in the calculation.
Select how to have the value adjusted. Some selections will display additional fields.
Select the value to be adjusted. Some values will display additional fields including: duration, time specific, percent, min, and max.
Provide the circumstance / condition that the adjusted value would be applied.
Experience defines take off and landing requirements the crew must perform within a select date range preceding the departure date of the flight the Regulatory Set is applied.
Select Crew Position
Select the crew position the experience requirement will apply to the personnel assigned that position for the trip/flight: PIC or SIC.
Model / Type
The experience requirements may be specified to be performed in the same aircraft make/model, same aircraft type rating, or based on all flying, regardless of aircraft type. If the toggle buttons are not selected, it refers to the aircraft type.
Day and Night Takeoffs / Landings Within Number of Days
Specify the number of take offs and landings the pilot is required to have performed within the number of days preceding the departure date of the flight. There are separate rows for those performed in the daytime and nighttime. If none required, leave as 0. For the night take offs and landings, there is the option of entering and alternate means of satisfying the requirement below.
Alternate Night Currency
If a pilot does not meet the requirement for the performed night take offs and landings within the number days defined, the pilot will then be checked against the alternate night currency requirement.
For example, to qualify for Alternate Night Currency the Crew Member must have the following:
1500 Total Flight hours
15 Flight hours (type specific) in 90 Days
3 Night TakeOffs and Landings in 6 Months (in ANY type)
6 SIM Night TakeOffs and Landings in 12 months.
The Crew Member must pass BOTH of the flight hour checks, and ONE of the TO/Landing checks, either in the aircraft OR SIM.
If the values for the alternate currency are kept as 0s, there will be no alternate currency check.
Note: SIM TakeOffs and Landings are input into a pilot's Logbook. The type set on the logbook entry must be Simulator to be considered in the Alternate Night Currency check. Add a Crew Logbook Entry
Time Off defines the amount of rest required for crew within a date range.
This works in conjunction with the Pre, Post, and Split Duty Rest defined in the Limitations section. If there are requirement entries submitted in this Time Off section, the Hard Days Off Per Quarter entry in the header will be nullified.
Add no activity to Total Time Off calculation
When toggled to YES, any available (non-event) time on the crew member's schedule will count as time off for the time off calculations. When toggled to NO, only events on the crew member's schedule with the selected Type or Category will count as time off.
Event Types and Event Categories that count towards Time Off
Click in the box to see a list of the available selections. Events on the crew member's schedule with the selected Type or Category will count as time off. Once selected/added they will display in blue. Use the X to remove.
Note: Event Types may be added / edited under My Company > Global Settings > General > Event Containers. And Duty/Event Categories may be added / edited under My Company > Global Settings > General > Duty/Event Categories.
Create New Time Off Requirement
Select the Add New button to create a new requirement. Four entry boxes will appear:
- Value - Enter a number that will be the amount of rest required.
- Type - Select the quantity type for the value entered: Hours or Days.
- Frequency - Enter a number that will be the range in which the rest will be required.
- Duration - Select the quantity type for the frequency entered: Days or Quarters.
Deactivating A Requirement Entry
Each entry has the option of being Active, which will include it in the requirement checks, or to be Inactive, which will not run the check and hide the entry. The checkbox controls the status of the entry - checked is Active. For Limitation entries, this is a toggle button.
Deactivated entries may be viewed by using the toggle buttons over to the Inactive list.