Date: 201511
Local time of day: 1201-1800
Location: PIT.Airport, PA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Hawker Horizon (Raytheon)
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B PIT
ATC / advisory: Tower PIT
Reporter organization: Corporate
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors
Primary problem: Human Factors

Narrative: I was the pilot flying during a clear night visual approach to Greater Pittsburgh Airport. We were at 6;000 feet when approach asked if we saw the airport at our 10 o'clock position. When I looked out the window; I saw what I believed to be the lights for runway 32. It was located within the airport boundaries in about the correct orientation so I shifted my attention inside the cockpit to begin configuring the aircraft for the approach. I needed to slow down and descend to 3;000 feet from 6;000 feet for my base to final turn. We extended the speedbrakes then flaps and gear to get down to the correct altitude and airspeed. Once this was accomplished; I directed my attention back outside the aircraft to start my base to final turn towards the runway. As I visually lined up with the runway it quickly became apparent to me that something was wrong. We always back up visual approaches with the instrument approach for that runway and things just did not line up correctly with the ILS for runway 32. At that point; I told the pilot not flying that our current approach was not correct and we were breaking off to the right so to line up with the ILS and FMS picture. Just then; PIT tower asked if there was some confusion and to turn right to reposition for runway 32. They turned up the runway 32 lights so that we could clearly see the correct runway. At no time were we in conflict with any other aircraft or in close proximity to the ground. After an uneventful landing; I called Pittsburgh TRACON on the phone to discuss the incident. He said it looked like we aligned our approach with the Tango taxiway lights which are always full bright with a greenish tint. Apparently; Ground has no control over their brightness. As I look back; I do recall the lights l saw display a greenish tint. One would think that this mistaken identity would be difficult to make at an airport we utilize frequently. But in the rush to lose altitude and airspeed; that quick glance at those greenish lights sure did have me convinced that I saw the runway. Having the ILS tuned and displayed via our FMS as a backup sure helped us to quickly realize our mistake. It is also comforting to know that the PIT Approach and Tower personnel were watching our back to correct any error quickly.


Second narrative: [Report narrative contained no additional information.]


Synopsis: Hawker 4000 flight crew reported lining up with Taxiway T instead of Runway 32 at PIT because the taxiway lights were on bright.