37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 995350 |
Time | |
Date | 201202 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | ZZZZ.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | B757-200 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Component | |
Aircraft Component | Altimeter |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 142 Flight Crew Total 17430 Flight Crew Type 8500 |
Person 2 | |
Function | First Officer Pilot Flying |
Experience | Flight Crew Last 90 Days 150 Flight Crew Total 8500 Flight Crew Type 5000 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Night; VMC arrival; all ATC requests were normal; except for a request to maintain high speed until late on base leg. By request; we were still at 250 on base; turning final. That said the spacing was good; with approximately five miles behind and in front of our two closest targets. Due to continuous descent approach (cda); we never leveled off; maintaining a nearly constant descent from FL340; all the way to the runway. The approach checklist was complete and holding on the local altimeter setting; but we failed to set the local altimeter as we started the turn from base to final. Consequently; we acquired the glideslope at approximately 6;000 ft and maintained the glide for the descent. Unfortunately; due to the incorrect altimeter; the aircraft thought that we were 450 ft lower than we actually were. While we were visually proceeding to the runway (which was in sight); using the glideslope for guidance; and we actually had correct terrain clearance; we received an egpws alert that we were too low; due to the incorrect altimeter input. Although we had an excellent visual picture of terrain and the runway; we complied with company policy with a CFIT recovery. During the resulting go-around; we were instructed to contact departure control; and were given an altitude of FL070. Since the transition on climb-out is 6;000; we both attempted to set our altimeters to standard; and that was when we realized that they were still in the standard setting. The correct local altimeter setting was 1031; and we had performed the approach with 1013.
Original NASA ASRS Text
Title: B757 flight crew reports forgetting set QNH during a night visual approach to an international airport. This results in a EGPWS alert and go around where the crew discovers their error passing through Transition Level.
Narrative: Night; VMC arrival; all ATC requests were normal; except for a request to maintain high speed until late on base leg. By request; we were still at 250 on base; turning final. That said the spacing was good; with approximately five miles behind and in front of our two closest targets. Due to Continuous Descent Approach (CDA); we never leveled off; maintaining a nearly constant descent from FL340; all the way to the runway. The approach checklist was complete and holding on the local altimeter setting; but we failed to set the local altimeter as we started the turn from base to final. Consequently; we acquired the glideslope at approximately 6;000 FT and maintained the glide for the descent. Unfortunately; due to the incorrect altimeter; the aircraft THOUGHT that we were 450 FT lower than we actually were. While we were visually proceeding to the runway (which was in sight); using the glideslope for guidance; and we actually had correct terrain clearance; we received an EGPWS alert that we were too low; due to the incorrect altimeter input. Although we had an excellent visual picture of terrain and the runway; we complied with company policy with a CFIT recovery. During the resulting Go-Around; we were instructed to contact Departure Control; and were given an altitude of FL070. Since the transition on climb-out is 6;000; we both attempted to set our altimeters to standard; and that was when we realized that they were still in the standard setting. The correct local altimeter setting was 1031; and we had performed the approach with 1013.
Data retrieved from NASA's ASRS site as of July 2013 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.