Asiana Airlines Flight 162

Last updated
Asiana Airlines Flight 162
Airbus A320-232, Asiana Airlines AN1912836.jpg
HL7762, the aircraft involved, photographed in 2011
Accident
Date14 April 2015 (2015-04-14)
SummaryDescent below final approach path and impact with ground structures due to pilot error and poor training
Site Hiroshima Airport, Mihara, Hiroshima, Japan
34°26′10″N132°55′10″E / 34.4361°N 132.9194°E / 34.4361; 132.9194
Aircraft
Aircraft type Airbus A320-232
Operator Asiana Airlines
IATA flight No.OZ162
ICAO flight No.AAR162
Call signASIANA 162
Registration HL7762
Flight origin Incheon International Airport, South Korea
Destination Hiroshima Airport, Japan
Occupants82
Passengers74
Crew8
Fatalities0
Injuries27
Survivors82

Asiana Airlines Flight 162 was a regular short-haul international passenger flight from Incheon International Airport near Seoul, South Korea, to Hiroshima Airport in Hiroshima, Japan. [1] On 14 April 2015, the Airbus A320-232 aircraft touched down short of the runway, struck the localizer array, skidded onto the runway on its tail, and spun 120 degrees before finally coming to a rest on the grass, opposite the terminal building. The aircraft suffered substantial damage to the left wing and engine. Of the 82 people aboard, 27 (25 passengers and two crew) were injured, one seriously. [2] [3] [4]

Contents

Aircraft and crew

The aircraft involved, an Airbus A320-200 registration HL7762, was delivered new to Asiana Airlines in 2007, making the aircraft seven years old at the time of the accident. The aircraft was written off as a result of the incident, [5] [6] making it the 32nd hull loss of an Airbus A320. [1]

The 47-year-old captain had 8,242 flight hours, including 1,318 hours on the Airbus A320. The 35-year-old co-pilot had 1,588 flight hours, with 1,298 of them on the Airbus A320. [7] :15–16 Both pilots had previous experience in landing at Hiroshima Airport, but Flight 162 was their first flight with each other. Actual names of the crew were not disclosed.

Accident

Landing path of Flight 162 at Hiroshima Asiana Airlines Flight 162 landing path at Hiroshima en.svg
Landing path of Flight 162 at Hiroshima

The transport ministry's Osaka Regional Civil Aviation Bureau stated that the crew tried to land the aircraft in darkness and inclement weather without access to an instrument landing system. At this airport, aircraft normally approach from the west because the instrument landing system is installed only at the eastern end of the runway. On this occasion, the pilot was instructed by an air traffic controller to approach from the east due to the wind direction. Bureau officials were reported to have stated that the pilot attempted to land in poor weather with low visibility while using such aids as the lighting near the centre-line of the runway that indicates glide angles (normally used in good weather conditions). [8] [9]

At 18:58 Japan Standard Time (JST), while cruising at flight level (FL) 33,000 feet (10,000 m) the first officer received the weather conditions at Hiroshima. The captain, who was the pilot flying, gave an approach briefing, stating he intended to land on runway 10 using radar vectors from air traffic control (ATC). He also warned the first officer about runway 28, as the full length of that runway was not visible from the threshold, and advised him to speak up if there were any concerns. The first officer then received the Automatic Terminal Information System (ATIS) which stated that runway 28 was the active runway and that aircraft were using the RNAV (area navigation) approach and told the relayed information to the captain. The crew decided to land on runway 28. [7] :4

The first officer then configured the Flight management system for the approach. The aircraft then began to descend from its cruising altitude. The captain then gave a second briefing, saying that he would configure the aircraft for landing before reaching the final approach fix (FAF) and acknowledged the new information in the FMC. At 19:57 the approach controller told Flight 162 to expect radar vectors to the waypoint (and the intermediate approach fix (IF)) VISTA. Two minutes later, Flight 162 was cleared for an RNAV approach to runway 28. At 20:00, Flight 162 was transferred to the tower controller, who cleared the flight to land. The landing gear was then lowered, the flaps were extended to full, and the landing checklist was carried out. After completing the landing checklist, the captain gave a go-around briefing, stating that TO/GA thrust would be used and the flaps would be retracted one position at a time. At 20:03, the flight crew discussed concern about the runway's appearance, as recorded on the aircraft's cockpit voice recorder (CVR): [7] :5–6

Captain: "The runway looks strange."
First officer: "Yes, a little bit awkward."
Captain: "It means we might have some cloud in there?"

The captain then disengaged the autopilot. Recovered flight data shows that, after autopilot disconnect, the aircraft began a slow and controlled descent below the normal glide slope approach path about 4 kilometres (2.5 mi; 2.2 nmi) before impact. [2] At 20:04, the first officer made two more comments about the weather saying "ah, It looks a bit ambiguous due to cloud, sir," and "wow, getting invisible in a second," at 20:04:14 and 20:04:39 respectively. At 20:04:42, the aircraft was at 1,484 feet (452 m) according to the Flight Data Recorder (FDR). The CVR recorded the following at this time:

Enhanced Ground Proximity Warning System (EGPWS): "Minimum."
First officer: "Minimum."
Captain: "Continue."
First officer: "Ah. Runway not in sight."
Captain: "Wait a second. Shoot, wait a second. We have RA [radio altimeter] is there-"
First officer "Yes, nine hundred, eight hundred."
Captain: "Please keep your eye on RA."
First officer: "Yes, six hundred, five hundred. Five hundred." (RA height
EGPWS: "Four hundred. Three hundred. Two hundred." (Actual height (above ground level))
First officer: "Five hundred."

At 20:05:11, the captain initiated a go-around and pulled the side-stick to full nose aft.

Captain: "No runway, go-around."
First officer: "Yes. Go-around."
EGPWS: "Forty."
First officer: "Yes."
Cockpit area microphone (CAM): [Sound of impact]
End of recording

Three seconds after the go-around was initiated, the aircraft struck the localizer 325 metres (355 yd; 1,066 ft) before the runway threshold in a nose-high attitude 148 metres (162 yd; 486 ft) short of the runway, with the main gear making contact with the ground 12 metres (39 ft) further on. After exiting the runway, the aircraft rotated until it came to rest facing the direction it had landed from. [10]

Investigation

HL7762 in open storage at Hiroshima Airport following the accident HL7762 Airbus A.320 Asiana Airlines Hiroshima Airport 20150501.jpg
HL7762 in open storage at Hiroshima Airport following the accident

The Japanese Transportation Safety Board (JTSB) opened an investigation into the accident. [2] Hiroshima Prefecture Prefectural police also launched an investigation on 15 April. [8] South Korean investigators and airline officials traveled to Japan to join the investigation on 15 April. [9]

On 16 April, investigators began debriefing the captain and first officer. One investigator from the JTSB stated that a downdraft during approach may have contributed to the inadequate altitude at the runway threshold. [11] The METAR (weather conditions) for the time did not indicate any unusual weather or wind shear. The weather was low overcast with almost no wind. [2] The captain stated to investigators that he had not lost sight of the runway during the approach, but initiated a go-around as an instrument showed the aircraft deviating to the right. The first officer, on the other hand, stated that he did lose sight of the runway and should have initiated a go-around after losing sight of it, but instead read the radio altimeters at the captain's request. [7] :8–12

The JTSB released its final report on 18 November 2016. The report determined that the probable cause of the accident was the captain's failure to immediately initiate a go-around when visual cues were lost, the first officer's failure to challenge the captain's performance (both of which did not follow to Standard Operating Procedures), lack of crew resource management (CRM) and Asiana Airlines' insufficient training. [7] :83 The JTSB's issued two safety recommendations to Asiana Airlines, both of which urged the airline to improve its flight crew training; the first recommendation stated that the airline should reinforce the importance of flight crew's adherence to SOP's, while the second instructed the airline to implement training for pilots in awareness with visual references and appropriately using flight instruments when necessary. [7] :87

See also

Related Research Articles

Asiana Airlines Inc. is a South Korean airline headquartered in Seoul. In 2019, it accounted for 25% of South Korea's international aviation market and 20% of its domestic market. It maintains its international hub at Seoul's Incheon International Airport. and its domestic hubs at Gimhae International Airport in Busan and Gimpo International Airport in Seoul. It is a full-service airline and a member of Star Alliance.

<span class="mw-page-title-main">Hiroshima Airport</span> Airport serving Hiroshima, Japan

Hiroshima Airport is an international airport in the city of Mihara, Hiroshima Prefecture, Japan. Located 50 km (31 mi) east of Hiroshima, it is the largest airport in the Chūgoku region. 80% of the airport's domestic traffic is to and from Haneda Airport in Tokyo. The Hiroshima-Haneda route is the fifth-busiest domestic air route in Japan.

<span class="mw-page-title-main">Gulf Air Flight 072</span> 2000 aviation accident

Gulf Air Flight 072 (GF072/GFA072) was a scheduled international passenger flight from Cairo International Airport in Egypt to Bahrain International Airport in Bahrain, operated by Gulf Air. On 23 August 2000 at 19:30 Arabia Standard Time (UTC+3), the Airbus A320 crashed minutes after executing a go-around upon failed attempt to land on Runway 12. The flight crew suffered from spatial disorientation during the go-around and crashed into the shallow waters of the Persian Gulf 2 km (1 nmi) from the airport. All 143 people on board the aircraft were killed.

<span class="mw-page-title-main">American Airlines Flight 1572</span> 1995 aviation accident

American Airlines Flight 1572 was a flight from Chicago O'Hare International Airport to Bradley International Airport on November 12, 1995. The McDonnell Douglas MD-83 struck trees and an instrument landing system (ILS) antenna during landing, causing $9 million in damage to the aircraft.

<span class="mw-page-title-main">Armavia Flight 967</span> 2006 plane crash in the Black Sea off Sochi, Russia

Armavia Flight 967 was a scheduled international passenger flight operated by Armavia from Zvartnots International Airport, Zvarnots in Armenia to Sochi, a Black Sea coastal resort city in Russia. On 3 May 2006, the aircraft operating the route, an Airbus A320-200, crashed into the sea while attempting a go-around following its first approach to Sochi airport; all 113 aboard were killed. The accident was the first major commercial airline crash in 2006. It was Armavia's only fatal crash during the airline's existence.

<span class="mw-page-title-main">Philippine Airlines Flight 137</span> 1998 aviation accident

Philippine Airlines Flight 137 was a scheduled passenger flight from Ninoy Aquino International Airport in Manila to Bacolod City Domestic Airport in Bacolod.

<span class="mw-page-title-main">Lufthansa Flight 2904</span> 1993 passenger plane crash in Warsaw, Poland

Lufthansa Flight 2904 was an Airbus A320-200 flying from Frankfurt, Germany to Warsaw, Poland that overran the runway at Okęcie International Airport on 14 September 1993.

<span class="mw-page-title-main">Indian Airlines Flight 605</span> 1990 passenger aircraft landing crash in Bangalore, India

Indian Airlines Flight 605 was a scheduled domestic passenger flight from Bombay to Bangalore. On 14 February 1990, an Airbus A320-231 registered as VT-EPN, crashed onto a golf course while attempting to land at Bangalore, killing 92 of 146 people on board.

<span class="mw-page-title-main">TACA Flight 390</span> 2008 aviation accident in Honduras

TACA Flight 390 was a scheduled flight on May 30, 2008, by TACA International from San Salvador, El Salvador, to Miami, Florida, United States, with intermediate stops at Tegucigalpa and San Pedro Sula in Honduras. The aircraft, an Airbus A320-233, overran the runway after landing at Tegucigalpa's Toncontín International Airport and rolled out into a street, crashing into an embankment and smashing several cars in the process.

<span class="mw-page-title-main">FedEx Express Flight 80</span> 2009 cargo plane crash in Tokyo, Japan

FedEx Express Flight 80 was a scheduled cargo flight from Guangzhou Baiyun International Airport in the People's Republic of China, to Narita International Airport in Narita, Chiba Prefecture, Japan. On March 23, 2009, the McDonnell Douglas MD-11F (N526FE) operating the flight crashed at 6:48 am JST, while attempting a landing on Runway 34L in gusty wind conditions. The aircraft became destabilized at flare and touchdown resulting in an unrecovered "bounced" landing with structural failure of the landing gear and airframe, and came to rest off the runway, inverted, and burning fiercely. The captain and first officer, the jet's only occupants, were both killed.

<span class="mw-page-title-main">American Airlines Flight 331</span> 2009 aviation accident

On 22 December 2009, an American Airlines Boeing 737-800, operating American Airlines Flight 331 and carrying 148 passengers and six crew, overran runway 12 on landing at Kingston in poor weather. The plane continued on the ground outside the airport perimeter and broke apart on the beach, causing injuries.

<span class="mw-page-title-main">UPS Airlines Flight 1354</span> 2013 aviation accident

UPS Airlines Flight 1354 (5X1354/UPS1354) was a scheduled cargo flight from Louisville, Kentucky, to Birmingham, Alabama. On August 14, 2013, the Airbus A300 flying the route crashed and burst into flames short of the runway on approach to Birmingham–Shuttlesworth International Airport. Both pilots were pronounced dead at the scene of the crash. They were the only people aboard the aircraft. It was the second fatal air crash for UPS Airlines.

<span class="mw-page-title-main">Air Canada Flight 624</span> 2015 aviation accident

Air Canada Flight 624 was a scheduled Canadian domestic passenger flight from Toronto Pearson International Airport to Halifax Stanfield International Airport in Halifax, Nova Scotia. During heavy snow and poor visibility, at 00:43 ADT on 29 March 2015, the Airbus A320-211 landed short of the runway and was severely damaged. Twenty-six people were injured.

<span class="mw-page-title-main">Turkish Airlines Flight 1878</span> 2015 aviation accident

Turkish Airlines Flight 1878 was an international passenger flight from Milan–Malpensa Airport, Italy to Atatürk Airport, Istanbul, Turkey. On 25 April 2015, the aircraft rolled sharply just before landing, causing a very hard touchdown resulting in substantial damage to the starboard wing and a fire. A go-around was initiated, and the aircraft positioned for a second approach attempt but veered off the runway on the second landing. All 102 passengers and crew survived unharmed.

<span class="mw-page-title-main">2009 Aviastar British Aerospace 146 crash</span>

The 2009 Aviastar British Aerospace 146 crash occurred on April 9, 2009, when a British Aerospace 146 crashed into Pikei Hill during a ferry flight from Sentani Airport to Wamena Airport, both in Indonesia's Papua province. Due to the force of the impact the aircraft was destroyed and all 6 crew members were killed. The aircraft was carrying voting paper to Wamena as well as several other goods, as a parliamentary election was held in the month. The wreckage was found in Pikei Hill, Tengah Mountain, Tangma, Yahukimo District.

<span class="mw-page-title-main">Air Canada Flight 759</span> 2017 aviation incident

On July 7, 2017, an Airbus A320-211 operating as Air Canada Flight 759 was nearly involved in an accident at San Francisco International Airport in San Mateo County, California, United States. The flight, which originated at Toronto Pearson International Airport, had been cleared by air traffic control to land on runway 28R and was on final approach to land on that runway; however, instead of lining up with the runway, the aircraft had lined up with the parallel taxiway, on which four fully loaded and fueled passenger airplanes were stopped awaiting takeoff clearance. The flight crew initiated a go-around prior to landing, after which it landed without further incident. The aircraft on the taxiway departed for their intended destinations without further incident. The subsequent investigation by the National Transportation Safety Board (NTSB) determined that the Air Canada airplane descended to 59 feet (18 m) above the ground before it began its climb, and that it missed colliding with one of the aircraft on the taxiway by 14 feet (4.3 m).

<span class="mw-page-title-main">Iberia Flight 1456</span> 2001 aviation incident

Iberia Flight 1456 was a domestic scheduled flight from Barcelona-El Prat Airport, Spain, to Bilbao Airport, Spain. On Wednesday, February 7, 2001, the Airbus A320, which took off from Barcelona-El Prat Airport, Spain, encountered a microburst-induced wind shear on final approach to Bilbao Airport, Spain. The wind shear caused the plane's landing gear to collapse. All 143 passengers onboard survived; with 25 people suffering light injuries, and 1 person receiving serious injuries. The aircraft was irreparably damaged as a result of the ordeal and was decommissioned soon after, making it the ninth loss of an Airbus A320 at that time. This accident prompted Airbus to develop a fail-safe modification for its flight control software by preventing the airplane's built-in protection against stall from being activated by a high rate of change for the angle of attack.

<span class="mw-page-title-main">LATAM Airlines Perú Flight 2213</span> 2022 aviation accident

LATAM Airlines Perú Flight 2213 was a scheduled domestic passenger flight in Peru from Lima to Juliaca. On 18 November 2022, the Airbus A320neo was taking off from Jorge Chávez International Airport when it collided with a fire engine that was crossing the runway, killing two firefighters and injuring a third, who died of his injuries seven months later. 40 passengers were injured. The aircraft was damaged beyond repair and written off, making it the first hull loss of the Airbus A320neo family.

References

  1. 1 2 Ranter, Harro (14 April 2015). "ASN Aircraft accident Airbus A320-232 HL7762 Hiroshima International Airport (HIJ)". aviation-safety.net. Aviation Safety Network . Retrieved 16 April 2015.
  2. 1 2 3 4 Hradecky, Simon. "Accident: Asiana A320 at Hiroshima on Apr 14th 2015, touched down short of runway". avherald.com. The Aviation Herald. Archived from the original on 2021-05-06. Retrieved 16 April 2015.
  3. "Asiana Airlines Plane Skids Off Runway In Japan". The Huffington Post. Retrieved 16 April 2015.
  4. "Asiana plane skids off runway in Japan, leaving 20 injured". The Daily Telegraph (online edition). AFP. 15 April 2015. Retrieved 15 April 2015.
  5. "Asiana Airlines HL7762 (Airbus A320)". airfleets.net. Airfleets aviation. Archived from the original on 2009-01-23. Retrieved 24 April 2015.
  6. "HL7762 Asiana Airlines Airbus A320-200 – cn 3244". planespotters.net. Archived from the original on 17 April 2015. Retrieved 16 April 2015.
  7. 1 2 3 4 5 6 "AIRCRAFT ACCIDENT INVESTIGATION REPORT ASIANA AIRLINES, INC. AIRBUS A320-200, HL7762 COLLISION WITH THE AERONAUTICAL RADIO NAVIGATION AIDS CAUSED BY UNDERSHOOTING HIROSHIMA AIRPORT AT 20:05 JST, APRIL 14, 2015" (PDF). Japanese Transport Safety Board. 2016-11-24. AA2016-9. Archived (PDF) from the original on 2018-08-19. Retrieved 2020-06-14.
  8. 1 2 "Police investigate airliner accident in Hiroshima on suspicion of pilot error". Asahi Shimbun . 15 April 2015. Archived from the original on 2015-04-15. Retrieved 15 April 2015.
  9. 1 2 Obe, Mitsuru; Nam, In-Soo (15 April 2015). "Japan, South Korea Probe Asiana Plane's Skid off Runway in Hiroshima". The Wall Street Journal . ISSN   0099-9660 . Retrieved 16 April 2015.
  10. Kaminski-Morrow, David (13 May 2015). "Crashed Asiana A320 drifted below glidepath in low visibility". Flight Global. Retrieved 17 May 2015.
  11. "Downdraft may be factor in Asiana jet's botched landing at Hiroshima". Japan Times . 16 April 2015. Retrieved 15 April 2015.