Stefan Posted February 12, 2012 Report Posted February 12, 2012 (edited) it's not always clear for me, what the exact criterias for starting the tracking of the programmed route are.on simple departures, tracking begins immediate after takeoff. On more complex departures as in LOWS the RTT4V.16 e.g. (with virtual waypoints, departure starts with visual left-turn after t/o), the only way to start tracking that i found, is the dir-to next real waypoint after the initial left-turn.imho, tracking should start and eliminate passed virtual points, even if i fly the first part of the procedure visually and by hand (e.g. vasfmc does so - and seems to be realistic for me). e.g. when i pass the virtual 2DME (@RW16) point in LOWS, i think it should disappear from the legs-list, telling me, to start the left-turn manually - but nothing happens. even when i intercept the programmed track, the FMC doesn't start tracking.can somebody pls explain this FMC-behaviour for me, and how the correct FMC-procedure for LOWS RWY16 departures looks like? Edited February 16, 2012 by Japo32
jergp Posted February 13, 2012 Report Posted February 13, 2012 I've noticed the same thing. I can not seem to figure out when it decides to start tracking. Sometimes it takes as long as passing my first waypoint. I'd appreciate any advice too.
Japo32 Posted February 13, 2012 Report Posted February 13, 2012 In airports that you don't have SIDs you have to choose the departure runway at least to show the route in the MFD.
Stefan Posted February 13, 2012 Author Report Posted February 13, 2012 (edited) i *have* entered a full route from LOWS via SID RTT4V and transition RTT to LOWI.The FMCs that i know from the past (vasfmc and WILCO Airbus) both start tracking immediate after takeoff, even if the first part of the SID is a *visual* turn and the first waypoints are virtual points - but the crj200 does not start tracking in this situation. Edited February 13, 2012 by stefanpi
Stefan Posted February 13, 2012 Author Report Posted February 13, 2012 that's it! thank you for the information!!(i could not find this in the documentation - it says "EXEC activates flightplan, but not "starts tracking", which might not be the the same)pressing exec after takeoff solved the problem.
philipp Posted February 13, 2012 Report Posted February 13, 2012 Yip. Only ACT flightplan is tracked, never MOD.Philipp
Japo32 Posted February 14, 2012 Report Posted February 14, 2012 You have to press EXEC before takeoff.
Stefan Posted February 14, 2012 Author Report Posted February 14, 2012 ok! - works perfectly now!stefan
Recommended Posts