 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A TRACON controller reported they issued an insufficient vector to an aircraft to avoid a higher minimum vectoring altitude area.
| Attributes | |
| ACN | 1676938 |
| Time | |
| Date | 201908 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | R90.TRACON |
| State Reference | NE |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 8 |
| Events | |
| Anomaly | ATC Issue All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was holding at 3;000 ft. Several miles northeast of a 4;000 ft. MVA (minimum vectoring altitude). Aircraft X requested to proceed to a fix to begin an RNAV approach. The vector 170 was issued to keep aircraft X from entering the 4;000 ft. MVA. Shortly afterwards; there was a minor unrelated occurrence that required some coordination with an adjacent facility. I allowed my attention to be diverted momentarily; and when I looked back at aircraft X; I noticed he had just slightly clipped the 4;000 ft. MVA while still at 3;000 ft. I do not believe this was any kind of pilot error; I suspect it was due to wind or the pilot turning slower than expected; or perhaps I should have initially issued a wider turn to keep clear of the 4;000 ft. MVA. The pilot exited the corner of the MVA shortly afterwards and did not report any issue. I should have stayed more vigilant; and possibly issued a wider initial vector to ensure against wind or slower than expected turns.
Original NASA ASRS Text
Title: A TRACON Controller reported they issued an insufficient vector to an aircraft to avoid a higher Minimum Vectoring Altitude area.
Narrative: Aircraft X was holding at 3;000 ft. several miles northeast of a 4;000 ft. MVA (Minimum Vectoring Altitude). Aircraft X requested to proceed to a fix to begin an RNAV approach. The vector 170 was issued to keep Aircraft X from entering the 4;000 ft. MVA. Shortly afterwards; there was a minor unrelated occurrence that required some coordination with an adjacent facility. I allowed my attention to be diverted momentarily; and when I looked back at Aircraft X; I noticed he had just slightly clipped the 4;000 ft. MVA while still at 3;000 ft. I do NOT believe this was any kind of pilot error; I suspect it was due to wind or the pilot turning slower than expected; or perhaps I should have initially issued a wider turn to keep clear of the 4;000 ft. MVA. The pilot exited the corner of the MVA shortly afterwards and did not report any issue. I should have stayed more vigilant; and possibly issued a wider initial vector to ensure against wind or slower than expected turns.
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.