Date: 201411
Local time of day: 0601-1200
Location: TRM.Airport, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Embraer Legacy 450/500
Operator: Fractional
Operating under: Part 91
Mission: Passenger
Flight phase: Landing
Airspace: Class E TRM
ATC / advisory: CTAF TRM
Second aircraft: Cessna Aircraft Undifferentiated or Other Model
Reporter organization: Fractional
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown; Situational Awareness
Second reporter function: Captain; Pilot Not Flying
Anomaly: Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Aircraft RA; Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Human Factors; Airport
Primary problem: Human Factors

Narrative: I was SIC (Second in Command) Pilot Flying in the left seat during a passenger flight to TRM; the weather was severe clear (day) with ASOS reporting calm winds.  We planned/briefed a visual approach to runway 35 because our direction of arrival from the north set us up nicely for a 45 degree left downwind entry and that runway had an instrument approach with vertical guidance (LNAV+V). We cancelled IFR at about 12 miles and entered the downwind as briefed.  My partner made our first radio call on CTAF at about 10 miles announcing our intentions.  One aircraft replied stating that he had just departed runway 17 and was clearing the pattern to the east.  No other aircraft replied.  My partner made three subsequent calls on CTAF announcing our position and intended landing on 35:  entering downwind; mid-field downwind and turning base.  There were no replies and no other aircraft transmitted on CTAF.  About halfway through our base leg; we heard an aircraft announce that he was taking runway 17 for takeoff.  My partner immediately replied that we were about to turn final on runway 35.  There was no reply.  My partner again asked the other aircraft where they were and again there was no answer.  Not knowing what this other aircraft was doing; we executed a missed approach at about 700 feet as we should have been turning final.  We started a climb to pattern altitude (1500 feet) and I offset to the right side of the runway to clear the departure path and set up for a left downwind to runway 17.  Climbing through approximately 1300 feet; we got a TCAS RA (climb).  As I was executing the RA; I saw a single engine Cessna pass about 500 feet below us.  After avoiding the traffic; we entered a left downwind for 17 and made an uneventful landing. I did not hear this aircraft make any CTAF calls other than the one announcing that they were taking 17. After disembarking the passengers; the FBO line crew told us that they saw the entire thing happen.  They went on to say that the offending aircraft was based at TRM. This event would not have occurred had the pilot used proper communication procedures.


Second narrative: We were inbound to TRM after having just cancelled IFR with SOCAL approach. We were about 10 miles north and we were setting up for a 45 degree entry to a left downwind to runway 35. On my initial call on the CTAF I requested an advisory and one aircraft had reported departing runway 17 shortly before my call. We then considered using 17 however decided to continue inbound to RWY 35 as the winds were calm and 35 had an approach with vertical guidance we could use to back up our visual approach. There was no other traffic inbound or outbound as well so we could go with either runway but 35 seemed to make the most sense.I then announced an 8 mile 45 degree entry. I also announced a 4 mile call as well as a call turning downwind; midfield downwind; and a base call. Just before turning final; a single engine Cessna announced lining up on RWY 17. Out of concern; I again announced our position and queried the aircraft about which runway they were departing and got no reply. My partner verbalized his desire to go around if we didn't hear from them. I agreed and queried once again. At that point the aircraft announced they were rolling on 17 and before turning final we went around and joined a modified crosswind for 17.I announced turning downwind and could see the aircraft flying toward us climbing out. We then got a TCAS RA and complied climbing slightly above pattern altitude when the RA ended. We then flew a normal traffic pattern to 17 and landed uneventfully. I think if the departing aircraft would have communicated the event wouldn't have happened.


Synopsis: EMB505 Flight crew experiences an airborne conflict during a visual approach to Runway 35 at TRM. The crew made position reports during pattern entry; downwind and base. As they are about to turn final a Cessna announces entering Runway 17 for departure and does not respond to requests from the EMB505 crew to allow them to land first. A go-around is initiated and a TCAS RA is complied with.