 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Denver TRACON controller reported a loss of separation when an aircraft on a RNAV route descended below a crossing restriction; responding to a RA for traffic the restriction was in place for.
| Attributes | |
| ACN | 1583951 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | D01.TRACON |
| State Reference | CO |
| Environment | |
| Light | Night |
| Aircraft 1 | |
| Make Model Name | B737-700 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Final Approach |
| Route In Use | Other Instrument Approach STAR TELLR TWO |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Altitude Crossing Restriction Not Met Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy |
Narrative:
I was working final for roughly 40 minutes and the rush was winding down. The last four or five arrivals all came in on the tellr arrival and all but one was cleared for the ILS to runway 35L off of the tellr arrival. The only one that wasn't was vectored. Aircraft X was the fourth one in the string of tellr's and was cleared the same way every other plane was cleared and was issued traffic that would be underneath them at 10;000 ft for the west complex runways. Aircraft X was observed vacating 11;000 ft; which is the altitude he should've been at until cruup on the localizer for that runway; so I issued a climb to 11;000 ft and a heading of 010 to intercept the localizer. When aircraft X was quizzed about what happened and why they were at an altitude they were leaving the altitude that they shouldn't have been; aircraft X responded that they were responding to a TCAS RA. Aircraft X was then issued the brasher. I don't really have a recommendation other than we should expect more from the pilot's tasked with flying numerous people all over the world. This situation should never happen since the airplane is flying an RNAV route and RNAV is designed to separate airplanes.
Original NASA ASRS Text
Title: Denver TRACON controller reported a loss of separation when an aircraft on a RNAV route descended below a crossing restriction; responding to a RA for traffic the restriction was in place for.
Narrative: I was working final for roughly 40 minutes and the rush was winding down. The last four or five arrivals all came in on the TELLR Arrival and all but one was cleared for the ILS to Runway 35L off of the TELLR Arrival. The only one that wasn't was vectored. Aircraft X was the fourth one in the string of TELLR's and was cleared the same way every other plane was cleared and was issued traffic that would be underneath them at 10;000 FT for the west complex runways. Aircraft X was observed vacating 11;000 FT; which is the altitude he should've been at until CRUUP on the localizer for that runway; so I issued a climb to 11;000 FT and a heading of 010 to intercept the localizer. When Aircraft X was quizzed about what happened and why they were at an altitude they were leaving the altitude that they shouldn't have been; Aircraft X responded that they were responding to a TCAS RA. Aircraft X was then issued the Brasher. I don't really have a recommendation other than we should expect more from the pilot's tasked with flying numerous people all over the world. This situation should never happen since the airplane is flying an RNAV route and RNAV is designed to separate airplanes.
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.