Weird strike mission

[Pheonix Starflare]

So i transferred to the 112th Warbirds and chose a 'assault' mission. I chose my loadout and then when i started the mission i saw the quantum jump graphic and 1/2 of my flight and I were sitting on an invisible carrier deck and we went through the normal launch animation. However, Raptors 3 and 4 never showed and my navpoints were in another sector or something, the distance was listed as 125G (I assume thats for Gigameters) and the time was XX:XX. However, there wasnt a carrier to return to, so i had to abort/discard the mission.

The next mission I chose was another strike on the same ship, however this one stated normally. My flight and I launched and as we formed up heading for the first nav we went into EMCON 2 and I timeskipped to the 2nd nav. Upon setting our course for the 3rd nav (the assault one) i sent the flight into EMCON 1 and set myself into it. However, the moment after coming out of timeskip i was being fired upon by an enemy frigate (not the one I was assaulting) and my decoy system was promptly knocked out and I died too far away from the target to hit it with any of my ASMs. Attached is the errlog of those two missions.

[Dirt12]

I've noticed the phantom Q-jump myself. I'm guessing this is to be fixed in the up coming patch. I find that all you need to do when you see it happen is quickly abort and then re-accept the mission right away. Then it's like it never happened in terms of the game and I've never seen it happen twice in a row.