 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA controller described a loss of separation event when failing to realized the ATC issued altitude was in fact different from the entered data block altitude information.
| Attributes | |
| ACN | 943602 |
| Time | |
| Date | 201104 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | Learjet 35 |
| Flight Phase | Climb |
| 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:
Aircraft Y was level at FL320. Aircraft X was level at FL290. I climbed aircraft X to FL320; meaning to climb him to FL310. He read back FL320 and it was put correctly in the data block as FL320. A minute later; I noticed the data block said FL320; and I changed it to FL310 thinking that it was put in incorrectly by me or the d-side. I neglected to verify the assigned altitude with aircraft X. Another minute later; aircraft Y announced that they were responding to a TCAS resolution advisory and climbed to FL330. That's when I noticed that aircraft X was through FL310 for FL320. I turned aircraft X 30 degrees to the right to try and help the situation but separation was already lost. I recommend that I personally do my best to make no assumptions as to what I believe to be true and always verify when something looks wrong. It was my mistake and it could have developed into a bad situation; but thankfully; it did not.
Original NASA ASRS Text
Title: ZLA Controller described a loss of separation event when failing to realized the ATC issued altitude was in fact different from the entered Data Block altitude information.
Narrative: Aircraft Y was level at FL320. Aircraft X was level at FL290. I climbed Aircraft X to FL320; meaning to climb him to FL310. He read back FL320 and it was put correctly in the Data Block as FL320. A minute later; I noticed the Data Block said FL320; and I changed it to FL310 thinking that it was put in incorrectly by me or the D-Side. I neglected to verify the assigned altitude with Aircraft X. Another minute later; Aircraft Y announced that they were responding to a TCAS resolution advisory and climbed to FL330. That's when I noticed that Aircraft X was through FL310 for FL320. I turned Aircraft X 30 degrees to the right to try and help the situation but separation was already lost. I recommend that I personally do my best to make no assumptions as to what I believe to be true and always verify when something looks wrong. It was my mistake and it could have developed into a bad situation; but thankfully; it did not.
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.