Dual Check Restrictions

The system has two ways to force Dual Check compliance, and these are controlled by the two Siteconfig entries of USE_EXPIREDUALCHECK_HRS and USE_EXPIREDUALCHECK_DATE. The USE_EXPIREDUALCHECK_DATE mechanism enforces a dual-check based on a date (i.e. if you want a dual-check every 90 days irrespective of hours flown). The USE_EXPIREDUALCHECK_HRS mechanism enforces a dual-check based on a certain number of hours flown (i.e. if you want a dual-check every 15 hours of flight time).

Dual Check by Flight Hours

Setting up dual check by flight hours

USE_EXPIREDUALCHECK_HRS: This defines the number of hours of flying a member can do before a warning appears during the green-tag process and a block occurs during flight authorisation (unless you are authorising a dual instruction flight). If a pilot has exceeded the number of hours between dual checks then they are ONLY able to authorise a flight if that flight includes an instructor and the instruction type is "Dual".

Indicating a Dual Check flight

There are two ways to indicate when a Dual Check flight has occurred. The first is that when a dual instruction flight is invoiced a tick-box labeled "This was a formal DUAL-CHECK flight" shows up on the invoice details screen. If you tick this box the member record is updated automatically and the dual check hours counter for that member reverts to zero.

If you did not indicate the flight as a dual check flight during invoicing then you need to update the Members record manually. You need to capture the flight number (the Invoice number from the invoice of the flight) from the most recent dual-check flight that was done with this pilot. This resets the dual check hours counter such that it only counts hours flown by this pilot since this specific flight.

Dual Check by Date

This is old and crude logic and is not used by many schools.

USE_EXPIREDUALCHECK_DATE: This enables (Value = 1) or disables (value = 0) the Dual Check date logic. When enabled, the "Next dual check date" field is included on each member record, and a member cannot authorise a solo flight if this date is in the past.

The system does not automatically maintain this date. When a dual check flight is flown you need to update the member record manually with an updated date.