The U.S. aircraft register, updated daily
Accidents · NTSB WPR20LA109 · Final report

Raytheon HAWKER 800XP accident near Scottsdale, Arizona, March 14, 2020

On March 14, 2020 at about 11:00 pm local time, a 2005 Raytheon HAWKER 800XP, registered N100AG, was substantially damaged in an accident during landing (flare/touchdown) near Scottsdale, Arizona (Scottsdale airport). It was an executive or corporate flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot’s inability to maintain directional control during landing for undetermined reasons, which resulted in a runway excursion.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
March 14, 2020 · about 11:00 pm local time · cases in 2020
Place
Scottsdale, Arizona · Scottsdale · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Raytheon HAWKER 800XP 850XP, built 2005
Registration
N100AG · registry record · serial 258747
Damage
Substantial damage
Flight
Executive or corporate flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The pilot stated that, upon landing, the airplane touched down on the runway centerline with light and variable wind conditions. The pilot recalled that the touchdown felt normal but that, during the landing roll, the airplane began to veer to the right. The pilot added full left rudder, but the airplane continued to veer off the runway surface and encountered large rocks located between the runway and taxiway. A postaccident operational check of the nosewheel steering system revealed no mechanical malfunctions or anomalies that would have precluded normal operation. The left nosewheel tire was not adequately inflated and was worn to the point at which the cord was exposed; the right nosewheel tire was within tolerances. Also, one-third of the rim was absent on the left nosewheel tire outer wheel half. The available evidence precluded a determination of whether the imbalance between the nosewheel tires contributed to the control problem on the runway. It could also not be determined if the left nosewheel tire damage occurred before the touchdown or as a result of the accident sequence.

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

  1. Loss of control on ground during landing (flare/touchdown) defining event
  2. Runway excursion during landing (landing roll)

The NTSB's findings

  • Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Directional control › Not attained/maintained
  • Not determined › Not determined › (general) › (general) › Unknown/Not determined

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 9,150 hours in all; 650 in this make and model; 52 in the last 90 days; 15 in the last 30 days; 6,786 as pilot in command; 364 on instruments
  • Last flight review: November 21, 2019
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot, commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 10,556 hours in all; 52 in the last 90 days; 15 in the last 30 days
  • Last flight review: September 14, 2019
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,823 hours
  • Last inspection: continuous airworthiness programme
  • Maximum gross weight: 28,000 lb
  • Seats: 9
  • Landing gear: retractable
  • Engine 1: Honeywell tfe731-5br-1h (turbofan); 4,726 hours total
  • Engine 2: Honeywell tfe731-5br-1h (turbofan); 4,761 hours total

The flight

  • Departed from: ROG Rogers AR at 8:15 pm
  • Destination: SDL Scottsdale AZ
  • Flight plan: IFR
  • Runway 21, 8,249 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: scat at 6,000 ft
  • Temperature: 70°F (21°C), dew point 43°F (6°C)
  • Altimeter: 30.05 inHg
  • Observation at 10:53 pm from SDL

Injuries

FatalSeriousMinorNone
Flight crew2

Photographs from the investigation 2 pictures from the NTSB's docket, as the NTSB released them

The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on June 14, 2022. 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.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/WPR20LA109.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.