 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B767 crew is asked to confirm their altitude after reaching cruise. They discover that they did not set qne passing the transition altitude causing the altitude deviation.
| Attributes | |
| ACN | 631050 |
| Time | |
| Date | 200409 |
| Day | Tue |
| Place | |
| Locale Reference | atc facility : zny.artcc |
| State Reference | NY |
| Altitude | msl single value : 35000 |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny.artcc tracon : zzz.tracon |
| Operator | common carrier : air carrier |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 240 flight time total : 17500 flight time type : 5300 |
| ASRS Report | 631050 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Events | |
| Anomaly | altitude deviation : excursion from assigned altitude non adherence : published procedure non adherence : far non adherence : clearance |
| Independent Detector | other controllerb other flight crewa other flight crewb |
| Resolutory Action | none taken : anomaly accepted |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
While climbing to our en route altitude, we had to level off at several intermediate altitudes, including 17000 ft. When cleared above 17000 ft, we conducted our usual FL180 SOP's, including cabin notification of double chimes and lights off, but somehow failed to set 29.92 hg. Shortly after arriving at FL350, the controller asked us to 'confirm level at FL350.' the first officer and I simultaneously realized that the altimeters were not set to 29.92 hg. We promptly corrected our altimeters and altitude. The controller had no further comments or questions. Although, the other FL180 SOP's had been accomplished, failure to set qne was an oversight on my part. I am responsible to ensure that all SOP's are complied with and accomplished at the correct time. This was an inadvertent error and I am sorry that this occurred. I fully understand the need to maintain accurate and correct altimetry. The oversight underscores the need to continuously scan for inconsistencies and ensure all SOP's are completed.
Original NASA ASRS Text
Title: A B767 CREW IS ASKED TO CONFIRM THEIR ALT AFTER REACHING CRUISE. THEY DISCOVER THAT THEY DID NOT SET QNE PASSING THE TRANSITION ALT CAUSING THE ALTDEV.
Narrative: WHILE CLBING TO OUR ENRTE ALT, WE HAD TO LEVEL OFF AT SEVERAL INTERMEDIATE ALTS, INCLUDING 17000 FT. WHEN CLRED ABOVE 17000 FT, WE CONDUCTED OUR USUAL FL180 SOP'S, INCLUDING CABIN NOTIFICATION OF DOUBLE CHIMES AND LIGHTS OFF, BUT SOMEHOW FAILED TO SET 29.92 HG. SHORTLY AFTER ARRIVING AT FL350, THE CTLR ASKED US TO 'CONFIRM LEVEL AT FL350.' THE FO AND I SIMULTANEOUSLY REALIZED THAT THE ALTIMETERS WERE NOT SET TO 29.92 HG. WE PROMPTLY CORRECTED OUR ALTIMETERS AND ALT. THE CTLR HAD NO FURTHER COMMENTS OR QUESTIONS. ALTHOUGH, THE OTHER FL180 SOP'S HAD BEEN ACCOMPLISHED, FAILURE TO SET QNE WAS AN OVERSIGHT ON MY PART. I AM RESPONSIBLE TO ENSURE THAT ALL SOP'S ARE COMPLIED WITH AND ACCOMPLISHED AT THE CORRECT TIME. THIS WAS AN INADVERTENT ERROR AND I AM SORRY THAT THIS OCCURRED. I FULLY UNDERSTAND THE NEED TO MAINTAIN ACCURATE AND CORRECT ALTIMETRY. THE OVERSIGHT UNDERSCORES THE NEED TO CONTINUOUSLY SCAN FOR INCONSISTENCIES AND ENSURE ALL SOP'S ARE COMPLETED.
Data retrieved from NASA's ASRS site as of July 2007 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.