Date: 201907
Local time of day: 0601-1200
Location: AVL.Airport, NC
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C AVL
ATC / advisory: TRACON AVL
Aircraft component: GPWS
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Troubleshooting
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew FLC Overrode Automation
Contributing factors: Human Factors; Aircraft
Primary problem: Human Factors

Narrative: It was the first time going to AVL for both myself and the FO (First Officer) and so we briefed the fact that there were mountains nearby but that we would be visual so it shouldn't be that big of a deal. We got cleared for a visual approach to Runway 35 on a left base around at 5500 ft. I spun in -1500 ft per minute down to 4000 ft for the FAF UMUXE altitude. We leveled at 4000 ft around 5 miles out from UMUXE on a left base. As we leveled ATC issued a low altitude alert. We thought it was odd as we were at the final approach fix altitude and only 4 miles or so now from it. Around 2-3 miles from UMUXE we started getting the EGPWS terrain caution message which I said continue as we were level and could see all obstacles below us. Shortly after the EGPWS terrain warning started to which I said continue because we could still see everything and were level. At this point I disconnected the autopilot to take better control of the aircraft in case we needed to take action. The warning message went away but we kept getting the caution message. I turned on to the localizer and started down the glideslope which we continued getting the terrain caution for a few hundred feet before it finally went away. During this whole event we showed on glide slope altitude on the PFD (Primary Flight Display). AVL is currently working on their main runway and the current Runway 35/17 seems to be temporary so I was wondering if that caused some issue with the EGPWS database not knowing there was an approach there. As I said earlier the terrain caution continued for a while we were on the localizer and glide path. So I wonder if the runway construction played some role in the event. Also; the fact that neither myself nor the FO had been to AVL before played a role in this. The company 10-7 pages do not give too much guidance on the mountainous terrain in the area besides saying that it's there and that high descent rates may result in an EGPWS warning. Nowhere did it warn us that we could get them level and that close to the final approach fix. I think it would aid pilots if the company did something similar to what they did with the 10-7 page for ZZZ and to make sure they get the information on the first page not hiding back on the second page.




Synopsis: CRJ-200 Captain reported receiving a low altitude alert from ATC as well as a terrain alert from the EGPWS but stated they continued because terrain was in sight.