Heading track deviation after a clearance interpretation problem.

Attributes
ACN	305070
Time
Date	199505
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bwi
State Reference	MD
Altitude	msl bound lower : 10000 msl bound upper : 10000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zdc
Operator	general aviation : corporate
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Operating Under FAR Part	Part 91
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	Other
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : cfi pilot : instrument
Experience	flight time last 90 days : 50 flight time total : 1200 flight time type : 50
ASRS Report	305070
Person 2
Affiliation	Other
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	inflight encounter : weather non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact other
Consequence	faa : reviewed incident with flight crew
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

During the initial climb out of bwi, a heading deviation was requested per my command by the PNF. He stated to the center 'north-number requests deviations to the right for WX.' as he finished the sentence, I corrected his misstatement over the intercom which he tagged onto this transmission 'correction to the left for WX.' center responded approved as requested. Mins later, center questioned why we are flying the current heading. We responded that we were still deviating to the left of course for WX. Center stated that we had asked for deviations in the opposite direction. I believe the mistake would not have occurred if, when the PNF misspoke, we had restated our request in the correct manner. Instead, it is obvious that either of 2 things occurred: first, the controller didn't listen to the PNF's correction, or second, the correction was blocked.

Original NASA ASRS Text

Title: HDG TRACK DEV AFTER A CLRNC INTERP PROB.

Narrative: DURING THE INITIAL CLBOUT OF BWI, A HDG DEV WAS REQUESTED PER MY COMMAND BY THE PNF. HE STATED TO THE CTR 'N-NUMBER REQUESTS DEVS TO THE R FOR WX.' AS HE FINISHED THE SENTENCE, I CORRECTED HIS MISSTATEMENT OVER THE INTERCOM WHICH HE TAGGED ONTO THIS XMISSION 'CORRECTION TO THE L FOR WX.' CTR RESPONDED APPROVED AS REQUESTED. MINS LATER, CTR QUESTIONED WHY WE ARE FLYING THE CURRENT HDG. WE RESPONDED THAT WE WERE STILL DEVIATING TO THE L OF COURSE FOR WX. CTR STATED THAT WE HAD ASKED FOR DEVS IN THE OPPOSITE DIRECTION. I BELIEVE THE MISTAKE WOULD NOT HAVE OCCURRED IF, WHEN THE PNF MISSPOKE, WE HAD RESTATED OUR REQUEST IN THE CORRECT MANNER. INSTEAD, IT IS OBVIOUS THAT EITHER OF 2 THINGS OCCURRED: FIRST, THE CTLR DIDN'T LISTEN TO THE PNF'S CORRECTION, OR SECOND, THE CORRECTION WAS BLOCKED.

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.