Although questioning their altitude clearance on vectors for Runway 11 at OAK; the flight crew of a B737-300 continued their descent until receiving a GPWS terrain warning at which time they confirmed their cleared altitude as 3;100 FT not 2;100 FT as they had read back and entered in the altitude alert window.

2011-03 · NASA ASRS report 939321

Date: 2011-03 · Aircraft: B737-300 · Phase: descent

Anomalies: deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

Although questioning their altitude clearance on vectors for Runway 11 at OAK; the flight crew of a B737-300 continued their descent until receiving a GPWS terrain warning at which time they confirmed their cleared altitude as 3;100 FT not 2;100 FT as they had read back and entered in the altitude alert window.

Narrative

While getting vectors after the COMMO Arrival to Runway 11 at OAK; we were given a descent from 5;000 FT to what we thought was 2;100 FT. That is what I understood and set into the altitude window; and that is what my First Officer read back to ATC. My First Officer and I thought that was kind of low for where we were in relation to the airport and discussed it. My First Officer then asked ATC what the MVA was in this area and he replied 5;000 FT where we were previously; a small band of 4;000 FT; and then 3;000 FT. We assumed that he was descending us into an area ahead of that with an even lower MVA. As we passed through about 2;700 FT ATC said the altitude was supposed to be 3;100 FT. I immediately started a climb to 3;100 FT and then I got a single GPWS caution; 'Caution; terrain.' I disconnected the autopilot and continued correcting the flight path of the aircraft. We leveled at 3;100 FT and continued to the airport without further problems.Since we were both sure of the clearance to descend to 2;100 FT and the subsequent read back was not challenged by ATC there is not too much I can think of to improve that part of the error. I think we did the right thing as far as discussing the MVA and asking ATC about it. I think my mistake was assuming that ATC was descending us into an area that the MVA was lower than the area that we were currently in. If something does not feel right; get clarification until it does feel right.

Second reporter narrative

I looked at the approach plate and remarked to the Captain that the MSA for where we were was 5;100 FT. He then remarked that that was within 25 miles of the fix. I looked at the FMC and noted that we were 22 miles from PLAZA. Then I asked the Controller what the minimum vectoring altitude was for where we were.Any altitude query at low altitude should prompt a repeat of the last issued altitude clearance. I will always start with my last clearance when checking about the MVA.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.