Due to 3 CTD's (in P3D), the FLT saved in P3Dv5HF2 is behind (earlier in the FLTPLN) then the FLT position that is saved in PF3. I suspect that the positional difference between P3D saved position and the PF3 saved position is what caused the subsequent error in PF3.
Actually, PF3 did a pretty good job of waiting till I entered the control zone (Bangkok) that P3D CTD'd in to come "alive"; i.e. the cmd list populates. Shortly thereafter PF3 errored-out.
Basically, the resume function picked up the FLT ahead of where my last save was before the CTD. I wasn't using FSUIPC autosave due to suspected stutters during saves, but I will start using it again.
Thanks,
Walter