2024-04 · NASA ASRS report 2109858
Air carrier flight crew reported an early descent on a visual approach resulted in an ATC low altitude alert; a terrain alert; and a CFTT event.
PIT was landing Runway 32; and we were approaching from the northeast. We were assigned a heading of 230 (pointed almost directly at TRINY); and given a descent to 3;000'. PIT asked if we had the airport in sight; I advised the FO to call it; and we were cleared for the visual approach to Runway 32. I turned downwind so that TRINY was off my 2-3 o'clock position on the 2.5nm ring on the MFD (Multi-function Flight Display). My intention was to do a descending turn as we slowed and configured to arrive at TRINY at 2;500'; on speed; configured for the Runway. Once cleared for the visual and TRINY passing my 3 o'clock position; I continued descent to 2;500' (the fix altitude) and was about to turn base. Soon thereafter; several things happened in rapid succession.First ATC advised us of a low altitude alert just as we got Caution-Terrain" audio. I immediately hit ALT as PIT directed us to climb to 3;000' and turn right to heading 240. I set 3;000' in the alerter; stowed the speed brakes; and began climbing as I turned the autopilot off. We leveled at 3;000 on the base leg and began configuring for landing. The rest of the approach and landing were uneventful. Suggestions:Looking back on it and more thoroughly reviewing the approach chart; I could have briefed the antennae located under our approach path. PIT hasn't landed Runway 32 as a matter of course in quite some time; so a more robust briefing from me was clearly in order. As pilots; we don't know the minimum vectoring altitudes used by ATC; so had no way to know that would trigger on their end once I left 3;000'; but clearly we were close enough to underlying obstacles that the GPWS (and ATC) alerting parameters were tripped. Our procedures state in VMC if a GPWS Caution is received; we are to take immediate action to eliminate the Caution; which I did by immediately arresting our descent and subsequently climbing. That said; my situational awareness in this instance clearly was lacking. I should have remained at 3;000' while I arced around TRINY; slowed; and configured. I'm aware that visual approaches are insidious; and this event is a stark reminder to not assume that since we've flown into an airport repeatedly that something can't go sideways quickly. I have never been one of those pilots who aggressively seeks out visual approach clearances- on the contrary- earlier today we were going into ZZZ and since the FO and I hadn't been in there in recent memory; as PF I had the FO decline the visual approach and insist on us getting clearance for the RNAV to Runway XXL. This approach event into PIT was simply a lack of recent familiarity on my part of that geographic area and its hazards - something that; again; I could have mitigated with a more thorough visual approach briefing."
On an ATC assigned vector 230 to intercept Runway 32 final approach course at 3;000'; the PIT Approach Controller cleared us for the visual approach 32. The PF set the FAF altitude of 2500 and began a descent. Upon reaching 2500' ATC gave a low altitude alert and we received and we received a caution-Terrain" aural alert. The PF arrested the descent and followed the controller's instruction to climb to 3;000'. And turn heading 240. Once level at 3;000 on base we configured for landing and the remainder of the approach and landing were completed without further incident. Suggestions:Due to the infrequent use of Runway 32 in PIT a more thorough briefing should have been completed. I believe that an inadequate briefing helped lead to a lack of situational awareness in this instance. This definitely underscores the importance of reviewing the terrain and obstacles that may be near your approach path particularly when infrequently used or unfamiliar approaches are in use. Additionally; it would have been pertinent to utilize the ILS approach and decline the visual in this particular instance."
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.