Professional Documents
Culture Documents
REVISION:
DATE:
22.03.00
CHANGES:
Date 22.03.00
REVISION INFO
REVISION:
DATE:
16.02.00
CHANGES:
revised EFRAS-description
Item 4 new details
Date 16.02.00
B767
Workbook
PUBLISHED BY
FLEET-MANAGER B767
B767 4 PUBLICATIONS
LAUDA-AIR
Luftfahrt Aktiengesellschaft
P.O.Box 56
A-1300 Vienna Airport - Austria
Tel.: (0043-1) 7007-3158
Fax.: (0043-1) 7007-5628
SITA: VIEDONG
FIRST ISSUED:
30.08.1996
COPYRIGHT
B767
LAUDA AIR
Workbook
INTRODUCTION
The LAUDA AIR B767 WORKBOOK is designed to provide flight crews with
readily accessible information for daily operation.
PREFACE:
OF
CHAPTER 1:
PROCEDURES
CHAPTER 2:
SUPPLEMENTARY PROCEDURES
CHAPTER 3:
SUPPLEMENTARY INFORMATION
CHAPTER 4:
INFORMATION APPENDIX:
FLEET-INFO
OF THE CHAPTERS:
Each chapter is subdivided into sections, categorized by the subject or type of material
presented. Sections are identified by a three-letter-code.
Example:
B767 1 SOP , Rev.1
B767 Workbook Chapter (B767 1), Section identifier for Standard Operating
Procedures (SOP), Revision Status (Rev.1), Revision date (30.08.96),
Pagenumber.
REVISION SYSTEM :
Revision to this workbook will be issued when necessary and are numbered
consecutively. Each revision should be inserted immediately and entered in
the Record of Revision.
Alterations to former pages will be identified by a vertical line, except
when a whole chapter or section is revised.
TABLE OF CONTENTS:
The Preface Chapter consists of a complete Table of Contents, a Record of
Revision Sheets and the List of Effective Pages. For quick reference, each
section also has a detailed Table of Contents.
CAUTION:
Lauda Air makes no express or implied warranty and disclaims any liability
with respect to the design, adequacy, accuracy, reliability, safety or
conformance with government standards or regulations and approved Airplane
Flight Manual. The user of this workbook has to verify the presented data by
appropriate means and never rely solely on this workbook.
Any questions with regard to the use of this workbook and the information
contained within should be directed to the
B767 FLEETOFFICE.
Page
2,
Date 30.08.96
TABLE OF CONTENTS
B767 WORKBOOK
Title Page
Introduction
PRF
PREFACE
CHAPTER 1
INT
Table of Contents
PRF
Revision Record
PRF
PRF
( PROCEDURES )
CHAPTER 2
NNP
( SUPPLEMENTARY PROCEDURES )
TOP
Landing Performance
LDP
NAT
CHAPTER 3
CHAPTER 4
( SUPPLEMENTARY INFORMATION)
B767-Limitations
LIM
B767-Differences
DIF
B767-EFRAS
ERS
SAB
RAI
INFORMATION APPENDIX
INF APP
Introduction
FLEET-INFO
Page
2,
Date 13.12.99
REVISIO
N
NUMBER
CHAPTER
REVISION
DATE
PREFACE
10.01.2000
EFRAS
10.01.2000
INITIALS
SIGNATURE
Note:
It is the responsibility of the workbook holder to keep it up to date.
INTENTIONALLY
LEFT
BLANK
Page
4,
Date 16.11.99
Normal Procedures
Table of Contents
Chapter NP
Section 0
lntroduction ............................................................................................................NP.10.1
General...............................................................................................................NP.10.1
Deviations from Normal Procedures .......................................................NP.10.1
Normal Procedures ...........................................................................................NP.10.1
Autopilot Flight Director System and Flight
Management System Monitoring ...........................................................NP.10.2
CDU Operation...........................................................................................NP.10.3
Radio Procedure.........................................................................................NP.10.3
ATC Procedure ..........................................................................................NP.10.3
Altimeter Procedures.................................................................................NP.10.4
Decision height reference indicator setting...........................................NP.10.4
Reference altitude marker (RAM) setting ..............................................NP.10.4
EHSI MAP Mode Procedure....................................................................NP.10.5
Instrument Approach Procedures General............................................NP.10.5
Final Approach Procedures General.......................................................NP.10.6
Area of Responsibility and Panel Scan.........................................................NP.10.7
Amplified Procedures .............................................................................................NP.20.1
Preflight..............................................................................................................NP.20.1
Exterior Inspection.....................................................................................NP.20.1
Cockpit Preparation...................................................................................NP.20.1
Cockpit Preparation First Officer (electrical power
established) ................................................................................................NP.20.1
Cockpit Preparation First Officer (electrical power not
established) ................................................................................................NP.20.2
Cockpit Preparation Captain ...............................................................NP.20.11
Cockpit Preparation Final....................................................................NP.20.15
Engine Start .....................................................................................................NP.20.18
Engine Start Procedure ...........................................................................NP.20.18
NP.0.1
Normal Procedures
Table of Contents
NP.0.2
Normal Procedures
Introduction
Chapter NP
Section 10
General
This chapter contains two tabbed sections titled Normal Procedures and
Supplementary Normal Procedures. The first section incorporates routine normal
procedures and associated flight patterns. The second section incorporates normal
procedures and flight patterns that are accomplished as required rather than routinely
performed on every flight.
Normal Procedures
Normal procedures are used by the trained flight crew to ensure the airplane
condition is acceptable for flight and that the cockpit is correctly configured for each
phase of flight. These procedures assume that all systems are operating normally and
that automated features are fully utilized.
Normal procedures are performed from recall and follow a panel scan pattern. These
procedures are designed to minimize crew workload and are consistent with new
flight deck technology. All procedural information is task orienteted.
Before engine start, when possible, individual system lights and indications are used
to verify system status when the system is activated or configured for flight. After
engine start, EICAS is used as the primary indication of a non-normal system
condition or improper configuration.
If an improper indication is noted during accomplishment of procedures, first verify
the proper control position. Then, if necessary, check the appropriate circuit
breaker(s) and test the related system light(s).
Exterior lighting used during periods of darkness, cockpit lighting and personal
comfort items such as sidewall heaters are systems that are assumed to have obvious
procedural requirements and are not addressed in this section.
Flight crewmember duties have been organized in accordance with an area of
responsibility concept. Each crewmember is assigned a cockpit area where the
crewmember can initiate action for required procedures. The panel illustration
followed on next page describes the crewmember's area of responsibility and scan
flow pattern for each panel. A normal scan flow is encouraged; however, certain
items may be handled in the most logical sequence for existing conditions (e.g., air
NP.10.1
Normal Procedures
Introduction
Operations Manual
conditioning, flight plan loading, etc.). Actions outside the crewmembers area of
responsibility are initiated at the direction of the Captain.
General phaseofflight responsibilities are as follows:
Pilot flying:
flight path and airspeed control.
airplane configuration.
navigation.
Pilot not flying:
checklist reading.
communications.
tasks requested by PF.
Phase of flight duties beginning with engine starting and ending with the after
landing procedure, are presented in table form in the appropriate procedures section.
The first officer, when flying the aircraft, performs the duties listed under pilot flying
and the captain performs those duties listed under pilot not flying.
Note: Although the mode control panel is designated as the pilot flyings
responsibility, the pilot not flying should operate the controls on the mode
control panel at direction of the pilot flying when the airplane is being flown
manually.
The Captain, however, retains final authority for all actions directed and performed.
NP.10.2
No
Introduction
CDU Operation
On the ground Control Display Unit (CDU) manipulations are normally performed by
the First Officer and verified by the Captain.
In automatic flight, CDU entries are accomplished by the pilot flying and verified by
the pilot not flying prior to execution. However, during high workload periods such
as departure, approach or holding, CDU entries shall be accomplished by the pilot
not flying on command of the pilot flying.
In manual flight, CDU entries are accomplished by the pilot not flying and verfied by
the pilot flying prior execution.
CDU manipulations should be accomplished prior to high workload periods such as
departure, arrival or holding. During high workload periods, using autopilot modes
such as heading select, flight level change, and the speed intervention feature along
with the HSI MAP Switches may be more efficient than making complex CDU
changes.
Radio Procedure
The L VHF shall be used for ATC communication.
The R VHF shall be used for company communication, weather broadcast or 121.5
Mhz listening watch.
The C VHF shall be used for DATA communication.
ATC Procedure
ATC heading and/or altitude clearances must be checked by both pilots.
On the ground, the first officer reads back heading and/or altitude clearances to ATC
and sets the heading/altitude in the heading/altitude window on the MCP. The
captain calls "Heading ____" , "____" feet, FL "____ , checked".
In manual flight, the pilot not flying reads back heading and/or altitude clearances to
ATC and sets the heading/altitude in the heading/altitude window on the MCP. The
pilot flying calls "Heading____" , "____" feet, FL "____ , checked.
In automatic flight, the pilot not flying reads back heading and/or altitude clearances
to ATC. The pilot flying sets the heading/altitude in the heading/altitude window on
the MCP. The pilot not flying calls "Heading ____" , "____" feet, FL "____,
checked.
NP.10.3
Normal Procedures
Introduction
Operations Manual
Altimeter Procedures
The pressure scale reading on the Captains, standby and Copilots altimeters shall
be set to a common value as follows:
Departing aircraft shall use QNH whilst climbing until passing transition altitude,
thereafter using standard pressure.
Aircraft descending for landing change to QNH on departing transition level;
however, aircraft may relate vertical position to QNH as soon as a clearence
down to an altitude (QNH) or after an approach clearance has been received and
descent commenced, provided level flight above the Transition Altitude is not
anticipated (an anticipatory altimeter setting resulting from the procedure above
may occasionally need to be reversed to standard pressure upon an ATC
request for an unexpected level-off or for FL report prior to crossing the
transition level).
For approaches where DH is based on the use of radio altimeter, set the
decision height reference indicator to:
- applicable DH for CATII/IIIA/IIIB
- -20 feet for CATIIIB without DH.
NP.10.4
No
Introduction
Note: Intercept localizer with HDG SEL (localizer intercept in LNAVMode is not authorized).
Note: Circling is a visual maneuver where the runway, runway lights
or special visual circling aids should be kept in sight while at
MDA for circling.
The A/T ARM switch will stay in ARM throughout the approach and landing
(except S/E).
at MDA
NP.10.5
Normal Procedures
Introduction
Below 500ft :
NP.10.6
- change of configuration
- recall items
- reading of non-normal checklist
No
Introduction
NP.10.7
Normal Procedures
Introduction
Intentionally Blank
NP.10.8
Normal Procedures
Chapter NP
Amplified Procedures
Section 20
PREFLIGHT
Exterior Inspection
Prior to each flight, the captain must verify the airplane is acceptable for flight.
Check:
Flight control surfaces unobstructed and all surfaces clear of ice, snow, or
frost.
Door and access panels (not in use) properly secured.
Ports and vents unobstructed.
Airplane free of damage and fluid leakage.
Wheel chocks in place and ground locking pins removed and nose gear steering
lever in normal position.
Tire condition.
Gear struts not fully compressed.
Cockpit Preparation
The following procedures assume the crew is aware of the airplane maintenance
status.
P.20.1
Normal Procedures
Amplified Procedures
Normal Procedures
Amplified Procedures
As installed
NP.20.3
Normal Procedures
Amplified Procedures
NP.20.4
Normal Procedures
Amplified Procedures
As installed
NP.20.5
Normal Procedures
Amplified Procedures
Operations Manual
As installed
NP.20.6
Normal Procedures
Amplified Procedures
As installed
NP.20.7
Normal Procedures
Amplified Procedures
Operations Manual
TAKEOFF page1:
Enter takeoff flap setting.
TAKEOFF page2:
Check and/or enter:
acceleration height.
runway wind.
runway slope.
Flight instrument control panel ............................................... Set
ADI DH Reference marker set -20
HSI RANGE selector Select:
10 NM range as pilot flying.
NP.20.8
Normal Procedures
Amplified Procedures
As installed
NP.20.9
Normal Procedures
Amplified Procedures
Normal Procedures
Amplified Procedures
NP.20.11
Normal Procedures
Amplified Procedures
Operations Manual
TAKEOFF page1:
Verify takeoff flap setting correct.
NP.20.12
Normal Procedures
Amplified Procedures
TAKEOFF page2:
Verify:
acceleration height correct
runway wind correct
runway slope correct.
Flight instrument control panel ............................................... Set
ADI DH Reference marker set -20
HSI RANGE selector Select:
10 NM range as pilot flying.
20 NM range as pilot non flying.
HSI Mode selector - MAP
WEATHER RADAR switch - OFF
MAP switches - AS DESIRED
SPEEDBRAKE lever ....................................................... DOWN
Reverse thrust levers ...................................................... DOWN
NOTE: Movement of the reverse thrust lever could result in
operation of the engine thrust reverser.
Forward thrust levers ...................................................CLOSED
FLAP lever .......................................................................... Set
Position lever to agree with flap position.
PARK BRAKE ...................................................................... Set
Observe PARK BRAKE light illuminated.
STABILIZER TRIM CUTOUT switches ............................NORM
FUEL CONTROL switches ..........................................CUT OFF
Audio Selector Panel ............................................................. Set
Cockpit window ........................................ CLOSED & LOCKED
Verify handle in locked (forward) position and WINDOW
NOT CLOSED decal hidden from view.
Crew oxygen ...........................................................Test and set
March 18, 2000 Rev.3
NP.20.13
Normal Procedures
Amplified Procedures
Mask - Stowed
Normal/100% selector - 100%
RESET/TEST slide lever - Push and hold
Verify yellow cross appears momentarily in flow indicator.
As installed
NP.20.14
Normal Procedures
Amplified Procedures
Altimeter - Set
Set barometric indication.
Verify proper altitude and no flags.
Vertical speed indicator - Check
Verify zero rate and no flag.
Clock - Check
AUTOLAND STATUS annunciator ...... .............................. Check
Verify blank indications.
RESERVE BRAKES and STEERING switch ............................OFF
Verify VALVE light extinguished.
Standby flight instruments ..................................................... Set
Attitude indicator - Check
Verify proper attitude. Position ILS selector to OFF and verify no flags.
Airspeed indicator - Check
Verify proper speed.
Altimeter - Set
Set barometric indication. Verify proper altitude.
Standby engine indicator selector .......................................AUTO
AUTO BRAKES selector ..................................................... OFF
Seat ................................................................................ Adjust
Position seat for optimum eye reference.
Rudder pedals ................................................................... Adjust
Adjust to permit full rudder pedal and brake application.
Call for BEFORE START CHECKLIST TO THE LINE.
Note: A takeoff briefing shall be accomplished by the pilot flying after
the preflight check, so as not to interfere with the Before Start
Procedure. It shall include:
- aircraft configuration
- normal departure procedure: anticipated routing
- MCP setting and NAV setting
- rejected takeoff procedure
NP.20.15
Normal Procedures
Amplified Procedures
Operations Manual
NP.20.16
Normal Procedures
Amplified Procedures
Enter:
zero fuel weight.
C, F/O
C
F/O
NP.20.17
Normal Procedures
Amplified Procedures
Operations Manual
F/O
F/O
F/O
NP.20.18
Normal Procedures
Amplified Procedures
NP.20.19
Normal Procedures
Amplified Procedures
Operations Manual
ENGINE START
Engine Start Procedure
The term L (R) engine is used with ground personnel and in the cockpit.
The normal start sequence is right then left.
Captain
Call START _____ ENGINE.
First Officer
Position _____ START selector to GND.
Push CLOCK switch.
Reset CLOCK.
NP.20.20
Normal Procedures
Amplified Procedures
F/O
F/O
F/O
F/O
freedom of movement
controls return to center.
NP.20.21
Normal Procedures
Amplified Procedures
Operations Manual
Ground equipment.......................................................Clear
F/O
NP.20.22
Normal Procedures
Operations Manual
Amplified Procedures
First Officer
Obtain taxi clearance.
Position ELAPSED TIME selector to
RUN with start of taxi or start of
pushback whichever occurs first.
NP.20.23
Normal Procedures
Amplified Procedures
Operations Manual
Takeoff Procedure
Captain
First Officer
Monitor airspeed.
Call "V1".
Rotate at VR.
At VR call "ROTATE".
Continued
NP.20.24
Pilot flying
Verify positive rate of climb.
Call for GEAR UP.
Normal Procedures
Amplified Procedures
Maintain V2 +15 to 25
After climb stabilized, at 400 feet call for
LNAV or HEADING SELECT,
HEADING _____".
CHECKLIST.
checklist.
Note: LNAV shall be used if it is obvious that LNAV track can be followed after
takeoff.
Heading select shall be used as a preference over LNAV if:
- large heading changes have to be executed immediately after takeoff
- clearance by ATC to follow a specific heading after takeoff
- departure procedure or route does not commence at the end of runway
- initial turning points are determined by DME distance (noise abatement)
NP.20.25
Normal Procedures
Amplified Procedures
Operations Manual
Set altimeters to standard and call Verify altimeter setting and indication and
call "CHECKED".
"STANDARD", flight level "_____".
Verify altitude and call "CHECKED".
Captain
NP.20.26
Normal Procedures
Amplified Procedures
Cruise Procedure
Pilot Flying
Note: The fuel crossfeed valve check is not required on airplanes with
two fuel crossfeed valves.
Note: During cruise in case of turbulences, no smoking and seat belts
sign selectors will be operated by the captain also when acting
as pilot flying.
NP.20.27
Normal Procedures
Amplified Procedures
Operations Manual
First Officer
NP.20.28
Normal Procedures
Operations Manual
Pilot Flying
Amplified Procedures
Captain
First Officer
NP.20.29
Normal Procedures
Amplified Procedures
Operations Manual
Landing Procedure
Pilot Flying
Call for FLAPS _____ according to flap Position flap lever as directed and call
extension schedule.
"FLAPS _____ SET", when flaps have
reached the commanded position.
When on localizer intercept heading with
localizer and glideslope pointers displayed
and approach clearance received arm APP
mode.
Verify localizer capture and call
CHECKED.
GEAR DOWN
FLAPS 20.
Captain
First Officer
NP.20.30
Normal Procedures
Operations Manual
Amplified Procedures
Captain
NP.20.31
Normal Procedures
Amplified Procedures
Operations Manual
Go - Around Procedure
Pilot Flying
Push GA switch.
Call for GO-AROUND,
FLAPS 20.
NP.20.32
Normal Procedures
Operations Manual
Amplified Procedures
Call 60 KNOTS.
First Officer
Reply "YOUR CONTROLS".
NP.20.33
Normal Procedures
Amplified Procedures
Operations Manual
First Officer
Start APU.
Position TAXI light switch ON and White Anti-Collision light switch OFF.
LANDING light switches OFF.
Position ELAPSED TIME selector to
HOLD.
Position
TAXI
and
RUNWAY
TURNOFF
light
switches
OFF
approaching parking position.
NP.20.34
Normal Procedures
Amplified Procedures
F/O
F/O
F/O
F/O
F/O
F/O
F/O
NP.20.35
Normal Procedures
Amplified Procedures
Operations Manual
F/O
F/O
F/O
F/O
F/O
CDU........................................................................... Set
Set EICAS page Flight times
F/O
F/O
F/O
F/O
CDU........................................................................... Set
Set PROG page 2/2
F/O
As installed
NP.20.36
Normal Procedures
Amplified Procedures
NP.20.37
Normal Procedures
Amplified Procedures
Secure Procedure
Accomplish only when aircraft will be left unattended .
IRS selectors .............................................................. OFF
F/O
F/O
F/O
F/O
F/O
F/O
F/O
F/O
F/O
F/O
F/O
NP.20.38
Normal Procedures
Flight Patterns
Chapter NP
Section 30
Takeoff
NP.30.1
Normal Procedures
Flight Patterns
ILS Approach
NP.30.2
Missed approach
- Push GA switch (AFDS)
- Flaps 20
- Go-around attitude
- Go-around thrust
- Posetive rate of climb,
gear up
- At 400 feet select roll
mode (AFDS)
- At flap retraction
altitude, set speed bug for
desired flap setting
- Retract flaps on schedule
- After flap retraction,
set climb thrust
- Select VNAV or FLCH as
required
- Verify tracking route and
altitutde capture
- After Takeoff checklist
Normal Procedures
Flight Patterns
Non-Precision Approach
NP.30.3
Normal Procedures
Flight Patterns
Circling
NP.30.4
Missed approach
- Push GA switch (AFDS)
- Flaps 20
- Go-around attitude
- Go-around thrust
- Posetive rate of climb,
gear up
- At 400 feet select roll
mode (AFDS)
- At flap retraction
altitude, set speed bug for
desired flap setting
- Retract flaps on schedule
- After flap retraction,
set climb thrust
- Select VNAV or FLCH as
required
- Verify tracking route and
altitutde capture
- After Takeoff checklist
Normal Procedures
Flight Patterns
NP.30.5
Normal Procedures
Flight Patterns
Operations Manual
Missed approach
- Push GA switch (AFDS)
- Flaps 20
- Go-around attitude
- Go-around thrust
- Posetive rate of climb,
gear up
- At 400 feet select roll
mode (AFDS)
- At flap retraction
altitude, set speed bug for
desired flap setting
- Retract flaps on schedule
- After flap retraction,
set climb thrust
- Select VNAV or FLCH as
required
- Verify tracking route and
altitutde capture
- After Takeoff checklist
NP.30.6
Go-around
- Push GA switch (AFDS)
- Flaps 20
- Go-around attitude
- Go-around thrust
- Posetive rate of climb, gear up
- Position F/D switches ON
- At 400 feet select roll mode
(AFDS)
- At flap retraction altitude, set
speed bug for desired flap setting
- Retract flaps on schedule
- After flap retraction,
set climb thrust
- Select VNAV or FLCH as
required
- Verify tracking route and
altitutde capture
- After Takeoff checklist
Normal Procedures
Flight Patterns
NP.30.7
Normal Procedures
Standard Callouts
Chapter NP
Section 40
Standard Callouts
Both crewmembers should be aware of altitude, airplane position and situation. Avoid
casual and non-essential conversation during critical phases of flight, particularly
during taxi, takeoff, approach and landing. Unnecessary conversation reduces crew
efficiency and alertness and is prohibited when below 10,000 feet.
The pilot not flying should accomplish callouts based on instrument indications or
observations for the appropriate condition. The pilot flying should verify the
condition/location from his instruments and acknowledge. If the pilot not flying does
not make the required callout, the pilot flying should make it.
One of the basic fundamentals of the Crew Coordination Concept is that each
crewmember must be able to supplement or act as a back-up for the other crewmember.
Proper adherence to standard callouts is an essential element of a well-managed
cockpit. These callouts provide both crewmembers required information about airplane
systems and about the participation of the other crewmember. The absence of a
standard callout at the appropriate time may indicate a malfunction of an airplane
system or indication, or indicate the possibility of incapacitation of the other
crewmember.
When optional GPWS voice callouts occur during approach, the pilot flying should
acknowledge the electronic callout. If the normally expected electronic voice callout is
not heard by the flight crew, the pilot not flying should make the callout.
When the aircraft is aligned by the captain and the first officer is PF, the captain has to
decide when he will handover the controls to the first officer by the callout Your
Controls and the first officer has to confirm this by the callout My Controls.
If the first officer is PF for the approach the captain has to decide when the controls
can be taken over after landing by the callout My Controls and the first officer has to
confirm this by the callout Your Controls.
NP.40.1
Normal Procedures
Operations Manual
Standard Callouts
Callout
(PNF)
Response (PF)
80 knots
V1
Rotate
Positive rate
Checked 1)
Checked
Checked
Checked
Checked
Checked
Checked
Localizer capture
Glide slope capture
Localizer intercept
Glide slope intercept
Outer Marker / FAP
_____ (feet) 2) , _____
(QNH)
VOR / NDB / FAF
_____ (feet) 2) , _____
(QNH)
500
Flare / rollout armed 3)
Approaching minimum
DH/MAP
Minimum
Contact/Go -around 4)
60 knots
Checked
Gear up
Approach
FD/ILS
ILS raw data
Precision approach
500 feet
Landing roll
Checked
Checked
Checked 1)
Checked
After 500 feet above field elevation the pilot not flying calls out significant deviations
from programmed airspeed, descent and instrument indications.
Note:
1)
2)
3)
4)
NP.40.2
Incapacitation check
Instrument approach chart altitude has to be called out
Autoland callout only
Not required, if runway in sight and confirmed by both pilots
No
Standard Callouts
Standard Phraseology
A partial list of recommended words and phrases follows:
AFDS SETTINGS:
Arm approach
Arm localizer
FLAP SETTINGS:
Flaps one
Flaps fifteen
Flaps twenty-five
Flaps up
Flaps five
Flaps twenty
Flaps thirty
AIRSPEED SETTINGS
80 Knots
V1
Rotate
Set flaps_____speed
NP.40.3
Normal Procedures
Standard Callouts
60 Knots
NP.40.4
No
Standard Callouts
Intentionally Blank
NP.40.5
Normal Procedures
Chapter NP
Section 50
Captain
Before Boarding
Cabin
Emergency Equipment
checked and ok
Apron
Close doors
XXX Pax on board and seated
Taxi-out
Inflight
At top of descent
Position NO SMOKING
or flightlevel 050)
Parking position
NP.50.1
Normal Procedures
Operations Manual
Intentionally Blank
NP.50.2
TABLE OF CONTENTS
B767 WORKBOOK CHAPTER 1:
PROCEDURES
TABLE OF CONTENTS......................................................................................................... 1
1 INTRODUCTION ....................................................................................................................... 3
2 GENERAL COCKPIT PROCEDURES.......................................................................................... 3
3 REJECTED TAKEOFF ............................................................................................................... 4
4 MALFUNCTION HANDLING ...................................................................................................... 4
5 LOW ALTITUDE LEVEL OFF AFTER TAKEOFF......................................................................... 4
6 AUTOPILOT............................................................................................................................. 5
7 GO-AROUND............................................................................................................................ 5
ONE ENGINE GO-AROUND (WEIGHT AT OR BELOW MAXIMUM LANDING WEIGHT) .................. 5
ONE ENGINE GO-AROUND (WEIGHT ABOVE MAXIMUM LANDING WEIGHT) ............................. 5
8 HIGH ALTITUDE ENGINE FAILURE AND DRIFT DOWN PROCEDURE......................................... 6
9 RAPID DEPRESSURIZATION / EMERGENCY DESCENT ............................................................. 7
10 FLAP/SLAT ASYMMETRY/DISAGREE....................................................................................... 8
INTENTIONALY
LEFT
BLANK
Page
2,
Date 13.01.00
INTRODUCTION
LAUDA AIR has laid down the following additional procedures, in order to supplement the B767
Operations Manual and Boeing 767 Flight Crew Training Manual. With the exception of the procedures
obtained in this section, no other deviation from any procedures in the above-mentioned manuals is
recommended.
Terms:
CDR
COP
PF
PNF
All Non-Normal Checklist items and responses have to be read by the PNF.
The PF commands and verifies the required action.
When the need for a recall* action arises, both pilots identify the problem.
PF ...................................................... "Name of the checklist-recall items"
PNF .............. "Checklist item" and set action after confirmation* with the PF
When complete:
PNF ..................................................................... "Recall items complete"
* Except "Rapid Depressurization or Emergency Descent" refer to Non-normal procedures.
Example:
PNF ................................................ "left engine severe damage - confirm?"
PF ................................................."left engine severe damage - confirmed"
PF .............................................. "left engine severe damage - recall items"
PNF ..................................................................... "left thrust lever - close"
PF ............................................................................................... "close"
PNF ............................................................................................... action
PNF ........................................................... "left fuel control switch - cutoff"
PF ............................................................................................ "cut - off"
PNF ............................................................................................... action
PNF ............................................................... "left engine fire switch - pull"
PF .................................................................................................. "pull"
PNF ............................................................................................... action
PNF .............................. "left engine severe damage recall items completed"
Note:
Recall items on GND are performed by the CDR after confirmation with the COP(e.g. engine
severe damage) except passenger evacuation where both pilots have separate tasks.
Distress Message (MAYDAY,...) should be sent in a case of serious and/or imminent danger and
when requiring immediate assistance (e.g. engine failure, emergency descent,...).
767 1 NNP , Rev.2
REJECTED TAKEOFF
Malfunction handling
No recall items or malfunction identification after V1 shall be commenced before the gear is
selected up and the aircraft is established in a climb.
Thereafter items shall be handled by the PNF automatically in case of engine failure:
- APU .....................................................................................................START
- A/T arm switch......................................................................................... OFF
- bank limit selector .................................................................15 IF REQUIRED
Single engine clean up after takeoff (straight out climb):
at S/E clean up altitude
Page
4,
Date 13.01.00
AUTOPILOT
GO-AROUND
PILOT FLYING
OR
Initiate descent at initial drift down speed
(Vref30+100). Use FL-CHANGE
Call
for
appropriate
CHECKLIST for failed engine.
Read
NON-NORMAL
CHECKLIST
command of PF and secure failed engine.
Follow applicable
(NORMAL/ETOPS).
drift
NON-NORMAL
down
schedule
on
Fly optimum D/D speed, with remaining engine at MAX CONT THRUST.
Frequently check TAS (Check PROG. Page 2). If TAS reduces to 420 kts, maintain 420 kts (V-NAV
speed intervention or FL-CHANGE).
Level-off can be accomplished approx. 6,000-10,000 ft below normal level-off altitude, maintaining 420
kts TAS.
DO NOT USE THIS PROCEDURE IF OBSTACLES ARE A FACTOR
Page
6,
Date 13.01.00
After putting on oxygen masks and establishing crew communication (if possible), the Commander will
take care of the flight path, while the Copilot will do the switching according recall items without
confirmation of the Commander.
The Autopilot shall be used whenever possible.
The Commander will execute the procedure, when occupying his pilots station.
BOTH
BOTH
COP
COP
CDR
CDR takes over controls if not PF and calls out ........ MY CONTROLS
CDR
FLYING PILOT
(Commander)
(Co-pilot)
PAX oxyg.Switch..............................PUSH
ENG ANTIICE........ ..............ON if required
Transponder...............................Set 7700
Inform ATC.......... .......................Req QNH
Check......................................MEA,MORA
11000ft
14000ft
9500ft
8500ft
10 FLAP/SLAT ASYMMETRY/DISAGREE
Initially fly FLAP PLACARD SPEED MINUS 5 OR appropriate MANOEUVERING SPEED (F),
whichever is lower.
TAKEOFF (Flaps 5)
-(Problem occurs between FL5 and FL1)
V-NAV Speed Intervention or FL/CH
Set SPEED 225 or VRef 30 + 60, whichever is lower
-(Problem occurs between FL1 and FL UP)
V-NAV Speed Intervention or FL/CH
Set SPEED 245 or Vref 30 + 80, whichever is lower
Set MCT (as required)
Continue CLIMB to a safe Altitude or as advised by ATC
Call for NON-NORMAL CHECKLIST
APPROACH (typical)
INITIALLY
-(Problem occurs between FL UP and FL1)
Set SPEED 245 or V
Ref 30
Ref 30
8,
Date 13.01.00
INTENTIONALY
LEFT
BLANK
Page
10 ,
Date 13.01.00
TABLE OF CONTENTS
TABLE OF CONTENTS..................................................................................................1
INTRODUCTION ..............................................................................................................2
10
CONTINGENCY PROCEDURE...........................................................................................4
11
12
13
INTRODUCTION
DETERMINATION OF MAX
PERMISSIBLE TAKE OFF
WEIGHT
2,
CALCULATING REDUCED
THRUST TAKE OFF
1.
2.
3.
4.
slippery
or
contaminated
RWY
Page
4,
Date 16.11.1999
FLAP SETTINGS
ACCELERATION ALTITUDE
TAKE OFF
The engine failure acceleration altitude is listed
in the Jeppesen RTOW chart.
10
CONTINGENCY PROCEDURE
TAKE OFF
Coordinate with ATC.
If no contingency procedure is published, the
flight crew shall fly on runway track.
Obstacle clearance is assured within a range of
25 NM from the takeoff runway.
When a Special Procedure involves a turn, it is
assumed that no acceleration is made during
the first turn even if the level off height has been
attained. The climb must be continued until on
course at the appropriate speed.
In the procedure development, Jeppesen
considers the first turn and intends that
acceleration takes place prior following turns.
Med poor
MEDIUM
GOOD
10%
11%
25%
26%
POOR
50%
51%
0,40
0,39
0,38
0,37
0,36
0,35
0,34
0,33
0,32
0,31
0,30
0,29
0,28
0,27
0,26
0,25
0,24
0,23
0,21
0,20
40
38
36
34
32
30
28
26
25
23
21
20
19
18
17
15
12
10
7
6
REDUCE
V1kt
0
13
16
22
23
25
27
29
30
31
32
33
34
35
36
36
37
38
39
39
Instruction:
Gross weight reduction from dry field limit weight (F) or obstacle limit weight (*), whichever is lower, as found
in the AAM or Boeing AOM VOL 3.
After reduction recheck for other limiting weights (e.g.: climb- or structural limit weight)
V1 reduction: calculate V1, VR, V2 as described under "calculation of T/O speeds"
Applicable V1 reduction from dry V1.
CAUTION:
Page
6,
FOR:
FOR:
SLUSH /STANDING WATER, WET SNOWCONTAMINATION MORE THAN 25% AND EQUIVALENT TO
3mm SLUSH /STANDING WATER AND MORE
All units in mm
Consider as
Slush/Standing
water
3
4
5
6
7
8
9
10
11
12
13
WEIGHT
TONS
120
125
130
135
140
145
150
155
160
165
170
175
180
185
190
Wet snow
5-6
7-8
9-10
11-12
13-14
15-16
17-18
19-20
21-22
23-24
Dry snow
6-8
9-11
12-14
15-17
18-20
21-23
24-26
27-29
30-31
32-34
35-37
10-15
16-27
28-33
34-40
41-47
48-50
6 mm contamination V1 22kt
13 mm contamination V113kt
SeaLevel
1000ft
2000ft
Sea
Level
1000ft
2000ft
Sea
Level
1000ft
2000ft
11500
12550
13600
14500
15400
16150
16900
17750
18200
18650
19100
19450
19800
20050
20300
12425
13463
14500
15400
16300
17063
17825
18463
19100
19563
20025
20375
20725
20963
21200
13350
14375
15400
16300
17200
17975
18750
19375
20000
20475
20950
21300
21650
21875
22100
12700
13950
15200
16250
17300
18250
19200
19950
20700
21300
21900
22350
22800
23100
23400
13600
14850
16100
17163
18225
19163
20100
20850
21600
22200
22800
23263
23725
24025
24325
14500
15750
17000
18075
19150
20075
21000
21750
22500
23100
23700
24175
24650
24950
25250
15200
16900
18600
20150
21700
23500
24300
25400
26500
27400
28300
28950
29600
30100
30600
16100
17813
19525
21063
22600
24275
25200
26300
27400
28300
29200
29863
30525
31013
31500
17000
18725
20450
21975
23500
2505
26100
27200
28300
29200
30100
30775
31450
31925
32400
NOTE: If RWY available is less than 8000ft use SLUSH/STANDING WATER T/O table (AOM 23 10 17).
Check QRH for minimum V1(MCG) if V1(MCG) limited set V1 to V1(MCG)!!
Instruction:
Gross weight reduction from dry field limit weight (F) or obstacle limit weight (*), whichever is lower, as found
in the AAM or Boeing AOM VOL 3.
767 1 TOP , Rev.3
Page
8,
Date 16.11.1999
13
Various Corrections may have to be applied to a Calculation of the Maximum permissible Take off
Weight, depending on the prevailing actual conditions. A summary of all Corrections has been
prepared in order to establish a flow pattern to be followed during calculation. Note that individual
corrections are conservative and are only applicable if not already included in Jeppesen Restricted
Take Off Weight Table.
CORRECTION FOR
AIR CONDITIONING PACKS OFF
ENGINE ANTI ICE ON
WING ANTI ICE ON
FROST ON UNDERSIDE OF WINGS
WET RUNWAY (< 2mm) refer to AAM + FOM
or GB/OM
STANDING WATER, SLUSH AND SNOW
BRAKING ACTION
QNH CORRECTION
* Applies to take off with 5flap. For take off with flap 15/20 see OM 23.10.18.
** Obstacle clearance charts in the AFM account for air-conditioning packs off.
TABLE OF CONTENTS
TABLE OF CONTENTS..................................................................................................1
1 INTRODUCTION...................................................................................................................2
2 LANDING FLAPS.................................................................................................................2
2.1 FLAPS 30 ...........................................................................................................................2
2.2 FLAPS 25 ...........................................................................................................................2
2.3 FLAPS 20 ...........................................................................................................................2
3 CONDITIONS ON WHICH LANDING PERFORMANCE IS BASED............................................2
4 DETERMINATION OF MAX. PERMISSIBLE LANDING WEIGHT .............................................3
4.1 NORMAL LANDING WEIGHTS............................................................................................3
4.2 OVERWEIGHT LANDING ...................................................................................................3
5 LANDING WITH MALFUNCTIONS CONDITION (EXAMPLE)...................................................4
6 MALFUNCTION - LANDING DISTANCE REQUIRED (Advisory only) .......................................5
7 LANDING PERFORMANCE CORRECTIONS ..........................................................................6
7.1 BR COEFFICIENT AVAILABLE ...........................................................................................6
7.2 BR COEFFICIENT NOT AVAILABLE....................................................................................6
8 CORRECTION ON AVAILABLE RUNWAY LENGTH................................................................7
9 MALFUNCTION TABLE........................................................................................................7
1 INTRODUCTION
If any doubt exists regarding the maximum
permissible landing weight for a particular
runway, it shall be calculated in accordance
with the performance section of the Aircraft
Flight Manual and/or Vol. 3 Aircraft Operating
Manual.
2 LANDING FLAPS
2.1 FLAPS 30
Flaps 30 is the normal landing flap setting giving
the lowest landing speeds and least runway
requirements. Flaps 30 shall not be used for
landing weights above 160 tons due to conflict
with flap load relief and the fact that Vref30 is
higher than Vref25 above, 160 tons.
2.2 FLAP 25
Flap 25 is the alternate landing flap setting. It
shall be used when landing close to max.
landing weight in gusty conditions or high
crosswind component where a greater margin to
flap load relief speed is desired.
CAUTION: AVOID HIGH NOSE UP ATTITUDE
ON LANDING TO PREVENT TAIL-SKID STRIKE
2.3 FLAPS 20
3 CONDITIONS ON WHICH
LANDING PERFORMANCE IS
BASED
The landing performance section of the Aircraft
Flight Manual and/or Vol. 3 Aircraft Operating
Manual give maximum permissible landing
weights on DRY and WET runways. The landing
distance (i.e. actual distance from 50ft at Vref to
complete stop) will then be 60% of the available
runway length.
The diagrams are based on:
Page
2,
Date 01.06.96
4 DETERMINATION OF MAX.
PERMISSIBLE LANDING WEIGHT
5 LANDING WITH
MALFUNCTIONS:
EXAMPLE:
DESCRIPTION:
Landing weighs are limited by the requirement
that landing distance on a dry runway may not
exceed 60% of available runway length. In the
event of landing with malfunctions this regulation
does not apply. In such a case proceed as
follows:
1. Find
the
(AFM/AOM)
normal
landing
1.
1800 m
5910ft
2.
1800 m x 1,37
----------------------------------2470 m
8090ft
4.
distance
REMARK:
Page
4,
2470 m x 0,6
2010 m
= 74%< 80%
To find min. RWY length required, multiply distance found in (2) by 0.75. This distance
must be less than corrected RWY length available found in (4).
e.g. 2470 x 0.75 = 1853<2010 (0,75=0,6 divided by 0,8)
Date 01.06.96
180 T
m
ft
160 T
m
ft
145 T
m
ft
1750
5750
1645
5400
1445
4750
SLATS UP + FLAPS UP
SLATS ASSYM, FLAPS 20
SLATS EXT, FLAPS <5
SLATS EXT, FLAPS 6-19
2485
2075
2110
1970
8160
6810
6930
6470
2090
1975
1875
1730
6860
6490
6160
5680
1835
1735
1645
1520
6030
5700
5400
4990
1695
5570
1615
5300
1420
4660
2140
7030
2020
6630
1770
5810
2075
2260
2570
2570
6810
7420
8440
8440
1975
2135
2435
2435
6480
7010
7990
7990
1735
1875
2140
2140
5700
6150
7030
7030
3615 11860
2705
8880
3085 10120
BASED ON:
PER EACH
PER EACH
PER EACH
5 kts
HWC
1 kts
TWC
1000FT ABOVE MSL
-50M -170
+30M +100
+40M +140
CONTAMINATION
BA / BR COEFF
MED/
GOOD
10% **
> 11%
MED
< 25%
> 26%
MED/
POOR
< 50%
> 50%
POOR
0.40
0.39
0.38
0.37
0.36
0.35
0.34
0.33
0.32
0.31
0.30
0.29
0.28
0.27
0.26
0.25
0.24
0.23
0.21
0.20
X-WIND
33
32
30
28
26
25*
24
23
22
21
20
19
18
17
16
15
12
10
07
05
REV ON
BOTH
ENGINES
REV INOP ON
ONE OR
BOTH
ENGINES
-90
-180
-270
-360
-450
-540
-630
-720
-810
-900
-990
-1080
-1170
-1260
300
600
900
1200
1500
1800
2100
2400
2700
3000
3250
3550
3850
4150
-100
-200
-300
-400
-500
-600
-700
-800
-900
-1000
-1100
-1200
-1300
-1400
-1500
-1600
-1700
-1800
-1900
- 700
-1400
2300
4600
-1000
-2100
330
660
990
1320
1650
1970
2300
2630
2960
3300
3610
3940
4370
4600
4930
5250
5580
6000
6300
BA MEDIUM
BA POOR
*
**
Page
3300
6900
Recommended Crosswind Limit including gusts WET Runway (Not applicable if RWY is grooved)
When airport temperature is close to zero and there is standing water, slush or wet snow on the
runway, the following braking action shall be used, unless the reported coeff results in an even
greater restriction:
10% and less of RWY covered:
Correct for BA WET
11-25% of RWY covered:
Correct for BA MEDIUM
26-50% of RWY covered:
Correct for BA MEDIUM to POOR
More than 50% of RWY covered:
Correct for BA POOR
6,
Date 01.06.96
CONDITION
FLAPS 25
(when based on flap
30)
AUTO
SPEEDBRAKE INOP
ONE WHEEL BRAKE
DEACT
AVAILABLE
2400 7920
RUNWAY
MIN +15% FOR CATI, 2040 6730
II, III
m
-100
ft
330
-260
860
-250
830
2800 9180
3000 9840
3200 10490
3400 11150
2380 7800
2550 8360
2720 8920
2890 9480
9 MALFUNCTION TABLE
INTENTIONALLY
LEFT
BLANK
Page
8,
Date 01.06.96
TABLE OF CONTENTS
B767 WORKBOOK CHAPTER 2:
SUPPLEMENTARY PROCEDURES
INTENTIONALLY
LEFT
BLANK
Page
2,
Date 15.10.98
INTRODUCTION
360
350
370
360
390
390
360
360
370
370
390
410
410
390
Only RVSM approved Aircraft / Operators may FLT PLAN or be cleared between
FL330 and FL370 inclusive.
NON RVSM approved Aircraft may FLT PLAN at FL390 for either Eastbound or
Westbound H24.
2.1
FLIGHT PLANNING
During flight planning the flightcrew should pay particular attention to conditions which may affect
operation in RVSM airspace. These include, but may not be limited to:
a.)
b.)
c.)
d.)
2.2
Page
4,
Elevation in ft
Capt to F/O
Sea level
40
40
5.000
45
50
Date 15.10.98
2.3
The following equipment should be operating normally at entry into RVSM airspace:
a.)
b.)
c.)
d.)
Should any of the required equipment fail prior to the aircraft entering RVSM airspace, the pilot should
request a new clearance so as to avoid flight in this airspace.
2.4
INFLIGHT PROCEDURES
a.) Flight crews should comply with aircraft operating restrictions (if required for the specific aircraft
group) related to RVSM airworthiness approval.
b.) Emphasis should be placed on promptly setting the sub-scale on all primary and standby
altimeters to 29.92 in.Hg/ 1013.2 (hPa) when passing the transition altitude and rechecking for
proper altimeter setting when reaching the initial cleared flight level (CFL);
c.) In level cruise it is essential that the aircraft is flown at the CFL. This requires that particular care
is taken to ensure that ATC clearances are fully understood and followed. Except in contingency
or emergency situations, the aircraft should not intentionally depart from CFL without a positive
clearance from ATC;
d.) During cleared transition between levels, the aircraft should not be allowed to overshoot or
undershoot the cleared flight level by more than 150feet;
Note: It is recommended that the level off be accomplished using the altitude capture feature of the
automatic altitude- control system, if installed.
e.) An automatic altitude- control system should be operative and engaged during level cruise,
except when circumstances require disengagement. In any event, adherence to cruise altitude
should be done by reference to one of the two primary altimeters;
f.) The altitude- alerting system should be operational;
g.) At intervals of approximately one hour, cross- checks between the primary altimeters should be
made. A minimum of two should agree within 200FT. (Failure to meet this condition will require
that the altimetry system be reported as defective and notified to ATC)
h.) Normally, the altimetry system being used to control the aircraft should be selected to provide
the input to the altitude- reporting transponder transmitting information to ATC.
i.) If the pilot is advised in real time that the aircraft has been identified by a heightmonitoring
system as exhibiting TVE1 greater than 300FT and/or ASE greater than 245FT then the pilot
should follow established regional procedures to protect the safe operation of the aircraft. (This
assumes that the monitoring system will identify TVE or ASE within agreed levels of accuracy
and confidence.)
j.) If the pilot is notified by ATC of an AAD error which exceeds 300FT then the pilot should take
action to return to CFL as quickly as possible.
Page
6,
Date 15.10.98
k.)
l.)
If unable to notify ATC and obtain an ATC clearance prior to deviating from the assigned CFL, the
pilot should follow established contingency procedures and obtain ATC clearance as soon as
possible.
Total Vertical Error: Vertical geometric difference between the actual pressure altitude flown by an aircraft and
its assigned pressure altitude (flight level).
2
Altimetry System Error: The difference between the pressure altitude displayed to the flightcrew when
referenced to ISA standard ground pressure setting (29.92 in. Hg/1013.25 hPa) and free stream pressure
altitude.
3
Assigned Altitude Deviation: The difference between transponded Mode C altitude and the assigned altitude/
flight level.
2.5
POST FLIGHT
In making maintenance log book entries against malfunctions in height- keeping systems, the pilot
should provide sufficient detail to enable maintenance to effectively troubleshoot and repair the system.
The pilot should detail the actual defect and the crew action taken to try to isolate and rectify the fault.
The following information should be noted when appropriate:
a.) Primary and standby altimeter readings.
b.) Altitude selector setting.
c.) Autopilot used to control the airplane and any differences when the alternate system was
selected.
d.) Differences in altimeter readings if alternate static ports selected.
e.) Use of air data computer selector for fault diagnosis procedure.
f)
Transponder selected to provide altitude information to ATC and any difference if alternate
transponder or altitude source was manually selected.
2.6
FLIGHTCREW TRAINING
Static Source Error Correction: A correction for the difference between the pressure sensed by the static
system at the static port and the undisturbed ambient pressure.
5
Position Error Correction.
Page
8,
Date 15.10.98
Contingency procedures are complicated when specific situations are detailed. However, if the details are
examined in the context of certain basic concepts, then they are more easily understood. Reviewing
these concepts should serve to aid pilots' understanding of the specific contingency procedures.
3.1
Commanders Responsibility: Guidance for contingency procedures should not be interpreted in any way
which prejudices the final authority and responsibility of the commander for the safe operation of the
aircraft.
If the pilot is unsure of the vertical or lateral position of the aircraft or the aircraft deviates from its
assigned altitude or track for cause without prior ATC clearance, then the pilot must take action to
mitigate the potential for collision with aircraft on adjacent routes or flight levels.
In this situation, the pilot should alert adjacent aircraft by making maximum use of aircraft lighting
and broadcasting position, flight level, and intentions on 121.5 Mhz (or 131.8 as a back-up).
Unless the nature of the contingency dictates otherwise, the pilot should advise ATC as soon as
possible of a contingency situation and if possible, request an ATC clearance before deviating from the
assigned route or flight level.
If a revised ATC clearance cannot be obtained in a timely manner and action is required to avoid potential
conflict with other aircraft, then the aircraft should be flown at an altitude and/or on a track where other
aircraft are least likely to be encountered:
This can be accomplished by offsetting from routes or altitudes normally flown in the airspace.
Doc. 7030 para 5 provides recommendations on the order preference for the following pilot actions:
The pilot may offset half the lateral distance between routes or tracks.
The pilot may offset half the vertical distance between altitudes normally flown.
The pilot may also consider descending below FL285 or climbing above FL410. (The vast
majority of North Atlantic traffic has been found to operate between levels 290 and 410. Flight
above FL410 or below FL285 limits exposure to conflict with other aircraft)
When executing a contingency maneuver the pilot should:
a.) Watch for conflicting traffic.
b.) Continue to alert other aircraft using 121.5 Mhz (or 13 I .8 as a back- up) and aircraft lights.
c.) Continue to fly offset tracks or altitudes until an ATC clearance is obtained.
d.) Obtain an ATC clearance as soon as possible.
4.1
GENERAL PROCEDURES
If an aircraft is unable to continue flight in accordance with its air traffic control clearance, a revised
clearance shall, whenever possible, be obtained prior to initiating any action. This shall also apply to
aircraft which are unable to maintain an accuracy of navigation on which the safety of the separation
minima applied by air traffic control between it and adjacent aircraft depends. This shall be accomplished
using the radiotelephony distress or urgency signal as appropriate. Subsequent air traffic control action
with respect to that aircraft shall be based on the intentions of the pilot and the overall air traffic situation.
If prior clearance cannot be obtained, an air traffic control clearance shall be obtained at the earliest
possible time and, in the meantime, the pilot shall:
1.) broadcast position (including the ATS route designator or the track code, as appropriate) and
intentions on frequency 121.5 Mhz at suitable intervals until air traffic control clearance is
received;
2.) make maximum use of aircraft lights to make aircraft visible;
3.) maintain a watch for conflicting traffic; and
4.) initiate such action as necessary to ensure safety of the aircraft.
Page
10,
Date 15.10.98
Initial action
If unable to comply with the provi sions above to obtain prior air traffic control clearance, the aircraft
should leave its assigned route or track by turning 90 degrees to the right or left whenever this is
possible. The direction of the turn should, where possible, be determined by the position of the aircraft
relative to any organized route or track system (e.g., whether the aircraft is outside, at the edge of, or
within the system). Other factors which may affect the direction of the turn are the direction of any
alternate airport, terrain clearance and the levels allocated to adjacent routes or tracks.
Subsequent action:
An aircraft able to maintain its assigned flight level should:
1.)
turn to acquire and maintain in either direction a track laterally separated by 30NM from its
assigned route or track; and
2.) if above FL410, climb or descend 1000FT; or
3.) if below FL410, climb or descend 500FT; or
4.) if at FL410, climb 1000FT or descend 500FT.
An aircraft not able to maintain its assigned flight level should:
1.) initially minimize its descent rate to the extent that it is operationally feasible;
2.) turn while descending to acquire and maintain in either direction a track laterally separated
by 30NM from its assigned route or track; and
3.) for the subsequent level flight, a level should be selected which differs from those normally
used by 1000FT if above FL410 or by 500FT if below FL410.
En route diversion across the prevailing NAT air traffic flow
The guidance in this para applies to aircraft that:
1.) are operating within the OTS or on random routes that are proximate to the OTS; and
2.) can climb or descend to an altitude above or below those where the majority of NAT aircraft
operate.
The basic concept of this guidance is that, when operationally feasible, before diverting across tracks or
routes with heavy traffic, the aircraft should offset from the assigned track or route by 3ONM and
expedite a descent to an altitude below or a climb to an altitude above those where the vast majority of
NAT aircraft operate before proceeding toward the alternate aerodrome. Flight below FL285 or above
FL410 should meet this objective.
In the event of a contingency which necessitates an en route diversion to an alternate aerodrome, across
the direction of the prevailing NAT traffic flow, and prior ATC clearance cannot be obtained:
An aircraft able to maintain its assigned flight level should:
1.)
2.)
3.)
4.)
5.)
6.)
7.)
turn toward the alternate aerodrome to acquire a track which is separated laterally by 3ONM
from the assigned route or track; and
if above FL410, climb or descend 1000FT; or
if below FL410, climb or descend 500FT; or
if at FL410, climb 1000FT or descend 500FT; and
fly the offset track while expediting its descent to an altitude below FL285 or a climb to an
altitude above FL410; and
when below FL285 or above FL410, proceed towards the alternate aerodrome while maintaining
a level which differs from those normally used by 500FT if below FL410 or 1000FT if above
FL410; or
if unable or unwilling to make a major climb or descend, fly an altitude offset for the diversion
until obtaining an ATC clearance.
11
CONTINGENCY SCENARIOS
5.1
SCENARIO 1
The pilot is unsure of the vertical position of the aircraft due to loss or degradation of all
primary altimetry systems or is unsure of the capability to maintain CFL due to turbulence or
loss of all automatic altitude control systems.
Pilot Action
The pilot should maintain CFL while evaluating the situation and:
a.) Watch for conflicting traffic
b.) If considered necessary, alert nearby aircraft by:
Making maximum use of exterior lights;
Broadcasting position, flight level, and immediate intentions on 121.5 MHZ
(or 131.8 as a back-up);
c.) Notify ATC of the situation and the intended course of action.
Possible courses of action include:
Continuing in MNPS airspace provided that the aircraft can maintain CFL.
Requesting ATC clearance to climb above or descend below RVSM airspace if the aircraft cannot
maintain CFL and ATC cannot establish adequate separation from other aircraft. Executing contingency.
maneuver to leave the assigned track if prior ATC clearance cannot be obtained and the aircraft cannot
maintain CFL.
Page
12,
Date 15.10.98
5.2
SCENARIO 2
Failure or loss of accuracy of one primary altimetry system (e.g., 200 feet or more difference
between primary altimeters).
Pilot Action
cross check standby altimeter, confirm the accuracy of a primary altimeter system and notify ATC of the
loss of redundancy. If unable to confirm primary altimeter system accuracy, follow pilot actions listed in
the preceding scenario.
5.3
SCENARIO 3
All automatic altitude control systems fail (e.g., automatic altitude hold)
Pilot Action
Initial:
1.) Maintain CFL
2.) Evaluate the aircraft's capability to maintain altitude through manual control.
Subsequent:
1.) Watch for conflicting traffic;
2.) If considered necessary, alert nearby aircraft by max. use of exterior lights and broadcasting of
position, flight level and immediate intentions on 121.5 Mhz (131.8)
3.) Notify ATC of the failure and the intended course of action.
Possible courses of action include:
Continuing in MNPS airspace provided that the aircraft can maintain CFL.
Requesting ATC clearance to climb above or descend below RVSM airspace if the aircraft cannot
maintain CFL and ATC cannot establish adequate separation from other aircraft. Executing contingency
maneuver to leave the assigned track if prior ATC clearance cannot be obtained and the aircraft cannot
maintain CFL.
5.4
SCENARIO 4
5.5
SCENARIO 5
13
Page
14,
Date 15.10.98
2.)
If unable to obtain ATC clearance, in a timely manner, execute Doc. 7030 contingency
procedures to leave the assigned route or track and descend below RVSM airspace (if
operationally feasible).
If it is not operationally feasible continue to alert nearby aircraft and coordinate with ATC.
5.6
SCENARIO 6
5.7
SCENARIO 7
Aircraft encounters turbulence (greater than moderate) which the pilot believes will impact the
aircraft's capability to maintain flight level.
Pilot Action
1.) Watch for conflicting traffic and make maximum use of exterior lights.
2.) Broadcast call sign, position, flight level, nature and severity of turbulence, and intentions on
121.5 MHz ( 131.8 MHz may be used as a back- up).
3.) Notify ATC as soon as possible and request flight level change if necessary.
4.) If the aircraft cannot maintain level, execute Doc. 7030 contingency procedures to leave the
assigned route or track.
5.8
The specific actions that ATC will take in the event of transponder failure in RVSM transition areas will be
determined by the provider States.
(Transition areas are planned to be established between airspaces where different vertical separation
standards are applied).
15
6.1
INTRODUCTION
Very few RAs are expected to occur in NAT airspace during normal operations after
RVSM is introduced. A TA will, however, occur each time an aircraft passes in close proximity to
another at an adjacent flight level (FL). (See page 4, RVSM Airspace Operations). It is important,
therefore, that pilots understand the affect of RVSM on TCAS operation.
TCAS software modification, Change 7, will contain changes that enhance TCAS compatibility with
RVSM operations.
6.2
SCOPE
This paper presents a set of proposed training standards for pilots operating TCAS II in an RVSM
airspace above FL 290. These standards cover four major topics: TCAS operating characteristics and
parameters applicable to RVSM airspace; the interaction between TCAS and the reduced separation
standards; operating recommendations; and the requirements for reporting TCAS events in this
environment, along with a review of the available means of reporting.
6.3
The pilot must demonstrate an understanding of basic TCAS operations and the criteria used for issuing
TAs and RAs above FL 290. This section of the training should address the following topics.
6.4
Objective:
Criteria:
Information:
a. TCAS will issue a TA or an RA only when another aircraft is "close" in both range and
altitude. Figure 1 shows these criteria and the RA threshold values used by TCAS above FL 290.
b. TAs and RAs can be issued based on either the time to closest point of approach (CPA) or a
fixed distance. In most airspace, most TAs and RAs will be issued based on time; however when
RVSM is introduced in the NAT, some advisories will be caused by the fixed range and altitude
thresholds.
Page
16,
Date 15.10.98
1. BOTH AIRCRAFT LEVEL: ALERT BASED ON TIME TO CPA AND VERTICAL DISTANCE
BETWEEN AIRCRAFT.
TA may be issued when the two aircraft are within 48 seconds of CPA horizontally and within 1200 feet
vertically. An RA may be issued when the two aircraft are within 35 seconds of CPA horizontally and
within 800 feet vertically. If the vertical separation between the two aircraft is less than 700 feet, a
corrective RA requiring a change in altitude will be issued. These thresholds are used when the two
aircraft are converging horizontally with closure rates above 100 knots and with both aircraft level. OR,
2. ONE OR BOTH AIRCRAFT WITH VERTICAL RATE: ALERT BASED ON TIME TO
VERTICAL AND HORIZONTAL CONFLICT.
A TA may be issued when the two aircraft are within 48 seconds of CPA horizontally and within 48
seconds of being at the same altitude. An RA may be issued when the two aircraft are within 35
seconds of CPA horizontally and within 35 seconds of being at the same altitude. If the TCAS aircraft is
level and another aircraft is climbing or descending, the RA will be delayed until the two aircraft are within
30 seconds of being at the same altitude to provide additional time for TCAS to detect a level off by the
other aircraft. If the vertical separation between the two aircraft at CPA is estimated to be less than 700
feet, a corrective RA requiring a change in vertical speed will be issued. If the vertical separation
between the two aircraft at CPA is estimated to be between 700 and 800 feet, a preventive RA will be
issued. These thresholds are used when the two aircraft are converging horizontally with closure rates
above 100 knots and when one or both aircraft have a vertical rate. OR,
3. BOTH AIRCRAFT LEVEL: ALERT BASED ON HORIZONTAL AND VERTICAL DISTANCE.
A TA may be issued when the two aircraft are within 1.3 nm of each other horizontally and within 1200
feet vertically. An RA may be issued when the two aircraft are within 1.1 miles of each other horizontally
and within 800 feet vertically. If the vertical separation between the two aircraft is less than 700 feet, a
corrective RA requiring a change in altitude will be issued. These thresholds are used when the two
aircraft are converging horizontally with slow closure rates (less than 100 knots) and with both aircraft
level. This is typical of an overtaking situation in which an aircraft on the same track at an adjacent
altitude passes another aircraft. OR,
4. ONE OR BOTH AIRCRAFT WITH VERTICAL RATE: ALERT BASED ON HORIZONTAL
DISTANCE AND TIME TO VERTICAL CONFLICT.
A TA may be issued when the two aircraft are within 1.3 nm of each other horizontally and within 48
seconds of being at the same altitude. An RA may be issued when the two aircraft are within 1.1 nm of
each other horizontally and within 35 seconds of being at the same altitude. If the vertical separation
between the two aircraft at CPA is estimated to be less than 700 feet, a corrective RA requiring a change
in vertical speed will be issued. If the vertical separation between the two aircraft at CPA is estimated to
be between 700 and 800 feet, a preventive RA will be issued. These thresholds are used when the two
aircraft are converging horizontally with slow closure rates (less than 100 knots) and when one or both
aircraft have a vertical rate. This is typical of an overtaking situation in which aircraft are on the same
track and maneuvering vertically towards each other to establish the reduced separation.
5. POTENTIAL FOR EXTENDED RA DISPLAY.
With the current version of TCAS, it is possible for an RA to remain displayed for an extended period of
time (two to five minutes) without being modified, if the RA is issued after the two aircraft have started to
diverge in a slow overtake encounter. The original RA will remain displayed even though adequate
vertical separation has been obtained during the initial response to the RA.
c. In the transition areas, it is most likely that TAs and RAs will be issued as aircraft are
changing altitudes to obtain the 1000 feet of vertical separation. In the NAT, a majority of advisories will
be issued when a faster aircraft on the same track passes another aircraft with 1000 feet of vertical
separation. Very few RAs are expected to occur in the NAT, but a TA can be expected every time
an aircraft passes another at the next level.
17
6.5
Because the TCAS thresholds for issuing TAs and RAs were designed for an environment with 2,000 feet
of vertical separation above FL 290, after RVSM is implemented, TCAS will issue TAs and RAs when
aircraft are operating in accordance with required separation standards. This section of the training will
highlight the types of TAs and RAs that can be expected in both an RVSM airspace and in the Transition
Areas at the entry and exit points of the RVSM airspace.
6.6
TAs
Objective:
Demonstrate knowledge about the frequency of TAs and the types of TAs that can be
expected.
Criteria: The pilot must be able to demonstrate a knowledge of the types of maneuvers and encounter
geometries that will result in TAs being issued while operating in the RVSM airspace. These include:
Information:
a. A TA will be issued whenever an aircraft operating 1,000 feet above or below the own aircraft
passes the aircraft, or is passed by the own aircraft. The TA may be displayed for as long as five
minutes, depending on the closure rate. (In this situation, if a second intruder aircraft passes own
aircraft within TA parameters, a second TA with associated aural alert will be issued). If the closure rate
is less than a 100 knots, the TA will not be issued until the aircraft are approximately 1.3 nm apart. On
most traffic displays, if the selected display range is greater than 10 nm, the intruder's aircraft symbol
will be touching the own aircraft symbol when the TA is issued.
b. When the closure rate between two aircraft is extremely slow (ground speeds within 20
knots), multiple TAs may be issued against the same intruder just prior to the TA being removed.
c. It is also possible to have multiple TAs issued against the same intruder during a crossing as
the winds at the adjacent altitude change and alter the ground speed of the two aircraft.
d. If an aircraft changes altitude while in the RVSM airspace using a vertical speed greater than
approximately 1500 fpm while in close horizontal proximity (less than two nm) to an aircraft that is level,
it is possible for TCAS to issue a TA.
Page
18,
Date 15.10.98
(B) RAs
Objective:
Demonstrate knowledge about the types of RAs that can be expected and the typical
deviation required to resolve the RA.
Criteria: The pilot must be able to demonstrate a knowledge of the types of maneuvers and encounter
geometries that will result in RAs being issued while operating in the RVSM airspace. These include:
Information:
a. POTENTIAL FOR EXTENDED RA DISPLAY: AIRCRAFT WITHIN TWO NM
HORIZONTALLY, ONE AIRCRAFT WITH VERTICAL RATE OF APPROXIMATELY
*1500 FPM AND APPROACHING ADJACENT FLIGHT LEVEL.
If an aircraft changes altitude while in the RVSM airspace using a vertical speed greater than
approximately 1500 fpm while in close horizontal proximity (within two nm) to another aircraft, it is
possible for TCAS to issue an RA as the climbing or descending aircraft approaches its altitude. For the
climbing or descending aircraft, the RA is likely to be an RA commanding a reduction in the climb or
descent rate. For the level aircraft, the RA is likely to be a Climb or Descend RA. In a typical
encounter, the Climb or Descend RA will be displayed until the level aircraft has climbed between 500
and 700 feet. If the climbing or descending aircraft is also TCAS equipped, the required displacement of
the level aircraft will be less.
*NOTE: OPERATING RECOMMENDATIONS. SEE PAGE 8. In airspace where RVSM is applied
(including Transition Areas), limiting climb and descent rates to 1000 fpm when operating in close
proximity to other aircraft will mitigate the potential for RVSM to affect TCAS operation.
b. In the situation described in paragraph a above, if the maneuvering aircraft is diverging in
range at a slow rate with the own aircraft, the Climb or Descend RA may remain displayed for several
minutes, even though the maneuvering aircraft has leveled off. WHILE THIS IS EXPECTED TO BE
RARE, such an event can cause very large displacements from the assigned altitude while complying
with the RA. If a Climb or Descend RA remains displayed for an extended period of time, it may be
indicative of a slow closure rate encounter and pilots should use all available data (TCAS traffic display,
visual cues, knowledge of other aircrafts clearance, etc.) to determine if the vertical separation between
the two aircraft is still converging. It is likely that a long duration Climb or Descend RA (displayed for
more than 30 seconds) is in response to this type of encounter which the current version of TCAS has
difficulty resolving.
However, pilots must also be aware that a long duration RA may also occur when an intruder aircraft
chases the TCAS aircraft, i.e., the intruder continues to climb after the TCAS aircraft responds to a
Climb RA. In a situation where a second intruder aircraft passes own aircraft within RA parameters, a
second RA with associated alerts will be issued.
c. AFFECT OF TURBULENCE WITH AIRCRAFT WITHIN 1.1 NM OF EACH OTHER.
Moderate and severe turbulence can induce aircraft motion which TCAS can interpret as a climb or
descent. These vertical speed changes can result in TCAS projecting the vertical separation to be less
than 800 feet at CPA, which can result in an RA being issued if the aircraft is in close proximity
(1.1 nm) of another aircraft at an adjacent altitude.
d. AFFECT OF CERTAIN SOFT ALTITUDE HOLD SYSTEMS WITH AIRCRAFT WITHIN 1.1 NM
OF EACH OTHER.
FAA RVSM approval criteria requires that soft altitude hold systems contain altitude variations within 130
feet. Prior to the introduction of this requirement, aircraft equipped with CERTAIN soft altitude hold
systems have caused numerous RA reports from operators. The soft altitude hold mode permits
oscillation about the selected altitude and can result in either the actual or projected vertical separation
between the TCAS aircraft and an intruder being reduced to less than 800 feet. If the intruder aircraft is
B767 2 NAT , Rev. 3
19
6.7
TAs
Objective:
Demonstrate knowledge about the types of TAs that can be expected.
Criteria: The pilot must be able to demonstrate a knowledge of the types of maneuvers and encounter
geometries that will result in TAs being issued while operating in the Transition Areas. These include:
Information:
a. If an aircraft changes altitude while in the transition area using a vertical speed greater than
approximately 1500 fpm while in close horizontal proximity to another aircraft that is level, it is possible
for TCAS to issue a TA.
b. If two aircraft are maneuvering vertically to attain 1,000 feet of vertical separation for entry into
the RVSM airspace, and are in close horizontal proximity to each other in either distance (1.3 nm) or
time (48 seconds), it is possible for TCAS to issue TAs to both aircraft if the combined vertical speed of
the two aircraft is greater than 1500 fpm.
c. Once two aircraft attain 1,000 feet of vertical separation in the transition area, the same types
of TAs outlined on page 4 (RVSM Airspace Operations: TAs) may occur.
d. In the transition area at the RVSM airspace exit point, very few TAs are expected because
aircraft should be diverging from each other vertically.
(B)
Objective:
RAs
Criteria: The pilot must be able to demonstrate a knowledge of the types of maneuvers and encounter
geometries that will result in RAs being issued while operating in the Transition Areas. These include:
Information:
a. POTENTIAL FOR RA DISPLAY: AIRCRAFT WITHIN TWO NM HORIZONTALLY, ONE
AIRCRAFT WITH VERTICAL RATE OF APPROXIMATELY 1500 FPM AND APPROACHING ADJACENT
FLIGHT LEVEL.
If an aircraft changes altitude while in the Transition Area using a vertical speed greater than
Page
20,
Date 15.10.98
21
6.8
Objective:
Demonstrate knowledge that the types of TAs and RAs described above exist with the
existing implementation of TCAS. The next TCAS software modification, Change 7, will contain changes
to make TCAS more compatible with reduced vertical separation above FL 290.
Information:
a. The TCAS design criteria is based on the 2,000 foot vertical separation standard
currently applied above FL 290. Some TAs and RAs will occur after RVSM implementation due to
current TCAS design criteria not considering RVSM above FL 290. TCAS software modification,
Change 7, which is expected to enter service in early 1998, will address known issues and
incompatibilities for TCAS operations in the RVSM airspace. The major areas for these
modifications are:
Page
22,
Date 15.10.98
6.9
a.
TCAS should be operated in the TA/RA mode during all operations in the RVSM
airspace and Transition Areas.
b.
Climb and descent rates in the RVSM airspace and Transition Areas should be limited
to 1000 fpm when operating within five (5) nm and 2000 feet of other aircraft to minimize the generation
of TAs and RAs.
23
B767 Limitations
TABLE OF CONTENTS
B767 LIMITATIONS
OPERATIONAL .............................................................................................................2
FLIGHTCONTROL.........................................................................................................2
FUEL ............................................................................................................................3
NAVIGATION ................................................................................................................3
APU..............................................................................................................................3
GROSS WEIGHT...........................................................................................................4
10
POWERPLANT .............................................................................................................4
11
B767 Limitations
OPERATIONAL
AFM
AFM
LAL
PERF
APP
AOM
AFM
Turbulent airspeed:
gear speed:extend:
AOM
AFM
AOM
15kts
225 mph
FLIGHTCONTROLS
AFM
Flap extension,max:
AOM
AFM
AOM
225kts
205kts
175kts
165kts
Fl 25
FUEL
AFM
Page
OE-LAT,- W, 250kts
AFM
20000ft
2,
Date 01.11.99
B767 Limitations
Max temp: 49C(JP4/JETB:43C)
Min temp: 3C above fuel freeze point
(JET A1:-47C,JETA -37C)
Min temp for takeoff: -40C
Max. fuel imbalace: 900 + 200kg
Max fuel load:
main
19548 kg
center
38646 kg
total
77742 kg(0,85)
71760 kg(0,78)
Refuelling pressure:
max :
55PSI
recommended:
35PSI
FIRE PROTECTION
AFM
To ensure cargo fire protection flight must be within 3 hours of suitable airport
whenever cargo is carried
AUTOMATIC FLIGHT
AFM
FOM
AFM
FOM
AFM
CAT II/III
NAVIGATION
AFM
VOR approaches :
AOM
Do not operate under IFR or at night into airports north of 73North or south of
60South latitude whose navigation aids are referenced to magnetic north.
One pilot must have raw data from the VOR associated
with the approach displayed in the HSI VOR mode no
later than the final approach fix.
APU
AOM
AFM
APU bleed air for cabin pressurization up to ~20000ftEXT power: min 90 KVA
B767 Limitations
GROSS WEIGHT[kg]
OE-LAT
Max Taxi wt :
185518
Max takeoff wt:
184612
Max landing wt:
145149
Max zero fuel wt:
130634
Min inflight wt( without fuel) : 81193
AFM
10
OE-LAU
177808
177354
136077
126098
POWERPLANT
AFM
Ignition:
11
Starter operation:
1) Normal duty cycle:
2 consecutive aborted starts with
EGT cooling periods.
After second consecutive cooling period let N2 decrease to zero
before reengagement
AOM
Page
4,
Date 01.11.99
B767 Differences
TABLE OF CONTENTS
B767 DIFFERENCES
TABLE OF CONTENTS......................................................................1
1
BRAKES .......................................................................................3
EICAS COMPUTER........................................................................3
10
FMC ..............................................................................................4
B767 Differences
31.10.1999
OE-LAT
OE-LAU
OE-LAW
OE-LAX
OE-LAY
OE-LAZ
MTM
MTOM
MLM
MZFM
185518
184612
145149
130634
177808
177354
136077
126098
187333
186880
145149
130634
187333
186880
145149
130634
187333
186880
145149
130634
187333
186880
145149
130634
Engine
PW 4060
PW 4056
PW 4060
PW 4060
PW 4060
PW 4060
10 minutes
10 minutes*
10 minutes
10 minutes
10 minutes
10 minutes
Seating Config.
C24/Y234
C24/234
C24/Y220
C24/220
C36/209
C36/209
ETOPS Time
AOC ITALY
160
AOC AUST
180
AOC ITALY
160
AOC AUST
180
AOC ITALY
160
AOC AUST
180
180 minutes
180 minutes
180 minutes
FMC
PIP
PIP
PIP
PIP
PEGASUS
PEGASUS
Near Door
1L
Closet in
mid area
Closet in
mid area
New C Brakes
E GPWS
Predictive WS
MMR / GPS
Rain Rep. Sys
* OE-LAU is certified for 10 minutes T/O-thrust, but currently operated for 5 minutes T/O-thrust only. Also
there are no AAM-tables for 10 minutes T/O-thrust available.
Page
2,
Date 16.11.99
B767 Differences
ALT will engage when the set altitude is reached. VNAV ALT is an altitude
hold sub-mode of VNAV. Resetting the MCP altitude and pushing the
Altitude Selector will re-engage VNAV. During descent the MCP may be set
to an altitude above the airplane without VNAV disengaging or stopping the
descent.
AOM 19.40.10
BRAKES
Brakes:
LAZ
New Allied Signal carbon brakes are installed on OE-LAZ. There are no changes in takeoff
performance, but there are some penalties in landing field length (250 to 350 ft). For more
detailed information refer to B767 OPS NOTICE 15/99.
CVR SWITCH
CVR Switch:
LAY, LAZ
AOM 09.20.02
CVR records continuously from ENG start until 5 minutes after the last ENG shut
down.
With Voice Recorder Switch installed, placing it in the ON position, will allow preflight
recordings to be made prior to ENG start. If the switch is in ON position, it will trip
to
AUTO after ENG start. It is Lauda-air procedure to leave the switch in AUTO
position.
EICAS COMPUTER
EICAS Computer:
LAY, LAZ
A new ASP has been installed with two additional Microphone Select
Switches
and two additional Receiver Controls for Satcom operation. Also a CALL
light
has been added to each Microphone Switch to indicate Selcal, Ground
call and FLT Interphone calls, in conjunction with the Communication
Crew Alerting System.
New EICAS computers have been installed, which provide a couple of new
Advisories and Cautions, including new Communication Alerts
B767 Differences
8
ENHANCED GPWS
Enhanced GPWS: LOOK AHEAD TERRAIN ALERTING: EGWPS use the radio altitude
LAZ
AOM 14.10.04B
AOM 14.20.04B
AOM 22.50.01
FIXED ELT
Fixed ELT:
LAY, LAZ
ELT PANEL with a guarded three position switch (reset, armed an on) and an ELT
ON light has been added to the overhead panel.
10
FMC
FMC:
LAY, LAZ
AOM 19.51.01
Page
4,
The Pegasus FMC incorporates a GPS, various new features, a revised CDU, and
FANS
(Future Air Navigation System). For differences between PIP FMC (product
improvement
package) and PEGASUS FMC refer to 757/767 Flight Crew Differences Training PIP
FMC to PEGASUS FMC manual and to AOM chapter 19.51.01.
Date 16.11.99
B767 Differences
B767 EFRAS
TABLE OF CONTENTS
B767 WORKBOOK CHAPTER 3:
SUPPLEMENTARY INFORMATION
B767 EFRAS
TABLE OF CONTENTS .................................................................................................................... 1
1
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
1.11
2
2.1
2.2
2.3
2.4
3
3.1
3.2
3.3
3.4
4
4.1
4.2
B767 EFRAS
1
GENERAL
2,
Date 07.02.2000
B767 EFRAS
- Items which are in general possible but not allowed for the respective conditions are
shown in gray colour on the different input fields (e.g. Eng Anti-Ice ON and Wing+Eng AI
ON in the ANTI-ICE input field for OAT < 11C)
- Press F10 to start the calculation.
- Exit the program with F11.
- 2 BASF is shown as BRAKES
- Settings which are different from the default/standard settings (e.g. Flaps 20 or AC
OFF) are shown in red colour or with red background.
- The message Airport not authorized (or A/P N/A) will be overruled by an entry in
Airport List or an Einzelflugfreigabe.
- Update stations are available in dispatch
1.2
LINEUP DISTANCE:
Lineup corrections are made when computing takeoff performance any time the access
to the runway does not permit positioning of the airplane at the threshold.
The EFRAS-program considers different possibilities for lineup, especially 90 degree
taxiway entry and 180 degree turnaround. Therefore appropriate minimum lineup
distance adjustments required by JAR-OPS1 and provided by Boeing (see table below)
are used. The data distinguish between the takeoff distance(TODA) and the acceleratestop distance (ASDA) and provide different lineup values for these cases. The takeoff
distance adjustment is based on the initial distance from the main gear to the beginning
of the runway since the screen height is measured from the main gear. The acceleratestop distance adjustment is based on the initial distance from the nose gear to the
beginning of the runway. Additionally the lineup correction for a 180 degree turnaround on
a runway is dependent on the runway width. There is a distingshion between the minimum
B767 EFRAS , REV 3
B767 EFRAS
and the nomianl lineup distances for a 180 degree turnaround on runway. For the nominal
180 degree turnaround the aircraft is realigned on the runway centerline. Whereas the
minimum value gives the absolute minimum value where the aircraft is not realigned on
the centerline.
The lineup corrections used for the calculation are displayed in the additional information
field available with the ESC key (see item 12)
13.20.20 BASIC SETTINGS - NOT SELECTABLE
1.3
The input-menu mainly consists of three zones which are indicated by A, B and C in the
figure below.
Zone A:
This line contains the input fields to define the mission, i.e. the type of aircraft, the flight
number, the airport and the runway.
By entering the aircraft registration the EFRAS-program selects the respective
airplane data including MTOW, engine type, etc.
The flight number is required for bookkeeping the different calculations, i.e. every
calculation with a flight number other than 0000 will be stored on the VAIO and
downloaded to the Lauda Air headoffice whenever the VAIO is updated.
If the flight number will be kept 0000 the calculation will not be stored on the VAIO
Therefore if you just want to perform a test calculation you should use the flight number
0000.
The airport could be entered either with the three or four letter code.
After the selection of the airport the EFRAS-program automatically shows the different
run-ways available at the respective airport for the selected aircraft (registration). The
Page
4,
Date 07.02.2000
B767 EFRAS
respective runway selection could also be activated by pressing the F12-key. For
detailed explanation please refer to item 5 (RUNWAY SELECTION).
A
B
Figure 1: Input-Menu
Zone B:
This line contains the input fields to define the environmental conditions, i.e. the wind, the
OAT and the QNH. Additionally you will find the input field for the estimated takeoff
weight.
The wind must be entered with direction and speed. The program then automatically
calculates the head/tail-wind component and the crosswind component.
The OAT can be entered in degree celsius or degree fahrenheit. As the temperature
range for both units overlap each other, you are required to add the unit when entering
the temperature. The program displays automatically the OAT in both units next to the
input field.
B767 EFRAS
The QNH may be entered in hPa or inch HG. As the QNH range for both units do not
overlap each other, you are not required to add the unit (C or F) when entering the QNH.
The program displays automatically the QNH in both units next to the input field.
With the Est TOW field you are able to select three different calculation modes.
- By entering 0 the different weights (MATOW, PTOW, field length-, climb- and obstacle
limited TOW), the EPRs, the VREF-speeds and the acceleration altitude are calculated
and the EFP will be displayed.
The V1, VR and V2 speeds are only calculated if the PTOW < MTOW.
- If you enter a specific weight, e.g. 160 tons for 767, the takeoff speeds and the
assumed temperature method values (if applicable) are always calculated additionally
(e.g. look at sample in item 4).
- By entering MAX the program will calculate the highest possible PTOW for the
respective runway. Therefore the Flaps will automatically be set to Optimal and the Packs
will automatically be set to OFF.
Like with Est TOW = 0 the V1, VR and V2 speeds are only calculated if the PTOW <
MTOW.
Additionally Improved Climb and V1/VR-Speed Ratio are no longer selectable. The
program automatically checks whether these procedures will give a higher TOW.
These two buttons will have yellow colour (only with MAX) in the output menu to indicate
that this selection was done by the program.
Zone C:
This zone consists of nine selection buttons covering the runway condition, the airplane
status conditions ( FLAPS, PACKS, ANTI-ICE, BRAKES, as well as specific
procedures ( CG, Improved Climb, V1/VR-Speed Ratio) and a SPECIALS field (for
runway shortening, additional obstacle, MEL and CDL). Each of the nine buttons is easily
accessible by pressing one of the F1 to F9 keys.
The F1 key gives you access to the RUNWAY CONDITION field. This will be explained
separately in item 6.
The FLAPS ( F2 key) buttons allows the selection of the different flap settings. For
some airports the selection is reduced due to performance requirements (e.g. flaps 1
and 5 not allowed for 767 at Salzburg, runway 16, due to turn radius considerations).
If Optimal is selected the program calculates the takeoff weights for all allowed flap
settings and then selects that flap setting which gives the highest PTOW.
By pressing F3 you have access to the PACKS selection buttons. If Est TOW is set to
MAX the PACKS are automatically set to OFF and no selection is possible.
Page
6,
Date 07.02.2000
B767 EFRAS
The ANTI-ICE selection is accessible with the F4 key. Please note that Eng Anti-Ice ON
and Wing+Eng AI ON is inhibited for temperatures higher than 10C.
With the F5 key it is possible to modify the brake configuration in the BRAKES . For
detailed information refer to item 7
The CG ( F6 key) input field handles the alternate forward C.G. limit for takeoff. It is only
appli-cable for the 767. For more information look at item 8.
The selection of Improved Climb can be activated with the F7 key.
The selection of improved climb is only possible at those airports where it is allowed by
Lauda Air.
YES /Optimum will be shown in black colour. If the usage is not allowed YES is shown in
grey colour.
If MAX is choosen as Est TOW the program deactivates the Improved Climb selection
and auto-matically selects improved climb whenever it is allowed and yields to a higher
PTOW.
The selection of V1/VR-Speed Ratio can be activated with the F8 key.
The selection of Max V1/VR is only possible at those airports where it is allowed by
Lauda Air.
Max V1/VR will be shown in black colour. If the usage is not allowed Max V1/VR is
shown in grey colour.
If MAX is chosen as Est TOW the program deactivates the V1/VR-Speed Ratio selection
and automatically selects Max V1/VR whenever it is allowed and yields to a higher
PTOW.
The F9 key gives access to the SPECIALS input field. This field is used for runway
shortening, additional obstacle and MEL/CDL items.
Additionally the selection of thrust reverser inoperative in case of wet/contaminated
runway will be possible if the respective runway condition was selected first in the
RUNWAY CONDITION (see item 9 and 10)
1.4
OE_LAX
0000
(000/0)
15C
1013 hPa
0
Date 07.02.2000 , Page
B767 EFRAS
FLAPS 1)
PACKS 1)
ANTI-ICE 1)
BRAKES 1)
CG 1)
Improved Climb 1)
V1/VR-Speed Ratio 1)
SPECIALS 1)
Optimal
ON
Anti-Ice OFF
Anti-Skid ON
Most Forward
No
Standard
NO
The output-menu shows the respective takeoff data for the selected conditions and also
provides a possibilitiy for modifying each of the selected conditions except the airport,
aircraft and flight number.
Like the input-menu the output-menu can also be divided into four major zones named D,
E, F and G as you can see from the figure below.
Zones D and E display the selected airport, environmental and aircraft conditions and
provide a possibility to modify most of the settings.
Zone F shows the result of the calculation, i.e. the takeoff parameters.
Zone G provides different buttons for general functions, e.g. start the calculation or exit
the program.
D
E
Figure 2: Output-Menu
Page
8,
Date 07.02.2000
B767 EFRAS
Zone D:
This zone contains the information about the aircraft and the airport/runway on which the
calculation is based.
The left field contains the aircraft type (e.g. B763), the registration (e.g. OE-LAX) and
the engine type (e.g. PW 4060).
The large field in the middle shows all relevant airport/runway information which are
used for the calculation. It is split into three lines.
The first line contains the three and four letter code and the name of the airport as
well as the airport elevation.
The second line provides the runway data (i.e. runway designator, runway length, slope,
clear-way and stopway) used for the determination. If you would like to change the runway
you could do this by pressing the F12 key which gives you the runway selection page
again.
The environmental conditions (wind component, OAT and QNH) as well as the
Est. TOW in-put field are shown in the third line.
If you change the runway the wind component will automatically change accordingly after
mov-ing to any other input field or starting the calculation.
The right field shows the runway designator. Please note that always the designator
of that runway is shown which is used for calculating the displayed takeoff parameters. If
you select a different runway the new designator will be shown after starting the
calculation by pressing the F10 key.
Zone E:
This zone contains the same selection boxes as zone C of the input menu. They are
accessible with the same F1-F9 keys and work similar (for explanation see item3/Zone
C). Additionally the flap setting and the takeoff thrust time limit used for the calculation
are displayed in a box on the right side.
Zone F:
This zone provides the takeoff parameters determined and is split into six different fields.
The major field on the left contains the relevant takeoff weights and speeds, i.e.
MATOW, Est. TOW (actual TOW), V1, VR, V2 and if applicable the assumed
temperature parameters, i.e. TASS and TOW TASS (the 25% max thrust reduction will
be observed).
The speeds are only shown if [Est. TOW 0] or [Est. TOW = MAX/0 and
PTOW < MTOW].
The second field from the left shows the different takeoff weight limits, i.e. PTOW,
MTOW, field length(FL)-, climib(CL)- and obstacle limited (OL) takeoff weight.
B767 EFRAS , REV 3
B767 EFRAS
The field length -, climb - and obstacle limited takeoff weight shown are adjusted for the
respective aircraft condition (e.g. MEL-Items) except for the following cases:
- wet/contaminated runway: FL/CL/OL-TOW are always shown for the dry runway
- Improved climb: CL-TOW shown for no improved climb
The brake energy and tire speed limited takeoff weights are not shown separately.
Therefore it is possible that the PTOW shown is lower than the displayed FL/CL/OL
takeoff weights.
Next to the different takeoff weights you find a field with the different EPR values
(takeoff, climb and go around). There are two columns showing the values for the OAT
and the TASS. The EPR values according to the OAT, i.e. full thrust takeoff, are always
shown. The respective values for the assumed temperature are only displayed if the
reduced thrust takeoff is applicable.
On the right side the VREF, VREF+40 and VREF+80 are displayed in a seperate field.
The acceleration altitude is shown in a separate box below the EPR- and VREF-field.
The engine failure procedure (EFP) is displayed in a seperate box in the lower right
corner.
By using the Bild (page up) / Bild (page down) keys it is possible to change the EFP
presentation (EFP can be displayed in the whole zone F).
Zone G:
This zone provides four buttons for general actions. From left to right: With the first one
F10: Re-Calculate (same as F10) it is possible to start the calculation again, the second
one Input will change the menu back to the input-menu, the third one Print is only a
provision and shall not be used and with the right one F11:Exit (same as F11) the
program can be closed.
13.20.40 EFRAS - OUTPUT - MENU
1.5
RUNWAY SELECTION
The runway selection window automatically opens by pressing the (TAB) key after an
airport entry has been made or by pressing the F12 key. By using the (down) or
( up) key you can select the desired runway which then will appear underlayed in blue
colour. The selection has to be confirmed with the (return) key.
All available runways for the selected aircraft are displayed.
All relevant information required to distinguish between the available runways/conditions,
e.g. different obstacle sets or runway shortenings, are displayed in the window.
The window is divided into eight columns ( RUNWAY, POSITION, DEPARTURE,
LENGTH, SLOPE, CWY,SWY, WIP(work in progress)).
For detailed explanation look at the following example:
The example shows an artificial airport with two runways 01/19 and 10/28. All runways
have zero slope and zero clearway ( CWY) and stopway ( SWY).
Page
10 ,
Date 07.02.2000
B767 EFRAS
11
B767 EFRAS
Figure 3: Runway-Selection
For runway 01/19 you find five different runways listed and for runway 10/28 four. The
runways are sorted basicly according to the designator and runway length.
The columns POSITION and DEPARTURE are used to distinguish between different
conditions of the same runway direction. Like with the runway weight charts, where
sometimes more than one chart was published for one runway direction, there are also
different runways displayed for selection in the EFRAS program. These different
runways cover different conditions and/or run-way length due to a wide variety of
reasons, e.g. runway shortening due to WIP or additional tem-porary obstalces like
cranes or ships in the flight path.
This example shows the different possiblities of presentation:
The first and sixth line show the presentation of a normal runway.
Runway 01 and 19 with 4000m length valid for all departures.
The second line shows an example for a taxiway intersection takeoff. In the column
POSTION you find the respective takeoff position, in this example the calculation would
be based on a takeoff on runway 01 from taxiway A. The available runway length is
3500m and it is valid for all cases ( DEPARTURE ALL).
Line three and seven represent a runway shortening at the end of runway 01,
threshold runway 19 is displayed by 800m as 3200m is shown in the LENGTH column.
Therefore you find NORMAL in the POSITION column for runway 01 and DISPL. THR in
the POSITION column of runway 19.
NORMAL in the POSITION column means that the takeoff position is the same as during
normal operation but there will be a runway shortening at the end of the runway.
As an additional indication for a preliminary runway you will find YES listed in the WIP
column.
Line four and five show an example for a runway with different obstacle sets and/or
EFPs for different departure routes. In these cases you will find the respective names
listed in the DEPARTURE column, e.g. LT DEP / RT DEP.
Page
12 ,
Date 07.02.2000
B767 EFRAS
Runway 28 at Rio de Janeiro (GIG/SBGL) would also be an example for such a case.
The last two lines represent a case of a runway with different obstacle sets for all
departures, e.g. ships within the flight path. In this example you could select between two
obstacle sets, NO SHIP and SHIP230, similar to the two different runway weight chart
published in the past. SHIP230 stands for an obstacle set which covers ships up to 230 ft
within the flight path. Practical examples for such cases are Singapore (SIN/WSSS) or
Boston (BOS/KBOS).
Another common case would be NOCRANE and CRANE to indicate a preliminary crane
in the flight path.
13.20.50 RUNWAY SELECTION
1.6
The EFRAS program covers the different runway conditions by applying the respective
decre-ments according to AOM chapter 8.10. To activate this function move to the
RUNWAY CONDITION selection box or press the F1 key. By pressing the (down) or (
up) key you can select the Wet or Contaminated field. As default the wet or contaminated
runway calcualtion is based on the use of reverse thrust. If no credit for reverse thrust
should be taken into account, e.g. thrust reverser inoperative, the Thrust Reverser inop
YES box must be selected in the SPECIALS menue. After selecting the Contaminated
field the following pop-up-menue will appear.
A
B
C2
C1
D
Figure 4: 767
B767 EFRAS , REV 3
13
B767 EFRAS
As explained in item 1 the (TAB) and (UP/DOWN) keys are alternately used to
navigate between and within the different input fields. In the expamle above the
(TAB) key is used to move between the A, B, C1, C2 and D fields and the
(UP/DOWN) keys for selection within the B and C2 field. Finally the selection has to be
confirmed with the (return) key.
13.20.60 RUNWAY CONDITION SELECTION
1.7
BRAKES SELECTION
The BRAKES selection box includes the buttons for Anti-Skid ON and OFF as well as
one brake deactivated (1-Brake Deact).
Additionally for the B767 the provisions are provided to cover the very unlikely possibility
of two brakes assumed to be failed (2-BASF). [Note: This feature would be required in
the exceptional cases that certain maintenance procedures could not be fulfilled and as a
consequence the airplane shall be dispatched with two brakes assumed failed.] As this
feature is not certified for normal operation the function is deactivated and therefore
appears in grey colours. As the one brake deactivated procedure distinguish between
method 1 and method 2 (see AOM 23.10.08) the following pop-up-menue will appear
after selecting the 1-Brake Deact. button. In this popup-menue the (TAB) key is used to
move between the A, B and C fields and the
(UP/DOWN) keys for selection within the B field as also explained in 1.The selection
has to be confirmed with the (return) key.
A
B
C
10.70
Page
14 ,
Date 07.02.2000
B767 EFRAS
1.8
CG SELECTION
As described in B767 alternate forward C.G. limit for takeoff the EFRAS program
also provides this procedure. This feature is only possible for selected airports.
After selecting the CG input field (e.g. with the F6 key) use the (UP/DOWN) keys to
move to the Alternate (% MAC) button. The following pop-up-menue will then appear and
the (TAB) key should be used to move within this menue. The selection has to be
confirmed with the (return) key.
13.20.80 (753/767) CG SELECTION
1.9
SPECIALS
The SPECIALS input field covers several abnormal conditions of the aircraft (e.g.
MEL/CDL and the runway (shortening or additional obstacle). After selecting the YES
button the following menue will open up. To navigate between the different input fields AG use the (TAB) key.
Line A and G are buttons to activate/deactivate the SPECIALS selection, i.e. whenever
you se-lected one of the lines B1-G you must move to the line H, Specials OK. After
choosing either A or G a confirmation with the (return) key is required.
The input fields B1 and B2 are used for runway shortenings. If the runway shortening
is at the beginning of the runway use the Start box to insert the displacement (in meter).
For shortenings at the end of the runway use the End field (B2). The input of a
displacement at the beginning and the end of the runway is also possible. After the
calculation the resulting new runway length is displayed on the output menue. The
inserted displacements are also displayed in the addtional information field available with
the ESC key (see 11). Please be informed that the line-up distance is the same as used
with the not shortened runway (for crosscheck you can also use the ESC key, see item
11).
15
B767 EFRAS
The MEL selection is available at line C and the CDL selection at line D. To dis-play
the respective selection list press any key. For more information regarding these
selection boxes refer to item10 MEL/CDL SELECTION.
The EFRAS program provides the calculation of wet and contaminated runway
based on the use of reverse thrust or no reverse thrust. Line E provides the respective
selection box to trig-ger the calculation not using reverse thrust and works only together
with the RUNWAY CONDITION selection box.
Please note that this line is only shown if a wet or contaminated runway is selected first in
the RUNWAY CONDITION selection box.
The EFRAS program also provides the possibility to add one additional obstacle.
Therefore line F and G are used to input the distance from brake release in meters (F:
Dist From BR[m] ) and the height above sealevel in feet (G: Height From SL [ft] ), i.e. the
elevation of the obstacle in feet above mean sea level (MSL). To crosscheck the input
you can use the ESC key, see item 11, after the calculation is performed.
A
B1
B2
C
D
E
F
G
Page
16 ,
Date 07.02.2000
B767 EFRAS
Figure 7: 767 SPECIALS input field
17
B767 EFRAS
2.1
GENERAL
A reduction in the required wing lift will present itself as either a reduction in airplane
attitude for the same speed and weight or a reduction in speed for the same attitude and
weight. This reduces both the stall speed and takeoff attitude limited speed (preventing
tail strike at rotation) which are the basis for calculating takeoff operating speeds. A
reduction in these speeds reduces the field length required for a given takeoff weight.
The reduction in tail down load also reduces the airplane's trim drag which improves
climb capability.
The resulting takeoff performance improvement is either an increase in the takeoff weight
for a particular airport's conditions or the same takeoff weight at more limiting conditions
(shorter field length, higher temperature, etc.). The key characteristics which determine
the amount of benefit are the weight of the airplane, the tail moment arm length, and the
distance between the original forward C.G. limit and the alternate forward C.G. limit.
21
B767 EFRAS
The location of the center of gravity affects the tail load to trim
2.2
LIMITATIONS
The use of an alternate forward C.G. limit for takeoff require the following mandatory
additional limitations:
EFRAS
The selection of the alternate forward C.G. limit for takeoff is possible with the respective
CG input field.
The use of the alternate forward C.G. limit for takeoff is restricted to selected airports.
Therefore the respective input window opens only with this selected airports.
After selecting the CG input field (e.g. with the F6 key) move to the Alternate (%MAC)
button. The following pop-up menu will then appear and the (TAB) key or the rnouse
should be used to move within this rnenu. The selection has to be confirmed with the
(return) key.
Page
22 ,
Date 07.02.2000
B767 EFRAS
2.4
SPEEDS
The takeoff speeds obtained with EFRAS are already corrected for the alternate forward
C.G. limit if this procedure is selected.
In case the speeds are determined with the speed table (QRH or AOM Vol.II Chapt. 11)
the V1-, VR- and V2-speeds shall be corrected using the following decrements to
account for the alternate forward C.G. limit.
lnterpolation between the different values (%MAC, T/O - speed) is allowed.
Correct V1-, VR- and V2-speed from speed table by the following correction value-.
T/O
V1, VR & V2 SPEED
Spee
CORRECTION KIAS
d
FLAPS 5 and 15
KIAS Alternate forward C.G limit (%MAC)
15% 20% 25% 30% 34%
100
-1
-1
-2
-2
-3
145
-1
-2
-3
-3
-4
190
-1
-2
-3
-4
-5
T/O
V1, VR & V2 SPEED
Spee
CORRECTION KIAS
d
FLAPS 20
KIAS Alternate forward C.G limit (%MAC)
15% 20% 25% 30% 34%
100
-1
-1
-2
-2
-3
135
-1
-1
-2
-3
-4
170
0
-1
-2
-3
-3
Example:
B767, TOW = 180.0 tons, Flaps 5, Sea level, 20C, Alternate fwd C.G. limit = 20%
QRH-Speed table: V1 = 161 kts, VR = 165 kts, V2 = 171 kts
T/O Speed decrement for alternate forward C.G. limit for 20%: -2 kts
T/O Speeds: V1 = 161 kts - 2 kts = 159 kts
B767 EFRAS , REV 3
23
B767 EFRAS
VR = 165 kts - 2 kts = 163 kts
V2 = 171 kts - 2 kts = 169 kts
The takeoff weights from the EFRAS-program are based either on a standard engine
failure procedure (EFP) or a special engine failure procedure (Special EFP), assuming
10 min T/O thrust for B 767. The time limit used is shown on the EFRAS OUTPUT-page
in a separate box.
3.1
Climb straight ahead at V2 speed until the acceleration altitude shown in ft QNH is
attained. Standard acceleration altitude is 1500 ft above aerodrome elevation. Level off
for flap retraction and, at the same time, start a 15 bank turn to the specified navigation
aid. During turn accelerate in level flight to final segment climb speed. After flap
retraction, which may be achieved prior to or after reaching the navigation aid, climb with
MCT to the desired altitude.
The PIC has to determine the moment when the climb will be finished for further actions
(approach, diversion or holding).
Nevertheless, the takeoff performance calculation assumes a continued climb
after flap retraction with MCT until reaching the specified holding.
A bank angle of 25 is assumed after reaching clean maneuver speed.
3.2
For several runways, special procedures are published to assure a safe and efficient
operation.
If in case of an engine failure a straight climbout to the level off altitude does not provide
the required obstacle clearance, a Special EFP will be specified.
All differences to the standard engine failure procedure are published. All non-addressed
items are unchanged from the description above for the standard EFP.
If obstacle clearance considerations require a turn before reaching clean maneuver
speed a bank angle of 15 is assumed.
The Special EFP procedure will be specified with the word Special EFP.
Note:
Page
24 ,
B767 EFRAS
In some EFP/Special EFP information is given in brackets, e.g. [4
DME FOX 111.1]. This is a secondary information, which has to be used
only if the primary information in front of the brackets is not useable.
3.3
EFP
Example:
Obstacle clearance is assured within the marked area on the figure above.
Appropriate wind correction is applied.
25
B767 EFRAS
Special EFP
Example:
Obstacle clearance is assured within the marked area on the figure above.
Appropriate wind correction is applied.
3.4
ACCELERATION ALTITUDE
The acceleration altitude (standard or non-standard) is given in the respective box on the
OUTPUT-menue of the EFRAS-program. These altitudes are calculated as a single point
and based on the respective environmental and obstacle conditions and rounded to the
next higher 100ft step.
Page
26 ,
Date 07.02.2000
B767 EFRAS
EFRAS program
Flight crews have to pass an introduction course concerning use of the EFRAS program.
Procedures
To avoid any mistakes in the T/O Performance calculation, both pilots have to
make a calculation and verify the output. If there are differences in the output,
check the inputs and the version of the EFRAS software (Database Ver. xx.xx.).
If there is a difference in the version of the EFRAS software, check with Dispatch
the right version and confirm the output with Dispatch. There must be always tow
ident outputs of a calculation.
Pilot notebooks
For takeoff, approach and landing the laptops have to be switched off and the power
adapter must be disconnected from the aeroplane power outlet.
In all phases of flight, especially during takeoff, approach and landing, the notebooks
have to be stowed safely.
4.2
In order to use the alternate forward center of gravity limit for takeoff on B767, the
following shall be considered and fulfilled:
- The EFRAS program is the sole mean for calculating the MTOM and the takeoff
speeds (including wet and contaminated runways).
- A curtailment of 4% MAC, which is automatically applied by the EFRAS program.
- The actual TOM shall be at or above 130 tons.
- The commander shall verify on the final mass and balance sheet (including the last
minute changes), that the actual center of gravity is behind the calculated center of
gravity, which was used for the calculation of the MTOM. If this is not the case, the
MTOM and takeoff speed calculation shall be based on a 7% MAC (standard most
forward MAC calculation).
- Flight crews have passed an introduction course concerning use and operational
considerations of alternate forward center of gravity limit for takeoff.
- The respective Ground Operations have passed an introduction course concerning
use and operational considerations of alternate forward center of gravity limit for
takeoff.
B767 EFRAS , REV 3
27
B767 EFRAS
Page
28 ,
Date 07.02.2000
B767
FLEET-INFO 1/99
GENERAL
This new format includes all valid fleet-infos and puts all fleet-infos previously issued
out of force.
TABLE OF CONTENTS
1
ENTERING OF ZFW.......................................................................................................................................................3
5.1
5.2
5.3
10
11
12
ATC CLEARANCE.........................................................................................................................................................5
13
14
15
16
17
18
19
20
21
FUEL - BALANCING......................................................................................................................................................8
Date 26.02.99 , Page 1
B767
FLEET-INFO 1/99
22
PILOT - LICENCE...........................................................................................................................................................8
23
24
25
26
27
ABORTED TAKEOFF....................................................................................................................................................9
28
29
30
31
32
33
34
35
36
B767
FLEET-INFO 1/99
1
ENTERING OF ZFW
No ZFW is to be entered into the CDU before figures can be reconfirmed with the actual
loadsheet.
Special attention must be drawn to the fact that in case a departure procedure involves a turn
to clear obstructions horizontally rather than vertically it is assumed that no acceleration is
made during the turn, even if the indicated level off height has been attained.
The climb must be continued until on course at the appropriate speed. This is required to
guarantee lateral obstacle clearance.
UNDER NO CIRCUMSTANCE MAY AN OLD OR OTHER PERFORMANCE SHEET BE
INSERTED INTO THE JEPPESEN AAM FOLDER!!!
In addition to the OPS NOTICE folder in Dispatch office, you will find a copy of the folder on
each B767 areoplane. The folders are stored under the observer seat in the cockpit. This
system has been installed to keep you up to date with all information, even while you are on a
rotation.
however all pilots are still required to sign the record sheet of the OPS NOTICE folder in the
Dispatch office.
If ground time in MUC is less than one hour all transit passengers from MIA must remain on
board. There have been several occasions, where smokers demanded to be let off the
areoplane in order to smoke in the terminal. Unless the areoplane is late, it is suggested to let
individual smokers off the areoplane.
Our complete B767-Fleet is now equipped with Phase 3 Engines. Drag factor and F/F factor
are changed accordingly. If you observe that these factors are insufficient make a note on the
Pilots Voyage Report, but please don't change it yourself.
B767
FLEET-INFO 1/99
5.1
Drag factor
+1
0
F/F factor
+1
0
ETOPS APPROVAL:
To avoid any further incidents in the future, please make sure that Crew Control has your
correct telephone number(s) and contact address.
According to an information from Boeing, the rain repellent fluid can produce toxic-gas. This
gas should not be inhaled by flight-crew or passengers. To mark the presence of this gas in
the case of a system malfunction (reservoir is located in the flight deck), this fluid is now
marked by lemon smell.
Boeing recommends to use 100% oxygen on the flightdeck and to land at the nearest
appropriate airport in the event of lemon smell.
Rain repellent system is not installed on OE-LAY and on any new delivered Boeing.
Flight documentation (e.g. CFP, WX charts, etc.) should be left in the areoplane and
forwarded to VIE Dispatch office by the returning crew.
In order to extend the life of our B767-engines all crews are requested to use maximum
reduced thrust T/O.
B767
FLEET-INFO 1/99
10
Your cooperation in keeping the computer screens in the cockpit clean is highly appreciated.
By any means do not clean the screens with the sanicom tissues which are provided for
desinfection purposes only. Please use only cleanex and tissuses for cleaning the screens.
11
12
ATC CLEARANCE
Please observe, that an ATC clearance prior departure shall only be requested with both
pilots present and on request of or in coordination with the Commander. If a certain time
frame is give (e.g. LOWW: ...request routing clearance 10 min prior planned push back), this
time frame shall be complied with.
13
Empty forms should be carried on the areoplane and the First Officer should check whether
they are available. (Forms file under observer seat) In case there are no Voyage Report
Forms found on a particular areoplane, please make sure that the next crew take some by
putting forms with a corresponding note into the respective areoplane tray in Dispatch.
14
If the carriage of additional fuel is required as per GB/OM (Item 8.1.7.1.6) this amount of fuel
will be shown on the CFP as Extra Fuel just above the minimum block fuel figure.
It is the Commanders authority to decide on uplifting of additional fuel whenever he thinks it
operationally required.
At this point it is important to know that a fixed fuel increment for each areoplane (increased
fuel flow with engine life etc) is already incorporated into the CFP estimated trip fuel
calculation. This increment is based on Lauda Air statistics on grounds of actual fuel burn
figures.
As experience shows, burn offs on all areoplane seem well within limits for the time being.
Date 26.02.99 , Page 5
B767
FLEET-INFO 1/99
In order to fine tune areoplane burn off even further as well as, in an everlasting attempt to
operate as economical as possible, the following procedure will aply:
If a higher speed that the CFP calculated speed must be flown, a new CFP or at least a
fuel analysis with this particular increased speed should be requested from dispatch in
order to obtain a new accurate fuel scenario.
The reason for selecting a higher speed must be indicated by means of voyage report to
OO and DO.
If the Commander decides to take extra fuel to the minimum block fuel shown on the CFP,
and this planned extra fuel is more than 2000/1500kg on standard/reclearance flightplan,
the reason for uplifting excessive fuel shall be indicated by means of PVR to OO and DO.
In addition CFP estimated burn off, actual burn off and the additional burn off (being the
difference between actual and estimated burn off) should be indicated by means of PVR.
If the actual and company estimated fuel burn differ by more than 3% having followed the
exact CFP flight scenario, a respective note on the PVR should be submitted.
All this is an aid of a more economical operation and the maintenance of realistic CFP
parameters. Your cooperation in this regard is highly appreciated.
15
Since in some countries (e.g. Germany) it is a legal requirement to seal ALL areoplane exit
and service doors, custom seals are now available on board of each areoplane (in a sealed
envelope in the A/C document bag in the cockpit).
The following procedure has been agreed upon with Manager Operations Standards:
Seals are stored in sealed envelope on board in the A/C document bag with spare record
forms.
In case of use by Commander, break seal, remove sticker and state numbers used in
areoplane technical log (left column)
Place stickers on areoplane doors and openings as required to prevent illegal opening.
On returning to areoplane break and remove all seals and note all numbers of broken seals
in technical areoplane log (right column).
Commander is responsible for returning the opened envelope to dispatch
Dispatch will provide new closed envelope with security seals for next flight.
16
Contents of the AAM will be tailored to match the trip kit. All these tables are surveyed airports
and therefore updated by Jeppesen.
RTOWs for additional unscheduled flights will be provided by Dispatch prior departure or
upon request.
All revised, amended and newly acquired RTOWs will be calculated using approved 10 min
T/O thrust in the event of engine failure. Tables where 10 min T/O thrust is not essential for
performance reasons will stay as is in the manual until revised for other reasons. However, it
Page 6 , Date 26.02.99
B767
FLEET-INFO 1/99
is Lauda Air policy to make use of 10 min T/O thrust in the one-engine out case, if required. If
more than 5 min T/O thrust was used, a corresponding tech log entry has to be
accomplished by the Commander.
17
Beside of PW4060, packs on/off and dry/wet, we have two different RTOW tables for runway
16 in SZG using
1. the overall length of 9022ft and a clearway of 197ft (backtrack from taxiway A
18
Use of V/S mode during climb should be avoided, because of no speed protection in this
mode.
19
FLAPS OPERATION
The slats/flaps can be retracted/extended before they reach a selected position as long as all
speedlimits are covered. During acceleration clean up with low weights the flaps can be
selected up before reaching flap 1 with the speed above Vref30+60 and below flaps 1
placard speed. The SOPs will be amended.
20
We have to point out, that interpolation in the AAM and B767 slush/standing water tables is a
standard procedure, if necessary. There shall also be nearly no objections against flying with
minimum blockfuel and trying to make it nonstop, as planning with a technical stop right away.
B767
FLEET-INFO 1/99
21
FUEL - BALANCING
On a recent meeting with Boeing the procedure of Fuel balancing was discussed. Boeing
underlined the importance to follow the QRH procedure in case of a EICAS Fuel Config. MSG,
in order to identify a suspected fuel leak.
This requires that fuel balancing should not be initiated before a fuel config. Msg appeared on
the EICAS.
22
PILOT - LICENCE
Please be advised, to fly with a copy of youre licence is not allowed. A recent case caused a
lot of troubles on a rampcheck by the CAA.
23
Every month Honeywell has certain infos for crews in regard to configuration problems.
This infos will be made available in a new section of Ops-Notice file.
24
With effect from 10. Nov 97 boarding will automatically be authorized by the respective gate
agent 30 minutes prior STD. In case of a possible delay inform the ramp agent in due time.
The ramp agent will coordinate boarding with the respective gate agent.
25
During the last ATC OPS meeting, again LaudaAir pilots were criticised for unprofessional
R/T discipline and phraseology by Air Traffic Control.
Points of the discussion were e.g. that Lauda-Air pilots start initial contact with Ground Control
while transmissions are already made on the frequency, resulting in blocked frequencies due
to a squeaking noise. Therefore frequency congestion and the controllers workload increase
due to additional readbacks. This usually happens during peak hours, however ATC is not
able to supply an additional frequency.
May I ask everybody to focus on correct R/T phraseology and discipline at all times!
26
The oil brand on our hole B767 fleet has been changed to
MOBILE JET OIL II
Please be informed that you also find same reserve oil canes in the fly away kit in the bulk
cargo.
The key for the Fly away kit is in the Video- compartment in the forward cabin.
Page 8 , Date 26.02.99
B767
FLEET-INFO 1/99
27
ABORTED TAKEOFF
28
CHECK OUT
Be advised that it is prohibited for the Crew to leave the areoplane before all passengers have
disembarked.
29
Due to noiseproblems do not take off on RWY 16 in VIE during nighthours (2000-0400 UTC)
except you need RWY 16 due to performance reason.
30
ATLANTIC OPERATION
With immediate effect heading reference switch have to be left in magnetic north for Atlantic
crossing.
Use the plotting chart for normal in-flight routine monitoring and position checking and in case
you have to send Met-reports use it also for recording mid-weather.
The North Atlantic operation worksheet has to be used as a navigational backup just in case
your clearance is different to the CFP routing.
For pilots which are beginners in the North Atlantic operation it is strongly recommended to
use the worksheet also for preparation in receiving the oceanic clearance.
31
Please note that it is not required anymore to dim the EFIS and CDU screens, because of
breaking the dim-switches to often. Normal lights have to be dimmed as usual.
B767
FLEET-INFO 1/99
32
I case you are operating with a non Lauda Air flight number, please state at the initial call with
clearance delivery VIE the term operated by Lauda Air, e.g. Vienna Delivery, this is OS
33
COMPANY ROUTES
When programming the FMC with a specified company route, only the B767 nav data ident as
stated on top of the CFP (e.g. VIEBKK1) should be used.
Reason for this change was that there were discrepancies when using exit numbers with
related nav data company routes as stated on the flight plan exit / conversion infos sheet
carried in the trip kit. This sheet will be deleted in the future.
34
Lauda Air has acquired a winter operation CBT for pilot training. Whenever possible pilots will
be rostered to view this CBT program which is available as of Monday 23rd November, 1998.
However, due to the current seasonal weather scenarios pilots may access the CBT program
even if not rostered on a time available basis. For co-ordination of CBT availability and details
concerning log-on please contact Graziela DW 8187.
35
36
From now on HSI MAP MODE can be used on both Pilots side at the same time during ILS
Approaches. The necessary change in the Normal Procedures will follow soon.