 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZLA controller failed to note an incorrect descent by an air carrier near R-2501; the reporter listing distractions as the primary causal factor.
| Attributes | |
| ACN | 871209 |
| Time | |
| Date | 201001 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZLA.ARTCC |
| State Reference | CA |
| Environment | |
| Light | Dusk |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR RIIVR2 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
We were working about seven to ten aircraft and the one in question was in bound for lax on the arrival from pgs to gramm for the RIIVR2 which takes the aircraft over R-2501. The aircraft was about the fourth in a string of about seven all given descent to FL290 because R-2501 was released FL290 and above. We didn't notice the aircraft descend to FL280; until he was in the center of the airspace; at which time another controller advised us. At this time the r-side climbed the aircraft back up to FL290. At this time we were being asked some questions about procedures regarding high altitude supersonic corridors by controllers from another area; which took our attention away from the scope. It is not excusable to let things distract us from the job at hand. However; if we weren't distracted we may have caught the aircraft descending below FL290. At the time the clearance was issued we both believe the read back and clearance were for FL290. We still should have caught the descent below FL290. Recommendation; we as controllers; should know not to ask questions to controllers at a working sector. More importantly as a controller working a sector we should not allow ourselves to be distract from our scope and the traffic we are responsible for. We should have directed the question to the supervisor or told them we would talk about it on a break. Luckily nothing adverse happened.
Original NASA ASRS Text
Title: ZLA controller failed to note an incorrect descent by an air carrier near R-2501; the reporter listing distractions as the primary causal factor.
Narrative: We were working about seven to ten aircraft and the one in question was in bound for LAX on the arrival from PGS to GRAMM for the RIIVR2 which takes the aircraft over R-2501. The aircraft was about the fourth in a string of about seven all given descent to FL290 because R-2501 was released FL290 and above. We didn't notice the aircraft descend to FL280; until he was in the center of the airspace; at which time another controller advised us. At this time the R-side climbed the aircraft back up to FL290. At this time we were being asked some questions about procedures regarding high altitude supersonic corridors by controllers from another area; which took our attention away from the scope. It is not excusable to let things distract us from the job at hand. However; if we weren't distracted we may have caught the aircraft descending below FL290. At the time the clearance was issued we both believe the read back and clearance were for FL290. We still should have caught the descent below FL290. Recommendation; we as controllers; should know not to ask questions to controllers at a working sector. More importantly as a controller working a sector we should not allow ourselves to be distract from our scope and the traffic we are responsible for. We should have directed the question to the supervisor or told them we would talk about it on a break. Luckily nothing adverse happened.
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.