Narrative:

After reviewing our dispatch paperwork; I tuned and called for our clearance. Our company flight plan was DAL8.soldo.mei. When I called for the clearance; there was some confusion in my readback. I believe I heard 'DALLAS8 hildo to meridian transition abc arrival to ZZZ; climb and maintain 10000 ft; expect 350; 10 mins after departure; squawk XXXX.' it is my belief I responded with 'dallas 8 hildo? With meridian transition abc arrival 10000 ft 350 in 10 squawk XXXX.' I mispronounced soldo as hildo as it was unclr to me. The controller phonetically spelled s-o-left-D-O intersection; and said soldo ('to'/'two') meridian and asked that I repeat my initial altitude and verify the squawk code as it was unreadable. He also asked about our RNAV capabilities several times; to which I replied we are RNAV capable. The controller said readback correct. After a few mins; the captain came in and we reviewed the departure as DAL8.soldo.mei...10/350 in 10 and XXXX squawk. We set up the departure as such in the FMS with me; first officer; as PF. After departure; we were climbing through approximately 6000 ft on a 160 degree heading in accordance with DAL8; when the departure controller said; 'aircraft X; I'm not quite sure where you're going; you were assigned the SOLDO2 departure weren't you?' after a brief period of confusion; the captain responded that we were on and assigned DAL8. The controller told us to maintain our present heading and maintain 10000 ft. We responded we would comply. After a short period of time we were assigned a 130 degree heading. We were level at 10000 ft when we received the next turn to 090 degree heading and were advised of traffic 1000 ft above. Shortly thereafter; we were cleared direct soldo intersection and handed off to the next controller. Once communication was established with the next sector; the captain went on communication #2 to return to the departure frequency. He wanted to clear up the departure confusion. The controller thanked him for the information. We were then handed off to our third controller and were advised that we needed to call the supervisor at dallas when we landed. The rest of the flight was conducted without event. It is my belief that this deviation occurred as a result of the break in the continuity of the clearance readback; whereby the DAL8 readback was not corrected. I believe that a major contributing factor was the nomenclature of the departure name. The readback of the filed and expected clearance was DAL8.soldo 'to' mei. With the break in the continuity in the readback without emphasis of 'RNAV;' soldo 2 mei sounds identical to the DAL8 readback of the expected 'soldo to mei.' it is recommended that strong consideration be given to eliminating the #2 from arrival and departure nomenclature to prevent any similar confusion in the future. As a result of this incident; it will now be my practice to insist on a full readback of the clearance if there is any confusion; rather than accepting a readback from point of the break in continuity.

Google
 

Original NASA ASRS Text

Title: ERJ170 FO EXPERIENCES CONFUSION OBTAINING CLEARANCE FROM CLEARANCE DELIVERY AT DFW WHICH IS NOT CORRECTED PRIOR TO DEPARTURE; RESULTING IN TRACK DEV.

Narrative: AFTER REVIEWING OUR DISPATCH PAPERWORK; I TUNED AND CALLED FOR OUR CLRNC. OUR COMPANY FLT PLAN WAS DAL8.SOLDO.MEI. WHEN I CALLED FOR THE CLRNC; THERE WAS SOME CONFUSION IN MY READBACK. I BELIEVE I HEARD 'DALLAS8 HILDO TO MERIDIAN TRANSITION ABC ARR TO ZZZ; CLB AND MAINTAIN 10000 FT; EXPECT 350; 10 MINS AFTER DEP; SQUAWK XXXX.' IT IS MY BELIEF I RESPONDED WITH 'DALLAS 8 HILDO? WITH MERIDIAN TRANSITION ABC ARR 10000 FT 350 IN 10 SQUAWK XXXX.' I MISPRONOUNCED SOLDO AS HILDO AS IT WAS UNCLR TO ME. THE CTLR PHONETICALLY SPELLED S-O-L-D-O INTXN; AND SAID SOLDO ('TO'/'TWO') MERIDIAN AND ASKED THAT I REPEAT MY INITIAL ALT AND VERIFY THE SQUAWK CODE AS IT WAS UNREADABLE. HE ALSO ASKED ABOUT OUR RNAV CAPABILITIES SEVERAL TIMES; TO WHICH I REPLIED WE ARE RNAV CAPABLE. THE CTLR SAID READBACK CORRECT. AFTER A FEW MINS; THE CAPT CAME IN AND WE REVIEWED THE DEP AS DAL8.SOLDO.MEI...10/350 IN 10 AND XXXX SQUAWK. WE SET UP THE DEP AS SUCH IN THE FMS WITH ME; FO; AS PF. AFTER DEP; WE WERE CLBING THROUGH APPROX 6000 FT ON A 160 DEG HDG IN ACCORDANCE WITH DAL8; WHEN THE DEP CTLR SAID; 'ACFT X; I'M NOT QUITE SURE WHERE YOU'RE GOING; YOU WERE ASSIGNED THE SOLDO2 DEP WEREN'T YOU?' AFTER A BRIEF PERIOD OF CONFUSION; THE CAPT RESPONDED THAT WE WERE ON AND ASSIGNED DAL8. THE CTLR TOLD US TO MAINTAIN OUR PRESENT HDG AND MAINTAIN 10000 FT. WE RESPONDED WE WOULD COMPLY. AFTER A SHORT PERIOD OF TIME WE WERE ASSIGNED A 130 DEG HDG. WE WERE LEVEL AT 10000 FT WHEN WE RECEIVED THE NEXT TURN TO 090 DEG HDG AND WERE ADVISED OF TFC 1000 FT ABOVE. SHORTLY THEREAFTER; WE WERE CLRED DIRECT SOLDO INTXN AND HANDED OFF TO THE NEXT CTLR. ONCE COM WAS ESTABLISHED WITH THE NEXT SECTOR; THE CAPT WENT ON COM #2 TO RETURN TO THE DEP FREQ. HE WANTED TO CLR UP THE DEP CONFUSION. THE CTLR THANKED HIM FOR THE INFO. WE WERE THEN HANDED OFF TO OUR THIRD CTLR AND WERE ADVISED THAT WE NEEDED TO CALL THE SUPVR AT DALLAS WHEN WE LANDED. THE REST OF THE FLT WAS CONDUCTED WITHOUT EVENT. IT IS MY BELIEF THAT THIS DEV OCCURRED AS A RESULT OF THE BREAK IN THE CONTINUITY OF THE CLRNC READBACK; WHEREBY THE DAL8 READBACK WAS NOT CORRECTED. I BELIEVE THAT A MAJOR CONTRIBUTING FACTOR WAS THE NOMENCLATURE OF THE DEP NAME. THE READBACK OF THE FILED AND EXPECTED CLRNC WAS DAL8.SOLDO 'TO' MEI. WITH THE BREAK IN THE CONTINUITY IN THE READBACK WITHOUT EMPHASIS OF 'RNAV;' SOLDO 2 MEI SOUNDS IDENTICAL TO THE DAL8 READBACK OF THE EXPECTED 'SOLDO TO MEI.' IT IS RECOMMENDED THAT STRONG CONSIDERATION BE GIVEN TO ELIMINATING THE #2 FROM ARR AND DEP NOMENCLATURE TO PREVENT ANY SIMILAR CONFUSION IN THE FUTURE. AS A RESULT OF THIS INCIDENT; IT WILL NOW BE MY PRACTICE TO INSIST ON A FULL READBACK OF THE CLRNC IF THERE IS ANY CONFUSION; RATHER THAN ACCEPTING A READBACK FROM POINT OF THE BREAK IN CONTINUITY.

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