FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

UPS Airlines Flight 1354

14 Aug 2013 · North of Birmingham–Shuttlesworth International Airport, Alabama, United States

United Parcel Service Airbus A300 - F4 622R · Controlled flight into terrain due to pilot error and pilot fatigue

From Louisville Muhammad Ali International Airport (SDF) to Birmingham-Shuttlesworth International Airport (BHM)

Report a problem

Event

NTSB case
DCA13MA133
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
Event fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
Occupants
2
Survivors
0
InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
0 serious · 0 minor (NTSB)
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
Unknown

Airbus A300 - F4 622R

Flight
5X1354
Aircraft type
Airbus A300
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
N155UP
Onboard fatalities
Unknown
Route
From Louisville Muhammad Ali International Airport (SDF), Louisville, KYTo Birmingham-Shuttlesworth International Airport (BHM), Birmingham, AL
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
Approach · IFR final approach
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
Controlled flight into terrain/object (CFIT)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Psychological

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

From the Wikipedia article

UPS Airlines Flight 1354 was a scheduled cargo flight from Louisville, Kentucky, to Birmingham, Alabama. On August 14, 2013, the Airbus A300 flying the route crashed and burst into flames short of the runway on approach to Birmingham–Shuttlesworth International Airport. Both pilots were pronounced dead at the scene of the crash. They were the only people aboard the aircraft. It was the second fatal air crash for UPS Airlines.

Accident

The aircraft was inbound on a scheduled flight at the time of the crash. Dark night visual flight rules prevailed at the airport, but variable instrument meteorological conditions with a variable ceiling were present north of the airport on the approach course.

A notice to airmen (NOTAM), in effect at the time of the accident, indicated that runway 06/24, the longest runway available at the airport and the only one with an ILS approach, would be closed from 04:00 to 05:00 CDT. Because the flight was scheduled to arrive at Birmingham at 04:51, only the shorter runway 18 with a non-precision approach was available to the pilots.

Forecasted weather at BHM indicated that the low ceilings upon arrival required an alternate airport, but the dispatcher did not discuss the low ceilings, the single-approach option to the airport, or the reopening of runway 06/24 about 05:00 with the flight crew. Further, during the flight, information about variable ceilings at the airport was not provided to the flight crew.

At 04:21:28, the cockpit voice recorder recorded the first officer stating, "they're sayin' six and two-four is closed. They're doin' the localizer to one eight," after the flight crew listened to BHM automatic terminal information service (ATIS) Papa, which included the 06/24 runway closure. The captain responded, "localizer (to) one eight, it figures." Between 04:23 and 04:30, the captain briefed the localizer runway 18 approach using the UPS Profile Briefing Guide from the UPS Aircraft Operating Manual (AFM). The captain then continued to review the localizer 18 approach chart. At no point did the captain or first officer mention that the localizer approach was not available.

At 04:33:33, air traffic control cleared the flight to descend to 11000 ft mean sea level (msl), and the captain commented, "They're generous today. Usually they kind'a take you to fifteen and they hold you up high." At 04:41:44, while flying level at 11,000 feet msl, the first officer contacted BHM approach control advising ATIS information and requesting a lower altitude. The BHM approach controller issued a descent clearance to 3000 ft and said, "uhm...runway six is still closed. you want...the localizer one eight?" The flight crew accepted the localizer 18 approach.

At 04:47:10.9, as the airplane passed the IMTOY stepdown fix near the minimum crossing altitude of 1380 ft msl, the captain said "two miles". However the airplane continued to descend at 1500 ft/min and passed through and continued below the desired glidepath. As the airplane approached and then descended through the minimum descent altitude of 1200 ft msl, neither pilot made the required callouts regarding approaching and reaching the minimum descent altitude. At 04:47:19.6 the first officer said, "it wouldn't happen to be actual [chuckle]."

At an altitude of about 1000 ft msl, about 250 ft above ground level, an enhanced ground proximity warning system (EGPWS) sink rate caution alert was triggered. About 1 second later, the captain began to reduce the selected vertical speed to about 600 ft/min. The captain reported the runway in sight about 3.5 seconds after the sink rate caution alert, and the first officer then confirmed that she also had the runway in sight. About 2 seconds after reporting the runway in sight, the captain further reduced the selected vertical speed to 400 ft/min. At 04:47:31.5, the captain disconnected the autopilot, and a second later, the cockpit voice recorder recorded the sound of rustling, corresponding to the airplane's first contact with trees. The recorder then recorded an EGPWS "too low terrain" caution alert and several additional impact noises until the recording ended.

The aircraft crashed around 04:47 local time (CDT, 09:47 UTC). It clipped trees and struck ground three times uphill. The fuselage broke apart, with the nose coming to rest about 200 yd away from the initial point of impact, and the rest of it about 80 yd farther down towards the runway and about 1 km from its edge and catching fire. Both crew members died in the accident.

Investigation and cause

Investigation

The National Transportation Safety Board (NTSB) launched an investigation and sent a 26-member go team to the crash site to collect perishable evidence. The cockpit voice recorder (CVR) and flight data recorder (FDR) were recovered on the following day and sent for analysis.

At their third media briefing on August 16, 2013, the NTSB reported that the crew had briefed the approach to runway 18 and were cleared to land by air traffic control two minutes prior to the end of the recording. At 16 seconds before the end of the recording, the aircraft's ground proximity warning system (GPWS) sounded two "sink rate" alerts, meaning that the aircraft was descending too rapidly. Three seconds later, Captain Beal reported having the runway in sight, which was confirmed by First Officer Fanning. The CVR recorded the sound of the first impact with trees 3 seconds after the pilots reported seeing the runway. A final "too low terrain" alert by the GPWS was then recorded, followed by the final sounds of impact.

To represent the country of manufacture, the French aviation accident investigation agency Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA), assisted by Airbus technical advisors, participated in the investigation. Members of the FBI Evidence Response Team also assisted the NTSB. The NTSB stated in late August that no mechanical anomalies had yet been uncovered, but that the complete investigation would take several months.

On February 20, 2014, the NTSB held a public hearing in connection with its investigation. Excerpts from the CVR were presented, in which both the captain and first officer discussed their lack of sufficient sleep prior to the flight.

During the investigation, the NTSB examined fatigue as a factor in the pilot's decision making during the landing, noting that both pilots had been overly busy during their expected rest period in the hours immediately prior to their flight; conflicting squabbles on rest, between UPS and the Independent Pilots Association, led to the NTSB excluding them from the remainder of the hearing.

On September 9, 2014, the NTSB announced that the probable cause of the accident was that the aircrew had made an unstabilized approach into Birmingham–Shuttlesworth International Airport. They failed to adequately monitor their altitude and descended below the minimum descent altitude when the runway was not yet in sight, resulting in controlled flight into terrain about 3300 ft short of the runway threshold.

The NTSB also found that contributing factors in the accident were:

the flight crew's failure to properly configure and verify the flight management computer for the profile approach

the captain's failure to communicate his intentions to the first officer once it became apparent the vertical profile was not captured

the flight crew's expectation that they would break out of cloud at 1000 ft above ground level [due to incomplete weather information]

the first officer's failure to make the required minimums callouts

the captain's performance deficiencies, likely due to factors including, but not limited to, fatigue, distraction, or confusion, consistent with performance deficiencies exhibited during training

the first officer's fatigue due to acute sleep loss resulting from her ineffective off-duty time management

Text from the Wikipedia article “UPS Airlines Flight 1354” (revision 1361599596, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article

NTSB narrative

The Safety Board's full report is available at http://www.ntsb.gov/investigations/AccidentReports/Pages/aviation.aspx. The Aircraft Accident Report number is NTSB/AAR-14/02.

On August 14, 2013, about 0447 central daylight time (CDT), United Parcel Service (UPS) flight 1354, an Airbus A300-600, N155UP, crashed short of runway 18 during a localizer nonprecision approach to runway 18 at Birmingham-Shuttlesworth International Airport (BHM), Birmingham, Alabama. The captain and first officer were fatally injured, and the airplane was destroyed by impact forces and postcrash fire. The nonscheduled cargo flight was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 121 on an instrument flight rules flight plan, and dark night visual flight rules conditions prevailed at the airport; variable instrument meteorological conditions (IMC) with a variable ceiling were present north of the airport on the approach course at the time of the accident. The flight originated from Louisville International Airport-Standiford Field (SDF), Louisville, Kentucky, about 0503 eastern daylight time (EDT).

Probable cause

the flight crew's continuation of an unstabilized approach and their failure to monitor the aircraft's altitude during the approach, which led to an inadvertent descent below the minimum approach altitude and subsequently into terrain. Contributing to the accident were (1) the flight crew's failure to properly configure and verify the flight management computer for the profile approach; (2) the captain's failure to communicate his intentions to the first officer once it became apparent the vertical profile was not captured; (3) the flight crew's expectation that they would break out of the clouds at 1,000 feet above ground level due to incomplete weather information; (4) the first officer's failure to make the required minimums callouts; (5) the captain's performance deficiencies likely due to factors including, but not limited to, fatigue, distraction, or confusion, consistent with performance deficiencies exhibited during training; and (6) the first officer's fatigue due to acute sleep loss resulting from her ineffective off-duty time management and circadian factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

Wikipedia article: UPS Airlines Flight 1354
Article
UPS Airlines Flight 1354
Revision
1361599596 · 2026-06-28 · retrieved 2026-09-18
Wikidata
Q14566965
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA13MA133
Event ID
20130814X15751
Case number
DCA13MA133
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "UPS Airlines Flight 1354" (page 40238748, revision 1361599596); merged with NTSB case DCA13MA133 (events / aircraft)
Date
NTSB record DCA13MA133: NTSB narrative opening date, consistent with the API date and time (local date)
Place and country
Wikipedia infobox: site; country from NTSB record DCA13MA133
Map position
NTSB record DCA13MA133: events decimal coordinates
Aircraft, operator and route
NTSB record DCA13MA133: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record DCA13MA133: operated under Part 121: Air Carrier
Fatalities
NTSB record DCA13MA133: NTSB API totalFatal
Ground fatalities
NTSB record DCA13MA133: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "UPS Airlines Flight 1354" and NTSB case DCA13MA133, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
  • 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.