Narrative:

Shortly after departing we were cleared direct to the kambl intersection and to continue on the ENDEE4 arrival. Pilot monitoring (pm) was getting ATIS and communicating with FBO at mdw making arrangements for our arrival. Pm had just returned to my frequency as we approached kambl intersection and he was inputting approach and landing data. I noticed as we hit the kambl intersection that the aircraft did not turn towards the next fix. So; I zoomed in the scale on the mfd display and immediately checked my flight director mode to make sure I was in LNAV; and confirmed we were in the correct mode.this delayed my reaction a few moments. I spoke up and asked the pm to verify what I was seeing. We both agreed to go to heading mode and turn the aircraft back on the arrival. About this time ATC asked us if we were on the endee arrival. I looked at the mfd as we communicated with the controller. We were turning back on course; but were 4 miles off course. The controller decided to clear us to another intersection along our planned route.the controller cleared us to what we heard as the hills intersection. This was read back to the controller and input into the FMS. This fix is the initial approach fix on the GPS/RNAV31C at mdw. The controller handed us off to the next approach controller. This controller asked us if we were still on the arrival. We responded that the previous controller had cleared us to the hills intersection on the approach. This controller said; 'no.' we were supposed to be flying to the 'jillz' intersection; which is on the arrival. He; then cleared us to endee intersection and we continued with no further issue. Course deviation was detected by crew as aircraft did not smart turn towards next intersection. Then; by ATC. The next controller advised us of the next fix we were flying to being the wrong fix. Not sure why initial course deviation occurred. The mfd displayed a dashed line after kambl extending our inbound heading to the fix; and the FD was flying in this dashed line. The arrival was also displayed. So; going to heading mode and flying until we could correct the FMS problem was our best course for a timely correction. The second problem was most likely hear back/read back error with similar sounding intersections along our cleared route. We complied with ATC instruction as best we could. FMS vigilance would have helped. My mfd was zoomed out to a range where I did not notice the dashed lined past kambl intersection until the aircraft's lack of turning clued me in. By this time I was in reactionary mode versus being proactive. In communication; extra vigilance should be paid to look for similar sounding fix names anywhere in the cleared flight plan. Then; if any confusion arises to get clarification immediately.

Google
 

Original NASA ASRS Text

Title: Fractional Jet flight crew reported of a possible equipment problem with the FMS that might have taken them off course. Flight crew also reported of similar sounding intersections that also caused navigation problems.

Narrative: Shortly after departing we were cleared direct to the KAMBL intersection and to continue on the ENDEE4 arrival. Pilot Monitoring (PM) was getting ATIS and communicating with FBO at MDW making arrangements for our arrival. PM had just returned to my frequency as we approached KAMBL intersection and he was inputting approach and landing data. I noticed as we hit the KAMBL intersection that the aircraft did not turn towards the next fix. So; I zoomed in the scale on the MFD display and immediately checked my flight director mode to make sure I was in LNAV; and confirmed we were in the correct mode.This delayed my reaction a few moments. I spoke up and asked the PM to verify what I was seeing. We both agreed to go to heading mode and turn the aircraft back on the arrival. About this time ATC asked us if we were on the ENDEE arrival. I looked at the MFD as we communicated with the controller. We were turning back on course; but were 4 miles off course. The controller decided to clear us to another intersection along our planned route.The controller cleared us to what we heard as the HILLS intersection. This was read back to the controller and input into the FMS. This fix is the initial approach fix on the GPS/RNAV31C at MDW. The controller handed us off to the next approach controller. This controller asked us if we were still on the arrival. We responded that the previous controller had cleared us to the HILLS intersection on the approach. This controller said; 'No.' We were supposed to be flying to the 'JILLZ' intersection; which is on the arrival. He; then cleared us to ENDEE intersection and we continued with no further issue. Course deviation was detected by crew as aircraft did not smart turn towards next intersection. Then; by ATC. The next controller advised us of the next fix we were flying to being the wrong fix. Not sure why initial course deviation occurred. The MFD displayed a dashed line after KAMBL extending our inbound heading to the fix; and the FD was flying in this dashed line. The arrival was also displayed. So; going to heading mode and flying until we could correct the FMS problem was our best course for a timely correction. The second problem was most likely hear back/read back error with similar sounding intersections along our cleared route. We complied with ATC instruction as best we could. FMS vigilance would have helped. My MFD was zoomed out to a range where I did not notice the dashed lined past KAMBL intersection until the aircraft's lack of turning clued me in. By this time I was in reactionary mode versus being proactive. In communication; extra vigilance should be paid to look for similar sounding fix names anywhere in the cleared flight plan. Then; if any confusion arises to get clarification immediately.

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.