FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

FedEx Express Flight 80

23 Mar 2009 · Narita International Airport, Narita, Japan

McDonnell Douglas MD-11F · Structural failure and collision with terrain following a bounced landing exacerbated by excessive pilot input

From Guangzhou Baiyun International Airport (CAN) to Narita International Airport (NRT)

Report a problem

Event

NTSB case
DCA09RA041
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
Final · JTSB final report, 26 Apr 2013 
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
Not recorded

McDonnell Douglas MD-11F

Flight
FX80
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
N526FE
Onboard fatalities
2
Route
From Guangzhou Baiyun International Airport (CAN)To Narita International Airport (NRT)
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
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
Abnormal runway contact
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

  • Personnel issues › Task performance
  • Personnel issues › Physical
  • Personnel issues › Experience/knowledge

From the investigation findings the Wikipedia article reports, sorted into the NTSB's cause areas with AI assistance.

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

FedEx Express Flight 80 was a scheduled cargo flight from Guangzhou Baiyun International Airport, China, to Narita International Airport, Japan, operated by FedEx Express. At 06:48 JST (UTC+09:00) on 23 March 2009, the McDonnell Douglas MD-11 registered N526FE operating the flight crashed while attempting a landing on Runway 34L in gusty and highly variable weather conditions, including winds in excess of 40 kn. The aircraft became destabilized after the fatigued co-pilot's delayed start of the landing flare, subsequently exacerbated by his excessively large, nose-down inputs causing abrupt changes in the plane's pitch, increasing the speed and severity of repeated touchdowns during the bounced landing. This resulted in a structural failure of the landing gear and airframe, with the left wing detaching and power of the jet on the right wing thus causing the plane to roll. The plane came to a stop off of the runway, with the plane inverted and on fire. The captain and first officer, who were the only occupants, survived the initial crash. The airport's rescue crew got the pilots out of the aircraft and tried getting them to a hospital, but the crew succumbed to their injuries before they could receive medical attention.

Accident

The flight took off from Guangzhou at 02:06 CST (UTC+8:00) and was expected to arrive at Narita at 06:53 JST (UTC+9:00), a planned flight time of just under four hours. At 06:43:57, air traffic control informed the flight crew that a Boeing 747 had landed at 06:41 and reported wind shear of ±15 kn below 2000 ft. Surface winds at the time of the accident were reported from 320° at 26 kn gusting to 40 kn. After making a hard landing on runway 34L, the plane bounced three times, coming back down on its nose gear first (a condition called "porpoising") resulting in the loss of directional and altitudinal control. The left wing struck the ground as the left main gear collapsed, causing the aircraft to veer to the left, burst into flames and invert as the airframe broke up, and came to rest upside down in the grass to the left of the runway. It took firefighters about two hours to extinguish the blaze, which completely destroyed the aircraft and its contents.

Investigation and cause

Cause

The Japan Transport Safety Board (JTSB) dispatched six investigators to the airport. The United States' National Transportation Safety Board (NTSB) sent a team to Japan to assist with the investigation. The crash was FedEx's second fatal accident involving a jet aircraft, following the loss of a FedEx owned B747-249F that crashed February 18, 1989, near Kuala Lumpur, while still painted in the Flying Tigers livery after the acquisition of the Flying Tiger Line by FedEx Express in December 1988. This was the first fatal accident at Narita Airport.

The accident was attributed by the JTSB to a series of "porpoising oscillations" that developed during touchdown, following a high sink rate during the final approach. The first officer executed a late flare, in which sink rate was not suppressed until the plane was nearly on the runway, but which also would minimize "float" that might carry the plane further down the runway and reduce its safe stopping distance, or carry it off the centerline in the existing crosswinds. This high touchdown sink rate, coupled with large nose-up inputs, caused the first bounce. A large nose-down input was applied, causing a touchdown on the nose gear. This deviates from approved procedures for the MD-11 during a bounce, which specifies the pilot is to hold a pitch angle of 7.5 deg and use thrust to adjust the descent rate. The plane bounced off this second touchdown, pitching upward. The large control inputs by the first officer resulted in a hard touchdown on the main landing gear. This final touchdown was hard enough (1200 ft/min) to cause the left wing to fail as the left main landing gear transferred force up into the wing, exceeding its design limit. The JTSB report suggested the fire might have been averted if the landing gear fuse pin had failed as designed, but that much of the touchdown force was horizontal to the pin rather than vertical, keeping it intact. The report also cited the crew's use of autothrottle during landing despite gusty wind conditions.

As a result of this accident the Japan Transport Safety Board published its final report on April 26, 2013, in which it made a number of new safety recommendations including that "in order to reduce the occurrence of MD-11 series airplanes' severe hard landing and bounce in which an overload is transferred to the MLGs and their supporting structure, the Boeing Company should improve the controllability and maneuver characteristics by improving the LSAS (Longitudinal Stability Augmentation System) functions, reducing the AGS (Auto Ground Spoilers) deployment delay time and other possible means. Possible improvement on LSAS functions may include: a function to limit large nose-down elevator input during touchdown phase, which is a common phenomenon in severe hard landing cases accompanied by structural destruction for MD-11; and a function to assist bounce recovery and go-around in case of bounce. In order to help pilots to conduct recovery operation from large bounces and judge the necessity of go-around, studies should be made to install a visual display and an aural warning system which show gear touchdown status on MD-11 series airplanes."

The investigation into the two pilots' performance during Flight 80 found that both exhibited signs of lack of sleep and fatigue, and the first officer was heard on the cockpit voice recorder talking about how he had not slept very much prior to operating the flight. A look at both pilots' activity in the days leading up to the flight found that, based on accounts from hotel staff, credit card transactions, and other signs of activity, neither pilot could have had more than four hours of consecutive sleep in the twenty-four hours leading up to the crash.

Additionally, the pilot flying, First Officer Anthony Pino, usually served as a relief pilot, taking control in the middle of long-haul flights. He therefore had little experience in landing the MD-11, and performed landings very infrequently.

Text from the Wikipedia article “FedEx Express Flight 80” (revision 1369600853, 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

On March 23, 2009, at 0649 local time, a FedEx Boeing (McDonnell Douglas) MD-11 crashed upon landing at Narita International Airport (NRT), Narita, Japan. The flight originated at Guangzho Baiyun International Airport (CAN), Guangzho, China. Both pilots were killed and no other persons were onboard. The accident is being investigated by the Japan Transport Safety Board.

All inquiries to this investigation should be directed to:

JAPAN TRANSPORT SAFETY BOARD Ministry of Land, Infrastructure, Transport and Tourism 2-1-2, Kasumigaseki, Chiyoda-ku Tokyo 100-8918 Japan

Website: http://www.mlit.go.jp/jtsb/english.html

Verbatim NTSB factual narrative from the NTSB dataset

Sources

Wikipedia article: FedEx Express Flight 80
Article
FedEx Express Flight 80
Revision
1369600853 · 2026-08-16 · retrieved 2026-09-18
Wikidata
Q1330826
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record DCA09RA041
Event ID
20090323X01952
Case number
DCA09RA041
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Where each value comes from
Record
Wikipedia article "FedEx Express Flight 80" (page 22095234, revision 1369600853); merged with NTSB case DCA09RA041 (events / aircraft)
Date
Wikipedia infobox: date; matches the Japan Transport Safety Board (JTSB) final report
Place and country
Wikipedia infobox: site
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports); gaps and aircraft details from NTSB record DCA09RA041
Operation
airline flight number in the infobox
Fatalities
Wikipedia: Wikipedia infobox: aircraft fatalities; matches the Japan Transport Safety Board (JTSB) final report
Ground fatalities
Wikipedia: not stated in the Wikipedia infobox
Summary
Wikipedia infobox: summary
Source notes (3)
  • One occurrence in two sources, merged: the Wikipedia article "FedEx Express Flight 80" and NTSB case DCA09RA041, matched by the same aircraft registration and date. For this event outside the United States Wikipedia's values are used where the two differ; each value names its source.
  • No bulk values were replaced by the NTSB case API.
  • Checked against the Japan Transport Safety Board (JTSB) final report (2013-04-26) on 2026-09-18. The report states the same date, flight number, fatalities, registration, departure, destination and damage. Shown unchanged where the report gives another value or wording: operator (shown FedEx Express; report Federal Express Corporation). Not checked: place, crash-site coordinates, aircraft type, type of operation and ground fatalities.