 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZBW controller experienced operational error when failing to note correct data block altitude; subsequently issuing a conflicting altitude assignment.
| Attributes | |
| ACN | 881470 |
| Time | |
| Date | 201004 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZBW.ARTCC |
| State Reference | NH |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | None |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | EMB ERJ 190/195 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I relieved the previous controller at hto 31. Three aircraft data blocks were at the south end of the sector already switched to ZDC and the data blocks were in slant zero configuration with some overlapping. I moved one data block to see the altitudes of the aircraft and thought I observed FL300; FL280 and FL260. Air carrier Y was actually at FL360. Opposite direction by about 15 miles was air carrier X at FL370 destined for pvd. As air carrier X crossed the sector boundary; I descended the aircraft to FL310 believing he was free of conflict to that altitude. Shortly afterward air carrier X stated he was climbing to FL370. I acknowledge the transmission and observed the confict with air carrier Y. The conflict alert engaged at this time as well.
Original NASA ASRS Text
Title: ZBW controller experienced operational error when failing to note correct data block altitude; subsequently issuing a conflicting altitude assignment.
Narrative: I relieved the previous controller at HTO 31. Three aircraft data blocks were at the South end of the sector already switched to ZDC and the data blocks were in slant zero configuration with some overlapping. I moved one data block to see the altitudes of the aircraft and thought I observed FL300; FL280 and FL260. ACR Y was actually at FL360. Opposite direction by about 15 miles was ACR X at FL370 destined for PVD. As ACR X crossed the sector boundary; I descended the aircraft to FL310 believing he was free of conflict to that altitude. Shortly afterward ACR X stated he was climbing to FL370. I acknowledge the transmission and observed the confict with ACR Y. The conflict alert engaged at this time as well.
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.