Regional Jet 200 ER/LR (CRJ200)
Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Distraction; Confusion; Situational Awareness
Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Flight Crew Executed Go Around / Missed Approach
Procedure; Human Factors; Airport; ATC Equipment / Nav Facility / Buildings
We were cleared direct on base leg and we called the airport in sight and shot the Visual Approach backed up by the ILS. As we were descending down we noticed the lights on the runway were dim. The approach lights were bright. We cycled the lights but only the approach lights were working. We executed the go around and turned downwind runway. We tried to run numbers for other runways but ACARS was not responding. So landing data was determined on the release. The length showed we could land on the runway. We did a quick brief for the runway. After we landed it seemed that runway was not that wide. We pulled in to the gate and noticed that runway was only 75 feet wide. When we looked up the data on the release it was noticed we pulled the wrong numbers. It started because the runway lights were not working; in the progress of coming back around the release landing data was misread. To avoid this event a better brief could have helped. Both pilots double check the release for data.
[Report narrative contains no additional information].
A CRJ-200 flight crew and dispatcher reported the flight crew landing at a non towered airport executed a missed approach due to the Runway Lights not working and landed on an intersecting runway that was not designated wide enough for their aircraft.