FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA08LA014 · Raytheon Corporate Jets Hawker 800XP

29 Oct 2007 · Santa Ana, CA, United States

Charter Communications Holding Raytheon Corporate Jets Hawker 800XP · Accident: fire during takeoff

From John Wayne Orange County International Airport (SNA) to Centennial Airport (APA)

Report a problem

Event

NTSB case
SEA08LA014
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

Raytheon Corporate Jets Hawker 800XP

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
N800CC
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Centennial Airport (APA), Denver, 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
Takeoff · rejected takeoff
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
Fire
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 › Procedures/directives, not followed

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

NTSB narrative

The pilot reported that during the first takeoff attempt, he noted that the engine was not spooling up normally and he aborted the takeoff, utilizing minimal braking to exit the runway. The airplane was taxied back for takeoff and 3 minutes later, the flight was cleared for takeoff again. During the takeoff roll, the pilot noted a warning light and again aborted the takeoff when the airplane was traveling at 20 to 30 knots, with minimal braking again used to exit the runway. The airplane taxied back once again and was cleared for takeoff 9 minutes later. During the takeoff roll for the third attempt, the pilot stated that at about 85 knots, he felt a rumble and heard a "pop" as the airplane started to drift to the left. The pilot called for an abort and was able to keep the airplane on the runway, eventually traveling into the overrun area at the end of the runway. The tower notified the flight crew that there was smoke and fire coming from the left main gear. Inspection of the landing gear found that the left main landing gear tires overheated and blew during the third takeoff attempt. The hydraulic line on the left main landing gear was severed when the tire blew and hydraulic fluid leaked out onto the hot brake surface and ignited. All of the wheels fusible plugs were blown. The Raytheon Aircraft Airplane Flight Manual states a required waiting period from completion of taxi-in following a rejected takeoff from a speed of 90 knots indicated airspeed or less, to before start of taxi-out for takeoff. After a single rejected takeoff, a waiting period of 25 minutes is required. After two or more successive rejected takeoffs, a waiting period of 45 minutes is required.

Probable cause

The failure of the pilot-in-command to follow procedures stipulated in the airplane flight manual regarding brake cooling time periods. Factors contributing to the accident were the intentional aborted takeoffs which resulted in the hot brakes, and the subsequent landing gear tire bursting.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA08LA014
Event ID
20071102X01707
Case number
SEA08LA014
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: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 7d2b6561b14dab00ea7cb18e5ba3786ee2a074107043aa82547c6a981158f7cc; retrieved 2026-09-22T03:18:20.660Z.