When responding to a request from another controller, such as receiving an APREQ for a block altitude, what must the student repeat?

When responding to a request from another controller, such as receiving an APREQ for a block altitude, what must the student repeat?

• A. ACID, the request and 'approved'
• B. ACID, the request and 'approved as requested'
• C. ACID, the request and 'denied'
• D. ACID, the request and 'pending'

Answer: (A)

In this coordination scenario, the clear goal is to confirm exactly what was requested and what decision was made. When you respond to an APREQ for a block altitude, you should repeat ACID, the request, and the status to leave no doubt about what was asked and whether it was approved. Saying “ACID, the request and 'approved'” communicates the identity involved, the original request details, and the final decision in a single, unambiguous line. The phrase should be simply 'approved' to reflect the granted status; adding qualifiers like 'as requested' isn’t part of the standard phrasing, and using 'denied' or 'pending' would imply a different outcome. This repetition helps ensure both controllers have an identical record of the coordination and reduces the chance of miscommunication.

In this coordination scenario, the clear goal is to confirm exactly what was requested and what decision was made. When you respond to an APREQ for a block altitude, you should repeat ACID, the request, and the status to leave no doubt about what was asked and whether it was approved. Saying “ACID, the request and 'approved'” communicates the identity involved, the original request details, and the final decision in a single, unambiguous line. The phrase should be simply 'approved' to reflect the granted status; adding qualifiers like 'as requested' isn’t part of the standard phrasing, and using 'denied' or 'pending' would imply a different outcome. This repetition helps ensure both controllers have an identical record of the coordination and reduces the chance of miscommunication.