 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A11 TRACON controller reported vectoring an aircraft below the minimum vectoring altitude.
| Attributes | |
| ACN | 1465288 |
| Time | |
| Date | 201707 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | A11.TRACON |
| State Reference | AK |
| Environment | |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Dash 8 Series Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Handoff / Assist Approach |
| Qualification | Air Traffic Control Developmental |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Track / Heading All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
It was a busy training session. I was training on south radar and south hand off combined. We had an unusual flight schedule due to fly-bys to runway 7R. I was instructed to vector all of our traffic to runway 7L; except for the runway 7R aircraft. After the fly-by was completed; tower still didn't want any aircraft to go to runway 7R. Aircraft X entered our airspace direct to anc VOR at 050. I told aircraft X to expect runway 7L. When he reached an appropriate place to turn upwind; I gave aircraft X a 070 heading to parallel aircraft Y that was on downwind. I started getting busy; intending to turn aircraft X to a 340 heading to the downwind about 5 miles in trail of aircraft Y I had aircraft Z that was on the NEELL5 arrival that was in conflict with aircraft Y so I was watching that and listening to final radar to see if he had turned aircraft Y to base. I then shipped aircraft Z to final and continued my scan. I saw aircraft X about 1 mile from the 6;000 feet MVA. I immediately turned aircraft X left to a 350 heading and pulled up my eovm [emergency obstruction video map]. Aircraft X was over the water and not near any terrain. I saw aircraft X continue straight after acknowledging the heading so I verified that the aircraft had the terrain in sight. He answered affirmatively and was instructed to maintain his own terrain and obstruction clearance. He was in the 6;000 feet MVA for a total of about 4 flying miles and remained over the water the entire time. During my debrief; my on the job training instructor said that I had caught the aircraft in time and corrected it before it was a factor. I was notified by a supervisor; that the region was made aware of it and called the front office. The front office watched and listened to the entire thing and made a determination that separation from terrain was lost.I recommend that the MVA's change around the anc area. There are MVA's over the water (sea level) that are 060-080 feet which is ridiculous. I know the terrain makes it difficult to establish consistent MVA's but our airspace is cramped and too small as it is; now we are not utilizing it in a way to help move airplanes.
Original NASA ASRS Text
Title: A11 TRACON Controller reported vectoring an aircraft below the Minimum Vectoring Altitude.
Narrative: It was a busy training session. I was training on south radar and south hand off combined. We had an unusual flight schedule due to fly-bys to Runway 7R. I was instructed to vector all of our traffic to Runway 7L; except for the Runway 7R aircraft. After the fly-by was completed; tower still didn't want any aircraft to go to Runway 7R. Aircraft X entered our airspace direct to ANC VOR at 050. I told Aircraft X to expect Runway 7L. When he reached an appropriate place to turn upwind; I gave Aircraft X a 070 heading to parallel Aircraft Y that was on downwind. I started getting busy; intending to turn Aircraft X to a 340 heading to the downwind about 5 miles in trail of Aircraft Y I had Aircraft Z that was on the NEELL5 arrival that was in conflict with Aircraft Y so I was watching that and listening to final radar to see if he had turned Aircraft Y to base. I then shipped Aircraft Z to final and continued my scan. I saw Aircraft X about 1 mile from the 6;000 feet MVA. I immediately turned Aircraft X left to a 350 heading and pulled up my EOVM [emergency obstruction video map]. Aircraft X was over the water and not near any terrain. I saw Aircraft X continue straight after acknowledging the heading so I verified that the aircraft had the terrain in sight. He answered affirmatively and was instructed to maintain his own terrain and obstruction clearance. He was in the 6;000 feet MVA for a total of about 4 flying miles and remained over the water the entire time. During my debrief; my On the Job Training Instructor said that I had caught the aircraft in time and corrected it before it was a factor. I was notified by a supervisor; that the region was made aware of it and called the front office. The front office watched and listened to the entire thing and made a determination that separation from terrain was lost.I recommend that the MVA's change around the ANC area. There are MVA's over the water (sea level) that are 060-080 feet which is ridiculous. I know the terrain makes it difficult to establish consistent MVA's but our airspace is cramped and too small as it is; now we are not utilizing it in a way to help move airplanes.
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.