 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Bhm controller reported they issued a clearance to an aircraft which placed it below the minimum vectoring altitude.
| Attributes | |
| ACN | 1695430 |
| Time | |
| Date | 201910 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | BHM.TRACON |
| State Reference | AL |
| Aircraft 1 | |
| Make Model Name | Light Transport |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3.0 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was handed off to me from center from the northeast; landing at tcl. There was weather throughout the airspace so the aircraft requested deviations and I approved it. I told the aircraft to expect direct nenmy when able. When the aircraft got within 30 miles of tcl airport he wanted to go west of the final app course of runway 22. I descended the aircraft to 4;000 feet because of the obstacle 20 miles northwest of the tcl airport and the final. When aircraft X said he could go direct to nenmy; I cleared him and told him to cross nenmy at or above 3;000 feet. At the time and position I did not realize that track would take him over the 3;700 feet MVA (minimum vectoring altitude) obstacle. The aircraft ended up passing over the MVA obstacle at 3;000 feet and already passed it when we realized it. The MSAW (minimum safe altitude warning) only flashed and there was no audible alarm heard. What I learned from this event is… whenever you have an aircraft approaching from the north in that general area and they will cleared on an instrument approach is wait until the aircraft is well south of that MVA area. The aircraft will have time to get down on a legal approach. Also; for me; maybe put a J ring around that obstacle as a reminder.
Original NASA ASRS Text
Title: BHM Controller reported they issued a clearance to an aircraft which placed it below the Minimum Vectoring Altitude.
Narrative: Aircraft X was handed off to me from Center from the northeast; landing at TCL. There was weather throughout the airspace so the aircraft requested deviations and I approved it. I told the aircraft to expect direct NENMY when able. When the aircraft got within 30 miles of TCL airport he wanted to go west of the final app course of Runway 22. I descended the aircraft to 4;000 feet because of the obstacle 20 miles northwest of the TCL airport and the final. When Aircraft X said he could go direct to NENMY; I cleared him and told him to cross NENMY at or above 3;000 feet. At the time and position I did not realize that track would take him over the 3;700 feet MVA (Minimum Vectoring Altitude) obstacle. The aircraft ended up passing over the MVA obstacle at 3;000 feet and already passed it when we realized it. The MSAW (Minimum Safe Altitude Warning) only flashed and there was no audible alarm heard. What I learned from this event is… whenever you have an aircraft approaching from the north in that general area and they will cleared on an instrument approach is wait until the aircraft is well south of that MVA area. The aircraft will have time to get down on a legal approach. Also; for me; maybe put a J Ring around that obstacle as a reminder.
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.