FedEx Express Flight 087

On 17 October 1999, FedEx Express Flight 087, a McDonnell Douglas MD-11F, crashed after landing at Subic Bay International Airport, Philippines. The aircraft was operating from Shanghai Hongqiao International Airport. Upon landing, the aircraft rolled down the whole length of the runway before plunging into the Subic Bay where it was completely submerged except for the cockpit. The aircraft was written off.[2][3][4]

FedEx Express Flight 087
Wreckage of the aircraft in the Subic Bay
Accident
Date17 October 1999 (1999-10-17)
SummaryRunway excursion due to blockage of pitot tubes and pilot error
SiteSubic Bay International Airport, Bataan, Philippines
Aircraft

The aircraft involved in the accident, while still in service with American Airlines in 1995
Aircraft typeMcDonnell Douglas MD-11F
Aircraft nameJoshua
OperatorFedEx Express
IATA flight No.FX087
ICAO flight No.FDX087
Call signFEDEX 087
RegistrationN581FE[1]
Flight originShanghai Hongqiao International Airport, Shanghai, China
DestinationSubic Bay International Airport, Bataan, Philippines
Occupants2
Crew2
Fatalities0
Injuries2
Survivors2
A FedEx Express McDonnell Douglas MD-11F, similar to the one involved in the accident

Background

edit

Aircraft

edit

The aircraft involved, manufactured by McDonnell Douglas in 1990, was a nine-year-old McDonnell Douglas MD-11F with aircraft registration N581FE and serial number 48419. The aircraft had logged 30,278 total airframe hours in 5,817 flight cycles. It was powered by three General Electric CF6 engines.[2]: 7 [5] The aircraft was worth 120 million dollars.[6]

Crew

edit

On board the aircraft were only two pilots:

  • In command was 53-year-old Captain Michael Rooney. He had a total of 14,000 flight hours and 1,430 hours of experience on the MD-11. The captain was employed by Flying Tiger Line in the 1980s as a co-pilot on the Douglas DC-8 and the Boeing 747. Since the company's merger with FedEx, he had been a captain on the Boeing 727, and in April 1996, he began flying the MD-11 as a captain.[2]: 6 

Accident

edit

The accident aircraft was operated as part of the U.S. Civil Reserve Air Corps. Most of the cargo was electronic goods and clothing.[3] The Subic Special Economic and Freeport Zone was formerly the site of the Subic Naval Base, and Subic Bay International Airport was one of FedEx's hubs.[4]

At around 13:00 UTC, the aircraft took off from Shanghai Hongqiao International Airport. At 3:24 p.m., the cockpit voice recorder (CVR) heard the captain's message "airspeed returned, there is no problem. I've got no speed problem." At 3:32 p.m., the CVR recorded the pilots again discussing airspeed. One minute later, the overspeed warning and the autopilot disengagement alarm were activated. At 3:53 p.m., the captain instructed the first officer to set the flaps to 50 degrees, and the first officer moved the flap levers to the 50-degree position. However, the flaps did not extend to 50 degrees, so the first officer moved the flap levers back to the 35-degree position. At 3:54 p.m., at an altitude of 500 feet (150 m), the rate of descent warning and ground proximity warning system were activated. At 15:55:04, the aircraft landed on Runway 07 at Subic Bay International Airport. The aircraft did not stop on the runway but came into contact with the localizer antenna and the approach lights. The aircraft plunged into the Subic Bay, and the aircraft was submerged except for the cockpit.[2]: 1–4  The nose of the aircraft broke away and the cargo fell out of the hold. The wing and nose of the aircraft were damaged.[7] The aircraft sank 32 feet (10 m) from the airport's shoreline. The aircraft had hit a concrete post and wire fence.[8][9]

The pilots escaped through the cockpit windows and waited for rescue on the wing.[2]: 4–5 [10] The pilots suffer minor injuries.[11] The pilots were later treated at Legenda Hospital in Cubi Point.[12][8] FedEx later released a statement saying it was "thankful" that the crew was safe.[13] The aircraft was leaking fuel into the water, which prompted airport authorities to surround the aircraft with a boom to prevent fuel from spreading.[14] Most of the cargo had been destroyed.[6]

 
Subic Bay International Airport in 1990

Investigation

edit

During an interview with the pilots, the captain said there was no problem with the airspeed indicator from takeoff to the time of the climb to cruising altitude. After the aircraft encountered clouds during cruise, the autopilot was disengaged several times and an airspeed (IAS) warning appeared on the primary flight display (PFD) on the captain's seat. The captain compared the airspeed indicator with the first officer's airspeed indicator, and when an error was observed, the source of the airspeed indicator on the first officer's side switched to the air data computer (ADC) on the captain's side. The captain testified that he did not notice any abnormalities except that he felt that the elevator rudder was operating slightly differently during the landing approach. On the final approach, the flaps could not be extended to 50 degrees, so the approach remained at 35 degrees, but the captain was not particularly worried. The captain said he was aware of the existence of a checklist for airspeed problems but had never been trained to use it.[2]: 4–5 

The first officer also testified that there was no problem with the airspeed indicator from takeoff to cruising altitude. The first officer said she was aware of the existence of a checklist for airspeed issues, but did not refer to it because the problem was solved by unifying the ADC. She also said that she had never encountered a situation in which the PFD was shown an IAS warning, and that she had not been trained for such a situation.[2]: 5 

Pitot tube inspection and testing

edit
 
Three pitot tubes are installed in the nose of the MD-11, just below the cockpit

Airspeed and altitude were calculated based on outside air pressure measured by a pitot tube. The MD-11 was equipped with three pitot tubes, each measuring data for the captain's side of the instrument, the co-pilot's side of the instrument, and the backup instrument. In addition, there were two drain holes in the pitot pipe.[2]: 22–23  An inspection of the drain in the pitot tube on the co-pilot's side revealed that one of the two pipes was blocked by transparent crystalline particles. In addition, the tip of the pitot tube was also blocked by white crystalline particles and dead insects. The drain of the pitot tube on the captain's side was both blocked by white and brown residue, respectively, and the tip was also blocked by the same particles as the co-pilot's side. Honeywell and Boeing conducted the experiment under the supervision of the Federal Aviation Administration (FAA). In the experiment, a certain amount of water was put into the pitot tube. As a result, it was found that there was an error in the measured data, and the airspeed was displayed as 12 knots (22 km/h) slower than it actually was. This was consistent with the initial error on Flight 87. Further experiments were conducted to test the extent of the error between descent and landing. As a result, the following data were obtained. Subsequent investigations revealed that there had been many reports of abnormal airspeed in the accident aircraft. FedEx had taken various measures, but had not inspected the drain, which was the root of the problem.[2]: 29 

Airspeed discrepancies

edit

According to the cockpit voice recorder and Digital Flight Data Recorder (DFDR) recordings, the airspeed discrepancy began to occur 43 minutes before landing. Ninety seconds later, the autopilot was released while the aircraft was cruising 37,000 feet (11,000 m). According to Boeing, the autopilot was designed to automatically disengage if there was an error of more than 12 knots (22 km/h) in the airspeed value. Based on the pilot's conversations recorded on the DFDR and CVR, the investigator summarized the airspeed displayed on the captain's side and the co-pilot's instrument as follows. An error of 12 knots (22 km/h) was initially introduced in the captain's instrument system, and then increased as the flight descended, resulting in a difference of 45 knots (83 km/h). This was similar to the data obtained in the experiment.[2]: 28–29 

Causes of the accident

edit

The final report attributed the accident to the pilot's failure to respond appropriately to the incorrect airspeed indication and to recognize the correct airspeed. In addition, the pitot pipe drain was blocked, the alarm system that alerted the airspeed abnormality was insufficient, and the checklist procedure did not include reference to backup instruments.[2]: 31–33 [15]

Recommendations

edit

The report listed some recommendations like requiring all DC-10, MD-11, and MD-10 operators to do a detailed inspection of the pitot tubes at frequent intervals and change training to emphasize correcting erroneous airspeed indications.[2]: 33 

Aftermath

edit

As a result of this accident and other reports of airspeed anomalies by other operators of the McDonnell Douglas MD-11, the MD-11 Flight Crew Operating Manual was revised by Boeing on 15 June 2000. It was revised so it could provide additional guidance to flight crews. The manual states that if the "SEL FADEC ALTN", "SEL ELEV FEEL MAN", and "SEL FLAP LIM OVRD" alerts are displayed simultaneously, any crew should use these alerts as indications to follow the "Airspeed Lost, Suspect, or Erratic" checklist.[2]: 158 

See also

edit

References

edit
  1. ^ "N581FE". Federal Aviation Administration. Retrieved 31 May 2025.
  2. ^ a b c d e f g h i j k l m n "Aircraft Accident Investigation Report – FEDERAL EXPRESS N581FE MD-11 AIRCRAFT – OCTOBER 17, 1999 – SUBIC BAY INTERNATIONAL AIRPORT". Republic of the Philippines Department of Transportation and Communications Aircraft Accident Investigation Board. Archived from the original on 9 February 2022. Retrieved 9 April 2025 – via FedEx Master Executive Council.
  3. ^ a b "Accident description FedEx Flight 87". Aviation Safety Network. Flight Safety Foundation. Retrieved 2 April 2020.
  4. ^ a b "Fedex plane misses runway in Philippines". Tulsa World. Manila, Philippines. The Associated Press. 18 October 1999. p. 33. Retrieved 20 May 2025 – via Newspapers.com.  
  5. ^ "Crash of a McDonnell Douglas MD-11F in Subic Bay". Bureau of Aircraft Accidents Archives. Retrieved 4 December 2020.
  6. ^ a b Hirschman, Dave. "FedEx plane overshoots runway in Philippines, rolls into bay". The Commercial Appeal. Newspapers.com. Retrieved 31 May 2025.
  7. ^ "Plane overshoots runway, crashes into sea". New Straits Times. 19 October 1999.
  8. ^ a b Empeño, Henry. "FedEx plane overshoots runway, plunges into sea". Philippine Daily Inquirer. Archived from the original on 28 November 1999. Retrieved 26 May 2025.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  9. ^ "The cockpit crew of a FedEx MD-11 suffered minor injuries Oct. 17". Aviation Week Network. 25 October 1999. Retrieved 31 May 2025.
  10. ^ "FedEx MD-11 in Subic Bay overrun". Flight International. FlightGlobal. 27 October 1999. Retrieved 3 December 2020.
  11. ^ "The chequered, tragic history of the MD-11". South China Morning Post. 18 October 1999. Archived from the original on 19 May 2025. Retrieved 3 December 2020.{{cite web}}: CS1 maint: bot: original URL status unknown (link)
  12. ^ "FEDEX CREW SURVIVES CRASH CARRIER LOSES COURT ROUND". The Journal of Commerce. 18 October 1999. Retrieved 3 December 2020.
  13. ^ "Two escape as cargo plane sinks into sea". IOL. Retrieved 31 May 2025.
  14. ^ Favila, Aaron. "FedEx Jet Skids Into Sea". CBS News. Retrieved 26 May 2025.
  15. ^ "Birgenair Flight ALW 301, TC-GEN Puerto Plata, Dominican Republic February 6, 1996". Federal Aviation Administration. Retrieved 31 May 2025.