Narrative:

We were in the terminal phase of flight going into teb when we were level at 7000 ft with the autoplt coupled to the FMS. After several blocked xmissions the controller issued an immediate turn to 090 degrees for a CL65 regional jet. After another blocked transmission the CL65 crew requested clarification from ZBW on which way they wanted them to turn. The controller responded to them and then issued a right turn to 270 degrees for our aircraft using an abbreviated, incorrect call sign. We initiated the turn as the order was given and upon reaching the 270 degree heading we got a TA on the TCASII. Center issued the traffic and we responded that we had it in sight. The controller asked what our routing was after huo VOR. We were south of the fix at that time. He informed us that we were involved in a possible pilot deviation. We acknowledged that our next fix cleared to was the coate intersection. I was the PIC on the flight but I was in the right seat (PNF). We realized that both the #1 FMS and #2 were navigating direct to the wanes intersection which is the first waypoint on the VOR DME a to teb. I don't know if I inadvertently removed coate intersection when I entered the approach information or it was dropped out due to an FMS glitch. We recently upgraded to the new 5.0 software and have had some erroneous performance messages. We would never deviate from an assigned route intentionally. I believe there were several factors involved in this situation. 1) fatigue -- we were en route from the united kingdom with a fuel stop at cyqx and we were airborne for 8 hours at this point. 2) congested radio frequency -- several transmission were unreadable because more than one source was transmitting simultaneously. 3) improper communications -- the controller, in a situation that needed immediate action, used an erroneous call sign. 4) high workload -- running checklists, attending to passenger needs and communications with ground support were required to be performed in roughly the same time frame. 5) equipment failure -- the #2 eadi failing caused a distraction because the altitude pre-select knob is on the right side of the aircraft but with the #2 eadi failed the pilot in the right seat has to lean over to look at the #1 eadi to set an altitude.

Google
 

Original NASA ASRS Text

Title: CL60 CREW DEVIATES FROM CLRED RTE IN ZBW AIRSPACE.

Narrative: WE WERE IN THE TERMINAL PHASE OF FLT GOING INTO TEB WHEN WE WERE LEVEL AT 7000 FT WITH THE AUTOPLT COUPLED TO THE FMS. AFTER SEVERAL BLOCKED XMISSIONS THE CTLR ISSUED AN IMMEDIATE TURN TO 090 DEGS FOR A CL65 REGIONAL JET. AFTER ANOTHER BLOCKED XMISSION THE CL65 CREW REQUESTED CLARIFICATION FROM ZBW ON WHICH WAY THEY WANTED THEM TO TURN. THE CTLR RESPONDED TO THEM AND THEN ISSUED A R TURN TO 270 DEGS FOR OUR ACFT USING AN ABBREVIATED, INCORRECT CALL SIGN. WE INITIATED THE TURN AS THE ORDER WAS GIVEN AND UPON REACHING THE 270 DEG HDG WE GOT A TA ON THE TCASII. CTR ISSUED THE TFC AND WE RESPONDED THAT WE HAD IT IN SIGHT. THE CTLR ASKED WHAT OUR ROUTING WAS AFTER HUO VOR. WE WERE S OF THE FIX AT THAT TIME. HE INFORMED US THAT WE WERE INVOLVED IN A POSSIBLE PLTDEV. WE ACKNOWLEDGED THAT OUR NEXT FIX CLRED TO WAS THE COATE INTXN. I WAS THE PIC ON THE FLT BUT I WAS IN THE R SEAT (PNF). WE REALIZED THAT BOTH THE #1 FMS AND #2 WERE NAVING DIRECT TO THE WANES INTXN WHICH IS THE FIRST WAYPOINT ON THE VOR DME A TO TEB. I DON'T KNOW IF I INADVERTENTLY REMOVED COATE INTXN WHEN I ENTERED THE APCH INFO OR IT WAS DROPPED OUT DUE TO AN FMS GLITCH. WE RECENTLY UPGRADED TO THE NEW 5.0 SOFTWARE AND HAVE HAD SOME ERRONEOUS PERFORMANCE MESSAGES. WE WOULD NEVER DEVIATE FROM AN ASSIGNED RTE INTENTIONALLY. I BELIEVE THERE WERE SEVERAL FACTORS INVOLVED IN THIS SIT. 1) FATIGUE -- WE WERE ENRTE FROM THE UNITED KINGDOM WITH A FUEL STOP AT CYQX AND WE WERE AIRBORNE FOR 8 HRS AT THIS POINT. 2) CONGESTED RADIO FREQ -- SEVERAL XMISSION WERE UNREADABLE BECAUSE MORE THAN ONE SOURCE WAS XMITTING SIMULTANEOUSLY. 3) IMPROPER COMS -- THE CTLR, IN A SIT THAT NEEDED IMMEDIATE ACTION, USED AN ERRONEOUS CALL SIGN. 4) HIGH WORKLOAD -- RUNNING CHKLISTS, ATTENDING TO PAX NEEDS AND COMS WITH GND SUPPORT WERE REQUIRED TO BE PERFORMED IN ROUGHLY THE SAME TIME FRAME. 5) EQUIP FAILURE -- THE #2 EADI FAILING CAUSED A DISTR BECAUSE THE ALT PRE-SELECT KNOB IS ON THE R SIDE OF THE ACFT BUT WITH THE #2 EADI FAILED THE PLT IN THE R SEAT HAS TO LEAN OVER TO LOOK AT THE #1 EADI TO SET AN ALT.

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.