Skyhawk 172/Cutlass 172
Flight Crew Private
Flight Crew Last 90 Days 31; Flight Crew Total 108; Flight Crew Type 52
Communication Breakdown; Situational Awareness
ATC Issue All Types; Conflict Ground Conflict; Less Severe
Flight Crew Took Evasive Action; Flight Crew Executed Go Around / Missed Approach
Human Factors
I had been acting as Safety Pilot for an IFR training flight for a friend. The flight was uneventful. Once we got back to Oakland; we decided to do a couple stop and goes for currency. We had each done one landing on [Runway] 28R; when the controller asked us to switch to left close traffic for [Runway] 28L. We complied; and flew the published 600 ft pattern. On downwind; the controller cleared us for the option of [Runway] 28L; and the Pilot Flying read it back and requested a short approach. The controller approved the short approach; and the Pilot Flying read back the approval. Abeam the numbers; we began our short approach for a practice engine out 180 maneuver. On very short final; I noticed a jet cross the [Runway] 28L hold bar and proceed onto the runway. I alerted the Pilot Flying; and he executed a go-around. He then informed the controller that the ground traffic had not passed. I don't not believe a collision was imminent; as our approach was slightly high and we probably would have gone over the jet. However; if we had landed there would have been two planes on the same runway. What's especially troubling is that if we had been lower we almost certainly would have collided on the runway if we had not been able to see the jet. This seems like it was a simple miscommunication between tower and ground controllers; or the tower simply misjudged how long it would take us to execute a short approach. Either way; it was way too close for comfort; and I feel like it should be brought to someone's attention.
Cessna pilot reported avoiding a runway incursion by going around when they observed a jet taxiing past the hold short line.