In the five-minute reroute sequence, which steps are required?

In the five-minute reroute sequence, which steps are required?

• A. Send a data block only
• B. Send a data block (if necessary), coordinate the reroute with the affected sector, inform the Radar controller reroute approved, update the flight plan, start handoff to the next sector
• C. Cancel the flight plan
• D. Wait for instructions

Answer: (B)

The idea here is to move a reroute through the system quickly and with everyone on the same page. Start by sending a data block only if necessary to push updated routing, altitude, and other flight plan details into the system so the displays and records reflect the change. Then coordinate the reroute with the affected sector so the neighboring controllers know what to expect and can adjust clearances and sequencing accordingly. After that, inform the Radar Controller that the reroute is approved, so they have current authority and situational awareness to manage separation and handoffs. Next, update the flight plan in the system to lock in the new route, constraints, and timing. Finally, start the handoff to the next sector to transfer surveillance and control as the aircraft moves into the adjacent airspace. This sequence ensures rapid, synchronized changes across data, coordination, authorization, plan updates, and sector transition. Sending only a data block would miss cross‑sector coordination and a formal approval; waiting for instructions would delay the reroute; canceling the flight plan would defeat the purpose of rerouting.

The idea here is to move a reroute through the system quickly and with everyone on the same page. Start by sending a data block only if necessary to push updated routing, altitude, and other flight plan details into the system so the displays and records reflect the change. Then coordinate the reroute with the affected sector so the neighboring controllers know what to expect and can adjust clearances and sequencing accordingly. After that, inform the Radar Controller that the reroute is approved, so they have current authority and situational awareness to manage separation and handoffs. Next, update the flight plan in the system to lock in the new route, constraints, and timing. Finally, start the handoff to the next sector to transfer surveillance and control as the aircraft moves into the adjacent airspace. This sequence ensures rapid, synchronized changes across data, coordination, authorization, plan updates, and sector transition. Sending only a data block would miss cross‑sector coordination and a formal approval; waiting for instructions would delay the reroute; canceling the flight plan would defeat the purpose of rerouting.