N1 control during a rolling takeoff centers on getting the engine speed close to the planned takeoff setting within a tight tolerance. The best practice is to tune thrust so the actual N1 is within a small margin below the target—specifically within 5% below. This slight under-run provides a safety buffer against engine response lag or gusts that could push N1 higher than intended, while still letting N1 rise to the target as airspeed increases. Being slightly under avoids pushing the engines above the exact takeoff setting, which could add unnecessary thrust, noise, or wear, and it keeps you on a predictable climb path once you rotate. Tolerances larger than 5% or requiring N1 above the target aren’t preferred because they either reduce margin for safe operation or overshoot the planned thrust level.

When a collision threat is resolved, you hear that you’re allowed to resume your flight path and altitude. The aural message that tells you you may return to the assigned altitude is “clear of conflict.” This signals that the avoidance maneuver is no longer necessary and you can go back to your previously assigned altitude, assuming ATC clearance allows. The other phrases aren’t about resuming altitude: a resolution advisory that ends still leaves you in a situation where you must stay on guard and follow any remaining instructions, a “What if” scenario isn’t an in-service clearance to change altitude, and a traffic advisory simply alerts you to nearby traffic without providing the clearance to return to the assigned altitude.

Unexpected weather during IMT 1 maneuvers calls for safety-first decision making. The best course is to abort the maneuver, descend to a safe altitude, and re-evaluate the flight plan or task. Aborting prevents you from flying into worsening conditions, while descending to a safe altitude reduces exposure to possible turbulence, icing, or restricted visibility and puts you in a position where you can regain control and reassess. Once at a safe level, check updated weather information and adjust the plan accordingly, choosing an alternate approach or route that keeps you clear of the weather. Continuing in hope of improvement isn’t reliable or safe, climbing to avoid weather can move you into new threats, and landing immediately is only necessary if you can’t safely continue.

FMS programming should be completed before the briefing because having the route, performance data, nav data, and other inputs loaded and verified ahead of time lets the crew review and discuss the plan without being tied up with data entry. This makes the briefing focused on validating the plan, weather, fuel, contingencies, and ATC clearances, rather than scrambling to input information. Doing the work during the briefing would split attention and hinder a smooth, safety-focused discussion. Doing it during the flight adds unnecessary workload and can violate sterile cockpit discipline during critical phases. Preparing the FMS beforehand keeps the briefing productive and the overall workflow safer and more efficient.