DCA19CA167

NTSB accident investigation · Boeing 757 · Newark, NJ · June 15, 2019

Accident · No injuriesClass 4 · Data collectionFinal report
Date
June 15, 2019, 12:55 local (16:55 UTC)
Place
Newark, NJ
Injuries
272 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N26123Boeing 757
Defining event
Landing-flare/touchdown: Hard landing
Weather
Visual (VMC) · Day
Status
Completed
Report
Approved by Office Director
Investigation class
Class 4 - Basic report with no Prelim publish
NTSB office
Major Investigations Division
Case key
99634

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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

Findings · 1

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Action: delayed actionPersonnel issues › Action/decision · CopilotBoeing 757-224: 1 caseAll aircraft: 894 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Analysis

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 andsupport structure

Aircraft

Registration
N26123
Reported as
Boeing 757 (224)
Category
Airplane
Serial number
28966
Built
1997
Engines
Rolls Royce, turbo fanRolls Royce, turbo fan
Damage
Substantial damage
Flight
Part 121
Operator
United Airlines
Registered owner
United Airlines Inc
Airworthiness certificate
Standard, Transport
Departed
KDEN · Denver, CO
Destination
KEWR · Newark, NJ
Flight plan
IFR
Airport
KEWR · Newarl International, runway 22L, 10,000 × 150 ft, asphalt

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
48
Injuries
None
Certificate
Airline transport
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Waiver time limited special
Last flight review
February 24, 2019
Seat
Left
Restraint
5-point
Flight hours
13,847 total · 1,140 in this make and model · 1,537 as pilot in command · 123 in the last 90 days · 54 in the last 30 days · 1 in the last 24 hours
Role
Co-pilot
Age
42
Injuries
None
Certificate
Airline transport
Airplane ratings
Single-engine land, Multi-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
May 30, 2019
Seat
Right
Restraint
5-point
Flight hours
11,545 total · 4 in this make and model · 7,986 as pilot in command · 4 in the last 90 days · 4 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
239° at 19 knots
Visibility
10 statute miles
Temperature
77 °F, dew point 52 °F
Altimeter
30.09 inHg
Observed at
EWR

Docket · 6

The files NTSB released with the investigation on February 25, 2022, on NTSB’s docket system: statements, records, photos and specialists’ reports. 12.6 MB in all.

FAA reports on this event · 2

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.