Narrative:

Our cleared route of flight from chicago to providence, ri, took us over the hancock VOR, then J68 to ponee intersection to join V-130 which proceeds through bradley VOR. The captain was flying, and in the area of hancock VOR we were cleared direct bradley VOR. Approaching bradley we were cleared to 14000 ft. The descent was started and approaching bradley VOR, the captain questioned ZBW about the routing beyond bradley. The captain assumed that the clearance direct bradley was off of our flight planned route. He was unaware that our flight planned route, which was now on the low chart as V-130, continued through the bradley VOR (bradley VOR was not listed as a fix on our ATC route of flight clearance). While I was trying to inform the captain of this, he was on the radio with ZBW. The aircraft passed over bradley VOR without the change in heading required to capture V-130. During the communications, an RA came up on the TCASII. The captain immediately followed the RA which occurred at 15000-15500 ft. A climb was started, and ATC notified. The intruding aircraft was acquired visually. At 16000 ft the conflict was cleared, and descent was resumed to 14000 ft. ZBW then assigned vectors to providence. There was no further comment on the incident. This incident was a result of the captain's unfamiliarity with the route. In particular, the point of changeover between jetway and vector airway routing. Better familiarity in the future will hopefully prevent this from happening again. There is a published arrival routing for the providence airport. It essentially duplicates the routing we were given. Had it been issued in our ATC clearance this incident would have been avoided. Supplemental information from acn 241223: the confusion could be avoided by my being more familiar with the route and better prepared. Also to note that the pvd tedy.TEDY1 STAR follows V-130 from bdl, and is much easier to use than the low altitude chart. If that STAR would have been issued there would have been no confusion.

Related reports:

Google
 

Original NASA ASRS Text

Title: HDG TRACK DEV ON PART OF FLC DEV FROM AND NON ADHERENCE TO ATC CLRNC CREATES A POTENTIAL CONFLICT. TCASII RA ENSUES.

Narrative: OUR CLRED RTE OF FLT FROM CHICAGO TO PROVIDENCE, RI, TOOK US OVER THE HANCOCK VOR, THEN J68 TO PONEE INTXN TO JOIN V-130 WHICH PROCEEDS THROUGH BRADLEY VOR. THE CAPT WAS FLYING, AND IN THE AREA OF HANCOCK VOR WE WERE CLRED DIRECT BRADLEY VOR. APCHING BRADLEY WE WERE CLRED TO 14000 FT. THE DSCNT WAS STARTED AND APCHING BRADLEY VOR, THE CAPT QUESTIONED ZBW ABOUT THE ROUTING BEYOND BRADLEY. THE CAPT ASSUMED THAT THE CLRNC DIRECT BRADLEY WAS OFF OF OUR FLT PLANNED RTE. HE WAS UNAWARE THAT OUR FLT PLANNED RTE, WHICH WAS NOW ON THE LOW CHART AS V-130, CONTINUED THROUGH THE BRADLEY VOR (BRADLEY VOR WAS NOT LISTED AS A FIX ON OUR ATC RTE OF FLT CLRNC). WHILE I WAS TRYING TO INFORM THE CAPT OF THIS, HE WAS ON THE RADIO WITH ZBW. THE ACFT PASSED OVER BRADLEY VOR WITHOUT THE CHANGE IN HDG REQUIRED TO CAPTURE V-130. DURING THE COMS, AN RA CAME UP ON THE TCASII. THE CAPT IMMEDIATELY FOLLOWED THE RA WHICH OCCURRED AT 15000-15500 FT. A CLB WAS STARTED, AND ATC NOTIFIED. THE INTRUDING ACFT WAS ACQUIRED VISUALLY. AT 16000 FT THE CONFLICT WAS CLRED, AND DSCNT WAS RESUMED TO 14000 FT. ZBW THEN ASSIGNED VECTORS TO PROVIDENCE. THERE WAS NO FURTHER COMMENT ON THE INCIDENT. THIS INCIDENT WAS A RESULT OF THE CAPT'S UNFAMILIARITY WITH THE RTE. IN PARTICULAR, THE POINT OF CHANGEOVER BTWN JETWAY AND VECTOR AIRWAY ROUTING. BETTER FAMILIARITY IN THE FUTURE WILL HOPEFULLY PREVENT THIS FROM HAPPENING AGAIN. THERE IS A PUBLISHED ARR ROUTING FOR THE PROVIDENCE ARPT. IT ESSENTIALLY DUPLICATES THE ROUTING WE WERE GIVEN. HAD IT BEEN ISSUED IN OUR ATC CLRNC THIS INCIDENT WOULD HAVE BEEN AVOIDED. SUPPLEMENTAL INFORMATION FROM ACN 241223: THE CONFUSION COULD BE AVOIDED BY MY BEING MORE FAMILIAR WITH THE RTE AND BETTER PREPARED. ALSO TO NOTE THAT THE PVD TEDY.TEDY1 STAR FOLLOWS V-130 FROM BDL, AND IS MUCH EASIER TO USE THAN THE LOW ALT CHART. IF THAT STAR WOULD HAVE BEEN ISSUED THERE WOULD HAVE BEEN NO CONFUSION.

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.