MD80 captain did not fly controller assigned headings.

Attributes
ACN	420440
Time
Date	199811
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : ott airport : dca
State Reference	MD
Altitude	msl bound lower : 14000 msl bound upper : 14000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	departure other enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 180 flight time total : 19800 flight time type : 80
ASRS Report	420440
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After takeoff from dca to the northwest, we were tracking the dca 328 degree radial. After having been given a left turn to 150 degrees, I inadvertently selected a heading of 170 degrees instead to intercept the ott 184 degree radial (because the selection of 150 degrees would have commanded a right turn on the autoplt instead of the left turn we were cleared to make). I failed to reset the heading to 150 degrees and we subsequently rolled out on a 170 degree heading (instead of 150 degrees). The controller later wondered why we were flying a 170 degree heading instead of 150 degrees (which would not intercept the ott 184 degree radial). He then turned us left to 090 degrees to intercept. He seemed annoyed at our mistake. I have learned that a turn on the autoplt of near 180 degrees can cause a problem like this if I don't establish the correct heading soon after turning somewhat. There was no conflict with traffic, and we eventually intercepted our radial and continued our climb to altitude. The controller switched us to a new frequency and nothing more was said. I'm new to the MD80 and learned a valuable lesson here.

Original NASA ASRS Text

Title: MD80 CAPT DID NOT FLY CTLR ASSIGNED HDGS.

Narrative: AFTER TKOF FROM DCA TO THE NW, WE WERE TRACKING THE DCA 328 DEG RADIAL. AFTER HAVING BEEN GIVEN A L TURN TO 150 DEGS, I INADVERTENTLY SELECTED A HDG OF 170 DEGS INSTEAD TO INTERCEPT THE OTT 184 DEG RADIAL (BECAUSE THE SELECTION OF 150 DEGS WOULD HAVE COMMANDED A R TURN ON THE AUTOPLT INSTEAD OF THE L TURN WE WERE CLRED TO MAKE). I FAILED TO RESET THE HDG TO 150 DEGS AND WE SUBSEQUENTLY ROLLED OUT ON A 170 DEG HDG (INSTEAD OF 150 DEGS). THE CTLR LATER WONDERED WHY WE WERE FLYING A 170 DEG HDG INSTEAD OF 150 DEGS (WHICH WOULD NOT INTERCEPT THE OTT 184 DEG RADIAL). HE THEN TURNED US L TO 090 DEGS TO INTERCEPT. HE SEEMED ANNOYED AT OUR MISTAKE. I HAVE LEARNED THAT A TURN ON THE AUTOPLT OF NEAR 180 DEGS CAN CAUSE A PROB LIKE THIS IF I DON'T ESTABLISH THE CORRECT HDG SOON AFTER TURNING SOMEWHAT. THERE WAS NO CONFLICT WITH TFC, AND WE EVENTUALLY INTERCEPTED OUR RADIAL AND CONTINUED OUR CLB TO ALT. THE CTLR SWITCHED US TO A NEW FREQ AND NOTHING MORE WAS SAID. I'M NEW TO THE MD80 AND LEARNED A VALUABLE LESSON HERE.

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.