B190 flight crew cleared for visual approach and conduct flight to wrong runway.

Attributes
ACN	441460
Time
Date	199906
Day	Sun
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : ric.airport
State Reference	VA
Altitude	msl single value : 2000
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : ric.tracon
Operator	common carrier : air carrier
Make Model Name	Beech 1900
Operating Under FAR Part	Part 135
Navigation In Use	other vortac
Flight Phase	descent : approach
Route In Use	approach : visual arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : instrument pilot : multi engine pilot : atp
Experience	flight time last 90 days : 120 flight time total : 1700 flight time type : 650
ASRS Report	441460
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : multi engine pilot : instrument pilot : commercial pilot : cfi
Experience	flight time last 90 days : 120 flight time total : 1200 flight time type : 120
ASRS Report	441077
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance controller : issued advisory flight crew : executed go around flight crew : became reoriented
Supplementary
Problem Areas	Airport Flight Crew Human Performance Environmental Factor
Primary Problem	Flight Crew Human Performance

Narrative:

We (aircraft X) were given a heading to fly and asked to report the field in sight. I called a runway in sight at our 1 O'clock position. Approach cleared us for the visual and told us to contact tower. We turned towards the runway on a right dogleg. We contacted tower and were cleared to land runway 20. At about a 2 or 3 mi final, we noticed that the VOR approach we were using to back up the approach was not ctring. We then looked at our heading of approximately 160 degrees and decided we were lined up for the wrong runway. I called tower and they said it looked like we were lined up for runway 16 and told us we were cleared to land runway 16 if we'd like. Because of the confusion we were not configured completely for landing, so I made the decision to go around. They gave us radar vectors to runway 20 and we landed uneventfully. As I look back, I'm not going to be accepting visual approachs at night unless I can back it up with an ILS. I also should have made the decision to go around as soon as things didn't look quite right.

Original NASA ASRS Text

Title: B190 FLC CLRED FOR VISUAL APCH AND CONDUCT FLT TO WRONG RWY.

Narrative: WE (ACFT X) WERE GIVEN A HDG TO FLY AND ASKED TO RPT THE FIELD IN SIGHT. I CALLED A RWY IN SIGHT AT OUR 1 O'CLOCK POS. APCH CLRED US FOR THE VISUAL AND TOLD US TO CONTACT TWR. WE TURNED TOWARDS THE RWY ON A R DOGLEG. WE CONTACTED TWR AND WERE CLRED TO LAND RWY 20. AT ABOUT A 2 OR 3 MI FINAL, WE NOTICED THAT THE VOR APCH WE WERE USING TO BACK UP THE APCH WAS NOT CTRING. WE THEN LOOKED AT OUR HDG OF APPROX 160 DEGS AND DECIDED WE WERE LINED UP FOR THE WRONG RWY. I CALLED TWR AND THEY SAID IT LOOKED LIKE WE WERE LINED UP FOR RWY 16 AND TOLD US WE WERE CLRED TO LAND RWY 16 IF WE'D LIKE. BECAUSE OF THE CONFUSION WE WERE NOT CONFIGURED COMPLETELY FOR LNDG, SO I MADE THE DECISION TO GO AROUND. THEY GAVE US RADAR VECTORS TO RWY 20 AND WE LANDED UNEVENTFULLY. AS I LOOK BACK, I'M NOT GOING TO BE ACCEPTING VISUAL APCHS AT NIGHT UNLESS I CAN BACK IT UP WITH AN ILS. I ALSO SHOULD HAVE MADE THE DECISION TO GO AROUND AS SOON AS THINGS DIDN'T LOOK QUITE RIGHT.

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.