Orf approach controller issues a confusing clearance to the crew of a DHC8 landing orf.

Attributes
ACN	572882
Time
Date	200301
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : orf.airport
State Reference	VA
Altitude	msl single value : 2000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : orf.tracon
Operator	common carrier : air carrier
Make Model Name	Dash 8-200
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 23 other other vortac
Flight Phase	descent : approach
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 12000 flight time type : 4000
ASRS Report	572882
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : far non adherence : published procedure other spatial deviation
Independent Detector	other controllera other flight crewa other flight crewb
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Ambiguous

Narrative:

Proceeding to a fix (which we were cleared to by previous approach controller), located on the ILS runway 23 orf, final approach controller gave an 'expect vectors to cross the final approach course' instruction. Upon reaching the assigned fix, with no heading or vector issued by the approach controller, proceeded to turn inbound to next fix along route. Soon after commencing turn, approach controller asked what our heading was. Informed approach controller heading of 230 degrees. Approach controller then issued new heading off of final approach course and stated that he had not authority/authorized turn onto final approach course. Told controller that he had only issued an 'expect vectors to cross final approach course,' and that since no other instructions or clrncs were issued by him before arriving at fix to which cleared, that our next fix was on the final approach course, ILS runway 23 orf. Conclusion: an 'expert' clearance is not authority/authorized to carry out the anticipated action, but simply to 'expect' it. If anticipated clearance is not given by the controller, next course of action is to continue on previously assigned clearance. Additional actions: before arrival at fix, controller could have been questioned by flight crew as to his intent after the fix.

Original NASA ASRS Text

Title: ORF APCH CTLR ISSUES A CONFUSING CLRNC TO THE CREW OF A DHC8 LNDG ORF.

Narrative: PROCEEDING TO A FIX (WHICH WE WERE CLRED TO BY PREVIOUS APCH CTLR), LOCATED ON THE ILS RWY 23 ORF, FINAL APCH CTLR GAVE AN 'EXPECT VECTORS TO CROSS THE FINAL APCH COURSE' INSTRUCTION. UPON REACHING THE ASSIGNED FIX, WITH NO HDG OR VECTOR ISSUED BY THE APCH CTLR, PROCEEDED TO TURN INBOUND TO NEXT FIX ALONG RTE. SOON AFTER COMMENCING TURN, APCH CTLR ASKED WHAT OUR HDG WAS. INFORMED APCH CTLR HDG OF 230 DEGS. APCH CTLR THEN ISSUED NEW HDG OFF OF FINAL APCH COURSE AND STATED THAT HE HAD NOT AUTH TURN ONTO FINAL APCH COURSE. TOLD CTLR THAT HE HAD ONLY ISSUED AN 'EXPECT VECTORS TO CROSS FINAL APCH COURSE,' AND THAT SINCE NO OTHER INSTRUCTIONS OR CLRNCS WERE ISSUED BY HIM BEFORE ARRIVING AT FIX TO WHICH CLRED, THAT OUR NEXT FIX WAS ON THE FINAL APCH COURSE, ILS RWY 23 ORF. CONCLUSION: AN 'EXPERT' CLRNC IS NOT AUTH TO CARRY OUT THE ANTICIPATED ACTION, BUT SIMPLY TO 'EXPECT' IT. IF ANTICIPATED CLRNC IS NOT GIVEN BY THE CTLR, NEXT COURSE OF ACTION IS TO CONTINUE ON PREVIOUSLY ASSIGNED CLRNC. ADDITIONAL ACTIONS: BEFORE ARR AT FIX, CTLR COULD HAVE BEEN QUESTIONED BY FLC AS TO HIS INTENT AFTER THE FIX.

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.