Flight 3030 · Saab-Scania SAAB 340B
Saab-Scania SAAB 340B · Accident: in flight encounter with weather en route
From Monterey Regional Airport (MRY) to Los Angeles International Airport (LAX)
Event
- NTSB case
- LAX05LA105
- 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
Saab-Scania SAAB 340B
- Aircraft type
- Saab Scania SAAB 340
- 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
- N394AE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Monterey Regional Airport (MRY), Monterey, CATo Los Angeles International Airport (LAX), Los Angeles, 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
- En route · descent
- 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
- Weather condition › Turbulence
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 encountered turbulence at 5,000 feet mean sea level (msl) during an approach to landing and the sole flight attendant was knocked unconscious and sustained serious injuries. The airplane was about 7 minutes from landing, and the flight attendant was completing his before landing checklist when turbulence was encountered. After regaining consciousness a few seconds later, he was able to get to an empty passenger seat. A deadheading flight attendant assumed the incapacitated flight attendant's duties. Review and analysis of available weather data and forecast products showed that airman's meteorological information (AIRMET) Update 6 was issued by the National Weather Service (NWS) and in effect for the flight for occasional moderate turbulence below 12,000 feet. A review of the meteorological data showed that the airplane was operating in conditions that would have supported at least moderate turbulence below 10,000 feet msl. The weather packet included in the flight release provided to the flight crew by the airline's dispatch prior to the flight contained information for AIRMET Update 3; however, AIRMET Update 6 (valid for the accident flight) was not listed. Information contained on the release indicated to the crew that no moderate or greater turbulence was present along the route of flight. At the time of the accident, the airline's contract weather provider evaluated current meteorological data and staff meteorologists used their judgment of the weather to issue a SIGMEC (significant meteorological conditions, a company issued advisory) based on the current weather conditions. NWS-issued SIGMET Yankee was canceled at 1630 because the current pilot reports (PIREPS) indicated that previously forecasted turbulent conditions had diminished. Although an AIRMET was in effect at the time of the accident for moderate or greater turbulence, there were no other supporting indicators to the airline staff meteorologist that moderate or greater turbulence was present along the route of flight. Due to the cancellation of the SIGMET and the lack of additional supporting information for moderate or greater turbulence, the meteorologist did not issue a SIGMEC. Therefore, the turbulence information was not on the flight release provided to the flight crew.
Probable cause
the in-flight encounter with turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA105
- Event ID
- 20050310X00294
- Case number
- LAX05LA105
- 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, damage. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-02-12.
- API snapshot SHA-256: 3ec07a8888f3f2ce2b4b0a34197c1c9c70809f6eb21fff193c274991d013ca2f; retrieved 2026-09-18T15:06:25.377Z.