Phoenix to Las Vegas: load a departure and an approach

advancedPremium

✈ Cessna 172 G1000⏱ ~9 minutes📊 4 steps

Build a cross-country plan at two airports this trainer has never flown, then use the PROC page to load a real FAA departure out of Phoenix and an ILS into Las Vegas.

Fly this one with Premium

The G1000 checks every knob, softkey and entry as you make it, and tells you when something was accepted but wrong.

See Premium →Try the free scenarios →

Step-by-step: Phoenix to Las Vegas: load a departure and an approach

On the FPL page, push the FMS knob and enter KPHX as the first waypoint.
The trainer resolves the ident against a worldwide airport layer rather than a short built-in list, so an airport it has never shown you before is still a valid waypoint.
Enter KLAS as the second waypoint, so the plan reads KPHX then KLAS.
The first waypoint is your origin and the last is your destination — that is how the PROC page knows which airport each selection is for.
Press PROC, choose SELECT DEPARTURE, and load the KEENS3 off runway 25L with the WLVRN transition.
KEENS3 is a departure Phoenix traffic really does use to leave for Las Vegas — WLVRN is where the route picks up the airway towards the Parker VORTAC. Only the branch for the runway you chose is inserted: off 25L that is WULKO then KEENS, where off the easterly runways it is a longer branch entirely. Loading all of them at once would not be a route.
Press PROC again, choose SELECT APPROACH, and load the I26LZ with the DICSA transition.
I26LZ is an FAA-coded ILS to runway 26L, and the unit shows that coded identifier rather than a chart title. Its DICSA transition runs in over the Boulder City VORTAC, which is the right side of Las Vegas to be arriving from Phoenix. The missed-approach legs are not spliced into the plan at all — they are flown only on a go-around.

Background reading

← Back to all scenarios