How should altitude information in data blocks reflect the clearance issued, with respect to JAN/MLU interim altitudes?

• A. Altitude data blocks should reflect the actual clearance issued; JAN/MLU interim altitudes LOA-compliant do not require entry; all other interim altitudes must be entered.
• B. Data blocks should reflect only the initial clearance.
• C. Interim altitudes must be entered regardless.
• D. Altitude data blocks are not used.

Answer: (A)

Altitude data blocks must reflect the clearance actually issued to the aircraft. That means the numbers you record in the block should match the controller’s current instruction. If an interim altitude is defined under a Letter of Agreement for JAN/MLU operations, that interim altitude is considered active through the LOA, so you don’t need to enter it separately in the data block—the LOA already covers it. But any interim altitude not covered by that LOA must be entered to keep the data block fully aligned with the flight’s explicit clearance and to avoid gaps in the instruction history. This approach keeps the data accurate and clear for pilots and for automation that relies on the issued clearance.