When ERAM is operational, flight progress strips must be posted for flights not contained in the ERAM system.

• A. When ERAM is operational, flight progress strips must be posted for flights not contained in the ERAM system.
• B. All flights must be posted regardless of ERAM status.
• C. Only flights contained in ERAM require strips.
• D. ERAM status does not affect strip posting for non-ERAM flights.

Answer: (C)

The policy hinges on ERAM being the source of the flight data. When ERAM is operational, the system already contains and displays the flight information for those flights, so a physical flight progress strip is produced only for flights that are represented within ERAM. This keeps the workflow streamlined by relying on the electronic record for most coordination while still providing a strip for those ERAM-listed flights as a supplement to the digital data. The other options would either require strips for flights not in ERAM, ignore ERAM status altogether, or contradict the relationship between ERAM presence and the need for a strip, which is why the statement that only flights contained in ERAM require strips is the best fit.