 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Sdf TRACON controller reported being distracted and failed to notice an aircraft entering a higher MVA.
| Attributes | |
| ACN | 1515470 |
| Time | |
| Date | 201801 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | SDF.TRACON |
| State Reference | KY |
| Aircraft 1 | |
| Make Model Name | Small Transport |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was en route at 3000 feet. This flight path took the aircraft directly over an antenna where the MVA is 3500ft. I noticed that the aircraft was about to enter the 3500ft MVA area and issued a 090 heading to keep the aircraft clear of the antenna. The aircraft turned to the 090 heading and the pilot reported the antenna in sight but at this point the aircraft was already in the higher MVA area and about 1.5 miles from the antenna as depicted on my radar map. I waited until the aircraft was more than 3 miles from the antenna before instructing the pilot to proceed on course.this event occurred because of a breakdown in my scan. The aircraft was at an altitude and in an area of my airspace that kept the aircraft well clear of my other traffic so my attention was drawn to other areas of my scope. In the future when I have an overflight that I know will be entering a quadrant of my airspace with a higher MVA; I will put a 'bat' on the radar target so that I can monitor the flight path more accurately. Closely monitoring the aircraft's flight path will allow me to notice issues like this farther in advance so that I can make corrections sooner.
Original NASA ASRS Text
Title: SDF TRACON controller reported being distracted and failed to notice an aircraft entering a higher MVA.
Narrative: Aircraft X was en route at 3000 feet. This flight path took the aircraft directly over an antenna where the MVA is 3500ft. I noticed that the aircraft was about to enter the 3500ft MVA area and issued a 090 heading to keep the aircraft clear of the antenna. The aircraft turned to the 090 heading and the pilot reported the antenna in sight but at this point the aircraft was already in the higher MVA area and about 1.5 miles from the antenna as depicted on my radar map. I waited until the aircraft was more than 3 miles from the antenna before instructing the pilot to proceed on course.This event occurred because of a breakdown in my scan. The aircraft was at an altitude and in an area of my airspace that kept the aircraft well clear of my other traffic so my attention was drawn to other areas of my scope. In the future when I have an overflight that I know will be entering a quadrant of my airspace with a higher MVA; I will put a 'bat' on the radar target so that I can monitor the flight path more accurately. Closely monitoring the aircraft's flight path will allow me to notice issues like this farther in advance so that I can make corrections sooner.
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.