FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Boeing 737-7H4 accident

26 Dec 2006 · San Diego, CA, United States

Boeing 737-7H4 and Boeing 737-3A4 · Accident: collision between aircraft (not in flight) while taxiing

Report a problem

Event

NTSB case
LAX07LA064
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

Aircraft 1 · Boeing 737-7H4

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
N207WN
Onboard fatalities
Unknown
Route
From San Diego International Airport (SAN), San Diego, CATo Harry Reid International Airport (LAS), Las Vegas, NV
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
Taxi · to runway
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
Collision between aircraft (not in flight)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Aircraft 2 · Boeing 737-3A4

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
N673AA
Onboard fatalities
Unknown
Route
From San Diego International Airport (SAN), San Diego, CATo Mineta San Jose International Airport (SJC), San Jose, 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
Pushback/towing
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
Collision between aircraft (not in flight)
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

  • Pilot in command › Clearance, not maintained
  • Pilot of other aircraft › Clearance, not maintained

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

NTSB narrative

Flight 1092 was parked at gate 5. The crew received pushback clearance, and was advised of a company airplane taxiing from gate 1. Ground personnel pushed flight 1092 back, and the captain set the airplane's brakes. The crew of flight 1011 received clearance to taxi from gate 1 to runway 27, and was advised to use caution because of a company airplane pushing back from gate 5. The crew of the taxiing airplane performed taxi checklist items, and discussed using caution regarding the stopped airplane that had been pushed back from gate 5. The first officer (FO) of the taxiing airplane pointed out that there was an open area on his side of the airplane in case the captain needed to deviate to the right for clearance. Flight data recorder information indicated that the taxiing airplane turned to the right (away from the stationary airplane) about 26.5 degrees while moving at a maximum ground speed of 11 knots. It then turned about 2.5 degrees back to the left (towards the stationary airplane) while the brakes were applied, and it stopped. About 8 seconds after coming to a stop, it began moving forward. It collided with the other airplane about 2 seconds later at a recorded groundspeed of 3 knots. The crew of the taxiing airplane was not sure what they hit. The left winglet from the taxiing airplane struck the right horizontal stabilizer of the stopped airplane. The top half of the winglet sheared off, and imbedded itself in the horizontal stabilizer just outboard of the elevator.

Probable cause

Failure of the captain, during taxi, to maintain adequate clearance from an occupied airplane stopped on the ramp.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX07LA064
Event ID
20070111X00042
Case number
LAX07LA064
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (6)
  • 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 2006-12-27.
  • API snapshot SHA-256: 153aaacb3817166dda2b142bc7c12ba3458bcaf9e01e9c17a9468f6c7365030e; retrieved 2026-09-18T14:48:24.524Z.
  • The NTSB's operator name is blank for N207WN; the operator shown is the name the NTSB's other records give its FAA operator code, SWAA.
  • The NTSB's operator name is blank for N673AA; the operator shown is the name the NTSB's other records give its FAA operator code, SWAA.