FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Federal Express Boeing 767 300F accident

19 Aug 2020 · Los Angeles, CA, United States

Boeing 767 300F · Accident: system/component malfunction/failure (non-power) on approach

From Newark Liberty International Airport (KEWR) to an unrecorded destination

Report a problem

Event

NTSB case
DCA20LA138
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 300F

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
N146FE
Onboard fatalities
Unknown
Route
From Newark Liberty International Airport (KEWR), Newark, NJTo not recorded
Aircraft age
About 3 years (built 2017)
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
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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft systems

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

NTSB narrative

In preparation for landing, LAX air traffic control cleared FedEx flight 1026 for an instrument landing system (ILS) approach to runway 24R. When the airplane descended to an altitude of about 1,800 ft, the flight crew moved the landing gear handle to lower the landing gear. The crew then received a “GEAR DISAGREE” message from the engine indicating and crew alerting system. The crew discontinued the approach and climbed the airplane to 5,000 ft to perform the quick reference handbook Gear Disagree checklist procedure. The checklist directed the crew to lower the landing gear using the alternate gear extension system, but the left main landing gear (MLG) still did not extend.

The flight crew then flew a low approach to the runway so that the tower controller could try to see if the left MLG was extended. The airplane descended to an altitude of about 500 ft above ground level, but the tower controller could not tell whether the left MLG was extended. The crew then declared an emergency and flew another low approach—this time at an altitude of about 200 to 300 ft above ground level and with airport operations personnel positioned along the runway to get a better view of the airplane. The second low approach determined that the left MLG was retracted.

The captain stated that, once the fuel was at an appropriate point to execute the gear-up approach and landing, air traffic control vectored the airplane for an ILS approach to the longest runway at the airport. The captain also stated the airplane made a “normal landing touchdown” and that, after the left engine contacted the runway, he maintained directional control with the ailerons, rudder, and right wheel braking. After the captain manually deployed the speedbrakes, the airplane came to a stop on the runway centerline about 2,000 to 3,000 ft from the end of the runway.

A brake rod, which is installed between each brake assembly housing and the shock strut, transfers the torque generated by the brake to the MLG. Each brake rod is connected to the torque arm on the brake assembly housing using, among other things, a pin that is secured by a retaining bolt. Postaccident examination of the left MLG assembly revealed that the No. 6 brake rod (corresponding to the aft inboard wheel) was connected at the shock strut end but was not connected to the torque arm on the brake assembly housing. The brake rod pin was likely in place during the accident flight takeoff given that no scrape marks or gouging were found on the brake rod, indicating that the brake rod had not contacted the runway while the airplane was moving, which would likely have happened if the brake rod was connected only at the shock strut end while the left MLG was in its extended position. The flight crew was unable to extend the left MLG during the approach because the pin had come loose during the flight, which allowed the brake rod to move out of its normal position and become hung up on the landing gear upstop.

The airplane had accumulated 73 flight cycles since the last No. 6 brake assembly change, which would have been the last time that the No. 6 brake rod was removed and reinstalled. The maintenance personnel who performed the No. 6 brake assembly change did not recall anything unusual or concerning about the installation of the brake assembly or brake rod.

The No. 6 brake rod attaching hardware components from the accident airplane were not located after the accident, precluding a determination of why the pin was in place for the takeoff but not when the crew tried to lower the landing gear. As a result, on the basis of the available evidence for this accident, the investigation was unable to determine the reason that the brake rod pin came loose during the accident flight.

Probable cause

The left main landing gear’s failure to extend due to the separation of the brake rod retaining hardware from the aft inboard wheel for reasons that could not be determined based on the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA20LA138
Event ID
20200826X34514
Case number
DCA20LA138
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, cause areas. 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: 8a1c4b966ac5fc414f58e111d888aa063d8af68350509e26465cad5873394c98; retrieved 2026-09-16T12:56:17.407Z.