Narrative:

Clearance delivery gave us runway 28. We began taxiing to runway 28 (after setting our heading bug for the correct departure SID heading for runway 28) dorval 3. En route to runway 28, ground control informed us runway 28 was now closed and to make a 180 degree turn back to runway 24R. We complied and taxied to runway 24R. When reaching the departure end of runway 24R, we were cleared for takeoff. At 400 ft, air carrier X procedures call for heading select (which was now left to heading 284 degrees), incorrect for runway 24R, but correct heading for runway 28, our original runway. Departure control was upset with our incorrect heading -- so were we! Honest mistake.

Google
 

Original NASA ASRS Text

Title: FLC OF A B737-500 TURNED THE WRONG WAY AFTER TKOF DUE TO HAVING THE WRONG RWY PROGRAMMED INTO THE FMC BECAUSE OF A RWY CHANGE JUST BEFORE TKOF.

Narrative: CLRNC DELIVERY GAVE US RWY 28. WE BEGAN TAXIING TO RWY 28 (AFTER SETTING OUR HDG BUG FOR THE CORRECT DEP SID HDG FOR RWY 28) DORVAL 3. ENRTE TO RWY 28, GND CTL INFORMED US RWY 28 WAS NOW CLOSED AND TO MAKE A 180 DEG TURN BACK TO RWY 24R. WE COMPLIED AND TAXIED TO RWY 24R. WHEN REACHING THE DEP END OF RWY 24R, WE WERE CLRED FOR TKOF. AT 400 FT, ACR X PROCS CALL FOR HDG SELECT (WHICH WAS NOW L TO HDG 284 DEGS), INCORRECT FOR RWY 24R, BUT CORRECT HDG FOR RWY 28, OUR ORIGINAL RWY. DEP CTL WAS UPSET WITH OUR INCORRECT HDG -- SO WERE WE! HONEST MISTAKE.

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