A TRACON Controller; their trainee; and the Controller in Charge working Flight Data reported Flight Data released an aircraft from a satellite airport at too low an altitude and an inappropriate direction of flight which resulted in the aircraft flying below the minimum vectoring altitude.

Date: 2023-06 · Aircraft: Small Transport; Low Wing; 2 Turbojet Eng · Phase: climb

Anomalies: atc-issue-all-types|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance|inflight-event-encounter-cftt-cfit

Synopsis

A TRACON Controller; their trainee; and the Controller in Charge working Flight Data reported Flight Data released an aircraft from a satellite airport at too low an altitude and an inappropriate direction of flight which resulted in the aircraft flying below the minimum vectoring altitude.

Narrative

I was on flight data when Aircraft X called for clearance and stated they were number 1 ready for departure at ZZZ Runway XX. I read the clearance and gave them an initial altitude of 050. They correctly read back everything. I coordinated with ZZZ for a release 'their freq and control' due to the fact that Runway XX at ZZZ is in close proximity to their boundary; ZZZ Controller stated they would block for the departure. I then coordinated with ZZZ1 Approach for the departure 'their freq and control' and they approved it and gave me the release. I then released the aircraft. The aircraft took off and began climbing/turning on course to ZZZ1. ZZZ1 Approach called and said they couldn't hear that aircraft at 5000 ft. where they were located. I expected them to be able to hear them and climb them before the 6800 ft. MVA. The aircraft then returned to ZZZ Approach control frequency where the Controller gave them a 180 heading and climbed him to 100. At that time the aircraft had entered the 6800 ft. MVA. I don't have any procedural recommendations at this time. I should have given the aircraft a fix to the South in my airspace so they could climb and avoid that MVA before turning on course. I could also have given a higher initial altitude so they could climb over that MVA. Departing Runway XX at ZZZ isn't a common occurrence and I will ensure that I take proper steps to avoid this happening in the future.

Second reporter narrative

Aircraft X entered into 6800 ft. MVA while climbing and in a turn to avoid it. I started OJT and was asked to release off a satellite airport ZZZ from my flight data/CIC. I approved the request. Communication was unclear and I inadvertently missed the aircraft being released at 5000 ft. direct first fix on their route of flight. My understanding was the aircraft was going straight to Center frequency and I only needed to block the airspace for the departure. Instead; the aircraft calls me and I proceed to radar ID the aircraft and begin the climb to 10000 ft. and issue a turn at my trainer's advisement. The aircraft flew a mile into the MVA while climbing and turning away from it. I am low in training hours in this facility as a Certified Professional Controller in Training (CPC-IT) and I will not allow this to happen again. The aircraft should have not been released to 5000 ft. and instead should have had the route amended southbound first to verify they did not enter the MVA.

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