37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 402500 |
Time | |
Date | 199805 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : rbs |
State Reference | IL |
Altitude | msl bound lower : 15000 msl bound upper : 23000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau |
Operator | common carrier : air carrier |
Make Model Name | B737-500 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | other other : other pilot : atp pilot : commercial pilot : flight engineer pilot : instrument |
Experience | flight time last 90 days : 240 flight time total : 14000 flight time type : 2600 |
ASRS Report | 402500 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 60 flight time total : 6000 flight time type : 60 |
ASRS Report | 402499 |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne less severe non adherence : required legal separation non adherence : clearance other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 18000 vertical : 400 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Aircraft was level at 15000 ft MSL just north of the rbs VOR en route from ord to stl. Call sign was 'airline XXX.' captain was performing the duties of the PF. The first officer was executing duties of the PNF. Mr X, an FAA aviation safety inspector was in the cockpit jump seat. At approximately XX40Z, as I was reaching into my flight bag to retrieve the STAR and approach plates I would need for arrival into st louis lambert field, ZAU issued a climb to FL230. First officer acknowledged the climb and reset the altitude alert window on the mode control panel to indicate 23000 ft. I pointed to the new altitude setting, stated 'climbing to FL230,' and then initiated climb using VNAV control. Passing approximately 15500 ft with a climb rate of about 1000 FPM, a TA was initiated by the TCASII system. The indication was an aircraft at about the 10-11 O'clock position, level at 16000 ft. I spotted the other aircraft visually, immediately rechked my altitude (15600 ft and climbing) and climb rate. Due to the juxtaposition of both aircraft and the climb rate vector of my aircraft, I elected to increase rate of climb using vertical speed control to 2000-2200 FPM. Estimated horizontal distance from the other aircraft at this time was about 3 mi. No RA was ever annunciated by the TCASII. At 17500 ft I reduced the climb rate to 1000 FPM, re-engaged VNAV, and continued climb to FL230. After switching to another center frequency, I was asked to call ZAU. I asked my first officer if, in fact, we had been cleared to FL230 and if he had acknowledged the call just to confirm in my mind that we had been cleared by ZAU. He stated emphatically that 'yes, he had.' I also asked the FAA inspector if he had noticed anything out of the ordinary or if I had done anything erroneously. He stated, 'no, I think you did everything you were supposed to do.' I have not been able to contact ZAU quality assurance/standardization as yet to discuss the matter with them. Radio communications by ZAU was extremely busy with almost constant xmissions between center and other aircraft in the area. Another aircraft -- different airline YYY -- was also on the frequency. I am now thinking that my new first officer, who was only on his third flight assignment for the company, might have acknowledged the climb intended for different airline YYY instead of us, airline XXX. I was temporarily distracted by trying to remove the approach plates from my flight bag and may have misinterpreted/misunderstood the call myself due to the similarities of the call signs and the frantic pace and constant chatter on the departure out of chicago. The FAA inspector did not pick up on any irregularity either, before the TA was initiated. The ZAU controller also did not pick up on the first officer's call acknowledging that 'airline XXX' was leaving 15000 ft for FL230.
Original NASA ASRS Text
Title: B737 CREW STARTED CLB FROM 15000 FT TO FL230. THEY GET TCASII TA AND INCREASE CLB RATE TO AVOID CONFLICTING TFC.
Narrative: ACFT WAS LEVEL AT 15000 FT MSL JUST N OF THE RBS VOR ENRTE FROM ORD TO STL. CALL SIGN WAS 'AIRLINE XXX.' CAPT WAS PERFORMING THE DUTIES OF THE PF. THE FO WAS EXECUTING DUTIES OF THE PNF. MR X, AN FAA AVIATION SAFETY INSPECTOR WAS IN THE COCKPIT JUMP SEAT. AT APPROX XX40Z, AS I WAS REACHING INTO MY FLT BAG TO RETRIEVE THE STAR AND APCH PLATES I WOULD NEED FOR ARR INTO ST LOUIS LAMBERT FIELD, ZAU ISSUED A CLB TO FL230. FO ACKNOWLEDGED THE CLB AND RESET THE ALT ALERT WINDOW ON THE MODE CTL PANEL TO INDICATE 23000 FT. I POINTED TO THE NEW ALT SETTING, STATED 'CLBING TO FL230,' AND THEN INITIATED CLB USING VNAV CTL. PASSING APPROX 15500 FT WITH A CLB RATE OF ABOUT 1000 FPM, A TA WAS INITIATED BY THE TCASII SYS. THE INDICATION WAS AN ACFT AT ABOUT THE 10-11 O'CLOCK POS, LEVEL AT 16000 FT. I SPOTTED THE OTHER ACFT VISUALLY, IMMEDIATELY RECHKED MY ALT (15600 FT AND CLBING) AND CLB RATE. DUE TO THE JUXTAPOSITION OF BOTH ACFT AND THE CLB RATE VECTOR OF MY ACFT, I ELECTED TO INCREASE RATE OF CLB USING VERT SPD CTL TO 2000-2200 FPM. ESTIMATED HORIZ DISTANCE FROM THE OTHER ACFT AT THIS TIME WAS ABOUT 3 MI. NO RA WAS EVER ANNUNCIATED BY THE TCASII. AT 17500 FT I REDUCED THE CLB RATE TO 1000 FPM, RE-ENGAGED VNAV, AND CONTINUED CLB TO FL230. AFTER SWITCHING TO ANOTHER CTR FREQ, I WAS ASKED TO CALL ZAU. I ASKED MY FO IF, IN FACT, WE HAD BEEN CLRED TO FL230 AND IF HE HAD ACKNOWLEDGED THE CALL JUST TO CONFIRM IN MY MIND THAT WE HAD BEEN CLRED BY ZAU. HE STATED EMPHATICALLY THAT 'YES, HE HAD.' I ALSO ASKED THE FAA INSPECTOR IF HE HAD NOTICED ANYTHING OUT OF THE ORDINARY OR IF I HAD DONE ANYTHING ERRONEOUSLY. HE STATED, 'NO, I THINK YOU DID EVERYTHING YOU WERE SUPPOSED TO DO.' I HAVE NOT BEEN ABLE TO CONTACT ZAU QUALITY ASSURANCE/STANDARDIZATION AS YET TO DISCUSS THE MATTER WITH THEM. RADIO COMS BY ZAU WAS EXTREMELY BUSY WITH ALMOST CONSTANT XMISSIONS BTWN CTR AND OTHER ACFT IN THE AREA. ANOTHER ACFT -- DIFFERENT AIRLINE YYY -- WAS ALSO ON THE FREQ. I AM NOW THINKING THAT MY NEW FO, WHO WAS ONLY ON HIS THIRD FLT ASSIGNMENT FOR THE COMPANY, MIGHT HAVE ACKNOWLEDGED THE CLB INTENDED FOR DIFFERENT AIRLINE YYY INSTEAD OF US, AIRLINE XXX. I WAS TEMPORARILY DISTRACTED BY TRYING TO REMOVE THE APCH PLATES FROM MY FLT BAG AND MAY HAVE MISINTERPRETED/MISUNDERSTOOD THE CALL MYSELF DUE TO THE SIMILARITIES OF THE CALL SIGNS AND THE FRANTIC PACE AND CONSTANT CHATTER ON THE DEP OUT OF CHICAGO. THE FAA INSPECTOR DID NOT PICK UP ON ANY IRREGULARITY EITHER, BEFORE THE TA WAS INITIATED. THE ZAU CTLR ALSO DID NOT PICK UP ON THE FO'S CALL ACKNOWLEDGING THAT 'AIRLINE XXX' WAS LEAVING 15000 FT FOR FL230.
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.