Narrative:

The first officer was flying the aircraft and we were recleared to las from luxor direct las VOR. The new routing was programmed into the FMC. We expected a 19L arrival and programmed the FMC for a visual to 19L with a 3-mile extension; leaving this routing in the FMC after a discontinuity following las. We discussed descent planning techniques and I demonstrated bringing the runway extension to the direct-to waypoint to show descent deviation information. We were switched to a new approach frequency who told us to expect 19R. The first officer changed the approach in the FMC and at this time the flight attendants called to inquire about securing the cabin and traffic was called by ATC. During these exchanges; we inadvertently changed the direct-to waypoint to the three mile extension for runway 19R instead of back to las. Soon after; ATC inquired if we were still heading direct las and we realized we were proceeding direct the runway extension waypoint. We immediately commenced a left turn; and ATC gave us a 20 degree left heading saying that we were approaching nellis airspace. No traffic conflict was observed. We flew the new heading and were soon cleared for the visual approach; which concluded without further incident. I should not have let myself become distracted by cabin calls and traffic and should have paid closer attention to the programming of the FMC. Following established company procedures for pilot flying programming and pilot not flying verification before executing a course change would have prevented this situation.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737 Flight Crew is cleared direct LAS planning Runway 19R. The FMC is programmed for direct to a three mile fix off Runway 19R instead of direct LAS. ATC corrects the track error.

Narrative: The First Officer was flying the aircraft and we were recleared to LAS from LUXOR direct LAS VOR. The new routing was programmed into the FMC. We expected a 19L arrival and programmed the FMC for a visual to 19L with a 3-mile extension; leaving this routing in the FMC after a discontinuity following LAS. We discussed descent planning techniques and I demonstrated bringing the runway extension to the direct-to waypoint to show descent deviation information. We were switched to a new Approach frequency who told us to expect 19R. The First Officer changed the approach in the FMC and at this time the Flight Attendants called to inquire about securing the cabin and traffic was called by ATC. During these exchanges; we inadvertently changed the direct-to waypoint to the three mile extension for Runway 19R instead of back to LAS. Soon after; ATC inquired if we were still heading direct LAS and we realized we were proceeding direct the runway extension waypoint. We immediately commenced a left turn; and ATC gave us a 20 degree left heading saying that we were approaching Nellis airspace. No traffic conflict was observed. We flew the new heading and were soon cleared for the visual approach; which concluded without further incident. I should not have let myself become distracted by cabin calls and traffic and should have paid closer attention to the programming of the FMC. Following established Company procedures for pilot flying programming and pilot not flying verification before executing a course change would have prevented this situation.

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