EMB145 first officer reported a track deviation after being cleared direct to bessi during arrival t...

Narrative:

After checking-in with washington center (it was either washington or potomac) we were hearing of many deviations on the phlbo arrival into ewr due to building storms along the arrival. After a few minutes of being on frequency we were given instructions to fly direct to the besse intersection; then direct a fix north of dqo; I believe it was dylin. As the controller was issuing the instruction; he spelled the intersection. As he did; I typed it into the FMS scratch pad and confirmed with the captain that it was the correct fix. He wrote the intersection down as the instruction was issued; and we both agreed it was correct. The besse fix took us further west than our original flight plan; but seemed to keep us clear of the weather so we did not question it. We were handed off to; and checked in with potomac and heard nothing after the check-in for probably ten minutes or so. The controller then asked which fix we were going to; and seemed confused as to why we were going that direction for besse. After having us spell the fix; controller discovered that we were going to another besse; and that we should have been going to bessi; much further north. Controller issued us a heading to get on course while we programmed the FMS; and explained no being aware of the existence of a besse intersection. After getting on course we were handed off to the next sector and thanked for our help. The flight continued without further issue or complication. In this case the two fixes were spelled the same with the exception of one letter. I believe the captain did read back the spelling of the fix; so it is hard to tell if the error was detectable. Being that the two fixes were relatively close together (besse and bessi are both in the northeast) it did not trigger a mental flag to question the assignment. In other cases of duplicate fixes; one fix may be on a totally different continent and the FMS will prompt the crew accordingly; but this not being the case made the threat more prominent.

Original NASA ASRS Text

Title: EMB145 First Officer reported a track deviation after being cleared direct to BESSI during arrival to EWR. The crew entered BESSE into the FMC and ATC detected the error.

Narrative: After checking-in with Washington Center (it was either Washington or Potomac) we were hearing of many deviations on the PHLBO arrival into EWR due to building storms along the arrival. After a few minutes of being on frequency we were given instructions to fly direct to the BESSE intersection; then direct a fix north of DQO; I believe it was DYLIN. As the controller was issuing the instruction; he spelled the intersection. As he did; I typed it into the FMS scratch pad and confirmed with the Captain that it was the correct fix. He wrote the intersection down as the instruction was issued; and we both agreed it was correct. The BESSE fix took us further west than our original flight plan; but seemed to keep us clear of the weather so we did not question it. We were handed off to; and checked in with Potomac and heard nothing after the check-in for probably ten minutes or so. The controller then asked which fix we were going to; and seemed confused as to why we were going that direction for BESSE. After having us spell the fix; controller discovered that we were going to another BESSE; and that we should have been going to BESSI; much further north. Controller issued us a heading to get on course while we programmed the FMS; and explained no being aware of the existence of a BESSE intersection. After getting on course we were handed off to the next sector and thanked for our help. The flight continued without further issue or complication. In this case the two fixes were spelled the same with the exception of one letter. I believe the Captain did read back the spelling of the fix; so it is hard to tell if the error was detectable. Being that the two fixes were relatively close together (BESSE and BESSI are both in the northeast) it did not trigger a mental flag to question the assignment. In other cases of duplicate fixes; one fix may be on a totally different continent and the FMS will prompt the crew accordingly; but this not being the case made the threat more prominent.

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

Attributes
ACN	1457466
Time
Date	201706
Local Time Of Day	1801-2400
Place
Locale Reference	ZDC.ARTCC
State Reference	VA
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Make Model Name	EMB ERJ 145 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	SID PHLBO3
Flight Plan	IFR
Person 1
Function	First Officer Pilot Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types

EMB145 first officer reported a track deviation after being cleared direct to bessi during arrival to ewr. The crew entered besse into the FMC and ATC detected the error.