Passenger Safety Briefing

References: 14 CFR 91.17, 14 CFR 91.21, 14 CFR 91.107, 14 CFR 91.319, 14 CFR 91.327, 14 CFR 91.519, InFO 26002

The PIC is required to:

• Brief passengers on how to fasten and unfasten their safety belts.
• Notify passengers to fasten their safety belts before taxi, takeoff, and landing.
• For experimental and light-sport aircraft, notify each passenger of the aircraft's special nature.
• For large and turbine-powered airplanes, comply with 14 CFR 91.519 (passenger briefing).

Except in an emergency, do not carry passengers who appear intoxicated or show physical or behavioral signs of being under the influence of drugs, unless they are medical patients under proper care. Impaired or intoxicated passengers seated near the flight controls can create a direct interference hazard.

Elements of a passenger "SAFETY" briefing:

• Seat Belts: How to fasten and unfasten; Required during taxi, takeoff, and landing
• Air: How to operate the environmental controls; The location of vents and airsickness bags; Smoking is prohibited
• Fire Extinguisher: Its location, how to unlatch it from its mount, and how to use it
• Exits, Emergencies, and Equipment: The location and operation of doors and emergency exits; Emergency procedures; The location and use of emergency and survival equipment
• Traffic and Talking: The importance of visual scanning; Sterile cockpit requirements
• Your Questions?: Allow passengers to ask questions

Other items to consider:

• If under IFR, the allowed use of portable electronic devices
• If flying over water, ditching procedures
• PIC authority

Related:

• Federal Aviation Regulations: Use of Portable Electronic Devices
• Federal Aviation Regulations: Use of Safety Belts and Shoulder Harnesses

Checklist Usage

Reference: SAFO 17006

Checklists act as a systematic guide, ensuring that all procedures are carried out in the correct sequence and nothing is omitted. Furthermore, they standardize flight operations, thereby minimizing the chances of human error.

Related: Pilot Training and Testing Standards: Applicant's Use of Checklists

Pilot Flying and Pilot Monitoring

Many checklists differentiate between checklist items by using the terms pilot flying (PF) and pilot monitoring/pilot not flying (PM/PNF) to avoid confusion. The PF is the pilot manipulating the controls, regardless of seat position.

Checklist Accomplishment Methods

The proper use of a checklist depends on the task being conducted. In some situations, using the checklist would be unsafe or impractical, especially in a single-pilot operation. In this case, reviewing the checklist after the elements are completed would be appropriate.

Challenge-And-Response (Do-List): A typical checklist has two columns. The left column shows the switch or control that needs to be moved or verified (the challenge), and the right column shows the action to take with the switch or control (the response). Each challenge is read, followed by the necessary task or check being completed. A response is made only after verifying that the proper configuration or condition exists.

Flow (Do-Verify): A mental "flow" check can be used in high workload situations. The flow is a systematic scan of the instrument panel. It shows the pilot what items to consider, not what to do. After completing the flow, the checklist is read to verify that all items have been completed.

Use of Commercially or Personally Developed Checklists

Note: Pilots operating under 14 CFR Part 121 or 135 are prohibited from using unapproved checklists.

Pilots may purchase or adapt checklists to streamline operations and incorporate personal preferences. Any changes must be thoroughly reviewed to ensure they align with the manufacturer's recommendations and aircraft limitations.

Adapting emergency checklists is generally not recommended due to the critical nature of these procedures. Improperly adapted checklists can lead to missed steps, procedural errors, and reduced safety margins during critical situations.

Electronic Flight Bags

Reference: AC 91-78

Electronic flight bags (EFBs) provide flight information and applications traditionally carried in a pilot's flight bag. They can replace paper information when used in accordance with applicable operating rules.

Related: Federal Aviation Regulations: Use of Electronic Flight Bags

Best Practices for Electronic Flight Bag Use

• Before flight, verify that the device, applications, charts, and databases are up to date.
• Know each operational function before using it in flight.
• Cross-check data entries and computed information.
• Secure or stow portable devices so they do not obstruct controls or outside visibility.
• Plan for device, application, power, or thermal failure so required information remains available.

Global Positioning System

References: 14 CFR 43.3, AIM 1-1-17, AIM 1-1-18, AIM 1-2-3, AC 90-100

The Global Positioning System (GPS) consists of a network of satellites managed by the U.S. Air Force. The U.S. is committed to maintaining the availability of at least 24 operational GPS satellites. To ensure this, 30 or more satellites travel in semi-synchronous (12-hour) orbits around the Earth.

GPS Limitations for VFR Operations

• VFR pilots should avoid relying solely on one navigation system. GPS should be supplemented by pilotage and dead reckoning.
• VFR-only panel-mount units must be placarded or display an annunciation prohibiting use under IFR.

GPS Limitations for IFR Operations

• Hand-held GPS systems are not authorized for IFR navigation, instrument approaches, or as a primary instrument flight reference.
• Not all panel-mount units are IFR-approved, and not all IFR-approved receivers are installed according to IFR operational requirements.
• Pilots must comply with the GPS limitations and operate within the approval criteria (en route, terminal, or approach) listed in the AFM/POH.
• Aircraft navigating by an IFR-approved GPS are considered to be Performance-Based Navigation (PBN) aircraft and have specific equipment suffixes.

Database Requirements

• At system initialization, pilots must confirm the navigation database is current and verify the aircraft's present position.
• Updates are typically issued every 28 days. Under 14 CFR 43.3, they are not considered maintenance and may be performed by pilots.
• If the chart cycle changes during a flight, pilots should check if an applicable chart amendment exists. If an amended chart is published for the procedure, the database must not be used to conduct the operation.

Preflight Requirements

Non-GPS/WAAS Receivers: RAIM availability must be confirmed for the intended route of flight.

RAIM Unavailable: In situations where RAIM is predicted to be unavailable, the flight must rely on other approved navigation equipment, reroute to where RAIM is available, delay departure, or cancel the flight.

WAAS Unavailable: Outside the WAAS coverage or if the WAAS fails, GPS/WAAS equipment reverts to GPS-only operation and satisfies the requirements for basic GPS equipment. Operators must verify GPS RAIM availability.

Alternate Airport Planning Requirements

Without RAIM: Any required alternate airport must have an available instrument approach procedure that does not require the use of GPS.

With RAIM and FDE (no WAAS): Pilots may plan to use a GPS-based IAP at either the destination or the alternate airport, but not at both locations. A preflight RAIM prediction must confirm availability at the airport where the RNAV (GPS) approach will be flown.

With RAIM, pilots may plan for alternate airport minimums using:

• LNAV or circling MDA;
• LNAV/VNAV DA if using approved Barometric Vertical Navigation (baro-VNAV) equipment; or
• RNP 0.3 DA if they are specifically authorized and are using approved baro-VNAV equipment.

With WAAS: Pilots may plan to use any instrument approach procedure authorized for use with their WAAS avionics at the destination and the required alternate with the following restrictions.

• When using WAAS at an alternate airport, flight planning must be based on one of the following:
  • The RNAV (GPS) LNAV minimums or circling minimums.
  • The minimums on a GPS approach procedure.
  • A conventional approach procedure with "or GPS" in the title.
• Pilots must use 14 CFR Part 91 guidance for non-precision approach procedures (ceiling 800' and visibility 2 SM) to determine the IFR alternate airport weather minimums.
• Upon arrival at an alternate, the approach can be completed using the displayed level of service (e.g., LNAV/VNAV or LPV).

Related: Navigation and Flight Planning: Alternate Airport Planning

Arrival, Departure, and Approach Requirements

• The GPS must be set to terminal (±1 NM) course deviation indicator (CDI) sensitivity to fly published departure procedures.
• Localizer-based approach procedures are not authorized to fly using GPS.
• Authorization for GPS-based instrument approaches and departures is limited to U.S. airspace. Operations outside the U.S. must be authorized by the appropriate sovereign authority.

Flight Deck Organization

Reference: InFO 07001

A place for everything and everything in its place.

Benjamin Franklin

Before starting the engine, items should be secured and placed within easy reach. These small steps reduce workload and improve safety. Because each pilot organizes differently, the best setup is usually developed through experience.

Best Practices for Flight Deck Organization

• Use a flight bag to secure loose items that won't be needed in flight.
• Do not block the flight controls with mounted accessories, cords, or lap organizers (kneeboards).
• Do not mount electronics or other devices where they obstruct the windshield or windows; preserve an unobstructed view in all directions.
• Confirm that noise-canceling headsets do not mask required aural warnings or important environmental sounds, including abnormal mechanical sounds, wind noise, or sounds from nearby aircraft during ground operations.

Automation Management

Reference: InFO 16022

Effective automation management enables the pilot to assess, detect, and correct errors, helping prevent accidents.

Active Automation Management

Automation should be managed actively rather than passively ("set and forget"). Active automation management enhances situational awareness and helps to identify automation failures.

To actively manage the automation, pilots must:

• Cross-reference data from various systems.
• Monitor the flight progress (e.g., waypoints and fuel burn).
• Know how the technology normally performs and its failure modes.
• Be ready to take action if the system does not perform as expected.
• When operating concentric knobs, verify the intended setting and check for unintended changes to other settings.

Autopilot Mode Verifications

Caution: Anytime the autopilot is disconnected, the pilot should have a firm grip on the controls to counter any unexpected trim forces.

Autopilot management errors can be reduced by:

• Verifying each button press is recognized by the system.
• Making callouts after every mode change and when arming the system.

Automation Management Errors

Humans are not well suited to monitoring automated systems. Extended periods of performing trivial tasks often lead to daydreaming or complacency.

Monitoring errors can be reduced by:

• Guarding against fixation.
• Making consistent verifications and callouts.
• Scanning the instruments in the same way as when hand flying.

Related: Risk Management: Automation Bias

Aeronautical Decision-Making

Aeronautical decision-making (ADM) is a systematic approach to the mental process used by pilots to consistently determine the best course of action in response to a given set of circumstances.

ADM = What pilots intend to do based on the information they have.

The Decision-Making Process

Note: This process is a simplified version of the DECIDE model and parallels the 3P risk management process.

1. Define the Problem: A problem is recognized when something changes or when an expected change does not occur. Available information is used to determine the nature and severity of the problem.

2. Choose a Course of Action: The available actions are considered based on the situation, time available, expected outcome, and level of risk.

3. Implement and Evaluate: The selected action is performed, and the outcome is evaluated to determine whether it is producing the desired result.

Related: Decision-Making Worksheet

Single-Pilot Resource Management

Single-pilot resource management (SRM) is the art and science of managing all resources (internal and external) available to a single pilot (before and during flight) to ensure the successful outcome of the flight.

SRM includes the concepts of:

• Situational awareness
• Flight deck management
• Aeronautical decision-making (ADM)
• Controlled flight into terrain (CFIT) awareness

Related:

• Visual Scanning and Collision Avoidance: Controlled Flight into Terrain
• Risk Management: Situational Awareness
• Risk Management: Aeronautical Decision-Making

Use of Resources

Pilots must be aware of the resources found both inside and outside the flight deck to make informed decisions.

Internal: Resources found in the airplane. They include the avionics, autopilot, checklists, the AFM/POH, and passengers.

External: Resources available during flight include ATC and flight service stations (FSS). ATC can help reduce pilot workload by providing traffic advisories, radar vectors, and assistance during emergencies. An FSS can provide weather and airport condition updates.

Crew Resource Management

References: 14 CFR 1.1, AC 120-51, AC 120-123, SAFO 15011

Crew resource management (CRM) makes optimum use of all available resources in a flight deck environment. The "crew" encompasses anyone working with the flight crew, including dispatchers, cabin crew, maintenance personnel, and ATC.

The key to crew coordination is "saying the right thing, to the right person, at the right time, in the right way."

Related:

• Before-Takeoff Check: Takeoff Briefing
• Crew and Passenger Briefings
• Flight Lesson Briefing Guide

Pilot Monitoring and Pilot Flying

At any point during a flight, one pilot is flying, and one pilot is monitoring.

The pilot flying (PF):

• Avoids tasks or activities that distract from flying the aircraft.
• Is responsible for managing the aircraft's flightpath and energy.
• Is always engaged in flying the aircraft (even when the autopilot is on).

The pilot monitoring (PM):

• Supports the PF at all times.
• Is responsible for monitoring the aircraft's flightpath and energy.
• Calls out deviations and intervenes if necessary.

If the PF needs to engage in activities that would distract from aircraft control, the PF should transfer aircraft control to the other pilot and assume the PM role.

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 a delay is brief and pilots are certain where the interruption occurred, they may complete the item and continue the checklist. Otherwise, restart the checklist from the beginning.

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 to verify 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.

Related: Inflight Emergencies: Checklist Usage During Emergencies

Common Errors in Flight Deck Management

• Over or under-reliance on automation
• Failure to prioritize tasks effectively
• Neglecting to use a written checklist
• Missing checklist items due to interruptions or lack of attention
• Neglecting to conduct a passenger safety briefing
• Inadequate use of all available resources

Risk Examples for Preflight Preparation and Procedures

Inoperative Equipment Discovered Before Flight

• Failure to recognize and report inoperative equipment compromises flight safety and violates regulations; follow proper procedures for managing inoperative equipment.
• Misjudging the significance of inoperative equipment can compromise flight safety; consult with maintenance or experienced personnel for proper evaluation.

Use of Systems or Equipment

• Misuse or overreliance on automation can reduce situational awareness and lead to improper flight management; use automation effectively and understand its capabilities.
• Distraction from portable electronic devices can lead to errors and compromise safety; minimize their use during critical phases of flight.

Passenger Distractions

• Passenger conversations can lead to a loss of situational awareness and an increased potential for errors; establish communication protocols before flight.