37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1349554 |
Time | |
Date | 201604 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | MMSD.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Other VOR DME-2 Runway 16 |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Altitude Overshoot Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was the non flying pilot and had been briefed for the minimum descent altitude on the airway coming into mmsd. Prior to marux we were given the cleared for approach. The captain flying briefed the 8000 feet until marux and then at the next 15.0 dme fix 3600 feet to 11.0 dme. As we were cleared for the approach the captain armed the approach and got the approach nav and final annunciation. When final captured we started our descent to 3600 feet. Upon reaching 3600 feet we were yelled at by ATC that we were not cleared to descend below 6000 feet as it was below minimum vectoring altitude of 5100 feet. We both noticed we were on profile and at this point we were both confused due to the on profile indication. We continued on in day VMC with airport in sight and were cleared visual approach while tracking the approach profile. Upon landing we debriefed the event and noticed that in fine print that the segment after marux and before the 15 dme fix was 6000 minimum. After 15 dme the 3600 min until 11 dme applies.we both missed the 6000 foot minimum restriction on the chart and it is not coded into the approach in navigation data for the VOR approach. Given the VFR conditions; we continued the approach and landed visually. We should probably have climbed back to 5100 foot MVA or 6000 feet for 4 miles and then continued descent to 3600 feet on the approach. The event occurred because we did not properly brief the altitudes on the approach chart.
Original NASA ASRS Text
Title: A320 First Officer reported not noticing the 6000 ft minimum vectoring altitude between MARUX and the IAF on the MMSD VOR DME-2 Runway 16 Approach. The reporter stated the altitude is not coded into their navigation database.
Narrative: I was the non flying pilot and had been briefed for the minimum descent altitude on the airway coming into MMSD. Prior to MARUX we were given the cleared for Approach. The Captain flying briefed the 8000 feet until MARUX and then at the next 15.0 dme fix 3600 feet to 11.0 Dme. As we were cleared for the approach the Captain armed the approach and got the Approach Nav and Final annunciation. When final captured we started our descent to 3600 feet. Upon reaching 3600 feet we were yelled at by ATC that we were not cleared to descend below 6000 feet as it was below Minimum Vectoring Altitude of 5100 feet. We both noticed we were on profile and at this point we were both confused due to the on profile indication. We continued on in day VMC with airport in sight and were cleared Visual Approach while tracking the approach profile. Upon landing we debriefed the event and noticed that in fine print that the segment after MARUX and before the 15 Dme fix was 6000 minimum. After 15 Dme the 3600 min until 11 Dme applies.We both missed the 6000 foot minimum restriction on the chart and it is not coded into the approach in NAV Data for the VOR Approach. Given the VFR conditions; we continued the approach and landed visually. We should probably have climbed back to 5100 foot MVA or 6000 feet for 4 miles and then continued descent to 3600 feet on the approach. The event occurred because we did not properly brief the altitudes on the approach chart.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.