Narrative:

I completely botched the departure out of sdq. Given runway heading to 3000 ft off runway 17. We had the kodix 2 deprogrammed and I asked for LNAV after takeoff. Started a left turn per the SID instead of runway heading. When sdq realized what we had done, I thought I heard maintain present heading and 3000 ft. I realized that the heading we were on would take us over the prohibited area and turned north. When things settled down departure said that we had missed the prohibited areda by 4 mi. It was my error. We had copied and read back runway heading and 3000 ft to 10 DME. No problem with communication until departure saw we had turned and got a little excited. What I think lulled me into this was that we had initially planned runway 35 as per ATIS and kodix 2 as per flight plan. We changed runway in FMC, but left the departure. I had briefed that I would use LNAV after takeoff before we were given runway 17. I have no valid excuse for this. Seq departure was concerned with a conflict with a navy aircraft also in their airspace. Supplemental information from acn 564236: crew briefed and planned for the kodix departure procedure off of runway 35, based on our initial fix en route and the ATIS information at sdq. En route clearance was requested 15 mins before pushback, but was not issued until taxi out. The clearance did not mention the kodix departure, but did tell us to expect runway 17 instead of runway 35. We should have flown runway heading. Departure control was talking with a navy aircraft, so we did not establish communications with them until we were heading north and level at 3000 ft. As soon as we established his surprise with our heading, we realized what had happened. There was a navy aircraft in the area whose clearance had to be changed by the controller to avoid a conflict.

Related reports:

Google
 

Original NASA ASRS Text

Title: HDG TRACK DEV BY A B757 FLC DURING THE KODIX 2 DEP PROC FROM MDSD, FO.

Narrative: I COMPLETELY BOTCHED THE DEP OUT OF SDQ. GIVEN RWY HDG TO 3000 FT OFF RWY 17. WE HAD THE KODIX 2 DEPROGRAMMED AND I ASKED FOR LNAV AFTER TKOF. STARTED A L TURN PER THE SID INSTEAD OF RWY HDG. WHEN SDQ REALIZED WHAT WE HAD DONE, I THOUGHT I HEARD MAINTAIN PRESENT HDG AND 3000 FT. I REALIZED THAT THE HDG WE WERE ON WOULD TAKE US OVER THE PROHIBITED AREA AND TURNED N. WHEN THINGS SETTLED DOWN DEP SAID THAT WE HAD MISSED THE PROHIBITED AREDA BY 4 MI. IT WAS MY ERROR. WE HAD COPIED AND READ BACK RWY HDG AND 3000 FT TO 10 DME. NO PROB WITH COM UNTIL DEP SAW WE HAD TURNED AND GOT A LITTLE EXCITED. WHAT I THINK LULLED ME INTO THIS WAS THAT WE HAD INITIALLY PLANNED RWY 35 AS PER ATIS AND KODIX 2 AS PER FLT PLAN. WE CHANGED RWY IN FMC, BUT LEFT THE DEP. I HAD BRIEFED THAT I WOULD USE LNAV AFTER TKOF BEFORE WE WERE GIVEN RWY 17. I HAVE NO VALID EXCUSE FOR THIS. SEQ DEP WAS CONCERNED WITH A CONFLICT WITH A NAVY ACFT ALSO IN THEIR AIRSPACE. SUPPLEMENTAL INFO FROM ACN 564236: CREW BRIEFED AND PLANNED FOR THE KODIX DEP PROC OFF OF RWY 35, BASED ON OUR INITIAL FIX ENRTE AND THE ATIS INFO AT SDQ. ENRTE CLRNC WAS REQUESTED 15 MINS BEFORE PUSHBACK, BUT WAS NOT ISSUED UNTIL TAXI OUT. THE CLRNC DID NOT MENTION THE KODIX DEP, BUT DID TELL US TO EXPECT RWY 17 INSTEAD OF RWY 35. WE SHOULD HAVE FLOWN RWY HDG. DEP CTL WAS TALKING WITH A NAVY ACFT, SO WE DID NOT ESTABLISH COMS WITH THEM UNTIL WE WERE HDG N AND LEVEL AT 3000 FT. AS SOON AS WE ESTABLISHED HIS SURPRISE WITH OUR HDG, WE REALIZED WHAT HAD HAPPENED. THERE WAS A NAVY ACFT IN THE AREA WHOSE CLRNC HAD TO BE CHANGED BY THE CTLR TO AVOID A CONFLICT.

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.