ATC TRACON and Tower Controllers reported a departing aircraft turned the wrong way resulting in flight towards terrain. The TRACON Controller issued a low altitude alert and heading to get the aircraft safely back on their route.

Date: 2025-08 · Aircraft: A321 · Phase: initial_climb

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

Synopsis

ATC TRACON and Tower Controllers reported a departing aircraft turned the wrong way resulting in flight towards terrain. The TRACON Controller issued a low altitude alert and heading to get the aircraft safely back on their route.

Narrative

While working the departure sector; I observed Aircraft X going southeast prior to check-in. The aircraft should have been on a northwest turn to XXX per coordination/SOP. Upon checking in; Aircraft X advises that he is climbing to 090 and in a left turn to XXX. I verify it was that aircraft and he confirms his information. My next transmission was a Low Altitude Alert advising the aircraft to make his left turn to XXX immediately. The pilot's readback was accurate. I then asked the pilot if he had all terrain in sight and he confirmed that he did. A second Low Altitude Alert was issued to climb and turn left immediately. The pilot confirmed that he was doing the best he could at climbing; but being an Aircraft X and his speed that it was challenging. I issued the aircraft to resume normal speed and climbed the aircraft more. I failed to 'Radar Contact' the aircraft during the event. RecommendationAccording to the SOP; Tower is supposed to catch readbacks of the correct turn direction from pilots when they issue the instruction. Additionally; Tower is supposed to observe the correct turn prior to transferring communication to Departure. These two rules in the SOP and when followed; help to assure aircraft are complying and in a safe route of flight.

Second reporter narrative

There was a storm cell to the southwest of Runway XXL; the departure runway; that contained light to heavy precipitation. I issed a weather advisory to Aircraft X along with the current wind and a right turn heading XXX in the take off clearance. Aircraft X departed then started a right turn so I reiterated the heading of XXX (making sure they continued their turn and didn't fly heading YYX which some times happens) and shipped communications to sector X in ZZZ. I had to lower my head to see Aircraft X beneath the ASDE and radar for the local east position. After shipping communications I continued facing the south (toward Aircraft X but could not see them because I was no longer bending my head down below the level of the scopes. Seconds after transferring communications sector X called up and said something to the effect of Aircraft X turned east; fix it. I replied something like - I shipped them; I'll try. I reached out on frequency and got no answer. Is started looking for guard frequency and asked somebody else to try guard and the reached out for Aircraft X again on my frequency XXX.XX and again got no answer. We watched in the Tower as Aircraft X did a full 225 degree left turn to heading XXX over the city; busting multiple mva's in the process. We learned from the front line manager (FLM) that ZZZ was talking to them at somepoint in the left turn. I have not watched a replay of this event. While filling out this report I was informed that Aircraft X did not read back turn right heading XXX during the take off clearance while still on the ground which I missed and that Aircraft X read back left turn heading XXX when I reissued the heading during the hand off transmission to ZZZ; which I also missed. I was also told the radar confirms Aircraft X was in a right hand turn when I transferred them to sector X at ZZZRecommendationI do not have any recommendations to fix this issue. We try to be vigiliant in catching any left turns in a south flow because of the proximity to the mountains. I personally will re-double my efforts to catch this in the future by not allowing obstacles in the Tower to impede my vision and ensuring a productive hear back/read back loop is maintained.

More incidents for this aircraft family →

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