Southwest Airlines Flight 1767
Boeing 737-300-3H4 737-300-3H · Incident: airframe, component or system failure on approach
From Harry Reid International Airport (LAS) to Hollywood Burbank/Bob Hope Airport (BUR)
Event
- NTSB case
- LAX96IA184
- 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 737-300-3H4 737-300-3H
- 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
- N331SW
- Operator
- Southwest Airlines
- Onboard fatalities
- Unknown
- Route
- From Harry Reid International Airport (LAS), Las Vegas, NVTo 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
- 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
- Other maintenance personnel › Gear extension, not possible
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported an unresolved main landing gear problem and orbited the area performing normal emergency gear extension procedures without success. The pilot performed low 'G' maneuvers and touch-and-go landings in an attempt to lower the left main gear. The pilot diverted to another airport where an emergency landing was made with minor damage and no injuries. The landing gear was removed and disassembled. The upper bearing carriers and bearing half shells were found out of position in the upper portion of the oleo strut. The subsequent over extension of the strut was a result of the gradual breakup of the bearings and bearing carriers due to improper/incompatible wear surfaces from the repair facility's improper assembly at overhaul. The compression/extension measurements after installation were not required.
Probable cause
The repair facility's improper assembly of the landing gear oleo strut during overhaul.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96IA184
- Event ID
- 20001208X05599
- Case number
- LAX96IA184
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: d51584f7bdc7c0aaf758faccf4ffc1c87711da33064f4a236b40cdac51f75199; retrieved 2026-09-18T17:51:40.964Z.
- The NTSB's operator name is blank for N331SW; the operator shown is the name the NTSB's other records give its FAA operator code, SWAA.