SlideShare a Scribd company logo
1 of 14
Download to read offline
Standard Operating Procedures
Flight Operations Briefing Notes                                           Conducting Effective Briefings




                                                 Flight Operations Briefing Notes
                                                      Standard Operating Procedures
                                                        Conducting Effective Briefings




    I   Introduction
        To ensure mutual understanding and effective cooperation among crewmembers and
        with ATC, in-depth takeoff and approach / go-around briefings should be conducted on
        each flight.
        A thorough briefing should be conducted regardless of:
        •   How familiar the departure airport / SID or destination airport / approach may be;
            or,
        •   How often the crewmembers have flown together.

        This Flight Operations Briefing Note provides generic guidelines for conducting effective
        and productive briefings.
        Effective briefings should be short, structured, concise and adapted to the particular
        conditions of the takeoff or approach-and-landing.
        The information provided hereafter has been expanded on purpose to provide
        an opportunity to review and discuss in details each briefing item.


   II   Statistical Data
        The quality of approach and go-around briefings is observed as a causal factor in
        approximately 50 % of approach-and-landing accident ( source : Flight Safety
        Foundation – 1998-1999 ), by affecting:
        •   Understanding of prevailing conditions;
        •   Horizontal or vertical situational awareness; and,
        •   Crew coordination.




                                                Page 1 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                                 Conducting Effective Briefings




  III   Objectives of Briefings
        Crew briefings ( i.e., PF to PNF briefings ) are aimed at the following objectives,
        in support of standard operating procedures (SOPs) :
        •   Define and communicate         action     plans   and    expectations,   under   normal   or
            non-normal conditions;
        •   Confirm applicable task sharing (i.e., crew members’ roles and responsibilities);
        •   Brief specific areas to the required level of details;
        •   Promote inquiry / advocacy and feedback;
        •   Ensure full understanding and agreement by both crew members on sequence
            of actions; and,
        •   Communicate objectives to other crew members (e.g., cabin crew, as applicable).

        Briefings are also intended to enhance the flight crew and cabin crew preparedness
        for facing unusual requirements or responding to unanticipated conditions
        ( i.e., « expecting the unexpected » ).


  IV    Briefing Techniques
        The importance of briefing techniques often is underestimated, although effective
        briefings contribute to enhance crew standardization and communication.

        The style and tone of the briefing play an important role; interactive briefings
        – i.e., confirming the agreement and understanding of the PNF after each phase of the
        briefing – provides more effective and productive briefings than an uninterrupted
        recitation terminated by the final query « Any question ? » .

        Interactive briefings better fulfill an important purpose of the briefings, that is
        to provide the PF and PNF with an opportunity to correct each other (e.g., confirming
        the use of the correct and effective departure / approach chart, confirming the correct
        setup of navaids for the assigned takeoff / landing runway, etc).

        Briefings should be structured (i.e., follow the logical sequence of the takeoff /
        departure or approach / landing) and concise.

        The routine and formal repetition of the same points on each sector may become
        counterproductive; adapting and expanding the briefing by highlighting the special
        aspects of the airport and departure / approach procedure or the prevailing weather
        conditions and circumstances result in more lively and effective briefings.

        In short, the briefing should encourage effective listening to attract the PNF’s attention.




                                                    Page 2 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                           Conducting Effective Briefings




       The briefing should therefore be conducted when the workload and availability of
       the PNF permit an effective communication.

       Any aspect that may affect normal operation (e.g., system failures, weather conditions
       or other particular conditions) should be carefully evaluated and discussed.

       The briefing should help both the PF (giving the briefing) and the PNF (receiving and
       acknowledging the briefing) understanding the sequence of events and actions, as well
       as the special hazards and circumstances of the takeoff, departure, approach and
       landing (i.e., by creating a common mental model of the takeoff or approach).

       Whether anticipated or not, changes in an air traffic control (ATC) clearance, weather
       conditions or landing runway require reviewing part of the initial briefing.


   V   Timeliness of Briefings
       Briefings should be conducted during low-workload periods.
       The takeoff Briefing should be conducted while the aircraft is stationary (i.e., at the
       gate or other parking position).
       Rushing during descent and approach is a significant factor in approach-and-landing
       incidents and accidents.
       To prevent any rush in initiating the descent and the resulting increased workload
       in conducting the approach, the descent preparation and the approach and go-around
       briefings typically should be completed 10 minutes before reaching the top-of-descent.


  VI   Scope of Briefings
       A study of team performance indicates that the quality of the pre-flight briefings
       ( i.e., flight crew / cabin crew briefing and flight crew takeoff briefing) shapes the
       quality of the crew performance throughout the entire flight.
       The pre-flight briefings start at the dispatch office when the Dispatcher hands over
       the Flight Folder / Dossier to the flight crew, for review and final decision on the route,
       cruise flight level and fuel quantity.
       The on-board takeoff briefing should include the following generic aspects of the takeoff
       and departure phase :
       •   Takeoff and departure conditions (i.e., weather and runway conditions, special
           hazards);
       •   Lateral and vertical navigation (i.e., intended use of automation);
       •   Communications;
       •   Non-normal procedures, as applicable; and,
       •   Review and discussion of takeoff and departure hazards.




                                               Page 3 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                            Conducting Effective Briefings




        The approach and go-around briefings should cover the following generic aspects of
        the approach and landing, including a possible missed approach and a second approach
        or diversion:
        •   Approach conditions (i.e., weather and runway conditions, special hazards);
        •   Lateral and vertical navigation (i.e., intended use of automation);
        •   Instrument approach procedure details;
        •   Communications;
        •   Non-normal procedures, as applicable; and,
        •   Review and discussion of approach-and-landing hazards.

        These aspects are expanded and discussed in details in this Flight Operations Briefing
        Note.


  VII   Takeoff Briefing
        The takeoff briefing is conducted by the crewmember designated as Pilot Flying (PF) for
        the flight leg.

        The takeoff briefing enables the PF to inform the PNF of the planned course of actions
        (i.e., expectations, roles and responsibilities, unique requirements) for both normal and
        abnormal conditions during the takeoff phase.

        A full takeoff briefing should be conducted on the first sector of the day, subsequent
        briefings should be limited to the specific aspects of each individual airport / runway /
        takeoff / SID conditions.

        The takeoff briefing should be guided and illustrated by referring to the applicable FMS
        pages and to the ND (e.g., to visualize the departure route and confirm
        the various data entries, …).

        An expanded review of the items to be covered in the takeoff briefing – as practical and
        appropriate for the conditions of the flight – is provided hereafter.


 VII.1 ATIS :
        Review the last ATIS message, including :
        •   Expected takeoff runway in use and SID:
        •   QNH / QFE;
        •   Transition altitude (if variable with QNH);
        •   Weather, OAT / Dew point;
        •   Wind and runway condition.




                                                 Page 4 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                           Conducting Effective Briefings




 VII.2 NOTAMs :
       Review and discuss takeoff and departure NOTAMs, as applicable, for possible
       operational impact, e.g. :
       •   Unserviceable navaids, change of departure routing, airspace restrictions, ….;
           and/or,
       •   Specific threats / hazards (e.g., work-in-progress on taxiways and/or runways,
           obstructions, man-made obstacles, volcanic activity, …).

       In case of any doubt on the contents or interpretation of a NOTAM, contact
       the company Dispatch office for confirmation.


 VII.3 Weather Briefing :
       Based on the weather briefing conducted by the dispatcher and on last ATIS
       information, discuss the effect of prevailing weather conditions on takeoff and
       departure procedures (e.g., use of weather radar in case of suspected windshear,
       requirement for a takeoff alternate, use of engine and wing anti-ice, …).


 VII.4 Dispatch Conditions ( MEL ) affecting Takeoff Performance :
       Review and discuss any dispatch condition (i.e., dispatch under MEL/DDG) that affects :
       •   Takeoff performance (i.e., takeoff weight and/or speeds); or,
       •   Fuel consumption.

       Ensure that dispatch conditions are compatible with the flight to be performed and do
       not combine conditions (i.e., inoperative items) that cannot be combined
       (i.e., exclusive dispatch conditions).


 VII.5 Takeoff Performance Limitations :
       Review and discuss prevailing takeoff performance limitation (e.g., runway, second
       segment, obstacle, …) as well as any specific takeoff performance limitation (i.e.,
       minimum climb gradient during SID, non-standard turn, EOSID, …).


 VII.6 Weight and Balance Data - Load Sheet Review :
       Review weight and balance data (i.e., preliminary data from the Flight Folder / Dossier
       or final Load & Trim Sheet).


 VII.7 Runway Condition and Wind :
       Confirm the expected takeoff runway, the runway condition and wind component.




                                              Page 5 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                            Conducting Effective Briefings




 VII.8 Takeoff Data :
       Confirm the computed takeoff data for the prevailing conditions, i.e. :
       •   Slats / Flaps configuration;
       •   V-speeds (i.e., V1, VR, V2 – F, S, Green Dot speeds or V3, V4, VFTO);
       •   Thrust setting (i.e., TOGA or FLEX …); and,
       •   Confirm the air bleed configuration for takeoff, i.e. :
           −   Air-conditioning packs / engine anti-ice / wing anti-ice.


 VII.9 Noise Abatement Procedure (as applicable) :
       Review and discuss the applicable noise-abatement procedure, particularly if the noise
       abatement procedure is not standard and / or not programmed in the FMS.


VII.10 Departure Route ( SID ) :
       Review and discuss the following elements, with reference to the FMS CDU, ND , FCU
       and chart :
       •   First cleared altitude (if departure clearance available);
       •   Transition altitude;
       •   Routing (i.e., speed and/or altitude constraints, airspace restrictions, terrain /
           MSA);
       •   Specific procedures in case of loss of communication (NORDO); and,
       •   Special procedures or considerations, as applicable.


VII.11 Navaids Setup – Use of Automation :
       Set navaids as required to fly and/or cross-check the correct tracking of the SID
       by the FMS, or in readiness to fly the EOSID or for an immediate return.


VII.12 Rejected Takeoff Briefing :
       The rejected takeoff ( RTO ) part of the takeoff briefing should include the following
       sections :
       •   Stop or Go Decision;
       •   Stop Actions; and,
       •   Go Actions.

       The RTO briefing is described and discussed in details in the Flight Operations Briefing
       Notes Revisiting the Stop or Go Decision.




                                                Page 6 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                          Conducting Effective Briefings




VII.13 Taxi to Active Runway :
       The taxi phase should be considered as a critical phase of flight and be carefully
       briefed.

       Using the airport chart, perform a review of the expected taxi routes with special
       attention to « hot spots » (i.e., intersections where the risk of confusion and
       the resulting risk of taxiway or runway incursion may exist).

       Plan the execution of checks and actions to be performed during taxi in order to
       prevent distraction by cockpit duties when approaching hot spots.

       Pay particular attention to temporary situations such as work in progress, other unusual
       activity and recent changes in airport layout.

       When taxi instructions are received from ATC, PF and PNF should refer again to
       the airport diagram to verbally agree on the assigned runway and taxi route, including
       instructions to hold short of or cross an intersecting runway.

       Be aware that the expectations established during the takeoff briefing can be
       significantly altered with a different and unexpected taxi clearance (i.e., be prepared to
       follow the clearance or instructions you actually received, and not the one you expected
       to receive).

       As applicable, discuss the low-visibility taxi procedures and routes (if published) and
       the characteristics of the airport surface movements guidance and control system
       (SMGCS).

       For more information on the prevention of taxiway and / or runway incursions, refer to
       the Flight Operations Briefing Note dedicated to Preventing Runway Incursions.


VII.14 Deviations from SOPs :
       Any intended deviation from SOPs or from standard calls should be discussed during
       the briefing.


VII.15 Briefing Confirmation during Taxi :
       Confirm the elements of the detailed takeoff briefing for possible changes (e.g., runway
       change, intersection takeoff, runway condition change, revised departure clearance, …).
       Confirm the takeoff data or modify the aircraft configuration (i.e., flaps, bleeds, …),
       the thrust setting (i.e., FLEX or TOGA) and the FMS / FCU setup, as required.




                                               Page 7 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                           Conducting Effective Briefings




 VIII   Cruise Briefing(s)
        As practical, depending on the duration of the cruise phase, it is recommended
        performing a structured cruise briefing – or repeated cruise briefings - covering
        the following aspects, as applicable, e.g. :
        •   Strategy in case of engine failure (e.g., speed strategy depending on obstacles and
            ETOPS/non-ETOPS nature of flight, preferred diversion airfield depending on aircraft
            position, …); and,
        •   Strategy in case of cabin depressurization (e.g., speed strategy, …).


  IX    Approach Briefing
        FMS pages and ND should be used to guide and illustrate the briefing, and to confirm
        the various data entries.
        An expanded review of the items to be covered in the approach briefing – as practical
        and appropriate for the conditions of the flight – is provided hereafter.


  IX.1 Aircraft Status :
        Review the aircraft STATUS, as applicable (i.e., any failure or malfunction experienced
        during the flight) and discuss the possible consequences in terms of operation and
        performance (i.e., final approach speed and landing distance).


  IX.2 Fuel Status :
        Review the fuel status:
        •   Fuel on board;
        •   Minimum diversion fuel; and,
        •   Available holding fuel and time.


  IX.3 ATIS :
        Review and discuss the following items:
        •   Runway in use (type of approach);
        •   Expected arrival route (standard terminal arrival [ STAR ] or radar vectors);
        •   Altimeter setting (QNH or QFE, as required),
            −   For international operations, be aware of the applicable altimeter setting unit
                (hectopascals or inches-of-mercury);

        •   Transition level (unless standard transition levels are used in the country or for the
            airport);




                                                Page 8 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                            Conducting Effective Briefings




       •   Terminal weather (e.g., icing conditions, turbulence, suspected low-level windshear,
           ceiling and visibility / RVR, …); and,
       •   Advisory messages (as applicable).


  IX.4 NOTAMs :
       Review and discuss enroute and terminal NOTAMs, as applicable, for possible
       operational impact (e.g., unserviceable navaids, airspace restriction, obstructions /
       man-made obstacles, …) or additional threat / hazards.
       In case of any doubt on the contents or interpretation of a NOTAM, contact
       the company Flight Watch office for confirmation.


  IX.5 Top-of-Descent Point :
       Confirm or adjust the top-of-descent ( TOD ) point, computed by the FMS, as a function
       of the expected arrival (i.e., following the published STAR or expecting radar vectors).
       Be aware of the resulting track-distance between the TOD point and the runway
       threshold.


  IX.6 Approach Chart :
       Review and discuss the following items using the approach chart and the FMS/ND
       (as applicable):
       •   Designated runway and approach type (confirm the designated PF for the approach,
           in line with company policy for the type of approach to be flown);
       •   Chart index number and date;
       •   Minimum Safe Altitude (MSA) - reference point, sectors and minimum sector safe
           altitudes;
       •   Let-down navaid(s), type, frequency and identifier (confirm the correct setup
           of navaids);
       •   Radio frequencies (discuss special procedures in case of loss of communications –
           NORDO – as applicable);
       •   Airport elevation;
       •   Approach transitions (IAF, IF, other fixes, holding pattern, altitude and speed
           constraints/restrictions, required navaids setup);
       •   Final approach course (and lead-in radial, as applicable);
       •   Terrain features (location and elevation of hazardous terrain or man-made
           obstacles);




                                                Page 9 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                              Conducting Effective Briefings




       •   Approach profile view (i.e., including crossing altitudes) :
           −   Final approach fix (FAF);
           −   Final descent point (if different from FAF);
           −   Outer marker (OM), as applicable;
           −   Visual descent point (VDP), if indicated on approach profile or if computed
               by flight crew;
           −   Missed-approach point (MAP);
           −   Typical vertical speed (V/S) for the expected final approach ground speed (GS);
               and,
           −   Touchdown zone elevation (TDZE).

       •   Missed approach :
           −   Lateral and vertical navigation; and,
           −   Speed restrictions.

           Refer to paragraph X. for a detailed description of the Go Around Briefing.

       •   Visibility/RVR minimums (and ceiling, as applicable);

       •   Descent/decision minimums:
           −   MDA(H) for non-precision approaches;
           −   Barometric DA(H) for CAT I ILS approaches; or,
           −   Radio-altimeter DH for CAT II and CAT III ILS approaches.

       •   Local airport requirement (e.g., noise restrictions on the use of thrust reversers,
           etc).


  IX.7 Airport Chart / Diagram :
       Review and discuss the following items using the airport chart:
       •   Runway length, width and slope;
       •   Approach and runway lighting, and other expected visual references;
       •   Specific hazards (as applicable); and,
       •   Intended turnoff taxiway.

       If another airport is located in the close vicinity of the destination airport, relevant
       details or procedures should be discussed for awareness purposes.




                                                Page 10 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                            Conducting Effective Briefings




  IX.8 Use of Automation :
       Discuss the intended use of automation for vertical / lateral guidance and for speed
       guidance, depending on FMS navigation accuracy (only for aircraft not equipped with
       GPS or if GPS PRIMARY LOST is displayed):
       •   Use of FMS vertical navigation and lateral navigation or use of selected vertical
           modes and lateral modes; and,
       •   Step-down approach (if a constant-angle non-precision approach – CANPA - is not
           available or not possible).


  IX.9 Use of Aircraft Systems :
       Discuss the use of the following aircraft systems, depending on prevailing conditions :
       •   Nacelle / engine anti-ice;
       •   Wing anti-ice;
       •   Weather radar; and,
       •   [ … ].


 IX.10 Landing and Stopping :
       Discuss the intended landing flaps configuration (if different from full flaps).

       Review and discuss the following features of the intended landing runway:
       •   Surface condition (i.e., nature and depth of contaminant, as applicable);
       •   Intended use of autobrake (i.e., intended mode) and thrust reversers; and,
       •   Expected runway turn-off taxiway.


 IX.11 Taxi to Gate :
       The taxi phase should be considered as a critical phase of flight and be carefully
       briefed.
       Review and discuss the following items :
       •   Anticipated taxiways to taxi to the assigned gate (e.g., back-track on active runway
           or on parallel runway, with special emphasis on the possible crossing of active
           runways, as applicable);
       •   Non-standard lighting and/or marking of taxiways; and/or,
       •   Possible work in progress on runways and taxiways.

       As required, this review and discussion can be delayed until after landing.




                                               Page 11 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                            Conducting Effective Briefings




 IX.12 CAT II / CAT III ILS briefing :
        For CAT II and CAT III ILS approaches, perform the specific CAT II (CAT III) briefing
        in accordance with company’ SOPs.


 IX.13 Deviations from SOPs :
        Any intended deviation from SOPs or from standard calls should be discussed during
        the briefing.


   X    Go Around Briefing
        A detailed go-around briefing should be included in the descent-and-approach briefing,
        highlighting the key points of the go-around maneuver and missed-approach, and
        the task sharing under normal or abnormal / emergency conditions.

        The go-around briefing should recall briefly the following key aspects:

        •   Go-around callout (i.e., a loud and clear go-around / flaps call);

        •   PF/PNF task sharing (i.e., flow of respective actions, including use of AP, speed
            restrictions, go-around altitude, parameter-excessive-deviation callouts);

        •   Intended use of automation (i.e., automatic or manual go-around, use of FMS
            lateral navigation or use of selected modes for missed-approach);

        •   Missed-approach lateral navigation and vertical profile (e.g., speed limitations,
            airspace restrictions, highlighting obstacles and terrain features, …, as applicable);
            and,

        •   Intentions (i.e., second approach or diversion) :
            −   In case of a second approach, discuss the type of approach (i.e., if a different
                runway and/or type of approach is envisaged); and,
            −   Confirm the minimum diversion fuel.

        It is recommended to briefly recall the main points of the go-around and missed-
        approach when established on the final approach course or after completing the landing
        checklist (as deemed practical).




                                                Page 12 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                              Conducting Effective Briefings




  XI    Summary of Key Points
        The takeoff, cruise, approach and go-around briefings should be adapted to
        the specific conditions of the flight and focus on the items that are relevant for
        the particular takeoff, departure, cruise phase (e.g., ETOPS, …), approach and landing
        (such as specific flight-phase-related hazards).

        The approach and go-around briefing should include the following ALAR-critical items:
        •   Minimum safe altitude;

        •   Terrain and man-made obstacles features;

        •   Weather and runway condition;

        •   Other approach hazards, as applicable (e.g., visual illusions);

        •   Applicable minimums (visibility or RVR, ceiling as applicable);

        •   Applicable stabilization height (approach gate);

        •   Final approach flight path angle (and vertical speed); and,

        •   Go-around altitude and missed-approach initial steps.


  XII   Associated Briefing Notes
        The following Flight Operations Briefing Notes should be reviewed in association with
        the above information for a complete overview of the operational and human factors
        associated with the conduct of effective briefings :

        •   Operating Philosophy - SOPs

        •   Preventing Runway Incursions

        •   Understanding the Takeoff Speeds

        •   Revisiting the Stop or Go Decision

        •   Being Prepared for Go-around

        •   Effective Pilot / Controller Communications

        •   Human Factors in Incidents and Accidents

        •   CRM Issues in Incidents and Accidents




                                                Page 13 of 14
Standard Operating Procedures
Flight Operations Briefing Notes                                                                       Conducting Effective Briefings




 XIII   Regulatory References
        •    ICAO – Annex 6 – Operation of Aircraft, Part I – International Commercial Air
             Transport – Aeroplanes, Appendix 2, 5.16.
        •    ICAO – Procedures for Air navigation Services – Aircraft operations (PANS-OPS, Doc
             8168), Volume I – Flight Procedures (Post Amendment No 11, applicable
             Nov.1/2001).
        •    ICAO – Preparation of an Operations manual (Doc 9376).
        •    FAR 121.315 – Cockpit Check Procedure, for normal and non-normal conditions.
        •    JAR-OPS 1.1045 and associated Appendix 1, paragraphs A.8 – Operating Procedures
             and B.2.1 – Normal Procedures.


 XIV    Airbus References
        •    Airbus model of JAR-OPS-compliant Operations Policy Manual – Chapter 8 –
             Operating Procedures.
        •    Airbus Flight Crew Operating Manual (FCOM) – Standard Operating Procedures
             (SOPs) chapter.




        This Flight Operations Briefing Note (FOBN) has been adapted from the corresponding ALAR Briefing Note developed by
        Airbus in the frame of the Approach-and-Landing Accident Reduction (ALAR) international task force led by the Flight Safety
        Foundation.

        This FOBN is part of a set of Flight Operations Briefing Notes that provide an overview of the applicable standards,
        flying techniques and best practices, operational and human factors, suggested company prevention strategies and personal
        lines-of-defense related to major threats and hazards to flight operations safety.

        This FOBN is intended to enhance the reader's flight safety awareness but it shall not supersede the applicable regulations
        and the Airbus or airline's operational documentation; should any deviation appear between this FOBN and the Airbus or
        airline’s AFM / (M)MEL / FCOM / QRH / FCTM, the latter shall prevail at all times.

        In the interest of aviation safety, this FOBN may be reproduced in whole or in part - in all media - or translated; any use of
        this FOBN shall not modify its contents or alter an excerpt from its original context. Any commercial use is strictly excluded.
        All uses shall credit Airbus and the Flight Safety Foundation.

        Airbus shall have no liability or responsibility for the use of this FOBN, the correctness of the duplication, adaptation or
        translation and for the updating and revision of any duplicated version.

                                                       Airbus Customer Services
                                             Flight Operations Support and Line Assistance
                                  1 Rond Point Maurice Bellonte - 31707 BLAGNAC CEDEX FRANCE
                                      FOBN Reference : FLT_OPS – SOP - SEQ06 - REV03 – JUNE 2004




                                                               Page 14 of 14

More Related Content

What's hot

Media Object File Flt Ops Sop Seq05
Media Object File Flt Ops Sop Seq05Media Object File Flt Ops Sop Seq05
Media Object File Flt Ops Sop Seq05syed viquar
 
Joint Service Transcripts - David Winchester
Joint Service Transcripts - David WinchesterJoint Service Transcripts - David Winchester
Joint Service Transcripts - David WinchesterDave Winchester
 
Media Object File Flt Ops Gen Seq02
Media Object File Flt Ops Gen Seq02Media Object File Flt Ops Gen Seq02
Media Object File Flt Ops Gen Seq02syed viquar
 
Eidws 104 administration
Eidws 104 administrationEidws 104 administration
Eidws 104 administrationIT2Alcorn
 
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis ToolIHSTFAA
 
2017 Heli-Expo - Helicopter FDM Research.
2017 Heli-Expo - Helicopter FDM Research.2017 Heli-Expo - Helicopter FDM Research.
2017 Heli-Expo - Helicopter FDM Research.IHSTFAA
 
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).IHSTFAA
 
Eidws 101 first aid
Eidws 101 first aidEidws 101 first aid
Eidws 101 first aidIT2Alcorn
 
Vardaman 4page resume_21Apr2016
Vardaman 4page resume_21Apr2016Vardaman 4page resume_21Apr2016
Vardaman 4page resume_21Apr2016David M. Vardaman
 
Eidws 110 operations
Eidws 110 operationsEidws 110 operations
Eidws 110 operationsIT2Alcorn
 
FAASTeam Pers Mins 10-10-2015
FAASTeam Pers Mins 10-10-2015FAASTeam Pers Mins 10-10-2015
FAASTeam Pers Mins 10-10-2015Steve Kiester
 
Tactical_Convoy_Handbook2002
Tactical_Convoy_Handbook2002Tactical_Convoy_Handbook2002
Tactical_Convoy_Handbook2002Kevin Parrish
 
Edwards - ATC Bulleted Resume
Edwards - ATC Bulleted ResumeEdwards - ATC Bulleted Resume
Edwards - ATC Bulleted ResumeGreg Edwards
 
ANA 4-01.45 Convoy OPNS TTP
ANA 4-01.45 Convoy OPNS TTPANA 4-01.45 Convoy OPNS TTP
ANA 4-01.45 Convoy OPNS TTPKevin Parrish
 
NTSB Safety Alert: Reduced Visual Reference s Require Vigilance
NTSB Safety Alert: Reduced Visual Reference s Require VigilanceNTSB Safety Alert: Reduced Visual Reference s Require Vigilance
NTSB Safety Alert: Reduced Visual Reference s Require VigilanceFAA Safety Team Central Florida
 
2016 asprs track: faa and uavs: what you need to know by caitlin reusch
2016 asprs track:  faa and uavs:  what you need to know by caitlin reusch2016 asprs track:  faa and uavs:  what you need to know by caitlin reusch
2016 asprs track: faa and uavs: what you need to know by caitlin reuschGIS in the Rockies
 

What's hot (20)

Media Object File Flt Ops Sop Seq05
Media Object File Flt Ops Sop Seq05Media Object File Flt Ops Sop Seq05
Media Object File Flt Ops Sop Seq05
 
Joint Service Transcripts - David Winchester
Joint Service Transcripts - David WinchesterJoint Service Transcripts - David Winchester
Joint Service Transcripts - David Winchester
 
Media Object File Flt Ops Gen Seq02
Media Object File Flt Ops Gen Seq02Media Object File Flt Ops Gen Seq02
Media Object File Flt Ops Gen Seq02
 
ifr
ifrifr
ifr
 
Personal and Weather Risk Assessment Guide v1.0
Personal and Weather Risk Assessment Guide v1.0Personal and Weather Risk Assessment Guide v1.0
Personal and Weather Risk Assessment Guide v1.0
 
Eidws 104 administration
Eidws 104 administrationEidws 104 administration
Eidws 104 administration
 
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool
2017 Heli-Expo - "What the FRAT?" Helicopter Risk Analysis Tool
 
2017 Heli-Expo - Helicopter FDM Research.
2017 Heli-Expo - Helicopter FDM Research.2017 Heli-Expo - Helicopter FDM Research.
2017 Heli-Expo - Helicopter FDM Research.
 
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).
2017 Heli-Expo "Seeing is Believing" (Advanced Vision Systems).
 
Eidws 101 first aid
Eidws 101 first aidEidws 101 first aid
Eidws 101 first aid
 
Vardaman 4page resume_21Apr2016
Vardaman 4page resume_21Apr2016Vardaman 4page resume_21Apr2016
Vardaman 4page resume_21Apr2016
 
Eidws 110 operations
Eidws 110 operationsEidws 110 operations
Eidws 110 operations
 
FAASTeam Pers Mins 10-10-2015
FAASTeam Pers Mins 10-10-2015FAASTeam Pers Mins 10-10-2015
FAASTeam Pers Mins 10-10-2015
 
Tactical_Convoy_Handbook2002
Tactical_Convoy_Handbook2002Tactical_Convoy_Handbook2002
Tactical_Convoy_Handbook2002
 
Edwards - ATC Bulleted Resume
Edwards - ATC Bulleted ResumeEdwards - ATC Bulleted Resume
Edwards - ATC Bulleted Resume
 
fm4-01.45(05)
fm4-01.45(05)fm4-01.45(05)
fm4-01.45(05)
 
ANA 4-01.45 Convoy OPNS TTP
ANA 4-01.45 Convoy OPNS TTPANA 4-01.45 Convoy OPNS TTP
ANA 4-01.45 Convoy OPNS TTP
 
The Safety Benefits of Angle of Attack Systems
The Safety Benefits of Angle of Attack SystemsThe Safety Benefits of Angle of Attack Systems
The Safety Benefits of Angle of Attack Systems
 
NTSB Safety Alert: Reduced Visual Reference s Require Vigilance
NTSB Safety Alert: Reduced Visual Reference s Require VigilanceNTSB Safety Alert: Reduced Visual Reference s Require Vigilance
NTSB Safety Alert: Reduced Visual Reference s Require Vigilance
 
2016 asprs track: faa and uavs: what you need to know by caitlin reusch
2016 asprs track:  faa and uavs:  what you need to know by caitlin reusch2016 asprs track:  faa and uavs:  what you need to know by caitlin reusch
2016 asprs track: faa and uavs: what you need to know by caitlin reusch
 

Viewers also liked

Media Object File Flt Ops Hum Per Seq04
Media Object File Flt Ops Hum Per Seq04Media Object File Flt Ops Hum Per Seq04
Media Object File Flt Ops Hum Per Seq04syed viquar
 
Media Object File Flt Ops Cab Ops Seq11
Media Object File Flt Ops Cab Ops Seq11Media Object File Flt Ops Cab Ops Seq11
Media Object File Flt Ops Cab Ops Seq11syed viquar
 
Edto module 6 –flight operations considerations
Edto module  6 –flight operations considerationsEdto module  6 –flight operations considerations
Edto module 6 –flight operations considerationsZhipeng Xu
 
Media Object File Maint Bst Prac Seq01
Media Object File Maint Bst Prac Seq01Media Object File Maint Bst Prac Seq01
Media Object File Maint Bst Prac Seq01syed viquar
 
Foo (flight operation officer)
Foo (flight operation officer)Foo (flight operation officer)
Foo (flight operation officer)Vedo Yudistira
 

Viewers also liked (6)

AeroProfessional Flight Operations Support
AeroProfessional Flight Operations SupportAeroProfessional Flight Operations Support
AeroProfessional Flight Operations Support
 
Media Object File Flt Ops Hum Per Seq04
Media Object File Flt Ops Hum Per Seq04Media Object File Flt Ops Hum Per Seq04
Media Object File Flt Ops Hum Per Seq04
 
Media Object File Flt Ops Cab Ops Seq11
Media Object File Flt Ops Cab Ops Seq11Media Object File Flt Ops Cab Ops Seq11
Media Object File Flt Ops Cab Ops Seq11
 
Edto module 6 –flight operations considerations
Edto module  6 –flight operations considerationsEdto module  6 –flight operations considerations
Edto module 6 –flight operations considerations
 
Media Object File Maint Bst Prac Seq01
Media Object File Maint Bst Prac Seq01Media Object File Maint Bst Prac Seq01
Media Object File Maint Bst Prac Seq01
 
Foo (flight operation officer)
Foo (flight operation officer)Foo (flight operation officer)
Foo (flight operation officer)
 

Similar to Media Object File Flt Ops Sop Seq06

Media Object File Flt Ops Fobn Seq02
Media Object File Flt Ops Fobn Seq02Media Object File Flt Ops Fobn Seq02
Media Object File Flt Ops Fobn Seq02syed viquar
 
Media Object File Flt Ops Sop Seq01
Media Object File Flt Ops Sop Seq01Media Object File Flt Ops Sop Seq01
Media Object File Flt Ops Sop Seq01syed viquar
 
Media Object File Flt Ops Ops Env Seq02
Media Object File Flt Ops Ops Env Seq02Media Object File Flt Ops Ops Env Seq02
Media Object File Flt Ops Ops Env Seq02syed viquar
 
Mission Observer Ground Training
Mission Observer Ground TrainingMission Observer Ground Training
Mission Observer Ground Trainingmtphillipscap
 
Human performance
Human performance Human performance
Human performance PeteAndre2
 
Media Object File Flt Ops Cab Ops Seq01
Media Object File Flt Ops Cab Ops Seq01Media Object File Flt Ops Cab Ops Seq01
Media Object File Flt Ops Cab Ops Seq01syed viquar
 
Allan Caro Resume
Allan Caro ResumeAllan Caro Resume
Allan Caro ResumeAllan Caro
 
Airport planning part 1 -erau webinar
Airport planning part 1 -erau webinarAirport planning part 1 -erau webinar
Airport planning part 1 -erau webinarERAUWebinars
 
Airside Ops & Ntm
Airside Ops & NtmAirside Ops & Ntm
Airside Ops & NtmAiDY
 
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAM
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAMCONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAM
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAMiQHub
 
Batangas Airport.pdf
Batangas Airport.pdfBatangas Airport.pdf
Batangas Airport.pdfssuser553bbc
 
ABHIJIT UPDATED RESUME
ABHIJIT UPDATED RESUMEABHIJIT UPDATED RESUME
ABHIJIT UPDATED RESUMEABHIJIT DEY
 
Batangas Airport Philippines.pdf
Batangas Airport Philippines.pdfBatangas Airport Philippines.pdf
Batangas Airport Philippines.pdfssuser553bbc
 
Aircraft Maintenance Records and Airworthiness Directives for General Aviation
Aircraft Maintenance Records and Airworthiness Directives for General AviationAircraft Maintenance Records and Airworthiness Directives for General Aviation
Aircraft Maintenance Records and Airworthiness Directives for General AviationFAA Safety Team Central Florida
 
Airport Emergency Planning Powerpoint presentation
Airport Emergency Planning Powerpoint presentationAirport Emergency Planning Powerpoint presentation
Airport Emergency Planning Powerpoint presentationAmrishPudaruth
 

Similar to Media Object File Flt Ops Sop Seq06 (20)

Media Object File Flt Ops Fobn Seq02
Media Object File Flt Ops Fobn Seq02Media Object File Flt Ops Fobn Seq02
Media Object File Flt Ops Fobn Seq02
 
Media Object File Flt Ops Sop Seq01
Media Object File Flt Ops Sop Seq01Media Object File Flt Ops Sop Seq01
Media Object File Flt Ops Sop Seq01
 
Media Object File Flt Ops Ops Env Seq02
Media Object File Flt Ops Ops Env Seq02Media Object File Flt Ops Ops Env Seq02
Media Object File Flt Ops Ops Env Seq02
 
Mission Observer Ground Training
Mission Observer Ground TrainingMission Observer Ground Training
Mission Observer Ground Training
 
Human performance
Human performance Human performance
Human performance
 
Media Object File Flt Ops Cab Ops Seq01
Media Object File Flt Ops Cab Ops Seq01Media Object File Flt Ops Cab Ops Seq01
Media Object File Flt Ops Cab Ops Seq01
 
Allan Caro Resume
Allan Caro ResumeAllan Caro Resume
Allan Caro Resume
 
Practial Risk Management for VFR XC Flying
Practial Risk Management for VFR XC FlyingPractial Risk Management for VFR XC Flying
Practial Risk Management for VFR XC Flying
 
Airport planning part 1 -erau webinar
Airport planning part 1 -erau webinarAirport planning part 1 -erau webinar
Airport planning part 1 -erau webinar
 
Airside Ops & Ntm
Airside Ops & NtmAirside Ops & Ntm
Airside Ops & Ntm
 
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAM
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAMCONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAM
CONCEPT OF OPERATIONS: THE TRANSITION FROM CREWED TO UNCREWED UAM
 
Batangas Airport.pdf
Batangas Airport.pdfBatangas Airport.pdf
Batangas Airport.pdf
 
FAA Risk Management
FAA Risk ManagementFAA Risk Management
FAA Risk Management
 
AppendixFPM.pptx
AppendixFPM.pptxAppendixFPM.pptx
AppendixFPM.pptx
 
ABHIJIT UPDATED RESUME
ABHIJIT UPDATED RESUMEABHIJIT UPDATED RESUME
ABHIJIT UPDATED RESUME
 
DPE Runway Incursion
DPE Runway IncursionDPE Runway Incursion
DPE Runway Incursion
 
Batangas Airport Philippines.pdf
Batangas Airport Philippines.pdfBatangas Airport Philippines.pdf
Batangas Airport Philippines.pdf
 
Single-Pilot Resource Management
Single-Pilot Resource ManagementSingle-Pilot Resource Management
Single-Pilot Resource Management
 
Aircraft Maintenance Records and Airworthiness Directives for General Aviation
Aircraft Maintenance Records and Airworthiness Directives for General AviationAircraft Maintenance Records and Airworthiness Directives for General Aviation
Aircraft Maintenance Records and Airworthiness Directives for General Aviation
 
Airport Emergency Planning Powerpoint presentation
Airport Emergency Planning Powerpoint presentationAirport Emergency Planning Powerpoint presentation
Airport Emergency Planning Powerpoint presentation
 

More from syed viquar

Media Object File Maint Hum Per Seq01
Media Object File Maint Hum Per Seq01Media Object File Maint Hum Per Seq01
Media Object File Maint Hum Per Seq01syed viquar
 
Media Object File Maint Hum Per Seq02
Media Object File Maint Hum Per Seq02Media Object File Maint Hum Per Seq02
Media Object File Maint Hum Per Seq02syed viquar
 
Media Object File Flt Ops Toff Dep Seq06
Media Object File Flt Ops Toff Dep Seq06Media Object File Flt Ops Toff Dep Seq06
Media Object File Flt Ops Toff Dep Seq06syed viquar
 
Media Object File Hyperlinks
Media Object File HyperlinksMedia Object File Hyperlinks
Media Object File Hyperlinkssyed viquar
 
Media Object File Flt Ops Sop Seq02
Media Object File Flt Ops Sop Seq02Media Object File Flt Ops Sop Seq02
Media Object File Flt Ops Sop Seq02syed viquar
 
Media Object File Flt Ops Rwy Ops Seq01
Media Object File Flt Ops Rwy Ops Seq01Media Object File Flt Ops Rwy Ops Seq01
Media Object File Flt Ops Rwy Ops Seq01syed viquar
 
Media Object File Flt Ops Gnd Hand Seq01
Media Object File Flt Ops Gnd Hand Seq01Media Object File Flt Ops Gnd Hand Seq01
Media Object File Flt Ops Gnd Hand Seq01syed viquar
 
Media Object File Flt Ops Ops Env Seq07
Media Object File Flt Ops Ops Env Seq07Media Object File Flt Ops Ops Env Seq07
Media Object File Flt Ops Ops Env Seq07syed viquar
 
Media Object File Flt Ops Supp Tech Seq01
Media Object File Flt Ops Supp Tech Seq01Media Object File Flt Ops Supp Tech Seq01
Media Object File Flt Ops Supp Tech Seq01syed viquar
 
Media Object File Flt Ops Toff Dep Seq08
Media Object File Flt Ops Toff Dep Seq08Media Object File Flt Ops Toff Dep Seq08
Media Object File Flt Ops Toff Dep Seq08syed viquar
 
Media Object File Flt Ops Toff Dep Seq04
Media Object File Flt Ops Toff Dep Seq04Media Object File Flt Ops Toff Dep Seq04
Media Object File Flt Ops Toff Dep Seq04syed viquar
 
Media Object File Flt Ops Supp Tech Seq07
Media Object File Flt Ops Supp Tech Seq07Media Object File Flt Ops Supp Tech Seq07
Media Object File Flt Ops Supp Tech Seq07syed viquar
 
Media Object File Flt Ops Ops Env Seq06
Media Object File Flt Ops Ops Env Seq06Media Object File Flt Ops Ops Env Seq06
Media Object File Flt Ops Ops Env Seq06syed viquar
 
Media Object File Flt Ops Ops Env Seq05
Media Object File Flt Ops Ops Env Seq05Media Object File Flt Ops Ops Env Seq05
Media Object File Flt Ops Ops Env Seq05syed viquar
 
Media Object File Flt Ops Hum Per Seq07
Media Object File Flt Ops Hum Per Seq07Media Object File Flt Ops Hum Per Seq07
Media Object File Flt Ops Hum Per Seq07syed viquar
 
Media Object File Flt Ops Fobn Seq03
Media Object File Flt Ops Fobn Seq03Media Object File Flt Ops Fobn Seq03
Media Object File Flt Ops Fobn Seq03syed viquar
 
Media Object File Flt Ops Appr Seq03
Media Object File Flt Ops Appr Seq03Media Object File Flt Ops Appr Seq03
Media Object File Flt Ops Appr Seq03syed viquar
 
Media Object File Flt Ops Adv Wx Seq02
Media Object File Flt Ops Adv Wx Seq02Media Object File Flt Ops Adv Wx Seq02
Media Object File Flt Ops Adv Wx Seq02syed viquar
 
Media Object File Flt Ops Adv Wx Seq07
Media Object File Flt Ops Adv Wx Seq07Media Object File Flt Ops Adv Wx Seq07
Media Object File Flt Ops Adv Wx Seq07syed viquar
 
Media Object File Flt Ops Hum Per Seq03
Media Object File Flt Ops Hum Per Seq03Media Object File Flt Ops Hum Per Seq03
Media Object File Flt Ops Hum Per Seq03syed viquar
 

More from syed viquar (20)

Media Object File Maint Hum Per Seq01
Media Object File Maint Hum Per Seq01Media Object File Maint Hum Per Seq01
Media Object File Maint Hum Per Seq01
 
Media Object File Maint Hum Per Seq02
Media Object File Maint Hum Per Seq02Media Object File Maint Hum Per Seq02
Media Object File Maint Hum Per Seq02
 
Media Object File Flt Ops Toff Dep Seq06
Media Object File Flt Ops Toff Dep Seq06Media Object File Flt Ops Toff Dep Seq06
Media Object File Flt Ops Toff Dep Seq06
 
Media Object File Hyperlinks
Media Object File HyperlinksMedia Object File Hyperlinks
Media Object File Hyperlinks
 
Media Object File Flt Ops Sop Seq02
Media Object File Flt Ops Sop Seq02Media Object File Flt Ops Sop Seq02
Media Object File Flt Ops Sop Seq02
 
Media Object File Flt Ops Rwy Ops Seq01
Media Object File Flt Ops Rwy Ops Seq01Media Object File Flt Ops Rwy Ops Seq01
Media Object File Flt Ops Rwy Ops Seq01
 
Media Object File Flt Ops Gnd Hand Seq01
Media Object File Flt Ops Gnd Hand Seq01Media Object File Flt Ops Gnd Hand Seq01
Media Object File Flt Ops Gnd Hand Seq01
 
Media Object File Flt Ops Ops Env Seq07
Media Object File Flt Ops Ops Env Seq07Media Object File Flt Ops Ops Env Seq07
Media Object File Flt Ops Ops Env Seq07
 
Media Object File Flt Ops Supp Tech Seq01
Media Object File Flt Ops Supp Tech Seq01Media Object File Flt Ops Supp Tech Seq01
Media Object File Flt Ops Supp Tech Seq01
 
Media Object File Flt Ops Toff Dep Seq08
Media Object File Flt Ops Toff Dep Seq08Media Object File Flt Ops Toff Dep Seq08
Media Object File Flt Ops Toff Dep Seq08
 
Media Object File Flt Ops Toff Dep Seq04
Media Object File Flt Ops Toff Dep Seq04Media Object File Flt Ops Toff Dep Seq04
Media Object File Flt Ops Toff Dep Seq04
 
Media Object File Flt Ops Supp Tech Seq07
Media Object File Flt Ops Supp Tech Seq07Media Object File Flt Ops Supp Tech Seq07
Media Object File Flt Ops Supp Tech Seq07
 
Media Object File Flt Ops Ops Env Seq06
Media Object File Flt Ops Ops Env Seq06Media Object File Flt Ops Ops Env Seq06
Media Object File Flt Ops Ops Env Seq06
 
Media Object File Flt Ops Ops Env Seq05
Media Object File Flt Ops Ops Env Seq05Media Object File Flt Ops Ops Env Seq05
Media Object File Flt Ops Ops Env Seq05
 
Media Object File Flt Ops Hum Per Seq07
Media Object File Flt Ops Hum Per Seq07Media Object File Flt Ops Hum Per Seq07
Media Object File Flt Ops Hum Per Seq07
 
Media Object File Flt Ops Fobn Seq03
Media Object File Flt Ops Fobn Seq03Media Object File Flt Ops Fobn Seq03
Media Object File Flt Ops Fobn Seq03
 
Media Object File Flt Ops Appr Seq03
Media Object File Flt Ops Appr Seq03Media Object File Flt Ops Appr Seq03
Media Object File Flt Ops Appr Seq03
 
Media Object File Flt Ops Adv Wx Seq02
Media Object File Flt Ops Adv Wx Seq02Media Object File Flt Ops Adv Wx Seq02
Media Object File Flt Ops Adv Wx Seq02
 
Media Object File Flt Ops Adv Wx Seq07
Media Object File Flt Ops Adv Wx Seq07Media Object File Flt Ops Adv Wx Seq07
Media Object File Flt Ops Adv Wx Seq07
 
Media Object File Flt Ops Hum Per Seq03
Media Object File Flt Ops Hum Per Seq03Media Object File Flt Ops Hum Per Seq03
Media Object File Flt Ops Hum Per Seq03
 

Recently uploaded

Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationSlibray Presentation
 
Advanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionAdvanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionDilum Bandara
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr BaganFwdays
 
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DayH2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DaySri Ambati
 
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostZilliz
 
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningDSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningLars Bell
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfPrecisely
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsPixlogix Infotech
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity PlanDatabarracks
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsSergiu Bodiu
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxNavinnSomaal
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek SchlawackFwdays
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piececharlottematthew16
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLScyllaDB
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Manik S Magar
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brandgvaughan
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfAlex Barbosa Coqueiro
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubKalema Edgar
 
Scanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsScanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsRizwan Syed
 

Recently uploaded (20)

Connect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck PresentationConnect Wave/ connectwave Pitch Deck Presentation
Connect Wave/ connectwave Pitch Deck Presentation
 
Advanced Computer Architecture – An Introduction
Advanced Computer Architecture – An IntroductionAdvanced Computer Architecture – An Introduction
Advanced Computer Architecture – An Introduction
 
"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan"ML in Production",Oleksandr Bagan
"ML in Production",Oleksandr Bagan
 
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo DayH2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
H2O.ai CEO/Founder: Sri Ambati Keynote at Wells Fargo Day
 
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
 
DSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine TuningDSPy a system for AI to Write Prompts and Do Fine Tuning
DSPy a system for AI to Write Prompts and Do Fine Tuning
 
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdfHyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
Hyperautomation and AI/ML: A Strategy for Digital Transformation Success.pdf
 
The Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and ConsThe Ultimate Guide to Choosing WordPress Pros and Cons
The Ultimate Guide to Choosing WordPress Pros and Cons
 
How to write a Business Continuity Plan
How to write a Business Continuity PlanHow to write a Business Continuity Plan
How to write a Business Continuity Plan
 
DevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platformsDevEX - reference for building teams, processes, and platforms
DevEX - reference for building teams, processes, and platforms
 
SAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptxSAP Build Work Zone - Overview L2-L3.pptx
SAP Build Work Zone - Overview L2-L3.pptx
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
"Subclassing and Composition – A Pythonic Tour of Trade-Offs", Hynek Schlawack
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piece
 
Developer Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQLDeveloper Data Modeling Mistakes: From Postgres to NoSQL
Developer Data Modeling Mistakes: From Postgres to NoSQL
 
Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!Anypoint Exchange: It’s Not Just a Repo!
Anypoint Exchange: It’s Not Just a Repo!
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
 
Unraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdfUnraveling Multimodality with Large Language Models.pdf
Unraveling Multimodality with Large Language Models.pdf
 
Unleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding ClubUnleash Your Potential - Namagunga Girls Coding Club
Unleash Your Potential - Namagunga Girls Coding Club
 
Scanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsScanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL Certs
 

Media Object File Flt Ops Sop Seq06

  • 1. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings Flight Operations Briefing Notes Standard Operating Procedures Conducting Effective Briefings I Introduction To ensure mutual understanding and effective cooperation among crewmembers and with ATC, in-depth takeoff and approach / go-around briefings should be conducted on each flight. A thorough briefing should be conducted regardless of: • How familiar the departure airport / SID or destination airport / approach may be; or, • How often the crewmembers have flown together. This Flight Operations Briefing Note provides generic guidelines for conducting effective and productive briefings. Effective briefings should be short, structured, concise and adapted to the particular conditions of the takeoff or approach-and-landing. The information provided hereafter has been expanded on purpose to provide an opportunity to review and discuss in details each briefing item. II Statistical Data The quality of approach and go-around briefings is observed as a causal factor in approximately 50 % of approach-and-landing accident ( source : Flight Safety Foundation – 1998-1999 ), by affecting: • Understanding of prevailing conditions; • Horizontal or vertical situational awareness; and, • Crew coordination. Page 1 of 14
  • 2. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings III Objectives of Briefings Crew briefings ( i.e., PF to PNF briefings ) are aimed at the following objectives, in support of standard operating procedures (SOPs) : • Define and communicate action plans and expectations, under normal or non-normal conditions; • Confirm applicable task sharing (i.e., crew members’ roles and responsibilities); • Brief specific areas to the required level of details; • Promote inquiry / advocacy and feedback; • Ensure full understanding and agreement by both crew members on sequence of actions; and, • Communicate objectives to other crew members (e.g., cabin crew, as applicable). Briefings are also intended to enhance the flight crew and cabin crew preparedness for facing unusual requirements or responding to unanticipated conditions ( i.e., « expecting the unexpected » ). IV Briefing Techniques The importance of briefing techniques often is underestimated, although effective briefings contribute to enhance crew standardization and communication. The style and tone of the briefing play an important role; interactive briefings – i.e., confirming the agreement and understanding of the PNF after each phase of the briefing – provides more effective and productive briefings than an uninterrupted recitation terminated by the final query « Any question ? » . Interactive briefings better fulfill an important purpose of the briefings, that is to provide the PF and PNF with an opportunity to correct each other (e.g., confirming the use of the correct and effective departure / approach chart, confirming the correct setup of navaids for the assigned takeoff / landing runway, etc). Briefings should be structured (i.e., follow the logical sequence of the takeoff / departure or approach / landing) and concise. The routine and formal repetition of the same points on each sector may become counterproductive; adapting and expanding the briefing by highlighting the special aspects of the airport and departure / approach procedure or the prevailing weather conditions and circumstances result in more lively and effective briefings. In short, the briefing should encourage effective listening to attract the PNF’s attention. Page 2 of 14
  • 3. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings The briefing should therefore be conducted when the workload and availability of the PNF permit an effective communication. Any aspect that may affect normal operation (e.g., system failures, weather conditions or other particular conditions) should be carefully evaluated and discussed. The briefing should help both the PF (giving the briefing) and the PNF (receiving and acknowledging the briefing) understanding the sequence of events and actions, as well as the special hazards and circumstances of the takeoff, departure, approach and landing (i.e., by creating a common mental model of the takeoff or approach). Whether anticipated or not, changes in an air traffic control (ATC) clearance, weather conditions or landing runway require reviewing part of the initial briefing. V Timeliness of Briefings Briefings should be conducted during low-workload periods. The takeoff Briefing should be conducted while the aircraft is stationary (i.e., at the gate or other parking position). Rushing during descent and approach is a significant factor in approach-and-landing incidents and accidents. To prevent any rush in initiating the descent and the resulting increased workload in conducting the approach, the descent preparation and the approach and go-around briefings typically should be completed 10 minutes before reaching the top-of-descent. VI Scope of Briefings A study of team performance indicates that the quality of the pre-flight briefings ( i.e., flight crew / cabin crew briefing and flight crew takeoff briefing) shapes the quality of the crew performance throughout the entire flight. The pre-flight briefings start at the dispatch office when the Dispatcher hands over the Flight Folder / Dossier to the flight crew, for review and final decision on the route, cruise flight level and fuel quantity. The on-board takeoff briefing should include the following generic aspects of the takeoff and departure phase : • Takeoff and departure conditions (i.e., weather and runway conditions, special hazards); • Lateral and vertical navigation (i.e., intended use of automation); • Communications; • Non-normal procedures, as applicable; and, • Review and discussion of takeoff and departure hazards. Page 3 of 14
  • 4. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings The approach and go-around briefings should cover the following generic aspects of the approach and landing, including a possible missed approach and a second approach or diversion: • Approach conditions (i.e., weather and runway conditions, special hazards); • Lateral and vertical navigation (i.e., intended use of automation); • Instrument approach procedure details; • Communications; • Non-normal procedures, as applicable; and, • Review and discussion of approach-and-landing hazards. These aspects are expanded and discussed in details in this Flight Operations Briefing Note. VII Takeoff Briefing The takeoff briefing is conducted by the crewmember designated as Pilot Flying (PF) for the flight leg. The takeoff briefing enables the PF to inform the PNF of the planned course of actions (i.e., expectations, roles and responsibilities, unique requirements) for both normal and abnormal conditions during the takeoff phase. A full takeoff briefing should be conducted on the first sector of the day, subsequent briefings should be limited to the specific aspects of each individual airport / runway / takeoff / SID conditions. The takeoff briefing should be guided and illustrated by referring to the applicable FMS pages and to the ND (e.g., to visualize the departure route and confirm the various data entries, …). An expanded review of the items to be covered in the takeoff briefing – as practical and appropriate for the conditions of the flight – is provided hereafter. VII.1 ATIS : Review the last ATIS message, including : • Expected takeoff runway in use and SID: • QNH / QFE; • Transition altitude (if variable with QNH); • Weather, OAT / Dew point; • Wind and runway condition. Page 4 of 14
  • 5. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings VII.2 NOTAMs : Review and discuss takeoff and departure NOTAMs, as applicable, for possible operational impact, e.g. : • Unserviceable navaids, change of departure routing, airspace restrictions, ….; and/or, • Specific threats / hazards (e.g., work-in-progress on taxiways and/or runways, obstructions, man-made obstacles, volcanic activity, …). In case of any doubt on the contents or interpretation of a NOTAM, contact the company Dispatch office for confirmation. VII.3 Weather Briefing : Based on the weather briefing conducted by the dispatcher and on last ATIS information, discuss the effect of prevailing weather conditions on takeoff and departure procedures (e.g., use of weather radar in case of suspected windshear, requirement for a takeoff alternate, use of engine and wing anti-ice, …). VII.4 Dispatch Conditions ( MEL ) affecting Takeoff Performance : Review and discuss any dispatch condition (i.e., dispatch under MEL/DDG) that affects : • Takeoff performance (i.e., takeoff weight and/or speeds); or, • Fuel consumption. Ensure that dispatch conditions are compatible with the flight to be performed and do not combine conditions (i.e., inoperative items) that cannot be combined (i.e., exclusive dispatch conditions). VII.5 Takeoff Performance Limitations : Review and discuss prevailing takeoff performance limitation (e.g., runway, second segment, obstacle, …) as well as any specific takeoff performance limitation (i.e., minimum climb gradient during SID, non-standard turn, EOSID, …). VII.6 Weight and Balance Data - Load Sheet Review : Review weight and balance data (i.e., preliminary data from the Flight Folder / Dossier or final Load & Trim Sheet). VII.7 Runway Condition and Wind : Confirm the expected takeoff runway, the runway condition and wind component. Page 5 of 14
  • 6. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings VII.8 Takeoff Data : Confirm the computed takeoff data for the prevailing conditions, i.e. : • Slats / Flaps configuration; • V-speeds (i.e., V1, VR, V2 – F, S, Green Dot speeds or V3, V4, VFTO); • Thrust setting (i.e., TOGA or FLEX …); and, • Confirm the air bleed configuration for takeoff, i.e. : − Air-conditioning packs / engine anti-ice / wing anti-ice. VII.9 Noise Abatement Procedure (as applicable) : Review and discuss the applicable noise-abatement procedure, particularly if the noise abatement procedure is not standard and / or not programmed in the FMS. VII.10 Departure Route ( SID ) : Review and discuss the following elements, with reference to the FMS CDU, ND , FCU and chart : • First cleared altitude (if departure clearance available); • Transition altitude; • Routing (i.e., speed and/or altitude constraints, airspace restrictions, terrain / MSA); • Specific procedures in case of loss of communication (NORDO); and, • Special procedures or considerations, as applicable. VII.11 Navaids Setup – Use of Automation : Set navaids as required to fly and/or cross-check the correct tracking of the SID by the FMS, or in readiness to fly the EOSID or for an immediate return. VII.12 Rejected Takeoff Briefing : The rejected takeoff ( RTO ) part of the takeoff briefing should include the following sections : • Stop or Go Decision; • Stop Actions; and, • Go Actions. The RTO briefing is described and discussed in details in the Flight Operations Briefing Notes Revisiting the Stop or Go Decision. Page 6 of 14
  • 7. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings VII.13 Taxi to Active Runway : The taxi phase should be considered as a critical phase of flight and be carefully briefed. Using the airport chart, perform a review of the expected taxi routes with special attention to « hot spots » (i.e., intersections where the risk of confusion and the resulting risk of taxiway or runway incursion may exist). Plan the execution of checks and actions to be performed during taxi in order to prevent distraction by cockpit duties when approaching hot spots. Pay particular attention to temporary situations such as work in progress, other unusual activity and recent changes in airport layout. When taxi instructions are received from ATC, PF and PNF should refer again to the airport diagram to verbally agree on the assigned runway and taxi route, including instructions to hold short of or cross an intersecting runway. Be aware that the expectations established during the takeoff briefing can be significantly altered with a different and unexpected taxi clearance (i.e., be prepared to follow the clearance or instructions you actually received, and not the one you expected to receive). As applicable, discuss the low-visibility taxi procedures and routes (if published) and the characteristics of the airport surface movements guidance and control system (SMGCS). For more information on the prevention of taxiway and / or runway incursions, refer to the Flight Operations Briefing Note dedicated to Preventing Runway Incursions. VII.14 Deviations from SOPs : Any intended deviation from SOPs or from standard calls should be discussed during the briefing. VII.15 Briefing Confirmation during Taxi : Confirm the elements of the detailed takeoff briefing for possible changes (e.g., runway change, intersection takeoff, runway condition change, revised departure clearance, …). Confirm the takeoff data or modify the aircraft configuration (i.e., flaps, bleeds, …), the thrust setting (i.e., FLEX or TOGA) and the FMS / FCU setup, as required. Page 7 of 14
  • 8. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings VIII Cruise Briefing(s) As practical, depending on the duration of the cruise phase, it is recommended performing a structured cruise briefing – or repeated cruise briefings - covering the following aspects, as applicable, e.g. : • Strategy in case of engine failure (e.g., speed strategy depending on obstacles and ETOPS/non-ETOPS nature of flight, preferred diversion airfield depending on aircraft position, …); and, • Strategy in case of cabin depressurization (e.g., speed strategy, …). IX Approach Briefing FMS pages and ND should be used to guide and illustrate the briefing, and to confirm the various data entries. An expanded review of the items to be covered in the approach briefing – as practical and appropriate for the conditions of the flight – is provided hereafter. IX.1 Aircraft Status : Review the aircraft STATUS, as applicable (i.e., any failure or malfunction experienced during the flight) and discuss the possible consequences in terms of operation and performance (i.e., final approach speed and landing distance). IX.2 Fuel Status : Review the fuel status: • Fuel on board; • Minimum diversion fuel; and, • Available holding fuel and time. IX.3 ATIS : Review and discuss the following items: • Runway in use (type of approach); • Expected arrival route (standard terminal arrival [ STAR ] or radar vectors); • Altimeter setting (QNH or QFE, as required), − For international operations, be aware of the applicable altimeter setting unit (hectopascals or inches-of-mercury); • Transition level (unless standard transition levels are used in the country or for the airport); Page 8 of 14
  • 9. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings • Terminal weather (e.g., icing conditions, turbulence, suspected low-level windshear, ceiling and visibility / RVR, …); and, • Advisory messages (as applicable). IX.4 NOTAMs : Review and discuss enroute and terminal NOTAMs, as applicable, for possible operational impact (e.g., unserviceable navaids, airspace restriction, obstructions / man-made obstacles, …) or additional threat / hazards. In case of any doubt on the contents or interpretation of a NOTAM, contact the company Flight Watch office for confirmation. IX.5 Top-of-Descent Point : Confirm or adjust the top-of-descent ( TOD ) point, computed by the FMS, as a function of the expected arrival (i.e., following the published STAR or expecting radar vectors). Be aware of the resulting track-distance between the TOD point and the runway threshold. IX.6 Approach Chart : Review and discuss the following items using the approach chart and the FMS/ND (as applicable): • Designated runway and approach type (confirm the designated PF for the approach, in line with company policy for the type of approach to be flown); • Chart index number and date; • Minimum Safe Altitude (MSA) - reference point, sectors and minimum sector safe altitudes; • Let-down navaid(s), type, frequency and identifier (confirm the correct setup of navaids); • Radio frequencies (discuss special procedures in case of loss of communications – NORDO – as applicable); • Airport elevation; • Approach transitions (IAF, IF, other fixes, holding pattern, altitude and speed constraints/restrictions, required navaids setup); • Final approach course (and lead-in radial, as applicable); • Terrain features (location and elevation of hazardous terrain or man-made obstacles); Page 9 of 14
  • 10. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings • Approach profile view (i.e., including crossing altitudes) : − Final approach fix (FAF); − Final descent point (if different from FAF); − Outer marker (OM), as applicable; − Visual descent point (VDP), if indicated on approach profile or if computed by flight crew; − Missed-approach point (MAP); − Typical vertical speed (V/S) for the expected final approach ground speed (GS); and, − Touchdown zone elevation (TDZE). • Missed approach : − Lateral and vertical navigation; and, − Speed restrictions. Refer to paragraph X. for a detailed description of the Go Around Briefing. • Visibility/RVR minimums (and ceiling, as applicable); • Descent/decision minimums: − MDA(H) for non-precision approaches; − Barometric DA(H) for CAT I ILS approaches; or, − Radio-altimeter DH for CAT II and CAT III ILS approaches. • Local airport requirement (e.g., noise restrictions on the use of thrust reversers, etc). IX.7 Airport Chart / Diagram : Review and discuss the following items using the airport chart: • Runway length, width and slope; • Approach and runway lighting, and other expected visual references; • Specific hazards (as applicable); and, • Intended turnoff taxiway. If another airport is located in the close vicinity of the destination airport, relevant details or procedures should be discussed for awareness purposes. Page 10 of 14
  • 11. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings IX.8 Use of Automation : Discuss the intended use of automation for vertical / lateral guidance and for speed guidance, depending on FMS navigation accuracy (only for aircraft not equipped with GPS or if GPS PRIMARY LOST is displayed): • Use of FMS vertical navigation and lateral navigation or use of selected vertical modes and lateral modes; and, • Step-down approach (if a constant-angle non-precision approach – CANPA - is not available or not possible). IX.9 Use of Aircraft Systems : Discuss the use of the following aircraft systems, depending on prevailing conditions : • Nacelle / engine anti-ice; • Wing anti-ice; • Weather radar; and, • [ … ]. IX.10 Landing and Stopping : Discuss the intended landing flaps configuration (if different from full flaps). Review and discuss the following features of the intended landing runway: • Surface condition (i.e., nature and depth of contaminant, as applicable); • Intended use of autobrake (i.e., intended mode) and thrust reversers; and, • Expected runway turn-off taxiway. IX.11 Taxi to Gate : The taxi phase should be considered as a critical phase of flight and be carefully briefed. Review and discuss the following items : • Anticipated taxiways to taxi to the assigned gate (e.g., back-track on active runway or on parallel runway, with special emphasis on the possible crossing of active runways, as applicable); • Non-standard lighting and/or marking of taxiways; and/or, • Possible work in progress on runways and taxiways. As required, this review and discussion can be delayed until after landing. Page 11 of 14
  • 12. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings IX.12 CAT II / CAT III ILS briefing : For CAT II and CAT III ILS approaches, perform the specific CAT II (CAT III) briefing in accordance with company’ SOPs. IX.13 Deviations from SOPs : Any intended deviation from SOPs or from standard calls should be discussed during the briefing. X Go Around Briefing A detailed go-around briefing should be included in the descent-and-approach briefing, highlighting the key points of the go-around maneuver and missed-approach, and the task sharing under normal or abnormal / emergency conditions. The go-around briefing should recall briefly the following key aspects: • Go-around callout (i.e., a loud and clear go-around / flaps call); • PF/PNF task sharing (i.e., flow of respective actions, including use of AP, speed restrictions, go-around altitude, parameter-excessive-deviation callouts); • Intended use of automation (i.e., automatic or manual go-around, use of FMS lateral navigation or use of selected modes for missed-approach); • Missed-approach lateral navigation and vertical profile (e.g., speed limitations, airspace restrictions, highlighting obstacles and terrain features, …, as applicable); and, • Intentions (i.e., second approach or diversion) : − In case of a second approach, discuss the type of approach (i.e., if a different runway and/or type of approach is envisaged); and, − Confirm the minimum diversion fuel. It is recommended to briefly recall the main points of the go-around and missed- approach when established on the final approach course or after completing the landing checklist (as deemed practical). Page 12 of 14
  • 13. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings XI Summary of Key Points The takeoff, cruise, approach and go-around briefings should be adapted to the specific conditions of the flight and focus on the items that are relevant for the particular takeoff, departure, cruise phase (e.g., ETOPS, …), approach and landing (such as specific flight-phase-related hazards). The approach and go-around briefing should include the following ALAR-critical items: • Minimum safe altitude; • Terrain and man-made obstacles features; • Weather and runway condition; • Other approach hazards, as applicable (e.g., visual illusions); • Applicable minimums (visibility or RVR, ceiling as applicable); • Applicable stabilization height (approach gate); • Final approach flight path angle (and vertical speed); and, • Go-around altitude and missed-approach initial steps. XII Associated Briefing Notes The following Flight Operations Briefing Notes should be reviewed in association with the above information for a complete overview of the operational and human factors associated with the conduct of effective briefings : • Operating Philosophy - SOPs • Preventing Runway Incursions • Understanding the Takeoff Speeds • Revisiting the Stop or Go Decision • Being Prepared for Go-around • Effective Pilot / Controller Communications • Human Factors in Incidents and Accidents • CRM Issues in Incidents and Accidents Page 13 of 14
  • 14. Standard Operating Procedures Flight Operations Briefing Notes Conducting Effective Briefings XIII Regulatory References • ICAO – Annex 6 – Operation of Aircraft, Part I – International Commercial Air Transport – Aeroplanes, Appendix 2, 5.16. • ICAO – Procedures for Air navigation Services – Aircraft operations (PANS-OPS, Doc 8168), Volume I – Flight Procedures (Post Amendment No 11, applicable Nov.1/2001). • ICAO – Preparation of an Operations manual (Doc 9376). • FAR 121.315 – Cockpit Check Procedure, for normal and non-normal conditions. • JAR-OPS 1.1045 and associated Appendix 1, paragraphs A.8 – Operating Procedures and B.2.1 – Normal Procedures. XIV Airbus References • Airbus model of JAR-OPS-compliant Operations Policy Manual – Chapter 8 – Operating Procedures. • Airbus Flight Crew Operating Manual (FCOM) – Standard Operating Procedures (SOPs) chapter. This Flight Operations Briefing Note (FOBN) has been adapted from the corresponding ALAR Briefing Note developed by Airbus in the frame of the Approach-and-Landing Accident Reduction (ALAR) international task force led by the Flight Safety Foundation. This FOBN is part of a set of Flight Operations Briefing Notes that provide an overview of the applicable standards, flying techniques and best practices, operational and human factors, suggested company prevention strategies and personal lines-of-defense related to major threats and hazards to flight operations safety. This FOBN is intended to enhance the reader's flight safety awareness but it shall not supersede the applicable regulations and the Airbus or airline's operational documentation; should any deviation appear between this FOBN and the Airbus or airline’s AFM / (M)MEL / FCOM / QRH / FCTM, the latter shall prevail at all times. In the interest of aviation safety, this FOBN may be reproduced in whole or in part - in all media - or translated; any use of this FOBN shall not modify its contents or alter an excerpt from its original context. Any commercial use is strictly excluded. All uses shall credit Airbus and the Flight Safety Foundation. Airbus shall have no liability or responsibility for the use of this FOBN, the correctness of the duplication, adaptation or translation and for the updating and revision of any duplicated version. Airbus Customer Services Flight Operations Support and Line Assistance 1 Rond Point Maurice Bellonte - 31707 BLAGNAC CEDEX FRANCE FOBN Reference : FLT_OPS – SOP - SEQ06 - REV03 – JUNE 2004 Page 14 of 14