37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 429601 |
Time | |
Date | 199903 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : etx.vor |
State Reference | PA |
Altitude | msl bound lower : 26000 msl bound upper : 26600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zny.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
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 |
Qualification | pilot : atp pilot : multi engine pilot : commercial |
Experience | flight time last 90 days : 210 flight time total : 15000 flight time type : 8000 |
ASRS Report | 429601 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : multi engine pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 160 flight time total : 20000 flight time type : 6000 |
ASRS Report | 429843 |
Events | |
Anomaly | altitude deviation : overshoot non adherence : clearance non adherence : far |
Independent Detector | other controllera |
Resolutory Action | controller : issued alert flight crew : returned to original clearance |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
As we approached leveloff, ZNY asked us our altitude then quickly said, check your altimeter set 29.92. The altimeter was set for 29.32. We started the aircraft back down, but were a minimum of 300 ft high and probably ballooned higher before the aircraft actually started to descend. First officer had called out FL180 29.92 set and I believe I faked him out by reaching for the altimeter but saw a '2' as the last digit and thought it was already reset. His was reset to correct reading. Conditions were good daylight, VFR and I had both panel lights and backgnd lights on but missed it. Last leg of a 4 day trip so somewhat tired but not overly so. Can't think of any other reasons, just missed it.
Original NASA ASRS Text
Title: CAPT OF A B737-300 LEVELED OFF HIGH DUE TO NOT RESETTING HIS ALTIMETER WHEN THE FO HAD CALLED FOR THE CHANGE DURING CLB. THE CTR CTLR NOTICED THE MISTAKE AND ALERTED THE FLC.
Narrative: AS WE APCHED LEVELOFF, ZNY ASKED US OUR ALT THEN QUICKLY SAID, CHK YOUR ALTIMETER SET 29.92. THE ALTIMETER WAS SET FOR 29.32. WE STARTED THE ACFT BACK DOWN, BUT WERE A MINIMUM OF 300 FT HIGH AND PROBABLY BALLOONED HIGHER BEFORE THE ACFT ACTUALLY STARTED TO DSND. FO HAD CALLED OUT FL180 29.92 SET AND I BELIEVE I FAKED HIM OUT BY REACHING FOR THE ALTIMETER BUT SAW A '2' AS THE LAST DIGIT AND THOUGHT IT WAS ALREADY RESET. HIS WAS RESET TO CORRECT READING. CONDITIONS WERE GOOD DAYLIGHT, VFR AND I HAD BOTH PANEL LIGHTS AND BACKGND LIGHTS ON BUT MISSED IT. LAST LEG OF A 4 DAY TRIP SO SOMEWHAT TIRED BUT NOT OVERLY SO. CAN'T THINK OF ANY OTHER REASONS, JUST MISSED IT.
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.