 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAB controller voiced concern regarding inbounds from mmzt that are sometimes stacked; all inbound to phx; the reporter made note of having limited airspace to provide needed in-trail spacing.
| Attributes | |
| ACN | 986017 |
| Time | |
| Date | 201112 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Aircraft 1 | |
| Make Model Name | A321 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Supervisor / CIC |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
Three air carriers all came from mazatlan center stacked on top of one another and all three aircraft were landing at phx. This sector has less than 30 miles to accomplish their vectoring and they need to blend the stream coming from the mazatlan center with the heavier kooly stream that comes from the east. There is restricted airspace to the east of tus and sua airspace to the west of it; meaning the sector can't vector until the aircraft are over the tus VOR. The complexity on the low sector (ZAB 46) is extremely high and it makes it nearly impossible to achieve adequate spacing when aircraft come over without any traffic management initiatives. The sector also had a restriction in place where they had to give mazatlan center 20 miles in trail regardless of destination and altitude. Recommendation; ZAB tmu says it's difficult for them to have any traffic management initiatives in place to help the sectors and they say it's difficult to have the tsd display enough information to place proper initiatives. Because of this; I propose an LOA with mmzt center specifying all phx terminal aircraft come over from mmzt at or above FL320 and 10 mi regardless of altitude and have to be established on proper routes prior to vylla.
Original NASA ASRS Text
Title: ZAB Controller voiced concern regarding inbounds from MMZT that are sometimes stacked; all inbound to PHX; the reporter made note of having limited airspace to provide needed in-trail spacing.
Narrative: Three air carriers all came from Mazatlan Center stacked on top of one another and all three aircraft were landing at PHX. This sector has less than 30 miles to accomplish their vectoring and they need to blend the stream coming from the Mazatlan Center with the heavier KOOLY stream that comes from the east. There is restricted airspace to the east of TUS and SUA airspace to the west of it; meaning the sector can't vector until the aircraft are over the TUS VOR. The complexity on the low sector (ZAB 46) is extremely high and it makes it nearly impossible to achieve adequate spacing when aircraft come over without any traffic management initiatives. The sector also had a restriction in place where they had to give Mazatlan Center 20 miles in trail regardless of destination and altitude. Recommendation; ZAB TMU says it's difficult for them to have any traffic management initiatives in place to help the sectors and they say it's difficult to have the TSD display enough information to place proper initiatives. Because of this; I propose an LOA with MMZT Center specifying all PHX terminal aircraft come over from MMZT at or above FL320 and 10 MI regardless of altitude and have to be established on proper routes prior to VYLLA.
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.