What is a Standard Operating Procedure (SOP)?
A look at Standard Operating Procedures and why they are used.
What is a Standard Operating Procedure?
SOP is an abbreviation for a Standard Operating Procedure. It is a framework of common procedures set out by an airline which supports pilots in operating a commercial aircraft safely and consistently.
Many industries use SOP’s as a common way of ensuring tasks or operations are completed correctly, however SOP’s are essential and fundamental in aviation.
Standard Operating Procedures (SOPs) serve a number of purposes such as:
- Ensuring that aircraft is flown correctly in accordance with the manufacturer’s guidelines
- Promote adherence to the manufacturer’s and airline’s operating philosophy
- Promote operational safety
- Promote operational efficiency
- Utilise aircraft resources and functionality appropriately
It also allows any pilots from the same company who may not have flown with each other before (or may even never met each other), to fly together as a crew. Adherence to SOPs means each pilot know exactly what they and the other pilot should be doing in any given phase of flight. This is particularly important when working for a large airline with hundreds of pilots.
Different types of SOP’s
The following are different types of Standard Operating Procedures:
A memory flow of arranging switches and levers in the correct position for a particular phase of flight. For example, it is normal that the PM / PNF (Pilot monitoring or Pilot not flying) will complete the before start flow and then read the before start checklist which the PF (Pilot flying) will respond to.
A call or acknowledgement of an event. For example, most EASA airlines have to acknowledge an automated callout of 1,000ft which would be followed by PM / PNF stating whether they are stable or not for the subsequent landing.
A procedure that requires completing with certain criteria. For example, in visible moisture below 10 degrees pilots will be required to taxi and take off with engine anti-ice systems on.
SOP’s can also be developed as time goes by to incorporate improvements based on experience, accidents, near misses or innovations from other manufacturers or operators to suit the needs of a particular organisation.
SOP design covers both normal and non-normal operations. For example, they dictate how the take-off should be flown whilst also providing guidelines for how to respond to an engine failure.
SOP’s should not be designed to be too detailed and exhaustive that the pilot does not provide any form of cognition to the process and not be too relaxed to the point that the crew have too many options to decide between.
If a pilot is not conforming to SOP’s he/she can be expected to be challenged by the other pilot. Failure to respond appropriately to 2 or more SOP deviation calls by the other pilot will lead them to assume you have become incapacitated and will assume control of the aircraft.
However, there may be an occasion where it is preferably or vital to ignore or not carry out an SOP. This would normally be in an emergency situation. An example of this would be continuing to land the aircraft below the operating minima where the pilots had not become visual with the runway as they had an uncontrollable cabin fire. In this case it would be safer to continue with the landing despite it being against the rules (or SOPs) to do so.