 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier was left on a heading and, due to controller workload, conflicted with another air carrier resulting in less than standard separation.
| Attributes | |
| ACN | 139706 |
| Time | |
| Date | 199003 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : hto |
| State Reference | NY |
| Altitude | msl bound lower : 28000 msl bound upper : 28000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | artcc : zbw |
| Operator | common carrier : air carrier |
| Make Model Name | Medium Large Transport, Low Wing, 2 Turbojet Eng |
| Flight Phase | cruise other |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Large Transport, Low Wing, 3 Turbojet Eng |
| Flight Phase | descent other |
| Route In Use | enroute : on vectors |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Qualification | controller : radar |
| ASRS Report | 139706 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : flight data |
| Qualification | controller : radar |
| ASRS Report | 139702 |
| Events | |
| Anomaly | non adherence : required legal separation non adherence : published procedure |
| Independent Detector | atc equipment other atc equipment : unspecified other controllera |
| Resolutory Action | controller : issued new clearance |
| Consequence | Other |
| Miss Distance | horizontal : 18000 vertical : 0 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Sectors were combined with a period of heavy traffic, and numerous situations that needed to be resolved. Air carrier Y landing pud from rdu had been issued a 060 degree heading and was out of FL290 for FL250. Air carrier X out of bos to dca was on a present heading vector to avoid other traffic. I had forgotten to have air carrier X join J174 because when I went to issue clearance another situation required attention. Then the data block for air carrier X was covered by another aircraft. The conflict alert feature did not activate until after action had been taken to resolve the situation. Action taken was not in time to prevent operational error. Had sectors been split traffic would have been manageable and this error may not have happened.
Original NASA ASRS Text
Title: ACR WAS LEFT ON A HEADING AND, DUE TO CTLR WORKLOAD, CONFLICTED WITH ANOTHER ACR RESULTING IN LESS THAN STANDARD SEPARATION.
Narrative: SECTORS WERE COMBINED WITH A PERIOD OF HEAVY TFC, AND NUMEROUS SITUATIONS THAT NEEDED TO BE RESOLVED. ACR Y LNDG PUD FROM RDU HAD BEEN ISSUED A 060 DEG HDG AND WAS OUT OF FL290 FOR FL250. ACR X OUT OF BOS TO DCA WAS ON A PRESENT HDG VECTOR TO AVOID OTHER TFC. I HAD FORGOTTEN TO HAVE ACR X JOIN J174 BECAUSE WHEN I WENT TO ISSUE CLRNC ANOTHER SITUATION REQUIRED ATTN. THEN THE DATA BLOCK FOR ACR X WAS COVERED BY ANOTHER ACFT. THE CONFLICT ALERT FEATURE DID NOT ACTIVATE UNTIL AFTER ACTION HAD BEEN TAKEN TO RESOLVE THE SITUATION. ACTION TAKEN WAS NOT IN TIME TO PREVENT OPERROR. HAD SECTORS BEEN SPLIT TFC WOULD HAVE BEEN MANAGEABLE AND THIS ERROR MAY NOT HAVE HAPPENED.
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.