37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 391068 |
Time | |
Date | 199801 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : ord |
State Reference | IL |
Altitude | msl bound lower : 22000 msl bound upper : 22400 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau tower : zzz |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude cruise other |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | DC-8 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : flight engineer |
Experience | flight time last 90 days : 200 flight time total : 8800 flight time type : 5800 |
ASRS Report | 391068 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 200 flight time total : 6000 flight time type : 1800 |
ASRS Report | 391067 |
Events | |
Anomaly | altitude deviation : overshoot conflict : airborne less severe non adherence : clearance non adherence : published procedure non adherence : required legal separation other anomaly other |
Independent Detector | other controllera |
Resolutory Action | controller : issued new clearance other other |
Consequence | Other |
Miss Distance | horizontal : 12000 vertical : 600 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
After takeoff on our way to hpn, we were cleared to FL220. After we had leveled off, we saw a DC8 on our left at FL230. A few seconds later, our TCASII went off and ATC asked us to verify that we were level at FL220. We confirmed this and at the same time we noticed that we had never set our 3 altimeters to 29.92 inches. They were still at 29.53 inches which was ord's current setting. When we reset the altimeters, we were really at FL224. No action was taken (needed) to avoid the DC8. This incident proves that you always have to stay vigilant. We had been given quite a few heading and altitude changes as well as TA's which had diverted our attention. Also, I have flown with this first officer on many occasions and had always been impressed with his flying ability which probably had made me more relaxed than I should have been. Supplemental information from acn 391067: climbing out of ord for hpn, both the captain and I inadvertently forgot to reset the altimeters to 29.92 after passing FL180. ATC requested that we level off at FL220 for crossing traffic. ATC then called out the traffic, a DC8, at FL230, sebound, at our 10:30 to 11 O'clock position. We saw the traffic visually and noted our altitude as we approached FL220. We advised ATC that we had a visual on the traffic. As we approached leveloff, we received a TCASII TA. Once again, we verified the aircraft approaching our leveloff altitude of FL220. We then received an RA from our TCASII advising us to 'reduce climb.' the autoplt was already leveling the aircraft and was actually complying with the flight path guidance bars as it leveled off. The DC8 passed well off our right side as we leveled at FL220. ATC then replied that we were showing FL224, and to please check our equipment. We acknowledged and nothing further was said by ATC, other than to issue us a climb to our planned flight level. Needless to say, vigilance must be maintained throughout all phases of flight. Both the captain and I were complacent in our actions and that resulted in a violation of assigned altitude and a potential conflict with another aircraft.
Original NASA ASRS Text
Title: A B737-3400 FLC FORGETS TO SET THEIR ALTIMETER TO 29 PT 92 ON CLB TO FL220. THEY INCUR A POTENTIAL CONFLICT WITH A XING DC8 AT FL230. THEIR ACFT WAS AT FL224. PIC CITES FLC DISTR DUE TO HDG, ALT CHANGES AND TA'S ON CLBOUT.
Narrative: AFTER TKOF ON OUR WAY TO HPN, WE WERE CLRED TO FL220. AFTER WE HAD LEVELED OFF, WE SAW A DC8 ON OUR L AT FL230. A FEW SECONDS LATER, OUR TCASII WENT OFF AND ATC ASKED US TO VERIFY THAT WE WERE LEVEL AT FL220. WE CONFIRMED THIS AND AT THE SAME TIME WE NOTICED THAT WE HAD NEVER SET OUR 3 ALTIMETERS TO 29.92 INCHES. THEY WERE STILL AT 29.53 INCHES WHICH WAS ORD'S CURRENT SETTING. WHEN WE RESET THE ALTIMETERS, WE WERE REALLY AT FL224. NO ACTION WAS TAKEN (NEEDED) TO AVOID THE DC8. THIS INCIDENT PROVES THAT YOU ALWAYS HAVE TO STAY VIGILANT. WE HAD BEEN GIVEN QUITE A FEW HDG AND ALT CHANGES AS WELL AS TA'S WHICH HAD DIVERTED OUR ATTN. ALSO, I HAVE FLOWN WITH THIS FO ON MANY OCCASIONS AND HAD ALWAYS BEEN IMPRESSED WITH HIS FLYING ABILITY WHICH PROBABLY HAD MADE ME MORE RELAXED THAN I SHOULD HAVE BEEN. SUPPLEMENTAL INFO FROM ACN 391067: CLBING OUT OF ORD FOR HPN, BOTH THE CAPT AND I INADVERTENTLY FORGOT TO RESET THE ALTIMETERS TO 29.92 AFTER PASSING FL180. ATC REQUESTED THAT WE LEVEL OFF AT FL220 FOR XING TFC. ATC THEN CALLED OUT THE TFC, A DC8, AT FL230, SEBOUND, AT OUR 10:30 TO 11 O'CLOCK POS. WE SAW THE TFC VISUALLY AND NOTED OUR ALT AS WE APCHED FL220. WE ADVISED ATC THAT WE HAD A VISUAL ON THE TFC. AS WE APCHED LEVELOFF, WE RECEIVED A TCASII TA. ONCE AGAIN, WE VERIFIED THE ACFT APCHING OUR LEVELOFF ALT OF FL220. WE THEN RECEIVED AN RA FROM OUR TCASII ADVISING US TO 'REDUCE CLB.' THE AUTOPLT WAS ALREADY LEVELING THE ACFT AND WAS ACTUALLY COMPLYING WITH THE FLT PATH GUIDANCE BARS AS IT LEVELED OFF. THE DC8 PASSED WELL OFF OUR R SIDE AS WE LEVELED AT FL220. ATC THEN REPLIED THAT WE WERE SHOWING FL224, AND TO PLEASE CHK OUR EQUIP. WE ACKNOWLEDGED AND NOTHING FURTHER WAS SAID BY ATC, OTHER THAN TO ISSUE US A CLB TO OUR PLANNED FLT LEVEL. NEEDLESS TO SAY, VIGILANCE MUST BE MAINTAINED THROUGHOUT ALL PHASES OF FLT. BOTH THE CAPT AND I WERE COMPLACENT IN OUR ACTIONS AND THAT RESULTED IN A VIOLATION OF ASSIGNED ALT AND A POTENTIAL CONFLICT WITH ANOTHER ACFT.
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.