Date: 201710
Local time of day: 1801-2400
Location: RIC.Airport, VA
Flight conditions: VMC
Light: Night
Aircraft: Embraer Jet Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C RIC
ATC / advisory: Tower RIC
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Aircraft was being vectored for a night visual approach to Runway 20 at RIC. Captain was PF; I was PM. We flew the DUCXS arrival. Vectoring began IVO NEAVL intersection; roughly 20 NM from airport. We were using the RNAV Z Runway 20 as an instrument procedure reference during the approach. We were vectored for a wide right downwind; roughly 10 NM West of field and given a descent to 2000. Once established at 2000 and abeam the airfield we were vectored toward FOBON; the FAF for RNAV Runway 20; [on] a heading of approximately 070. Based on this approach angle to FOBON we anticipated the corner would be cut so we fully configured the aircraft for landing. About 5 miles SSW of FOBON we were asked if we had field in sight. At that point I could clearly see the Runway 16 lighting system and the terminal area and pointed this out to the PF. He said to report field in sight; which I did. We were immediately cleared for the visual 20. He began a descent and started a right turn to intercept the Final Approach Course (FAC). During the turn to intercept the captain turned past the 202 inbound course to about a 230 heading without ever intercepting the final approach course. He appeared to be lining up for Runway 16; which had a MALSR and was more brightly lit than Runway 16.I immediately advised the Captain he was far right of course and needed to come well left. He immediately turned back toward the Runway 20 FAC. I asked him to level off which he did at 1000 feet. At that point I was able to verbally guide the PF toward the FAC and reestablish the aircraft on a stable glide path. Just as we were reestablishing ourselves on the FAC; ATC called to report she just received a low altitude alert on our aircraft.I acknowledged her call and we elected to continue as by this point we were level; on course and about to restart our descent on glide path. I called 1000 configured to the Captain and we began our descent. Shortly thereafter the Captain commented that he felt like he had black hole illusion. Since we were configured and stable I immediately gave distance and altitude callouts to the runway; which the Captain felt was helpful. We continued the approach to a normal landing.I think if we had discussed the runway and lighting configuration in more detail; to include potential visual illusions and lack of other visual references; it would have ensured a better common operating picture between me and the Captain. This would have reduced the risk of the Captain attempting to line up on the incorrect runway. Although we were already correcting when we received the ATC alert; the safest and most conservative action at that moment would have been to conduct a go-around.




Synopsis: ERJ First Officer reported they received a low altitude alert from ATC on a night visual approach to RIC.