It's even possible to do the raw data flying, communicate, set the heading bug and radio at the same time, while doing the navigation and paperwork all alone. I guess this is what every pilot started out doing
Isn't that what trainers - sim and line spend far to much time knocking out of the new pilots straight out of flight school?
And to be honest it's not that big a deal for the PF to e.g. turn the heading bug while PM set a radio freq. Keyword is cockpit communication - "I have set heading 250 for you", "ohh thanks, 250 is checked".
Oh shock and horror, I know I am not allowed. Or I'll even e.g. turn to the assigned heading even if the heading bug has not yet been set, and then wait for the PM to turn the bug.
I am sure that lots of people (probably the majority) are able to do this. However, it flies in the face of so many reasons for having SOPs - cross checks, closed loops etc.
Or I'll even e.g. turn to the assigned heading even if the heading bug has not yet been set, and then wait for the PM to turn the bug.
Would you climb to the cleared level and wait for the asel to be set also?
Waiting for the PF turns to heading 230 and sits there and after doing some other task the PM sets FL230 in the asel window and direct ABC in the FMS.
What you are describing is no different from the PF who because the PM is busy with a frequency change reaches over and retracts the flap. The SOP crosschecks are there for a reason.