2022-04 · NASA ASRS report 1893014
Air Carrier flight crew reported a CFIT situation due in part by an ATC assigned extended downwind vector in mountainous terrain area. As the flight crew were discussing altitude concerns ATC issued a low altitude alert and assigned a climb and heading correction. Flight crew complied expeditiously and continued to a safe landing.
On the final segment of the HHOOD4 STAR; Runway 10L transition at 3;000 ft.; we were about 5nm west of the last waypoint; NNUTT; on the published track. This area has rising terrain to the west. We were given a low altitude alert from ATC; with a climb to 3;500 ft.; and a left turn to a heading of 160 I believe. We executed the instructions and continued the approach to land on 10L after receiving a visual approach clearance shortly after the turn.It seemed like a long downwind since there was little traffic in the area. The FO (First Officer)/ PF (Pilot Flying) mentioned that he didn't like the look of the hills rising ahead. I agreed and added that our terrain display showed only green ahead. Because it was night; we could not make out the terrain clearly; but we were becoming uneasy. We both agreed it was time to check on our base vector when ATC gave us the low altitude alert; climb; and turn. In retrospect; I feel that I should have asked about the base turn earlier. It didn't make sense that we should be on such a long downwind; when it appeared we were number 1 for the runway. I was biased towards believing there was a reasonable explanation; rather than it being in error.
While conducting the JKNOX.HOOD4 arrival into PDX at night for Runway 10L ATC descended us to 3;000 ft. in the vicinity of NNUTT intersection. Beyond NNUTT on a heading of 278 at 3;000 ft. with flaps 2 in LNAV/ALT HOLD the flight crew noticed and discussed mountainous terrain ahead of the aircraft with increasing urgency. FO (First Officer)/PF (Pilot Flying) commented on the rising terrain ahead of the aircraft. CA (Captain)/PM (Pilot Monitoring) commented that he expected a turn toward the final approach course already and thought we were extending our downwind too far. FO/PF said; I want to turn"; and seconds later ATC instructed us to climb immediately to 3;500 and turn left approximately 90 degrees. CA/PM set MCP altitude to 3;500 and FO/PF pressed altitude intervene. CA/PM suggested turning off automation and FO/PF immediately clicked off the autopilot and autothrottles; and advanced the throttles smartly to initiate a climbing turn while the CA/PM selected HSEL and adjusted the heading bug to the assigned heading. ATC issued a low altitude alert and advised that the MVA in the area was 3;500 ft. FO/PF briefly leveled at 3;500 ft.; then continued the climb to 4;000 ft. due to concerns about terrain. ATC thanked us for the prompt response to their climb instructions; vectored us further left to a heading of 130; and cleared us for the visual approach Runway 10L. Flight crew conducted a normal visual approach with ILS backup without automation. While handing us off to Tower; the controller thanked us again."
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.