FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Delta Airlines Flight 1972

13 Mar 2000 · San Francisco, CA, United States

Boeing 727-232 · Incident: airframe, component or system failure during initial climb

From San Francisco International Airport (SFO) to Salt Lake City International Airport (SLC)

Report a problem

Event

NTSB case
LAX00IA127
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
Incident
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
0
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 727-232

Aircraft type
Boeing 727
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
N516DA
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Salt Lake City International Airport (SLC), Salt Lake City, UT
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
Initial climb
First occurrenceThe 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
Airframe, component or system failure
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Reason for occurrence undetermined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane landed with the right main landing gear partially extended. This was the second leg of the day in the airplane for this crew; the second officer (SO) completed walk around inspections prior to both flights and noted no discrepancies. The captain was hand flying the airplane in the initial takeoff climb, and selected landing gear up passing through 300 to 500 feet above ground level (agl). The red "doors" light illuminated on the front panel and the amber right main gear door light illuminated on the second officer's panel. All attempts to lower the right main gear were unsuccessful, so the captain elected to return to the airport and land with the right main gear extended about 15 degrees. Inspection of the right main landing gear revealed that the safety bar bent down about 20 degrees at the leading edge and 15 degrees at its midpoint. The safety bar's inboard flanges buckled just below the reinforced area. The inner gear door drive rod bent aft about 15 degrees at the upper attachment fitting, and the tube buckled and separated below the four attachment nuts. The outboard section of the clamshell gear door sustained mechanical damage. Examination of the airplane revealed that the door rods were not loose, and all were in good condition. A general inspection of the wheel well revealed no other damage. There was no abnormal wear or movement marks on the up-lock hook, and the hook was properly adjusted. The actuator adjustor plate was properly installed. Delta maintenance technicians installed new clamshell door halves and a new drive rod. They serviced the strut, isolated the right main clamshell gear door, and cycled the gear. Then they cycled the right main wheel with the door. Finally, they cycled all of the landing gear together. All wheels and doors cycled in proper sequence. Metallurgical examination discovered no cracks in the safety plate. There were no fatigue crack arrest marks or corrosion in the fracture faces on the drive rod; it fractured as a result of overstress. A black coating that felt greasy covered the interior side of the outer clamshell door. There was a rectangular scuffmark in the center of the black area, which had its long axis parallel to the longitudinal axis of the airplane. The black coating appeared pushed into a slight ridge along the outer edge of the scuffmark. A small piece of rubber was under a rivet in the middle of the scuffmark. After placing the tire and gear door together to match their positions when the airplane came to rest, the tire did not touch the scuffmark. Fourier Transform Infrared Spectroscopy (FTIR) examination of the small piece of rubber and samples from the tire and a chock determined that they were all hydrocarbon compounds, but could not distinguish between the samples. Whether the scuffmark and rubber piece came from runway debris or another rubber object could not be determined.

Probable cause

failure of the right main landing gear to fully extend for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00IA127
Event ID
20001212X20664
Case number
LAX00IA127
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2000-03-14.
  • API snapshot SHA-256: cdcb31783ca0e696647d8a469e98ecc0acfb88d5d8f30bacc417e6713ac703eb; retrieved 2026-09-18T16:45:34.669Z.