Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Air Crash Response topic
No spam. Unsubscribe anytime.
Airport officials detail Asiana Flight 214 response, call for clearer EOC roles and better tools
Summary
Airport staff reviewed the July 6 Asiana Flight 214 crash response: 307 aboard (304 survived), rapid mutual‑aid and unified command helped, and officials recommended clarifying EOC roles, improving WebEOC use, better public information coordination and enhanced plans for unaccompanied minors.
Airport officials presented an after‑action summary of the July 6 Asiana Flight 214 accident, describing response outcomes and a set of recommended changes to emergency procedures.
Rob Forrester, speaking for airport operations, summarized the accident and immediate aftermath: a Boeing 777 struck a retaining wall on approach to Runway 28 Left; the aircraft came to rest off the runway. “The fact that 304 of those 307 passengers survived the crash was really miraculous,” Forrester said, and he credited rapid coordination among airfield safety officers, fire department responders and mutual‑aid partners for survivor care and evacuations.
Forrester described a phased after‑action process that focused first on recognizing responders and collecting firsthand accounts, then on the response phase, recovery phase (airfield clearance and runway reopening) and medical/family assistance. Immediate operational successes included reopening two crossing runways within four hours and restoring full airport operations within six days while coordinating with the NTSB.
Recommendations in the consultant’s final report include better defining the airport EOC’s role in regional coordination, fuller use of WebEOC for information sharing, improved integration of public information officers and social media management, designation of an EOC medical‑operations coordinator, and advance planning for passenger support—highlighting the need for layered support for unaccompanied minors. Forrester said the airport has already acted on multiple items and is tracking implementation in an action‑item log.
