EFRAS. The Performance Tool from Condor. 06 September 2011

Transcription

1 EFRAS The Performance Tool from Condor 06 September 2011

2 EFRAS 15 years of continuous development and experience: Start of development Start of Test-Phases with increasing number of Condor Pilots all Condor F/O equiped with Laptops and EFRAS all Condor pilots use EFRAS1 / Paper RWCs removed from aircrafts CIB A320 and CFG 753 start operation with EFRAS from first day Introduction of EFRAS Start of Development of Landing-Module Development of EFRAS Start of Development of EFRAS First operational use of EFRAS 2.2 on ICELANDAIR 757/767 fleet 2007 First operational use of Landing EFRAS on Austrian Airlines ER fleet 2008 Adaptation of EFRAS for use on Astronautic EFB Class 2 with ELAL ER fleet 2009 Entry into service on new B777F with AeroLogic Adaptation of EFRAS for use on navaero EFP Class 2 with Condor 757/767 fleet 2

3 EFRAS is in use by the following airlines 3

4 EFRAS Customer Base ELAL Israel Airlines: B /-200F, B ER, B /-300, B and B /-800/-800W Austrian Airlines: B ER, B ER and B /-700W/-800W CSA Czech Airlines: A310, B /-400, ATR 42/72 Icelandair: B , B /-300 Jade Cargo Airlines: B ERF Thomas Cook Airlines Belgium: A320 Thomas Cook Airlines (UK): B /-300, B ER, A320, A321, A330 Livingston Energy Flight: A321, A SunExpress: B , B W/-800WSFP Royal Flight Oman: B VIP His Majesty Sultan Flight of Brunei: B VIP Jazeera Airways: A320 WIZZAIR: A320, A321 DC Aviation: A319CJ AeroLogic: B777F Air Cargo Germany: B SF Uzbekistan Airways: A320, B , B ER TNT Airways: B F/-400F, B777F, B C Condor Flugdienst: B , B ER Condor Berlin: A320 4

5 In general EFRAS consists of three modules which work together: Pilot-Interface Calculation-module Database Calculation Program (Fortran 95) Performance Database Airport and Aircraft Database 5

6 EFRAS - Introduction 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 6

7 EFRAS Introduction TAKEOFF-MENU (standard) LANDING-MENU EFRAS Pilot Interface Version 2.2 provides different layouts with all relevant Information on one page. Pilots have the full authority to select settings and Conditions. 7

8 EFRAS Introduction Alternate TAKEOFF-MENU are available based on customer definition 8

9 EFRAS Introduction Generated by Condor Based on: - AIP - Topo-Charts - Jeppco-Charts - LIDO RM-Charts - ONC/TPC - Airport-Check - Notam Note: See Backup Information for more details Airport - Data Airport data are revised on a daily basis. Updates are provided to customer on a specially agreed schedule. Includes: - over 1400 airports Two options offered: - all airports provided - airline defined selection of airports 9

10 Example for EFRAS 2.2 Update (EFB Class 1) Performance and Operations Engineering Department Database / Software Update Dispatch Station (or FTP - Server) ISDN Modem (or Internet) Flight Reports Takeoff Data Sheet Update LOG LAN Update USB Update (or Internet) 10

11 Example for EFRAS 2.2 on Astronautic EFB Class 2 11

12 Example for EFRAS 2.2 on navaero EFB Class 2 12

13 Backup Information Airport-Data: : Obstacle Information Sources AIP ICAO Type A Aerodrome Obstruction Chart Example: Quito (UIO/SEQU) 13

14 Backup Information Airport-Data: : Obstacle Information Sources AIP ICAO Type B or C Aerodrome Obstruction Chart Example: HKG 14

15 Backup Information Airport-Data: : Obstacle Information Sources Topographical Maps Example Kangerlussuaq (SFJ/BGSF) 15

16 Backup Information Airport-Data: : Obstacle Information Sources Other Sources Jeppesen-Charts LIDO-Charts Airport Authority Google Earth ONC / TPC Airport Check any other source... 16

17 Backup Information Airport-Data: : Engine Failure Procedure (EFP) Design Turn Analysis Procedure Study the terrain in the area around the airport and select a departure path (EFP) - several path may be required Determine any critical obstacles for the choosen departure path Determine the required turn radius Examine other issues like: - Weather (winds, OAT, QNH) - Implications of airport situation, e.g. high altitude - Piloting considerations 17

18 Backup Information Airport-Data: : Engine Failure Procedure (EFP) Design Example Problem IMC Sply 900m 900m 18

19 Backup Information Airport-Data: : Engine Failure Procedure (EFP) Design Performance Considerations Field Length Climb Obstacle Tire Speed Brake Energy Weight associated with turn radius limited speed Runway Pavement restrictions others? 19

20 Backup Information Airport-Data: : Engine Failure Procedure (EFP) Design Turn Radius Limited Speed 20

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

22 Backup Information Airport-Data: Engine Failure Procedure (EFP) Design Calculation 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) 22

23 Backup Information Airport-Data: Engine Failure Procedure (EFP) Design Flight Path with Wind Example: T/O RWY 13R BOG Design Takeoff Sector for Zero Wind Flight Path with Wind 310 /20kt Flight Path with Zero Wind Flight Path with Wind 130 /20kt 23

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