Date: 202010
Local time of day: 1201-1800
Location: AVL.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C AVL
ATC / advisory: Tower AVL
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Confusion
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach
Contributing factors: Airport; Chart Or Publication; Human Factors
Primary problem: Human Factors

Narrative: I read the company e-mail concerning Runway 16 at AVL being closed. At the time I didn't realize I had a trip coming up to go there. During the flight over to AVL; my FO (First Officer) and I looked over the special airport qualification pages for AVL. Pages indicated that the closed Runway 16-34 was completely torn up; and just dirt. I forgot the e-mail I had read that stated that the runway was actually almost finished. It was hazy in the AVL area. I had not landed there in several years; so we decided to do the RNAV approach to Runway 17. I expected to see just one runway as shown on Jeppesen 19-3 chart. We got the airport in sight and the Tower cleared us to land. When fully configured and below 1;000 AGL; Runway 16 was much more prominent than Runway 17. We both thought 16 was 17. Both of [us] saw a small light flash on the runway that looked like an aircraft taxing onto the runway. I saw the flash again; and it looked like a very small 'X'. I reported that to the Tower; and they instructed us to go around; which we did. After talking to the Tower and being vectored back around we saw our error; and successfully landed on Runway 17. I blame myself for not putting the information together and noticing that there was a discrepancy between what the e-mail stated and the Jeppesen charts. It would be nice if Jeppesen could keep their airport qualification charts updated.


Second narrative: We were going to Asheville North Carolina which was my first time going there. I asked the Captain to request the RNAV approach going into Asheville since there were mountains and I'm not familiar with the airport; we have reviewed the special airport on the Jepp chart which was showing one runway and the runway [that] was shown was much torn up and under construction. When we were on final; I noticed there was an X on the runway which I thought was an airplane. I did not see another runway next to it even though there was. But the runway that was next to it; was very small; narrow; short and nothing like the runway [that] was showing on the [Jepp] chart. I realize that's not an airplane on the runway but it was an X flashing. I asked the Captain to let Tower know what's going on. Tower said go around; and after completing the go around procedure Tower has informed us that the main runway is closed and we are supposed to land on the adjacent runway. The adjacent runway is nothing like what was showing on the special airport chart. The picture that was showing in the special report chart is very different than what is in real life. People need to be aware that the predominant runway is not the runway that is used.


Synopsis: Air carrier Flight Crew mistook a runway at AVL Airport under construction as an active runway.