FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Hawaiian Airlines Flight 56

13 Aug 2018 · Los Angeles, CA, United States

Airbus A321-271N · Accident: abnormal runway contact during landing

From Kahului International Airport (PHOG) to Los Angeles International Airport (KLAX)

Report a problem

Event

NTSB case
DCA18CA283
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Airline
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Airbus A321-271N

Aircraft type
Airbus A321
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N204HA
Onboard fatalities
Unknown
Route
From Kahului International Airport (PHOG), Maui, HITo Los Angeles International Airport (KLAX), Los Angeles, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 121: Air Carrier
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · flare/touchdown
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Abnormal runway contact
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Aircraft › Aircraft systems
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On August 13, 2018, about 1645 pacific daylight time, Hawaiian Airlines flight 56, an Airbus A321, N204HA, experienced a tail strike during landing at Los Angeles International Airport (KLAX), Los Angeles, California. There were no injuries to the 197 passengers and crew onboard. The airplane sustained substantial damage. The domestic passenger flight was operating under 14 Code of Federal Regulations Part 121 from Kahului Airport (PHOG), Kahului, Hawaii, to KLAX. The first officer (FO) was the pilot flying and the captain was the pilot monitoring. According to the flight crew, they received a GPWS Fail message on the electronic centralized alert monitoring (ECAM) at about 1,500 feet altitude above the ground (agl) after the airplane was established on the ILS 6R approach. The flight crew conducted the appropriate ECAM actions, which only required them to turn off the ground proximity warning system (GPWS) and continued the approach. As the airplane descended through about 50 feet agl, the FO realized the electronic automatic altitude callouts were not being provided by the airplane system but did not have time to react. The airplane touched down firmly, bounced, and the pitch attitude increased before it was arrested by the FO, resulting in the tail section contacting the runway. Post flight examination of the airplane found damage to the aft lower skin, as well as several deformed stringers, tie clips, and frames. During the approach, the crew did not receive any automated altitude callouts that are determined by the radio altimeter (RA). The crew only received the “100 above” and “minimums” callouts, both of which are based on barometric altitude. Visual meteorological conditions prevailed with light winds at the time of the approach resulting in the airplane descending over calm water. In February 2018 (updated on August 6, 2018) the manufacturer released a Flight Operations Transmission (FOT) and an Operations Engineering Bulletin in July 2018 referencing “No RA Available During Approach Over Water”. The FOT indicated that a new RA had abnormal behavior if the airplane approach is over a flat-water area and may not be available. Subsequent to the accident, the operator issued a Memorandum to Pilots that described the circumstances of the accident and the FOT and issued an Operations Engineering Bulletin, which detailed the required procedures if no RA is available.

Probable cause

a tailstrike caused by inappropriate recovery technique after a bounced landing. Contributing to the accident was the failure of the radio altimeter, caused by the approach being over calm/flat water, that was not recognized by the flight crew.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA18CA283
Event ID
20180905X90334
Case number
DCA18CA283
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 33dbcc123bbd7859b1d2fbc99e34f7ea355986699037907bb09ee7de036285c5; retrieved 2026-09-16T08:12:45.652Z.