01.12.2012 Aufrufe

PAN – PAN – PAN Emirates und Co. Fluglärm in Frankfurt Prof. Dr ...

PAN – PAN – PAN Emirates und Co. Fluglärm in Frankfurt Prof. Dr ...

PAN – PAN – PAN Emirates und Co. Fluglärm in Frankfurt Prof. Dr ...

MEHR ANZEIGEN
WENIGER ANZEIGEN

Sie wollen auch ein ePaper? Erhöhen Sie die Reichweite Ihrer Titel.

YUMPU macht aus Druck-PDFs automatisch weboptimierte ePaper, die Google liebt.

✈ Possible collision scenario<br />

at hold<strong>in</strong>g po<strong>in</strong>t<br />

Graphics: CIAIAC<br />

✈ Map<br />

Graphics: Google Earth<br />

Spa<strong>in</strong>’s CIAIAC released their report <strong>in</strong> their bullet<strong>in</strong> 02/2012,<br />

page 212 and follow<strong>in</strong>g, conclud<strong>in</strong>g:<br />

The <strong>in</strong>cident resulted from the crew of the Ryanair B737’s<br />

misjudg<strong>in</strong>g of the distances as it passed beh<strong>in</strong>d the B767,<br />

which was stopped at the G3 position of the runway 25L<br />

hold<strong>in</strong>g po<strong>in</strong>t.<br />

Assign<strong>in</strong>g position G3 to an aircraft with a long fuselage,<br />

such as a B767-300, and the position of said aircraft, relatively<br />

far away from the hold<strong>in</strong>g po<strong>in</strong>t mark<strong>in</strong>g, contributed<br />

to the <strong>in</strong>cident.<br />

The defi ciencies <strong>in</strong> the communications between the cab<strong>in</strong><br />

and fl ight crews on the B737 resulted <strong>in</strong> the collision go<strong>in</strong>g<br />

unnoticed and <strong>in</strong> both aircraft cont<strong>in</strong>u<strong>in</strong>g with their fl ights<br />

without an assessment of the damage produced.<br />

The CIAIAC reported the American Airl<strong>in</strong>es Boe<strong>in</strong>g 767-300<br />

was positioned on hold<strong>in</strong>g po<strong>in</strong>t G3 (the most western hold<strong>in</strong>g<br />

po<strong>in</strong>t) about 16 meters short of the hold short l<strong>in</strong>e stat<strong>in</strong>g:<br />

“From the pilot’s po<strong>in</strong>t of view, the ma<strong>in</strong> concern is not<br />

to <strong>in</strong>terfere with aircraft circulat<strong>in</strong>g on the runway at any<br />

time. A pilot will therefore give priority to this consideration<br />

over any potential problems <strong>in</strong>volv<strong>in</strong>g tail<strong>in</strong>g aircraft, and<br />

will keep the hold<strong>in</strong>g po<strong>in</strong>t mark<strong>in</strong>g well <strong>in</strong> sight and ahead<br />

of the nose of the airplane, barr<strong>in</strong>g any <strong>in</strong>struction to the<br />

contrary from ATC.”<br />

The CIAIAC reported neither of the Boe<strong>in</strong>g 767-300 crew got<br />

aware of the contact between the aircraft, especially they did<br />

not notice any movement that would by typical for a collision.<br />

When the B738 crew refused to cont<strong>in</strong>ue to taxi before<br />

the B763 had moved, they moved about 10 feet forward.<br />

Für Sie gelesen<br />

The CIAIAC reported the B738 capta<strong>in</strong> had asked the fi rst offi<br />

cer to verify separation to the Boe<strong>in</strong>g 767-300 as they were<br />

pass<strong>in</strong>g along. She steered the aircraft about half a meter to<br />

the left of the taxiway center l<strong>in</strong>e to ensure separation. The<br />

fi rst offi cer <strong>in</strong>dicated there was no concern as the w<strong>in</strong>g-tip<br />

passed the tail cone of the 767 however he asked to stop<br />

immediately when the w<strong>in</strong>g tip approached the end of the<br />

left hand horizontal stabilizer. The capta<strong>in</strong> rose out of her<br />

seat to assess the situation and was surprised about the<br />

short distance, the fi rst offi cer assured however the aircraft<br />

had not made contact. Shortly thereafter the <strong>in</strong>tercom rang<br />

(s<strong>in</strong>gle chime only, company policy requir<strong>in</strong>g three chimes <strong>in</strong><br />

case of a serious problem) and the fl ight attendant said “for<br />

your <strong>in</strong>formation” leav<strong>in</strong>g the capta<strong>in</strong> <strong>und</strong>er the impression<br />

only one passenger had reported contact between the aircraft<br />

<strong>–</strong> she cont<strong>in</strong>ued to say <strong>in</strong> the <strong>in</strong>terview that had she<br />

been aware of multiple passengers observ<strong>in</strong>g the collision<br />

she would have reacted differently.<br />

After return<strong>in</strong>g the Barcelona both fl ight crew believed the<br />

contact must have happened before stopp<strong>in</strong>g.<br />

The CIAIAC released one safety recommendation to Spa<strong>in</strong>’s<br />

AENA to reassess the taxi limitations on taxiway K and hold<strong>in</strong>g<br />

po<strong>in</strong>ts G.<br />

The CIAIAC also released one safety recommendation to<br />

Ryanair to “reassess those aspects of its tra<strong>in</strong><strong>in</strong>g program<br />

<strong>in</strong>volv<strong>in</strong>g fl ight and cab<strong>in</strong> crew communications and address<br />

the defi ciencies noted, if any. Special emphasis should be<br />

placed on the benefi ts to safety that stem from the effective<br />

transmission of <strong>in</strong>formation from the passenger cab<strong>in</strong> to the<br />

fl ight deck.”<br />

der fl ugleiter 2012/04<br />

49

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!