37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 206290 |
Time | |
Date | 199203 |
Day | Mon |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : fll |
State Reference | FL |
Altitude | msl bound lower : 7000 msl bound upper : 8000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : mia |
Operator | common carrier : air carrier |
Make Model Name | Large Transport, Low Wing, 2 Turbojet Eng |
Navigation In Use | Other Other |
Flight Phase | descent other |
Route In Use | enroute : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Light Transport, Low Wing, 2 Turboprop Eng |
Flight Phase | cruise other |
Route In Use | enroute : direct |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : approach |
Qualification | controller : radar |
ASRS Report | 206290 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
ASRS Report | 206070 |
Events | |
Anomaly | conflict : airborne less severe inflight encounter : weather non adherence : published procedure non adherence : required legal separation |
Independent Detector | other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | faa : investigated faa : reviewed incident with flight crew |
Miss Distance | horizontal : 0 vertical : 400 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Operational Error |
Narrative:
I was controling air carrier X in the arrival corridor en route to land at fll. Also in that corridor was air carrier Y landing mia at 7000. Air carrier X was at 8000 and requested a wbound heading to avoid WX. There was WX everywhere covering most of south fl, especially over fort lauderdale and miami areas. Both aircraft were due sbound at this time, in close proximity to each other separated by altitude at this time. There was much coordination to be done during this time frame since when aircraft deviate they penetrate other sector's airspace. It appeared to me that air carrier X was 1/4 mi west of the propeller, so I turned air carrier X to a wbound heading and descended him to 7000 since he was head-on with another jet at 6000. He asked me what altitude his 2 O'clock traffic was at and I told him 6000. About 5 seconds later, he said 'my traffic is at 7000' and descended below 7000. He filed an near midair collision. The supervisor in charge of the satellite sector informed me that there was probably a beacon displacement of up to 1 mi since air carrier X was on the fll radar system and air carrier Y, landing mia, was on the mia beacon system. I believe that the alphanumeric data blocks FLIP-flopped to offset one from the other, there, I believed air carrier X was west of the propeller, when, in fact, he most likely was not. Some new modernized ATC equipment could alleviate this from happening in the future. Supplemental information from acn 206070: air carrier X radar vector by mia approach for fll. Descending on a right downwind to runway 27 at fll as we passed approximately 4500 ft my copilot and a dispatcher on our jump seat both cried out as an aircraft appeared out of the clouds immediately beneath us and very close. I had about 1 min earlier turned our TCASII from the TA/RA mode to the TA mode to avoid nuisance alerts near the airport. There was an aircraft about 1500 ft above us on the TCASII screen covering the TCASII symbol of the aircraft that went beneath us, an air carrier Y. On the ground, I spoke on the phone with area manager -- mia tower, and he explained the scenario to me and stated it appeared that an 'operational error' had occurred. There were thunderstorm cells all around and aircraft were being vectored to stay clear. We were being vectored by same controller and immediately thereafter, another controller took over. The air carrier Y noticed us at about the same time we noticed them. The dispatcher stated it appeared to him that the air carrier Y aircraft was in a steep right bank at the time.
Original NASA ASRS Text
Title: ACR X DSCNT THROUGH OCCUPIED ALT HAD LTSS FROM ACR Y. SYS ERROR.
Narrative: I WAS CTLING ACR X IN THE ARR CORRIDOR ENRTE TO LAND AT FLL. ALSO IN THAT CORRIDOR WAS ACR Y LNDG MIA AT 7000. ACR X WAS AT 8000 AND REQUESTED A WBOUND HDG TO AVOID WX. THERE WAS WX EVERYWHERE COVERING MOST OF S FL, ESPECIALLY OVER FORT LAUDERDALE AND MIAMI AREAS. BOTH ACFT WERE DUE SBOUND AT THIS TIME, IN CLOSE PROX TO EACH OTHER SEPARATED BY ALT AT THIS TIME. THERE WAS MUCH COORD TO BE DONE DURING THIS TIME FRAME SINCE WHEN ACFT DEVIATE THEY PENETRATE OTHER SECTOR'S AIRSPACE. IT APPEARED TO ME THAT ACR X WAS 1/4 MI W OF THE PROP, SO I TURNED ACR X TO A WBOUND HDG AND DSNDED HIM TO 7000 SINCE HE WAS HEAD-ON WITH ANOTHER JET AT 6000. HE ASKED ME WHAT ALT HIS 2 O'CLOCK TFC WAS AT AND I TOLD HIM 6000. ABOUT 5 SECONDS LATER, HE SAID 'MY TFC IS AT 7000' AND DSNDED BELOW 7000. HE FILED AN NMAC. THE SUPVR IN CHARGE OF THE SATELLITE SECTOR INFORMED ME THAT THERE WAS PROBABLY A BEACON DISPLACEMENT OF UP TO 1 MI SINCE ACR X WAS ON THE FLL RADAR SYS AND ACR Y, LNDG MIA, WAS ON THE MIA BEACON SYS. I BELIEVE THAT THE ALPHANUMERIC DATA BLOCKS FLIP-FLOPPED TO OFFSET ONE FROM THE OTHER, THERE, I BELIEVED ACR X WAS W OF THE PROP, WHEN, IN FACT, HE MOST LIKELY WAS NOT. SOME NEW MODERNIZED ATC EQUIP COULD ALLEVIATE THIS FROM HAPPENING IN THE FUTURE. SUPPLEMENTAL INFO FROM ACN 206070: ACR X RADAR VECTOR BY MIA APCH FOR FLL. DSNDING ON A R DOWNWIND TO RWY 27 AT FLL AS WE PASSED APPROX 4500 FT MY COPLT AND A DISPATCHER ON OUR JUMP SEAT BOTH CRIED OUT AS AN ACFT APPEARED OUT OF THE CLOUDS IMMEDIATELY BENEATH US AND VERY CLOSE. I HAD ABOUT 1 MIN EARLIER TURNED OUR TCASII FROM THE TA/RA MODE TO THE TA MODE TO AVOID NUISANCE ALERTS NEAR THE ARPT. THERE WAS AN ACFT ABOUT 1500 FT ABOVE US ON THE TCASII SCREEN COVERING THE TCASII SYMBOL OF THE ACFT THAT WENT BENEATH US, AN ACR Y. ON THE GND, I SPOKE ON THE PHONE WITH AREA MGR -- MIA TWR, AND HE EXPLAINED THE SCENARIO TO ME AND STATED IT APPEARED THAT AN 'OPERROR' HAD OCCURRED. THERE WERE TSTM CELLS ALL AROUND AND ACFT WERE BEING VECTORED TO STAY CLR. WE WERE BEING VECTORED BY SAME CTLR AND IMMEDIATELY THEREAFTER, ANOTHER CTLR TOOK OVER. THE ACR Y NOTICED US AT ABOUT THE SAME TIME WE NOTICED THEM. THE DISPATCHER STATED IT APPEARED TO HIM THAT THE ACR Y ACFT WAS IN A STEEP R BANK AT THE TIME.
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.