FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DEN07LA078 · Dassault Aviation Mystere Falcon 900C

23 Mar 2007 · Rifle, CO, United States

XOJet Dassault Aviation Mystere Falcon 900C · Accident: overrun during landing

From Scottsdale Airport (SDL) to Garfield County Regional Airport (RIL)

Report a problem

Event

NTSB case
DEN07LA078
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
Accident
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
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Dassault Aviation Mystere Falcon 900C

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
N129KJ
Operator
XOJet
Onboard fatalities
Unknown
Route
From Scottsdale Airport (SDL), Scottsdale, AZTo Garfield County Regional Airport (RIL), Rifle, CO
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 91: General Aviation
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 · landing roll
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
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Airspeed(vref), excessive
  • Pilot in command › Planning/decision, improper
  • Pilot in command › Proper touchdown point, not attained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to departure, the airplane was fueled with approximately 17,500 pounds (lbs) of fuel, which allowed a landing weight at the destination of greater than 2,000 lbs. under maximum gross landing weight. The pilot "did not use wet runway performance numbers...[and] did note the 135 landing distance requirements as an aid for safety margin; approximately 6,600 feet." During the downwind leg to runway 26, the crew could see the runway. Prior to the final approach fix for the instrument landing system (ILS) approach to runway 26 and approximately 8 miles from the airport, the crew had the runway in sight. The pilot flew the airplane on the glideslope approximately VRef (Final Approach Speed) 128 knots plus 10-15 knots, then below 1,000 feet, VRef plus 10 knots. The crew reported that the airplane touched down approximately 1,500 feet from the approach end of runway 26. The co-pilot reported the airbrake was in the #2 position and they had "good anti-skid indication" after touchdown. The pilot began braking, deployed the thrust reverser, and continued to increase brake pressure. With approximately 2,500 feet of runway remaining, the airplane continued to not decelerate normally, and the pilot knew they did not have enough runway to execute a go-around. With approximately 1,000 feet of runway remaining, the pilot pulled the parking brake to the second detent, and the aircraft slid off the end of the runway into the dirt and muddy terrain. A performance study revealed that the accident flight crossed the runway 26 threshold at 150 knots airspeed (VRef plus 22 knots) and touched down 2,300 feet from the threshold at 141 knots airspeed (VRef plus 13 knots), with a minus 1 foot per second vertical speed. Immediately at touchdown, the spoilers were deployed. Approximately 4 seconds later and 3,260 feet from the threshold (3,740 feet of landing distance remaining), the thrust reverser was fully deployed with engine 2 fan speed (N1) reaching about 100 percent 9 seconds later. The airplane continued to roll down the runway with the thrust reverser deployed and exited the end of the runway at about 65 knots ground speed coming to a stop in the safety area approximately 268 feet from the end of runway 26. The airport featured one ungrooved asphalt runway, Runway 8/26, which was 7,000 feet by 100 feet, and had a 1.25 percent downslope gradient to the west. According to the airport/facilities directory, the airport remarks section notes, "Runway 08-26 slick when wet, airport manager recommends landing uphill on runway 08 when able." The accident airplane's flight manual does not provide any data on runway slope effect on the landing distance, therefore, the distances mentioned above would increase for landing on runway 26 which has a negative (down) 1.25 percent slope. Since 2001, 12 business jet aircraft have experienced a runway overrun on runway 26. All but one of the overruns included "wet" runway conditions. Since the accident, the runway has been grooved and plans are proceeding with a runway improvement project.

Probable cause

The pilot's improper decision to land with excessive airspeed during the approach and failure to obtain the proper touchdown point, which resulted in a runway overrun. Contributing factors were the pilot's failure execute a missed approach, to use available reverse thrust in a timely manner, and the wet, ungrooved, downsloped runway.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DEN07LA078
Event ID
20070405X00373
Case number
DEN07LA078
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 2007-03-24.
  • API snapshot SHA-256: 072885546003ebbbca5c35e0cf66918f3e5441922edc1b58c5fc81ac42e57019; retrieved 2026-09-22T03:57:46.505Z.