In CRM/FMS operations, which statement best defines confirmation?

In CRM/FMS operations, which statement best defines confirmation?

• A. Confirmation is confirming after actions have been taken to verify results
• B. Confirmation is verifying that information relates to the autopilot mode
• C. Verifying that information or an action is correct before execution
• D. Confirmation is optional if procedures are known

Answer: (C)

In CRM/FMS operations, confirmation means verifying that the information or an action is correct before you execute it. This pre-action check is crucial because it catches mistakes before they can affect the flight, turning a potential error into a safe, manageable decision. It fits with crew practices like cross-checking data, readbacks, and mutual verification, and with FMS use like validating the waypoint sequence, altitudes, and performance inputs prior to pressing “enter” or execute. Choosing this pre-execution verification over post-action checks makes sense because confirming after the action has been taken only reveals whether a mistake occurred, not prevent it. It’s not limited to autopilot-related details, since confirmation applies to any information or action, not just mode changes. And it isn’t optional; in CRM/FMS practice, verification before execution is a standard safety step even when procedures are well known.

In CRM/FMS operations, confirmation means verifying that the information or an action is correct before you execute it. This pre-action check is crucial because it catches mistakes before they can affect the flight, turning a potential error into a safe, manageable decision. It fits with crew practices like cross-checking data, readbacks, and mutual verification, and with FMS use like validating the waypoint sequence, altitudes, and performance inputs prior to pressing “enter” or execute.

Choosing this pre-execution verification over post-action checks makes sense because confirming after the action has been taken only reveals whether a mistake occurred, not prevent it. It’s not limited to autopilot-related details, since confirmation applies to any information or action, not just mode changes. And it isn’t optional; in CRM/FMS practice, verification before execution is a standard safety step even when procedures are well known.