SkyWest Airlines Flight 3855
Bombardier CL-600-2B19 · Incident: loss of control in flight during landing
From Salt Lake City International Airport (SLC) to Rapid City Regional Airport (RAP)
Event
- NTSB case
- CHI04IA056
- 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
- Incident
- 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
- Instrument Meteorological Cond
Bombardier CL-600-2B19
- Aircraft type
- Bombardier CL-600
- 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
- N595SW
- Operator
- SkyWest Airlines
- Onboard fatalities
- Unknown
- Route
- From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Rapid City Regional Airport (RAP), Rapid City, SD
- 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
- Landing · flare/touchdown
- 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
- Loss of control 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
Cause areas
- Copilot/second pilot › Aircraft control, not maintained
- Pilot in command › Remedial action, delayed
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, being operated on a scheduled passenger flight, contacted the runway with the left wing tip, following a loss of control while landing. Weather conditions were varying due to freezing fog that was moving into and out of the area. The control tower at the destination airport was closed and the airplane was being controlled by a near-by approach control facility. After holding in-flight to wait for the weather to improve, the crew began the instrument landing system (ILS) approach when the visibility was reported as one-half mile. The captain stated that almost immediately upon entering the top of the fog layer they received an ICE caution message. He stated they turned on the wing and engine inlet anti-ice, but the ice accumulation on the windshield wipers was rapid and ice was accumulating on the winglet. The captain stated the approach lights came into sight when they were just above minimums and that he had the runway in sight at approximately 140 feet above the ground. The first officer then disconnected the autopilot and the nose came up slightly. He stated he informed the first officer to keep the nose down and add thrust. The captain stated they were slightly left of the centerline and the first officer was making "small" corrections back to the right. He stated the airspeed was just inside the "bottom of the bucket" and the trend vector was indicating a decrease in airspeed. The captain stated he "again said something about more thrust and keeping the nose down." He stated the airplane continued to move to the right of the centerline and he took control of the airplane. He stated the airplane responded "poorly" feeling "heavy and sluggish." The captain stated the airplane was close to the right side of the runway and he added thrust at which time the ailerons became more responsive. He stated the left wing dropped, scraping the runway, at about the same time the left main gear touched down. The captain stated the airplane bounced into the air then landed hard on the runway. The crew then taxied the airplane to the gate. The first officer stated that when the captain reported having the runway in sight, she transitioned her sight outside of the airplane and realized she needed to correct to the right. She stated she began the correction at which time the nose of the airplane pitched up, the airplane veered toward the correction, and it started sinking toward the right side of the runway. She stated the captain took over the controls, but the airplane dropped to the runway, bounced, and touched down harder the second time. The first officer, who was flying the approach, had about 15 hours of total flight time in the CL-600. The captain, who was also a check airman, had a total of 1,196 hours of flight time in the CL-600. At the time of the accident the local weather was reported as being visibility 1/4 mile in freezing fog, vertical visibility 100 feet. Inspection of the airport and airplane on the afternoon following the incident revealed ice was still visible on the antennas, windshield wipers, radome, winglets, and horizontal and vertical stabilizers. The main body of ice on these structures measured between one-half to five-eights of an inch thick and that the main body of ice plus the "ice spines" totaled three-quarters of an inch thick. A Kinematic parameter extraction showed loss of lift consistent with airframe icing but there was no early stall due to icing prior to touchdown and no indication that airframe icing had caused any loss of control. Marks on the ground and on the runway revealed the airplane initially touched down 1,976 feet from the approach end of the runway with the right main landing gear in the grass off the side of the runway. The left wing tip then left a 63-foot long scrape mark on the runway, which was followed about 1,100 feet later by another set of tire marks. Data from the flight data recorder showed the airplane rolled slightly to the left followed by a roll to the right when the autopilot was disengaged. It then showed the airplane touched down with a vertical acceleration of at least 1.8g's. The airplane then became airborne in a 16-degree left bank, with a 5-degree nose up pitch at which time the ground and flight spoilers deployed contributing to the firmness of the 3.25 g touchdown one second later.
Probable cause
The copilot's failure to maintain control of the airplane during the landing and the captain's delay in initiating remedial action. Factors contributing to the accident were the low ceiling and low visibility due to fog, and the aircraft's deviation from expected performance due to airframe icing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04IA056
- Event ID
- 20040121X00083
- Case number
- CHI04IA056
- 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. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2004-01-18.
- API snapshot SHA-256: 9ae90bc7fc5b6f0d5884cd0ac7474a3a5efad45068526a54ad4dc65a960f822f; retrieved 2026-09-18T15:31:37.109Z.