 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A possible airspace incursion event when coordination regarding activation of a restricted area was not timely.
| Attributes | |
| ACN | 978504 |
| Time | |
| Date | 201111 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Flight Phase | Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Function | Enroute |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I was conducting radar ojti. W174 and W465 had been active all day. Aircraft X was climbing southwest bound with crossing traffic. We were advised that W465 was no longer active. When the status board was updated; I observed W174c was not being shown active. I questioned this and it was confirmed that it was cold. With this information separation techniques were discussed with my trainee that would allow aircraft X to safely climb above traffic. It was decided to place aircraft X on a heading that would remain clear of traffic. This became possible with W174c being inactive as the vector would put the aircraft in the warning area. When vertical separation was established; aircraft X was cleared on course. We were offered a break and during the relief briefing it was stated W174c was cold. The d-side heard this and stated it was going active. The time of activation was questioned and it was very close to the current time. Aircraft X was issued a vector to expedite clearing the area and the d-side called the mru to cap the airspace below aircraft X. I believe this was done timely but I am not positive. Recommend ZMA have procedures in place for sua activation. When correctly followed this should be sufficient.
Original NASA ASRS Text
Title: A possible airspace incursion event when coordination regarding activation of a restricted area was not timely.
Narrative: I was conducting RADAR OJTI. W174 and W465 had been active all day. Aircraft X was climbing Southwest bound with crossing traffic. We were advised that W465 was no longer active. When the status board was updated; I observed W174c was not being shown active. I questioned this and it was confirmed that it was cold. With this information separation techniques were discussed with my trainee that would allow Aircraft X to safely climb above traffic. It was decided to place Aircraft X on a heading that would remain clear of traffic. This became possible with W174c being inactive as the vector would put the aircraft in the warning area. When vertical separation was established; Aircraft X was cleared on course. We were offered a break and during the relief briefing it was stated W174c was cold. The D-Side heard this and stated it was going active. The time of activation was questioned and it was very close to the current time. Aircraft X was issued a vector to expedite clearing the area and the D-Side called the MRU to cap the airspace below Aircraft X. I believe this was done timely but I am not positive. Recommend ZMA have procedures in place for SUA activation. When correctly followed this should be sufficient.
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.