37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 585538 |
Time | |
Date | 200306 |
Day | Mon |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | navaid : twf.vortac |
State Reference | ID |
Altitude | msl bound lower : 21000 msl bound upper : 23000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | artcc : zlc.artcc |
Operator | common carrier : air carrier |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other other vortac |
Flight Phase | climbout : intermediate altitude |
Route In Use | enroute airway : j515.airway |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | artcc : zlc.artcc |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : flight engineer pilot : commercial pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 7000 flight time type : 500 |
ASRS Report | 585538 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | altitude deviation : excursion from assigned altitude conflict : airborne critical non adherence : required legal separation |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | flight crew : took precautionary avoidance action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 4500 vertical : 500 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
During a flight from slc to geg, a TCASII RA was encountered. The autoplt with VNAV and LNAV was engaged. Aircraft was at 310 KIAS, VMC, level at 17000 ft with ZLC. An air carrier Y was ahead and above at FL220. The captain and I heard air carrier Y request and receive a climb to FL240 for turbulence. We were then cleared to climb and maintain FL230. During the climb, approximately 1/2 NM behind air carrier Y, we received a TCASII RA to level off/descend. I immediately disconnected the autoplt and initiated a descent back to FL210 in accordance with TCASII commands. We passed below and to the left of air carrier Y. Upon hearing TCASII advise 'clear of conflict,' I initiated a slow climb. Approaching FL220, air carrier Y queried slc center about the RA, so we descended back to FL210. During the RA, we advised slc center of the alert, our return to FL210, and that we had air carrier Y in visual contact. (The controller sounded confused as he thought he had cleared us only to FL210.) upon reaching spokane (geg), the captain called the slc center supervisor and was told that his controller had cleared us to FL230 (after reviewing the tapes). He said it was controller error and that he was glad we had maintained visual contact with air carrier Y and followed TCASII commands. He further said no action was going to be initiated against us. This was leg 3 on day 2 of the rotation. Fatigue was a contributing factor. Also, although all TCASII commands were followed and visual contact maintained, a more aggressive and earlier deviation might have negated the TCASII RA.
Original NASA ASRS Text
Title: B737 FLT CREW RECEIVES A TCASII RA DURING CLB TO ALT AFTER DEPARTING SLC.
Narrative: DURING A FLT FROM SLC TO GEG, A TCASII RA WAS ENCOUNTERED. THE AUTOPLT WITH VNAV AND LNAV WAS ENGAGED. ACFT WAS AT 310 KIAS, VMC, LEVEL AT 17000 FT WITH ZLC. AN ACR Y WAS AHEAD AND ABOVE AT FL220. THE CAPT AND I HEARD ACR Y REQUEST AND RECEIVE A CLB TO FL240 FOR TURB. WE WERE THEN CLRED TO CLB AND MAINTAIN FL230. DURING THE CLB, APPROX 1/2 NM BEHIND ACR Y, WE RECEIVED A TCASII RA TO LEVEL OFF/DSND. I IMMEDIATELY DISCONNECTED THE AUTOPLT AND INITIATED A DSCNT BACK TO FL210 IN ACCORDANCE WITH TCASII COMMANDS. WE PASSED BELOW AND TO THE L OF ACR Y. UPON HEARING TCASII ADVISE 'CLR OF CONFLICT,' I INITIATED A SLOW CLB. APCHING FL220, ACR Y QUERIED SLC CTR ABOUT THE RA, SO WE DSNDED BACK TO FL210. DURING THE RA, WE ADVISED SLC CTR OF THE ALERT, OUR RETURN TO FL210, AND THAT WE HAD ACR Y IN VISUAL CONTACT. (THE CTLR SOUNDED CONFUSED AS HE THOUGHT HE HAD CLRED US ONLY TO FL210.) UPON REACHING SPOKANE (GEG), THE CAPT CALLED THE SLC CTR SUPVR AND WAS TOLD THAT HIS CTLR HAD CLRED US TO FL230 (AFTER REVIEWING THE TAPES). HE SAID IT WAS CTLR ERROR AND THAT HE WAS GLAD WE HAD MAINTAINED VISUAL CONTACT WITH ACR Y AND FOLLOWED TCASII COMMANDS. HE FURTHER SAID NO ACTION WAS GOING TO BE INITIATED AGAINST US. THIS WAS LEG 3 ON DAY 2 OF THE ROTATION. FATIGUE WAS A CONTRIBUTING FACTOR. ALSO, ALTHOUGH ALL TCASII COMMANDS WERE FOLLOWED AND VISUAL CONTACT MAINTAINED, A MORE AGGRESSIVE AND EARLIER DEV MIGHT HAVE NEGATED THE TCASII RA.
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.