The predictive EGPWS function should be manually inhibited when which scenario occurs?

The predictive EGPWS function should be manually inhibited when which scenario occurs?

• A. Landing at an airport not in the database to avoid unwanted alerts
• B. During normal cruise
• C. On takeoff
• D. While taxiing

Answer: (A)

Predictive EGPWS relies on the terrain and airport database to forecast terrain conflicts ahead and issue alerts before you reach the danger. If you’re landing at an airport that isn’t in the database, the system can’t accurately model the surrounding terrain and runway environment, which can cause false or unwanted alerts during the approach. Manually inhibiting the predictive function in that scenario prevents these nuisance warnings, allowing you to fly the approach with the standard terrain awareness in place without being distracted by incorrect alerts. Once you’re established on final at a known airport, re-enable predictive EGPWS to keep full protection. In normal cruise, takeoff, or taxiing, there’s no database mismatch, so there’s no need to inhibit the function.

Predictive EGPWS relies on the terrain and airport database to forecast terrain conflicts ahead and issue alerts before you reach the danger. If you’re landing at an airport that isn’t in the database, the system can’t accurately model the surrounding terrain and runway environment, which can cause false or unwanted alerts during the approach. Manually inhibiting the predictive function in that scenario prevents these nuisance warnings, allowing you to fly the approach with the standard terrain awareness in place without being distracted by incorrect alerts. Once you’re established on final at a known airport, re-enable predictive EGPWS to keep full protection. In normal cruise, takeoff, or taxiing, there’s no database mismatch, so there’s no need to inhibit the function.