A320
Flight Crew Last 90 Days 200; Flight Crew Total 8000; Flight Crew Type 2000
Other / Unknown; Situational Awareness
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance; Flight Crew Became Reoriented
Human Factors; Airport
Brief; checklist; start; and all phases leading to the incident were in accordance with SOP and no issues. I was the Pilot Flying. Approach had us at 4;000 FT and on a vector to intercept final for Runway 17R at OKC. We reported the field in sight and were cleared for the approach and to contact Tower. I was completely visual at this point and locked onto the PAPI at what turned out to be Runway 17 at Wiley Post. We were in a gentle descent to 2;800 FT (IAF altitude at OKC 17R) when OKC Tower came on frequency and said it looked like we were lined up on Wiley Post; and to climb to 3;000 FT and gave us an appropriate heading. We complied with the instructions and picked up OKC 17R and landed without incident. There were no TCAS RAs/TAs; the aircraft was always in a stable configuration; and there were no additional instructions from the Tower.
Upon reaching 2;800 FT the pilot not flying commented that the ILS DME for Runway 17R still showed 12 NM; but that the runway seemed very close. We then both commented that the ILS glide slope showed low while the VASI showed high.Our company procedure of backing up all approaches with available navaids helped the crew realize something was not right during the approach; but it was the Tower that clarified our visual error.
Cleared for a visual approach to OKC; the flight crew of an A320 mistook PWA for OKC and began a descent to land there. Approach Control noted their track and altitude and brought the error to their attention.