 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA radar associate controller described operational error at FL200 as both he and the radar controller failed to realize an aircraft was not climbing to the altitude displayed in the data block.
| Attributes | |
| ACN | 721556 |
| Time | |
| Date | 200612 |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | atc facility : zla.artcc |
| State Reference | CA |
| Altitude | msl single value : 20000 |
| Environment | |
| Flight Conditions | VMC |
| Light | Night |
| Aircraft 1 | |
| Controlling Facilities | artcc : zla.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Route In Use | departure : on vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | artcc : zla.artcc |
| Operator | common carrier : air carrier |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Route In Use | departure sid : n/s |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Qualification | controller : developmental |
| Experience | controller military : 7 controller supervisory : 1 |
| ASRS Report | 721556 |
| Person 2 | |
| Affiliation | government : faa |
| Function | controller : radar |
| Events | |
| Anomaly | conflict : airborne less severe non adherence : required legal separation |
| Independent Detector | atc equipment : conflict alert other controllera |
| Resolutory Action | flight crew : took evasive action |
| Consequence | faa : investigated |
| Miss Distance | horizontal : 24000 vertical : 600 |
| Supplementary | |
| Problem Areas | ATC Human Performance |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
I was the radar associate at the time of the error. I did not notice the potential conflict until my r-side controller caught it and began issuing corrective instructions. I saw FL230 in the data block of the B737 but did not notice he stopped climbing at FL200. At the time the radar controller began issuing instructions I was debating whether or not to get control of a pilatus I took radar on that was sbound from sector 18 (northeast of lax). I was also periodically scanning my departure list for bad or incorrect rtes/altitudes. I believe perceived pilot actions was cause a of this error because both the radar controller and I were expecting the aircraft to climb to FL230 as his data block indicated.
Original NASA ASRS Text
Title: ZLA RADAR ASSOCIATE CTLR DESCRIBED OPERROR AT FL200 AS BOTH HE AND THE RADAR CTLR FAILED TO REALIZE AN ACFT WAS NOT CLBING TO THE ALT DISPLAYED IN THE DATA BLOCK.
Narrative: I WAS THE RADAR ASSOCIATE AT THE TIME OF THE ERROR. I DID NOT NOTICE THE POTENTIAL CONFLICT UNTIL MY R-SIDE CTLR CAUGHT IT AND BEGAN ISSUING CORRECTIVE INSTRUCTIONS. I SAW FL230 IN THE DATA BLOCK OF THE B737 BUT DID NOT NOTICE HE STOPPED CLBING AT FL200. AT THE TIME THE RADAR CTLR BEGAN ISSUING INSTRUCTIONS I WAS DEBATING WHETHER OR NOT TO GET CTL OF A PILATUS I TOOK RADAR ON THAT WAS SBOUND FROM SECTOR 18 (NE OF LAX). I WAS ALSO PERIODICALLY SCANNING MY DEP LIST FOR BAD OR INCORRECT RTES/ALTS. I BELIEVE PERCEIVED PLT ACTIONS WAS CAUSE A OF THIS ERROR BECAUSE BOTH THE RADAR CTLR AND I WERE EXPECTING THE ACFT TO CLB TO FL230 AS HIS DATA BLOCK INDICATED.
Data retrieved from NASA's ASRS site as of January 2009 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.