Originally Posted by
Ian W
Perhaps you should read the FANS Operations Manual. If a waypoint is inserted and activated in the active route a Waypoint Change Event Report is triggered in ACARS.
Thanks for the suggestion. The FANS Operations Manual makes for interesting reading. Way more info than we get in our regular training. It looks like whoever programmed the turn didn't know about it either, and it likely triggered the last ACARS transmission.
http://overlookci.com/files/Download...n%206-0%20.pdf
6.2.2 The event contract
An event contract specifies a request for reports to be transmitted by the aircraft whenever a defined “event”
occurs. Only one event contract can be established between a ground system and a particular aircraft at any one
time, however the event contract can contain multiple event types.
Note that multiple ATSUs with ADS-C connections can each establish their own event contracts with an
aircraft.
Once an event contract has been established, it remains in effect until the specific event requests are fulfilled, or
it is cancelled by the ground system.
The Vertical Rate Change Event is triggered when the aircraft’s vertical rate is either less than or greater than
a parameter defined in the contract.
The Lateral Deviation Change Event is triggered when the aircraft’s actual position exceeds a lateral distance
parameter from the aircraft’s expected position on the active flight plan.
The Altitude Range Change Event is triggered when the aircraft’s altitude exceeds the altitude ceiling or floor
defined in the contract by the ground system.
Once a vertical rate change, lateral deviation change, or altitude range event trigger has occurred, a recurrence
of this event no longer triggers an event report. The ground system must initiate a new event contract every time
that one of these specific events occurs.
The Waypoint Change Event is triggered by a change to the next or the next-plus-one waypoints. Such a
change normally occurs due to routine waypoint sequencing. However, it will also be triggered by occurrences
such as a change to a non-ATS waypoint entered by the pilot for operational reasons, or execution of a new
route affecting the next or next-plus-one waypoints. Unlike the other event contracts, the waypoint change
event
trigger remains in effect for all waypoint changes.
6.3.3 Flight crew modification of active route
The flight crew will often insert non-ATS waypoints into the active flight plan in the FMS for flight system monitoring, or will modify the active route for planning purposes. Once the change is activated, a Waypoint Change Event report may be triggered. If so, non-ATS waypoints included in the active flight plan will be reflected in the Predicted Route Group, as well as the Intermediate and Fixed Projected Intent Groups, which may result in the next, or the next-plus-one waypoints from the report not being waypoints expected in the ATS flight plan or flight data record.