PPRuNe Forums - View Single Post - Incident at Heathrow
View Single Post
Old 4th Jun 2013, 09:25
  #907 (permalink)  
NigelOnDraft
 
Join Date: Jan 2001
Location: UK
Posts: 2,044
Likes: 0
Received 0 Likes on 0 Posts
I disagree about the "both engines" aspect in this case.

It is valid where the work, if not carried out correctly, would lead to loss of both engines e.g. the BMI 734 incident.

Until the recent BA event, no A320 series cowl loss had seriously risked an engine AFAIK? If the BA event had followed that pattern, there was little more thought involved for the crew in returning with 1 engine sans cowls, and 2.

This incident alters that aspect, as noted by the AAIB, in that the RH Engine damage / fire was something not yet seen. We shall see what recommendations are made, and cruically which are followed up. I am "optimistic" that the severity of certain aspects of this event might see some "mitigations" or "traps" put in place. It is fine for the MS Simmers just to be interested in HF and "blame", but apart from appeasing their smugness, it does little to enhance safety in the future. 32+ events suggests we need to do more than rely on HF

This actually (if confirmed) seems to show that time pressure is a main contributing factor
As noted, so long as the Pax are willing to regularly see 15+min delays. With short Turnrounds, the walkround is often performed before the refueller even arrives / baggage holds opened / engineering taks etc. If we find something requiring rectification (not infrequent) this is lttle scope to go out and reinspect. We have to give engineers 20+min notice*, they often rectify during Pax boarding, and the paperwork is signed by the engineer, then Capt and as the Engineer then leaves the door closes with pushback required within 3 minutes of that. Else we get the "blame" for the delay (which is all the airlines and Pax / compensation are really interested in it seems).

It is our job to resist these commercial / admin "trivialities" over safety. But just to be clear, it is not "safety comes first". It is always a "risk balance", and human nature means that balance will be judged differently by different people.


* PS and the first concern of the engineers is then whether they, or we, will cop the delay code.
NigelOnDraft is offline