Landed short, Serious incident occurring January 20th, 1999 at Frankfurt/Main to a Boeing B

Similar documents
AIRPROX incident between a Cessna 650, LN-NLD, and Airbus A320, HS- IPZ, approximately 20 NM north of Oslo.

Investigation Report

Date: 5 November East of Frankfurt/Main

Investigation Report. Identification. Factual information. German Federal Bureau of Aircraft Accidents Investigation. TX002-0/07 September 2008

Interim Report. Identification. Factual Information. History of the Flight. Bundesstelle für Flugunfalluntersuchung.

Investigation Report. Bundesstelle für Flugunfalluntersuchung. Identification. Factual information

Pitch control problems, Boeing , March 27, 2001

EFIS failure, Incident on board aircraft SE-LGX in the air space north-east of Stockholm/Arlanda Airport, AB county, 13 November 2002

Micro-summary: A failure of electronic flight instrumentation on this BAe-146 results in an altitude bust.

Investigation Report

Date: 20 October Manufacturer / Model: The Boeing Company / B Minor damage to aircraft

Nosewheel stuck 90, Airbus A320, N536JB, September 21, 2005

Investigation Report

FINAL REPORT BOEING B777, REGISTRATION 9V-SWH LOSS OF SEPARATION EVENT 3 JULY 2014

USE OF RADAR IN THE APPROACH CONTROL SERVICE

Runway incursion, Incident at Vaasa airport, Finland, on 15 December 1999

Investigation Report

Tire failure and systems damage on takeoff, Airbus A , G-JDFW, 10 July 1996

Aircraft Accident Investigation Bureau of Myanmar

LOW VISIBILITY OPERATION

GENERAL INFORMATION Aircraft #1 Aircraft #2

SECURITY OVERSIGHT AGENCY June 2017 ALL WEATHER (CAT II, CAT III AND LOW VISIBILITY) OPERATIONS

ILS APPROACH WITH B737/A320

Loss of separation west of Helsinki-Vantaa airport on

AIR LAW AND ATC PROCEDURES

Near-miss between a DHC-8-311, LN-WFR, and Boeing

In-Flight Fire/Emergency Landing, Federal Express Flight 1406 Douglas DC-10-10, N68055, Newburgh, New York September 5, 1996

AIRCRAFT INCIDENT REPORT

REPORT SERIOUS INCIDENT

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AERODROME OPERATING MINIMA

Fast level off produces broken leg, Boeing , June 2, 2002

VFR GENERAL AVIATION FLIGHT OPERATION

Runway overrun, Serious incident occurring January 19, 2004 at Frankfurt-Hahn involving a DC-10-40F

Interim Report. Identification. Bundesstelle für Flugunfalluntersuchung. Date: 13 July French Airspace; 33 NM west of Grostenquin (GTQ)-VOR

Flight Safety Foundation. Approach-and-landing Accident Reduction. Tool Kit. FSF ALAR Briefing Note 1.6 Approach Briefing

All-Weather Operations Training Programme

Air Accident Investigation Unit Ireland FACTUAL REPORT

Wing strike on landing, Delta Air Lines Boeing N8873Z, Calgary International Airport, Alberta, 10 March 1999

Flight attendant fall off Boeing , May 4, 1997

AIRCRAFT INCIDENT REPORT

Chapter 6. Airports Authority of India Manual of Air Traffic Services Part 1

BULLETIN Serious incident involving BEECH 33 E33A G-GMCT

REPORT IN-011/2012 DATA SUMMARY

London City Airport. 43 years

Turbulence injury, Boeing , G-BNLS, April 1, 2002

Appendix F ICAO MODEL RUNWAY INCURSION INITIAL REPORT FORM

Date: 12 January Two pilots and two passengers fatally injured. Open wire, forest and crop damages

AA AIRCRAFT ACCIDENT INVESTIGATION REPORT UNITED AIRLINES N U A

Investigation Report. Bundesstelle für Flugunfalluntersuchung. Identification. Factual Information

Instrument failure, Airbus A , G-EUOB

AVIATION INVESTIGATION REPORT A02P0290 GEAR-UP LANDING

AVIATION INVESTIGATION REPORT A00Q0116 RISK OF COLLISION

Nose gear-up landing, Boeing C, February 22, 1996

Investigation Report

Contents. Subpart A General 91.1 Purpose... 7

Collision with edge lights on takeoff, Serious incident on March 5, 2002 at Dresden Airport involving an Aerospatiale ATR i.

INTERNATIONAL FEDERATION OF AIR TRAFFIC CONTROLLERS ASSOCIATIONS. Agenda Item: B.5.12 IFATCA 09 WP No. 94

Uncontained engine failure, Boeing , N107BV, August 2, 1993

Tailstrike on landing, Boeing , June 5, 2001

Air Accident Investigation Unit Ireland SYNOPTIC REPORT

TANZANIA CIVIL AVIATION AUTHORITY AIR NAVIGATION SERVICES INSPECTORATE. Title: CONSTRUCTION OF VISUAL AND INSTRUMENT FLIGHT PROCEDURES

AIRPROX REPORT No PART A: SUMMARY OF INFORMATION REPORTED TO UKAB

Severe icing, Serious incident occurring January 28, 2000 near Berlin- Tegel, involving an Aerospatiale-Alenia ATR

Injury to worker while opening door of pressurized airplane, Douglas DC F, March 6, 1998

Advisory Circular. Regulations for Terrain Awareness Warning System

CHAPTER 7 AEROPLANE COMMUNICATION AND NAVIGATION EQUIPMENT

MINISTRY OF INFRASTRUCTURE STATE COMMISSION ON AIRCRAFT ACCIDENT INVESTIGATION FINAL REPORT. Serious Incident No: 518/07

Flight control system failure, Airbus A320 EI-TLI, on

ICAO Big Data Project ADS-B Data as a source for analytical solutions for traffic behaviour in airspace

OCTOBER 2011 DGCA SAFETY BULLETIN. Informative Reading material

GOVERNMENT OF INDIA INVESTIGATION REPORT

CFIT-Procedure Design Considerations. Use of VNAV on Conventional. Non-Precision Approach Procedures

DUTCH SAFETY BOARD. Threshold lights damaged during landing

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

Any queries about the content of the attached document should be addressed to: ICAO EUR/NAT Office:

Cracked main landing gear cylinder, Douglas DC-8-61, July 4, 1997

Assault on flight attendant and self-evacuation, Boeing , May 20, 2000

5 Cockpit Crew, 6 Cabin Attendants. Shannon Airport, Co. Clare, Ireland

CIVIL AVIATION AUTHORITY, PAKISTAN OPERATIONAL CONTROL SYSTEMS CONTENTS

OVERSEAS TERRITORIES AVIATION REQUIREMENTS (OTARs)

Tailstrike on landing, Boeing APF, December 25, 1994

AI AIRCRAFT SERIOUS INCIDENT INVESTIGATION REPORT THAI AIRASIA X CO., LTD. H S X T C CHINA AIRLINES B

Air Accident Investigation Unit Ireland. FACTUAL REPORT ACCIDENT Colibri MB-2, EI-EWZ ILAS Airfield, Taghmon, Co. Wexford

INTERNATIONAL CIVIL AVIATION ORGANIZATION FIRST MEETING OF DIRECTORS OF CIVIL AVIATION OF THE CARIBBEAN REGION (CAR/DCA/1)

VFR PHRASEOLOGY. The word IMMEDIATELY should only be used when immediate action is required for safety reasons.

CLASS D CONTROLLED AIRSPACE GUIDE

F I N A L R E P O R T ON SERIOUS INCIDENT OF THE AIRCRAFT SR-20, REGISTRATION D-ELLT, WHICH OCCURED ON MAY , AT ZADAR AIRPORT

Research on Controlled Flight Into Terrain Risk Analysis Based on Bow-tie Model and WQAR Data

July 2008 COMPANY INDOCTRINATION TRAINING 1.0 PURPOSE

Date: 29 Jun 2018 Time: 1502Z Position: 5325N 00312W Location: 5nm NW Liverpool Airport

AIRCRAFT ACCIDENT REPORT AND EXECUTIVE SUMMARY

AOP 11 Low Visibility Procedures (LVP s) (Aerodrome Operating Procedure)

Flight Operations Briefing Notes

Time: 1111Z Position: 5049N 00016W Location: 1nm SE Brighton City Airport

OPERATIONS MANUAL PART A

Investigation Report

Air Navigation (General) Regulations (as amended and as applied to the Isle of Man)

SERIOUS INCIDENT. Aircraft Type and Registration: Boeing 737-8F2, TC-JKF. No & Type of Engines: 2 CFM 56-7B22 turbofan engines

TRAFFIC ALERT AND COLLISION AVOIDANCE SYSTEM (TCAS II)

Transcription:

Landed short, Serious incident occurring January 20th, 1999 at Frankfurt/Main to a Boeing B747-400 Micro-summary: This Boeing 747-400 touched down on the underrun area before the main runway, damaging the main tires and resulting in a go-around in diminishing visibility. Event Date: 1999-01-20 at 1639 UTC Investigative Body: Federal Bureau of Aircraft Accidents Investigation (BFU), Germany Investigative Body's Web Site: http://www.bfu-web.de/ Note: Reprinted by kind permission of the BFU. Cautions: 1. Accident reports can be and sometimes are revised. Be sure to consult the investigative agency for the latest version before basing anything significant on content (e.g., thesis, research, etc). 2. Readers are advised that each report is a glimpse of events at specific points in time. While broad themes permeate the causal events leading up to crashes, and we can learn from those, the specific regulatory and technological environments can and do change. Your company's flight operations manual is the final authority as to the safe operation of your aircraft! 3. Reports may or may not represent reality. Many many non-scientific factors go into an investigation, including the magnitude of the event, the experience of the investigator, the political climate, relationship with the regulatory authority, technological and recovery capabilities, etc. It is recommended that the reader review all reports analytically. Even a "bad" report can be a very useful launching point for learning. 4. Contact us before reproducing or redistributing a report from this anthology. Individual countries have very differing views on copyright! We can advise you on the steps to follow. Aircraft Accident Reports on DVD, Copyright 2006 by Flight Simulation Systems, LLC All rights reserved. www.fss.aero

German Federal Bureau of Aircraft Accidents Investigation Report Translation of the German Investigation Report. The sole permissible specimen in law is the German Report EX002-0/99 September 1999 Factual Information Classification: Serious Incident Date of event: 20 th January, 1999 Location: Aircraft: Airport Frankfurt/Main Civil Jet Aircraft Manufacturer / Type: Boeing B747-400 Injuries to persons: Damage to aircraft: Third party damage: History of the Flight: none severe Airport Equipment A B747-400 arriving from Delhi, with 311 passengers and 25 crewmembers on board approached runway 25 L at Frankfurt Airport at approximately 16:35 UTC. The approach to runway 25 L was conducted with the intention to perform a manual landing under CAT I conditions. This intention resulted from the ATIS (Automatic Terminal Information Service) of 16:20 UTC which was copied by the crew before starting the approach. The Meteorological Aerodrome Report contained in this ATIS indicated a visibility of 2 500 m and few clouds in 300 ft. Frankfurt Approach Control vectored the aircraft to a 9 NM localizer intercept for runway 25 L. The glideslope was captured just before the outer marker (FR) at approximately 1 400 ft GND, because the average sinkrate of 1 200 ft/min from Fl 110 to 4 000 ft respective 3 000 ft was too low for the remaining distance to the glideslope. When reaching an altitude of 3 000 the autoflight system was switched off and the airplane flown manually. Apparently the crew did not realise the rapid deterioration of the visibility during the approach caused by fog-banks drifting in from the southwest. The additional special met report at 16:35 UTC indicating a decrease in visibility between 800 m RVR and 400 m RVR did not come to the knowledge of the crew. The landing clearance was issued before passing the outer marker (FR) at 16:37 UTC including the current RVR-readings for runway 25 L - A 300 m, B 550 m, C 375 m - and the advice that still CAT I is in process. During the intermediate approach the crew dealt with a minor hydraulic pump malfunction in the hydraulic system number 4. At approximately 800 ft GND the flaps were set from 25 0 to 30 0, the aircraft deviated about 100 ft above the glideslope. The sinkrate increased up to 1 450 ft/min and the aircraft went below glideslope at 400 ft GND. According to the flight crew the approach lights were sighted at a height of 300 ft. Because of the high sinkrate the GPWS sounded 8 times SINKRATE, SINKRATE, SINKKRATE... and shortly after 16:39 UTC the aircraft touched down unintentionally, approximately 1 000 m prior to the touchdown zone on the hard surface of the old runway in front of runway 25 L. The pilot-in-command immediately initiated a goaround. Meanwhile the RVR decreased so that at 16:50 UTC CAT II and from 16:54 UTC CAT III was in force. The second landing was performed at 16:58 UTC on runway 25 R as an automatic landing under CAT III conditions. Some of the previously damaged main landing gear tires started to burn, but were quickly extinguished by the fire brigade standing by. The fire

EX002-0/99 Seite 2 crew had already been alerted by the tower controller because of an explosion-like sound at the time of the go-around. Weather At the time of the approach the weather was characterised by low visibility, resulting in operational limitations for approaches and landings. According to the tower s daily report the airport changed from Category I, permitting manually flown approaches, to Category III, where automatic landings are mandatory. The current airport weather conditions were broadcasted on the ATIS-frequency 118.02 MHz every 30 minutes. The edition N of 16:20 UTC (24003KT 2500 BR FEW 003 02/02 1023) was the last one received by the crew of the B 747 (according to their own statement). Since the weather was deteriorating rapidly during the approach, two further special meteorological reports indicated by O and P were transmitted at 16:35 UTC and 16:38 UTC. These special met reports were not copied by the crew. At 16:37 UTC, during the final approach, the crew received the current RVR (runway visibility range) on Runway 25 L (zone A 300 m, B 550 m and C 375 m) by the tower in combination with the landing clearance (source: voice transcript of the radio communication). Low Visibility Operation at Frankfurt International Airport On 3 rd December 1998, the Federal Minister of Transport, Building and Housing (Bundesminister für Verkehr, Bau- und Wohnungswesen) issued a change to low visibility operations via Notam (Nachrichten für Luftfahrer NfL), which became effective at the 15 th January 1999. In parallel, there is an operational agreement between Frankfurt Airport Services (FAG) and the German Air Traffic Control ltd. (DFS) issued on 1 st December 1998 defining the responsibilities at Frankfurt Rhein-Main Airport. This agreement also regulates the procedure for low visibility operations as follows: With a runway visual range (RVR) of 1 000 m or less and/or a ceiling of 300 ft or less, the overseer of Approach Control (DFS) informs Central Apron Control (FAG) about the intended implementation of CAT II/III. Then Frankfurt Airport Service (FAG) will check whether the necessary requirements for CAT II/III operations are met from their side and forward the result to DFS. The overseer of DFS informs the FAG when actually resuming CAT II/III operations. The go ahead-message from the FAG has not yet been received by the DFS when the B747 was approaching runway 25 L. Therefore still CAT I was in operation at this time, although weather conditions for CAT II were already prevailing. Radar Evaluation The radar plot shows that the airplane was radar vectored from the southeast to intercept the runway centre line of Runway 25 L about 9 NM from touchdown (Enclosure 3). At this time the airplane was still flying above the nominal glidepath. The lateral navigation on the runway centre line was accurate according to the radar recording of the DFS. The vertical deviations of the airplane from the glide path shortly before touchdown were confirmed by the evaluation of the flight data recorder. Instrument landing system (ILS) With the surveillance recordings it was possible to determine that ILS equipment for Runway 25 L was working properly within permissible tolerances and without any deficiencies during the approach of the B747. Radio Communications Radio communications had been accomplished in English language and recorded and were evaluated. The landing clearance was confirmed by the copilot incorrectly with the call sign only, which in turn was accepted by the approach controller. Damage to Aircraft and Surface Equipment Tire marks with a length of 85 m maximum were clearly visible - 22 lights of the approach lighting system were damaged or destroyed (Enclosure 4). The localizer antenna for Runway 07 R was broken out at a width of about 16 m. So the approach lighting system 25 L and the ILS 07 R of the southern runway were unservicable until further (Enclosure 5). The B747 suffered damages to the main gear because of the collision with the surface equipment, its far spread debris causing damage to two engines and the fuselage as well (Enclosure 6). The aircraft underwent the necessary repair in Frankfurt for a ferry flight to Mumbai. Evaluation of the Electronic Monitoring Equipment of the Aircraft Systems After the event the Present Leg Faults Summary Report and Fault History Summary Report of the airborne recording system (CMC - Central Maintenance Computer) were printed out in Frankfurt and evaluated at the BFU in Braunschweig. There was not any clue to a system malfunction that could have contributed to the incident.

EX002-0/99 Seite 3 Evaluation of CVR and DFDR The cockpit voice recorder (CVR) was evaluated and a transcript was made. Because of the partially poor quality not all dialogues in the cockpit could be written down. Nonetheless the evaluation gives sufficient clues as to the proceedings in the cockpit of the airplane. The evaluation of the digital flight data recorder (DFDR) is available in appendix 1 and 2 and gives sufficient insight in the course of the incident in context with the evaluation of the CVR. Operational Procedures According to his own statement the approach to Runway 25 L was flown manually by the pilot-incommand. He was orderly licensed for long range flights with the B 747-400 according to his documents. At the time of the incident the flight crew was rated for CAT I approaches only. The airline concerned is presently about to implement CAT II operations. According to the statements of the flight crew the autoland-mode was used regularly with this type of aircraft. The second landing on Runway 25 R was performed automatically under weather conditions requiring CAT II/III operations.. The flight crew did not declare any emergency. Go-Around Procedure The go-around procedure and the second landing were not part of the investigation. The evaluation of the CVR during this flight phase however delivered information about the handling of operational procedures. Analysis The glideslope intercept from above, increased the workload for the crew definitely and exposed them to pressure of time. When the flight reached the preselected ALT 3 000 ft and the autoflight system brought the airplane to a level off, the autopilot was switched off and the approach was continued manually to facilitate the glideslope interception from above. A common Crew Co-ordination Concept (CCC) and Crew Resource Management (CRM) was not applied during the approach. The evaluation of the cockpit voice recorder (CVR) shows that there was no constructive dialogue about the current weather situation. Before passing the outer marker (FR) the crew received the landing clearance together with the current RVR-values for Runway 25 L (300 m / 550 m / 375 m) and the additional information that there is still CAT I in progress. In order to comply with the published procedures it would have been mandatory to discontinue the approach at this point because the visibility requirements were not fulfilled for CAT I any longer. This fact came to the knowledge of the crew before passing the outer marker. It is unclear whether the crew had comprehended the full contents of the report. The pilot in command did not realize the deterioration of the visibility according to his own statement. The caution message during the approach referring to the hydraulic system 4, and the subesequent solving of the hydraulic problem by reading the checklist hydraulic pressure demand 4 increased the workload of the crew additionally in a high concentration phase. The selection of flaps 30 0 was done to late for the weather conditions prevailing. Normally the final landing configuration should be established at 1 000 ft GND the latest and no major thrust changes should be made. It is not quite apparent why the airplane got above the glideslope during this approach phase because there is no mentionable ballooning effect to be expected when extending the flaps from 25 0 to 30 0. It is a fact, however, that the glideslope was left at the very moment when the final flap setting was established so that a coherence cannot be excluded. The reaction of the crew to the automatic call out of the ground proximity warning system (GPWS, SINKRATE! ) was too late to avoid ground contact. The go-around procedure was initiated just when touching the ground ahead of the runway. After completing the go-around procedure the crew did not analyse the situation. The hesitant question of the second pilot whether they possibly had touched approach lights was negated by the commander. The crew did not pay sufficient attention to the problem that the landing gear could not be retracted after the go-around. A thorough trouble shooting would have been quite probable to lead them to the conclusion that the gear had been damaged during the ground contact. The information from air traffic control that CAT III was in use was confirmed by the PIC with the words we do autoland. There was no further briefing accordingly. The implementation of CAT II/III operations had been postponed in this case since the go-ahead message as described in the Low Visibility Flight Operations Section had not been received yet. CAT II/III operations require greater separation distances for approaches and departures thus leading to considerable delays in flight operations. For technical reasons, the change to low visibility flight operations always involves a certain delay. Asking the crew to indicate their personal minima, a procedure usually applied in Great Britain, for example, would have caused them to reconsider their intentions.

EX002-0/99 Seite 4 An amendment to the German air traffic control procedures should be taken into consideration accordingly. Conclusions The ground contact about 1 000 m in front of the touchdown zone (coming short) was the consequence of an unstabilized final approach which was not discontinued by initiating a go-around procedure in a timely manner. Contributing factors were: The glideslope interception from above. A hydraulic malfunction during the approach requiring to perform the referring checklist The rapid deterioration of the visibility The continuation of the manual approach although the flight crew was not qualified for CAT II/III approaches Poor crew co-ordination and missing crew resource management Crew Resource Management (CRM) and Crew Coordination Concept (CCC). Resulting from the investigation the BFU recommends to the operator as follows: 10/99 Implementation of low visibility operations and training of crews according ICAO Annex 6, Chapter 4 and 5. 11/99 Realization of a CRM-training for all cockpit crews accordingly. 12/99 Revision of manuals with respect of CRM and CCC. The BFU recommends to the Luftfahrt-Bundesamt (Federal Office of Civil Aeronautics) and to the relevent aviation authorities: 09/99 Foreign operators should not only be granted entry permissions, but the aviation authorities responsible for the supervision of operators and for air traffic surveillance at aerodromes should also adequately supervise compliance with the requirements (e.g. CAT II / III). Safety Recommendations As a result of the investigation of this serious incident the BFU comes to the conclusion that there are major deficiencies with the airline involved concerning flight operations and crew training, especially with respect of Investigator-in-charge Structures Performance Field Investigation Mueller Leibe Blau Müller / Leibe The investigation was performed in conformity to the Law relating to the investigation into Accidents and Incidents associated with the Operation of Civil Aircraft dated August 26. 1998. Accordingly the sole objective of the investigation of an accident shall be the prevention of future accidents. It is not the purpose of this activity to apportion blame or liability Editor: Bundesstelle für Flugunfalluntersuchung Hermann-Blenk-Str. 16 38108 Braunschweig mail: box@bfu-web.de http://www.bfu-web.de Tel: 0 531 35 48 0 Fax: 0 531 35 48 246 Distributer Pramme - Media Tel: 05307 98 01 55 Industriestraße 9 38110 Braunschweig

Illustration not Available Fss.aero was unable to obtain permission from Jeppesen-Sanderson, Inc. to reproduce this copyrighted chart. Please see the FAQ for easy work-arounds. Jeppesen-Sanderson can be reached at: www.jeppesen.com 55 Inverness Drive East Englewood, CO 80112-5498