37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 256469 |
Time | |
Date | 199311 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : stl |
State Reference | MO |
Altitude | msl bound lower : 6000 msl bound upper : 7400 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tracon : stl |
Operator | common carrier : air carrier |
Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : departure |
Qualification | controller : radar |
ASRS Report | 256469 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other flight crewa |
Resolutory Action | none taken : anomaly accepted |
Consequence | faa : reviewed incident with flight crew |
Miss Distance | horizontal : 6000 vertical : 1400 |
Supplementary | |
Primary Problem | Aircraft |
Air Traffic Incident | other |
Narrative:
I was working departure north position. Air carrier X was a departure I was working at 6000 ft going north. Air carrier X would go under an arrival track that would have aircraft at 7000 or descending to 7000 going southwest. I issued traffic to air carrier X. One was air carrier Y, an arrival at 8000 descending to 7000, and air carrier Z, an arrival at 7000. As air carrier X was going under the arrival track, he asked if he had traffic at 6000. I said the only traffic in the vicinity of him was air carrier Z at 7400 at his 3 O'clock and 1 mi and air carrier Y at 7000 at his 3 O'clock and 4 mi. He said he got a TCASII alert to descend. Quite often, there would be propeller traffic at 5000 in the vicinity of this incident. There was no traffic at 6000 within 20 mi of air carrier X. These false TCASII alerts tie up my frequency and add to my workload and have the potential to be dangerous. TCASII should be turned off in class B airspace.
Original NASA ASRS Text
Title: FLC OF AN MLG ACR ACFT ADVISED ATC OF TCASII RA TO DSND. CTLR INFORMED FLC THAT THERE WAS NO CONFLICTING TFC WITHIN 20 MI.
Narrative: I WAS WORKING DEP N POS. ACR X WAS A DEP I WAS WORKING AT 6000 FT GOING N. ACR X WOULD GO UNDER AN ARR TRACK THAT WOULD HAVE ACFT AT 7000 OR DSNDING TO 7000 GOING SW. I ISSUED TFC TO ACR X. ONE WAS ACR Y, AN ARR AT 8000 DSNDING TO 7000, AND ACR Z, AN ARR AT 7000. AS ACR X WAS GOING UNDER THE ARR TRACK, HE ASKED IF HE HAD TFC AT 6000. I SAID THE ONLY TFC IN THE VICINITY OF HIM WAS ACR Z AT 7400 AT HIS 3 O'CLOCK AND 1 MI AND ACR Y AT 7000 AT HIS 3 O'CLOCK AND 4 MI. HE SAID HE GOT A TCASII ALERT TO DSND. QUITE OFTEN, THERE WOULD BE PROP TFC AT 5000 IN THE VICINITY OF THIS INCIDENT. THERE WAS NO TFC AT 6000 WITHIN 20 MI OF ACR X. THESE FALSE TCASII ALERTS TIE UP MY FREQ AND ADD TO MY WORKLOAD AND HAVE THE POTENTIAL TO BE DANGEROUS. TCASII SHOULD BE TURNED OFF IN CLASS B AIRSPACE.
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.