 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZID ARTCC controller accepts a point out on ZOB traffic and receives control to climb ZID traffic into ZOB airspace. ZID controller alleges the displayed data tag was not the aircraft he was supposed to climb in-reference-to and is involved in an operational error with a third aircraft he does not have displayed on his pvd.
| Attributes | |
| ACN | 404685 |
| Time | |
| Date | 199806 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : fdy |
| State Reference | OH |
| Altitude | msl bound lower : 31000 msl bound upper : 31000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zid artcc : zob |
| Operator | general aviation : corporate |
| Make Model Name | Learjet 31 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : intermediate altitude |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B727 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Experience | controller non radar : 3 controller radar : 5 |
| ASRS Report | 404685 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : published procedure other anomaly other |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | none taken : insufficient time |
| Consequence | Other |
| Miss Distance | horizontal : 24000 vertical : 1600 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
At approximately XA20 jun/tue/98, ZOB called me to inform me aircraft #1 was climbing to FL290 with my control respect a XXXX code. Aircraft #2 was the only data block displayed that could have possibly been traffic at FL310. Aircraft #1 was climbed. Separation was lost with the XXXX code. Aircraft #2 was the only data block (limited or full) within 20 mi and would be considered traffic. Based on the information I had available, I thought aircraft #2 was the traffic at FL310 (the XXXX code) since nothing else was observed. After ZOB called to ask the altitude of aircraft #1, an extensive search took place to locate the XXXX code. Approximately 5-6 mins later the XXXX code appeared 45-50 mi west of fdy VOR going west. That was the first time the radar team ever observed that code.
Original NASA ASRS Text
Title: ZID ARTCC CTLR ACCEPTS A POINT OUT ON ZOB TFC AND RECEIVES CTL TO CLB ZID TFC INTO ZOB AIRSPACE. ZID CTLR ALLEGES THE DISPLAYED DATA TAG WAS NOT THE ACFT HE WAS SUPPOSED TO CLB IN-REF-TO AND IS INVOLVED IN AN OPERROR WITH A THIRD ACFT HE DOES NOT HAVE DISPLAYED ON HIS PVD.
Narrative: AT APPROX XA20 JUN/TUE/98, ZOB CALLED ME TO INFORM ME ACFT #1 WAS CLBING TO FL290 WITH MY CTL RESPECT A XXXX CODE. ACFT #2 WAS THE ONLY DATA BLOCK DISPLAYED THAT COULD HAVE POSSIBLY BEEN TFC AT FL310. ACFT #1 WAS CLBED. SEPARATION WAS LOST WITH THE XXXX CODE. ACFT #2 WAS THE ONLY DATA BLOCK (LIMITED OR FULL) WITHIN 20 MI AND WOULD BE CONSIDERED TFC. BASED ON THE INFO I HAD AVAILABLE, I THOUGHT ACFT #2 WAS THE TFC AT FL310 (THE XXXX CODE) SINCE NOTHING ELSE WAS OBSERVED. AFTER ZOB CALLED TO ASK THE ALT OF ACFT #1, AN EXTENSIVE SEARCH TOOK PLACE TO LOCATE THE XXXX CODE. APPROX 5-6 MINS LATER THE XXXX CODE APPEARED 45-50 MI W OF FDY VOR GOING W. THAT WAS THE FIRST TIME THE RADAR TEAM EVER OBSERVED THAT CODE.
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.