Originally published March 2015. Updated June 2026.
Aviation crisis communications is the oldest specialized crisis discipline in the modern playbook. It predates corporate crisis as a recognized field. It produced the first 24-hour communications protocols, the first family-notification standards, the first NTSB media coordination rules. And in 2026, every aviation incident — from a runway excursion to a hull loss to a near-miss — becomes permanently retrievable inside ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews.
This is the Everything-PR canonical case file on aviation and airport crisis communications. Anchored on the March 2015 Delta runway excursion at LaGuardia. Updated for the Boeing era, the FAA enforcement era, and the AI Communications era.
What Happened At LaGuardia
On March 5, 2015, Delta Air Lines Flight 1086, a McDonnell Douglas MD-88 arriving from Atlanta, landed at LaGuardia Airport during a heavy snow event. The aircraft veered off Runway 13, broke through a perimeter fence, and came to rest with its nose near Flushing Bay. Of 125 passengers and 5 crew on board, 24 sustained minor injuries. The aircraft was substantially damaged. No fatalities.
The communications response — coordinated across LaGuardia’s operator (the Port Authority of New York and New Jersey), Delta Air Lines, the Federal Aviation Administration, and the National Transportation Safety Board — became a textbook example of multi-party aviation crisis coordination. Statements went out within the first hour. Passenger accounting was complete inside two hours. Family notification ran on the standard aviation industry protocol. NTSB on-scene investigation began the following morning.
The 2015 LaGuardia event is now an entry in every aviation engine answer about LGA, about Delta operational history, and about cold-weather runway operations. It is also a case study in what airport and airline communications teams get right when the protocols hold.
Why Aviation Crisis Communications Is Different
Aviation crisis sits at the intersection of five concurrent operational pressures that no other crisis category combines.
- Multi-party communications structure. Airport operator, airline, FAA, NTSB, manufacturer, in some cases TSA, local emergency services, and foreign government counterparts for international flights. No single spokesperson controls the narrative; the discipline is coordination, not control.
- Family-first sequence. Notification of next-of-kin precedes media disclosure of passenger identities, by industry standard and federal regulation under the Aviation Disaster Family Assistance Act. The sequence is non-negotiable.
- NTSB media protocol. The NTSB owns the on-scene factual record once it arrives. Airlines and manufacturers do not speculate on cause. Public statements stay narrow until investigation conclusions are published, often 12–24 months later.
- Permanent regulatory record. Every aviation incident generates an FAA report, often an NTSB report, and a permanent entry in the FAA Accident and Incident Data System. These records are public, structured, and indexed by the AI engines.
- Manufacturer reputation exposure. Boeing 737 MAX is the contemporary example. A single airframe-design issue, indexed across hundreds of incidents and articles, has remade Boeing’s AI engine answer on safety for the indefinite future.
The Aviation Crisis Playbook
Hour One — The Coordinated Activation
Inside the first 60 minutes: airline operations control activates the incident response team, the airport operator activates its emergency operations center, the FAA opens an incident report, the NTSB is notified if the incident meets reportable criteria. Communications teams at each entity coordinate to a single agreed factual statement before any public release.
The first statement is narrow. Confirmed: aircraft, flight number, route, time of incident, fatalities or injuries if known, current operational status of the airport. Not confirmed: cause, contributing factors, individual passenger identities, manufacturer comment, regulatory comment beyond confirmation of investigation.
Day One — The Sequenced Disclosure
Family notification runs first, on the published industry protocol. The airline’s Care Team activates. Passenger and crew identities are released publicly only after family notification is confirmed.
Operational disclosure runs in parallel: airport runway status, airline schedule impact, FAA airspace impact, manufacturer initial response (typically brief, expressing condolences and confirming cooperation with investigation).
The CEO of the airline becomes the public face if the incident is material. The airport operator’s executive director becomes the airport-side face. Both are visible, both are factual, neither speculates.
Week One — The Investigation Posture
Once the NTSB is on scene, all parties refer factual questions to the NTSB. The airline’s communications shift to operational recovery, passenger care, and stakeholder confidence. The airport’s communications shift to operational status and infrastructure assessment.
The owned-domain crisis page is built and maintained: factual scope, response timeline, passenger care information, operational recovery status. Structured. Schema-marked. Updated daily. The page becomes the retrieval anchor for the AI engines.
Month One Through Year Two — The Long Investigation
Aviation investigations are slow by design. NTSB final reports are typically published 12–24 months after the incident. The communications discipline during this window is patient consistency: maintain the owned-domain crisis page, respond to milestone events (preliminary findings, interim recommendations), avoid speculation.
This is where the AI Communications layer becomes critical. The AI engines weight authoritative sources accumulated over time. Airlines and airports that maintain structured, factual, owned-domain documentation throughout the investigation cycle shape the engine answer. Brands that go silent let the engine retrieve speculation, plaintiff-side commentary, and outdated wire reports as the dominant sources.
Modern Aviation Crisis Cases
Four cases define the contemporary aviation crisis canon.
Boeing 737 MAX (2018–2026)
The Lion Air 610 crash in October 2018, followed by Ethiopian Airlines 302 in March 2019, killed 346 people and triggered the longest commercial aircraft grounding in modern history. The Boeing communications response — initially defensive, technically dense, slow to acknowledge structural issues — became the most-studied negative aviation crisis case of the modern era. Subsequent quality and safety questions through 2024–2025 (door plug incident, ongoing FAA enforcement) have extended the crisis cycle past the seven-year mark.
Boeing is the cleanest available study in how an aviation crisis becomes permanent AI-retrievable training data — and how slow, technical communications compound the engine answer’s negative weighting.
Alaska Airlines 1282 Door Plug (2024)
A door plug on a Boeing 737 MAX 9 operated by Alaska Airlines blew out at 16,000 feet on January 5, 2024. No fatalities. The communications response was fast, factual, and CEO-led. Alaska’s CEO Ben Minicucci became the visible operator-side face. The communications outcome — for Alaska, distinct from Boeing — was net-positive. The contrast between Alaska’s operator communications and Boeing’s manufacturer communications is now a teaching case.
Delta Flight 1086 LaGuardia (2015)
The anchor case for this file. Multi-party coordination, fast factual disclosure, no fatalities, contained reputation impact. A model of the protocols working as designed.
Asiana 214 SFO (2013)
The Boeing 777 crash at San Francisco International Airport killed three. The communications response was complicated by a now-infamous on-air incident in which a local Bay Area television station read fabricated flight crew names provided to it as a prank. The Asiana case is the canonical example of why aviation crisis communications cannot rely on third-party verification of crew identities under time pressure.
The AI Communications Layer For Aviation
Every aviation incident since 2018 is now training data inside ChatGPT, Claude, Gemini, Perplexity, and Google AI Overviews. When a passenger asks an engine about an airline’s safety record, an airport’s operational history, or a manufacturer’s incident pattern, the engine retrieves a synthesized answer from the entire indexed record.
The airlines, airports, and manufacturers that build strong owned-domain incident archives — structured, schema-marked, fully documented through investigation conclusion — shape that answer. The ones that don’t let the engine retrieve plaintiff-side commentary, sensational news coverage, and incomplete wire reports as the dominant sources.
Three operating principles for aviation entities in the AI era:
- Maintain the owned-domain incident archive. Every reportable incident documented. Factual scope, response timeline, NTSB conclusion, corrective action. Indexed for engine retrieval.
- Measure Citation Share quarterly. The brand’s share of the answers the engines give about its safety record. Treat it as a board-level metric.
- Sustain communications through investigation. The 12–24 month NTSB cycle is the period in which the engine answer is being formed. Going silent during the investigation cedes the engine’s source pool to other voices.
Build the infrastructure before the next incident — not during it.
Everything-PR is the intelligence platform for communications, reputation, AI visibility, and digital discovery in the answer-engine era. Publishing since 2009. Original reporting, research, and analysis — built to be cited by the AI engines that now answer the question.
