37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 624028 |
Time | |
Date | 200407 |
Day | Sat |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : tul.tracon |
State Reference | OK |
Altitude | msl bound lower : 6000 msl bound upper : 8500 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : tul.tracon tower : atl.tower |
Operator | common carrier : air carrier |
Make Model Name | B737-800 |
Operating Under FAR Part | Part 121 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tracon : tul.tracon |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | descent : intermediate altitude |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 624028 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
ASRS Report | 624739 |
Events | |
Anomaly | conflict : nmac non adherence : far non adherence : published procedure non adherence : required legal separation other anomaly other |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | controller : issued alert |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 0 vertical : 100 |
Supplementary | |
Problem Areas | Flight Crew Human Performance ATC Human Performance |
Primary Problem | Ambiguous |
Narrative:
During climb out from tul (runway 18L) 178 degrees runway heading to 15000 ft, tulsa departure issued us a traffic alert at our 1 - 1:30 O'clock position, type and altitude unknown. We were told that 'if the traffic was not in sight, suggest you level your aircraft now.' hand flying, using the HUD, I put the flight path vector on the horizon to immediately level us off while we tried to visually acquire the traffic. At that point our TCASII gave us a TA, with the aural warning, 'traffic, traffic.' it then changed to red with an RA to 'climb, climb' with an additional warning to 'increase climb.' hand flying, I was able to follow the symbology in the HUD without any delay. I then heard, 'monitor vertical speed.' I held what I had until the 'clear of conflict' was heard. The initial TA showed the target at -300 ft and closing. The RA in red showed the target at -100 ft passing under the aircraft symbol on our display. After the conflict was resolved, I resumed the normal climb profile to altitude. ATC was not sure why the target aircraft showed up all of a sudden. I was told that he thinks he just turned his transponder on when we received the alerts. We never saw the aircraft. Tulsa departure did raise him on the frequency and I heard the target aircraft say 'we have the airliner in sight and will maintain visual separation.' at that point he was no longer a threat and we proceeded to dfw on course. Upon arrival at the gate, I called the dispatcher to file the report and company wanted to have a conference call with tulsa approach/departure. A supervisor came on the phone and told us that, as per their procedures, the call will be recorded. We discussed the events that happened on climb out and then told him that I had no choice but to follow the TCASII RA. I believe that had I not climbed, we would have passed even closer, or possibly collided. The TCASII worked and performed flawlessly. Supervisor said the tapes have been pulled and will be reviewed. Supplemental information from acn 624739: climbing out of tul, through about 8000 ft cleared to 15000 ft, captain flying. Talking to tul departure. Noticed a target pop up on the TCASII, which I had on the 10 mi range. It was very close in, reading +06. I said 'hey, what's this guy?' just as ATC called 'traffic alert.' by this time I had put the range on 5 mi, only to see the target showing +02, so close to our aircraft symbol, the bearing was indiscernible. Controller said, 'if you don't see him, suggest you level immediately.' we were doing about 3000 FPM at the time, and the captain, who was hand flying, immediately began to level. About this time, the TCASII issued an RA saying, 'climb, climb' with most of the vsi red, except for the portion above about 2800 FPM. Because we had just been told to level immediately and were in the process of doing so, it took us a few seconds to process this information and make the transition. The seemingly contradicting information was due to the fact that we had passed through the altitude of the other aircraft during our attempt to level, and now he was below us, although we could not see that because the target was superimposed on our aircraft symbol on the TCASII screen. About this time, the TCASII issued a secondary warning, something like 'increase climb rate,' although I do not recall the exact verbiage. After we were clear of the conflict, we queried ATC, who indicated that this traffic popped up on his screen the same time he popped up on ours, and that he was not in contact with him at all. He also indicated that the aircraft was 'on the edge' of being illegal in the airspace, and he would 'look into it.' we never did see this aircraft, but we came within a few hundred ft laterally and within zero ft vertically. This was way too close.
Original NASA ASRS Text
Title: A B737-800 FLT CREW RPTED THAT, DURING DEP FROM TUL, THEY EXPERIENCED AN NMAC WITH ANOTHER ACFT THAT HAD NOT BEEN POINTED OUT BY TUL TRACON.
Narrative: DURING CLBOUT FROM TUL (RWY 18L) 178 DEGS RWY HDG TO 15000 FT, TULSA DEP ISSUED US A TFC ALERT AT OUR 1 - 1:30 O'CLOCK POS, TYPE AND ALT UNKNOWN. WE WERE TOLD THAT 'IF THE TFC WAS NOT IN SIGHT, SUGGEST YOU LEVEL YOUR ACFT NOW.' HAND FLYING, USING THE HUD, I PUT THE FLT PATH VECTOR ON THE HORIZON TO IMMEDIATELY LEVEL US OFF WHILE WE TRIED TO VISUALLY ACQUIRE THE TFC. AT THAT POINT OUR TCASII GAVE US A TA, WITH THE AURAL WARNING, 'TFC, TFC.' IT THEN CHANGED TO RED WITH AN RA TO 'CLB, CLB' WITH AN ADDITIONAL WARNING TO 'INCREASE CLB.' HAND FLYING, I WAS ABLE TO FOLLOW THE SYMBOLOGY IN THE HUD WITHOUT ANY DELAY. I THEN HEARD, 'MONITOR VERT SPD.' I HELD WHAT I HAD UNTIL THE 'CLR OF CONFLICT' WAS HEARD. THE INITIAL TA SHOWED THE TARGET AT -300 FT AND CLOSING. THE RA IN RED SHOWED THE TARGET AT -100 FT PASSING UNDER THE ACFT SYMBOL ON OUR DISPLAY. AFTER THE CONFLICT WAS RESOLVED, I RESUMED THE NORMAL CLB PROFILE TO ALT. ATC WAS NOT SURE WHY THE TARGET ACFT SHOWED UP ALL OF A SUDDEN. I WAS TOLD THAT HE THINKS HE JUST TURNED HIS XPONDER ON WHEN WE RECEIVED THE ALERTS. WE NEVER SAW THE ACFT. TULSA DEP DID RAISE HIM ON THE FREQ AND I HEARD THE TARGET ACFT SAY 'WE HAVE THE AIRLINER IN SIGHT AND WILL MAINTAIN VISUAL SEPARATION.' AT THAT POINT HE WAS NO LONGER A THREAT AND WE PROCEEDED TO DFW ON COURSE. UPON ARR AT THE GATE, I CALLED THE DISPATCHER TO FILE THE RPT AND COMPANY WANTED TO HAVE A CONFERENCE CALL WITH TULSA APCH/DEP. A SUPVR CAME ON THE PHONE AND TOLD US THAT, AS PER THEIR PROCS, THE CALL WILL BE RECORDED. WE DISCUSSED THE EVENTS THAT HAPPENED ON CLBOUT AND THEN TOLD HIM THAT I HAD NO CHOICE BUT TO FOLLOW THE TCASII RA. I BELIEVE THAT HAD I NOT CLBED, WE WOULD HAVE PASSED EVEN CLOSER, OR POSSIBLY COLLIDED. THE TCASII WORKED AND PERFORMED FLAWLESSLY. SUPVR SAID THE TAPES HAVE BEEN PULLED AND WILL BE REVIEWED. SUPPLEMENTAL INFO FROM ACN 624739: CLBING OUT OF TUL, THROUGH ABOUT 8000 FT CLRED TO 15000 FT, CAPT FLYING. TALKING TO TUL DEP. NOTICED A TARGET POP UP ON THE TCASII, WHICH I HAD ON THE 10 MI RANGE. IT WAS VERY CLOSE IN, READING +06. I SAID 'HEY, WHAT'S THIS GUY?' JUST AS ATC CALLED 'TFC ALERT.' BY THIS TIME I HAD PUT THE RANGE ON 5 MI, ONLY TO SEE THE TARGET SHOWING +02, SO CLOSE TO OUR ACFT SYMBOL, THE BEARING WAS INDISCERNIBLE. CTLR SAID, 'IF YOU DON'T SEE HIM, SUGGEST YOU LEVEL IMMEDIATELY.' WE WERE DOING ABOUT 3000 FPM AT THE TIME, AND THE CAPT, WHO WAS HAND FLYING, IMMEDIATELY BEGAN TO LEVEL. ABOUT THIS TIME, THE TCASII ISSUED AN RA SAYING, 'CLB, CLB' WITH MOST OF THE VSI RED, EXCEPT FOR THE PORTION ABOVE ABOUT 2800 FPM. BECAUSE WE HAD JUST BEEN TOLD TO LEVEL IMMEDIATELY AND WERE IN THE PROCESS OF DOING SO, IT TOOK US A FEW SECONDS TO PROCESS THIS INFO AND MAKE THE TRANSITION. THE SEEMINGLY CONTRADICTING INFO WAS DUE TO THE FACT THAT WE HAD PASSED THROUGH THE ALT OF THE OTHER ACFT DURING OUR ATTEMPT TO LEVEL, AND NOW HE WAS BELOW US, ALTHOUGH WE COULD NOT SEE THAT BECAUSE THE TARGET WAS SUPERIMPOSED ON OUR ACFT SYMBOL ON THE TCASII SCREEN. ABOUT THIS TIME, THE TCASII ISSUED A SECONDARY WARNING, SOMETHING LIKE 'INCREASE CLB RATE,' ALTHOUGH I DO NOT RECALL THE EXACT VERBIAGE. AFTER WE WERE CLR OF THE CONFLICT, WE QUERIED ATC, WHO INDICATED THAT THIS TFC POPPED UP ON HIS SCREEN THE SAME TIME HE POPPED UP ON OURS, AND THAT HE WAS NOT IN CONTACT WITH HIM AT ALL. HE ALSO INDICATED THAT THE ACFT WAS 'ON THE EDGE' OF BEING ILLEGAL IN THE AIRSPACE, AND HE WOULD 'LOOK INTO IT.' WE NEVER DID SEE THIS ACFT, BUT WE CAME WITHIN A FEW HUNDRED FT LATERALLY AND WITHIN ZERO FT VERTLY. THIS WAS WAY TOO CLOSE.
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.