FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Southwest Airlines Boeing 737-7H4 accident

4 Jun 2004 · Liberal, KS, United States

Boeing 737-7H4 · Accident: in flight encounter with weather en route

From Phoenix Sky Harbor International Airport (PHX) to John Glenn Columbus International Airport (CMH)

Report a problem

Event

NTSB case
CHI04LA148
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 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
N757LV
Onboard fatalities
Unknown
Route
From Phoenix Sky Harbor International Airport (PHX), Phoenix, AZTo John Glenn Columbus International Airport (CMH), Columbus, OH
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
En route · cruise
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
In flight encounter with weather
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
None

Cause areas

  • Flight attendant › Seat belt, not used
  • Flightcrew › Flight into adverse weather, encountered

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

NTSB narrative

The scheduled domestic passenger air carrier flight encountered severe turbulence during cruise flight in an area covered by a convective SIGMET. The air carrier reported the flight crew had passed to the north of convective activity. They saw a patch of blue sky to the right front with no radar returns. They then encountered a large buildup when it appeared in front of the airplane with less than two seconds notice. The airplane also experienced severe turbulence and small hail. Other aircraft in the area reported no conditions greater than light turbulence. Just prior to the encounter, the captain released the flight attendants to resume service. The 'A' flight attendant informed the flight crew that as the flight attendants in the galley removed their seat belts, the 'B' flight attendant became injured when she sustained a broken ankle.

Probable cause

The adverse weather encountered during cruise flight by the flight crew and the flight attendant not being restrained. A contributing factor was the convective activity.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI04LA148
Event ID
20040630X00887
Case number
CHI04LA148
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, coordinates, damage. 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: 19a863b23331b956d2f43e3cef7a69c099c9938e6b1866dbb4dc32003aeaac44; retrieved 2026-09-18T15:24:24.627Z.
  • The NTSB's operator name is blank for N757LV; the operator shown is the name the NTSB's other records give its FAA operator code, SWAA.