This walkthrough connects the Canberra arrival scenario to the references needed to approach, land and stop. Use it as an example of applying the docs during a run; the linked aircraft procedures and charts supply the operating details.
The scenario starts the Boeing 737-800 about 25 nautical miles (NM) from runway 35, at 5,000 ft and 220 knots (kt). The engines are running, and the autopilot holds heading, altitude and speed. There is no route in the flight management computer (FMC). The task is to approach, land and stop.
Start with the aircraft you have
Read the flight-deck indications and confirm the actual position, altitude, airspeed, selected targets, flight modes and configuration. The scenario description is an initial setup, not a fresh observation. Use the approach procedure to decide which preparation applies to the current flight.
Read the current checklist section for its item and execution identifiers. Mark an item only after checking its conditions and required evidence. Do not perform an earlier ground procedure in flight to fill in historical progress.
Select and read the approach
The route reference names the instrument landing system (ILS) approach ILS-Y runway 35. Read the ILS-Y or LOC-Y runway 35 chart for the complete setup, distance references, minima and missed approach. Its CB DME distances differ from the ICB DME profile on the ILS-Z chart. DME is distance-measuring equipment; CB and ICB identify different distance references. Keep the selected procedure and distance source together.
Reconcile the procedure with the installed navigation data and your assignment. Verify receiver tuning, identification, course, pressure setting and the applicable minima. An ILS frequency or a lit approach button does not establish capture.
For an agent, start with search_docs using a phrase such as “Canberra ILS-Y runway 35”. Read the returned page with read_docs; follow its links for supporting procedures. You can also read the known chart path directly:
Fly the selected aircraft procedure
Use ILS landing — part 1 and part 2. Observe the conditions for gear, flap, start-switch and speedbrake selections. Distinguish approach arming, localizer capture, glide slope alive and glide slope capture through the relevant flight-mode and navigation indications.
Use assigned performance data for the actual landing weight, flap setting and conditions. The 220 kt scenario starting speed is not a landing-speed target. After approach configuration, follow ILS autoland and rollout through channel verification, flare, touchdown and stopping. Checklist completion alone does not establish touchdown or rollout.
If a go-around is required, use the selected chart’s missed approach together with the aircraft go-around procedure. The chart supplies the track, altitude and climb-gradient requirements; the aircraft procedure supplies the applicable configuration and verification steps.
Land, clear and stop
Read the aerodrome layout before planning runway exit and taxi. Runway 35 has a displaced landing threshold: its published 2,683 m landing distance differs from its 3,283 m takeoff run. Review the marked incursion hot spots and the assigned taxi clearance.
Complete the applicable after-landing procedure, continue observing the aircraft, and stop as required by the scenario. Report missing reference information or controls through report_issue while retaining aircraft control. Last modified on October 30, 2026
