FedEx Beechcraft Aborts Takeoff After Boeing 747 with Horses Crosses Runway

Casualties unknown • Ontario, CA, US

A FedEx Beechcraft E18S aborted its takeoff roll after spotting a Boeing 747 carrying race horses still taxiing across the active runway. The aircraft registrations were N3657G and N8172G.

What happened

The incident involved two aircraft operating at the same airport on the same runway, designated RWY 8L. A Beech E18S, registered as N3657G and operating under Federal Express flight number 954L, received clearance to begin its takeoff roll. Prior to this clearance, a Boeing 747, registered as N8172G and operating as Interflight flight 429, had been cleared to cross the same runway.

The Boeing 747 was transporting a cargo load that included race horses. Due to the excitable nature of these animals, the crew of the Boeing 747 was forced to taxi at a significantly reduced speed. Consequently, the large jet remained on the active runway longer than typical for a crossing maneuver.

As the Beechcraft E18S initiated its takeoff roll, it was a tailwheel-equipped aircraft requiring specific handling during the initial phase of acceleration. When the pilot raised the tailwheel to lift the nose, the view forward improved, revealing the Boeing 747 still occupying the runway ahead. Recognizing the imminent collision hazard, the pilot-in-command of the Beechcraft immediately aborted the takeoff.

Post-incident statements from the Beechcraft's pilot indicated that his aircraft was approximately 500 to 1,000 feet away from the Boeing when the decision to abort was made. The ground controller had coordinated the crossing clearance for the Boeing with the local controller responsible for the runway. Both air traffic controllers maintained an unobstructed view of both aircraft from their positions within the control tower.

The investigation

The investigation focused on the sequence of events leading to the near-collision and the coordination between air traffic control sectors. It was determined that the delay caused by the live animal cargo was a primary factor in the runway occupancy time exceeding normal expectations for the Boeing 747.

Findings

The proximity of the two aircraft during critical phases of ground operation highlighted the risks associated with mixed operations involving large jets and smaller, tailwheel-equipped planes. The successful avoidance of a collision relied heavily on the visual detection by the Beechcraft crew and the timely abort decision. The air traffic control team had adequate visibility to monitor both aircraft, but the timing of the takeoff clearance relative to the runway crossing created a conflict that was only resolved by the pilot's reaction.

Safety message

Operations involving live animal cargo can result in unpredictable delays due to animal behavior. Pilots and controllers must remain vigilant for extended runway occupancy times when such cargo is present, particularly during simultaneous takeoff and crossing clearances.

Probable cause

The pilot-in-command of the Beechcraft E18S aborted the takeoff after visually detecting a Boeing 747 still occupying the runway. The Boeing's slow taxi speed was caused by the excitable nature of race horses in its cargo, which extended its runway occupancy time beyond normal limits.

Frequently asked questions

What happened in the 1984-03-15 Beech C-45G accident near Ontario, CA?

A FedEx Beechcraft E18S aborted its takeoff roll after spotting a Boeing 747 carrying race horses still taxiing across the active runway. The aircraft registrations were N3657G and N8172G.

What aircraft was involved and where did it happen?

The accident on 1984-03-15 involved a Beech C-45G, registration N3657G, at Ontario, CA.

What was the probable cause of the accident?

The pilot-in-command of the Beechcraft E18S aborted the takeoff after visually detecting a Boeing 747 still occupying the runway. The Boeing's slow taxi speed was caused by the excitable nature of race horses in its cargo, which extended its runway occupancy time beyond normal limits.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20001214X39056. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.

Loading the flight search…