FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Airlines Flight 627

15 Jun 2019 · Newark, NJ, United States

Boeing 757 224 · Accident: hard landing

From Denver International Airport (KDEN) to Newark Liberty International Airport (KEWR)

Report a problem

Event

NTSB case
DCA19CA167
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

Boeing 757 224

Aircraft type
Boeing 757
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
N26123
Onboard fatalities
Unknown
Route
From Denver International Airport (KDEN), Denver, COTo Newark Liberty International Airport (KEWR), Newark, NJ
Aircraft age
About 22 years (built 1997)
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
Hard landing
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

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

On June 15, 2019, about 12:55 eastern daylight time (EDT), United Airlines flight 627, a Boeing 757-224, N26123, experienced a hard landing at Newark International Airport (KEWR), Newark, New Jersey. There were no injuries to the 172 passengers and crew onboard, and the airplane received substantial damage. The flight was operating under Title 14 Code of Federal Regulations Part 121 as a regularly scheduled domestic passenger flight from Denver International Airport (KDEN), Denver, Colorado. The first officer (FO) was the pilot flying, and the captain was pilot monitoring. The takeoff, cruise, and decent were normal. The captain stated that it was an Initial Operating Experience (IOE) flight for the first officer. The auto speed brake system on the airplane was deferred in accordance with the Minimum Equipment List, and had been briefed, and all checklists had been completed. The captain stated that the FO flew a “solid” approach profile with few minor airspeed deviations, all of which were corrected immediately. The crew stated that during the descent to runway 22L the wind became gusty (220 degrees at 14 kts, gusting to 22 kts), and they increased the VREF speed in accordance with company procedures. At 500 feet, the airplane was on profile, on speed and stable. According to the crew the initial touchdown was smooth, on centerline, and in the touchdown zone. Upon touchdown on the main wheels, the captain manually deployed the speed brakes and the nose pitched up. To avoid a tailstrike, the captain said she physically blocked the yoke from moving back and instructed the FO to pitch forward. The airplane then bounced on the runway. The airplane was equipped with a L-3/Fairchild FA2100 Flight Data Recorder (FDR). FDR data showed that at 12:54:54 EDT, the airplane was on final approach to runway 22L with the autopilot off, glideslope mode engaged, and both flight directors on. At 12:55:14 EDT, with a pitch angle of 2.8 degrees, and the speed brake handle in the down (unarmed) position, the main landing gear (MLG) weight-on-wheels (WOW) parameter changed to GROUND. At 12:55:16 variations in the vertical acceleration, pitch, elevator, and control column parameters increased in magnitude. At 12:55:17, MLG WOW parameter changed back to AIR for one second, then back to GROUND for one second, then back to AIR for one second, before finally cycling back to GROUND. At 12:55:20 the nose gear WOW indicated GROUND for the first time, along with the largest magnitude vertical acceleration of 1.6042 g’s. Both left and right engine thrust reversers indicated deployed six seconds after initial MLG touchdown. Postaccident inspection of the airplane revealed extensive structural damage to the right and left forward area (41/43 station) of the fuselage. There was extensive damage to twelve skin panels, eleven severed RH stringers and twelve buckled LH stringer sections, multiple underlying damaged structural components, and damage to the nose landing gear and support structure

Probable cause

an improper landing flare, which resulted in a bounced landing and substantial damage.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA19CA167
Event ID
20190617X92437
Case number
DCA19CA167
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, coordinates, 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: afc82abba16e5960cea13436197cf1c2f5442be8de97c2ac24198c136e146285; retrieved 2026-09-16T09:17:44.735Z.