Originally Posted by
Herkflyr
My point about the rigidity of things (perhaps not SOPA/SMAC but other NWA guidance) was:
1. F/O's didn't even know how to load the FMS because that was the captain's strict domain. Ditto for overhead preflight panel, and the exterior walkaround. While I like the fact that usually a certain duty is delegated for this crewmember or that, to absolutely 100% of the time state "only" this guy does this or that, results in you losing a lot of knowledge, and more importantly, degrades airmanship.
2. Apparently at NWA you would rather go around than have the pilot flying actually touch the flap handle? While 99% of the time the flying pilot doesn't touch the flaps or gear, there are the rare occasions when the captain is busy on the radio or coordinating something with the FAs. In that case if I am slowing down I will move the flaps and just sort of indicate what I did. The captain always just kind of nods and continues what he was doing. As the FOM clearly states, we all know that is the exception and not the rule.
Correct me if I am wrong on any of this. Aside from a few things like this (if true) I still think that your way of doing operational business at NWA was stellar.
"Many years ago NWA developed an operating philosophy under which individual pilot tasks were organized into a time-ordered flow of events. THe objective of this method of organization was a smooth, coordinated flight deck management system which promoted standardization and enhanced safety.
Under the Northwest system each crewmember is assigned specific duties. However, an organized and standardized method of integrating these duties with the other pilot is also needed. SOPA is established of this purpose. SOPA is not intended to supply detailed systems or component operating information, but primarily:
1. to establish the sequence in which the designated steps are accompolished and
2. to designate which crewmember normally accomplishes each step.
Adherence
All pilots will follow SOPA during
normal operations.
The captain has the authority to deviate form SOPA, but only when unusual circumstances require him or her to do so in the interest of safety.
Structure
All duties are normally performed in the order in which they appear in SOPA. However, that does not preclude the earlier or later performance of isolated items that are not "on command" items or part of a specific flow pattern. In other words, the time ordered nature of SOPA outlines what may be considered a normal flight, but aside from flows and "on command" items, it allows some flexiblilty in the order of performance to allow for specific circumstances."
SOPA allowed the standardization between fleets as much as possible in that you knew with a new aircraft training event you would be doing the same things at the same times in your new plane vs the old plane decreasing the amount of training that you would need on the new aircraft. Having flown SOPA and the new DAL procedures, I prefer SOPA. Not saying that it is better, just that I prefer it. It allows you to identify a guy that is not up to speed or having a bad day instantly and you are not sitting there going well this must be the way this guy does it. Both sides have pluses and minuses. Hopefully a blend will come out of this giving us a great set of operating procedures.
