ZSE Controller reported military aircraft was off filed departure route and entered a higher MVA resulting in a CFTT event.

2024-08 · NASA ASRS report 2155031

Date: 2024-08 · Aircraft: Helicopter · Phase: initial_climb

Anomalies: atc-issue-all-types|airspace-violation-all-types|deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

ZSE Controller reported military aircraft was off filed departure route and entered a higher MVA resulting in a CFTT event.

Narrative

Aircraft X called on the ground at EAT looking for IFR clearance to EAT (via a long training route). I cleared the aircraft as filed at the requested altitude; 7000; which was safe for the route of flight until at least ZSE Approach Control's airspace (ZZZ sector). I instructed the aircraft to contact me leaving 4000. When they did; I noticed that they were southbound entering the 8600 MIA. I queried them a couple of times if they were flying some sort of departure procedure and they indicated that they were southbound towards ELN. I said that they needed to be on their filed route towards QUINT; and they indicated they were turning that way. I and gave them a low altitude alert (admittedly probably a bit too late and with imperfect phraseology) and climbed them to the MIA (8600). There was other traffic at 8600 so climbed them to 9600 and vectored them to the south (H160) to avoid a traffic situation. Once above the MIA; I instructed Aircraft X to climb to 100 and fly H065 to keep him clear of traffic. I asked Aircraft X his intentions. He said he wanted to go to ZZZ and get vectors for ILSXX. I gave him a southerly heading and handed him off to ZZZ1 [Tower] after explaining why I wasn't comfortable clearing the aircraft on course. The relieving controller read the Brasher statement to Aircraft X. Suggestion: I could have assigned the OFARO SID to the aircraft which would have been another way to reinforce the aircraft going eastbound on departure; although I don't know if that would have made a difference. I am still not sure why the aircraft decided not to fly its filed route.I was really startled by this situation; especially considering that I had traffic at the MIA; and am disappointed that I reacted more slowly than I would have liked. I was pretty flustered. Some of my actions were too slow and others were too excessive.We were on the standby for CHXX and it didn't seem to be working as well as the mains. Having to repeat transmissions added a bit of complexity to this situation.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.