 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZME enroute controller reported a loss of separation occurred between two transport aircraft. Cpdlc testing was cited as contributing to the error.
| Attributes | |
| ACN | 1584801 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZME.ARTCC |
| State Reference | TN |
| Aircraft 1 | |
| Make Model Name | B757-200 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 24 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Loss of separation occurred between aircraft X and aircraft Y. Controller pilot data link communications (cpdlc) testing had just begun. This was my first time using it. I uplinked a climb message to aircraft X to climb to FL300 and handed him off to the R21 controller leaving FL195 climbing to FL300. The R21 controller did catch that aircraft X was climbing to FL300. Aircraft Y was being worked by R21 controller descending to FL240. The R21 [controller] realized aircraft X was climbing to FL300 after the aircraft had been handed off and switched to the R27 controller. The R21 controller then stopped [aircraft X] at FL250 and turned the aircraft and called traffic. Separation was lost. Aircraft X should have been climbed to FL230 by me.
Original NASA ASRS Text
Title: ZME Enroute Controller reported a loss of separation occurred between two transport aircraft. CPDLC testing was cited as contributing to the error.
Narrative: Loss of separation occurred between Aircraft X and Aircraft Y. Controller Pilot Data Link Communications (CPDLC) testing had just begun. This was my first time using it. I uplinked a climb message to Aircraft X to climb to FL300 and handed him off to the R21 Controller leaving FL195 climbing to FL300. The R21 Controller did catch that Aircraft X was climbing to FL300. Aircraft Y was being worked by R21 Controller descending to FL240. The R21 [Controller] realized Aircraft X was climbing to FL300 after the aircraft had been handed off and switched to the R27 Controller. The R21 Controller then stopped [Aircraft X] at FL250 and turned the aircraft and called traffic. Separation was lost. Aircraft X should have been climbed to FL230 by me.
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.