Skip to main content
This worked flight-planning example connects Sydney to Canberra in the Boeing 737-800. It shows how the route, navigation-data observations and scenario assumptions fit together; it is not a flight plan for every run. It does not include weather, wind or an ATC clearance. The source plan states that those inputs are not available through its tools; obtain any required clearance from the user rather than treating the route as a clearance.

​
Route

Waypoints (latitude, longitude): The source records these FMC legs from a check on the aircraft using navigation-data cycle 2610:
  • Departure: (500), DUNES, DEENA, GROOK, OLVAG (6000 A), ISBEX (270 B), WOL.
  • WOL to LEECE is a direct leg of about 50 NM. The FMC leaves a ROUTE DISCONTINUITY there until LECE is inserted after WOL.
  • Arrival: LEECE, AKLIM (9000 A), EKASA (7000 A), SLICK (6000 A), FOXLO (6000 A), MOMBI (4760 A), DAMKO (3140), RW35 (1919), then the missed approach.
The GROOK Two chart supplies the published tracks, crossing restrictions and speeds for this departure. Its initial right turn is “as soon as practicable”; the (500) item above is the recorded FMC leg, not a separately stated turn-altitude restriction on that chart. The recorded simulator navigation data has SID GROOK2, not GROOK1. A route file saved against an older cycle may still say GROOK1. The discontinuity note above calls the inserted fix LECE, while the route table names LEECE; check the actual FMC selection and route display rather than assuming those labels are interchangeable.

​
Scenario performance assumptions

These values are scenario assumptions, not values taken from an operational flight plan (OFP).

​
FMC units

The FMC works in thousands of pounds, not kilograms. Convert from the airplane readings:
  • ZFW (thousand lb) = (takeoff-data.gross-weight - takeoff-data.fuel-total) x 2.2046 / 1000
  • For example 57 159 kg is 126.0; 5171 kg of fuel is 11.4.

​
Load in the cold-and-dark scenario

About 5.2 t of fuel and a gross weight of about 62.3 t (ZFW about 57.2 t). Read the current values from takeoff-data before you use them.

​
Arrival naming across snapshots

The recorded simulator plan pairs LECE1W with ILS Y runway 35. The published LEECE One Whiskey chart in this collection continues to RNP W runway 35 (AR). The Alpha chart includes an ILS continuation. These are different source snapshots; verify the installed FMC route and assigned approach instead of silently combining the branches.

​
Approach and airport references

Use the Canberra ILS-Y runway 35 reference, Canberra airport procedures, and Sydney airport procedures alongside the assigned flight. The chart collection is a separate fixed snapshot; reconcile it with the installed navigation data. Source: IRL Gym’s Sydney–Canberra scenario flight plan.
Last modified on October 30, 2026