Narrative:

Aircraft X departed okc enroute to [destination]. We were cleared for the MUDDE1 departure to mudde; then direct to rbukl. Sometime between mudde and rbukl; we were instructed to depart fawnt heading 220. Fawnt was not along our route; so believed that phaup was the fix that the controller stated. We read back 'depart phaup heading 220'; and the controller accepted our readback. Sometime past fawnt; and prior to phaup; the controller asked us why we weren't flying the 220 heading that he instructed. We stated that we hadn't arrived at phaup yet. He stated that we were 25 miles (approx) past 'fawnt'; and instructed us to turn to a heading of 240. We complied and turned to the heading of 240. We asked if the spelling of the fix was P.H.a.U.P. He stated 'no; I don't have time to discuss it'. Afterward; we referenced the arrival chart and realized that he must have been referring to the fawnt intersection; and he must have not known that we were cleared from mudde to rbukl; bypassing fawnt. No other events occurred; and the flight arrived safely and on time.controller was not aware that we were cleared from mudde directly to rbukl; therefore bypassing fawnt. The name of the fix 'fawnt' sounds similar to the fix 'phaup'. The clearance was read back; referencing the 'phaup' intersection; without correction from the controller. Alleviate similar sounding fixes on a departure; arrival; and approach procedure. Or; until then; controllers spell out the name of the fix; to alleviate confusion or error.

Related reports:

Google
 

Original NASA ASRS Text

Title: An aircraft was instructed to depart a fix on a heading. The aircraft acknowledged the clearance but read back a different similar sounding fix. The Controller did not catch the read back error. The aircraft did not turn to the heading the Controller wanted due to the communication confusion.

Narrative: Aircraft X departed OKC enroute to [destination]. We were cleared for the MUDDE1 departure to MUDDE; then direct to RBUKL. Sometime between MUDDE and RBUKL; we were instructed to depart FAWNT heading 220. FAWNT was not along our route; so believed that PHAUP was the fix that the controller stated. We read back 'depart PHAUP heading 220'; and the controller accepted our readback. Sometime past FAWNT; and prior to PHAUP; the controller asked us why we weren't flying the 220 heading that he instructed. We stated that we hadn't arrived at PHAUP yet. He stated that we were 25 miles (approx) past 'FAWNT'; and instructed us to turn to a heading of 240. We complied and turned to the heading of 240. We asked if the spelling of the fix was P.H.A.U.P. he stated 'no; I don't have time to discuss it'. Afterward; we referenced the arrival chart and realized that he must have been referring to the FAWNT intersection; and he must have not known that we were cleared from MUDDE to RBUKL; bypassing FAWNT. No other events occurred; and the flight arrived safely and on time.Controller was not aware that we were cleared from MUDDE directly to RBUKL; therefore bypassing FAWNT. The name of the fix 'FAWNT' sounds similar to the fix 'PHAUP'. The clearance was read back; referencing the 'PHAUP' intersection; without correction from the controller. Alleviate similar sounding fixes on a departure; arrival; and approach procedure. Or; until then; controllers spell out the name of the fix; to alleviate confusion or error.

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.