CEN15IA014 · Raytheon Aircraft Company HAWKER 800XP
Raytheon Aircraft Company HAWKER 800XP · Incident: system/component malfunction/failure (non-power) during takeoff
From Centennial Airport (APA) to Arnold Palmer Regional Airport (LBE)
Event
- NTSB case
- CEN15IA014
- 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
- Incident
- 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 Aircraft Company HAWKER 800XP
- Aircraft type
- Raytheon HAWKER
- 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
- N694ES
- Operator
- Eaton Metals
- Onboard fatalities
- Unknown
- Route
- From Centennial Airport (APA), Denver, COTo Arnold Palmer Regional Airport (LBE), Latrobe, PA
- Aircraft age
- About 10 years (built 2004)
- 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
- Defining eventThe 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Minor
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The commercial pilot and the airline transport pilot were operating a business flight. According to the operator, the pilots reported that, during the takeoff roll, they felt and heard a vibration emanating from the airframe. They continued the takeoff and retracted the landing gear. Air traffic control tower personnel radioed the pilots and informed them that they had momentarily observed white smoke coming from the airplane. Shortly after, the hydraulic low pressure lights illuminated. The pilots returned to the airport but were unable to extend the landing gear normally. They subsequently attempted to extend the landing gear using the alternate gear extension procedures without success. Due to the hydraulic system malfunction, the pilots diverted to an airport with a longer runway and landed the airplane with the flaps and gear retracted.
An examination of the airplane revealed that the No. 2 (inboard) tire on the left main landing gear assembly had ruptured, which resulted in the servo block separating from its actuator. The separation of the servo block resulted in the loss of both the normal and emergency hydraulic system pressures.
There were no obvious signatures of cuts or foreign object damage to the tire's external layer, and no manufacturing anomalies of the tire were noted. An examination of the tire fragments revealed wrinkles on the inner liner of the tire shoulder area consistent with overdeflection. The tire could have become overdeflected if it was operated below the recommended pressure and/or if it was overloaded. According to the operator, tire pressures were checked before flight, but the pressures were not recorded; therefore, it could not be determined whether the incident tire was consistently operated at the recommended pressure. The operator was not aware of any overloaded condition of the airplane.
Due to similar incidents, the airplane manufacturer had previously issued a service bulletin (SB), which recommended the installation of a landing gear jack that had improved servo block mounting hardware that would prevent separation of the servo block in the event of a tire failure. The SB recommended installing the landing gear jack with the improved hardware at the next landing gear jack replacement or overhaul; however, the airplane had not required a landing gear jack overhaul or replacement and, therefore, it did not have the improved servo block mounting hardware installed. No similar failures involving the improved mounting hardware have been reported.
Probable cause
The failure of the main landing gear tire, which resulted in separation of the servo block and subsequent total loss of all hydraulic system pressure and prevented the landing gear from extending before landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN15IA014
- Event ID
- 20141016X45532
- Case number
- CEN15IA014
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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. 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: 0880b5a4c41a1c697a15b61a3d4e8a1e2720f3e4804fd2caaa650f146a0a1e7c; retrieved 2026-09-16T01:51:35.404Z.