Asiana Airlines Flight 214

Asiana Airlines Flight 214 was a scheduled transpacific passenger flight from Incheon International Airport near Seoul, South Korea, to San Francisco International Airport in the United States. On the morning of 6 July 2013, the Boeing 777-200ER crashed on final approach into San Francisco International Airport. Of the 307 people on board, three died; another 187 were injured, 49 of them seriously.[1]:13 Among the injured were four flight attendants who were thrown onto the runway while still strapped in their seats when the tail section broke off after striking the seawall short of the runway. It was the first fatal crash of a Boeing 777 since that aircraft type entered service in 1995.

Asiana Airlines Flight 214
The wreckage of the Boeing 777 at San Francisco International Airport the day after the crash
DateJuly 6, 2013 (2013-07-06)
SummaryControlled flight into terrain
SiteSan Francisco International Airport, San Mateo County, California, United States
37°36′48″N 122°21′52″W / 37.61333°N 122.36444°W / 37.61333; -122.36444Coordinates: 37°36′48″N 122°21′52″W / 37.61333°N 122.36444°W / 37.61333; -122.36444
Aircraft typeBoeing 777-28EER
OperatorAsiana Airlines
IATA flight No.OZ214
ICAO flight No.AAR214
Call signASIANA 214
Flight originIncheon International Airport, Seoul, South Korea
DestinationSan Francisco International Airport, San Mateo County, California, U.S.

The investigation by the U.S. National Transportation Safety Board concluded that the accident was the result of the flight crew's mismanagement of the airplane's final approach to the airport. Deficiencies in Boeing's documentation of complex flight control systems and in Asiana Airlines's pilot training were also cited as contributory factors.[1]:129


On 6 July 2013, Flight OZ214 took off from Incheon International Airport (ICN) at 5:04 p.m. KST (08:04 UTC), 34 minutes after its scheduled departure time. It was scheduled to land at San Francisco International Airport (SFO) at 11:04 a.m. PDT (18:04 UTC).[2]

The flight was cleared for a visual approach to runway 28L at 11:21 a.m. PDT, and told to maintain a speed of 180 knots (330 km/h; 210 mph) until the aircraft was 5 miles (8.0 km) from the runway. At 11:26 a.m., Northern California TRACON ("NorCal Approach") passed air traffic control to the San Francisco tower. A tower controller acknowledged the second call from the crew at 11:27 a.m. when the plane was 1.5 miles (2.4 km) away, and gave clearance to land.[3]

The weather was very good; the latest METAR reported light wind, 10 miles (16 km) visibility (the maximum it can report), no precipitation, and no forecast or reports of wind shear. The pilots performed a visual approach[4] assisted by the runway's precision approach path indicator (PAPI).[5]

 Runway 28L 
 Left engine 
 and right engine 
 Landing gear 
Approximate locations of the wreckage.[6][7] The arrow indicates the flight direction before impact.

At 11:28 a.m., HL7742[8] crashed short of runway 28L's threshold. The landing gear and then the tail struck the seawall that projects into San Francisco Bay.[5][9][10] Both engines and the tail section separated from the aircraft.[11] The NTSB noted that the main landing gear, the first part of the aircraft to hit the seawall, "separated cleanly from [the] aircraft as designed" to protect the wing fuel tank structure.[12][13][1]:34 The vertical and both horizontal stabilizers fell on the runway before the threshold.[14]

The remainder of the fuselage and wings rotated counter-clockwise approximately 330 degrees, as it slid westward. Video showed it pivoting about the wing and the nose while sharply inclined to the ground. It came to rest to the left of the runway, 2,400 feet (730 m) from the initial point of impact at the seawall.[15]

After a minute or so, a dark plume of smoke was observed rising from the wreckage. The fire was traced to a ruptured oil tank above the right engine. The leaking oil fell onto the hot engine and ignited.[16] The fire was not fed by jet fuel.[12][13]

Final position of plane with exit doors marked

Two evacuation slides were deployed on the left side of the airliner and used for evacuation.[11][17] Despite damage to the aircraft, "many ... were able to walk away on their own."[18] The slides for the first and second doors on the right side of the aircraft (doors 1R and 2R) deployed inside the aircraft during the crash, pinning the flight attendants seated nearby.[3][1]:41–42

According to NBC reports in September 2013, the US government had been concerned about the reliability of evacuation slides for decades: "Federal safety reports and government databases reveal that the NTSB has recommended multiple improvements to escape slides and that the Federal Aviation Administration has collected thousands of complaints about them." Two months before the accident at SFO, the FAA issued an airworthiness directive ordering inspection of the slide release mechanism on certain Boeing 777 aircraft, so as to detect and correct corrosion that might interfere with slide deployment.[19][20]

This was the third fatal crash in Asiana's 25-year history.[21]


HL7742, the aircraft involved landing at Hong Kong Chek Lap Kok International Airport, in 2011

The Boeing 777-200ER, registration HL7742,[8] was powered by two Pratt and Whitney PW4090 engines.[4][22] It was delivered new to Asiana Airlines on 7 March 2006,[23][24] and at the time of the crash had accumulated 37,120 flight hours and 5,388 (takeoff-and-landing) cycles.[1]:20

The Boeing 777 has a good reputation for safety.[25] This was its first fatal accident, second crash (after British Airways Flight 38), and third hull loss since the 777 began operating commercially in 1995.[26]

Crew and passengersEdit

Nationalities of passengers and crew[18][27]
Nationality Passengers Crew Fatalities Total
China 141 0 3 141
South Korea 77 14 0 91
United States 64 0 0 64
Canada 3 0 0 3
India 3 0 0 3
Thailand 0 2 0 2
France 1 0 0 1
Japan 1 0 0 1
Vietnam 1 0 0 1
 Total 291 16 3 307


The aircrew consisted of three captains and one first officer. Captain Lee Jeong-min (Hangul: 이정민; Hanja: 李鄭閔), age 49, in the right seat (co-pilot position)[28] filled the dual role of a check / instructor captain and pilot in command, responsible for the safe operation of the flight.[29] He had 12,387 hours of flying experience of which 3,220 hours were in a 777.[30] This was his first flight as an instructor.[31]

Captain Lee Kang-kook (Hangul: 이강국; Hanja: 李江鞠; variant Lee Gang-guk), age 45, in the left seat (captain's position) was the pilot receiving his initial operating experience (IOE) training and was halfway through Asiana's IOE requirements. He had 9,793 hours of flying experience, of which 43 were in a 777 over nine flights,[32] and was operating the controls under the supervision of the instructor in the right seat.[33]

First officer Bong Dong-won (Hangul: 봉동원; Hanja: 棒動員), who had been in the cockpit, received medical treatment for a cracked rib; none of the other pilots needed hospital care.[34]

Four flight attendants seated at the rear were ejected from the aircraft when the tail section broke off, and they survived.[1]:111[3][35]

Twelve flight attendants were on board: ten South Korean and two Thai. Six flight attendants received physical and emotional treatment. The other six returned to South Korea.[5][36]


Seat map indicating injuries and deaths[1]:38

Two 16-year-old girls with Chinese passports were found dead outside the aircraft soon after the crash, having been thrown out of the aircraft during the accident.[1]:108–110[37][38][39][40] Neither victim had been using her seatbelt.[1]:108–110 It is likely that these passengers would have remained in the cabin and survived had they been wearing their seatbelts.[1]:xii,110 On 19 July 2013, the San Mateo County Coroner's office determined that one of the two girls was still alive prior to being run over by a rescue vehicle, and was killed due to blunt force trauma.[41][42] On 28 January 2014, the San Francisco city attorney's office announced their conclusion that the girl was already dead when she was run over.[43][44]

A third passenger, a 15-year-old Chinese girl, died of her injuries at San Francisco General Hospital six days after the accident.[1]:108–110[45][46][47][48] She had been wearing her seatbelt and was seated in 42A, which is the last row of passenger seats on the left side of the aircraft and was immediately forward of door 4L. During the crash the back of her seat rotated back and against the floor, leaving her exposed. Her injuries were likely due to being struck by door 4L, which separated during the airplane's final impact.[1]:110

Ten people in critical condition were admitted to San Francisco General Hospital and a few to Stanford Medical Center.[49] Nine hospitals in the area admitted 182 injured people.[50] San Francisco Fire Department Chief Joanne Hayes-White, after checking with two intake points at the airport, told reporters that all on board had been accounted for.[51]

Of the passengers, 141 (almost half) were Chinese citizens. More than 90 of them had boarded Asiana Airlines Flight 362 from Shanghai Pudong International Airport, connecting to Flight 214 at Incheon.[52] Incheon serves as a major connecting point between China and North America. In July 2013, Asiana Airlines operated between Incheon (Seoul) and 21 cities in mainland China.[53]

Seventy students and teachers traveling to the United States for summer camp were among the Chinese passengers. Thirty of the students and teachers were from Shanxi, and the others were from Zhejiang.[54] Five of the teachers and 29 of the students were from Jiangshan High School in Zhejiang; they were traveling together.[55] Thirty-five of the students were to attend a West Valley Christian School summer camp. The Shanxi students originated from Taiyuan,[56] with 22 students and teachers from the Taiyuan Number Five Secondary School and 14 students and teachers from the Taiyuan Foreign Language School.[57] The three passengers who died were in the Jiangshan High School group to West Valley camp.[54][56][58][59]

Survivor and eyewitness accountsEdit

The rear cabin after the crash
The charred middle cabin after the crash and fire

Several passengers recalled noticing the plane's unusual proximity to the water on final approach, which caused water to thrust upward as the engines were spooling up in the final seconds before impact.[18][54][60]

In the initial moments after the crash, the cockpit crew told flight attendants to delay evacuating the aircraft as they were communicating with the tower. A flight attendant seated at the second door on the left side (door 2L) observed fire outside the aircraft near row 10 and informed the cockpit crew, at which point the evacuation order was given some 90 seconds after the aircraft came to rest. Flight attendants told NTSB investigators that there was no fire inside the cabin when the evacuation began.[3]

The crew also helped several passengers who were unable to escape on their own; a pilot carried out one passenger with an injured leg. One flight attendant said that many Chinese passengers who sat at the back of the plane near the third exit were not aware of the evacuation.[61]

Smoke rising from the crash site as seen from Terminal 1

During the evacuation, a pilot used an extinguisher on a fire that had penetrated from the exterior to the inside of the cabin.[3][61]

During the crash two of the inflatable chutes deployed into the cabin.[1]:41–42 The first chute, which blocked the forward right exit, nearly suffocated a flight attendant and was deflated by a pilot with a fire axe from the cockpit.[62] The second chute expanded toward the center of the aircraft near the fire. It trapped a second flight attendant until a co-pilot deflated it with a dinner knife.[61]

Some passengers sitting at the rear of the aircraft escaped through the hole left by the missing tail section.[63]

Eyewitnesses to the crash included the cockpit crew and many passengers on board United Airlines Flight 885 (UA 885), a Boeing 747-400 that was holding on taxiway F, next to use the runway.[64][65] Others saw it from the terminal and near the airport.[65] At least one person recorded it on video.[66][67] Writing on the Professional Pilots Rumour Network internet forum, the first officer of UA 885 described what he saw:[68][68][69][70]

I then noticed at the apparent descent rate and closure to the runway environment the aircraft looked as though it was going to impact the approach lights mounted on piers in the SF Bay. The aircraft made a fairly drastic-looking pull up in the last few feet and it appeared and sounded as if they had applied maximum thrust. However the descent path they were on continued and the thrust applied didn't appear to come soon enough to prevent impact. The tail cone and empennage of the 777 impacted the bulkhead seawall and departed the airplane and the main landing gear sheared off instantly.

— United Flight 885 first officer, "Inside United Flight 885: A Pilot's Gripping Account", Chicago Business Journal[70]

Passengers and others praised the flight attendants' conduct after the crash. Cabin manager Lee Yoon-hye was last off the burning plane. San Francisco fire chief Hayes-White praised Lee's courage, saying, "She wanted to make sure that everyone was off. ... She was a hero."[71]

A firefighter who entered the cabin said that the back of the plane had suffered structural damage, but the seats near the front "were almost pristine" before the cabin fire.[12][72]


NTSB investigators at the crash site

The National Transportation Safety Board (NTSB) sent a team of 20 to the scene to investigate.[28][50] On 7 July 2013, NTSB investigators recovered the flight data recorder and cockpit voice recorder and transported them to Washington, D.C., for analysis.[73] Additional parties to the investigation include the Federal Aviation Administration, airframe manufacturer Boeing, engine manufacturer Pratt & Whitney, and the Korean Aviation and Railway Accident Investigation Board (ARAIB). ARAIB's technical adviser is Asiana Airlines.[28]

ARAIB tested the pilots for drug use four weeks after the accident; the tests proved negative.[1]:36

The NTSB's investigative team completed the examination of the airplane wreckage and runway. The wreckage was removed to a secure storage location at San Francisco International Airport. The Airplane Systems, Structures, Powerplants, Airplane Performance, and Air Traffic Control investigative groups completed their on-scene work. The Flight Data Recorder and Cockpit Voice Recorder groups completed their work in Washington. The Survival Factors/Airport group completed their interviews of the first responders.[74] The next phase of the investigation included additional interviews, examination of the evacuation slides and other airplane components, and a more detailed analysis of the airplane's performance.[12]

The final report into the crash was released on 24 June 2014.[75] The NTSB found that the "Mismanagement of Approach and Inadequate Monitoring of Airspeed led to the Crash of Asiana flight 214". The NTSB determined that the flight crew mismanaged the initial approach and that the airplane was well above the desired glidepath. In response, the captain selected an inappropriate autopilot mode (FLCH, or Flight Level Change) that, without the captain's awareness, resulted in the autothrottle no longer controlling airspeed. The aircraft then descended below the desired glidepath with the crew unaware of the decreasing airspeed. The attempted go-around was conducted below 100 feet, by which time it was too late. Over-reliance on automation and lack of systems understanding by the pilots were cited as major factors contributing to the accident.[76]

The NTSB further determined that the pilot's faulty mental model of the airplane's automation logic led to his inadvertent deactivation of automatic airspeed control. In addition, Asiana's automation policy emphasized the full use of all automation and did not encourage manual flight during line operations. The flight crew's mismanagement of the airplane's vertical profile during the initial approach led to a period of increased workload that reduced the pilot monitoring's awareness of the pilot flying's actions around the time of the unintended deactivation of automatic airspeed control. Insufficient flight crew monitoring of airspeed indications during the approach likely resulted from expectancy, increased workload, fatigue, and automation reliance. Lack of compliance with standard operating procedures and crew resource management were cited as additional factors.[77]

The NTSB reached the following final conclusion:

The National Transportation Safety Board determines that the probable cause of this accident was the flight crew's mismanagement of the airplane's descent during the visual approach, the pilot flying's unintended deactivation of automatic airspeed control, the flight crew's inadequate monitoring of airspeed, and the flight crew's delayed execution of a go-around after they became aware that the airplane was below acceptable glidepath and airspeed tolerances. Contributing to the accident were (1) the complexities of the autothrottle and autopilot flight director systems that were inadequately described in Boeing's documentation and Asiana's pilot training, which increased the likelihood of mode error; (2) the flight crew's nonstandard communication and coordination regarding the use of the autothrottle and autopilot flight director systems; (3) the pilot flying's inadequate training on the planning and executing of visual approaches; (4) the pilot monitoring/instructor pilot's inadequate supervision of the pilot flying; and (5) flight crew fatigue, which likely degraded their performance.[1]:129

Timeline of the accidentEdit

NTSB animation reconstructing the failed descent
Descent flight path

According to the NTSB, the weather was fair and the aircraft was cleared for a visual approach.[18][28]

The instrument landing system's vertical guidance (glide slope) on runway 28L was out of service, as scheduled, beginning on 1 June (and a Notice To Airmen (NOTAM) to that effect had been issued);[78] therefore, a precision ILS approach to this runway was not possible.

Preliminary analysis indicated that the plane's approach was too slow and too low. Eighty-two seconds before impact, at an altitude of about 1,600 feet (490 m),[15] the autopilot was turned off, the throttles were set to idle, and the plane was operated manually during final descent.[79] NTSB Chairman Deborah Hersman stated the pilots did not "set the aircraft for an auto-land situation ... They had been cleared for a visual approach and they were hand-flying the airplane," adding: "During the approach there were statements made in the cockpit first about being above the glide path, then about being on the glide path, then later reporting about being below the glide path. All of these statements were made as they were on the approach to San Francisco...Three seconds before the crash, someone in the cockpit called for the plane to abort the landing, or 'go around.' Then 1.5 seconds before impact, a different crew member again called for a 'go around.'" Both were spoken in the cockpit but not over the radio.[72][80]

The main landing gear of the aircraft hit the seawall short of the runway as the crew attempted to abort the landing and execute a go-around.[13] Based on preliminary data from the flight data recorder (FDR), the NTSB said the plane's airspeed on final approach fell to 34 knots below its target approach speed of 137 knots (254 km/h; 158 mph). A preliminary review of FAA radar return data did not show an abnormally steep descent curve,[28][81][82] although the crew did recognize that they began high on the final approach.[3] At a height of 38 metres (125 ft), eight seconds before impact, the airspeed had dropped to 112 knots (207 km/h; 129 mph). According to initial reports from the cockpit crew, the plane's autothrottle was set for the correct reference speed, but until the runway's precision approach path indicator (PAPI) showed them significantly below the glide path, the pilots were unaware the autothrottle was failing to maintain that speed. The instructor pilot stated that the PAPI indicated a deviation below the glide path at approximately 500 feet above ground level, and he attempted to correct it at that time. Between 500 and 200 feet, the instructor pilot also reported a lateral deviation that they attempted to correct.[16]

Flight 214 final approach airspeed and glide path (July 6 flight shown in red).

Seven seconds before impact, one pilot called for an increase in speed.[4][83] The FDR showed the throttles were advanced from idle at that time.[28] The instructor pilot reported he had called for an increase in speed, but that the pilot flying had already advanced the throttles by the time he reached for the throttles.[16] The sound of the stick shaker (warning of imminent stall) could be heard four seconds before impact on the cockpit voice recorder.[4] Airspeed reached a minimum of 103 knots (191 km/h; 119 mph) (34 knots below the target speed) three seconds before impact, with engines at 50% power and increasing.[28] The crew called for a go-around 1.5 seconds before impact.[4] At impact, airspeed had increased to 106 knots (196 km/h; 122 mph).[28][84]

Hersman said that the NTSB conducted a four-hour interview with each pilot, adding that the pilots were open and cooperative. She said both pilots at the controls had ample rest before they left South Korea and during the flight when they were relieved by the backup crew.[29]

All three pilots told NTSB investigators that they were relying on the 777's automated devices for speed control during final descent.[85] The relief first officer also stated to NTSB investigators that he had called out "sink rate" to call attention to the rate at which the plane was descending during the final approach.[3][86] This "sink rate" warning was repeated several times during the last minute of the descent.[87]

The pilot flying reported to Korean investigators that he was blinded by a bright light at 500 feet (35 seconds prior to impact).[3][88] The NTSB, calling the bright light's effect 'temporary', said the pilot flying did not believe it affected his ability to fly the aircraft, and no reference to any light was made by the other pilots during interviews or at the time, according to the cockpit voice recorder.[12][86][89]

Based on a preliminary review of FDR data, the NTSB stated there was no anomalous behavior of the engines, the autopilot, the flight director, or the autothrottle.[12][72] The autothrottle control was found to be in the "armed" position during documentation of cockpit levers and switches,[3][16][90] differing from both the "on" and "off" positions.[citation needed] Furthermore, the pilot flying's flight director (Primary Flight Display) was deactivated whereas the instructor pilot's was activated[16] (this may prove to be significant, as deactivating neither or both Flight Directors enables and forces an autothrottle "wake-up" whereas deactivating only one Flight Director inhibits an autothrottle "wake-up").[91][92]

All three fire handles were extended; these operate safety equipment intended to put out fires on the aircraft (a handle for each engine and the auxiliary power unit). The speedbrake lever was down, showing it was not being used.[34]

The flight data recorder (left) and cockpit voice recorder were recovered from the aircraft undamaged.

Hersman said: "In this flight, in the last 2.5 minutes of the flight, from data on the flight data recorder we see multiple autopilot modes and multiple autothrottle modes ... We need to understand what those modes were, if they were commanded by pilots, if they were activated inadvertently, if the pilots understood what the mode was doing."[29][93] Hersman has repeatedly emphasized it is the pilot's responsibility to monitor and maintain correct approach speed[94] and that the crew's actions in the cockpit are the primary focus of the investigation.[95][failed verification][96]

In response to media reports in South Korea that air traffic controllers had a shift change 30 seconds before the crash, Hersman said that the plane had been cleared to land over 30 seconds[97] before crashing and, "the tower actually called for the emergency and the emergency vehicles prior to the flight crew calling the tower for an emergency."[72]

The NTSB published a three-page preliminary report on August 7, 2013.[98]

NTSB use of social mediaEdit

NTSB Chair Deborah Hersman answers questions on July 7

Shortly after the accident, the US National Transportation Safety Board (NTSB) used Twitter and YouTube to inform the public about the investigation and quickly publish quotes from press conferences. NTSB first tweeted about Asiana 214 less than one hour after the crash. One hour after that, the NTSB announced via Twitter that officials would hold a press conference at Reagan Airport Hangar 6 before departing for San Francisco. Less than 12 hours after the crash, the NTSB released a photo showing investigators conducting their first site assessment.[99] On 24 June 2014, the NTSB published to YouTube a narrated accident sequence animation.[100]

Air Line Pilots AssociationEdit

On 9 July 2013, the Air Line Pilots Association (ALPA) criticized the NTSB for releasing "incomplete, out-of-context information" that gave the impression that pilot error was entirely to blame.[101][102]

NTSB Chairman Hersman responded: "The information we're providing is consistent with our procedures and processes ... One of the hallmarks of the NTSB is our transparency.[96] We work for the traveling public. There are a lot of organizations and groups that have advocates. We are the advocate for the traveling public. We believe it's important to show our work and tell people what we are doing."[103] Answering ALPA's criticism, NTSB spokeswoman Kelly Nantel also said the agency routinely provided factual updates during investigations. "For the public to have confidence in the investigative process, transparency and accuracy are critical," Nantel said.[104]

On 11 July 2013, in a follow-up press release without criticizing the NTSB, ALPA gave a general warning against speculation.[105]

South Korean investigationEdit

The South Korean government is investigating whether the crew followed procedures and how they were trained, according to a Ministry of Land, Infrastructure and Transport statement.[106]


Removal of the wreckage

The airport was closed for five hours after the crash.[5][11][37] Flights destined for San Francisco were diverted to Oakland, San Jose, Sacramento, Los Angeles, Portland (OR), and Seattle–Tacoma.[107] By 3:30 p.m. PDT, runway 1L/19R and runway 1R/19L (both of which run perpendicular across the runway of the accident) were reopened; runway 10L/28R (parallel to the runway of the accident) remained closed[5][37] for more than 24 hours.[108] The accident runway, 10R/28L, reopened on 12 July after being repaired. Asiana continues to serve the Seoul-San Francisco route; the flight has been renumbered to OZ212 and departs with a retimed schedule of 8.40pm instead of OZ214's 4.40pm departure.[109]

In the U.S., drug and alcohol tests are standard after air accidents, but this is not a requirement for pilots of foreign-registered aircraft, and the pilots were not tested immediately after the accident.[110] The lack of alcohol testing received much public attention and was critically discussed by various media and politicians after the accident.[111][112][113] Shortly after the accident, Congresswoman Jackie Speier stated that she will consider legislation to improve airline safety by requiring increased pilot training and mandatory drug and alcohol testing for international crews.[114]

The crash damaged Asiana's reputation[21][115][116][117] and that of South Korea's aviation industry following years of apparent improvements after a series of aircraft disasters in the 1980s and early 1990s.[118] Asiana shares fell on the first day of trading after the crash, by 5.8%.[119] Any insurance payment will not cover[better source needed] the loss of aircraft, litigation and other charges and erosion in passenger numbers following the accident, Cho Byoung Hee, an analyst at Kiwoom Securities Co., said in July 2013. As of August 2013, shares of the airline fell 2 percent to 4,530 won, the lowest price since April 5, 2010, in Seoul trading.[relevant? ][117]

Response from Asiana AirlinesEdit

In the hours after the accident, Asiana Airlines CEO Yoon Young-doo (윤영두; 尹永斗) said his airline had ruled out mechanical failure as the cause of the crash.[120] Later, he defended the flight crew, calling them "very experienced and competent pilots."[121][122] On 9 July Yoon apologized directly to the parents of the two victims,[123] then flew aboard Flight 214 to San Francisco, the same route as the crashed aircraft, to meet with NTSB officials.[124] Asiana gave flights to San Francisco to the families of the victims.[125]

Asiana Airlines announced on 29 July 2013, that it would retire flight numbers 214 and 213 on August 12, 2013. Flights from Incheon to San Francisco and the return leg would thenceforth operate as OZ212 and OZ211, respectively.[126]

Asiana Airlines officials said the airline would improve training for its pilots: in particular, for pilots learning to fly different types of aircraft, and in various skills such as making visual approaches and flying on autopilot.[127][128][129] Asiana officials also said they will seek to improve communications skills among crew members, introduce a system to manage "fatigue risk," set up separate maintenance teams for Boeing and Airbus planes, and improve safety management systems.[130]

On August 12, 2013, Asiana Airlines announced initial payouts to crash survivors of US$10,000, stating the survivors "need money to go to hospital or for transportation so we are giving them the $10,000 first," Asiana spokeswoman Lee Hyo Min said in a telephone interview. "Even if they are not hurt or they don't go to hospital, we will still give them this money." "The carrier may pay more after the U.S. National Transportation Safety Board completes its investigation into the accident. The families of those who died were paid more than $10,000 as an initial compensation," Lee said, without providing a specific figure.[117][131]

Response from the South Korean governmentEdit

South Korean transport ministry officials ordered Korean Air and Asiana to check engines and landing equipment on all 48 of their model 777 aircraft and announced that the government would conduct special inspections on the nation's eight carriers through August 25, 2013.[132] "The measures could include [changing] rules on training flights if needed," Deputy Minister for Civil Aviation Choi Jeong-ho told reporters.[133] The officials also said South Korea had no fatal air crashes between December 1999 and the July 2011 crash of an Asiana freighter.

Response from the San Francisco Fire DepartmentEdit

Chief of the San Francisco Fire Department Joanne Hayes-White stated that the department's 2009 ban on video recording devices has now been extended to include any devices mounted on helmets that record emergencies. Helmet-recorded images were taken at the crash scene and resulted in inquiries regarding the death of one victim struck by an emergency vehicle. No charges were filed for the accidental death involving the firetruck.[134]


On 15 July 2013, two Korean passengers filed a lawsuit against Asiana Airlines in a California federal court for "an extensive litany of errors and omissions" and improper crew training and supervision.[135] On the same day, 83 passengers filed a petition for discovery in Chicago, alleging a possible failure of the autothrottle system and malfunctioning evacuation slides and seat belts.[135][136][137] An additional lawsuit against Asiana Airlines and Boeing Aircraft Company was filed on August 9, 2013. In addition to alleging product defects, the suits focus on the training provided to the Asiana crew.[135][136][138]

Seventy-two passengers reached an undisclosed settlement that was filed in United States Federal court on 3 March 2015.[139] On the same day the Los Angeles Times reported that, "At least 60 lawsuits against the airline filed in the Northern District of California ... have not reached settlements," and "dozens of claims have been filed against the airline in China and South Korea and against Boeing in an Illinois state court."[139]

Asiana also initially announced it would file a defamation lawsuit against KTVU for having aired the Asiana Airlines KTVU prank, but withdrew from that course of action two days later.[140][141]

Legislative actionEdit

On 30 July 2013, an amendment to Transportation bill H.R. 2610 was adopted by voice vote for the transfer of $500,000 from the Next Generation Air Transportation System account to the air safety account to study implementing a verbal warning system for low air speed.[142]


On 25 February 2014, the U.S. Department of Transportation (DOT) fined Asiana Airlines US$500,000 for failing to keep victims and family of victims updated on the crash.[143]

In popular cultureEdit

False names as aired by KTVU

Mayday: Air Crash Investigation included Asiana Airlines Flight 214 in Episode 11, "Getting Out Alive" of Season 13. Another episode, Episode 2, "Terror in San Francisco" of Season 15 aired on 13 January 2016 and focused solely on the accident, as the previous episode studied a series of accidents and how passengers were able to escape.

San Francisco television station KTVU fell victim to "a prank"[144][145][146] in which then-news-anchor Tori Campbell reported a quartet of phonetic double entendres as the actual names of the flight crew. The names reported were Sum Ting Wong ("something['s] wrong"), Wi Tu Lo ("we['re] too low"), Ho Lee Fuk ("holy fuck"), and Bang Ding Ow (onomatopoeia for crashing sound and expression of pain). The prank has been described as racist and insensitive.[147][148][149]


Firefighters on the scene saw two of the three victims still alive after being thrown from the plane. The driver of the fire engine ran over them. The firefighter is reported to have said "She got run over... I mean, s— happens, you know?" Afterward the incident was reported by the firefighter to his San Francisco Fire Chief Joanne M. Hayes-White stating "Chief, there’s a woman there who’s been run over by one of our rigs." The chief only asked if the victim had been crushed, to which the firefighter replied "like someone dropped a pumpkin." Chief Hayes-White made a lengthy public statement lauding her firefighters for having "worked as best as it possibly could have" and deliberately omitted any mention of the collision for two days.[150]

See alsoEdit


  1. ^ a b c d e f g h i j k l m n o Descent Below Visual Glidepath and Impact With Seawall, Asiana Airlines Flight 214, Boeing 777-200ER, HL7742, San Francisco, California, July 6, 2013 (PDF). National Transportation Safety Board. June 24, 2014. NTSB/AAR-14/01. Retrieved January 16, 2016.
  2. ^ "HL-7742 – 06-Jul-2013 – RKSI / ICN – KSFO". FlightAware. Retrieved July 8, 2013.
  3. ^ a b c d e f g h i NTSB (July 10, 2013). "NTSB Press Briefing (no. 4)". Press briefing by NTSB chairman Deborah Hersman uploaded to YouTube. San Francisco, California: NTSB. Retrieved July 31, 2013.
  4. ^ a b c d e NTSB (July 7, 2013). "NTSB Press Briefing (no. 1)". Press briefing by NTSB chairman Deborah Hersman uploaded to YouTube. San Francisco, California: NTSB. Retrieved July 31, 2013.
  5. ^ a b c d e Hradecky, Simon (July 7, 2013). "Accident: Asiana B772 at San Francisco on Jul 6th 2013, touched down short of the runway, broke up and burst into flames". The Aviation Herald. Retrieved July 7, 2013.
  6. ^ "Where Asiana Flight 214 Came to Rest". The New York Times. July 6, 2013. Retrieved July 7, 2013.
  7. ^ "San Francisco crash Boeing 'tried to abort landing'". BBC News. July 7, 2013. Retrieved July 7, 2013.
  8. ^ a b "Asiana 777 (AAR214) crashes upon landing at SFO". FlightAware. July 6, 2013. Retrieved July 6, 2013.
  9. ^ Arkin, Daniel (July 6, 2013). "Boeing 777 crashes while landing at San Francisco airport". NBC News. Retrieved July 6, 2013.
  10. ^ Somaiya, Ravi (July 6, 2013). "Plane Crashes on Landing in San Francisco". The New York Times. Retrieved July 6, 2013.
  11. ^ a b c "Boeing 777 plane crash-lands at San Francisco airport". BBC News. July 7, 2013. Retrieved July 7, 2013.
  12. ^ a b c d e f NTSB (July 11, 2013). "NTSB Press Briefing (no. 5)". Press briefing by NTSB chairman Deborah Hersman uploaded to YouTube. San Francisco, California: NTSB. Retrieved July 31, 2013.
  13. ^ a b c Young, Kathryn M. (July 12, 2013). "NTSB completes work at Asiana 777 crash site; no systems anomalies found". Retrieved July 16, 2013.
  14. ^ "What happened with Asiana Flight 214?". Atlanta, Georgia: CNN. July 12, 2013. Retrieved August 2, 2013.
  15. ^ a b "Accident description (Type: Boeing 777-28EER, Operator: Asiana Airlines, Registration: HL7742, C/n / msn: 29171/553)". Aviation Safety Network. Flight Safety Foundation. July 6, 2013. Retrieved July 30, 2013.
  16. ^ a b c d e NTSB (July 9, 2013). "NTSB Press Briefing (no. 3)". Press briefing by NTSB chairman Deborah Hersman uploaded to YouTube. San Francisco, California: NTSB. Retrieved July 31, 2013.
  17. ^ Ahlers, Mike; Botelho, Greg (July 9, 2013). "NTSB: Asiana jet's landing gear slammed into seawall at San Francisco airport". CNN. Retrieved July 9, 2013.
  18. ^ a b c d Onishi, Norimitsu; Drew, Christopher; Wald, Matthew L. (July 7, 2013). "Terror on Jet: Seeing Water, Not Runway". The New York Times. Retrieved July 8, 2013.
  19. ^ Kirchner, Elyce. "Federal Records Show History of Problems with Escape Slides". NBC Bay Area. Retrieved September 21, 2013.
  20. ^ "Asiana Airline Evacuation Slides Were Faulty – And The Feds Knew". September 19, 2013. Retrieved September 21, 2013.
  21. ^ a b "Asiana jet crash further tarnishes Korean carrier's safety record". Reuters. July 7, 2013. Retrieved July 7, 2013.
  22. ^ Stagis, Julie. "Pratt & Whitney Engines Powered Asiana Airlines Plane". Hartford Courant. Archived from the original on July 8, 2013. Retrieved July 7, 2013.
  23. ^ "HL7742 Asiana Airlines Boeing 777-28E(ER) – cn 29171 / ln 553". Retrieved July 6, 2013.
  24. ^ "Asiana Plane Crash Lands: 'No Engine Problems'". Sky News HD. London, United Kingdom: BSkyB. July 7, 2013. Retrieved July 30, 2013.
  25. ^ Dan Nakaso (July 6, 2013). "Boeing 777 that crashed in SFO has a stellar reputation among pilots". San Jose Mercury News. San Jose, California: Media News Group. Retrieved July 27, 2013.
  26. ^ Norris, Guy (July 6, 2013). "NTSB Investigates Asiana 777 Accident In San Francisco". Aviation Week. McGraw Hill Financial. Retrieved July 30, 2013. The Asiana accident represents only the third hull loss for the 777 since the aircraft entered service in 1995. The Asiana accident is also the first involving a 777 which has resulted in a passenger fatality.
  27. ^ Asiana Airlines (July 7, 2013). "Information for Incident Involving Asiana Flight HL7742". Press Release (in English, Korean, and Chinese). Asiana Airlines. Archived from the original on July 26, 2013. Retrieved July 30, 2013.
  28. ^ a b c d e f g h NTSB (July 8, 2013). "NTSB Press Briefing (no. 2)". Press briefing by NTSB chairman Deborah Hersman uploaded to YouTube. San Francisco, California: NTSB. Retrieved July 31, 2013.
  29. ^ a b c Wilhelm, Steve (July 10, 2013). "NTSB focuses on pilots' communication, autopilot, in Asiana briefing". Puget Sound Business Journal. American City Business Journals. Retrieved July 26, 2013.
  30. ^ "Asiana Airlines crash: The pilots". ITV. July 7, 2013. Retrieved July 7, 2013.
  31. ^ Ng, Christina; Castellano, Anthony (July 9, 2013). "Two Asiana Airline Flight Attendants Thrown from Plane During Crash". ABC News. Retrieved July 9, 2013.
  32. ^ "Asiana Airlines Crash: Pilot Was in 9th Training Flight for Boeing 777". ABC News. Retrieved July 8, 2013.
  33. ^ "Pilot was at his first landing with a B777". July 8, 2013.
  34. ^ a b Chappell, Bill (July 9, 2013). "Asiana Crash Trip Was Pilot's First As Instructor, NTSB Says". Washington, District of Columbia: National Public Radio. Retrieved July 24, 2013.
  35. ^ Hull, Dana; DeBolt, David; Emmons, Mark; Sulek, Julia Prodis (July 10, 2013). "SFO crash: Three flight attendants ejected from plane strapped in their seats". San Jose Mercury News. San Jose, California: Media News Group. Retrieved July 27, 2013.
  36. ^ "VIDEO: Six Asiana flight attendants return home after plane crash". London: Retrieved September 21, 2013.
  37. ^ a b c Botelho, Greg (July 7, 2013). "2 die, 305 survive after airliner crashes, burns at San Francisco airport". CNN. Retrieved July 7, 2013.
  38. ^ "The 2 victims were heading for a camp". July 7, 2013. Archived from the original on July 11, 2013. Retrieved July 7, 2013.
  39. ^ "Asiana Crisis Management System". Asiana Airlines. Archived from the original on January 25, 2014. Retrieved July 7, 2013.
  40. ^ Dan Noyes (July 27, 2013). "I-Team: Firefighter who hit Asiana crash victim was driving alone". New York Daily News. Archived from the original on January 16, 2014. Retrieved May 28, 2019.
  41. ^ Branson-Potts, Hailey (July 19, 2013). "Asiana passenger likely killed by vehicle; fire chief 'heartbroken'". Los Angeles Times. Retrieved July 19, 2013.
  42. ^ Martinez, Michael; Hanna, Jason (July 19, 2013). "Coroner: Asiana Airline passenger killed by rescue vehicle, was alive at time". CNN. Retrieved July 19, 2013.
  43. ^ "SF City Attorney: Asiana Plane Crash Victim Already Dead When Run Over". CBS San Francisco. January 29, 2014. Retrieved March 8, 2014.
  44. ^ McCoy, Tryg; Carnes, Dale (January 17, 2014). "Accident Investigation Party Submission by the City and County of San Francisco under 49 CFR § 845.27" (PDF). CBS San Francisco. Retrieved March 8, 2014.
  45. ^ "Teenage girl killed in Asiana crash was hit by fire truck, S.F. police say". CBS Interactive, Inc. July 12, 2013. Retrieved July 14, 2013.
  46. ^ "3rd fatality in Asiana flight crash". CBS News. Associated Press. July 12, 2013. Retrieved July 12, 2013.
  47. ^ Botelho, Greg (July 12, 2013). "3rd person dies from Asiana crash, hospital says". CNN. Retrieved July 12, 2013.
  48. ^ Salonga, Robert (July 12, 2013). "SFO crash: Child dies at hospital, becomes third fatality of Asiana Airlines disaster". San Jose Mercury News. San Jose, California: Media News Group. Retrieved July 27, 2013.
  49. ^ "Flight 214 Crash: Six Remain In Critical Condition At SF General". The San Francisco Appeal. Appeal Media, LLC. July 6, 2013. Retrieved July 30, 2013.
  50. ^ a b Welch, William; Swartz, Jon M.; Strauss, Gary (July 6, 2013). "2 confirmed dead in San Francisco Airport crash". USA Today. Retrieved July 6, 2013.
  51. ^ KTVU and Wires (July 6, 2013). "Two dead, dozens injured in Boeing 777 crash". Oakland, CA: KTVU-TV. Archived from the original on October 25, 2014. Retrieved July 7, 2013.
  52. ^ Guyuan Kun (July 7, 2013). "More than 90 of the Asiana Airlines flight's passengers departed from Shanghai (韩亚失事航班90余名乘客由上海出发)". Xinhua News Agency (in Chinese). Archived from the original on January 25, 2014.
  53. ^ Staff writer(s) (July 7, 2013). "Why Nearly Half of Asiana Passengers Were Chinese". The Wall Street Journal. Retrieved September 25, 2015.
  54. ^ a b c "Two dead in Asiana plane crash are Chinese citizens, identified as teenage girls". South China Morning Post. Reuters. July 7, 2013. Retrieved July 7, 2013.
  55. ^ Yang, Sunny (July 7, 2013). "Asiana crash deaths ID'd as 2 Chinese teens". USA Today. Associated Press. Retrieved July 7, 2013. A teacher told Chinese television that there were 34 people traveling in the Jiangshan Middle School group — five teachers and 29 students.
  56. ^ a b Hunt, Katie (July 7, 2013). "Girls killed in crash were headed for camp". CNN. Retrieved July 8, 2013.
  57. ^ Chen, Stephen (July 8, 2013). "China mourns students from Zhejiang school killed in San Francisco air crash". Hong Kong: Agence France-Press. Retrieved August 7, 2015.
  58. ^ Bailey, Brandon (July 13, 2013). "Third teenager who died in the Asiana crash attended same school as other 2 victims". San Jose Mercury News. San Jose, California: Media News Group. Retrieved July 27, 2013.
  59. ^ "Biographies of 3 Chinese SF airliner crash victims". Associated Press. July 15, 2013. Retrieved July 20, 2013.
  60. ^ William M. Welch; Chris Woodyard; Doug Stanglin, eds. (July 8, 2013). "NTSB: Jet was traveling below target speed before crash". USA Today. Retrieved July 8, 2013.
  61. ^ a b c Kim, Victoria (July 8, 2013). "Asiana flight attendant, last person off jet, describes ordeal". Los Angeles Times. Retrieved July 13, 2013.
  62. ^ Lee Romney, Victoria Kim & Kate Mather (July 8, 2013). "After Asiana jet crash, a dramatic race to rescue passengers". Los Angeles Times. Retrieved July 18, 2013.
  63. ^ Dearen, Jason; Lowy, Joan (July 8, 2013) [July 6, 2013]. "Officials probe why crashed SF jet flew too slow". Seattle Times. Associated Press. Retrieved July 13, 2013.
  64. ^ Lazare, Lewis (July 8, 2013). "United Flight 885: Too close for comfort?". Chicago Business Journal. Retrieved July 10, 2013.
  65. ^ a b Romney, Lee; Reston, Maeve; Groves, Martha (July 6, 2013). "San Francisco plane crash: Onlookers stunned, stranded, delayed". LA Times. Retrieved July 9, 2013.
  66. ^ Smith, Matt; Hall, Lindy (July 8, 2013). "'Oh, Lord have mercy': Witness captures fatal jet crash". CNN. Retrieved July 8, 2013.
  67. ^ Hayes, Fred. Man catches plane crash on camera (YouTube). CNN. Retrieved July 8, 2013.
  68. ^ a b Noyes, Dan (July 9, 2013). "United Airlines pilot witnesses Asiana Flight 214 crash". KGO-TV. KGO-TV, ABC. Archived from the original on July 18, 2013. Retrieved July 11, 2013.
  69. ^ Boeing 777 crash at San Francisco International. Getty Images. Retrieved July 9, 2013.
  70. ^ a b Lazare, Lewis (July 9, 2013). "Inside United Flight 885: A pilot's gripping account". Chicago Business Journal. Retrieved July 9, 2013.
  71. ^ Mutzbaugh, Ben (July 8, 2013). "Asiana flight 214 flight attendants applauded as 'heroes'". USA Today. Retrieved July 9, 2013.
  72. ^ a b c d Dan Nakaso (July 11, 2013). "NTSB wants to expedite investigation of Asiana Flight 214 crash". San Jose Mercury News. San Jose, California: Media News Group. Retrieved July 27, 2013.
  73. ^ Yoon, Julie; Bruton, F. Brinley; DeLuca, Matthew (July 7, 2013). "NTSB: Officials recover black boxes from San Francisco crash site". NBC News. Retrieved July 7, 2013.
  74. ^ "NTSB issues investigative update on crash of Asiana Flight 214". NTSB Press Release. NTSB. July 15, 2013. Retrieved July 26, 2013.
  75. ^ Sze, Kristen (June 19, 2014). "Former NTSB Chair Deborah Hersman shares insights ahead of Asiana SFO crash anniversary". Retrieved August 19, 2016.
  76. ^ "Archived copy". Archived from the original on June 25, 2014. Retrieved 2014-06-25.CS1 maint: archived copy as title (link)
  77. ^ "Crash of Asiana Flight 214 Accident Report Summary". Archived from the original on June 25, 2014. Retrieved June 24, 2014.
  78. ^ "KSFO San Francisco Intl". PilotWeb. Federal Aviation Administration. Archived from the original on September 29, 2013. Retrieved July 7, 2013. 06/005 SFO navigation instrument landing system Runway 28L glide path out of service with effect from or effective from 1306011400-1308222359
  79. ^ Scott, Alwyn (July 9, 2013). "Timeline: Final moments of Asiana Airlines Flight 214 before crash". Reuters. Retrieved July 31, 2013.
  80. ^ Chelsea J. Carter, Mike Ahlers and Ed Payne (July 12, 2013). "NTSB: 2 Asiana pilots call for landing to be aborted". Atlanta, Georgia: CNN. Retrieved July 31, 2013.
  81. ^ Bowens, Dan (July 7, 2013). "NTSB: Asiana flight flew too slow before crash". MyFox New York. Retrieved July 8, 2013.
  82. ^ This was in response to a chart showing an abnormal descent rate, that was later corrected. "An Uneven Descent". The New York Times. July 7, 2013. Retrieved October 27, 2013. The corrected data show that the plane descended 200 feet in eight seconds, not 600 feet in nine seconds.
  83. ^ "San Francisco crash Boeing 'tried to abort landing'". BBC News. July 8, 2013. Retrieved July 8, 2013.
  84. ^ Chappell, Bill (July 8, 2013). "Asiana Crash: Plane Was 34 Knots Below Target Speed, NTSB Says". Washington, District of Columbia: NPR. Retrieved July 9, 2013.
  85. ^ Weikel, Dan; Vartabedian, Ralph; Nelson, Laura (July 9, 2013). "Asiana Airlines pilots say auto-throttle didn't maintain landing speed". Los Angeles Times. Retrieved July 10, 2013.
  86. ^ a b Alan Levin, Kyunghee Park & Rose Kim (July 11, 2013). "Asiana Evacuation Delayed as Fire Erupted Outside Crash". Bloomberg News. Retrieved July 26, 2013.
  87. ^ "San Francisco Crash: Pilot Warnings 'Ignored'". Sky News HD. London, United Kingdom: BSkyB. July 10, 2013. Retrieved July 30, 2013.
  88. ^ "San Francisco Crash Pilot 'Blinded By Light'". Sky News HD. London, United Kingdom: BSkyB. July 11, 2013. Retrieved July 30, 2013.
  89. ^ Ohlheiser, Abby (July 11, 2013). "A Flash of Light Didn't Blind the Asiana 214 Pilot". The Atlantic Wire. Retrieved July 12, 2013.
  90. ^ "Asiana 214 pilot realised plane flying too low". BBC News. July 9, 2013. Retrieved July 9, 2013.
  91. ^ "NTSB: Asiana pilots say they used automatic speed controls for landing that went tragically wrong in San Francisco". CBS News. CBS/Associated Press. July 9, 2013. Retrieved July 31, 2013.
  92. ^ The Associated Press reported,

    ... the captain flying the plane, Lee Kang Kuk, 45, who was new to the 777, inadvertently deactivated the autothrottle, putting it into a hold mode. A training captain who was sitting next to Kuk in the right seat didn't notice the error, and then compounded it by turning off only one of two other key systems for managing the flight [by turning-off the pilot flying's Primary Flight Display, while maintaining his own, thereby requiring the pilot flying to continuously scan his "six-pack" backup flight instruments to know how his airplane was performing, rather than by concentrating on his single Primary Flight Display]. Both [Primary Flight Display] systems are supposed to be on or off, but not one on and one off [and should one be on and the other off, then the autothrottle "wake-up" function is disabled].

  93. ^ Mendoza, Martha; Lowy, Joan (July 9, 2013). "NTSB: Pilots of Asiana 214 relied on automatic speed control, as plane flew too slow, too low". Associated Press. Archived from the original on August 20, 2013. Retrieved October 27, 2013.
  94. ^ Botelho, Greg (June 17, 2013). "Asiana pilot was halfway through 777 training". CNN. Archived from the original on July 14, 2013. Retrieved July 13, 2013.
  95. ^ Johnston, Ian (July 9, 2013). "Asiana Airline chief says it plans to improve pilot training after San Francisco crash". NBC News. Retrieved July 10, 2013.
  96. ^ a b Young, Kathryn M. (July 10, 2013). "Asiana Flight 214 pilots' actions scrutinized". Retrieved July 16, 2013.
  97. ^ Cleared to land at 11:27:10, 40 seconds before impact
  98. ^ "Preliminary Report Aviation – DCA13MA120". National Transport Safety Board. August 7, 2013.[permanent dead link]
  99. ^ Derner, Phil (July 8, 2013). "The NTSB Utilizes Social Media During Asiana 214 Investigation". Retrieved August 21, 2013.
  100. ^ Animation of Asiana Flight 214 accident sequence on YouTube
  101. ^ Wald, Matthew (July 9, 2013). "Inquiry Suggests Chance That Mechanical Failure Had Role in Crash". The New York Times. Archived from the original on July 11, 2013. Retrieved July 9, 2013.
  102. ^ "ALPA Asks for Answers to Key Questions in Accident Investigation" (Press release). ALPA News. July 9, 2013. Archived from the original on July 15, 2013. Retrieved July 9, 2013.
  103. ^ Bachman, Justin. "In Probing the Asiana Crash, NTSB Gets Busy on Twitter". Businessweek. Retrieved July 13, 2013.
  104. ^ Alwyn Scott (July 9, 2013). "Pilots union says probe of Asiana crash revealed too much, too fast". Reuters. Archived from the original on July 14, 2013. Retrieved July 14, 2013.
  105. ^ "ALPA Reaffirms Commitment to Finding All Factors in Crash of Asiana Flight 214". ALPA. July 11, 2013. Archived from the original on January 25, 2014. Retrieved July 23, 2013. As contributing factors continue to be discovered in the Asiana Flight 214 accident investigation, ALPA again warns about the dangers of speculation based on incomplete data.
  106. ^ Levin, Alan. "Korean Pilots Avoided Manual Flying, Former Trainers Say". Retrieved July 24, 2013.
  107. ^ "Plane crash at San Francisco airport, 2 dead". CBS News. Associated Press. July 6, 2013. Retrieved July 6, 2013.
  108. ^ Nelson, Laura J; Romney, Lee (July 7, 2013). "Third of four runways reopens at SFO, officials say". Los Angeles Times. Retrieved July 7, 2013.
  109. ^ "SFO Runway Involved In Asiana 214 Crash Reopens". CBS. July 12, 2013. Retrieved July 12, 2013.
  110. ^ Lowy, Joan (July 10, 2013). "NTSB: Pilots of Asiana 214 relied on automatic speed control, as plane flew too slow, too low". Star Tribune. Minneapolis: Star Tribune Media Company LLC. Retrieved July 30, 2013.
  111. ^ Macintosh, Jeane (July 10, 2013). "Four foreign pilots of Asiana Flight 214 not tested for drugs or alcohol". Retrieved August 21, 2013.
  112. ^ Klein, Karin (July 9, 2013). "A lame reason for not drug-testing Asiana pilots – Los Angeles Times". Retrieved August 21, 2013.
  113. ^ Alex Davies (July 9, 2013). "Asiana 214 Pilots Not Drug Tested". Business Insider. Retrieved August 21, 2013.
  114. ^ "Airline Safety". Retrieved August 21, 2013.
  115. ^ Hawon, Jung (July 9, 2013). "Crash 'mars Asiana's image' after years of efforts". AFP. Retrieved July 10, 2013.
  116. ^ Riley, Charles (July 7, 2013). "Asiana Airlines shares tumble after San Francisco crash". CNN Money. Retrieved July 10, 2013.
  117. ^ a b c Evans, Rachel. "Asiana Offers San Francisco Crash Victims $10,000 Payout". Bloomberg. Retrieved August 21, 2013.
  118. ^ Sang-Hun, Choe (July 8, 2013). "Asiana President Says Pilot Was in Training". The New York Times. Retrieved July 10, 2013.
  119. ^ Akane Otani (July 9, 2013). "Shares of Asiana Airlines decline after San Francisco crash". The Christian Science Monitor. Retrieved August 3, 2013.
  120. ^ Jin, Hyunjoo; Chance, David (July 7, 2013). Tait, Paul (ed.). "Plane, engines not at fault in Asiana crash: CEO". Reuters. Retrieved July 9, 2013.
  121. ^ France-Presse, Agence (July 9, 2013). "Asiana CEO defends 'very experienced' crash pilots". Retrieved July 9, 2013.
  122. ^ "Asiana chief defends "very experienced" crash pilots". Channel NewsAsia. AFP/nd. July 9, 2013. Retrieved July 9, 2013.
  123. ^ "Asiana Airlines CEO Apologizes to Families". NBC Bay Area News. July 9, 2013. Retrieved July 9, 2013.
  124. ^ Shih, Gerry (July 9, 2013). "Asiana Airlines CEO in San Francisco for crash probe". Reuters. Retrieved July 9, 2013.
  125. ^ "Asiana Airlines flying in victims' families from overseas". July 7, 2013. Archived from the original on July 10, 2013. Retrieved July 13, 2013.
  126. ^ Kate Mather (August 6, 2013). "Asiana Airlines to change number of Seoul-S.F. flight after crash". Los Angeles Times. Retrieved August 21, 2013.
  127. ^ "Asiana Airline to improve pilot training after San Francisco plane crash – Society – Panorama – Armenian news". Retrieved July 13, 2013.
  128. ^ "Asiana Airlines plans to improve pilots training". July 6, 2013. Archived from the original on January 25, 2014. Retrieved July 13, 2013.
  129. ^ "Asiana Airline chief says it plans to improve pilot training after San Francisco crash – U.S. News". NBC News. July 9, 2013. Retrieved July 13, 2013.
  130. ^ "Asiana says to beef up training of pilots shifting to new jets". July 15, 2013. Retrieved July 16, 2013.
  131. ^ Nakaso, Dan (August 12, 2013). "Asiana denies responsibility in SFO crash, offers surviving passengers $10,000 each". San Jose Mercury News. Retrieved August 19, 2013.
  132. ^ Kyunghee Park, Bloomberg (July 8, 2013). "Asiana Airlines crash may spur Korean air travel regulations overhaul". Skift. Retrieved July 13, 2013.
  133. ^ Kong, Kanga (July 10, 2013). "South Korea Inspects Airlines After Asiana Crash". The Wall Street Journal. Retrieved July 13, 2013.
  134. ^ Mather, Kate (October 18, 2013). "No charges to be filed in death of Asiana Airlines crash survivor". Los Angeles Times. Retrieved October 27, 2013.
  135. ^ a b c Dye, Jessica (July 17, 2013). "Passengers eye legal action against Boeing, Asiana over crash". Reuters. Retrieved July 17, 2013.
  136. ^ a b Kim, Victoria; Mather, Kate (July 16, 2013). "83 Asiana victims file legal papers against Boeing, cite malfunction". Los Angeles Times. Retrieved July 16, 2013.
  137. ^ "Passengers begin legal action against Boeing after Asiana Airlines crash". Cable News Network. July 16, 2013. Retrieved July 16, 2013.
  138. ^ Pitre, Frank M. (August 9, 2013). "Copy of complaint: US District Court, Northern District of California Case#CV133684 (Filing only)" (PDF). Cotchett, Pitre & McCarthy, LLP. Retrieved August 13, 2013.
  139. ^ a b Hamilton, Matt (March 3, 2015). "Asiana crash: 72 passengers settle lawsuits against airline". Los Angeles Times. Retrieved September 25, 2015.
  140. ^ "Asiana Airlines confirms it will sue KTVU-TV over broadcast of racist fake pilot names". CBS News. Retrieved July 15, 2013.
  141. ^ "Asiana Airlines not to sue U.S. TV station". Retrieved July 17, 2013.
  142. ^ "H.Amdt.423 to H.R.2610, 113th Congress (2013–2014)". United States Legislative Information. Washington, District of Columbia: United States Congress. July 30, 2013. Retrieved August 1, 2013. Sponsor: Rep. Speier, Jackie [D-CA-14] (Offered 07/30/2013)
  143. ^ Nakaso, Dan (February 25, 2014). "Asiana Airlines hit with unprecedented fine in response to fatal SFO crash". The Mercury News. Retrieved February 26, 2014.
  144. ^ "Asiana pilot names: NTSB intern 'no longer with agency,' report says". Los Angeles Times. July 15, 2013. Retrieved June 23, 2016.
  145. ^ Philip Matier; Andrew Ross (July 24, 2013). "KTVU firings over airing of prank Asiana pilots' names". San Francisco Chronicle. Hearst Corporation. Retrieved September 17, 2016.
  146. ^ "The Craziest Things News Anchors Have Said And Done On Air – Page 29 of 66 – trendchaser". KTVU via Trend-Chaser. July 6, 2013. Retrieved March 19, 2017. Includes screen-grab of the prank names.
  147. ^ Engel, Pamela. "NTSB Intern 'Erroneously' Confirmed Racist Asiana Pilot Names To KTVU Station". Business Insider.
  148. ^ Abad-Santos, Alexander (July 12, 2013). "No, These Racist 'Asian' Names Aren't Really the Pilots of Asiana Flight 214". The Atlantic.
  149. ^ Mullin, Joe (July 24, 2013). "TV station tries—and fails—to use copyright to hide its racist news blunder". Ars Technica.
  150. ^ "Firefighter said "s— happens" after girl run over at SFO in 2013 Asiana crash | Mercury News". Mercury News. Retrieved July 7, 2018.

External linksEdit