 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Distracted by trying to confirm landing assured or IFR cancellation; a ZID controller failed to observe a developing MOA airspace incursion.
| Attributes | |
| ACN | 1040459 |
| Time | |
| Date | 201210 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZID.ARTCC |
| State Reference | IN |
| Aircraft 1 | |
| Make Model Name | SR22 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Cessna 425/441 Conquest I/Conquest II |
| Flight Plan | VFR |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy |
Narrative:
A cessna 441 was on my frequency trying to land VFR at ser; but flew over the field at 3;000 ft and still couldn't see the runway. So I vectored the cessna 441 southeast of the field about 15 miles for the GPS runway 32 approach to ser. When I turned the aircraft to the IAF (zekam) he reported the field insight and cancelled 15-18 miles southeast of ser; I questioned his transmission but he insisted that he had the field insight. While this was going on; I took the hand off on SR22 at 8;000 ft. I was still questioning in my head if the cessna 441 had actually seen ser or another runway close by. The controller in charge and I were in the process of trying to confirm [that] cessna 441 landed at ser when SR22 violated racer a/B MOA at 8;000 ft. The status board was up to date and it showed the racer a/B going hot. The racer MOA should be depicted on our low altitude maps; before an aircraft goes through the lateral confines of a restricted/MOA. I always double check and make sure it is cold; and if it isn't on our maps we tend to forget about it.
Original NASA ASRS Text
Title: Distracted by trying to confirm landing assured or IFR cancellation; a ZID Controller failed to observe a developing MOA airspace incursion.
Narrative: A Cessna 441 was on my frequency trying to land VFR at SER; but flew over the field at 3;000 FT and still couldn't see the runway. So I vectored the Cessna 441 southeast of the field about 15 miles for the GPS Runway 32 approach to SER. When I turned the aircraft to the IAF (ZEKAM) he reported the field insight and cancelled 15-18 miles southeast of SER; I questioned his transmission but he insisted that he had the field insight. While this was going on; I took the hand off on SR22 at 8;000 FT. I was still questioning in my head if the Cessna 441 had actually seen SER or another runway close by. The CIC and I were in the process of trying to confirm [that] Cessna 441 landed at SER when SR22 violated Racer A/B MOA at 8;000 FT. The status board was up to date and it showed the Racer A/B going hot. The Racer MOA should be depicted on our low altitude maps; before an aircraft goes through the lateral confines of a Restricted/MOA. I always double check and make sure it is cold; and if it isn't on our maps we tend to forget about it.
Data retrieved from NASA's ASRS site as of July 2013 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.