Date: 201809
Local time of day: 0001-0600
Location: FAI.TRACON, AK
Aircraft: Fighting Falcon F16
Operator: Military
Operating under: Part 91
Flight plan: IFR
Flight phase: Descent
Airspace: Class E FAI
ATC / advisory: TRACON FAI
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Workload; Distraction; Situational Awareness
Anomaly: ATC Issue All Types; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Procedure

Narrative: During my post brief; after being relieved off of position by the East Controller and combining sectors; I was instructed to take a break and return when the fighters were RTB (Returning to Base). I advised the Facility CIC [FCIC] that the fighters were due inbound shortly and it should stay combined. After 5 minutes had elapsed from me being off of position; the fighters started to call up. It was a mixture of VFR and IFR pickups. One of them being Aircraft X. I quickly plugged into EAST and started to do the entries to decombine the sectors. At this time I am monitoring; inputting the commands; selecting frequencies; and loading my position preferences. I hear the controller tell Aircraft X to proceed direct PAGGI; depart PAGGI direct BOGIE and expect vectors prior to BOGIE for the ILS RWY 32 approach into EIL; maintain VFR expect clearance once outside of the MOA's. I got the brief; and took position.I tried to input data block information but it was giving me audible error noises. I tried combining the airspace again with the commands outlined and I was still unable to get the data tags for the aircraft; or input any new data tag entries. I had to do manual coordination with EIL TWR for an inbound aircraft; while others were calling as well. I scan back to Aircraft X; who was at 070 in a 073 MVA (Minimum Vectoring Altitude) and decided to wait a few more miles until he was established in the 059 MVA which was only a few miles away. Once established; I cleared him and told him to maintain 060; the pilot read back the 060 clearance. I went back to trying to fix the issue of not being able to input anything; and was getting help from my FCIC / WEST controller. I was also fielding calls from EIL TWR; ZAN; and the other fighter aircraft. That's when Aircraft X came over the frequency and advised that he had gone below the 060 altitude. I observed his altitude readout at 051; and he advised he was climbing back up to 060. He was just inside the 059 MVA when he called up and advised me of that; then flew into a lower MVA of 040. That's when I issued to maintain 040; as I saw his readout go to 055. I did not brasher the pilot due to controller workload.




Synopsis: Fairbanks Controller reported having a flight of aircraft below the Minimum Vectoring Altitude and waiting until it went into an area of higher terrain. Reporter also stated the flight additionally descended below another MVA and reported doing so.