FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Parcel Service Flight 916

5 Mar 2016 · Albuquerque, NM, United States

Boeing 767 34AF · Accident: tailstrike during landing

From Louisville Muhammad Ali International Airport (KSDF) to Albuquerque International Sunport (KABQ)

Report a problem

Event

NTSB case
DCA16CA113
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 767 34AF

Aircraft type
Boeing 767
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
N305UP
Onboard fatalities
Unknown
Route
From Louisville Muhammad Ali International Airport (KSDF), Louisville, KYTo Albuquerque International Sunport (KABQ), Albuquerque, NM
Aircraft age
About 21 years (built 1995)
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
Tailstrike
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 as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

On March 5, 2016 at 6:31 mountain standard time, a Boeing 767-300, N305UP, operated by United Parcel Service (UPS) as flight 916 was substantially damaged following a tailstrike during landing on runway 03 at the Albuquerque International Sunport Airport (ABQ), Albuquerque, New Mexico. Neither of the 2 flight crew were injured. The flight originated from the Louisville International Airport (SDF), Louisville, Kentucky.

The airplane sustained damage to a 23 foot long section of lower fuselage skin, 4 fuselage stringers, 5 fuselage frames, 3 floor stringers and the tail skid. The replacement of the frames and stringers was considered a major repair and qualified as substantial damage in accordance with 49 CFR 830.2

According to the operator, the Captain was the pilot flying, and the First Officer the pilot monitoring for the flight from SDF-ABQ. Ground operations were normal in SDF and no aircraft loading or Weight and Balance discrepancies were noted. The climb, cruise, and descent portion of the flight were uneventful. Weather conditions at ABQ prior to arrival were reported as visual conditions, with wind from 090 at 20 knots gusting to 29 knots. The target approach speed used was 146 knots. The crew was vectored to the ILS approach to runway 03 and joined the localizer and glideslope using the autopilot. The autopilot was then disengaged at 1103 feet Height Above Touchdown (HAT) and at 1000 feet HAT the approach met all UPS Stabilized Approach criteria with the aircraft fully configured at flaps 30, gear down, and speed 145 knots. At 500 feet HAT the approach continued to meet all stabilized approach criteria with speed 146 knots. Flight data indicated that the crosswind component at this point was 23 knots from the right.

At 158 feet above touchdown the approach met all stabilized approach criteria and the Captain disconnected the autothrottles. UPS guidance recommends use of the autothrottle until 50 feet above touchdown. From this point on the approach until touchdown, the aircraft pitch attitude began to increase as the airspeed slowly decreased. Flight Data indicates that the thrust levers were at a reduced thrust setting when the autothrottles were disconnected and remained at that setting until touchdown. At 1.75 seconds from touchdown the airspeed had decayed to 129 knots and the aircraft pitch had increased to 7.2 degrees. The crosswind had also decreased and was now 13 knots from the right. At touchdown the airspeed was 128 knots and pitch attitude 8.4 degrees. The tailskid impacted the runway at touchdown followed immediately by the lower aft fuselage as the pitch attitude increased momentarily to 8.6 degrees. Initial tailskid impact occurred at approximately 800 feet from the runway threshold.

The crew reported that they encountered a 10 knot wind loss just prior to touchdown and landed firmer than normal, but didn't suspect that they had struck the tailskid.

Probable cause

the pilot flying's failure to maintain airspeed and correct pitch attitude. Contributing to the accident was the pilot's failure to maintain appropriate thrust after disconnecting the autothrottles. Also contributing was the first officer's failure to monitor the decaying airspeed and increasing pitch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA16CA113
Event ID
20160330X72920
Case number
DCA16CA113
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. 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: 4ae125fe276a6ee0e80cbcc8c58ee2c061d9a8a84b7354291ab37ff1fd8a8c35; retrieved 2026-09-16T03:15:43.050Z.