A Raytheon Hawker Beechjet 400A staged a dramatic, but ultimately non-fatal, sequence that began with a controlled glide into the low altitude environment and ended with a mechanical problem after rollout—an incident highlighted in a Flight Safety Foundation report focused on hazards uncovered in official investigation findings. The episode, described as a “dead-stick landing” event, involved minor damage and no injuries, underscoring that pilot actions can preserve safety even when something goes wrong during the landing phase.
According to the Flight Safety Foundation’s account in its “OnRecord” section, the aircraft was being flown on a fractional ownership positioning mission from Indianapolis, Indiana, to Marco Island, Florida, on the afternoon of Nov. 28, 2005. At the time the operation was underway, the Beechjet had been established at high altitude—flown at Flight Level 400 (approximately 40,000 feet) for 30 minutes and at FL 380 for about 15 minutes—before the next descent clearance came from air traffic control.
The report states that after the crew received clearance from air traffic control (ATC) for further descent to FL 330, the aircraft continued in the approach-to-landing context that would later involve a landing gear deployment that was not accomplished through normal automated means. While the available excerpt focuses on the immediate low-altitude events rather than the preceding trigger, it makes clear that the critical configuration change—landing gear extension—required manual action.
As the flight came down, the aircraft was described as being at about 9,000 feet when the landing gear was extended manually. That manual extension marked a key departure from standard procedure during a phase where airspeed management, energy management, and checklist adherence are particularly important. The excerpt then notes that the Beechjet emerged from the clouds at about 1,200 feet. The cloud break at that relatively low altitude suggests that visibility and pilot workload may have been challenging during the final segments of the descent and approach.
After the aircraft reached the ground, the sequence continued in a way that further illustrates the layered nature of landing risk: the report indicates that following the landing and the rollout off the runway onto a taxiway, the right landing gear tire deflated. In other words, the touchdown and initial roll did not immediately prevent continued ground movement, but the tire failure occurred after the runway phase, during the transition to taxiway operations.
The Flight Safety Foundation text emphasizes the broader safety purpose of such “OnRecord” summaries: they are presented to increase awareness of problems identified by official investigative authorities, with the aim of preventing similar outcomes. In this case, the combination of manual gear extension, a low cloud-break height, and subsequent tire deflation offers a snapshot of how multiple issues can converge around the landing moment without turning into an accident with injuries.
While the excerpt does not specify the root cause of the right tire deflation, its mention of minor damage and no injuries suggests that the crew maintained control and that the aircraft’s ground handling did not escalate into a more severe event. Still, the incident points to the practical need for well-understood procedures for landing gear configuration—especially if circumstances require manual extension—and for disciplined post-landing attention to signs of abnormal indications during rollout and taxi.
For pilots and operators of Beechjet 400A aircraft, the safety lessons associated with landing gear reliability are complemented by the presence of service guidance and mandatory inspection frameworks within manufacturer documentation. Industry references listing Hawker Beechcraft service bulletins show that operators have long relied on formal maintenance and inspection programs to address potential component concerns, including items connected to landing gear and braking systems. For example, a service bulletin listing includes mandatory inspection requirements for brake-related assemblies, demonstrating how manufacturers routinely direct attention to systems that can affect landing and ground operations (Aviation DataBase).
Although the bulletin list in the provided source snippet does not explicitly name the exact component involved in this specific tire deflation, it reinforces a general point: after landing gear deployment issues and ground roll anomalies, thorough inspection of tires, wheels, brakes, and related interfaces becomes essential. Tire deflation after rollout can be influenced by factors such as pre-existing damage, wear, improper inflation, impacts, or braking heat—each of which falls within the realm of maintenance programs and inspection schedules.
In fractional ownership and positioning contexts, crews may also benefit from robust training and clear guidance tailored to abnormal and degraded landing scenarios, particularly when aircraft configuration changes depend on manual actions. The Flight Safety Foundation’s framing of the incident as a hazard-related item—specifically associated with “No Training or Guidance on Hazard” in the excerpt—highlights a recurring safety theme: when abnormal conditions arise, crews perform better when they have rehearsed decision-making and troubleshooting steps that match the scenario.
Even so, the outcome in this case remains a strong indicator of effective crew performance. The Beechjet broke out of clouds at roughly 1,200 feet, landed, rolled off the runway onto a taxiway, and then experienced right tire deflation without injuries. The report’s emphasis on minor damage implies that the aircraft remained controllable and that the consequences were limited despite the complication on the ground.
Ultimately, this incident illustrates the interconnected risks of descent, configuration management, and post-touchdown monitoring. The manual landing gear extension at about 9,000 feet, the cloud break near 1,200 feet, and the post-runway tire deflation all form a chain of events that safety investigators use to educate operators—so that future flights can anticipate, detect, and respond to similar hazards with preparation and procedural clarity. For readers seeking the original investigative summary, the account appears in the Flight Safety Foundation’s AEROSafetyWorld compilation (Flight Safety Foundation).
SHOP AMAZON BEST SELLERS, CLICK TO BUY FROM AMAZON.
SHOP AMAZON BEST SELLERS, CLICK TO BUY FROM AMAZON.
