37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 260692 |
Time | |
Date | 199401 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | atc facility : bvt |
State Reference | IN |
Altitude | msl bound lower : 31000 msl bound upper : 33000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zau tower : pie |
Operator | general aviation : corporate |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise other |
Flight Plan | IFR |
Person 1 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Experience | controller radar : 5 |
ASRS Report | 260692 |
Person 2 | |
Affiliation | government : faa |
Function | controller : radar |
Qualification | controller : radar |
Events | |
Anomaly | conflict : airborne less severe non adherence : required legal separation non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : unspecified |
Resolutory Action | none taken : detected after the fact |
Consequence | faa : investigated |
Miss Distance | horizontal : 27000 vertical : 1500 |
Supplementary | |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
Having relieved the previous controller, I continued working a moderate traffic period, using altitude separation between 2 aircraft in conflict. An adjacent sector requested a transfer of communication on aircraft #3, who was 5-10 mi north of my area of jurisdiction. The data block on this aircraft was displayed on my radar scope, overlapping the FL310 data block, and once I shipped aircraft #3, subsequently forgot about the aircraft at FL310 and climbed the FL290 aircraft through the protected airspace of the FL310 aircraft. The data block on aircraft #3 was initially dropped off the scope since it was outside my airspace. Someone re-displayed the aircraft to my sector, and unknown to them, it overlapped one of my data blocks, perhaps a computer patch preventing overlapped data blocks could prevent this from happening.
Original NASA ASRS Text
Title: ARTCC RADAR CTLR FORGOT ABOUT TFC AT FL310 DUE TO DATA BLOCK OVERLAP, CLBED A CPR JET THROUGH ALT OF ACR ACFT WITH LTSS.
Narrative: HAVING RELIEVED THE PREVIOUS CTLR, I CONTINUED WORKING A MODERATE TFC PERIOD, USING ALT SEPARATION BTWN 2 ACFT IN CONFLICT. AN ADJACENT SECTOR REQUESTED A TRANSFER OF COM ON ACFT #3, WHO WAS 5-10 MI N OF MY AREA OF JURISDICTION. THE DATA BLOCK ON THIS ACFT WAS DISPLAYED ON MY RADAR SCOPE, OVERLAPPING THE FL310 DATA BLOCK, AND ONCE I SHIPPED ACFT #3, SUBSEQUENTLY FORGOT ABOUT THE ACFT AT FL310 AND CLBED THE FL290 ACFT THROUGH THE PROTECTED AIRSPACE OF THE FL310 ACFT. THE DATA BLOCK ON ACFT #3 WAS INITIALLY DROPPED OFF THE SCOPE SINCE IT WAS OUTSIDE MY AIRSPACE. SOMEONE RE-DISPLAYED THE ACFT TO MY SECTOR, AND UNKNOWN TO THEM, IT OVERLAPPED ONE OF MY DATA BLOCKS, PERHAPS A COMPUTER PATCH PREVENTING OVERLAPPED DATA BLOCKS COULD PREVENT THIS FROM HAPPENING.
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.