 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZSU controller described a loss of separation event claiming fatigue as a primary causal factor.
| Attributes | |
| ACN | 936395 |
| Time | |
| Date | 201103 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZSU.ARTCC |
| State Reference | PR |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B757-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | B767-300 and 300 ER |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
I was working R4 with complex traffic [and] a coordinator was provided; because of the volume. After approximately an hour and a half working the sector; my fatigue increased and my scanning of the sector deteriorated. I had air carrier X northbound direct keeka at FL380 requesting FL400; but wanted to stay at FL380 for a while. Later on air carrier X was ready for higher and I assigned FL400. Air carrier Y checked in on frequency and I assigned a new beacon code. I did not realize that air carrier Y was coming over the same fix [as] air carrier X was leaving the airspace; and that he was at FL390. When air carrier Y popped up on radar I saw that he was coming over keeka and at FL390. Air carrier X was at FL390 climbing; approximately 10 NM head on. I turned both aircraft away from each other; but it was too late. They ended up approximately within 3 NM and maybe 500 ft [vertically of each other]. At the time of the incident; the coordinator was no longer available. Recommendation; the only solution I see here is to eliminate any factor that leads to [a] controller's fatigue. If staffing improves [and] rotation improves; fatigue will not be a factor; awareness is going to be maintained; and safety will not be compromised.
Original NASA ASRS Text
Title: ZSU Controller described a loss of separation event claiming fatigue as a primary causal factor.
Narrative: I was working R4 with complex traffic [and] a Coordinator was provided; because of the volume. After approximately an hour and a half working the sector; my fatigue increased and my scanning of the sector deteriorated. I had Air Carrier X northbound direct KEEKA at FL380 requesting FL400; but wanted to stay at FL380 for a while. Later on Air Carrier X was ready for higher and I assigned FL400. Air Carrier Y checked in on frequency and I assigned a new beacon code. I did not realize that Air Carrier Y was coming over the same fix [as] Air Carrier X was leaving the airspace; and that he was at FL390. When Air Carrier Y popped up on RADAR I saw that he was coming over KEEKA and at FL390. Air Carrier X was at FL390 climbing; approximately 10 NM head on. I turned both aircraft away from each other; but it was too late. They ended up approximately within 3 NM and maybe 500 FT [vertically of each other]. At the time of the incident; the Coordinator was no longer available. Recommendation; the only solution I see here is to eliminate any factor that leads to [a] Controller's fatigue. If staffing improves [and] rotation improves; fatigue will not be a factor; awareness is going to be maintained; and safety will not be compromised.
Data retrieved from NASA's ASRS site as of April 2012 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.