 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZNY controller inadvertently drops data block on crossing traffic, fails to remember potential conflict, resulting in operational error.
| Attributes | |
| ACN | 625333 |
| Time | |
| Date | 200407 |
| Day | Fri |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | navaid : sfk.vor |
| State Reference | PA |
| Altitude | msl bound lower : 31000 msl bound upper : 33000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zny.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Gulfstream 100 [G100] (IAI 1125 Astra) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : level |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zny.artcc |
| Operator | general aviation : corporate |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise : enroute altitude change cruise : level descent : intermediate altitude |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar controller : military |
| Experience | controller military : 3 controller radar : 32 controller time certified in position1 : 32 |
| ASRS Report | 625333 |
| Person 2 | |
| Affiliation | company : corporate |
| Function | flight crew : captain oversight : pic |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 27000 vertical : 400 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Aircraft X (the astrojet) was en route to cyyz. Aircraft Y (the beechjet) was en route to teb. Traffic had been heavy due to WX. Data blocks were overlapping. When I moved aircraft X data block I dropped it by mistake, but I decided to not bring it back up. Aircraft Y was at FL330 with crossing traffic, I started him down to FL270 forgetting about aircraft X at FL310 whose limited data was covered by another data block. I noticed the mistake just as the conflict alert went off when aircraft Y passed through FL314. Aircraft X was north of aircraft Y but maybe not 5 mi from him.
Original NASA ASRS Text
Title: ZNY CTLR INADVERTENTLY DROPS DATA BLOCK ON XING TFC, FAILS TO REMEMBER POTENTIAL CONFLICT, RESULTING IN OPERROR.
Narrative: ACFT X (THE ASTROJET) WAS ENRTE TO CYYZ. ACFT Y (THE BEECHJET) WAS ENRTE TO TEB. TFC HAD BEEN HVY DUE TO WX. DATA BLOCKS WERE OVERLAPPING. WHEN I MOVED ACFT X DATA BLOCK I DROPPED IT BY MISTAKE, BUT I DECIDED TO NOT BRING IT BACK UP. ACFT Y WAS AT FL330 WITH XING TFC, I STARTED HIM DOWN TO FL270 FORGETTING ABOUT ACFT X AT FL310 WHOSE LIMITED DATA WAS COVERED BY ANOTHER DATA BLOCK. I NOTICED THE MISTAKE JUST AS THE CONFLICT ALERT WENT OFF WHEN ACFT Y PASSED THROUGH FL314. ACFT X WAS N OF ACFT Y BUT MAYBE NOT 5 MI FROM HIM.
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.