Narrative:

Release from dispatcher stated flight plan in FMS should not be followed due to errors. Clearance at bdl gave initial clearance to fly bradley 4 departure for vectors to hfd 143/hto 010 radial as filed. Filed route differed from initial departure instructions and portions of the file route agreed with what was programmed in the FMS (which we were told to disregard). The confusion occurred as to where on the route we were supposed to continue 'as filed.' since the route showed us to fly J121 from hampton we assumed after intercepting the hto 010 degree right we were to fly to hto and continue on J121 bos center asked us our route of flight after the hfd 143/17 because they had our route of flight as hfd 143/hto 010 then via a victor route to CCC. The confusion caused us to deviation from this course and made the controller give us vectors to prevent possible future conflict with other aircraft. Since we had basically three different clrncs 1. FMS 2. Company filed route 3. Cleared route by clearance delivery we were confused as to which one we should fly. If clearance delivery issues a route different than the filed route then the entire route should be read to the pilots. To avoid confusion, also we as pilots should question the entire route since the route cleared differed from the route filed. Supplemental information from acn 203072: we flew inbound on the hto 010 and missed the turn on the V16 since the fme routing was taking us to hto first. Boston center noticed our deviation when a conflict arose with another aircraft and issued us an avoidance vector. I have no idea how close the traffic was, the TCASII was set on a 10 mi range and did not display any targets on the scope.

Related reports:

Google
 

Original NASA ASRS Text

Title: DEV FROM FLT PLAN CLRNC RTE.

Narrative: RELEASE FROM DISPATCHER STATED FLT PLAN IN FMS SHOULD NOT BE FOLLOWED DUE TO ERRORS. CLRNC AT BDL GAVE INITIAL CLRNC TO FLY BRADLEY 4 DEP FOR VECTORS TO HFD 143/HTO 010 RADIAL AS FILED. FILED RTE DIFFERED FROM INITIAL DEP INSTRUCTIONS AND PORTIONS OF THE FILE RTE AGREED WITH WHAT WAS PROGRAMMED IN THE FMS (WHICH WE WERE TOLD TO DISREGARD). THE CONFUSION OCCURRED AS TO WHERE ON THE RTE WE WERE SUPPOSED TO CONTINUE 'AS FILED.' SINCE THE RTE SHOWED US TO FLY J121 FROM HAMPTON WE ASSUMED AFTER INTERCEPTING THE HTO 010 DEG R WE WERE TO FLY TO HTO AND CONTINUE ON J121 BOS CTR ASKED US OUR RTE OF FLT AFTER THE HFD 143/17 BECAUSE THEY HAD OUR RTE OF FLT AS HFD 143/HTO 010 THEN VIA A VICTOR RTE TO CCC. THE CONFUSION CAUSED US TO DEV FROM THIS COURSE AND MADE THE CTLR GIVE US VECTORS TO PREVENT POSSIBLE FUTURE CONFLICT WITH OTHER ACFT. SINCE WE HAD BASICALLY THREE DIFFERENT CLRNCS 1. FMS 2. COMPANY FILED RTE 3. CLRED RTE BY CLRNC DELIVERY WE WERE CONFUSED AS TO WHICH ONE WE SHOULD FLY. IF CLRNC DELIVERY ISSUES A RTE DIFFERENT THAN THE FILED RTE THEN THE ENTIRE RTE SHOULD BE READ TO THE PLTS. TO AVOID CONFUSION, ALSO WE AS PLTS SHOULD QUESTION THE ENTIRE RTE SINCE THE RTE CLRED DIFFERED FROM THE RTE FILED. SUPPLEMENTAL INFO FROM ACN 203072: WE FLEW INBOUND ON THE HTO 010 AND MISSED THE TURN ON THE V16 SINCE THE FME RTING WAS TAKING US TO HTO FIRST. BOSTON CTR NOTICED OUR DEV WHEN A CONFLICT AROSE WITH ANOTHER ACFT AND ISSUED US AN AVOIDANCE VECTOR. I HAVE NO IDEA HOW CLOSE THE TFC WAS, THE TCASII WAS SET ON A 10 MI RANGE AND DID NOT DISPLAY ANY TARGETS ON THE SCOPE.

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.