2023-06 · NASA ASRS report 2008891
A319 flight crew reported a CFIT advisory from ATC. The pilots reported they were given a late runway change; in a mountainous area; turbulent conditions; encountering a tailwind and given a ninety degree turn to final. The approach became unstable and the crew stated they executed a missed approach.
As we were descending on the ZZZZZ RNAV arrival; ZZZ Approach advised us that ZZZ airport would be changing from landing South to landing North and to expect the visual approach to Runway XXR. Shortly thereafter; we were given a left turn off of the arrival; which established us on a right base to Runway XXR. We were vectored directly through cumulous build ups and this made installing the runway and verifying the approach challenging through the turbulence. Time was also a factor because the vector was close to the final approach. As we were established on base; ZZZ advised us that the airport was at 3 o'clock and 20 miles; so I asked the First Officer to inform ZZZ that we were IMC and in and out of the cloud bases. ZZZ then cleared us for the approach and asked us to maintain 11;000 ft. until established. I armed the approach; but the autopilot did not capture the course due to either being too close to the approach course or over it. At approximately the same time we encountered visual conditions; so I disconnected the autopilot and made a right turn back to the airport and final approach course. We transitioned to the visual approach and began descending for the next final approach course fix; ZZZZZ1; which had a crossing altitude of 9;900 ft. ZZZ advised us that we were showing a low altitude alert. Although we were visual; we stopped the descent to ensure that we were not missing anything. We had no visual or oral GPWS indications as well as visual conditions of our course and the airport. We verified that we were clear of all terrain and continued the approach visually. This; coupled with a tailwind at altitude; left us high over ZZZZZ1 and the remainder of the approach.I slowed and configured the aircraft with gear; flap; and speed brakes. ZZZ switched us to ZZZ Tower. ZZZ Tower cleared us to land and we requested S-turns on final to lose altitude. We performed an S-turn to the West and returned to the final course still too high to make a stabilized approach and landing. At this point we performed a go around and returned to the airport for an uneventful visual approach and landing; backed up by the same RNAV/GPS X XXR approach. After we were cleared for the approach; I armed the approach and all functions were normal. The autopilot intercepted and followed the vertical and lateral guidance. As we returned to the airport and while on downwind for Runway XXR; ZZZ Tower advised us of a possible pilot deviation. We were advised to call the ZZZ Controller upon landing. After arriving at the gate; I called and spoke with the ZZZ Controller as requested. A short vector from the arrival to the final course. The approach set up was a 90 degree intercept to the final approach course. A tail wind on the final approach course as well as turbulence from a vector through cumulus cloud bases on the base course. We were also given a late clearance for the approach. I have thought about this quite a bit and I believe that the best course of action would have been to ask for a delaying vector to ensure that we were set and ready for the approach. I also believe this would have given ATC a better opportunity to set us up for the approach with something like a 30 degree intercept to the final course instead of the 90 degree intercept we were given. This is paramount in mountainous terrain.
During arrival into ZZZ; and while descending on the ZZZZZ arrival; we were told that they are switching to Runway XXR from YYL; as originally planned. Then gave us a quick left turn; which put us a beam final. This followed by a right turn to intercept the final; we could see the airport by then. We were asked to maintain 11;000 ft. Until intercept the final; the aircraft didn't intercept the final as we flew through it; disconnecting the autopilot and headed for ZZZZZ1; and began descending; again the airport was very clear to us. Began descending to get to ZZZZZ1; because we were high; as a result we went around; and did the same arrival again followed by landing. This was a very tight approach with last minute runway changes. We should have refused the arrival and ask for more space.
More incidents for this aircraft family
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.