2024-02 · NASA ASRS report 2089930
Corporate jet flight crew reported momentary loss of aircraft control at 12;000 feet as a result of severe turbulence during descent into BZN airport.
On descent into BZN we were cleared to 12;000 feet in the vicinity of the GARNT waypoint. After passing GARNT; en route to LEVER on the approach; we encountered severe turbulence lasting about 15 seconds as we passed 12;000 feet. We had just descended below the overcast and were VMC. Prior to the event we were encountering pockets of moderate turbulence that was previously reported by two aircraft on approach in front of us.Anything not tied down became airborne and crashed violently to the floor. Drawers in the galley opened and the content was thrown all over the floor.It was a ferry leg so there were no passengers; all crew members were strapped in; and there were no personal injuries. Although we were thrown against our restraints several times.There were no abnormal indications in the cockpit after the incident. Cause: Severe turbulence Suggestions: Having a real time turbulence plot and mountain wave forecasting system in place. Making ForeFlight a mandatory application to provide pilots with real time reports of weather and turbulent conditions as the current application in use pales in comparison. I think it appropriate to point out that flight operations was more concerned with getting the aircraft cleaned up than the safety concerns of a severe turbulence encounter. Subtle pressure to call the event moderate turbulence rather than severe turbulence was brought to bear. They were unaware that a severe turbulence encounter required a maintenance inspection to determine the airworthiness of the aircraft. Less experienced pilots might have flown and the results may have been catastrophic.
During descent into Bozeman on an empty repo leg; roughly halfway between waypoints GARNT and LEVER (around 11000 ft MSL?); we encountered a pocket of severe turbulence. The two aircraft immediately in front of us on the descent had reported nothing more than moderate. We filed a PIREP with ATC and continued the descent as cleared. During the encounter; we heard all sorts of things crashing around and breaking in the cabin. I was able to visually verify from the cockpit that our cabin hostess was safe and secure in her seat and was not injured. During our RNAV GPS Y approach to Runway 30; Tower instructed us to go around as the preceding aircraft had not yet cleared the runway. We executed the go around and we were vectored back for a visual approach and uneventful landing on Runway 30. After shut down; I went back to assess the damage in the cabin and galley. Several galley drawers had come open; and there were shattered plates and glasses everywhere. Debris from the galley was found as far forward as the aft facing table seats in the cabin. We alerted operations and Dispatch as to our situation and called Maintenance Control to ask their guidance. Eventually; it was determined that the airplane would have to be inspected. What I found somewhat concerning is the number of people who a) were not aware that a severe turbulence encounter required an aircraft inspection; and b) the subtle-yet-clear attempts to get us to reverse course and categorize the event as just 'moderate turbulence' so as to be able to continue with our revenue leg from BZN-VNY. Nobody came out and said as much directly; but there were some very leading questions regarding the definitions of moderate and severe turbulence. We are professionals with many decades of experience between us. When we say we experienced severe turbulence; we do not do so flippantly or without careful consideration of the implications; so to have the company attempt; albeit subtly; to get us to change our story; seemingly for the sake of profitability and expediency; is a concern.Cause: Mountain wave turbulence.Suggestions: This was an unforecast; unforeseeable severe turbulence encounter. But the company needs to do a better job of supporting crews in these kinds of situations. Attempting to coerce crews into lessening the severity of the encounter so as to save time and money is never acceptable. Eventually the right and safe decisions were made; but it took us standing our ground with several departments in order to reach that conclusion.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
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.
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.
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.
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.