Narrative:

During preflight; the incorrect SID was entered and was not recognized until after takeoff. Our clearance was Relta3.B. Relta3 was entered. In sal; there are 4 reltas - (Relta3.; Relta3.a; B; and C - 737 is not allowed to do Relta3C). First officer received the clearance; and read it back; I monitored. We briefed in several stages- prior to the clearance; I briefed terrain and what he could expect for the SID because he was unfamiliar with sal. He got the clearance; I heard him read back 'Relta3.B' and when we briefed just prior to the checklist; it was verbalized again. In the FMC; I verified on departure page 2 that it said Relta3; but with no B. This gave me a momentary pause that if I had followed up on adequately or more thoroughly; I wouldn't need to file this [report]. The FMC departure page 2 indicated Relta3.relta in 1L; and relta in 1R; not Relta3B in 1L and relta in 1R. When I looked on the legs page; the first couple points seemed to be what I was expecting so I didn't investigate further. After takeoff; the nav display was showing a tear drop course reversal to the right; when Relta3B indicates turning left to intercept CAT R351. Putting this together quickly while the first officer was hand flying; I realized the incorrect SID had been entered into the FMC. I told the first officer (flying pilot) to turn to the left; and manually set him up for the radial intercept. This happened quickly; and I missed the altitude requirement to meet prior to turning clearly indicated on the SID page in the initial climb section. In my hurry; I only saw 'turn left heading 315 to intercept CAT 351 to relta' indicated in the routing section. Not long after the turn; departure queried; and subsequently made it clear that we had turned too early; but he was saying other things with such a thick accent it was difficult to understand exactly what else we had done wrong. I am still uncertain if we encroached on airspace; or if we caused a traffic conflict; or just irritated the controller by messing up. Terrain clearance was never an issue; and we didn't see any traffic on TCAS. Upon review; we definitely turned too early; and at night or IMC this could have been a grievous error. Luckily; it was VMC with high ceilings and good visibility.

Related reports:

Google
 

Original NASA ASRS Text

Title: B737NG flight crew reported a track deviation occurred departing MSLP when the crew loaded the wrong departure.

Narrative: During preflight; the incorrect SID was entered and was not recognized until after takeoff. Our clearance was Relta3.B. Relta3 was entered. In SAL; there are 4 Reltas - (Relta3.; Relta3.A; B; and C - 737 is not allowed to do Relta3C). First Officer received the clearance; and read it back; I monitored. We briefed in several stages- prior to the clearance; I briefed terrain and what he could expect for the SID because he was unfamiliar with SAL. He got the clearance; I heard him read back 'Relta3.B' and when we briefed just prior to the checklist; it was verbalized again. In the FMC; I verified on Departure page 2 that it said Relta3; BUT with no B. This gave me a momentary pause that if I had followed up on adequately or more thoroughly; I wouldn't need to file this [report]. The FMC departure page 2 indicated Relta3.Relta in 1L; and Relta in 1R; not Relta3B in 1L and Relta in 1R. When I looked on the legs page; the first couple points seemed to be what I was expecting so I didn't investigate further. After takeoff; the nav display was showing a tear drop course reversal to the right; when Relta3B indicates turning left to intercept CAT R351. Putting this together quickly while the First Officer was hand flying; I realized the incorrect SID had been entered into the FMC. I told the First Officer (flying pilot) to turn to the left; and manually set him up for the radial intercept. This happened quickly; and I missed the altitude requirement to meet prior to turning clearly indicated on the SID page in the Initial Climb section. In my hurry; I only saw 'turn left heading 315 to intercept CAT 351 to Relta' indicated in the routing section. Not long after the turn; Departure queried; and subsequently made it clear that we had turned too early; but he was saying other things with such a thick accent it was difficult to understand exactly what else we had done wrong. I am still uncertain if we encroached on airspace; or if we caused a traffic conflict; or just irritated the Controller by messing up. Terrain clearance was never an issue; and we didn't see any traffic on TCAS. Upon review; we definitely turned too early; and at night or IMC this could have been a grievous error. Luckily; it was VMC with high ceilings and good visibility.

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.