37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 413754 |
Time | |
Date | 199809 |
Day | Fri |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : ckh |
State Reference | HI |
Altitude | msl bound lower : 32000 msl bound upper : 32000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : hnl |
Operator | common carrier : air carrier |
Make Model Name | DC-10 10 |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent other |
Route In Use | arrival other enroute : on vectors enroute : direct |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | L-1011 Tri-Star All Series |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | descent other |
Route In Use | arrival other enroute : direct enroute : on vectors |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : instrument pilot : atp pilot : commercial pilot : flight engineer |
Experience | flight time last 90 days : 142 flight time total : 13190 flight time type : 2228 |
ASRS Report | 413754 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure non adherence : required legal separation other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : returned to intended course or assigned course flight crew : took evasive action |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 15000 vertical : 1000 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
We were at FL320, about 10 mi behind our company who was at FL340. Inside of anele intersection company was cleared direct bambo intersection. First officer and I were both on headsets with me working the radios. We were expecting direct bambo and I heard the tail end of a transmission clearing someone direct bambo. I asked ATC if they were calling us and they were and cleared us direct bambo. Next, ATC cleared us to turn left to a heading of 1?0 degrees. The middle digit was unreadable so I asked for a repeat, which was 160 degrees. We were expecting another turn to the right, direct bambo. A short time later I thought I heard the tail end of another clearance, clearing someone direct bambo. Again I asked ATC if the clearance was for us, which it was. The first officer started punching in direct bambo on the GPS when we got a TA warning from the TCASII. I checked the screen, then outside, and saw an aircraft about 300 ft below and about 8 mi away as indicated on the TCASII screen. We only got a TA and not an RA. By the time we set up the GPS to turn direct bambo, ATC called again, this time for us to turn to a heading of 220 degrees. But ATC didn't express urgency for us to turn by saying make immediate right turn to heading 220 degrees. After our turn to 220 degrees, first officer saw target was about 2 1/2 mi away and about 1400 ft below us. I kept a visual eye on the target until I was convinced he would be no factor. I asked ATC how many times he tried to call us and he said about 3. We apparently only heard the end of his second or third transmission. I talked to the controller on the phone after arrival into hnl. I told him that we were having difficulty hearing him and that we wrote up our radio even though we didn't know if ATC had a bad transmitter or if we had a bad receiver. During this call, I learned that air carrier Y captain was going to report the event because he took evasive action. I don't know if the other captain actually got an RA, but I am sure that I would have gotten an RA if he hadn't initiated evasive action. I also learned that air carrier Y was on a different frequency and that my controller was working both frequencys independently. I never heard a transmission to air carrier Y. Another piece of information I got from hnl ATC was that they changed their radio system about a month ago and that they have been logging their communication problems, apparently because they have had so many. It seems apparent that this event was primarily caused by us not hearing the initial calls of ATC. If we had turned sooner toward bambo, there probably would have been proper separation with air carrier Y aircraft. VHF communications has consistently been a problem going into hnl from the west coast. I am also concerned that the controller didn't tell us to make an immediate right turn the first time he had our attention (he cleared us direct bambo instead) and also the second time when he cleared us to a heading of 220 degrees.
Original NASA ASRS Text
Title: ACR DC10 AND L1011 FLCS COME INTO CONFLICT APPARENTLY DUE TO ACKNOWLEDGING CLRNCS FOR EACH OTHER. THE CTLR ISSUED CTL INSTRUCTIONS, BUT THE ACFT INVOLVED REQUIRED MULTIPLE CONFIRMATIONS. UPON LNDG, THE DC10 PIC CALLED ATC AND WAS TOLD THE OTHER ACFT WAS DECLARING AN NMAC. THE SUPVR ACKNOWLEDGED FREQ PROBS IN THAT AREA AND THAT THE CTLR WAS XMITTING SIMULTANEOUSLY ON 2 SEPARATE FREQS.
Narrative: WE WERE AT FL320, ABOUT 10 MI BEHIND OUR COMPANY WHO WAS AT FL340. INSIDE OF ANELE INTXN COMPANY WAS CLRED DIRECT BAMBO INTXN. FO AND I WERE BOTH ON HEADSETS WITH ME WORKING THE RADIOS. WE WERE EXPECTING DIRECT BAMBO AND I HEARD THE TAIL END OF A XMISSION CLRING SOMEONE DIRECT BAMBO. I ASKED ATC IF THEY WERE CALLING US AND THEY WERE AND CLRED US DIRECT BAMBO. NEXT, ATC CLRED US TO TURN L TO A HDG OF 1?0 DEGS. THE MIDDLE DIGIT WAS UNREADABLE SO I ASKED FOR A REPEAT, WHICH WAS 160 DEGS. WE WERE EXPECTING ANOTHER TURN TO THE R, DIRECT BAMBO. A SHORT TIME LATER I THOUGHT I HEARD THE TAIL END OF ANOTHER CLRNC, CLRING SOMEONE DIRECT BAMBO. AGAIN I ASKED ATC IF THE CLRNC WAS FOR US, WHICH IT WAS. THE FO STARTED PUNCHING IN DIRECT BAMBO ON THE GPS WHEN WE GOT A TA WARNING FROM THE TCASII. I CHKED THE SCREEN, THEN OUTSIDE, AND SAW AN ACFT ABOUT 300 FT BELOW AND ABOUT 8 MI AWAY AS INDICATED ON THE TCASII SCREEN. WE ONLY GOT A TA AND NOT AN RA. BY THE TIME WE SET UP THE GPS TO TURN DIRECT BAMBO, ATC CALLED AGAIN, THIS TIME FOR US TO TURN TO A HDG OF 220 DEGS. BUT ATC DIDN'T EXPRESS URGENCY FOR US TO TURN BY SAYING MAKE IMMEDIATE R TURN TO HDG 220 DEGS. AFTER OUR TURN TO 220 DEGS, FO SAW TARGET WAS ABOUT 2 1/2 MI AWAY AND ABOUT 1400 FT BELOW US. I KEPT A VISUAL EYE ON THE TARGET UNTIL I WAS CONVINCED HE WOULD BE NO FACTOR. I ASKED ATC HOW MANY TIMES HE TRIED TO CALL US AND HE SAID ABOUT 3. WE APPARENTLY ONLY HEARD THE END OF HIS SECOND OR THIRD XMISSION. I TALKED TO THE CTLR ON THE PHONE AFTER ARR INTO HNL. I TOLD HIM THAT WE WERE HAVING DIFFICULTY HEARING HIM AND THAT WE WROTE UP OUR RADIO EVEN THOUGH WE DIDN'T KNOW IF ATC HAD A BAD XMITTER OR IF WE HAD A BAD RECEIVER. DURING THIS CALL, I LEARNED THAT ACR Y CAPT WAS GOING TO RPT THE EVENT BECAUSE HE TOOK EVASIVE ACTION. I DON'T KNOW IF THE OTHER CAPT ACTUALLY GOT AN RA, BUT I AM SURE THAT I WOULD HAVE GOTTEN AN RA IF HE HADN'T INITIATED EVASIVE ACTION. I ALSO LEARNED THAT ACR Y WAS ON A DIFFERENT FREQ AND THAT MY CTLR WAS WORKING BOTH FREQS INDEPENDENTLY. I NEVER HEARD A XMISSION TO ACR Y. ANOTHER PIECE OF INFO I GOT FROM HNL ATC WAS THAT THEY CHANGED THEIR RADIO SYS ABOUT A MONTH AGO AND THAT THEY HAVE BEEN LOGGING THEIR COM PROBS, APPARENTLY BECAUSE THEY HAVE HAD SO MANY. IT SEEMS APPARENT THAT THIS EVENT WAS PRIMARILY CAUSED BY US NOT HEARING THE INITIAL CALLS OF ATC. IF WE HAD TURNED SOONER TOWARD BAMBO, THERE PROBABLY WOULD HAVE BEEN PROPER SEPARATION WITH ACR Y ACFT. VHF COMS HAS CONSISTENTLY BEEN A PROB GOING INTO HNL FROM THE WEST COAST. I AM ALSO CONCERNED THAT THE CTLR DIDN'T TELL US TO MAKE AN IMMEDIATE R TURN THE FIRST TIME HE HAD OUR ATTN (HE CLRED US DIRECT BAMBO INSTEAD) AND ALSO THE SECOND TIME WHEN HE CLRED US TO A HDG OF 220 DEGS.
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.