Appendix 2 “American 234 holding in position runway 24L,” or “American 234 holding in position runway 24L at Bravo.”
NOTE: FAA analysis of accidents and incidents involving aircraft holding in position indicate that TWO MINUTES or more elapsed between the time the instruction w as issued to “position a nd hold” and the resulting event (e.g., landover or go-around). Pilots should co nsider the length of time that they have been holding in position w henever they HAVE NOT been a dvised of any expected delay to determin e w hen it’s appropriate to que ry the controller.
13. To signal intent to aircraft downfield turn on landing lights when cleared for takeoff.
14. As part of the approach briefing, review the airport diagram and anticipated taxi route.
CAUTION A potential pitfall of pre-taxi and pre-la nding planning is setting expectations and then receiving different instructions from ATC. Flightcrew s need to follow the clearan ce or instructions that are actually received , and not the ones the flightcrew expected to receive.
Recommended Practices and Techniques
1. State your position whenever making initial contact with any tower or ground controller, regardless of whether you have previously stated your position to a different controller.
2. Write down non-standard or complex taxi instructions.
3. To signal intent to other pilots, consider turning on the taxi light when the aircraft is moving or intending to move on the ground, and turning it off when stopped, yielding, or as a consideration to other pilots or ground personnel.
4. At night, use edge lights to distinguish between taxiways (blue) and runways (white).
5. Flightcrews should minimize “heads-down” activities, such as entering data into the FMS, while the aircraft is moving. Advise the pilot taxiing whenever heads-down activity is required.
6. When visually scanning the runway and approach area, flight crewmembers should verbally confirm scan results with each other (e.g., “clear right,” “clear left”).
7. When holding in position for takeoff, actively monitor the assigned tower frequency or the Common Traffic Advisory Frequency (CTAF) for potential conflicts involving your runway.
Appendix 2
8. If unsure of position and on a runway, immediately clear the runway and notify ATC.
Always notify ATC if you are unsure of your position; consider requesting “progressive taxi.”
9. When taxi visibility is low, crews should perform heads down tasks (e.g., programming the FMS, calculating takeoff data) while the aircraft is stopped or while taxiing straight ahead on a taxiway without complex intersections.
10. To confirm proper runway or taxiway selection, verify that the compass heading approximately matches the runway heading and taxiway orientation.
11. Some cockpit displays of traffic information (such as some implementations of the Traffic Alert and Collision Avoidance System (TCAS)) have the capability and sufficient resolution to enable the display of traffic behind you. When holding in position, consider displaying traffic landing behind you to increase your awareness of the traffic situation.
12. When holding in position at night, consider lining up slightly to the left or right of centerline (approximately 3 feet) to better enable a landing aircraft to visually differentiate the holding aircraft from runway lights.
13. When on final approach, actively monitor the assigned tower frequency (or CTAF) for potential conflicts involving your runway.
14. Do not accept last minute turnoff instructions from the tower unless you clearly understand the instructions and are certain that you can comply.
Appendix 3 APPENDIX 3
Pre-Departure Briefing
There is a strong correlation between crews who use effective briefings and those who perform with fewer errors. The purpose of a pre-departure briefing is to make sure that all flight crewmembers are mentally “on the same page” and to highlight items that may be unique about the planned operation. Pay special attention to those items that are different or are potential problem areas, such as low visibility, runway incursion “hot spots,” and short taxi distance. If it is anticipated that active runways will be crossed, attention should be devoted to discussing that as well. The following list contains several items that should be covered during a pre-departure briefing.
NOTE: Those areas that are gen eric to pre-departure briefings are shaded and those topics that a re specific to airport surface operations are unshaded.
The reason that the airport opera tions information is shown integrated with a generic aircra ft is to show airport operations-specific informatio n in the context of a normal flight operation.
n Fuel o Air Traffic Control (ATC) Clearance p Expected Taxi Route q Standard Instrument Departure (SID) or Instrument Flight Rules (IFR) Departure Procedure r Any Applicable Special Considerations, such as:
Unique airport advisory information Unique noise abatement procedures Unique engine failure procedures Significant terrain or obstacles in the terminal area relative to departure routing Significant weather considerations Any other known risks and intentions
n Fuel. Discuss the fuel onboard and ensure it is adequate for the flight including delays, alternates, weather en route, etc.
o ATC Clearance. Discuss the ATC clearance and make sure that it matches the Flight Release and what is loaded into the Flight Management System (FMS).
p Expected Taxi Route. Discuss where you are (gate location) and which runway you anticipate for departure. Then discuss how you plan to get from the gate to the runway. At a minimum, brief any planned crossings of active runways, complex taxi intersections, known or anticipated runway incursion “hot spots,” airport construction that may affect taxi or takeoff, and anything out of the norm.
Appendix 3
CAUTION A potential pitfall of pre-taxi and pre-la nding planning is setting expectations and then receiving different instructions from ATC. Flightcrew s need to follow the clearan ce or instructions that are actually received , and not the ones the flightcrew expected to receive.
q SID or IFR Departure Procedure. Brief the normal takeoff, in terms of anticipated flap and thrust settings. Brief departure clearance, and verify Mode Control Panel and FMS are properly set up for normal departure.
r Any Applicable Special Considerations. Focus on those things that are non-normal for this takeoff, or any special procedures. These may include elements such as unique airport advisory information, unique noise abatement procedures, unique engine failure procedures, significant terrain or obstacles in the terminal area relative to departure routing, significant weather considerations, and any other known risks and intentions.
CAUTION After tax i clearance has been receive d, th e crew w ill agree on the runw ay assigned, any restrictions, and the taxi route. If not in agreement, seek clarification from ATC.
Example Pre-Departure Briefing:
Accomplish the pre-departure briefing once you receive the ATC clearance and your aircraft is fueled (fuel slip onboard if applicable). Ideally, the briefing should be conducted about ten minutes prior to gate departure. When discussing the taxi portion, both pilots should reference the airport diagram. Below is an example of how these items can be briefed:
n The required fuel for the flight is onboard. We don’t need a takeoff alternate but because CLT has a forecast of 800 broken and 2 miles visibility we have a destination alternate of RIC.
The weather in RIC is 2,000 broken and 5 miles.
o Our ATC clearance has been crosschecked with the Flight Release and what is in the FMS.
p We are at Gate B28 and we are planning a departure on Runway 28L at the Papa intersection. To get to that runway, we can expect to first hold short of Runway 28C, probably on taxiway Victor. With the light rain and 7 degree temperature, we will plan engine anti-ice on for taxi and takeoff.
q Let’s plan Flaps 1 and Flex thrust. Our clearance is via the Pittsburgh Five Departure, which says “climb runway heading to 1,700 ft. before turning on course. Maintain 5,000.” I see that runway heading is set on the mode control panel and so is 5,000 ft. Let’s beware that the SID requires a climb gradient of 1,133 fpm to 1,700 msl if the weather falls below 300-1. Our first fix is BURGS intersections, and that is in the FMS.
Appendix 3 r As far as special conditions are concerned, there are no unique procedures for this airport.
However, if we lose an engine, the engine-out procedure says ‘turn to heading of 200 degrees using 15 degree of bank, and climb to 3,000.’ Also, instead of using a clean-up height of 1,000 ft, if we lose an engine we will clean-up at 1,200 ft agl, which is 2,400 msl. Is there anything that you would like to discuss further, or do you have any questions?
Page 3 (and 4)
Appendix 4 APPENDIX 4
Airport Surface Operations Procedures/Departure
The following dialogue boxes illustrate airport surface operations procedures integrated into the context of a normal airport departure.
NOTE: Those areas that are related to s pecific aircraft opera tions are shaded and those that are specific to airport surface operations are unshaded.
Preflight Captain First Officer (F/O) 60 minutes prior to departure obtain Flight Release and weather package.
Report to aircraft at least 30 minutes (45 minutes for international operations) prior to scheduled departure time.
• Accomplish Crew Briefing when originating trip
• Participate in Crew Briefing
•• If electrical power is not already on, read and do “Safety & Power On Checklist.”
• Accomplish Captain’s Preflight • Accomplish First Officer’s Exterior Preflight or Exterior Intermediate Preflight
• Record current ATIS information
• Accomplish First Officer’s Preflight
Before Start Captain F/O At least 20 minutes prior to departure when fueling is complete:
• Check fuel slip for accuracy. Verify actual fuel load is within limits of GATE REL fuel and balanced.
• Check ACARS GMT for correct time. Insert flight number, departure and destination airport identifiers, flight plan time, and payroll numbers.
• Verify actual fuel load is within limits of GATE REL fuel and balanced. Enter actual FOB into ACARS.
•• Obtain ATC clearance. If done verbally, both pilots should listen to clearance.
• Verify the proper altitude and transponder code is set
• Set the proper altitude in altitude alerter
• Accomplish “Captain’s Before Start Flow (to the line)”
• Accomplish “First Officer’s Before Start Flow (to the line)” Page 1
Appendix 4
•• Review Flight Release, Weather Package, and all pertinent Jeppesen pages
•• Set communication frequencies and navigation frequencies and courses for departure
•• MCP set for departure
•• Verify ATC clearance matches FMC and Flight Release route
•• Both pilots must be thoroughly familiar with airport orientation and taxi route
•• Have airport diagram out and in view
•• PF accomplish Departure Review:
– Fuel – ATC Clearance – Expected taxi route – SID or IFR Departure Procedure – Any applicable special considerations, such as:
Unique airport advisory information Unique noise abatement procedures Unique engine failure procedures Significant terrain or obstacles in the terminal area relative to departure routing Significant weather considerations Any other known risks and intentions “Before Start Checklist” • Accomplish Before Start Checklist to the line Initiated by Captain approximately 10 minutes prior to departure:
• Accomplish Welcome Aboard announcement
Just prior to pushback – or engine start at gate – after agent provides count and verifies fuel onboard and GSI status:
• Ensure Cabin Ready Notification is received from flight attendant and relay short taxi, overwater beyond 50 nm, or other pertinent information
• Obtain pushback clearance, if required.
• Anti-Collision lights ON. LOGO lights (if installed) ON for night operations.
• Door Lights & Lock Check.
Pushback Captain F/O
•• Accomplish pushback procedures if required
Appendix 4
Engine Start Captain F/O Normal starting procedure is to start Engine 2, then Engine 1 using APU air and electrical supply.
When cleared to start engines:
“Below the line” • L & R Packs & Press – OFF/Checked
• Accomplish Before Start Checklist below the line Accomplish engine start.
After Start Captain F/O
• Give thumbs up signal when ground crew is no longer required
When ground equipment is clear and “thumbs up” has been received from the ground crew:
• Accomplish After Start Flow • Accomplish After Start Flow “After Start Checklist” • Accomplish After Start Checklist
Taxi Captain F/O
• Monitor Taxi Clearance and restate any hold short instructions
• Turn taxi light on when aircraft is moving
• Once Captain is able to monitor ATC communications, request Taxi Clearance
• Write down non-standard or complex taxi instructions
• Request confirmation if Captain does not restate any hold short instructions
• Maintain vigilance outside the aircraft
• Inform captain if out of the loop for any reason
•• Crosscheck HSI, airport diagram, and airport signage to confirm aircraft position while taxiing.
•• Approaching the entrance to an active runway, ensure compliance with hold short or crossing clearance before continuing with non-monitoring tasks. Visually scan runway and approach areas.
When clear of congested area and TOW and W & B message received:
•• Discuss TOW and W&B message.
• Enter FMC data (inform captain that you will be out of the loop) Page 3
Appendix 4
Before Takeoff Captain F/O After a runway assignment has been issued and takeoff data has been received:
• Accomplish Before Takeoff Flow to the line
• Accomplish Before Takeoff Flow to the line
•• PF accomplish Takeoff Briefing:
− Initial heading − Initial altitude − Initial fix or route segment − Summarize applicable special considerations previously briefed and any new considerations “Before Takeoff Checklist” • Accomplish Before Takeoff Checklist to the line 1-3 minutes prior to takeoff:
• Flight Attendants – Notify Cleared onto the active runway:
•• Verbally confirm ATC clearance onto active runway with other crewmembers and confirm proper runway selection using airport signs and markings and the airport diagram.
•• Visually scan runway and approach areas.
•• Check that FOB is at or above T.O. Min. Fuel Quantity and at or below BRN TO Quantity if applicable.
• Turn on wing, logo, and runway turn-off and taxi lights
“Below the line”
• Transponder – TA/RA
• Start Switches – CONT
• Complete Before Takeoff Checklist When the aircraft is at the takeoff end of the runway:
•• Confirm proper runway selection using HSI.
• If F/O is PF, transfer aircraft controls
• Ensure correct departure runway is displayed on line 5R
• Select 5R and press EXEC When cleared for takeoff:
• Turn on all remaining exterior lights Page 4
Appendix 5 APPENDIX 5
Arrival Briefing
As in the case of the pre-departure briefing, an effective arrival briefing can increase crew performance by highlighting those potential areas that need special attention and consideration.
The arrival briefing should ideally be conducted during low workload periods prior to beginning descent. This is supported by data from Line Operations Safety Audits (LOSA), which indicate that crews who conducted the arrival briefing after beginning descent committed 1.6 times more errors during descent/approach and landing, compared to those crews who briefed prior to top of descent. When the briefing is conducted during lower workload periods (such as cruise flight), greater attention can be provided to the content of the briefing.
To increase awareness of anticipated operations on the airport, attention should be devoted to discussing items that are different, or potential problem areas, such as low visibility, runway incursion “hot spots,” airport construction and short taxi distance. If it is anticipated that active runways will be crossed, attention should be devoted to discussing that, as well.
CAUTION A potential pitfall of pre-taxi and pre-la nding planning is setting expectations and then receiv ing different ins tructions from Air Traffic Control (ATC).
Flightcrews need to f ollow the clearance or instruct ions that are actually received, and not the ones the flightcrew expected to receive.
During the arrival briefing, pilots should refer to each of the charts that are applicable to the planned operation. For example, if a Standard Terminal Arrival (STAR) will be flown, refer to that chart, and crosscheck the applicable information. Likewise, refer to the applicable approach chart, as well as the airport diagram chart.
NOTE: The follow ing list con tains items that should be covered during an arrival briefing. Those areas that a re gen eric to an arrival briefing are shaded, and those topics that are speci fic to airport surface opera tions are unshaded.
n Arrival chart: Use STAR chart, if applicable, to confirm/verify the lateral routing and vertical profile, such as waypoint altitude and speed crossing restrictions if not already accomplished. Crosscheck that these values are properly set into the Flight Management System (FMS), if applicable.
o Discuss weather at destination and surrounding areas, if weather is a factor.
Appendix 5 p Approach chart: Accomplish a complete approach briefing except when not required in day Visual Meteorological Conditions (VMC). At a minimum in day VMC, discuss any special considerations and discuss and use the most precise navigation and visual approach aids available. A complete approach briefing is accomplished as follows using the approach chart and other relevant radios/instruments:
- Approach name and runway
- Approach chart date
- Primary navaid frequency
- Final approach course
- Crossing altitude at Final Approach Fix (FAF)
- Decision Altitude (height) (DA (H)), Alert Height (AH), or Minimum Descent Altitude/Missed Approach Point (MDA/MAP)
- Touchdown Zone Elevation (TDZE)
- Highest Minimum Safe Altitude (MSA)
- Missed approach
- Required visibility
- Any applicable special considerations, such as:
Compliance with stabilized approach conditions Unique airport advisory approach information Unique noise abatement procedures Unique engine failure during missed approach procedure Significant terrain or obstacles in the terminal area relative to approach routing Significant weather considerations Any other known risks and intentions
q Airport diagram chart: Refer to the airport diagram and discuss approach lighting, usable runway length, anticipated direction of turn off and airport operations. While referring to runway length, this may be a logical time to discuss planned landing flap setting and auto brake usage. If planning to land on a runway that will require crossing another runway during taxi to the terminal, make note of that. It may also be helpful to denote the planned runway exit point.
r Anything else that may be applicable to increase safety of the operations.
CAUTION A potential pitfall of pre-taxi and pre-la nding planning is setting expectations and then receiving different instructions from ATC. Flightcrew s need to follow the clearan ce or instructions that are actually received , and not the ones the flightcrew expected to receive.
Example Arrival Briefing: Accomplish the Arrival Briefing once the Arrival ATIS is received.
Ideally, the briefing should be planned so that it is conducted prior to beginning descent.
Reference each relevant chart as that information is being discussed. Below is an example of how these items can briefed: