EMB-175 Flight Crew reported a controlled flight into terrain event during a visual approach in which a terrain caution followed by a terrain warning were enunciated. Flying pilot took evasive action to the correct flight path.
Synopsis
EMB-175 Flight Crew reported a controlled flight into terrain event during a visual approach in which a terrain caution followed by a terrain warning were enunciated. Flying pilot took evasive action to the correct flight path.
Narrative
Coming in visual into ZZZ 10000 ft. descending with adequate amount of time and spacing for aircraft configuration to land Runway XX. Flaps 3; gear down on base turn on a left base abeam the ridge peak and with next peek ahead at 7821; our altitude was 6900 and descending through both mountain peaks. Received terrain; pull-up alert all a while maintaining vigilance of terrain. Flaps 5; gear on final approach course around 17 miles from the airport. No other events thereafter. Drawing way points from the runway to aid in my setup and descent planning allowed for an easy descent into ZZZ. Wanting some additional spacing and time to configure is the reasoning of my approach. The alerts were assumed and understood whilst we were being visual the whole time. I; the Captain; was pilot flying on this leg. First time flying into this airport. Suggestion - Provide a RNP visual approach into ZZZ to allow for better planning. Though all was briefed; TERRAIN; TERRAIN; PULL UP was annunciated with terrain in sight; Runway and airport insight.
Second reporter narrative
Aircraft X from ZZZ1 to ZZZ. Visual conditions; visual approach to Runway XX after ZZZZZ on ZZZZZ1 arrival. Captain is a pilot flying. Enroute to ZZZ Captain used FMS to create waypoints using a page X off ZZZ VOR in the FMS for enhanced situational awareness; as there is no published approach procedure to Runway XX (only company pages). Off ZZZZZ; Captain was cleared for visual to Runway XX. Captain asked to start configuring the aircraft. My head was down in the flight deck configuring for landing. After selecting flaps 3; we received a 'caution terrain' aural warning (current altitude at this time 6900 ft). Within 3-5 seconds; the caution alert became a 'terrain terrain; pull up' aural warning. In addition; ATC gave us a low altitude alert. The Captain took corrective action; avoided the terrain; and turned left to align with the final approach course to Runway XX. No company procedures; SOP; or FAA regulations were violated and after landing; no further incidents were noted.New Captain at an unfamiliar high elevation airport and company page Y implies flight through this valley of terrain is procedure/acceptable. Unsure of the Captain's visual approach intention (after the incident). Unsure if intention was to remain higher than terrain; then descend once past terrain; or if the inbound turn to Runway XX was made inadvertently too late. Our path can be seen and understood more easily looking at company page X. I believe we should have turned inbound within 15 NM of the ZZZ VOR; but our actual path was approximately 2 NM East (total of 17 NM out) of the ZZZ VOR. This meant our flight path was East of the noted 6886 ft. elevation on the chart. It was at this position (adjacent to the 6889 ft. at 6900 ft. altitude) that we received the warning and low altitude advisory by ATC. Just passing this elevation is where the Captain took corrective action and turned left to intercept the final visual approach course to Runway XX.Suggest amendment to procedure Y [for] ZZZ. I suggest keeping pilots west of the mountains; no greater than 15nm from the ZZZ VOR as shown in [procedure] Y. However; I would like this to be written in [procedure] X as the explicit guidance would be clear to all crew members. The company procedure allows descent over the mountain side; as stated on bullet point one of Y; and shown with red path line in between terrain. This is not safe for operation.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.