How do I identify several hooked tracks at once?

Check every contact first

A group change saves repeated button presses. It does not identify the aircraft for you. Complete the identification checks for each contact before assigning the same letter to all of them. An identity change can also affect fighters already investigating a contact.

Choose the group and apply its identity

1. Start with a clear working group: finish any map-target selection, close popups, then right-click an empty part of the map without dragging. This removes existing hooks.
2. Left-click each intended contact once to hook it. Read its callsign and track serial. Clicking an already-hooked contact again removes its hook, so check the result rather than counting clicks.
3. Use TRACK LIST if contacts overlap. Its Hook column shows which contacts are hooked. Make sure the selected contact is also in the hooked group; a selected contact outside that group takes the single-contact path.
4. With at least two changeable contacts hooked, leave text entry and press the appropriate identity shortcut, such as Ctrl + A for Assumed Friendly, Ctrl + U for Unknown, Ctrl + S for Suspect or Ctrl + H for Hostile. Left-clicking the same letter on the identity bar also uses the group.
5. If a confirmation appears, read the track count and any listed identity conflicts. Choose YES only if that group is correct. Choose NO or press Escape to cancel without applying the pending change.
6. In ASMA, choose SYS to read TRACKS RECLASSIFIED, then check the resulting letters on the intended tracks. Leaving ATC ends an open controller conversation. A contact may be skipped or refused; a group request does not guarantee that every letter changed. If no contact could be changed, choose ATC and look for IDENT FAILED. If neither message appears, check the actual letters and message filters before repeating the action.
7. Check ACTIVE OPS for any fighter task affected by the classification. If QRA launch options open, review the target and aircraft before confirming; the window alone does not mean fighters have launched.

Why a confirmation may not appear

The game asks before certain changes between the displayed threat and friendly categories. It does not ask before every group change. Check the hooked group before pressing a key, even when you expect a confirmation.

Which contacts are excluded?

The group operation skips friendly military role letters I, E, K, T and F, missiles marked M, and jamming strobes marked JAM. Other eligibility checks still apply when the change is made. Z (Zombie) uses its own individual-track checks and is not a group identity assignment.

Can an unhooked track change too?

Yes. The game can copy a classification to other contacts belonging to the same raid, even when they were not in your hooked group. This is separate from choosing a group of hooks. Check the related track letters afterwards; read identity changes and their effects before changing a threat classification.

When the command acts on one contact

The group feature is disabled in the built-in training lessons. It also falls back to the single-contact path when fewer than two changeable hooked contacts remain, or when the current selection is outside the hooked group. Complete the lesson’s own instructions and recheck the selected contact before assigning its identity.

Cancel a mistaken group

Choose NO in the confirmation, then right-click empty map space without dragging to clear the hooks. Select and check the intended contacts again. If you already confirmed, the cancellation cannot undo that change: reassess the affected contacts and their fighter tasks before making a correction.