kwri10s

Ok, did I miss something with the latest MD11 comm update? The Captain is no longer in command when he show at the airplane and finds it acceptable. He is now not in charge until he blocks out ("flight time")? Do we just inform MX and GOC what is happening and let them decide? Do we now get told when it's OK to start? If the Capt is not in command should we be asking for beacon? Shouldn't we just notify ramp we have completed our checklists and await further instructions? If the Capt is not in command he can't really call for a checklist, he can ask the FO I he wants to run the check. Better yet, he no longer can decide who gets on the jumpseat (see 777 thread), it is decided for him. Although I guess if he disagrees after block out he can block back in and kick them off. Not that we would have "who's in charge of approving Jumpseaters" issues with the contract up again. Just wondering if that emphasis change seems as strange to others as it did to me.

hypoxia

One thing is for certain, you are definitely not the guy or gal "in charge", so relax!

HazCan

Put the knife down Francis. It was after block in, not before block out.

FLMD11CAPT

Interesting comment.To my knowledge my previously known responsebilities were extended to any and all safety reports, Pilot discrepency reports, crew performance communications with pro-stan as well as any ACP interactions......and this is the short list.............all of which happen after block in....l...Hmmmmm..........Capt Admin Pay?.........

HazCan

My point was (and maybe I was a little harsh) is that it was after block in, chocks in, brakes off, engines shut down, etc, etc. Most guys I know are too busy getting their stuff and getting out of the jet to worry about what mx is doing. Seems like a reasonable thing to do for mx (pull the CB) so that the suppression system doesn't go off with someone in the back. If it were me (and I know it's NOT), once it's shut down and everyone is getting off....it's not my bird anymore.

Nitefrater

Your "responsibilities" include all of those things. The issue in the Comm Update is PIC "authority", as in the "ultimate authority" as defined by the FARs. You have authority and responsibilities outside of blockout-to-blockin, but they don't extend to directing maintenance. The Comm update doesn't change anything... it just reiterates what most (but not everyone) already knew.

Spanky

Good Explanation Nitefrater. It seemed like the Capt that led to this email overstepped his authority and SR rather than just say so explained why.