United Airlines Boeing 757-222 accident
Boeing 757-222 · Accident: on ground/water collision with terrain/water during takeoff
From LaGuardia Airport (LGA) to Denver International Airport (DEN)
Event
- NTSB case
- DEN90LA046
- 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
- 0
- 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-222
- 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
- N505UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From LaGuardia Airport (LGA)To Denver International Airport (DEN), Denver, CO
- 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
- Takeoff · roll/run
- First occurrenceThe 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
- On ground/water collision with terrain/water
- 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
- Pilot in command › Rotation, excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE PREPARING FOR FLT IN A BOEING 757, THE 1ST OFFICER (FO) INADVERTENTLY COMPUTED THE TAKEOFF DATA BY USING THE BOEING 767 DATA. V1, VR & V2 SPEEDS WERE CALCULATED TO BE 115, 118 & 129 KTS. THE CORRECT SPEEDS SHOULD HAVE BEEN 145, 148 & 152 KTS. THE CAPT DID NOT CONFIRM THE V-SPEED COMPUTATION; BOTH PLTS SET THEIR AIRSPEED BUGS AT THE IMPROPER SPEEDS. DURING LIFT-OFF, THE ACFT WAS OVERROTATED & THE LOWER AFT FUSELAGE CONTACTED THE RWY. THE CREW NOTED A 'JOLT,' BUT ELECTED TO CONTINUE TO THEIR DESTN AFTER DISCUSSING THE SITUATION WITH MAINTENANCE PSNL. AFTER LANDING, DAMAGE WAS NOTED TO THE LOWER AFT SKIN, AFT PRESSURE BULKHEAD & ASSOCIATED STRUCTURE.
Probable cause
OVERROTATION OF THE AIRCRAFT DURING TAKEOFF. FACTORS RELATED TO THE ACCIDENT WERE: THE FIRST OFFICER'S IMPROPER USE OF THE FLIGHT MANUAL, WHICH RESULTED IN HIS IMPROPER CALCULATIONS OF THE ROTATION SPEED, AND INADEQUATE SUPERVISION CONCERNING VERIFICATION OF THE TAKEOFF DATA BY THE CAPTAIN.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DEN90LA046
- Event ID
- 20001212X22410
- Case number
- DEN90LA046
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: 5113d4e64ecb3acbb445b7439f1f61e0f66cd15c778c8d35d675aee19f47ad15; retrieved 2026-09-18T19:05:36.258Z.