ASN Wikibase Occurrence # 139628
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Thursday 3 November 2011 |
| Time: | 12:09 LT |
| Type: |  Boeing 777-312ER |
| Owner/operator: | Singapore Airlines |
| Registration: | 9V-SWQ |
| MSN: | 34582/716 |
| Year of manufacture: | 2008 |
| Fatalities: | Fatalities: 0 / Occupants: 158 |
| Aircraft damage: | Minor |
| Category: | Serious incident |
| Location: | München-Franz Josef Strauss Airport (MUC/EDDM) -
 Germany
|
| Phase: | Landing |
| Nature: | Passenger - Scheduled |
| Departure airport: | Manchester International Airport - MAN/EGCC |
| München-Franz Josef Strauss Airport - MUC/EDDM | |
| Investigating agency: | BFU |
| Confidence Rating: |  Accident investigation report completed and information captured |
Singapore Airlines flight SQ327 departed Manchester, U.K. on a flight to Munich, Germany, and Singapore. The co-pilot was initially Pilot Flying (PF) during the flight to Munich.
Based on the latest weather information at Munich, visibility 2,000 m, cloud base 300 ft, the Pilot in Command (PIC) decided to assume the role of PF, and the co-pilot became Pilot Monitoring (PM). The PIC decided to conduct an automatic approach and autoland.
At 11:52 hours local time during descent to Flight Level (FL) 110 the crew contacted Munich approach control for the first time. The crew received several instructions, such as heading and rate of descent, from the controller.
At 11:58 hrs the crew contacted Munich Director and received heading and descent instructions for the final approach to the Instrument Landing System (ILS) of runway 08R.
At 12:00 hrs the crew received the approach clearance to runway 08R "[...] descend 5,000 feet cleared ILS zero eight." Three minutes later the crew was instructed to reduce speed to 170 kt and contact Munich Tower.
At 12:08 hrs the crew received the latest wind information and was cleared to land: “[...] one three zero degrees, seven knots runway zero eight right, cleared to land”.
As the Boeing 777 was about 50 ft above the runway in the flare phase the airplane began to slowly bank left up to 3.5°. The PIC called out: “Okay, flaps twenty.” At approximately 420 m beyond the runway threshold the airplane touched down with the left main landing gear and 132 kt (KIAS). At that time the Auto Flight System (AFS) switched to rollout mode.
The autopilot was still engaged as the airplane moved toward the left runway edge and veered off the runway with a speed of 123 kt (KIAS) about 944 m beyond the threshold in the area of taxiway B4. For about 400 m the airplane rolled through the grass north of runway 08R in a slightly curved right hand turn. The largest lateral deviation from the runway was reached at about 1,242 m beyond the threshold; speed was 109 kt KIAS. Because of the system design the autopilot disengaged due to crew inputs via the rudder pedals. The airplane turned right by about 40°, re-entered the runway close to the intersection with taxiway B6, about 1,566 m beyond the threshold. The aircraft crossed the runway with a heading of about 120°. Speed was still 71 kt KIAS. The airplane veered off the runway again, turned left by about 40°, and came to a stop in the grass south of and parallel to runway 08R. At 12:09:09 hrs the airplane crossed the threshold; at 1209:51 hrs it came to a stop.
According to the pilots there was no need to evacuate the passengers via the slides, because no one had suffered any injuries and the airplane was apparently not damaged. About two minutes after the airplane had come to a stop the fire brigade arrived at the scene. The passengers disembarked the airplane via two stairs from the fire brigade.
The crew stated that during the approach and the landing there were no indications as to malfunctions or system failures. The PIC stated he had tried to initiate a goaround procedure by pushing the TO/GA buttons on the thrust levers and thereby triggering the go-around mode once it had been noticed that the airplane banked to the left. But the airplane did not respond. At the same time he retracted the ground spoilers manually which had automatically been deployed at the time of the touchdown.
Immediate Causes:
- The crew decided to conduct an autoland landing even though the conditions on the ground for a safe conduct were not given.
- Shortly before touch-down the airplane was deviated to the left of its flight direction by a disturbed LOC signal. A BAE 146-RJ85 taking off a short distance ahead of the B 777 caused the interference.
- The two pilots could not keep the airplane on the runway after touch-down because the autopilot was still engaged.
- The crew was confused by the behaviour of the airplane. They had not noticed that the go-around mode had already been deactivated by the initial touchdown of the left main landing gear.
Systemic Causes:
- The recommendation concerning the conduct of autoland landings under CAT I conditions published in the FCOM of the operator allowed the decision for an autoland landing without having to consider the required conditions on the ground.
Accident investigation:
 |
|
Sources:
https://www.youtube.com/watch?v=0rn-iI7wX-Y&feature=youtu.be
https://www.feuerwehrmagazin.de/wissen/boeing-777-am-flughafen-munchen-verunfallt-23880
http://aerossurance.com/safety-management/sia-b777-autoland-localiser-re/
https://www.bfu-web.de/EN/Publications/Investigation%20Report/2011/Report_11_EX010_B777_Munic.pdf?__blob=publicationFile
History of this aircraft
Other occurrences involving this aircraft
| 27 March 2023 | 9V-SWQ | Singapore Airlines | 0 | near Los Angeles International Airport, CA (LAX/KLAX) |  |
non |
| Inflight smoke | ||||||
Images:
Media:
#singaporeair #B777 in Autoland Mode Left Runway at #munichairport When Another Aircraft Interfered With the Localiser Signal (includes VIDEO)https://t.co/f7ke1q5DsV#BFU report 7 years 1 month after incident #avgeek #flightsafety pic.twitter.com/6t2PD2m4To
— Aerossurance (@Aerossurance) December 24, 2018
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 03-Nov-2011 08:43 | ryan | Added |
| 03-Nov-2011 09:13 | harro | Updated [Aircraft type, Nature, Source, Narrative] |
| 03-Nov-2011 09:17 | RobertMB | Updated [Time, Location, Nature, Departure airport, Destination airport, Source, Damage, Narrative] |
| 06-May-2012 01:19 | harro | Updated [Source] |
| 12-Feb-2017 11:45 | Anon. | Updated [Narrative, Photo, ] |
| 18-Jan-2018 18:17 | Anon. | Updated [Damage] |
| 17-Dec-2018 18:11 | harro | Updated [Source, Narrative, Accident report, ] |
| 23-Dec-2018 15:34 | harro | Updated [Time, Nature, Narrative] |
| 23-Dec-2018 18:05 | harro | Updated [Embed code] |
| 24-Dec-2018 12:59 | Aerossurance | Updated [Source, Embed code] |
| 25-Dec-2018 18:58 | Aerossurance | Updated [Source, Embed code] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation