SR22
Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Commercial
Flight Crew Last 90 Days 14; Flight Crew Total 788; Flight Crew Type 155
Situational Awareness; Communication Breakdown
Conflict NMAC; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action
Airport; Procedure
I was pilot flying for an instrument currency flight. My safety pilot had a private pilot certificate. I was wearing a view limiting device and he was scanning for traffic.I was flying the practice RNAV 30 at Byron Airport (C83) to LPV minima. I was under flight following with NorCal Approach. They advised me of parachute activity in the vicinity of Byron Airport; but gave me no further instructions; so I simply acknowledged the advisory. They then handed me off to CTAF after clearing me for the approach.On CTAF I broadcast my position periodically as I continued the approach. There was one other aircraft also broadcasting on frequency; he broadcast that he was on short final when I was about 5 miles out; so I judged there to be no traffic conflict.When I was nearing LPV minima; I initiated the go-around for the missed approach. The missed approach procedure involves a straight-ahead climb to 1;000 ft. before the first turn. The autopilot was fully coupled; so it continued to fly runway heading overhead the airport while climbing to 1;000 ft. MSL.I announced the overflight on CTAF; stating that I was overhead the airport and flying upwind on the published missed approach. At this point I heard another transmission; presumably from the jump plane; in a very urgent tone of voice; advising me to turn immediately; as jumpers were overhead the airport.I removed my view-limiting device and made immediate visual contact with the parachutists to the left and above me; approximately 500 to 1;000 ft. away. I made an evasive right turn and then continued the published missed approach procedure. There were of course multiple parachutists and I couldn't verify that I had made contact with everyone.The root cause of this incident was: My inaction in responding to the skydiving alert from NorCal; and my inaction in creating an avoidance plan for the skydivers.Contributing factors:In my experience; when NorCal issues skydiving alerts to a specific aircraft by callsign (not 'attention all aircraft' alerts); those are associated with instructions (such as 'turn 30 degrees left'). Since I didn't receive any additional instructions; I treated the alert as advisory; which contributed to me not making an avoidance plan.By the time I had tuned to CTAF; the jump plane was no longer transmitting. I presume that he did make a 'jumpers away; do not overfly the airport' call; but it must have been prior to me tuning CTAF. Typically I monitor CTAF on COMM2 as I prep for the approach with NorCal; but due to radio and task saturation; I had COMM2 muted at that time.I am familiar with skydiving operations at Yolo County Airport (DWA); where they have a specific jump zone that is Northeast of the airport. Aircraft there can fly the traffic pattern; but merely must avoid crossing over to the east side of the airport. I'm not sure what the procedure is at Byron; but I hadn't assumed that the skydivers would overfly the traffic pattern directly. I should have checked the Chart Supplements page for Byron to review their skydiving operations procedures.
SR22 pilot reported NMAC with skydivers.