37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1153453 |
Time | |
Date | 201402 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZMA.ARTCC |
State Reference | FL |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Cessna Citation Undifferentiated or Other Model |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Radar 29 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
During a very busy and complex traffic period I issued an air carrier a descent clearance to get below traffic and land at ZZZ. At the time that I issued the clearance it appeared that I had lateral separation and that there was enough room for the air carrier to descend from FL370 through a business jet at FL360. The sector was too busy for me to go back and reassess the descent rate and the lateral separation. My d-side and I were extremely busy and did not use these tools; the polygon/halo. The frequency was extremely congested with two sectors being combined. My d-side was extremely busy keeping up with manual coordination and hand-offs to and from a foreign facility; dealing with ade and verifying all the redundant information with multiple duplicated information. I was busy separating and controlling numerous other situations and missed this one conflict. The center NAS monitors displayed the traffic flow management system (tfms) was red for at least 30 minutes and I had over 21 data blocks and over 25 aircraft on frequency. My d-side had a page and half on the en route information display system (erids) and a bay full of strips as well as a stack on the printer.I would recommend;a. Improve automated data exchange (ade) and ICAO flight plan filing to reduce the workload of sectors dealing with ade. Having to verify numerous accounts of inaccurate; duplicate or erroneous information during peak traffic; put an insurmountable amount of extra workload on sectors dealing with ade.B. The supervisor should walk around the sectors and observe the volume on the erids; the number of strips in the bay and coming off the printer and not just rely on the center NAS monitors; and traffic flow management system (tfms) displays. The sectors should be split early enough to reduce frequency congestion during peak traffic which allows for a smaller range on the radar display; so you can see closely all traffic situations.C. Distribute the workload and complexity.D. Reduce the coordination for the d-side. Assign an a-side assistant to help the d-side so the d-side can assist the r-side and not have all the down time coordinating and stuffing strips; and dealing with ade issues. Assign a tracker to assist the r-side.
Original NASA ASRS Text
Title: ZMA Center Controller descended aircraft in too close proximity of another aircraft due to the fact that he thought he would have lateral separation. Sector was busy and Controller did not have time to re-check the separation.
Narrative: During a very busy and complex traffic period I issued an air carrier a descent clearance to get below traffic and land at ZZZ. At the time that I issued the clearance it appeared that I had lateral separation and that there was enough room for the air carrier to descend from FL370 through a business jet at FL360. The sector was too busy for me to go back and reassess the descent rate and the lateral separation. My D-side and I were extremely busy and did not use these tools; the polygon/Halo. The frequency was extremely congested with two sectors being combined. My D-side was extremely busy keeping up with manual coordination and hand-offs to and from a foreign facility; dealing with ADE and verifying all the redundant information with multiple duplicated information. I was busy separating and controlling numerous other situations and missed this one conflict. The Center NAS Monitors displayed the Traffic Flow Management System (TFMS) was red for at least 30 minutes and I had over 21 Data blocks and over 25 aircraft on frequency. My D-side had a page and half on the En Route Information Display System (ERIDS) and a bay full of strips as well as a stack on the printer.I would recommend;A. Improve Automated Data Exchange (ADE) and ICAO flight plan filing to reduce the workload of sectors dealing with ADE. Having to verify numerous accounts of inaccurate; duplicate or erroneous information during peak traffic; put an insurmountable amount of extra workload on sectors dealing with ADE.B. The Supervisor should walk around the sectors and observe the volume on the ERIDS; the number of strips in the bay and coming off the printer and not just rely on the Center NAS Monitors; and Traffic Flow Management System (TFMS) displays. The sectors should be split early enough to reduce frequency congestion during peak traffic which allows for a smaller range on the radar display; so you can see closely all traffic situations.C. Distribute the workload and complexity.D. Reduce the coordination for the D-side. Assign an A-side assistant to help the D-side so the D-side can assist the R-side and not have all the down time coordinating and stuffing strips; and dealing with ADE issues. Assign a tracker to assist the R-side.
Data retrieved from NASA's ASRS site 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.