37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 490207 |
Time | |
Date | 200010 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : sfo.airport |
State Reference | CA |
Altitude | msl bound lower : 6000 msl bound upper : 6500 |
Environment | |
Flight Conditions | IMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : o90.tracon |
Operator | common carrier : air carrier |
Make Model Name | B737-300 |
Operating Under FAR Part | Part 121 |
Navigation In Use | ils localizer & glide slope : 25r other |
Flight Phase | descent : intermediate altitude |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : flight engineer pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 180 flight time total : 16850 flight time type : 4175 |
ASRS Report | 490207 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : flight engineer pilot : multi engine |
Experience | flight time last 90 days : 220 flight time total : 4500 flight time type : 4000 |
ASRS Report | 489980 |
Events | |
Anomaly | conflict : airborne less severe non adherence : clearance non adherence : published procedure non adherence : required legal separation |
Independent Detector | atc equipment other atc equipment : radar aircraft equipment : tcas other controllera other flight crewa other flight crewb |
Resolutory Action | controller : issued new clearance controller : issued advisory controller : separated traffic other |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 18500 vertical : 0 |
Supplementary | |
Problem Areas | Flight Crew Human Performance Weather ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error other |
Narrative:
We were being vectored on a 120 degree heading at 6000 ft (left downwind ILS runway 28 sfo). Our next turn was to a 030 degree heading (an apparent left base). Almost immediately an aircraft appeared on the TCASII on an apparent right base for runway 28R at 6000 ft. Our paths would converse at about the same spot on the localizer if neither was given a turn. About the time I was going to query ATC on our situation 2 things happened almost simultaneously. ATC asked us our heading stating that we had an aircraft at our altitude and we received a TCASII TA. The first officer stated our heading was 030 degrees. ATC gave us an immediate right turn to 100 degrees (approximately heading) and also gave the other aircraft a right turn away from us. As we were in the turn we received a TCASII RA to 'climb' which I followed. At about 6500 ft we received a clear of conflict report from TCASII. As we began the TCASII climb the first officer reported to ATC that we were in a TCASII climb. ATC responded asking us what our heading had been. The first officer stated 030 degrees. Then ATC asked for our heading before that turn. The first officer stated 120 degrees. ATC then gave us a left turn to a 280 degree heading. I asked the first officer to verify that that was a left turn to 280 degrees. ATC responded turn left to 280 degrees, intercept the runway 28R localizer, maintain 4000 ft to dumra, cleared for the ILS to runway 28R. No further mention was made by ATC regarding the mix-up. After landing I called bay approach on the telephone to see if they needed to talk to us. The gentleman that answered said he'd check. When he came back he indicated that they would have to investigate to see if required separation had been maintained. He asked if I thought we'd gotten closer than 3 mi. I said I didn't know, but that we were in the turn before receiving the TCASII RA. He said 'that's good.' he said that they didn't have a problem with us, but that the controller thought he'd given us a 330 degree heading not 030 degrees. He went on to say that even if we turned to and read back the wrong heading, the problem they had was whether the controller had maintained adequate separation. I asked if that meant we could expect any action from them concerning our part and he said 'no' they would be investigating the controller's actions not ours. That ended the phone call.
Original NASA ASRS Text
Title: CAPT OF A B737 TURNED AND CLBED IN RESPONSE TO NEW HEADING GIVEN BY APCH CTL AND SUBSEQUENT TCASII RA DURING VECTORS TO SFO ILS. BOTH ACFT WERE NOSE TO NOSE TURNING FINAL FROM OPPOSITE BASED LEGS.
Narrative: WE WERE BEING VECTORED ON A 120 DEG HDG AT 6000 FT (L DOWNWIND ILS RWY 28 SFO). OUR NEXT TURN WAS TO A 030 DEG HDG (AN APPARENT L BASE). ALMOST IMMEDIATELY AN ACFT APPEARED ON THE TCASII ON AN APPARENT R BASE FOR RWY 28R AT 6000 FT. OUR PATHS WOULD CONVERSE AT ABOUT THE SAME SPOT ON THE LOC IF NEITHER WAS GIVEN A TURN. ABOUT THE TIME I WAS GOING TO QUERY ATC ON OUR SIT 2 THINGS HAPPENED ALMOST SIMULTANEOUSLY. ATC ASKED US OUR HEADING STATING THAT WE HAD AN ACFT AT OUR ALT AND WE RECEIVED A TCASII TA. THE FO STATED OUR HEADING WAS 030 DEGS. ATC GAVE US AN IMMEDIATE R TURN TO 100 DEGS (APPROX HEADING) AND ALSO GAVE THE OTHER ACFT A R TURN AWAY FROM US. AS WE WERE IN THE TURN WE RECEIVED A TCASII RA TO 'CLB' WHICH I FOLLOWED. AT ABOUT 6500 FT WE RECEIVED A CLR OF CONFLICT RPT FROM TCASII. AS WE BEGAN THE TCASII CLB THE FO RPTED TO ATC THAT WE WERE IN A TCASII CLB. ATC RESPONDED ASKING US WHAT OUR HEADING HAD BEEN. THE FO STATED 030 DEGS. THEN ATC ASKED FOR OUR HEADING BEFORE THAT TURN. THE FO STATED 120 DEGS. ATC THEN GAVE US A L TURN TO A 280 DEG HDG. I ASKED THE FO TO VERIFY THAT THAT WAS A L TURN TO 280 DEGS. ATC RESPONDED TURN L TO 280 DEGS, INTERCEPT THE RWY 28R LOC, MAINTAIN 4000 FT TO DUMRA, CLRED FOR THE ILS TO RWY 28R. NO FURTHER MENTION WAS MADE BY ATC REGARDING THE MIX-UP. AFTER LNDG I CALLED BAY APCH ON THE TELEPHONE TO SEE IF THEY NEEDED TO TALK TO US. THE GENTLEMAN THAT ANSWERED SAID HE'D CHK. WHEN HE CAME BACK HE INDICATED THAT THEY WOULD HAVE TO INVESTIGATE TO SEE IF REQUIRED SEPARATION HAD BEEN MAINTAINED. HE ASKED IF I THOUGHT WE'D GOTTEN CLOSER THAN 3 MI. I SAID I DIDN'T KNOW, BUT THAT WE WERE IN THE TURN BEFORE RECEIVING THE TCASII RA. HE SAID 'THAT'S GOOD.' HE SAID THAT THEY DIDN'T HAVE A PROB WITH US, BUT THAT THE CTLR THOUGHT HE'D GIVEN US A 330 DEG HDG NOT 030 DEGS. HE WENT ON TO SAY THAT EVEN IF WE TURNED TO AND READ BACK THE WRONG HEADING, THE PROB THEY HAD WAS WHETHER THE CTLR HAD MAINTAINED ADEQUATE SEPARATION. I ASKED IF THAT MEANT WE COULD EXPECT ANY ACTION FROM THEM CONCERNING OUR PART AND HE SAID 'NO' THEY WOULD BE INVESTIGATING THE CTLR'S ACTIONS NOT OURS. THAT ENDED THE PHONE CALL.
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.