M-20 J (201) / Allegro
Flight Crew Private; Flight Crew Instrument
Flight Crew Last 90 Days 6; Flight Crew Total 2878; Flight Crew Type 1102
Situational Awareness
Conflict NMAC
General None Reported / Taken
Human Factors
I was entering the traffic pattern at 45 degrees for a downwind entry for RWY14 at FIT. I had previously announced my intentions and location on the 122.7 CTAF. I did not see or hear the conflicting traffic during its go around and climb out from RWY14.  I was alerted to the traffic by an ADS B traffic alert on my iPad. At this point I could not see the traffic in my field of view. I turned 45 to downwind and added power to get away from the traffic.  Earlier I had heard the conflicting aircraft on the CTAF advising it was on the RNAV20 approach and would be breaking off the approach for a straight in to RWY14. Calls to the conflicting traffic before and after ADS B alert we're not answered.It all happened very quickly and I only glanced at the ADS B display; figuring my attention should be outside the airplane looking for the traffic. But the combination of repeated ADS B traffic warnings and not being able to visually see and avoid the traffic was quite stressful.  Today; I was able to get the conflicting traffic's flight path from flight aware and compare it to my own from Garmin Pilot. It appears the conflicting traffic did a low approach to RWY14 and a go around; making a left climbing turn close to my own flight path. From the flight paths; the time stamps; and the fact that I never made visual contact with the conflicting aircraft; I think it passed behind me; and estimate it may have gotten as close as 500 ft.Being more vigilant to visually identify and track what I thought was landing traffic; would likely have avoided this dangerous conflict. The fact that the conflicting traffic never responded to my radio calls should also have raised a red flag.
M20 pilot reported experiencing an NMAC in the pattern at FIT airport.