37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1233220 |
Time | |
Date | 201501 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | VABB.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | B747-C/F |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Vectors |
Person 1 | |
Function | Pilot Flying First Officer |
Experience | Flight Crew Last 90 Days 20 Flight Crew Total 22000 Flight Crew Type 3000 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 112 Flight Crew Total 12500 Flight Crew Type 1750 |
Events | |
Anomaly | ATC Issue All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
We were being vectored in for an ILS runway 27 into mumbai. The weather was reported to be 1900 meters visibility; haze; smoke and light to variable winds. I believe we [were] leading the pack because we were told to maintain mach .84 or greater and to cross emrak at a certain time or earlier. When starting our descent we were told to cross emrak at 18000 or below and continue to 15000. The frequency congestion was very heavy with other carriers and controllers blocking each other and asking to repeat ATC instructions. The communications with controllers was also difficult to understand. We were given a vector to a heading of 255 for the approach into mumbai. We were also given altitude changes to cross at certain distances. We had complied with these instructions and given a descent to 1900 msl on a heading of 255 to intercept to localizer to runway 27. The captain and I both confirmed the altitude. The captain then read back the clearance for the ILS runway 27. We also had a jumpseat rider that was also qualified on the aircraft listening in and backing us up. The controller never ever questioned our read back. The approach had gotten busy for us because we were told to keep our speed up in the descent and approach and trying to get down. The heading; altitude and descent that we were given flew us over a mountain ridge that set off the GPWS. I disengaged the autopilot (a/P) had hand flew while starting a climb but we had already passed the conflict. I reengaged the a/P; leveled off at 1900/2000 feet msl. The controller asked about our altitude and said we should have been at 2900 ft. Msl. The captain told him he had cleared us down to 1900 ft. Msl. The controller didn't say anything other than cleared for the approach and handed us over to the tower. We were cleared to land which we did and taxied in to our assigned spot. We proceeded to shut down and secure the aircraft which we did. At no point in time where we told contact ATC or talk to any ATC representative about what had happened. We as crew members must maintain an even higher level of vigilance when coming into airports such as mumbai. The low visibility due to smoke/haze; terrain; and hard to understand controllers can make it very challenging. I had briefed what the MSA and GS but not the 2900 ft. Msl on the profile. I could have briefed the approach better and asked about the 1900 ft. We had the mountain ridge in sight and clear of the conflict. I should have executed a go around and get vectored back in for another approach.
Original NASA ASRS Text
Title: B747 flight crew reports being cleared to descend to 1900 feet during vectors to ILS 27 at VABB. The Controller questions their altitude stating they should be at 2900 feet at about the time a GPWS terrain warning is annunciated. The ridge causing the warning is visible and the approach is continued to landing.
Narrative: We were being vectored in for an ILS RWY 27 into Mumbai. The weather was reported to be 1900 meters visibility; haze; smoke and light to variable winds. I believe we [were] leading the pack because we were told to maintain Mach .84 or greater and to cross Emrak at a certain time or earlier. When starting our descent we were told to cross Emrak at 18000 or below and continue to 15000. The frequency congestion was very heavy with other carriers and controllers blocking each other and asking to repeat ATC instructions. The communications with controllers was also difficult to understand. We were given a vector to a heading of 255 for the approach into Mumbai. We were also given altitude changes to cross at certain distances. We had complied with these instructions and given a descent to 1900 msl on a heading of 255 to intercept to LOC to runway 27. The captain and I both confirmed the altitude. The captain then read back the clearance for the ILS runway 27. We also had a Jumpseat rider that was also qualified on the aircraft listening in and backing us up. The controller never ever questioned our read back. The approach had gotten busy for us because we were told to keep our speed up in the descent and approach and trying to get down. The heading; altitude and descent that we were given flew us over a mountain ridge that set off the GPWS. I disengaged the autopilot (A/P) had hand flew while starting a climb but we had already passed the conflict. I reengaged the A/P; leveled off at 1900/2000 feet msl. The controller asked about our altitude and said we should have been at 2900 ft. msl. The captain told him he had cleared us down to 1900 ft. msl. The controller didn't say anything other than cleared for the approach and handed us over to the tower. We were cleared to land which we did and taxied in to our assigned spot. We proceeded to shut down and secure the aircraft which we did. At no point in time where we told contact ATC or talk to any ATC representative about what had happened. We as crew members must maintain an even higher level of vigilance when coming into airports such as Mumbai. The low visibility due to smoke/haze; terrain; and hard to understand controllers can make it very challenging. I had briefed what the MSA and GS but not the 2900 ft. msl on the profile. I could have briefed the approach better and asked about the 1900 ft. We had the mountain ridge in sight and clear of the conflict. I should have executed a go around and get vectored back in for another approach.
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.