Standard Operating Procedures

Standard Operating Procedures

Standard Operating Procedures (SOPs) are written policies and practices designed to ensure operational consistency and reduce errors. They encompass normal, abnormal, non-normal, and emergency operations to achieve predictable, safe outcomes across all phases of flight.

SOPs = Doing it the right way, all the time, every time.

Structure of an SOP

Each SOP provides a structured approach to tasks in all flight phases, detailing what needs to be done, when it should be done, and who is responsible for its execution.

Personalizing and Developing SOPs

SOPs should be adapted to align with specific equipment and the individual pilot, instructor, or flight school. They can be structured around five key areas that cover all phases of flight: Plan, Brief, Do, Review, and Renew.

  • Plan (Flight Preparation): Ensure readiness by addressing pilot, aircraft, environment, and external pressures (PAVE) using a structured preflight approach.
  • Brief (Shared Mental Models): Align expectations through preflight, passenger, and phase-specific briefings to enhance coordination and preparedness.
  • Do (Execution of the Flight): Use checklists, callouts, and standard profiles (routines) to maintain consistency.
  • Review (Post-Flight Analysis): Conduct debriefs to identify lessons learned and guide future improvements.
  • Renew (Continuous Improvement): Regularly refine skills and update procedures.

SOPs for Visual Scanning and Collision Avoidance

  • Keep cockpit windows clean and free of obstructions.
  • Fly the correct en-route altitude for the direction of flight.
  • Monitor local airport frequencies to “get the picture” of the traffic in the area.
  • Develop a systematic scanning technique and have everyone on the aircraft help scan for traffic.
  • Avoid practicing flight maneuvers near instrument approach areas or extended runway centerlines.
  • Perform clearing turns before all flight training maneuvers, using two 90° turns in opposite directions to visually scan above, below, and around the aircraft.
  • Incorporate verbal callouts during clearing procedures to reinforce vigilance (e.g., “clear left/right,” “clear above/below”).
  • Turn ON all exterior lights, including strobes, in high-traffic areas and near airports to enhance visibility to other aircraft.
  • Be aware of meteorological conditions, including the sun’s angle, that limit the ability to see other aircraft.

SOPs for Radio Communications

  • Use standard phraseology at all times to ensure clear and consistent communication.
  • Listen carefully before transmitting to avoid interrupting or blocking ongoing communications.
  • Eliminate ambiguous terms such as “to” and “for” to prevent confusion with the numbers “2” and “4.”
  • Avoid using “Roger” or “Wilco” when reading back ATC clearances or instructions.
  • Read back all ATC instructions and clearances, including heading, altitude, and hold short directives, to confirm understanding.
  • Request immediate clarification if any ATC instruction is unclear or appears unsafe.
  • Actively monitor the guard frequency (121.5 MHz) on a secondary radio, if equipped, to ensure awareness of emergency broadcasts and missed radio calls.
  • Carry a backup handheld radio transmitter during all flights to maintain communication in the event of primary radio failure.

SOPs for Risk Management

  • Make key decisions on the ground whenever possible, where stress is lower and options are clearer.
  • Use a Flight Risk Assessment Tool (FRAT) to identify, mitigate, and manage risks.
  • Plan ahead by reviewing critical resources, such as the airport diagram, before taxiing.
  • Pause regularly to assess the flight environment using the 5P checklist (Plan, Plane, Pilot, Passengers, and Programming).
  • Maintain heightened situational awareness during critical phases of flight and ground operations, actively scanning for hazards.
  • Set personal minimums that exceed regulatory requirements, accounting for experience, proficiency, and conditions. Maintain proficiency with a regular training plan.

SOPs for Flight Deck Management

  • Do not place headsets or other items on the dashboard to prevent scratching the windscreen.
  • Brief all roles and responsibilities, including pilot flying (PF) and pilot monitoring (PM) duties, before flight.
  • Discuss the initial autopilot modes and expected transitions during the preflight briefing.
  • Use the level of automation that provides the highest margin of safety.
  • Verify each autopilot mode change with a verbal callout.
  • Display the most relevant information for the current phase of flight.
  • Use a three-step verbal and visual handoff process when exchanging flight controls.
  • Instruct passengers to avoid unnecessary conversation during critical phases of flight.
  • Maintain a sterile cockpit during all ground operations, below 2,500′ AGL, and within 10 minutes of landing.

Checklist Usage

Beginning and Ending a Checklist: State the checklist’s name before beginning. Conclude by stating the checklist name and affirming “checklist complete.”

Interrupted Checklists: If the checklist is only delayed for a brief period and the pilot is sure of where he or she was interrupted, the item may be completed, and the checklist may continue. Otherwise, restarting the checklist from the beginning is recommended.

Touch Verification: Enhance accuracy by physically touching each gauge, switch, or control when verifying items. This method minimizes the risk of false confirmations.

Single-Pilot Operations:

  • Use the challenge-and-response method during noncritical phases to enhance focus and prevent omissions.
  • Apply the flow (do-verify) method during high workload phases to complete tasks efficiently, followed by a checklist review for accuracy.

Two-Pilot Operations:

  • Use the challenge-and-response method for critical checklists, including those confirming landing gear and flap configurations.
  • Silent checklists may be used by the pilot monitoring during low workload phases but must conclude with a verbal acknowledgment to ensure mutual understanding.

Emergencies: Use the challenge-and-response method for non-normal and emergency checklists to ensure a methodical approach and reduce the risk of errors during critical situations.

SOPs for Preflight Assessments

  • Adhere to the same preflight procedures without deviation, regardless of time pressures or adverse conditions such as cold temperatures.
  • Maintain a personalized checklist to ensure that maintenance records, aircraft squawks, weather conditions, NOTAMs, and operational-specific items are reviewed before each flight.
  • Do not adjust personal minimums within 24 hours of a planned flight to ensure objective decision-making.
  • Establish a policy of briefing passengers to ensure they understand that safety decisions take precedence over schedules.

SOPs for Taxiing

  • Complete all checklist items, program the avionics, and set the communication and navigation radios before taxiing to reduce workload during movement.
  • Review and brief any changes to the expected taxi route immediately upon receiving instructions to ensure situational awareness.
  • Keep the airport diagram available and use all visual cues, including the heading indicator, to track progress and adhere to the taxi route.
  • Maintain a sterile cockpit to enhance focus and prevent distractions.
  • The parking brake can be used to assist the pilot, but can not be relied upon to hold the aircraft stationary. Feet must remain on the brakes while the aircraft is stopped.

Line-Up-and-Wait Operations (Towered Airports)

  • Turn on traffic information displays, if equipped, and zoom in to monitor nearby traffic.
  • Increase the aircraft’s visibility by turning on all exterior lights except the landing lights. Turn the landing lights on when the aircraft begins rolling.
  • At night, line up slightly left or right of the centerline to help distinguish the aircraft from the runway lights.

SOPs for the Use of Exterior Lighting

  • Engines Running: Rotating beacon ON
  • Sunset to Sunrise: Position lights ON
  • Taxi: Taxi light ON when moving; Taxi light OFF when stopped or yielding
  • Crossing a Runway: All exterior lights ON
  • Line Up and Wait: Landing light OFF; All other exterior lights ON
  • Takeoff and Landing: All exterior lights ON
  • Climb and Descent: All exterior lights ON

SOPs for Traffic Patterns

  • Reach the traffic pattern altitude at least 3 miles from the airport to improve visual scanning.
  • Enter and exit traffic patterns using recommended procedures.
  • Turn landing lights ON within 10 miles of the airport to enhance visibility.
  • Use traffic displays, if equipped, set to an appropriate range (“zoom in”) to supplement visual scanning.
  • Maintain standard flight profiles with consistent airspeeds and configurations on each leg of the pattern.
  • Increase situational awareness at airports with parallel or crossing runways.

SOPs for After Landing and Taxiing

  • Before landing, review the expected runway exit and taxi route to the parking location.
  • Decline last-minute runway exit instructions if unable to comply safely.
  • Clear the runway before stopping to request taxi instructions or resolve confusion.
  • Do not enter or cross a runway without an ATC clearance.
  • Delay nonessential configuration changes until after clearing the runway.
  • Follow ATC instructions exactly and avoid relying on assumptions or expectations.

SOPs for Parking and Securing

  • Continuously monitor the proximity of aircraft, vehicles, equipment, and personnel while operating on airport surfaces.
  • If ramp conditions are hazardous, exit the aircraft before assisting passengers.
  • Escort passengers at all times while on the ramp.
  • Do not leave the airplane unattended unless the wheels are chocked or the airplane is properly secured.

Securing Procedures for Periods of Inactivity

  • Fill the fuel tanks to minimize water condensation inside the tanks.
  • Secure the airplane with wheel chocks and tie-down chains or ropes, as applicable.
  • Release the parking brake after the wheel chocks are installed or the airplane is tied down.
  • Install pitot tube covers, cowling inlet covers, flight control gust locks, window sunscreens, and security locks, as applicable.

Extended Use of the Parking Brake

Once the airplane is properly secured, the parking brake should be released to relieve pressure in the braking system.

Reasons to release the parking brake after securing the airplane include:

  • Prolonged brake pressure may contribute to brake seal wear or hydraulic fluid leakage.
  • Brake pads may freeze to the rotors in cold weather conditions.
  • The airplane may need to be repositioned or towed by ground personnel.

Extended Use of the Parking Brake

Once the airplane is properly secured, the parking brake should be released to relieve pressure in the braking system.

Reasons to release the parking brake after securing the airplane include:

  • Prolonged brake pressure may contribute to brake seal wear or hydraulic fluid leakage.
  • Brake pads may freeze to the rotors in cold weather conditions.
  • The airplane may need to be repositioned or towed by ground personnel.

Standard Crew Callouts

Flight Deck Management

Action PF PM
Confirm understanding of ATC instructions “I heard [instruction]” Reads back the ATC instruction
Change to an altitude or heading selection “[altitude/heading] set” Sets the heading/altitude
Change to an autopilot or flight director mode “Engage [mode]” “[mode] active/on”
Checklist accomplishment Calls for the checklist by name, “[checklist title] checklist” Completes the checklist, “[checklist title] checklist complete”
Action PF PM
Deviations from the intended flightpath are detected “Correcting” States the deviation

Ground Operations

Action/Condition PF PM
Before engine start “Clear prop!”
Before taxiing, turning, crossing a taxiway/runway, or entering a runway for takeoff “Clear right” or “Clear left” “Clear left” or “Clear right”
Before crossing a runway “Crossing runway [number]” Reads back the ATC instruction
Hold short instructions received “Holding short runway [number]” Reads back the ATC instruction
Action/Condition PF PM
Line up and wait (LUAW) instructions received “Lining up and waiting runway [number]” Reads back the ATC instruction
Just before takeoff “Runway [number] verified, heading [initial heading], altitude [initial altitude]” Confirms the PF’s statements

Takeoff Roll

Action PF PM
Begin the takeoff roll “Power set, T&P’s in the green”
Airspeed alive “Airspeed alive”
At rotation speed “Rotate”
Engine failure or other abnormality before rotation “Aborting” “Abort, abort, abort!”

Note: “T&P’s in the Green” means the engine temperatures and pressures are in their normal ranges.

Climbing and Descending

Action PF PM
1,000′ before reaching the level-off altitude “1,000 to go” “1,000 to go”
At the level-off altitude “Leveling at [altitude]”

Instrument Approaches

Altitude/Condition PF PM
1,000′ to minimums “Check” “1,000 to minimums”
500′ to minimums “Check” “500 to minimums”
100′ to minimums “Check” “100 to minimums”
At DA/DH “Landing” or “Missed approach” “Minimums”
MDA reached before the MAP “Leveling” “MDA ____ feet”
Descending below the MDA for landing “Leaving the MDA”
At MAP and runway not in sight “Missed approach” “Missed approach point, no contact”
Altitude/Condition PF PM
Approach lights in sight “Continuing” “Approach lights in sight”
Runway in sight “Landing” “Runway in sight”

Instrument Approach Deviations

Condition PF PM
Course deviation ±1 Dot “Correcting” “[Right/Left] of course”
Glideslope deviation ±1 Dot “Correcting” “[Above/Below] glideslope”
Airspeed deviation +10/-5 KIAS “Correcting” “Airspeed”
Sinkrate more than 1,000 FPM “Correcting” “Sinkrate”
Altitude deviation +50’/-0′ of MDA “Correcting” “Altitude”

Before Landing

Condition PF PM
At the minimum stabilization height “Stabilized—Continuing” or “Not stabilized—Going around”
On final approach “Heels on the floor, toes off the brakes”

Complex Airplanes

Action/Condition PF PM
After liftoff “Gear up” “Positive rate”
1,000′ AGL or on the base leg “Blueline—GUMP Check” or “GUMP Check”
Before descending below TPA or upon crossing the FAF inbound “Gear Down Before Landing Checklist” Completes the checklist