FMS hold entry
Hold clearance
Record fix, course, turn and leg.
Identify holding fix, inbound course, turn direction, leg time or distance, cleared altitude and any speed restriction from the clearance and chart.
Position before entry
Know the current active leg and mode. A hold edit should not distract from an imminent turn or altitude capture.
Open the hold function
Open NAV INDEX 1/2. FSS lists a direct HOLD prompt and also PATTERNS → HOLD.
Choose the fix
The F-PLN page says either route puts *HOLD* in the scratchpad; the NAV page also describes HOLD as a direct select. Follow the prompt shown. If *HOLD* is in the scratchpad, press the left line-select key beside the appropriate FPL fix. Confirm that it matches the clearance.
Complete the page
Compare the page with clearance.
Check course, direction, leg parameters and EFC against the clearance. The current FSS page lists no cleared-altitude field. INSERT/APPLY puts the pattern in the MOD plan.
Review and activate
Inspect MOD, then verify active guidance.
Inspect the geometry and remaining route on the map before ACTIVATE. Verify the active lateral mode and follow the aircraft.
Plan the exit
Check onward leg and clearance.
FSS lists EXIT and RESUME HOLD as context prompts. Check the planned exit leg and your onward clearance before using either.
Check the active fix and the exit leg after making the hold active. FSS flight-plan page [20].
Set the cleared altitude separately on ALT SEL and confirm it on the PFD. The current HOLDING PATTERN page lists no altitude field; selecting ALT SEL sets a target but does not itself start a climb or descent. FSS vertical modes [38] · PFD altitude indications [62].
The entry page shows how to build a hold in the MOD plan. It does not confirm that the aircraft is flying the charted pattern; monitor the actual track after activation.
One v1.0 E190 video describes a programmed hold that was flown and exited, but does not show enough parameters or mode indications to repeat the result. Discord posts from 8–9 November report an endless route and say the hold function was not working. Neither report identifies the exact build and route well enough to diagnose the difference. Treat programmed holding as something to verify in your installed build, not a guaranteed result or a confirmed version-wide failure. Before ACTIVATE, compare the MOD geometry with the chart. After activation, compare the FMA and actual track with the clearance. If they do not match, do not assume the aircraft is flying the hold correctly; maintain the cleared path with a suitable selected mode or manual control. v1.0 E190 video report [63] · Community-support report, 8–9 November [64] · General-talk discussion, 9 November [65] · Reply on hold programming [66]