Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

A320 declares "Emergency" because of autobrake fult

Tech Log The very best in practical technical discussion on the web

A320 declares "Emergency" because of autobrake fult

Old 9th Nov 2018, 19:17
  #21 (permalink)  
 
Join Date: Sep 2007
Location: Canada
Posts: 90
Originally Posted by msbbarratt View Post
If they had carried on with the original approach, could they not have simply turned it into a touch and go if they found the brakes to be inoperative when they pushed the pedals?

I suppose there was a chance that's the brakes could kinda half work, enough to prevent returning to flight. I can see an argument for not touching the ground so that you can get the airport prepped for a tricky landing after a second approach.
An intentional touch and go is not a manoeuvre that is allowed. They would have been well outside of SOPs had they have done so. Go-arounds after touchdown are taught by some carriers, but taught as an emergency procedure only.
Commander Taco is offline  
Old 10th Nov 2018, 03:14
  #22 (permalink)  
 
Join Date: Mar 2006
Location: USA
Posts: 2,101
Originally Posted by Commander Taco View Post


An intentional touch and go is not a manoeuvre that is allowed. They would have been well outside of SOPs had they have done so. Go-arounds after touchdown are taught by some carriers, but taught as an emergency procedure only.
Devil's advocate. The crew declared an emergency. If they determined that the safest course of action is a touch and go, why not? It's not inherently dangerous.

GA after touchdown isn't an emergency procedure at my shop. We practice it every time we're in the sim.
Check Airman is offline  
Old 10th Nov 2018, 17:22
  #23 (permalink)  
 
Join Date: Feb 2017
Location: Isla Grande
Posts: 965
Many moons ago on a 737NG of a major EU carrier starting take off roll in VMC/daylight , the very junior FO yelled "STOP".

CPT aborted.

CPT: What was wrong?
FO: We had the FD OFF.
gearlever is offline  
Old 12th Nov 2018, 17:02
  #24 (permalink)  
 
Join Date: Aug 2012
Location: N . Daarset
Age: 68
Posts: 218
Airborne at AMS with a 30 min leg to LHR in a 75 . 'Oh look' , quoth I a yellow a/brake caution [ details now fzzy ] . F/O flying ' man brakes then ' .
I get the QRH out , quite a read thru' ... ' better slow down , this'll take a while ' .
End result , could take in excess of 3200m landing roll ! Didn't really need that , but firetrucks raced after us on roll out ; and the only way to get them out and following is a Mayday / Pan .
We both felt a bit silly ........ However .......
.....

It was the f/o's sector so he explained to pax !

rgds condor .
condor17 is offline  
Old 18th Nov 2018, 05:23
  #25 (permalink)  
 
Join Date: Jun 2007
Location: Wanderlust
Posts: 2,922
a yellow a/brake caution [ details now fzzy ] .
If it is Airbus can you explain this? Because no A/B on yellow it is on green.
vilas is offline  
Old 18th Nov 2018, 08:30
  #26 (permalink)  

Only half a speed-brake
 
Join Date: Apr 2003
Location: Commuting home
Age: 43
Posts: 3,295
Wartime story from 757?
FlightDetent is online now  
Old 14th Oct 2019, 03:04
  #27 (permalink)  
 
Join Date: Nov 2004
Location: Here, there, and everywhere
Posts: 715
Could someone explain what happened in this A320 incident. The crew was faulted for improper braking.

http://dgca.gov.in/accident/reports/incident/VT-ESL.pdf
punkalouver is offline  
Old 14th Oct 2019, 06:05
  #28 (permalink)  
 
Join Date: Jun 2007
Location: Wanderlust
Posts: 2,922
Originally Posted by punkalouver View Post
Could someone explain what happened in this A320 incident. The crew was faulted for improper braking.

http://dgca.gov.in/accident/reports/incident/VT-ESL.pdf
Although the investigation report doesn't exactly cover itself with glory what is absolutely clear is for a performance limited airfield the experienced PIC's performance was far below the required. Below 180 ft RA the aircraft was allowed to deviate to 3/4 below GS and then was flown back to GS. So obviously the reduced ROD was going to shift the touchdown point and the very high flare at 55ft aggravated the problem. He continued to float at 2ft and instead of pushing the stick forward he is pleading the aircraft to touch down. On approach to RW limited airport any problems with braking system a goaround and proper assessment of threat and plan is required. The way he landed he had no chance to stop with ASkid failure. However he seems to have been faulted because the normal brake was available and there was no need to switch off antiskid. All he had to do was touch down at normal point and max manual braking.
vilas is offline  
Old 14th Oct 2019, 14:02
  #29 (permalink)  
 
Join Date: Nov 2004
Location: Here, there, and everywhere
Posts: 715
Originally Posted by vilas View Post
However he seems to have been faulted because the normal brake was available and there was no need to switch off antiskid.All he had to do was touch down at normal point and max manual braking.
But the report makes it sound like the alternate brakes were being used but not slowing the aircraft down very much.

"At 064506 UTC, • Max brake pedals deflection was reached after 08 sec. • The deceleration progressively increased and stabilized between +0.2g and +0.25g. • The ground speed decreased from 145kt to 125kt. As there was ECAM message of “Break Auto Break Fault” during landing, aircraft was on alternate braking, brake pedal order commanded alternate braking pressures. However the deceleration experienced by the aircraft remained low (between +0.2 and +0.25g) despite max brake pedal application.

From 064506 UTC after touchdown to 064517 UTC, the brake pedals were maintained to full deflection while aircraft deceleration remained constant. As a consequence, the ground speed continued to decrease regularly from 125kt to 76kt.

At 064517 UTC, the anti-skid was turned off as per Abnormal and Emergency procedures. Aircraft continued to decelerate. "
punkalouver is offline  
Old 14th Oct 2019, 16:31
  #30 (permalink)  
 
Join Date: Jun 2007
Location: Wanderlust
Posts: 2,922
Originally Posted by punkalouver View Post
But the report makes it sound like the alternate brakes were being used but not slowing the aircraft down very much.

"At 064506 UTC, • Max brake pedals deflection was reached after 08 sec. • The deceleration progressively increased and stabilized between +0.2g and +0.25g. • The ground speed decreased from 145kt to 125kt. As there was ECAM message of “Break Auto Break Fault” during landing, aircraft was on alternate braking, brake pedal order commanded alternate braking pressures. However the deceleration experienced by the aircraft remained low (between +0.2 and +0.25g) despite max brake pedal application.

From 064506 UTC after touchdown to 064517 UTC, the brake pedals were maintained to full deflection while aircraft deceleration remained constant. As a consequence, the ground speed continued to decrease regularly from 125kt to 76kt.

At 064517 UTC, the anti-skid was turned off as per Abnormal and Emergency procedures. Aircraft continued to decelerate. "
It's evident that inquiry officer either didn't know much about A320 braking system or English. There's evidence of both. With Brakes Auto Brake fault the system doesn't change to alternate. It remains on Normal brake (green). but manual peddle braking is required. With Brake Normal brake Fault it will automatically change to alternate yellow system brake with anti skid. You just apply max peddle braking. But if it doesn't change to yellow then you have to manually select Antiskid NWS off. Then you get braking from yellow system without ASkid where you must apply only 1000psi to prevent tire burst. Here my guess is pilot landed deep ans the runway end was appearing followed loss of braking procedure which was incorrect.
vilas is offline  
Old 14th Oct 2019, 22:49
  #31 (permalink)  
 
Join Date: Nov 2004
Location: Here, there, and everywhere
Posts: 715
The report says that the Autobrake fault was due to a faulty servo valve for one of the 8 main wheels(Indian Airbus): "During approach when the landing gear was selected down “Brake Auto Brake Fault” ECAM warning message was triggered at 0642 UTC with failure message of “BRK NORM SERVOVLV7 (80GG)”.

Later in the report, it states that braking action was reduced due to the loss of the servo valve: "High pitch angle at touchdown, prolonged flare and low response of braking action due to the failure of servo valve along with the improper application of emergency checklist resulted into increase in the landing distance and runway overrun at Jammu airport."

One would think that losing only one of seven servo valves would hardly be noticable for the difference in braking capability.
punkalouver is offline  
Old 16th Oct 2019, 16:58
  #32 (permalink)  
 
Join Date: Jul 2016
Location: Broughton, UK
Posts: 114
What is so wrong with calling the trucks out. They spend most of their time thinking up reasonable practice scenarios, that they would welcome any event that is mildly out of the ordinary.
.
scifi is offline  
Old 16th Oct 2019, 20:10
  #33 (permalink)  
 
Join Date: Sep 2003
Location: away from home
Age: 60
Posts: 771
Break Auto Brake or Brake Auto Break Fault?
I think I´ll give the Airbus class a miss...
oceancrosser is online now  
Old 17th Oct 2019, 02:42
  #34 (permalink)  
 
Join Date: Jun 2007
Location: Wanderlust
Posts: 2,922
Originally Posted by oceancrosser View Post
Break Auto Brake or Brake Auto Break Fault?
I think I´ll give the Airbus class a miss...
It is Brake the system, Auto Brake fault is failure.
unless you are having fun with spelling
vilas is offline  

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off


Thread Tools
Search this Thread

Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service - Do Not Sell My Personal Information -

Copyright © 2021 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.