You are on page 1of 47

Flight Ops Working Together - Use of A350 MEL for Dispatch

Flight Ops Working Together

A350 Flight Operations & Training

Use of A350 MEL for


Dispatch
Flight Ops Working Together - Use of A350 MEL for Dispatch

Contents

1 Brake Failure after Landing

2 APU Failure after Pushback

3 Smoke Detection Failure during Cockpit Preparation

4 Key Points

Page 2

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: General Workflow


After landing: At the gate:
BRAKES RELEASED BRAKES RELEASED
BRK 01 RELEASED > BRAKES BRK 01 RELEASED New defect in the logbook (pilot)

Press the DISPCH button (pilot)


Logbook consultation
(Maintenance)

Fault confirmation
(Maintenance)

MEL consultation
with AirN@v Dispatch MEL
Cockpit Preparation:
(Maintenance)
BRAKES RELEASED
> BRAKES BRK 01 RELEASED

New deferred MEL item in the logbook:


MEL check (pilot) Press the DISPCH button (pilot) 32-42-01 Normal Wheel Brake 01
(Maintenance)

Page 3

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Maintenance Crew

Same principle thanTick the box to activate the MEL item:

Page 4

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Maintenance Crew

Page 5

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Maintenance Crew

Page 6

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Maintenance Crew

Page 7

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: General Workflow


After landing: At the gate:
BRAKES RELEASED BRAKES RELEASED
BRK 01 RELEASED > BRAKES BRK 01 RELEASED New defect in the logbook (pilot)

Press the DISPCH button (pilot)


Logbook consultation
(Maintenance)

Fault confirmation
(Maintenance)

MEL consultation
with AirN@v Dispatch MEL
Cockpit Preparation:
(Maintenance)
BRAKES RELEASED
> BRAKES BRK 01 RELEASED

New deferred MEL item in the logbook:


MEL check (pilot) Press the DISPCH button (pilot) 32-42-01 Normal Wheel Brake 01
(Maintenance)

Page 8

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

Page 9

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

1. Display the DISPATCH page:

BRAKES RELEASED
BRAKES RELEASED
> BRAKES BRK 01 RELEASED
> BRAKES BRK 01 RELEASED

Page 10

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

2. In the OIS, click on ECAM EVENTS:

Page 11

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

3. Click on DISPATCH MSG:


VN-A350

BRAKES RELEASED
>AIR
BRAKES
PACK 1BRK
CTL01
2 RELEASED

Page 12

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

4. Read the Aircraft Status and click on the link to the associated MEL item:

Page 13

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

5. Read the dispatch conditions then click on the operational procedure symbol:

Page 14

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

6. Read the operational procedure…and check compliance:

Page 15

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

7. Return to the MEL item:

Page 16

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 1: Focus on MEL Use by Flight Crew

8. Tick the box to activate the MEL item:

OIS performance applications are automatically


updated.
Page 17

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Contents

1 Brake Failure after Landing

2 APU Failure after Pushback

3 Smoke Detection Failure during Cockpit Preparation

4 Key Points

Page 18

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: General Workflow


During pushback, after engine start:
APU AUTO SHUTDOWN
APU AUTO SHUTDOWN > APU FLAP CLOSED
MCC call
(pilot)

Apply ECAM procedure (pilot)


Press the DISPCH button (pilot) MEL check (pilot)

Decision to return
to gate (pilot, MCC)

Deactivation of the
APU flap
in open position
(Maintenance)

APU
> APU FLAP OPEN

New deferred MEL item in the logbook:


MEL check (pilot) 49-16-01A APU Flap
Press the DISPCH button (pilot)
(Maintenance)

Page 19

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

1. In the OIS, open the Ops Library:

Page 20

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

2. In the Ops Library, open the MEL:

Page 21

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

3. Open the MEL – Dispatch Messages section:

Page 22

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

4. In the Dispatch Messages section, select “APU”:

Page 23

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

5. In the APU Dispatch Messages, select “APU FLAP CLOSED”:

Page 24

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

6. Read the Aircraft Status. Choose between the two dispatch conditions:
In this scenario, the pilot, in coordination with the Maintenance Control Center (MCC),
decides to return to gate in order to deactivate the APU flap in open position (to recover
the APU).

Page 25

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: General Workflow


During pushback, after engine start:
APU AUTO SHUTDOWN
APU AUTO SHUTDOWN > APU FLAP CLOSED
MCC call
(pilot)

Apply ECAM procedure (pilot)


Press the DISPCH button (pilot) MEL check (pilot)

Decision to return
to gate (pilot, MCC)

Deactivation of
the APU flap in
open position
(Maintenance)

APU
> APU FLAP OPEN

New deferred MEL item in the logbook:


MEL check (pilot) 49-16-01A APU Flap
Press the DISPCH button (pilot)
(Maintenance)

Page 26

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Maintenance Crew

Page 27

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: General Workflow


During pushback, after engine start:
APU AUTO SHUTDOWN
APU AUTO SHUTDOWN > APU FLAP CLOSED
MCC call
(pilot)

Apply ECAM procedure (pilot)


Press the DISPCH button (pilot) MEL check (pilot)

Decision to return
to gate (pilot, MCC)

Deactivation of the
APU flap
in open position
(Maintenance)

APU
> APU FLAP OPEN

New deferred MEL item in the logbook:


MEL check (pilot) 49-16-01A APU Flap
Press the DISPCH button (pilot)
(Maintenance)

Page 28

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

1. Display the DISPATCH page:

BRAKES RELEASED
APU> BRAKES BRK 01 RELEASED
> APU FLAP OPEN

Page 29

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

2. In the APU Dispatch Messages, select “APU FLAP OPEN”:

Page 30

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

3. Read the Aircraft Status and click on the link to the associated MEL item:

Page 31

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use by Flight Crew

4. Read the dispatch conditions then click on the operational procedure symbol:

Page 32

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use

5. Read the operational procedure…and check compliance:

Page 33

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use

6. Return to the MEL item:

Page 34

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 2: Focus on MEL Use

7. Tick the box to activate the MEL item:

Performance Applications are automatically updated.

Page 35

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Contents

1 Brake Failure after Landing

2 APU Failure after Pushback

3 Smoke Detection Failure during Cockpit Preparation

4 Key Points

Page 36

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: General Workflow


Cockpit Preparation::
SMOKE L AVNCS DET FAULT
SMOKE L AVNCS DET FAULT
> SMOKE L AVNCS DET
Apply ECAM procedure (pilot)

MEL check (pilot) AOG


Press the DISPCH button (pilot)
(no dispatch)

Change both
smoke detectors
(Maintenance)

Aircraft release
(Maintenance)

Page 37

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

2. In the OIS, open the Ops Library:

Page 38

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

3. In the Ops Library, open the MEL:

Page 39

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

4. Open the MEL – Dispatch Messages section:

Page 40

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

5. In the Dispatch Messages section, select “SMOKE”:

Page 41

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

6. In the APU Dispatch Messages, select “SMOKE L AVNCS DET”:

Page 42

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: Focus on MEL Use

7. Read the Aircraft Status:

Page 43

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Scenario 3: General Workflow


Cockpit Preparation::
SMOKE L AVNCS DET FAULT
SMOKE L AVNCS DET FAULT
> SMOKE L AVNCS DET
Apply ECAM procedure (pilot)

MEL check (pilot) AOG


Press the DISPCH button (pilot)
(no dispatch)

Change both
smoke detectors
(Maintenance)

Aircraft release
(Maintenance)

Page 44

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Contents

1 Brake Failure after Landing

2 APU Failure after Pushback

3 Smoke Detection Failure during Cockpit Preparation

4 Key Points

Page 45

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

Key Points

Enter the MEL with the Dispatch Message (not the ECAM alert)

In the Dispatch Messages Section, the Aircraft Status can provide tips
to mitigate operational effects

A Dispatch Message may be NO-GO

Connectivity between the MEL and performance applications.

Page 46

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.


Flight Ops Working Together - Use of A350 MEL for Dispatch

© Airbus S.A.S. All rights reserved. Confidential and proprietary document. This document and all information contained herein is the sole property of AIRBUS. No intellectual property rights are granted by the delivery of this document or the disclosure of
its content. This document shall not be reproduced or disclosed to a third party without the express written consent of AIRBUS S.A.S. This document and its content shall not be used for any purpose other than that for which it is supplied. The statements
made herein do not constitute an offer. They are based on the mentioned assumptions and are expressed in good faith. Where the supporting grounds for these statements are not shown, AIRBUS S.A.S. will be pleased to explain the basis thereof.
AIRBUS, its logo, A300, A310, A318, A319, A320, A321, A330, A340, A350, A380, A400M are registered trademarks.

Page 47

© AIRBUS S.A.S. All rights reserved. Confidential and proprietary document.

You might also like