37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1214030 |
Time | |
Date | 201410 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | HCF.TRACON |
State Reference | HI |
Aircraft 1 | |
Make Model Name | Globemaster (C-17) |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Person 1 | |
Function | Traffic Management |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Radar 25 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
A C17; inbound to hnl from the north. Controller at sector 2/6/8 noticed a target at FL350 more than 200 nm south in warning area W-188/rainbow. W-188/rainbow extends to the northern boundary of hcf. The controller called pmrf [pacific missile range facility] to inquire about the target. Pmrf said it was a uav. The controller then asked the flm if W-188/rainbow was active because it was not reflected on the sia board. The flm asked me and I said that is was not active. He told me about the uav. I double-checked the special-use airspace binder and realized that the airspace was scheduled to be in use from XXXA30-XYXB00 [12 hour span]; sfc to unlimited. I immediately called pmrf and told them about the mistake and got a point-out for the aircraft for the rest of him transition through W-188/rainbow. Contributing factors: pmrf had faxed us at least 3-4 changes to their weekly schedule during the current week due to mission/airspace changes. I failed to notice that rainbow was listed on the facsimile and did not post it accordingly on the sia board. Being as we only have two traffic management coordinator (tmc)'s here at the facility; I was my own relief from the previous day and believing that I had done all the duties correct the day before; I didn't check the airspace schedule. Discussed with fellow tmc; operations manager (OM) and front line manager (flm) and I recommended that we highlight rainbow on the weekly fax from pmrf to prevent us from making the same mistake again.
Original NASA ASRS Text
Title: HCF TMU Controller reports failing to note the active status of W-188 until queried by another Controller about a target at FL350 in the Warning Area. PMRF is contacted and the target is identified as a UAV. Multiple faxes from PMRF changing the active times resulted in the oversight.
Narrative: A C17; inbound to HNL from the north. Controller at sector 2/6/8 noticed a target at FL350 more than 200 nm south in warning area W-188/RAINBOW. W-188/RAINBOW extends to the northern boundary of HCF. The controller called PMRF [Pacific Missile Range Facility] to inquire about the target. PMRF said it was a UAV. The controller then asked the FLM if W-188/RAINBOW was active because it was not reflected on the SIA board. The FLM asked me and I said that is was not active. He told me about the UAV. I double-checked the special-use airspace binder and realized that the airspace was scheduled to be in use from XXXA30-XYXB00 [12 HOUR SPAN]; SFC to UNLIMITED. I immediately called PMRF and told them about the mistake and got a point-out for the aircraft for the rest of him transition through W-188/RAINBOW. Contributing factors: PMRF had faxed us at least 3-4 changes to their weekly schedule during the current week due to mission/airspace changes. I failed to notice that RAINBOW was listed on the FAX and did not post it accordingly on the SIA board. Being as we only have two Traffic Management Coordinator (TMC)'s here at the facility; I was my own relief from the previous day and believing that I had done all the duties correct the day before; I didn't check the airspace schedule. Discussed with fellow TMC; Operations Manager (OM) and Front Line Manager (FLM) and I recommended that we highlight RAINBOW on the weekly fax from PMRF to prevent us from making the same mistake again.
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.