Air taxi flight crew reported an aircraft taking the runway while on final approach. Flight crew executed a missed approach and returned for landing without incident.

Date: 2025-12 · Aircraft: Medium Transport; Low Wing; 2 Turbojet Eng · Phase: approach

Anomalies: conflict-airborne-conflict|conflict-ground-conflict|critical|deviation-discrepancy-procedural-published-material-policy

Synopsis

Air taxi flight crew reported an aircraft taking the runway while on final approach. Flight crew executed a missed approach and returned for landing without incident.

Narrative

We were Enroute from ZZZ to TRM and on descent into the valley north of the TRM airport. So far the flight had been normal and uneventful. At the time we were talking to SoCal Approach and about 25-30 miles north of the airport. I put the CTAF frequency for TRM on Com 2 and began making position reports at 25 miles with our intended pattern entry and intentions to land as Aircraft X". The runway in use at the time was Runway 17. The frequency was busy with another Aircraft Z who was approaching from the south as well as two small aircraft approach from the north at low altitude and a helicopter transitioning at around 5;000 MSL. However this level of traffic is common at TRM. As we got closer to the airport; I handed over the responsibilities for SoCal and comm 1 to the PF as it began to get busy to manage both frequencies at the same time and I wanted to make and receive accurate position reports on the CTAF. I continued to make several position reports and continually monitored what traffic was also reporting. As we were about 7-10 miles NW of the field SoCal gave us a vector to the north and then shortly there after a vector back south to join a right base to continue descent. Once we're turned back towards the airport and we're both visual with the field; The PF called visual with TRM to SoCal and we were cleared visual approach. At the same time I made another position report on the CTAF stating that we were on a 5 mile right base leg for Runway 17. Immediately after the Aircraft Z called that they were visual with us and were going to extend the left downwind to follow us in. Shorty thereafter I gained positive visual contact with Aircraft Z and confirmed that they would be turning behind us. We turned onto final and I made a 5 mile call on final; followed by a 3 mile call. The two small aircraft had both crossed over midfield at their TPA (Traffic Pattern Altitude) and now were both joining the left downwind at this time; so I knew that no one who was on the radios was to the right of us. At about 2 to 1.5 miles to the runway and about 5-600 feet agl; I was monitoring the TCAS screen when the PM announced to me "Who's this jet taking the runway?" I remember being initially surprised because I hadn't heard anyone announce that they were taxiing or planning to depart on the CTAF when I heard this. I looked up to observe a large sized business jet about mid turn on the numbers for Runway 17 lining up for departure. I realized that the spacing was way too tight and immediately called for the go around. We executed the go around procedure and I announced on the CTAF that we were going around and would be offsetting Runway 17 to the right in the upwind. Aircraft X behind us then asked if "that guy made any radio calls?" to which I responded "no". We continued to remain visually separated with the jet and climbed to 1500 feet AGL for TPA. I continued to report our position. The large jet eventually made the left turn per the MECCA1 SID; but never made a radio call. We then flew a standard left traffic pattern for 17 and landed without issue. I estimate that at one point we were less than 1/2 mile and co-altitude with the conflicting traffic. The PF spoke with Aircraft Z on the ground who corroborated that they also heard no radio calls from the large business jet. The tail number for the conflicting aircraft was Aircraft Y.Cause: Failure by Aircraft Y to monitor the CTAF; Failure by Aircraft Y to announce position/intentions on the CTAF; Failure by Aircraft Y to visually clear final approach for taking an active runway; Traffic density and types of operations at TRM without an operating control tower. Suggestions: Proper monitoring and use of CTAF; Proper visually clearing runway/final;"

Second reporter narrative

Short final go-around due to aircraft (I believe it was Aircraft Y) taking off Runway 17 without making any radios calls on CTAF. Go-around was called by PM at approximately 2-2.5 miles and under 500'. Autopilot was already disengaged; so I side stepped to the west of the runway; climbing to 1500'. Flew a visual pattern and landed without incident.Aircraft Z that was #2 behind us verified that Aircraft Y did not make any radios calls. I spoke to him after we landed.Cause: Lack of situational awareness from the departing Aircraft Y.Suggestions: FAA needs to make a Tower at TRM a priority. This is not the first time this has happened.

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