Air carrier mdt track heading deviation.

Attributes
ACN	148246
Time
Date	199006
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : btg airport : pdx
State Reference	WA
Altitude	msl bound lower : 13000 msl bound upper : 13000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Transport, Low Wing, 2 Turboprop Eng
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors enroute airway : j1 enroute airway : v23
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 80 flight time total : 3000
ASRS Report	148246
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : far non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Departed 10L at pdx and contacted pdx departure. We were instructed to turn right 210 degrees, intercept 'the arwy.' being in the mdt, we were filed J1 to mfr (btf right 163). Now that we were established on BT6 right 163, departure told us that we were on the mokee arrival and to turn right 240 degrees to intercept V23. Confused and unclear of the instruction, the captain and I questioned it. Departure controller responded with a turn to 240 degrees for the intercept of V23. Again unsure that the controller was actually meaning us, we verified we were en route to mfr and not inbound to pdx (which is the mokee 2 arrival). Another controller told us to make an immediate right turn to 250 degrees (he must have been supervisor controller). We complied, intercept V23 (btg right 175) and proceeded to mfr. When handed off to ZSE we verified our route filed. He told us V23 and that he showed us as an light transport. What caused the problem/misunderstanding was the changed flight plan with the equipment change scheduled for this route. Our company operates both aircraft on that route and have made recent changes. This could be prevented by more alertness by controllers and crews.

Original NASA ASRS Text

Title: ACR MDT TRACK HEADING DEVIATION.

Narrative: DEPARTED 10L AT PDX AND CONTACTED PDX DEP. WE WERE INSTRUCTED TO TURN RIGHT 210 DEGS, INTERCEPT 'THE ARWY.' BEING IN THE MDT, WE WERE FILED J1 TO MFR (BTF R 163). NOW THAT WE WERE ESTABLISHED ON BT6 R 163, DEP TOLD US THAT WE WERE ON THE MOKEE ARR AND TO TURN RIGHT 240 DEGS TO INTERCEPT V23. CONFUSED AND UNCLEAR OF THE INSTRUCTION, THE CAPT AND I QUESTIONED IT. DEP CTLR RESPONDED WITH A TURN TO 240 DEGS FOR THE INTERCEPT OF V23. AGAIN UNSURE THAT THE CTLR WAS ACTUALLY MEANING US, WE VERIFIED WE WERE ENRTE TO MFR AND NOT INBND TO PDX (WHICH IS THE MOKEE 2 ARR). ANOTHER CTLR TOLD US TO MAKE AN IMMEDIATE RIGHT TURN TO 250 DEGS (HE MUST HAVE BEEN SUPVR CTLR). WE COMPLIED, INTERCEPT V23 (BTG R 175) AND PROCEEDED TO MFR. WHEN HANDED OFF TO ZSE WE VERIFIED OUR RTE FILED. HE TOLD US V23 AND THAT HE SHOWED US AS AN LTT. WHAT CAUSED THE PROB/MISUNDERSTANDING WAS THE CHANGED FLT PLAN WITH THE EQUIP CHANGE SCHEDULED FOR THIS RTE. OUR COMPANY OPERATES BOTH ACFT ON THAT RTE AND HAVE MADE RECENT CHANGES. THIS COULD BE PREVENTED BY MORE ALERTNESS BY CTLRS AND CREWS.

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.