United Airlines Boeing 737-322 incident
Boeing 737-322 · Incident: gear not extended on approach
From Oakland San Francisco Bay Airport (OAK) to Hollywood Burbank/Bob Hope Airport (BUR)
Event
- NTSB case
- LAX90IA293
- 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
- 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 737-322
- Aircraft type
- Boeing 737
- 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
- N305UA
- Operator
- United Airlines
- Onboard fatalities
- Unknown
- Route
- From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Hollywood Burbank/Bob Hope Airport (BUR), Burbank, CA
- 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
- 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
- Gear not extended
- 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
- Company maintenance personnel › Maintenance, service of aircraft/equipment, improper
- Landing gear, main gear › Foreign object
Approximate · Estimated position: the centre of Los Angeles, CA, the place the record names. Not the accident site.
NTSB narrative
THE FLIGHT OF UAL FLIGHT 1257 WAS UNEVENTFUL UNTIL THE CREW EXTENDED THE LANDING GEAR FOR LANDING AT THE DESTINATION AND RECEIVED AN UNSAFE RIGHT MAIN LANDING GEAR INDICATION. THE CREW WAS UNABLE TO EXTEND THE GEAR AND PRECEDED TO AN AIRPORT WITH A LONGER RUNWAY FOR A GEAR UP LANDING. THE LANDING WAS ACCOMPLISHED WITHOUT INJURIES. THE RIGHT POWERPLANT NACELLE RECEIVED INCIDENTAL DAMAGE DURING THE LANDING TOUCHDOWN. WHEN THE RIGHT LANDING GEAR WAS OPENED A 3 CELL FLASHLIGHT WAS FOUND SANDWICHED BETWEEN THE CARGO FLOORING AND THE LANDING GEAR RETRACT/EXTEND LINKAGE.
Probable cause
IMPROPER MAINTENANCE SERVICE BY A COMPANY EMPLOYEE WHO ALLOWED A FOREIGN OBJECT (FLASHLIGHT) TO REMAIN IN THE LANDING GEAR EXTEND/RETRACT LINKAGE DURING A NIGHT SERVICING BEFORE THE FLIGHT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90IA293
- Event ID
- 20001212X24038
- Case number
- LAX90IA293
- 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: 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.
- API snapshot SHA-256: 8fd7623d0631cb738c4125ace6311e29c1999f68c722766a1c817ce9b206b049; retrieved 2026-09-18T18:59:51.079Z.