37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1757997 |
Time | |
Date | 202008 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ANC.Airport |
State Reference | AK |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Departure |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X departed anc on the SID climbing to 4;000 ft. I vectored aircraft X to the north and climbed him to 7;000 ft. Below another IFR aircraft that was eastbound above. I became busy with other aircraft requesting special VFR clearances. When my scan brought me back to aircraft X; I saw he was at an altitude that I could turn him on course into higher mvas and thought I climbed him to 20;000 ft.as my scan approached him again; he was climbing well through 6;500 ft. In a 2;000 ft. MVA area. I asked him for a PIREP and was writing that down on the PIREP form. I turned around to give the PIREP form to the controller in charge and as I was sitting down; aircraft X requested higher. I saw that aircraft X was still at 7;000 ft. In an 8;000 ft. MVA by a few miles and climbed him to 20;000 ft. I realized the climb was not going to be well enough to clear the 10;000 ft. MVA so I expedited his climb through 10;000 ft. When I realized that wasn't going to work and he was out of 8;000 ft.; I turned him left to avoid the higher mvas. He was clear of the 10;000 ft. MVA box but had already missed the 8;000 ft. MVA.my recommendation is when we are inundated with ifrs off of our satellites and primary airport and our satellites start going below basic VFR; we should have a low radar staffed so that they can deal with all the special VFR requests rather than leaving the north radar controller to do it all.
Original NASA ASRS Text
Title: TRACON Controller reported being overwhelmed by distractions from satellite airport operations and forgetting to climb an air carrier departure; resulting in the aircraft flying below the Minimum Vectoring Altitude.
Narrative: Aircraft X departed ANC on the SID climbing to 4;000 ft. I vectored Aircraft X to the north and climbed him to 7;000 ft. below another IFR aircraft that was eastbound above. I became busy with other aircraft requesting special VFR clearances. When my scan brought me back to Aircraft X; I saw he was at an altitude that I could turn him on course into higher MVAs and thought I climbed him to 20;000 ft.As my scan approached him again; he was climbing well through 6;500 ft. in a 2;000 ft. MVA area. I asked him for a PIREP and was writing that down on the PIREP form. I turned around to give the PIREP form to the CIC and as I was sitting down; Aircraft X requested higher. I saw that Aircraft X was still at 7;000 ft. in an 8;000 ft. MVA by a few miles and climbed him to 20;000 ft. I realized the climb was not going to be well enough to clear the 10;000 ft. MVA so I expedited his climb through 10;000 ft. When I realized that wasn't going to work and he was out of 8;000 ft.; I turned him left to avoid the higher MVAs. He was clear of the 10;000 ft. MVA box but had already missed the 8;000 ft. MVA.My recommendation is when we are inundated with IFRs off of our satellites and primary airport and our satellites start going below basic VFR; we should have a low radar staffed so that they can deal with all the special VFR requests rather than leaving the North Radar Controller to do it all.
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.