User Guide

190-00494-00 Rev. B
Garmin G1000 Pilot’s Guide for the Cessna Citation Mustang
3-11
EICAS
CAS DISPLAY INHIBITS
Inhibits prevent certain CAS messages from being displayed during the following conditions:
Aircraft on ground (GROUND)
Emergency bus power (EMER)
Engine start (Engine Start Inhibit, ESI)
Takeoff (TOPI)
Aircraft in air (AIR)
Landing (LOPI)
Engine shutdown (Engine Shutdown Inhibit, ESDI)
Inhibits affecting each CAS message are indicated with an “X” under the corresponding inhibit column in
Table 3-2. Alerts affected by an inhibit are not displayed while the inhibit is enabled. If an alert is displayed
prior to the activation of an inhibit affecting it, the alert continues to be displayed normally until the condition
causing the alert ceases to exist.
Takeoff and Landing Operation Phase inhibits (TOPI and LOPI) are implemented to reduce flight crew
workload and distractions during takeoff and landing. The following tables list the criteria which must be met
to activate or deactivate TOPI or LOPI; only one criterion must be met for activation or deactivation to occur.
Activation Deactivation
Transitions from on-ground to in-air
Airborne > 25 sec
IAS transitions > 50 knots (on either PFD)
IAS > 40 knots (on either PFD)
IAS invalid (on both PFDs)
Pressure altitude > 400 ft above field elevation*
TOPI active > 90 sec
* Pressure altitude captured when the aircraft transitions from on-ground to in-air
Table 3-3 Takeoff Operation Phase Inhibit (TOPI) Activation/Deactivation Criteria
Activation Deactivation
Transitions from in-air to on-ground
On-ground > 25 sec
IAS < 40 knots (on either PFD)
IAS invalid (on both PFDs)
GPS altitude transitions < 400 ft above field elevation* GPS altitude > 600 ft above field elevation*
LOPI active > 90 sec
* Stored in terrain database
Table 3-4 Landing Operation Phase Inhibit (LOPI) Activation/Deactivation Criteria
In order to prevent nuisance messages in the event of a dual generator failure, most messages are inhibited
when the emergency bus is powering the aircraft. Failure of a bus or processor also triggers an inhibit to prevent
invalid data from triggering a message. Most messages are not generated based upon invalid data; however,
there may be exceptions.