Narrative:

We were cleared via flight plan and pre departure clearance on the bndto RNAV SID. Crger transition dct jct. After the FMC initialization; I noticed that the route on the flight plan pages in the FMC [included both] crger and jct. I retrieved the bndto one departure page and began checking it against the FMC. I noticed that the altitudes were not in the FMC and that's when I went to the departures page in the FMC and selected the bndto one departure. After inserting the departure; I went back to the flight plan page and checked that the altitudes matched the printed SID; and they did. At that point I stated to the first officer that I needed to remember the proper verbiage for my first contact with ATC since we would be getting an RNAV departure with published altitude constraints. I then retrieved my ipad and opened to the fom to review the recent changes concerning RNAV departure verbiage. I then returned to the flight plan page and inserted the runway and RNAV arrival into our destination; followed by a total mileage check and then an initial departure track check between the printed SID and the FMC. I only recall that jct was still in the route. I still remember that I had seen crger in the route in the FMC at one time; but since crger had no altitude constraint; I can't be absolutely positive about where in the sequence of events I had seen it. We were [then] cleared for takeoff on [runway] 15L; 'RNAV scamm' to which I clarified to the first officer; (pilot flying); that scamm was in fact in the FMC with an altitude constraint. The takeoff and initial climb out were uneventful. After passing bndto we turned toward the next fix and I remember seeing jct on my nd still in the distance. ATC contacted us within a few miles of bndto to inform us that we were on the wrong transition. They cleared us direct to cuzzz and told us to resume the crger transition. ATC then said there were no separation issues and not to worry and that they had had many aircraft make that same mistake recently on this departure. ATC then stated that we needed to call them on the phone when we arrive lax. ATC then read me a phone number to contact them. When I arrived lax and called them; they stated that this problem had occurred about 15 times that day and over 100 times over the 2 days previous to that. The rest of the flight was uneventful.

Related reports:

Google
 

Original NASA ASRS Text

Title: An A320 flight crew; cleared to depart IAH on the BNDTO RNAV SID; CRGER transition; inexplicably departed BNDTO on the JCT transition. ATC noted the deviation and asked the crew to call after arriving at their destination. Noteworthy was the fact that JCT VOR was also an enroute fix on their flight plan not withstanding their assignment of the CRGER transition.

Narrative: We were cleared via flight plan and PDC on the BNDTO RNAV SID. CRGER transition DCT JCT. After the FMC initialization; I noticed that the route on the flight plan pages in the FMC [included both] CRGER and JCT. I retrieved the BNDTO ONE departure page and began checking it against the FMC. I noticed that the altitudes were not in the FMC and that's when I went to the departures page in the FMC and selected the BNDTO ONE departure. After inserting the departure; I went back to the FLT PLAN page and checked that the altitudes matched the printed SID; and they did. At that point I stated to the First Officer that I needed to remember the proper verbiage for my first contact with ATC since we would be getting an RNAV departure with published altitude constraints. I then retrieved my iPad and opened to the FOM to review the recent changes concerning RNAV departure verbiage. I then returned to the FLT PLAN page and inserted the runway and RNAV arrival into our destination; followed by a total mileage check and then an initial departure track check between the printed SID and the FMC. I only recall that JCT was still in the route. I still remember that I had seen CRGER in the route in the FMC at one time; but since CRGER had no altitude constraint; I can't be absolutely positive about where in the sequence of events I had seen it. We were [then] cleared for takeoff on [Runway] 15L; 'RNAV SCAMM' to which I clarified to the First Officer; (pilot flying); that SCAMM was in fact in the FMC with an altitude constraint. The takeoff and initial climb out were uneventful. After passing BNDTO we turned toward the next fix and I remember seeing JCT on my ND still in the distance. ATC contacted us within a few miles of BNDTO to inform us that we were on the wrong transition. They cleared us direct to CUZZZ and told us to resume the CRGER transition. ATC then said there were no separation issues and not to worry and that they had had many aircraft make that same mistake recently on this departure. ATC then stated that we needed to call them on the phone when we arrive LAX. ATC then read me a phone number to contact them. When I arrived LAX and called them; they stated that this problem had occurred about 15 times that day and over 100 times over the 2 days previous to that. The rest of the flight was uneventful.

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.