 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Hts TRACON controller reported of an airspace violation with a VFR aircraft and a MOA. The aircraft came too close to the airspace. The controller did not turn on the MOA display on the scope which is something he normally did. Controller believes this led to him forgetting the airspace was hot and the possible airspace violation.
| Attributes | |
| ACN | 1326215 |
| Time | |
| Date | 201601 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | HTS.TRACON |
| State Reference | WV |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (mon) 8 |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was working north and south radar combined like always. I was informed by the pike sector that the buckeye and brush creek moas would be active beginning at XA35Z. I informed the local controller; and adjusted the memory aid to reflect the MOA status. I normally also turn on the MOA map on the radar scope to give myself a more obvious reminder; but I failed to do so on this occasion. At about XA47Z; aircraft X made an initial call requesting IFR to lex at 040. I radar identified aircraft X; and told the pilot to maintain VFR. I then pointed the aircraft out to the pike sector; who approved direct at 040. I then cleared aircraft X direct to lex at 040. I believe I had around 1.5 miles separation from the brush creek MOA at the closest point. I realized what I had done about 45 minutes later when pike sector called back to advise that the moas were going 'cold.'I failed to maintain my normal procedure of turning on the MOA map when they are active. In the future; I need to be more diligent in my own standard procedure to avoid a similar situation from occurring.
Original NASA ASRS Text
Title: HTS TRACON Controller reported of an airspace violation with a VFR aircraft and a MOA. The aircraft came too close to the airspace. The Controller did not turn on the MOA display on the scope which is something he normally did. Controller believes this led to him forgetting the airspace was hot and the possible airspace violation.
Narrative: I was working North and South radar combined like always. I was informed by the PIKE sector that the Buckeye and Brush Creek MOAs would be active beginning at XA35Z. I informed the local controller; and adjusted the memory aid to reflect the MOA status. I normally also turn on the MOA map on the radar scope to give myself a more obvious reminder; but I failed to do so on this occasion. At about XA47Z; Aircraft X made an initial call requesting IFR to LEX at 040. I RADAR identified Aircraft X; and told the pilot to maintain VFR. I then pointed the aircraft out to the PIKE sector; who approved direct at 040. I then cleared Aircraft X direct to LEX at 040. I believe I had around 1.5 miles separation from the Brush Creek MOA at the closest point. I realized what I had done about 45 minutes later when PIKE sector called back to advise that the MOAs were going 'cold.'I failed to maintain my normal procedure of turning on the MOA map when they are active. In the future; I need to be more diligent in my own standard procedure to avoid a similar situation from occurring.
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.