Narrative:

The following situation has been occurring daily, since air carrier started to fly yyz to bos, which began a couple of months ago. This is not an isolated event. Air carrier has filed and been cleared by yyz as indicated on the attached flight progress strip. However, the company has programmed the aircraft's FMS to deviate from the filed route at ehman intersection and proceed direct to the hankk intersection. See map below. Ehman intersection is approximately 12 mi north of J16. Although this deviation is slight and controllers daily encounter aircraft not precisely on their rtes, this deviation becomes critical because the aircraft is transitioning through the low to high altitude structure. The low altitude controller climbs the CL65 to FL270 and hands the aircraft off to the high altitude sector, dsv. The dsv controller believes the CL65 will proceed southeast to J16 and then turn left, will assign a higher altitude commensurate with his traffic, ie, the air carrier. I was involved with this identical situation the night before. I asked the buf sector controller if the CL65 was on his filed route and he confirmed that indeed he was. I did not assign a higher altitude and thankfully I didn't because the CL65 turned left at ehman as per his FMS. This would have a midair collision. Callback conversation with reporter revealed the following information: reporter stated the problem has not occurred in the last 2 or 3 weeks but indicated it took 2 months to get it stopped. Reporter indicated that someone from the facility had talked with the chief pilot about the routing situation. Reporter said the facility received a copy of an internal memo given to the flcs to the pilots and indicated it discussed the problem and the route to be flown. Reporter felt that there may be more occurrences of this nature with other commuters as they progress to regional jets and glass cockpits with automated equipment which he thought might affect their situation awareness.

Google
 

Original NASA ASRS Text

Title: RPTR STATES THE FLC OF COMMUTER CL65 DEVIATED FROM THE CLRED ROUTING. RPTR ALLEGES THE ACFT FMS IS PROGRAMMED FOR EHMAN DIRECT HANKK RATHER THAN THE V252 AND J16 RTE OVER THESE FIXES. THE DIRECT ROUTING CONFLICTS WITH TFC ON J547.

Narrative: THE FOLLOWING SIT HAS BEEN OCCURRING DAILY, SINCE ACR STARTED TO FLY YYZ TO BOS, WHICH BEGAN A COUPLE OF MONTHS AGO. THIS IS NOT AN ISOLATED EVENT. ACR HAS FILED AND BEEN CLRED BY YYZ AS INDICATED ON THE ATTACHED FLT PROGRESS STRIP. HOWEVER, THE COMPANY HAS PROGRAMMED THE ACFT'S FMS TO DEVIATE FROM THE FILED RTE AT EHMAN INTXN AND PROCEED DIRECT TO THE HANKK INTXN. SEE MAP BELOW. EHMAN INTXN IS APPROX 12 MI N OF J16. ALTHOUGH THIS DEV IS SLIGHT AND CTLRS DAILY ENCOUNTER ACFT NOT PRECISELY ON THEIR RTES, THIS DEV BECOMES CRITICAL BECAUSE THE ACFT IS TRANSITIONING THROUGH THE LOW TO HIGH ALT STRUCTURE. THE LOW ALT CTLR CLBS THE CL65 TO FL270 AND HANDS THE ACFT OFF TO THE HIGH ALT SECTOR, DSV. THE DSV CTLR BELIEVES THE CL65 WILL PROCEED SE TO J16 AND THEN TURN L, WILL ASSIGN A HIGHER ALT COMMENSURATE WITH HIS TFC, IE, THE ACR. I WAS INVOLVED WITH THIS IDENTICAL SIT THE NIGHT BEFORE. I ASKED THE BUF SECTOR CTLR IF THE CL65 WAS ON HIS FILED RTE AND HE CONFIRMED THAT INDEED HE WAS. I DID NOT ASSIGN A HIGHER ALT AND THANKFULLY I DIDN'T BECAUSE THE CL65 TURNED L AT EHMAN AS PER HIS FMS. THIS WOULD HAVE A MIDAIR COLLISION. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THE PROB HAS NOT OCCURRED IN THE LAST 2 OR 3 WKS BUT INDICATED IT TOOK 2 MONTHS TO GET IT STOPPED. RPTR INDICATED THAT SOMEONE FROM THE FACILITY HAD TALKED WITH THE CHIEF PLT ABOUT THE ROUTING SIT. RPTR SAID THE FACILITY RECEIVED A COPY OF AN INTERNAL MEMO GIVEN TO THE FLCS TO THE PLTS AND INDICATED IT DISCUSSED THE PROB AND THE RTE TO BE FLOWN. RPTR FELT THAT THERE MAY BE MORE OCCURRENCES OF THIS NATURE WITH OTHER COMMUTERS AS THEY PROGRESS TO REGIONAL JETS AND GLASS COCKPITS WITH AUTOMATED EQUIP WHICH HE THOUGHT MIGHT AFFECT THEIR SIT AWARENESS.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.