37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1626301 |
Time | |
Date | 201903 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | CLT.TRACON |
State Reference | NC |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | STAR RNAV |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 10.0 |
Events | |
Anomaly | ATC Issue All Types Deviation - Altitude Crossing Restriction Not Met Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Speed All Types |
Narrative:
While working the arrival radar position the first and only arrival I took a handoff on was aircraft X. He appeared a little high but the crossing fixes for the center don't lock them down to anything other than at or above 12;000 feet. He was around 16;000 feet 2 miles from the fix. The aircraft checked on inside my airspace and immediately stated he was unable to meet any speed or altitude restrictions on the arrival due to center taking him off the arrival and giving him a higher rate of speed to the fix. Then he advised me he was assigned descend via clearance over the fix and switched all in the same transmission. Thank goodness I had no other traffic because this required multiple vectors and hard descents to avoid others airspace and set him up for a stable approach. Zero coordination was done with me from the center per usual.we at clt see this every day. Most controllers just complain really loud about this in the operation/break room but are unwilling to spend time filling out the [reports]. Most supervisors are the same way and don't do the [reporting] on it. I was this way for a while but this happens to me multiple times a day and it's super frustrating. We are in a constant jam not being coordinated with and with guys high and fast on a short side arrival at the 6th busiest airport; it's unacceptable. Some days we even have to have our tmc's (traffic management controllers) request to give airplanes hard crossing altitudes to make it workable. This doesn't help the airlines and even makes it harder for the center due to phraseology; yet it's the only way to make it work sometimes. We need to either have the procedure to be a hard crossing altitude (the airlines won't like this because it does away with their profile descent); have the center be better at assigning these profile descents earlier and force them to be established in their airspace (won't happen without your help); or redesign the arrivals fully (best option but will cost a lot of money which won't be approved.) we would like to take these lessons learned from the 4 or 5 years we have had this and use this to adjust how things run. This would be quicker and could easily allow for more aircraft in our airspace without these issues. All we need is to have ZTL held accountable or at minimum coordinate with us when they mess up. At that point from time to time they may have to eat an airplane or two. If tower makes a mistake and launches 4 of the same transition back to back to back to back I don't just give them all normal speed and fixes further along their route and not coordinate. We fix these issues we just ask that they do a better job.
Original NASA ASRS Text
Title: CLT TRACON Controller reported an arriving aircraft was handed off to them that was unable to comply with any of the restrictions on the RNAV Arrival due to being left high and fast.
Narrative: While working the Arrival Radar position the first and only arrival I took a handoff on was Aircraft X. He appeared a little high but the crossing fixes for the center don't lock them down to anything other than at or above 12;000 feet. He was around 16;000 feet 2 miles from the fix. The aircraft checked on inside my airspace and immediately stated he was unable to meet any speed or altitude restrictions on the arrival due to Center taking him off the arrival and giving him a higher rate of speed to the fix. Then he advised me he was assigned descend via clearance over the fix and switched all in the same transmission. Thank goodness I had no other traffic because this required multiple vectors and hard descents to avoid others airspace and set him up for a stable approach. Zero coordination was done with me from the Center per usual.We at CLT see this every day. Most controllers just complain really loud about this in the operation/break room but are unwilling to spend time filling out the [reports]. Most Supervisors are the same way and don't do the [reporting] on it. I was this way for a while but this happens to me multiple times a day and it's super frustrating. We are in a constant jam not being coordinated with and with guys high and fast on a short side arrival at the 6th busiest airport; it's unacceptable. Some days we even have to have our TMC's (Traffic Management Controllers) request to give airplanes hard crossing altitudes to make it workable. This doesn't help the airlines and even makes it harder for the center due to phraseology; yet it's the only way to make it work sometimes. We need to either have the procedure to be a hard crossing altitude (the airlines won't like this because it does away with their profile descent); have the Center be better at assigning these profile descents earlier and force them to be established in their airspace (won't happen without your help); or redesign the arrivals fully (best option but will cost a lot of money which won't be approved.) We would like to take these lessons learned from the 4 or 5 years we have had this and use this to adjust how things run. This would be quicker and could easily allow for more aircraft in our airspace without these issues. All we need is to have ZTL held accountable or at minimum coordinate with us when they mess up. At that point from time to time they may have to eat an airplane or two. If tower makes a mistake and launches 4 of the same transition back to back to back to back I don't just give them all normal speed and fixes further along their route and not coordinate. We fix these issues we just ask that they do a better job.
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.