37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 571934 |
Time | |
Date | 200301 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : fll.airport |
State Reference | FL |
Altitude | msl single value : 4000 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : mia.tracon tower : tpa.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | approach : traffic pattern |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : mia.tracon |
Operator | common carrier : air carrier |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Experience | flight time last 90 days : 240 flight time total : 12500 flight time type : 8000 |
ASRS Report | 571934 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Experience | flight time last 90 days : 150 flight time total : 6000 flight time type : 3000 |
ASRS Report | 571975 |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance other spatial deviation |
Independent Detector | aircraft equipment : tcas other controllerb other flight crewa |
Resolutory Action | controller : issued new clearance |
Consequence | faa : reviewed incident with flight crew other |
Miss Distance | vertical : 1000 |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
ATC instructions misinterped, possible traffic separation problem. We were on 280 degree assigned heading, left downwind for runway 9L fll. At 4000 ft MSL, we were given what we believed to be a 190 degree heading, and read it back as such, and began the left turn, standard rate, level at 4000 ft. This seemed logical as we were at about the normal area for a base turn. About halfway through the turn, I visually acquired another aircraft at my 2 O'clock position and checking the TCASII, I could see he was 1000 ft above us and descending. He was on final for runway 9L as well. From the TCASII, and my visual, it appeared that a conflict might result if we continued the turn. Simultaneously, we got TA from TCASII, and the controller asking us why we were in the turn. We were rolling out of the turn at about 210 degree heading when the controller said 'I gave you 190 degree speed, not a 190 degree heading.' at this time, he directed us to descend to 2000 ft and fly our current heading. I heard him tell the other aircraft to slow his descent. The TA ceased on TCASII, and we had the A320 visually at all times. He told the controller that he had us visually. The controller cleared the A320 for the visual approach to runway 9L and shortly after, he cleared us for the visual approach. Traffic separation (5 mi) and landing were uneventful from this point. Upon shutting down at the gate, I contacted miami approach on my cell phone and explained to the supervisor what I thought our clearance had been and what had happened. I also asked if there had been a separation problem. He said he had reviewed the situation with the controller and did not see where we had violated any minimum separation distances, but could have if we had not rolled out or acquired the other traffic visually. He said he would contact the other pilot, and if he had no problem, then approach would have no problem either. We discussed the events, radio calls leading to the potential conflict, and what we could do to prevent such events in the future. The supervisor was very understanding of the events and agreed that the turn made sense, at that point, when normally we turn base. We talked about the importance of proper radio terminology and readbacks. We thought we read back 190 degree heading, but both myself and the first officer could not remember if he said degree. The supervisor was able to speak to the other captain, and he said he had no problem with any traffic separation and that he saw us the entire time. The approach supervisor called me back and said no further action was needed and the event was closed with no conflict noted. The lesson learned is to listen up on the radio, ask for clarification if unsure, and use proper radio terminology. Also, never assume that because the timing and location and heading of the turn 'feel' right, that it is right. Had the event taken place in IMC, it might not have felt as comfortable when ATC and the TCASII start barking at us at the same time. My thanks to the controller and the other captain for their understanding of the situation. We also called our company ATC representative and informed him of the events.
Original NASA ASRS Text
Title: B737 LNDG FLL TURNS TO 190 DEG HDG, ATC CONTENDS 190 WAS SPD ASSIGNMENT.
Narrative: ATC INSTRUCTIONS MISINTERPED, POSSIBLE TFC SEPARATION PROB. WE WERE ON 280 DEG ASSIGNED HDG, L DOWNWIND FOR RWY 9L FLL. AT 4000 FT MSL, WE WERE GIVEN WHAT WE BELIEVED TO BE A 190 DEG HDG, AND READ IT BACK AS SUCH, AND BEGAN THE L TURN, STANDARD RATE, LEVEL AT 4000 FT. THIS SEEMED LOGICAL AS WE WERE AT ABOUT THE NORMAL AREA FOR A BASE TURN. ABOUT HALFWAY THROUGH THE TURN, I VISUALLY ACQUIRED ANOTHER ACFT AT MY 2 O'CLOCK POS AND CHKING THE TCASII, I COULD SEE HE WAS 1000 FT ABOVE US AND DSNDING. HE WAS ON FINAL FOR RWY 9L AS WELL. FROM THE TCASII, AND MY VISUAL, IT APPEARED THAT A CONFLICT MIGHT RESULT IF WE CONTINUED THE TURN. SIMULTANEOUSLY, WE GOT TA FROM TCASII, AND THE CTLR ASKING US WHY WE WERE IN THE TURN. WE WERE ROLLING OUT OF THE TURN AT ABOUT 210 DEG HDG WHEN THE CTLR SAID 'I GAVE YOU 190 DEG SPD, NOT A 190 DEG HDG.' AT THIS TIME, HE DIRECTED US TO DSND TO 2000 FT AND FLY OUR CURRENT HDG. I HEARD HIM TELL THE OTHER ACFT TO SLOW HIS DSCNT. THE TA CEASED ON TCASII, AND WE HAD THE A320 VISUALLY AT ALL TIMES. HE TOLD THE CTLR THAT HE HAD US VISUALLY. THE CTLR CLRED THE A320 FOR THE VISUAL APCH TO RWY 9L AND SHORTLY AFTER, HE CLRED US FOR THE VISUAL APCH. TFC SEPARATION (5 MI) AND LNDG WERE UNEVENTFUL FROM THIS POINT. UPON SHUTTING DOWN AT THE GATE, I CONTACTED MIAMI APCH ON MY CELL PHONE AND EXPLAINED TO THE SUPVR WHAT I THOUGHT OUR CLRNC HAD BEEN AND WHAT HAD HAPPENED. I ALSO ASKED IF THERE HAD BEEN A SEPARATION PROB. HE SAID HE HAD REVIEWED THE SIT WITH THE CTLR AND DID NOT SEE WHERE WE HAD VIOLATED ANY MINIMUM SEPARATION DISTANCES, BUT COULD HAVE IF WE HAD NOT ROLLED OUT OR ACQUIRED THE OTHER TFC VISUALLY. HE SAID HE WOULD CONTACT THE OTHER PLT, AND IF HE HAD NO PROB, THEN APCH WOULD HAVE NO PROB EITHER. WE DISCUSSED THE EVENTS, RADIO CALLS LEADING TO THE POTENTIAL CONFLICT, AND WHAT WE COULD DO TO PREVENT SUCH EVENTS IN THE FUTURE. THE SUPVR WAS VERY UNDERSTANDING OF THE EVENTS AND AGREED THAT THE TURN MADE SENSE, AT THAT POINT, WHEN NORMALLY WE TURN BASE. WE TALKED ABOUT THE IMPORTANCE OF PROPER RADIO TERMINOLOGY AND READBACKS. WE THOUGHT WE READ BACK 190 DEG HDG, BUT BOTH MYSELF AND THE FO COULD NOT REMEMBER IF HE SAID DEGREE. THE SUPVR WAS ABLE TO SPEAK TO THE OTHER CAPT, AND HE SAID HE HAD NO PROB WITH ANY TFC SEPARATION AND THAT HE SAW US THE ENTIRE TIME. THE APCH SUPVR CALLED ME BACK AND SAID NO FURTHER ACTION WAS NEEDED AND THE EVENT WAS CLOSED WITH NO CONFLICT NOTED. THE LESSON LEARNED IS TO LISTEN UP ON THE RADIO, ASK FOR CLARIFICATION IF UNSURE, AND USE PROPER RADIO TERMINOLOGY. ALSO, NEVER ASSUME THAT BECAUSE THE TIMING AND LOCATION AND HDG OF THE TURN 'FEEL' RIGHT, THAT IT IS RIGHT. HAD THE EVENT TAKEN PLACE IN IMC, IT MIGHT NOT HAVE FELT AS COMFORTABLE WHEN ATC AND THE TCASII START BARKING AT US AT THE SAME TIME. MY THANKS TO THE CTLR AND THE OTHER CAPT FOR THEIR UNDERSTANDING OF THE SIT. WE ALSO CALLED OUR COMPANY ATC REPRESENTATIVE AND INFORMED HIM OF THE EVENTS.
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.