37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 965119 |
Time | |
Date | 201108 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZHU.ARTCC |
State Reference | TX |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | No Aircraft |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was briefed that W228C and W228B were active from FL190-210. I called victoria low controller and he said he had no knowledge of them being active and that they hadn't been active since he sat down. I only called him because my d-side happened to look at the active airspace on uret's gpd and we saw it wasn't activated there. I have been reporting problems with the coordination of W228 directly to management for several years. I would estimate that 80% of the time when I work either ocean west or offshore west; something to do with that airspace will be wrong. For example; showing [that] the airspace [is] active when it is not; showing no airspace activation when in fact airspace is active; showing the airspace active at altitudes other than what my data block shows. 1) I have already identified a gap in procedures where no one is required to communicate altitudes released from offshore for W228A to victoria low. This gap in procedure has not been resolved by the facility. 2) coordination between all involved parties is failing and I think controllers and flms need to be held accountable to ensure the status of all saas are accurate.
Original NASA ASRS Text
Title: ZHU Controller voiced concern regarding the non-adherence to LOA directives concerning the operation of W228C and W228B.
Narrative: I was briefed that W228C and W228B were active from FL190-210. I called Victoria Low Controller and he said he had no knowledge of them being active and that they hadn't been active since he sat down. I only called him because my D-Side happened to look at the active airspace on URET's GPD and we saw it wasn't activated there. I have been reporting problems with the coordination of W228 directly to Management for several years. I would estimate that 80% of the time when I work either Ocean West or Offshore West; something to do with that airspace will be wrong. For example; showing [that] the airspace [is] active when it is not; showing no airspace activation when in fact airspace is active; showing the airspace active at altitudes other than what my data block shows. 1) I have already identified a gap in procedures where no one is required to communicate altitudes released from Offshore for W228A to Victoria Low. This gap in procedure has not been resolved by the facility. 2) Coordination between all involved parties is failing and I think controllers and FLMs need to be held accountable to ensure the status of all SAAs are accurate.
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.