E120 crew had track deviation in ZOB class east.

Attributes
ACN	466620
Time
Date	200003
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : zob.artcc
State Reference	OH
Altitude	msl bound lower : 11000 msl bound upper : 12000
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zob.artcc tower : mli.tower
Operator	common carrier : air carrier
Make Model Name	Brasilia EMB-120 All Series
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Route In Use	enroute : direct
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : atp pilot : cfi pilot : multi engine
Experience	flight time last 90 days : 55 flight time total : 1950 flight time type : 55
ASRS Report	466620
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : multi engine pilot : commercial
Events
Anomaly	non adherence : clearance non adherence : published procedure non adherence : company policies other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued advisory controller : issued new clearance
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

This was a routine flight from cle to cmh. The route of flight on the flight plan was cleveland to mansfield VOR to appleton VOR to columbus. While on the ground the first officer preselected the 2 VOR frequencys on the navigation radios. He inadvertently selected 117.5 for appleton and I concurred with this frequency when I called 'radios set.' in-flight, before reaching mansfield VOR we were cleared direct to appleton. We flipped the preselect switch and started tracking to rosewood VOR assuming it was appleton. A short while later we were given a turn to 160 degrees. When we questioned why, we were told we had already passed mansfield. Then we realized appleton was south of us, not southwest, and that we had been tracking to the wrong VOR due to an incorrect (but often used) frequency. I believe 3 things could prevent a reoccurrence of the situation: 1) always verify frequencys by referencing them on the chart, 2) having a better situational awareness of the approximately direction of our next fix, and 3) verify the new VOR on the EFIS display 3 letter identifier or using aural morse code.

Original NASA ASRS Text

Title: E120 CREW HAD TRACK DEV IN ZOB CLASS E.

Narrative: THIS WAS A ROUTINE FLT FROM CLE TO CMH. THE RTE OF FLT ON THE FLT PLAN WAS CLEVELAND TO MANSFIELD VOR TO APPLETON VOR TO COLUMBUS. WHILE ON THE GND THE FO PRESELECTED THE 2 VOR FREQS ON THE NAV RADIOS. HE INADVERTENTLY SELECTED 117.5 FOR APPLETON AND I CONCURRED WITH THIS FREQ WHEN I CALLED 'RADIOS SET.' INFLT, BEFORE REACHING MANSFIELD VOR WE WERE CLRED DIRECT TO APPLETON. WE FLIPPED THE PRESELECT SWITCH AND STARTED TRACKING TO ROSEWOOD VOR ASSUMING IT WAS APPLETON. A SHORT WHILE LATER WE WERE GIVEN A TURN TO 160 DEGS. WHEN WE QUESTIONED WHY, WE WERE TOLD WE HAD ALREADY PASSED MANSFIELD. THEN WE REALIZED APPLETON WAS S OF US, NOT SW, AND THAT WE HAD BEEN TRACKING TO THE WRONG VOR DUE TO AN INCORRECT (BUT OFTEN USED) FREQ. I BELIEVE 3 THINGS COULD PREVENT A REOCCURRENCE OF THE SIT: 1) ALWAYS VERIFY FREQS BY REFING THEM ON THE CHART, 2) HAVING A BETTER SITUATIONAL AWARENESS OF THE APPROX DIRECTION OF OUR NEXT FIX, AND 3) VERIFY THE NEW VOR ON THE EFIS DISPLAY 3 LETTER IDENTIFIER OR USING AURAL MORSE CODE.

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.