domingo, 3 de noviembre de 2013
Adjuntamos artículo de SKYbrary sobre un incidente que sufrió un avión en su aproximación al Aeropuerto de Madrid-Barajas.
E145, en route, north east of Madrid Spain, 2011 (CFIT LB HF AGC)
Categories: Accidents and Incidents
On 4 August 2011, an Embraer ERJ 145 being operated by Luxair on a scheduled passenger flight from Luxembourg to Madrid in day VMC when its crew read back a clearance to descend to 10,000 feet as one to descend to 5000 feet, an altitude below both the STAR minimum altitude and the MRVA. The controller did not notice the read back error and when the aircraft was then transferred to the next sector, the controller there also did not notice the error when the crew advised their clearance on first call. An EGPWS ‘PULL UP’ Hard Warning was subsequently activated and recovery followed. There were no injuries to the 47 occupants during this manoeuvre.
An Investigation was carried out by the Spanish Investigation Agency CIAIAC. It was noted that the First Officer had been acting as PF at the time of the Incident and that both pilots were experienced on the aircraft type and familiar with Madrid.
It was found that when the aircraft was cleared to descend to 10,000 feet by the controller in the ACC East Director position using the phraseology “descend to ten thousand feet”, spoken clearly and enunciated properly, the aircraft crew had wrongly read back a clearance to descend to 5000 feet which was not noticed by the controller concerned and was also below the altitude for the STAR being flown (10,000 feet), the MSA on the STAR chart (9500 feet) and the applicable MRVA. Prior to the aircraft reaching 10,000 feet, there was then a change of controller in position with the relevant strip showing a clearance to 10,000 ft. The aircraft was then transferred to the Initial Approach Director on the assumption that it was descending in accordance with the clearance issued. The receiving controller, despite advising the aircraft of “radar contact”, failed to notice the wrong cleared altitude when 5000 feet was given as well as not noticing that the aircraft was below the MRVA. He advised the Investigation that “the aircraft was transferred to him while supposedly descending through 10,000 ft and that there must have been a miscommunication since he asked the (East Sector) controller if he had cleared the aircraft to descend, to which he replied no”. The Investigation noted that “the information obtained from the (East Director) executive controllers and the planning controllers did not yield anything of relevance to the investigation of the event”.
Recorded data showed that when the aircraft was transferred to the Initial Approach controller, it was already below 8000 feet and the advice to the crew of “radar contact” was given with the aircraft descending through an altitude of 7349 feet. The aircraft EGPWS was triggered a little over half a minute later with a Terrain Alert followed about 20 seconds later by a Hard Warning “Terrain Pull Up” to which the crew responded by disconnecting the AP, increased thrust and climbing. The minimum altitude reached by the aircraft was found to have been 6290 ft. The Warning and the response to it was not reported to ATC until responding shortly afterwards to a second transmission to turn right for traffic separation when after acknowledging the instructed radar heading, the crew added “and we’ll maintain seven thousand feet due to mountain”. Subsequently, ATC instructed the aircraft to climb to 10,000 feet.
The actual altitude of the aircraft in relation to altitude clearance restrictions and key points during the event are shown in the diagram below. It can be seen that the aircraft was below the minimum altitude for the STAR for four minutes and below the MRVA for three minutes. The Investigation does not comment on the terrain clearance actually achieved during the event.
Flight profile of the aircraft during the incident (Reproduced from the Final Report)
The Investigation did note that:
• Each of the controller positions involved was manned by an “executive controller” and a “planning controller” but that “the functions of the planning controller are not documented by the service provider (AENA), meaning the exact tasks involved in the planning controller’s job are unknown.
• The radar control system installed at the ACC involved was capable of generating MSAW alerts but that according to AENA “this function is not enabled at any of Spain’s control centres because the relevant operational validation to determine which operating parameters are needed for said alert has not been performed yet”.
The formal statement of Cause made by the Investigation reads:
“The incident occurred because the aircraft descended below the minimum standard terminal arrival route, minimum radar vectoring and minimum sector altitudes. The crew, which was obligated to maintain separation with terrain and know that the minimum altitude specified by the arrival procedure was 10,000 ft, descended below said altitude without confirming with ATC whether the clearance given was correct.
The (ACC) sector controller used improper phraseology and cleared the aircraft to descend to 10,000 ft. The crew acknowledged descending to 5,000 ft and the controller did not correct the faulty readback”.
It was also noted that contributing to the incident was “the fact that (the controllers involved) noticed that the aircraft had descended below the minimum altitude in the procedure and below the minimum radar vectoring altitude. The (Initial Approach) controller only realised this fact after being informed by the crew when the aircraft’s EGPWS alerted them and they started to climb.”
Three Safety Recommendations were made as a result of the Investigation as follows:
• that AENA evaluate the incorporation of topics involving the use of standard phraseology and the recommendations issued by EUROCONTROL, as well as information concerning faulty acknowledgments and its consequences, into the continuing training programs for control personnel so as to raise controller awareness regarding the importance of these aspects. [REC 01/13]
• that AENA establish the measures needed to implement the altitude alert function in (the radar control system), at least in those posts where aircraft separation with terrain could be critical (as is the case of Madrid-Barajas when in a south configuration). [REC 02/13]
• that AENA issue a document where the operation procedure be described and the tasks of the planner controllers be defined. [REC 03/13]
It was noted that as Luxair had decided during the Investigation to "revise its procedures, to improve its training and to present this incident internally to its crews as a case study to remind them of the importance of increasing their awareness of altitude restrictions and limitations” a Safety Recommendation to the Operator was not necessary. The Final Report (in Spanish) was approved for publication on 30 January 2013 and subsequently made available in English translation: Final Report (in English).
Related articles and further readings were not included but are available in the skybrary article.
El informe publicado por la CIAIAC, con fecha de aprobación del 30 de enero de 2013, se puede consultar en el siguiente enlace: Informe técnico.
La aeronave, modelo Embraer 145, con matrícula LX-LGX y distintivo de llamada LGL 3837, realizaba un vuelo entre el Aeropuerto Internacional de Luxemburgo (ELLX) y el Aeropuerto de Madrid/Barajas (LEMD) el día 04 de agosto de 2011. A las 16:57:55 h la aeronave se encontraba en las proximidades del aeropuerto de Madrid/Barajas, en descenso.
Las condiciones meteorológicas informadas por el METAR de las 17:00 h indicaba que la intensidad media del viento era de 8 kt y la dirección 210°, variable entre 190° y 260°, con ráfagas de hasta 20 kt. Según el informe proporcionado por la AEMET la visibilidad era de 10 km o más, sin fenómenos de tiempo significativo y sin nubes de importancia para las operaciones.
Según se indica en el informe el incidente se produjo porque la aeronave descendió por debajo de las altitudes mínimas del procedimiento de llegada normalizada, mínima de Guía Vectorial radar y mínima de sector, como consecuencia de que la tripulación, que debía mantener su separación con el terreno y conocer que la altitud mínima marcada por el procedimiento era 10.000 ft, descendió por debajo de ésta, sin confirmar con ATC si la autorización proporcionada era correcta. El controlador de Sector RES, utilizando una fraseología inadecuada, había autorizado a la aeronave a descender a 10.000 ft, ésta colacionó que descendía a 5.000 ft y el controlador no corrigió esta colación incorrecta. Además, contribuyó al incidente el hecho de que los controladores de Sector RES y Sector AIS tampoco detectaron que la aeronave había descendido por debajo de la altitud mínima del procedimiento y la de Guía Vectorial radar. El controlador de Sector AIS fue consciente de este hecho tras ser informado por la tripulación, después de que se activara el EGPWS de la aeronave y comenzaran el ascenso.
Sirva este incidente no sólo para modificar procedimientos, sino para valorar lo importante que es disponer de controladores bien formados, bien descansados y sin presiones externas (léase políticas, laborales, mediáticas, etc.), que puedan inducirles a cometer fallos. Los responsables políticos y sus jefes de AENA tienen la obligación de proporcionarles el adecuado ambiente de trabajo, para que puedan desempeñar sus funciones con las garantías debidas, en lugar de arrojarlos al circo mediático en el que llevan lidiando desde hace varios años.