EFRASThe Performance Tool

from Condor

06 September 2011

FRA HO/E2

EFRAS

15 years of continuous development and experience:

1994 - Start of development1995 - Start of Test-Phases with increasing number of Condor Pilots

1996 - all Condor F/O equiped with Laptops and EFRAS1

1997 - all Condor pilots use EFRAS1 / Paper RWCs removed from aircrafts

1999 - CIB A320 and CFG 753 start operation with EFRAS from first day

2001 - Introduction of EFRAS2

2002 - Start of Development of Landing-Module

2003 - Development of EFRAS 2.1

2005 - Start of Development of EFRAS 2.2

2006 - First operational use of EFRAS 2.2 on ICELANDAIR 757/767 fleet

2007 – First operational use of Landing EFRAS on Austrian Airlines 777-200ER fleet

2008 – Adaptation of EFRAS for use on Astronautic EFB Class 2 with ELAL 777-200ER fleet

2009 – Entry into service on new B777F with AeroLogic

2011 - Adaptation of EFRAS for use on navAero EFP Class 2 with Condor 757/767 fleet

FRA HO/E3

EFRAS is in use by the following airlines

FRA HO/E4

EFRAS Customer BaseELAL Israel Airlines: B747-400/-200F, B777-200ER, B767-200/-300, B757-200 and B737-700/-800/-800WAustrian Airlines: B777-200ER, B767-300ER and B737-600/-700W/-800WCSA Czech Airlines: A310, B737-500/-400, ATR 42/72Icelandair: B767-300, B757-200/-300Jade Cargo Airlines: B747-400ERFThomas Cook Airlines Belgium: A320Thomas Cook Airlines (UK): B757-200/-300, B767-300ER, A320, A321, A330Livingston Energy Flight: A321, A330-200SunExpress: B757-200, B737-800W/-800WSFPRoyal Flight Oman: B747-400VIPHis Majesty Sultan Flight of Brunei: B767-200VIPJazeera Airways: A320WIZZAIR: A320, A321DC Aviation: A319CJAeroLogic: B777FAir Cargo Germany: B747-400SFUzbekistan Airways: A320, B757-200, B767-300ERTNT Airways: B737-300F/-400F, B777F, B757-200CCondor Flugdienst: B757-300, B767-300ERCondor Berlin: A320

FRA HO/E5

In general EFRAS consists of three modules which work together:

Pilot-Interface Calculation-module

CalculationProgram

(Fortran 95)

Perfo

rman

ceDa

taba

se

Airport

and

Aircraft

Database

Database

FRA HO/E6

The EFRAS-Program has been designed to:- provide standardized takeoff / landing weight calculation

- allow the calculation of the highest possible TOW/LW for the respective conditions

- automatically observe all required limitations

- highest possible communality for different aircraft types

- provide additional performance background information if required

- give the pilot the highest possible authority in the selection of procedures

- allow the implementation of restrictions for each individuell aircraft and runway

- offer the possibility to present information to pilots depending on A/C & RWY

- make use of all performance options offered by the manufacture programs

- include MEL and CDL items

- provide optimized calculation of runway shortening or

additional obstacle

EFRAS - Introduction

FRA HO/E7

EFRAS 2.2 - Introduction

EFRAS Pilot Interface Version 2.2 provides different layouts with all relevantInformation on one page.Pilots have the full authority to select settings and Conditions.

TAKEOFF-MENU (standard) LANDING-MENU

FRA HO/E8

EFRAS 2.2 - Introduction

Alternate TAKEOFF-MENU are available based on customer definition

FRA HO/E9

Airport - Data

Based on:- AIP

- Topo-Charts

- Jeppco-Charts

- LIDO RM-Charts

- ONC/TPC

- Airport-Check

- Notam

Includes:- over 1400 airports

Two options offered:

- all airports provided

- airline defined selectionof airports

Generated byCondor

Airport data are revised on adaily basis. Updates are providedto customer on a speciallyagreed schedule.

EFRAS 2.2 - Introduction

Note: See BackupInformationfor more details

FRA HO/E10

Performance and OperationsEngineeringDepartment

Dispatch Station (or FTP - Server)

Example for EFRAS 2.2 Update (EFB Class 1)

LAN UpdateUSB Update(or Internet)

ISDN Modem

(or Internet)

Database / Software Update

Flight Reports

Takeoff Data Sheet

Update LOG

FRA HO/E11

Example for EFRAS 2.2 on Astronautic EFB Class 2

FRA HO/E12

Example for EFRAS 2.2 on navAero EFB Class 2

FRA HO/E13

Backup Information Airport-Data: :Obstacle Information SourcesAIP – ICAO Type A Aerodrome Obstruction Chart

Example: Quito (UIO/SEQU)

FRA HO/E14

Backup Information Airport-Data: :Obstacle Information SourcesAIP – ICAO Type B or C Aerodrome Obstruction Chart

Example: HKG

FRA HO/E15

Backup Information Airport-Data: :Obstacle Information SourcesTopographical Maps – Example Kangerlussuaq (SFJ/BGSF)

FRA HO/E16

Backup Information Airport-Data: :Obstacle Information Sources Other Sources

Jeppesen-Charts

LIDO-Charts

Airport Authority

Google Earth

ONC / TPC

Airport Check

any other source....

FRA HO/E17

Backup Information Airport-Data: :Engine Failure Procedure (EFP) DesignTurn Analysis Procedure

Study the terrain in the area around the airport and select adeparture path (EFP) - several path may be required

Determine any critical obstacles for the choosen departurepath

Determine the required turn radius

Examine other issues like:

- Weather (winds, OAT, QNH)

- Implications of airport situation, e.g. high altitude

- Piloting considerations

FRA HO/E18

Backup Information Airport-Data: :Engine Failure Procedure (EFP) DesignExample Problem

IMC Sply 900m

900m

FRA HO/E19

Backup Information Airport-Data: :Engine Failure Procedure (EFP) DesignPerformance Considerations

Field Length

Climb

Obstacle

Tire Speed

Brake Energy

Weight associated with turn radius limited speed

Runway Pavement restrictions

others ?

FRA HO/E20

Backup Information Airport-Data: :Engine Failure Procedure (EFP) DesignTurn Radius Limited Speed

FRA HO/E21

Backup Information Airport-Data: :Engine Failure Procedure (EFP) DesignObstacle Height Adjustment for Turning Departure

FRA HO/E22

Backup Information Airport-Data:Engine Failure Procedure (EFP) DesignCalculation Tools

Certified Performance (AFM-DPI)

Takeoff Analysis

- Boeing Takeoff Module (BTM)

- Boeing STAS program

- EFRAS

Analytical Tools

- Performance Engineer Manual (PEM)

- Boeing Climbout Program (BCOP)

- Fugawi (Electronic Chart program)

FRA HO/E23

Backup Information Airport-Data:Engine Failure Procedure (EFP) DesignFlight Path with Wind

Flight Path with Wind 130°/20kt

Flight Path with Wind 310°/20kt

Flight Path with Zero Wind

Design TakeoffSector forZero Wind

Example: T/O RWY 13R BOG

FRA HO/E24

Backup Information Airport-Data:Engine Failure on SID Check/Chart