Used wrong VOR to set intersection intercept.

Attributes
ACN	186629
Time
Date	199108
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : roc
State Reference	NY
Altitude	msl bound lower : 8000 msl bound upper : 8000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : intermediate altitude
Route In Use	enroute : on vectors enroute airway : roc
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 15000
ASRS Report	186629
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : commercial
Events
Anomaly	non adherence : clearance 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:

Our clearance was a turn to 100 degree after takeoff on runway 22, to intercept V34 to the beeps intersection. Several mins after the vector to intercept was issued, the controller 'nicely' advised us that we were slightly north of the airway. We corrected immediately! (No conflict). On our pre-departure briefing, I had briefed the radial off of the buffalo VOR, making up the 'beeps' intersection. This was incorrect, but the first officer missed my error. I was 'asleep at the switch' and very embarrassed! I usually doublechk the chart, on the ground, and again in the air, because it's easy to 'misread' a chart. I do multiple checks for this very reason. As for my first officer, he will probably look at what I have set in for course information from now on! Coming off of vacation, I was not as 'crisp' as I usually like to be. A continuing lesson: pay attention -- if something can go wrong, it will. Always be vigilant!

Original NASA ASRS Text

Title: USED WRONG VOR TO SET INTXN INTERCEPT.

Narrative: OUR CLRNC WAS A TURN TO 100 DEG AFTER TKOF ON RWY 22, TO INTERCEPT V34 TO THE BEEPS INTXN. SEVERAL MINS AFTER THE VECTOR TO INTERCEPT WAS ISSUED, THE CTLR 'NICELY' ADVISED US THAT WE WERE SLIGHTLY N OF THE AIRWAY. WE CORRECTED IMMEDIATELY! (NO CONFLICT). ON OUR PRE-DEP BRIEFING, I HAD BRIEFED THE RADIAL OFF OF THE BUFFALO VOR, MAKING UP THE 'BEEPS' INTXN. THIS WAS INCORRECT, BUT THE FO MISSED MY ERROR. I WAS 'ASLEEP AT THE SWITCH' AND VERY EMBARRASSED! I USUALLY DOUBLECHK THE CHART, ON THE GND, AND AGAIN IN THE AIR, BECAUSE IT'S EASY TO 'MISREAD' A CHART. I DO MULTIPLE CHKS FOR THIS VERY REASON. AS FOR MY FO, HE WILL PROBABLY LOOK AT WHAT I HAVE SET IN FOR COURSE INFO FROM NOW ON! COMING OFF OF VACATION, I WAS NOT AS 'CRISP' AS I USUALLY LIKE TO BE. A CONTINUING LESSON: PAY ATTN -- IF SOMETHING CAN GO WRONG, IT WILL. ALWAYS BE VIGILANT!

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.