Plane Crash List

Beechcraft HAWKER 900XP N526FC

20 July 2024 · Telluride, Colorado, United States · No injuries

Summary

On 20 July 2024 at about 19:39 local time, a Beechcraft HAWKER 900XP registered N526FC, operated by Foreshore Capital, LLC, was involved in an accident near Telluride, Colorado, United States. 2 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 19:39
Classification
Accident
Location
Telluride, Colorado, United States
Nearest airport
Telluride Rgnl (TEX)
Coordinates
37.9567, -107.9216
Aircraft
Beechcraft HAWKER 900XP
Registration
N526FC
Category
Airplane
Year built
2007
Engines
2
Operator
Foreshore Capital, LLC
Operating rule
Part 91: General Aviation
Purpose of flight
Positioning
Phase of flight
Not recorded
Route
Telluride → Miami
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
CEN24LA328

People

Nobody was injured.

On board Died Serious Minor Uninjured
2 0 0 0 2

Probable cause

The flight crew’s failure to properly configure the airplane for takeoff in a high-density altitude environment, which resulted in a loss of control and a subsequent runway excursion. Contributing to the accident was the flight crew’s failure to use checklists.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

The airplane landed at the high-elevation airport and the passengers disembarked. For the subsequent departure on the 7,111 ft-long runway, the pilot calculated that a takeoff roll of 6,800–6,900 ft would be needed with the wing flaps extended to 15°. The copilot was flying the airplane during the takeoff. During the departure takeoff roll on the dry asphalt, the airplane did not attain 75% of the planned takeoff speed about halfway down the runway, so the copilot decided to abort the takeoff. The brakes, air brakes, and thrust reversers were used to slow the airplane; however, the airplane did not slow down. Maximum braking was then applied, and the airplane began to depart from the runway to the right. The airplane traveled over the engineered material arresting system (EMAS) and came to rest upright. After exiting the airplane, the pilot saw the wing flaps were fully retracted and were not extended to 15°. The airplane sustained substantial damage to the lower fuselage. A review of the cockpit voice recorder (CVR) data found that during the startup, taxi, and attempted takeoff from runway 27, there was no discussion of checklist usage or configuration settings for the airplane. A review of the airplane flight manual (AFM) found two checklists where the flight crew sets and confirms the flap position before takeoff. Postaccident examination of the airframe confirmed flight control continuity. The flap handle and the flap mechanical indicator on the pedestal were found in the fully up position (0°). Both engines were found to be operating and responding to power lever inputs throughout the takeoff roll and the accident sequence. Airframe to engine control continuity for both engines was established. At the time of the accident, the estimated density altitude for the airport was 11,244 ft msl. A review of video footage from an automated weather observing system (AWOS) camera facing east showed an extended windsock with an east wind during the takeoff and subsequent aborted takeoff. The wind was from 120° at 12 kts, with gusts to 17 kts, which exceeded the airplane’s maximum tailwind component for takeoff. According to the FAA-approved AFM, for a field pressure altitude of 9,000 ft, a takeoff weight of 24,000–25,000 lbs, and an outside air temperature of 20°C, the runway length needed for takeoff would have been 6,448–7,035 ft with 15° flaps. For a field pressure altitude of 9,000 ft, a takeoff weight of 24,000–25,000 lbs, and an outside air temperature of 20°C, the runway length needed for takeoff would have been 7,912–9,308 ft with 0° flaps. Based on the available evidence, it is likely that the flight crew did not properly configure the airplane for the takeoff in the high-density altitude environment, as the flaps were found at 0° instead of 15°. Additionally, the flight crew attempted to take off with a tailwind that exceeded an operational limitation for the airplane. If the flight crew had used their checklists, the flaps would have been appropriately set during the before takeoff checks and the lineup checks.

Quoted verbatim from the NTSB record.

Other Beechcraft HAWKER accidents

Date Aircraft Location Operator Outcome Died
7 Feb 2024 Beechcraft HAWKER 900XP
N900VA
Westwater, Utah, United States Clay Lacy Aviation, Inc. Fatal 2
20 Jan 2025 Beechcraft HAWKER 800XP
N6NR
Minneapolis, Minnesota, United States - No injuries -
16 Oct 2025 Beechcraft HAWKER 800XP
XA-JMR
Bath, Michigan, United States Aerolineas del Centro Fatal 3
3 Nov 2023 Beechcraft HAWKER
5N-AMM
Ibadan, Nigeria
no coordinates
- No injuries -
21 Feb 2022 Beechcraft HAWKER 800XP
N99AP
Aspen, Colorado, United States Nxt Jet, Inc. No injuries -
14 Mar 2020 Beechcraft HAWKER 800XP
N100AG
Scottsdale, Arizona, United States - No injuries -

All 15 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
7 Jun 2024 Beechcraft V35A
N150WR
Arvada, Colorado, United States Whiskey Romeo LLC Fatal 1
24 Oct 2024 Cessna 172P
N62740
Falcon, Colorado, United States Doomac LLC DBA No injuries -
5 Sep 2024 Air Tractor AT-602
N602BA
Camden, Colorado, United States Scott Aviation Inc Fatal 1
27 Dec 2024 Cessna 560
N753MB
Pagosa Springs, Colorado, United States Metroplex Flight Services No injuries -
8 Sep 2024 Bellanca 7GCAA
N36008
Rifle, Colorado, United States - Serious injuries -
11 Sep 2024 Cessna 172
N20747
Englewood, Colorado, United States ATP Flight School Minor injuries -

All 170,864 records in United States