Date: 201810
Local time of day: 0001-0600
Location: EUG.Airport, OR
Flight conditions: VMC
Light: Night
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E EUG
ATC / advisory: Tower EUG
Reporter organization: Air Carrier
Reporter function: Pilot Flying; First Officer
Reporter qualification: Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument
Human factors: Confusion
Second reporter function: Captain; Pilot Not Flying
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Human Factors; Procedure
Primary problem: Ambiguous

Narrative: It was my first time flying into KEUG and I was the pilot flying. The weather was VMC and we setup for the Visual to 16R backed up by the ILS. I briefed the full approach including the MSA. We were at 4000 approximately 15 miles NE of the field and I told the Captain I had the airport in sight. He advised ATC and we were cleared for the visual approach and handed off to the tower. The Captain set 2000 for the FAF altitude and I turned the aircraft towards the FAF. The autopilot was on in HDG SEL and ALT HOLD at a speed of 240. I set a vertical speed of approximately 800 FPM and set the speed to 210 and asked for flaps 1 and 5. The green arc on the ND was aligned with the crossing the FAF at 2000 as published. The Captain verbally stated that the terrain was rising off the left side of the aircraft. We both had terrain turned on and I checked the ND and only saw green dots but I believe that it was the old version that doesn't give terrain height information. At that moment the GPWS went off saying Terrain Terrain Pull Up. My first reaction was to look at the ND and look outside and I didn't see any terrain and the airport was still in sight. After the second GPWS alert; the Captain said pull up and I disconnected the autopilot and autothrottles and pitched the aircraft up while adding power. We were maybe at 3700 feet and after the recovery we were back at 4000 and the GPWS instantly stopped. We leveled off at 4000 and I slowed the aircraft down again and we continued the visual approach to a successful landing in Eugene. ATC never mentioned our low altitude or proximity to the terrain.


Second narrative: Night VMC visual approach left base leg into EUG Runway 16R; we called field insight and Cascade Approach cleared us for the visual and handed us off to EUG Tower. I set FAF altitude of 2000 in the MCP window the FO (First Officer) selected V/S and heading select. I noticed terrain blocking some city lights and mentioned that looks scary. The terrain map was showing some green texture. Then the GPWS called terrain terrain; Pull up; I repeated pull up the FO disconnected the AP and AT checked speed brake stowed and pulled up. The GPWS Aural warning stopped and we continued for an uneventful landing. We checked with the flight attendants and they said they were in their seats ok but wondered about the pull up. After landing I called Cascade Approach and asked what they had seen. The controller told me that he saw a low altitude alert after the handoff.


Synopsis: Air carrier flight crew reported receiving a Terrain warning while on a night visual approach to EUG.