 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Boise TRACON controller reported vectoring an aircraft into a higher minimum vectoring altitude [MVA] area.
| Attributes | |
| ACN | 1567583 |
| Time | |
| Date | 201808 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BOI.TRACON |
| State Reference | ID |
| Aircraft 1 | |
| Make Model Name | Small Aircraft Low Wing 1 Eng Fixed Gear |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X was an overflight via lvm and wys. The flight progress strip in front of me; left by the previous controller had a giant 'V' on it; which I interpreted to mean he was VFR. Wys is not displayed on our radar maps (though it should be) and I looked at the VFR sectional to determine where it was in relation to ennis; which is in my airspace. I projected that the flight path from lvm to wys would be through my 11;000 and 12;000 MVA's. At a point where the 11; 12; and 13;000 MVA's meet; I realized that aircraft X was just dragging through the corner so I turned him on a 250 heading into the 11;000 MVA; climbed him to 13;000; for the higher MVA's ahead and coordinated it with ZLC sector 6.we get enough people going to and by wys and enough tfr's and notams for it that we should at least display that on our radar map.this happened because I was complacent and thought: 1.) the plane was VFR; even though level at FL120. So many pilots fly VFR at other than right for flight VFR altitudes; I was tricked by the giant 'V' on the strip. The data block did not indicate VFR or have a (*) splat indicating MSAW (minimum safe altitude warning) not processed. 2.) the direct line from lvm to wys was clear of the 13;000 MVA area.
Original NASA ASRS Text
Title: Boise TRACON Controller reported vectoring an aircraft into a higher Minimum Vectoring Altitude [MVA] area.
Narrative: Aircraft X was an overflight via LVM and WYS. The flight progress strip in front of me; left by the previous controller had a giant 'V' on it; which I interpreted to mean he was VFR. WYS is not displayed on our radar maps (though it should be) and I looked at the VFR sectional to determine where it was in relation to ENNIS; which is in my airspace. I projected that the flight path from LVM to WYS would be through my 11;000 and 12;000 MVA's. At a point where the 11; 12; and 13;000 MVA's meet; I realized that Aircraft X was just dragging through the corner so I turned him on a 250 heading into the 11;000 MVA; climbed him to 13;000; for the higher MVA's ahead and coordinated it with ZLC sector 6.We get enough people going to and by WYS and enough TFR's and NOTAMs for it that we should at least display that on our radar map.This happened because I was complacent and thought: 1.) The plane was VFR; even though level at FL120. So many pilots fly VFR at other than right for flight VFR altitudes; I was tricked by the giant 'V' on the strip. The data block did not indicate VFR or have a (*) splat indicating MSAW (Minimum Safe Altitude Warning) not processed. 2.) The direct line from LVM to WYS was clear of the 13;000 MVA area.
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.