A300 on functional check flight lines up with wrong runway on approach.

Attributes
ACN	304760
Time
Date	199505
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : jfk
State Reference	NY
Altitude	msl bound lower : 2000 msl bound upper : 2000
Environment
Flight Conditions	Mixed
Light	Dusk
Aircraft 1
Controlling Facilities	tracon : n90
Operator	common carrier : air carrier
Make Model Name	A300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent : approach
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : atp
Experience	flight time last 90 days : 110 flight time total : 4300 flight time type : 1300
ASRS Report	304760
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	other controllera
Resolutory Action	flight crew : became reoriented flight crew : returned to intended course or assigned course other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Flight functional check flight on airbus A300-600ER from jfk to jfk. We were returning to jfk to land on runway 31R. We had the approach set up in the FMC for runway 31R. The first officer's FMC was inoperative as it failed in-flight. The standard awareness items were briefed for the approach. However, the crew still had ILS for runway 31L in the ILS selection window. We had departed off of runway 31L when we left jfk and failed to change the frequency to runway 31R. Our first indication that we knew something was wrong was when approach control informed us we intercepted the runway 31L localizer after having been cleared for the runway 31R ILS approach. We immediately corrected back to the runway 31R localizer and landed uneventfully. The approach controller was very nice about the whole thing and there were no traffic conflicts. Since the WX was better than 1500 ft and 3 NM there was no company requirement to brief the approach. However, we briefed the approach but neglected to brief the localizer frequency. That was the biggest mistake I can discern.

Original NASA ASRS Text

Title: A300 ON FUNCTIONAL CHK FLT LINES UP WITH WRONG RWY ON APCH.

Narrative: FLT FUNCTIONAL CHK FLT ON AIRBUS A300-600ER FROM JFK TO JFK. WE WERE RETURNING TO JFK TO LAND ON RWY 31R. WE HAD THE APCH SET UP IN THE FMC FOR RWY 31R. THE FO'S FMC WAS INOP AS IT FAILED INFLT. THE STANDARD AWARENESS ITEMS WERE BRIEFED FOR THE APCH. HOWEVER, THE CREW STILL HAD ILS FOR RWY 31L IN THE ILS SELECTION WINDOW. WE HAD DEPARTED OFF OF RWY 31L WHEN WE LEFT JFK AND FAILED TO CHANGE THE FREQ TO RWY 31R. OUR FIRST INDICATION THAT WE KNEW SOMETHING WAS WRONG WAS WHEN APCH CTL INFORMED US WE INTERCEPTED THE RWY 31L LOC AFTER HAVING BEEN CLRED FOR THE RWY 31R ILS APCH. WE IMMEDIATELY CORRECTED BACK TO THE RWY 31R LOC AND LANDED UNEVENTFULLY. THE APCH CTLR WAS VERY NICE ABOUT THE WHOLE THING AND THERE WERE NO TFC CONFLICTS. SINCE THE WX WAS BETTER THAN 1500 FT AND 3 NM THERE WAS NO COMPANY REQUIREMENT TO BRIEF THE APCH. HOWEVER, WE BRIEFED THE APCH BUT NEGLECTED TO BRIEF THE LOC FREQ. THAT WAS THE BIGGEST MISTAKE I CAN DISCERN.

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.