19 May 2008: MCDONNELL DOUGLAS DC10 30 — Omni Air International

19 May 2008: MCDONNELL DOUGLAS DC10 30 (N720AX) — Omni Air International

No fatalities • Pacific Ocean, United States

Probable cause

An inadvertent in-flight encounter with unforecasted clear air turbulence

— NTSB Determination

Accident narrative

On May 19, 2008, about 1340 UTC, a McDonnell Douglas DC-10-30, N720AX, operated by Omni Air International, as a Title 14 CFR Part 121 supplemental, non-scheduled international passenger flight, reportedly experienced moderate turbulence, over the Pacific Ocean, while in cruise flight at FL360, about 450 nautical miles east of the Territory of Guam, United States of America. The airplane subsequently landed in Guam, uneventfully. Visual meteorological conditions prevailed, and an instrument flight rules flight plan was filed. Of the 150 passengers and 12 crewmembers on board, two passengers and two flight attendants received minor injuries, and one flight attendant received serious injuries. The flight originated at Honolulu International Airport, Honolulu, Hawaii, the same day, about 0745 UTC.

According to Omni Air International’s Director of Safety, the accident captain stated in his irregularity report that at approximately 1330z while at 36,000 feet, they encountered moderate turbulence. He said that the ride had been smooth for the whole flight and that the seatbelt sign had been off. There was some thunderstorm activity in the area, and the airplane’s radar indicated the presence of a cell about 30 miles south of the airplane’s position, with tops that reached about 28,000 to 30,000 feet. The pilot said that they saw some towering cumulus clouds in the area, but that the ride still continued to be smooth. The lead flight attendant was on the flight deck, and they encountered an area of higher clouds, but the radar did not indicate any activity. The Captain said that within a few seconds they felt an initial bump, followed by moderate turbulence. The seatbelt sign was then turned on, and the lead flight attendant sat in the observer’s seat. According to the Captain the turbulence lasted only a few seconds, after which the lead flight attendant left the flight deck. A few minutes later the lead flight attendant communicated with the flight deck and informed the Captain of the injured passengers and flight attendants.

The lead flight attendant stated that about 1330Z they encountered "bad turbulence", which lasted about 30 seconds. She further stated that she was in the cockpit at the time, and as soon as the turbulence was gone she left the cockpit to check on everyone, at which time another flight attendant informed her that two flight attendants were "down." She then communicated with the flight deck and relayed the information to the captain.

Another flight attendant stated that the flight encountered two turbulence events while the cabin crew was making preparations for the second meal service. She said that the turbulence in the first event was slight but the second event was "drastic." She said that the second turbulence event caused her to hit the ceiling and then her entire body descended and slammed to the floor.

The accident airplane’s flight data recorder (FDR) was sent to the NTSB’s Recorder Laboratory, Washington DC, for readout, and was found to contain 14 minutes of data pertaining to the accident flight. The data indicated that at 13:27:22 FDR Recorded GMT, at a pressure altitude of 36,000 feet, the vertical acceleration changed from 0.9 g’s to 1.8 g’s to -0.5 g’s to 1.7 g’s and then back to 0.9 g’s all within 3 seconds. The data showed that the airplane’s autopilot had been engaged, and that there was lateral acceleration during the drop in altitude, without corresponding flight or engine control input, consistent with severe clear air turbulence. See the NTSB FDR Factual Report.

In addition, the NTSB conducted a meteorological study using data to include synoptic, upper air, and satellite data. See the NTSB Meteorological Factual Report.

Contributing factors

  • cause Clear air turbulence

Conditions

Weather
VMC

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.