AEGIS BMD — ambiguous track refresh.

Interactive scenario plan. Every objective and event carries a citation to the source paragraph that defines the expected behavior. Review, regenerate-with-note, or approve.

LEARNING OBJECTIVES · 4

LO-01
Identify a closing BMD profile and correctly classify the track within established timelines.
Cites NTTP 3-32.1 ¶ 4.2.3
LO-02
Execute the engagement handoff between Air Defense Commander and the track supervisor under EMCON.
Cites NTTP 3-32.1 ¶ 5.1.1
LO-03
Recognize an ambiguous-track pattern matching HAZREP 25-04-003 and respond per the updated TTP.
Cites TACMEMO 3-01 ¶ 2.4 · HAZREP 25-04-003
LO-04
Apply safety holds when fatigue-compromised decision patterns appear during the engagement window.
Cites OPNAVINST 3120.2A CFEMP § 3.6

SCENARIO EVENT TIMELINE · ~ 20 MIN

T+0:00Scene open · normal watch posturenormal
T+3:20Unknown air contact; bearing 043T, descendingnormal
T+4:15Track confidence decision pointdecision
T+6:00TACMEMO 3-01 ambiguity injectdecision
T+9:30EMCON shift · handoff to ADCnormal
T+12:40Engagement window openscritical
T+16:00Safety-hold prompt (fatigue heuristic)critical
T+20:00Debrief triggernormal

Approve & launch scenario →Generated by MAVRC AI · 87s · deterministic seed 0042