37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 260922 |
Time | |
Date | 199401 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : pie airport : tpa |
State Reference | FL |
Altitude | msl bound lower : 10000 msl bound upper : 10000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other Other |
Flight Phase | descent other |
Route In Use | arrival other arrival star : star enroute airway : tpa |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Beechcraft Twin Turboprop Jet Undifferentiated or Other Model |
Operating Under FAR Part | other : unknown |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : flight engineer pilot : instrument pilot : atp pilot : commercial |
Experience | flight time last 90 days : 174 flight time total : 12395 flight time type : 906 |
ASRS Report | 260922 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : instrument |
Events | |
Anomaly | conflict : airborne less severe other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other controllera other flight crewa |
Resolutory Action | controller : issued new clearance other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 18000 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | other |
Narrative:
We were on the dades arrival into tpa approaching dades, level at 13000 ft and just turned over to tpa approach control. The approach controller cleared us to 10000 ft. The first officer started a 1000 FPM descent. When we were passing 10700 ft, the controller asked our altitude. As I responded, he told us to turn right to 250 degrees reference traffic in our 12 O'clock approximately 7 mi. The first officer who had been monitoring the traffic via TCASII began an immediate 30 degree bank turn to the new heading while I looked for the traffic. At the completion of the turn, TCASII indicated the traffic was approximately 3 mi off our left wing. At about that time, TCASII declared a TA which was subsequently turned into an RA indicating a 500 FPM descent. By that time, we were level with our clearance altitude of 10000 ft. We had already received a turn from approach control reference the traffic and were complying with the existing clrncs exactly. The controller had not made any further reference to the traffic and the appearance was that everything was under control from the controller's point of view. By the time the RA was announced by TCASII, the traffic was behind our left wing and diverging. The first officer was taking all this into account and momentarily delayed reacting to the RA, since in his judgement the possibility of a near miss was now non-existent. By the time I looked back at the instruments and realized that the first officer had not reacted to the RA, TCASII announced clear of conflict. All this took only a few seconds. The rest of the flight into tpa was uneventful. After we arrived at the gate, I asked the first officer why he had not responded to the RA. He replied that any potential conflict had passed by the time the RA had occurred, and that he had considered the safer avenue was to continue complying with our altitude clearance since there was no possibility of getting any closer to the target at that time. At the time, I was of the opinion that regardless of the appearance of a false warning, it would have been safer to comply with the RA knowing that it would be a brief deviation and there might have been something else that TCASII was responding to that we were unaware of. In any event, I called tpa approach control after gate arrival. I talked to the supervisor and was told that the target was a king air at 10000 ft. He confirmed that we had been cleared to 10000 ft and IFR separation had not been compromised. He also acknowledged that the controller had been very busy. I guess the controller realized that the turn he had assigned was going to be sufficient to keep legal separation, but the closeness of the encounter gave us some anxious moments and could have very easily resulted in us having to violate our altitude clearance to comply with TCASII. In hindsight, I wish that in addition to the turn, the controller would have told us to climb back to 11000 ft. Once we had reached 11000 ft there would have been no possible conflict.
Original NASA ASRS Text
Title: ATC CTLR GAVE EVASIVE ACTION TURN TO AN MLG ACR ACFT TO AVOID ANOTHER ACFT CONVERGING AT THE SAME ALT.
Narrative: WE WERE ON THE DADES ARR INTO TPA APCHING DADES, LEVEL AT 13000 FT AND JUST TURNED OVER TO TPA APCH CTL. THE APCH CTLR CLRED US TO 10000 FT. THE FO STARTED A 1000 FPM DSCNT. WHEN WE WERE PASSING 10700 FT, THE CTLR ASKED OUR ALT. AS I RESPONDED, HE TOLD US TO TURN R TO 250 DEGS REF TFC IN OUR 12 O'CLOCK APPROX 7 MI. THE FO WHO HAD BEEN MONITORING THE TFC VIA TCASII BEGAN AN IMMEDIATE 30 DEG BANK TURN TO THE NEW HDG WHILE I LOOKED FOR THE TFC. AT THE COMPLETION OF THE TURN, TCASII INDICATED THE TFC WAS APPROX 3 MI OFF OUR L WING. AT ABOUT THAT TIME, TCASII DECLARED A TA WHICH WAS SUBSEQUENTLY TURNED INTO AN RA INDICATING A 500 FPM DSCNT. BY THAT TIME, WE WERE LEVEL WITH OUR CLRNC ALT OF 10000 FT. WE HAD ALREADY RECEIVED A TURN FROM APCH CTL REF THE TFC AND WERE COMPLYING WITH THE EXISTING CLRNCS EXACTLY. THE CTLR HAD NOT MADE ANY FURTHER REF TO THE TFC AND THE APPEARANCE WAS THAT EVERYTHING WAS UNDER CTL FROM THE CTLR'S POINT OF VIEW. BY THE TIME THE RA WAS ANNOUNCED BY TCASII, THE TFC WAS BEHIND OUR L WING AND DIVERGING. THE FO WAS TAKING ALL THIS INTO ACCOUNT AND MOMENTARILY DELAYED REACTING TO THE RA, SINCE IN HIS JUDGEMENT THE POSSIBILITY OF A NEAR MISS WAS NOW NON-EXISTENT. BY THE TIME I LOOKED BACK AT THE INSTS AND REALIZED THAT THE FO HAD NOT REACTED TO THE RA, TCASII ANNOUNCED CLR OF CONFLICT. ALL THIS TOOK ONLY A FEW SECONDS. THE REST OF THE FLT INTO TPA WAS UNEVENTFUL. AFTER WE ARRIVED AT THE GATE, I ASKED THE FO WHY HE HAD NOT RESPONDED TO THE RA. HE REPLIED THAT ANY POTENTIAL CONFLICT HAD PASSED BY THE TIME THE RA HAD OCCURRED, AND THAT HE HAD CONSIDERED THE SAFER AVENUE WAS TO CONTINUE COMPLYING WITH OUR ALT CLRNC SINCE THERE WAS NO POSSIBILITY OF GETTING ANY CLOSER TO THE TARGET AT THAT TIME. AT THE TIME, I WAS OF THE OPINION THAT REGARDLESS OF THE APPEARANCE OF A FALSE WARNING, IT WOULD HAVE BEEN SAFER TO COMPLY WITH THE RA KNOWING THAT IT WOULD BE A BRIEF DEV AND THERE MIGHT HAVE BEEN SOMETHING ELSE THAT TCASII WAS RESPONDING TO THAT WE WERE UNAWARE OF. IN ANY EVENT, I CALLED TPA APCH CTL AFTER GATE ARR. I TALKED TO THE SUPVR AND WAS TOLD THAT THE TARGET WAS A KING AIR AT 10000 FT. HE CONFIRMED THAT WE HAD BEEN CLRED TO 10000 FT AND IFR SEPARATION HAD NOT BEEN COMPROMISED. HE ALSO ACKNOWLEDGED THAT THE CTLR HAD BEEN VERY BUSY. I GUESS THE CTLR REALIZED THAT THE TURN HE HAD ASSIGNED WAS GOING TO BE SUFFICIENT TO KEEP LEGAL SEPARATION, BUT THE CLOSENESS OF THE ENCOUNTER GAVE US SOME ANXIOUS MOMENTS AND COULD HAVE VERY EASILY RESULTED IN US HAVING TO VIOLATE OUR ALT CLRNC TO COMPLY WITH TCASII. IN HINDSIGHT, I WISH THAT IN ADDITION TO THE TURN, THE CTLR WOULD HAVE TOLD US TO CLB BACK TO 11000 FT. ONCE WE HAD REACHED 11000 FT THERE WOULD HAVE BEEN NO POSSIBLE CONFLICT.
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.