A crj-200 flight crew and dispatcher reported the flight crew landing at a non towered airport execu...

Attributes
ACN	1669075
Time
Date	201907
Local Time Of Day	0001-0600
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Other Missed Approach
Flight Plan	IFR
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Person 2
Function	Pilot Flying Captain
Qualification	Flight Crew Multiengine Flight Crew Instrument Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural Published Material / Policy Ground Event / Encounter Other / Unknown

Narrative:

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.

Original NASA ASRS Text

Title: 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.

Narrative: 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.

Data retrieved from NASA's ASRS site 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.

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.