Hawker Beechcraft CORP HAWKER 900XP accident near Westwater, Utah, February 7, 2024
On February 7, 2024 at about 5:48 pm local time, a 2007 Hawker Beechcraft CORP HAWKER 900XP, registered N900VA, was destroyed in an accident during maneuvering near Westwater, Utah (Grand Junction Rgnl airport). It was a positioning flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
Preview. This page is not yet listed for search engines.
The NTSB's probable cause their words, unchanged
The flight crew’s decision to conduct a post-maintenance stall test in an area of icing conditions, which resulted in wing contamination that significantly decreased the airplane’s critical angle of attack. Also causal was the airplane manufacturer’s lack of training and experience requirements for the flight crew to safely conduct the stall test, which resulted in an attempted remedial action that aggravated the aerodynamic stall and led to a loss of control from which they were unable to recover. Contributing to the accident was the flight crew’s failure to follow the test conditions regarding cloud clearance, altitude limit, visual meteorological conditions, and ensuring all external surfaces were free from ice.
Source: NTSB aviation accident database, copy made October 4, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 7, 2024 · about 5:48 pm local time
- Place
- Westwater, Utah · Grand Junction Rgnl · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Hawker Beechcraft CORP HAWKER 900XP, built 2007 · all HAWKER 900XPs on the register
- Registration
- N900VA · no longer on the register · serial HA-0020
- Damage
- Destroyed
- Flight
- Positioning flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The flight crew, comprised of the pilot-in-command (PIC) and second-in-command (SIC), was conducting a stall test in the airplane following the recent removal, inspection, and reinstallation of the wing leading edges and de-ice panels as part of routine maintenance. The airplane departed normally, entered a climbing right turn to the northeast, and leveled off about 20,000 ft mean sea level (msl). In its final minute of flight, the airplane entered a rapid vertical descent consistent with a flat spin and never recovered. The airplane was mostly consumed by postcrash fire and was highly fragmented, which precluded a complete and thorough wreckage examination of the airframe and engines. A review of the flight data showed no anomalies with the flight controls or engines, as the flight control surface movements were consistent with the flight control inputs and engine performance matched the power lever movement. Performance data indicated that before the airplane entered the spin, it decelerated and its pitch attitude increased, consistent with the flight crew preparing to perform their planned post-maintenance stall warning and identification system checks. The airspeed then slowed further, with flaps retracted for the first system check. Performance calculations showed that the stick shaker activated about 117.5 kts, one knot below the activation speed for the stick shaker at flaps zero. The stick pusher then activated at 113.5 kts, 3 kts above the stick pusher activation speed. Given the airplane’s weight and load factor, the shaker and pusher both activated at appropriate speeds; however, the airplane entered the stall at the same time the stick shaker activated, which provided no warning to the flight crew. The correct stall warning sequence should be stick shaker, stick pusher, then, if the pilot does not attempt a stall recovery, stall entry. The stall warning sequence for the accident flight, with the stall occurring at the same time the stick shaker activated, was likely due to a degradation in the relationship between lift and angle of attack (AOA) from wing contamination, either by icing or the airplane’s recent maintenance. A weather study showed that the airplane was in instrument meteorological conditions (IMC) during some or all of its climb from 5,000 ft through 16,700 ft msl and could have accreted up to 1 mm of ice on the wings during this time. An icing study determined that even a 2-minute icing encounter could have reduced the maximum coefficient of lift by up to 40% and reduced the stall AOA by up to 6°. Wing Contamination Two AIRMETs were issued about 2.5 hours before the accident flight for moderate icing throughout the airplane’s climb and cruise altitude for the stall test. In addition, video showed that the departure airport was surrounded by obscuration and precipitation during takeoff. Evidence showed that the flight crew was aware of the presence of sleet and “storm” conditions before departure during their interactions with maintenance personnel. The presence of these conditions should have given the flight crew pause before they executed the stall test, which required visual meteorological conditions and no icing according to the airplane’s Pilot’s Operating Manual (POM). The airplane recently underwent routine maintenance to inspect the wing leading edges for signs of cracks and corrosion. This inspection included an extensive inspection of the flight controls and wing ribs that required a removal of the leading edges, numerous inspection panels, and control surfaces. After maintenance, the wings were subject to multiple inspections for the reinstallation of the TKS panels and wing leading edges and a final post-maintenance inspection of the leading edges. While the postcrash fire prevented the investigation from determining if there was any wing contamination that was introduced by the maintenance team during reassembly, the number of post-maintenance and preflight inspections decreases the likelihood of improper maintenance. Stall Test Conditions During the flight, the crew complied with most of the stall test conditions required by the POM: an empty ventral tank, an operative stall identification system, and autopilot OFF. However, the pilots did not follow the cloud clearance and height limitations prescribed by the stall test procedure. Audio from the cockpit voice recorder also indicated that the flight crew knowingly chose to execute the stall test above clouds about 2,000 ft above the prescribed maximum altitude. There is also no evidence they attempted to verify that the external surfaces were free of ice after flying through IMC and icing conditions despite the airplane being equipped with an ice detection spotlight system that could have been used to illuminate the wing fairings. The airplane was also equipped with an ice detector that had to be manually activated by the flight crew as it was not directly connected to the airframe ice protection system. Flight recorder data and cockpit voice recorder audio indicated that the flight crew intentionally departed without engine ice protection and likely without airframe ice protection. The reason for this decision is unknown but may have been to prevent the de-icing fluid from contaminating the airflow over the wing during the stall test. After the airplane entered the stall, the flight crew input full left-wing-down aileron when the airplane abruptly banked right and applied full power and full aft control column, which aggravated the aerodynamic stall/spin. The flight crew’s attempted remedial action suggested that they were insufficiently trained for the flight and the brief guidance from the POM provided no clear instructions for the possible consequences of “unacceptable stall characteristics” referenced as a cautionary note or a proper recovery. Stall Test Pilot Qualifications The structural repair manual (SRM) offers only a broad definition of those qualified to perform the stall test flight, requiring that the pilot be “familiar with the stall identification system and stall characteristics” of the airplane. Further, the stall section of the POM states that “pilots conducting stall checks should have prior experience in performing stalls in the Hawker and must be prepared for unacceptable stall behavior at any point leading up to and throughout the maneuver.” In the previous year, the flight crewmembers attended separate simulator training sessions at a commercial facility for the SIC’s initial training and the PIC’s recurrent training. These courses covered the operation of the stall warning and identification system (shaker and pusher), which is focused on recognizing and avoiding stalls. The simulator training was not designed to teach full stalls, including stall entry, or to prepare the crew for a possible uncommanded roll as described in the stall section of the POM. Although the PIC participated in a stall test flight 4 years before the accident, it was likely with limited involvement in the test as he was SIC at the time. The SIC for the accident flight had not participated in a stall test before the accident flight. Therefore, it is unlikely that the flight crewmembers’ simulator training on the stall warning and identification system and the PIC’s previous participation in a stall test flight adequately prepared them to safely conduct a stall flight test or address any unacceptable stall behavior. The accident was the result of the flight crew’s decision to conduct a post-maintenance stall test in an area of icing conditions, which resulted in wing contamination that significantly degraded the airplane’s critical angle of attack. The airplane manufacturer’s lack of training and experience requirements to ensure flight crew preparedness to safely conduct the stall test resulted in an attempted remedial action that aggravated the aerodynamic stall and led to a loss of control from which the flight crew was unable to recover. Contributing to the accident was the flight crew’s failure to follow the test conditions related to cloud clearance, altitude limit, visual meteorological conditions, and ensuring all external surfaces were free from ice.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during maneuvering defining event
The NTSB's findings
- Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
- Personnel issues › Experience/knowledge › Training › Total instruct/training recvd › Flight crew
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Angle of attack › Not specified
- Personnel issues › Task performance › Use of equip/info › Use of policy/procedure › Flight crew
- Personnel issues › Task performance › Use of equip/info › Use of equip/system › Flight crew
- Personnel issues › Task performance › Use of equip/info › Aircraft control › Flight crew
- Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Pitch control › Incorrect use/operation
- Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to structural icing › Decision related to condition
- Environmental issues › Conditions/weather/phenomena › Temp/humidity/pressure › Conducive to structural icing › Effect on equipment
- Organizational issues › Management › Policy/procedure › Adequacy of policy/proc › Manufacturer
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane
- Flight time: 8,188 hours in all; 70 in this make and model; 32 in the last 90 days; 4,062 as pilot in command
- Last flight review: October 6, 2023
- Medical certificate: Class 1 (with waivers/limitations)
- Seat: rgt
- Injury: fatal
Pilot
- Certificate: airline transport pilot
- Ratings: multi-engine land; single-engine land; instrument: airplane
- Flight time: 15,734 hours in all; 2,249 in this make and model; 32 in the last 90 days; 12,190 as pilot in command
- Last flight review: October 28, 2024
- Medical certificate: Class 1 (waiver time limited special)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 4,704 hours
- Last inspection: annual inspection, February 2, 2024
- Maximum gross weight: 28,120 lb
- Seats: 10
- Landing gear: retractable
- Engine 1: Honeywell TFE731-50R-1H (turbofan); 4,686 hours total
- Engine 2: Honeywell TFE731-50R-1H (turbofan); 4,537 hours total
- Fire on the ground
- Operator: Clay Lacy Aviation, Inc.
The flight
- Departed from: GJT Grand Junction CO at 5:37 pm
- Destination: TIW Tacoma WA
- Flight plan: IFR
- A second pilot was aboard
Weather at the time
- Light: daylight
- Wind: from 260° at 10 knots
- Visibility: 10 statute miles
- Sky: overcast at 10,000 ft; a few clouds at 6,000 ft
- Temperature: 46°F (8°C), dew point 30°F (-1°C)
- Altimeter: 29.59 inHg
- Observation at 11:53 am from KGJT, 25 miles away
Weather report (METAR): KGJT 071853Z 26010KT 10SM FEW060 FEW080 OVC100 08/M01 A2959 RMK AO2 RAE30 SLP994 P0000 T00781006
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
33 documents, released by the NTSB on December 23, 2025. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
About this page
Everything above comes from the NTSB's public accident database: the narrative, probable cause and findings are the NTSB's own words, and the coded tables behind its report (pilot, aircraft, flight, weather, injuries, sequence of events) are written out in plain English. Pilots' ages, home towns and medical details are left out on purpose. The documents and photographs are the NTSB's docket, the folder of records gathered during the investigation, shown as the NTSB released them (the NTSB redacts some personal details first) and listed under the NTSB's own titles. This site's own text never names pilots, passengers or anyone else involved. A preliminary report describes what is known soon after the event and can change; the final report, with the probable cause, usually follows one to two years later and this page is refreshed when it does. Case number WPR24FA083.
