An Air Carrier flight crew reported they descended below the Minimum Vectoring Altitude.

Date: 2024-02 · Aircraft: B737-700 · Phase: descent

Anomalies: atc-issue-all-types|deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

An Air Carrier flight crew reported they descended below the Minimum Vectoring Altitude.

Narrative

To the best of my recollection; we were at 6;000 ft. and given a descent clearance to 5;000 ft. by Approach. I can't remember if the controller on frequency gave us that clearance or if it was the previous Approach Controller. The FO (First Officer) believes it was the previous Controller. After a few minutes at 5;000 ft. the Approach with an accent asked what altitude we were at; and I replied 5;000 ft. The Approach Controller stated that the MVA for that sector was 5;200 ft. due to the terrain to the east of our position. I am unsure if we misunderstood the descent clearance from 6;000 ft. or if the descent clearance was actually down to 5;000 ft. versus 5;200 ft. Either way the FO and Captain are sure we read back 5;000 ft. The Controller on frequency had an accent that made them somewhat difficult to understand but it is quite possible that the previous Controller issued that descent instruction and the Controller on frequency was simply correcting the issue. Either way it appears we were 200 ft. low and below the MVA altitude for that sector.

Second reporter narrative

To the best of my recollection; we were at 6;000 ft. given a descent clearance to 5;000 ft. and a heading of 200 from the initial Approach Controller. The Controller did respond with any different instructions. We were then handed off to the final Approach Controller. The final Controller asked what altitude we were at. PM stated 5;000 ft. Approach Controller responded with you should be at 5;200 feet for the MVA due to terrain in the area". They then vectored us closer to the field to then join the Localizer for ILS Approach Runway XXR. The final Approach Controller had stated that it could have been a previous Controllers error; she did not give us a number to call."

More incidents for this aircraft family →

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