Narrative:

Enroute we received a reroute while cruising at FL370; M.80. The initial point in the reroute was direct 'pontiac.' my first officer looked up the identifier for pontiac; mi (psi) and entered it in the FMS. Shortly after we started the right turn I noticed an aircraft on the TCAS at FL370 and picked him up visually crossing from left to right in front of us at our altitude. I stopped the right turn and came back left to our original course to ensure we would pass well behind him. At the same time we confirmed the identifier for 'pontiac' with chicago center and were told pnt (pontiac; il). My first officer entered it in the FMS and we proceeded direct; basically straight ahead and only a few degrees from our original course before the reroute. These maneuvers were all done on autopilot. The other aircraft passed 5 NM in front of us and would have been closer had I not turned back to the left. The TCAS resulted in a traffic advisory (TA) but no resolution advisory (RA). ATC was concerned; as was I; with the above events so I asked for and received a telephone number so I could call them after landing. I did so and later that evening was informed no pilot deviation report would be filed with the FAA. Cause: three reasons: 1) the controller did not use the phonetic identifier (pnt) in the reroute instructions. 2) we did not request a phonetic identifier; but simply looked it up; and started a turn to the wrong 'pontiac.' 3) the major reason this event occurred is because the department of transportation/FAA has allowed two navaids (vors) in the same region of the united states (the great lakes) to have the same name (pontiac). This is an accident waiting to happen! Suggestions: change the name of one of the 'pontiac' vors like we recently changed the name of las vegas; NM; to fort union so it would no longer be confused with las vegas; nv. Do this immediately!

Google
 

Original NASA ASRS Text

Title: TWO VORS; PSI AND PNT; HAVE NAME OF PONTIAC AND CAN BE CONFUSED BY PLTS IF ATC DOES NOT CLRLY IDENTIFY THE DESIRED FIX.

Narrative: ENROUTE WE RECEIVED A REROUTE WHILE CRUISING AT FL370; M.80. THE INITIAL POINT IN THE REROUTE WAS DIRECT 'PONTIAC.' MY FO LOOKED UP THE IDENTIFIER FOR PONTIAC; MI (PSI) AND ENTERED IT IN THE FMS. SHORTLY AFTER WE STARTED THE R TURN I NOTICED AN ACFT ON THE TCAS AT FL370 AND PICKED HIM UP VISUALLY CROSSING FROM L TO R IN FRONT OF US AT OUR ALTITUDE. I STOPPED THE R TURN AND CAME BACK L TO OUR ORIGINAL COURSE TO ENSURE WE WOULD PASS WELL BEHIND HIM. AT THE SAME TIME WE CONFIRMED THE IDENTIFIER FOR 'PONTIAC' WITH CHICAGO CENTER AND WERE TOLD PNT (PONTIAC; IL). MY FO ENTERED IT IN THE FMS AND WE PROCEEDED DIRECT; BASICALLY STRAIGHT AHEAD AND ONLY A FEW DEGS FROM OUR ORIGINAL COURSE BEFORE THE REROUTE. THESE MANEUVERS WERE ALL DONE ON AUTOPILOT. THE OTHER ACFT PASSED 5 NM IN FRONT OF US AND WOULD HAVE BEEN CLOSER HAD I NOT TURNED BACK TO THE L. THE TCAS RESULTED IN A TFC ADVISORY (TA) BUT NO RESOLUTION ADVISORY (RA). ATC WAS CONCERNED; AS WAS I; WITH THE ABOVE EVENTS SO I ASKED FOR AND RECEIVED A TELEPHONE NUMBER SO I COULD CALL THEM AFTER LNDG. I DID SO AND LATER THAT EVENING WAS INFORMED NO PLT DEV RPT WOULD BE FILED WITH THE FAA. CAUSE: THREE REASONS: 1) THE CTLR DID NOT USE THE PHONETIC IDENTIFIER (PNT) IN THE REROUTE INSTRUCTIONS. 2) WE DID NOT REQUEST A PHONETIC IDENTIFIER; BUT SIMPLY LOOKED IT UP; AND STARTED A TURN TO THE WRONG 'PONTIAC.' 3) THE MAJOR REASON THIS EVENT OCCURRED IS BECAUSE THE DEPARTMENT OF TRANSPORTATION/FAA HAS ALLOWED TWO NAVAIDS (VORS) IN THE SAME REGION OF THE UNITED STATES (THE GREAT LAKES) TO HAVE THE SAME NAME (PONTIAC). THIS IS AN ACCIDENT WAITING TO HAPPEN! SUGGESTIONS: CHANGE THE NAME OF ONE OF THE 'PONTIAC' VORS LIKE WE RECENTLY CHANGED THE NAME OF LAS VEGAS; NM; TO FORT UNION SO IT WOULD NO LONGER BE CONFUSED WITH LAS VEGAS; NV. DO THIS IMMEDIATELY!

Data retrieved from NASA's ASRS site as of January 2009 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.