2010-01 · NASA ASRS report 869702
A320 Flight Crew experiences a GPWS terrain warning at 5000 feet during vectors to OAK. The Crew takes evasive action and informs ATC.
I was the Flying Pilot. Shortly after crossing the ECA VOR; we were given radar vectors off of the arrival; and a descent clearance to 8000 feet. The vectors took us directly over the Byron (identifier C83) airport; and generally toward Mt. Diablo. We then entered IMC. As briefed in the approach briefing; the MSA for our sector was 5100 feet; with Mt. Diablo at an elevation of +-3900 feet. We were cleared and descended to 5000 ft; and began to slow from 250 KIAS to 200 KIAS as we were approaching the SFO Class B airspace boundary. Both the Captain and I had our NAV Displays set to Weather Radar as we entered into light rain showers. I temporarily set my NAV Display back to Terrain to see if it would 'paint' Mt. Diablo; (which it did not); and then switched back to Weather. Shortly after switching back to Weather; we received a GPWS 'Terrain; Terrain; Pull-up; Pull-up.' By the second 'Pull-up'; I had initiated the GPWS Terrain escape maneuver (as outlined in the Flight Manual); and concurrently the Captain advised NorCal Approach that we were climbing due to the GPWS Terrain warning. The warning ceased almost immediately after the initiation of the climb. NorCal Approach re-cleared us; when able; to descend to 4000 feet. Recovery from the climb started at about 6000 feet; and (to my recollection) never exceeded 7000 feet; at which point we began a slow descent back down to 4000 feet. During the descent back to 4000 feet; I re-engaged the autopilot and autothrust. At this point we were approximately on the OAK VOR 015 at 15DME. We broke out into VMC shortly thereafter; continued to get vectors onto the localizer for the OAK ILS 11; and made an uneventful visual approach and landing. The hardest part of the whole event; was trying not to keep thinking about what just happened (GPWS Warning); but to focus on what still needed to be done (approach and landing). The Captain did a great job of communicating with ATC; verifying our clearances and status of aircraft configuration with regard to autofight; position etc. with me. There was no other mention of the event by ATC.
Clean configuration. Without warning; we received a 'Too Low; Terrain. Terrain; Terrain; Pull Up; Pull Up'. There was no pop-up feature on the ND. The First Officer immediately performed the escape maneuver; and I told ATC that we were climbing for a terrain warning. The terrain warning ceased climbing through around 6500 feet; and we leveled close to 7000 feet. ATC cleared us back down to 4000 feet when able; and we began a gradual descent back down to that altitude; with the First Officer's terrain function on.
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.