Date: 8th December 2024
Location: El Dorado International Airport, Bogota, Colombia
Aircraft: Boeing 767-300 Freighter, registration HP-3310DAE
Operator: DHL Aero Expreso
Flight Number: D5-926
Route: Bogota (BOG) to Miami (MIA)
Occupants: Unknown (crew only)
Injuries: None reported
Summary of Events
On 8th December 2024, a DHL Aero Expreso Boeing 767-300 freighter, operating flight D5-926 from Bogota to Miami, rejected its takeoff from runway 14R at El Dorado International Airport at a high speed of approximately 160 knots. The aircraft slowed safely and vacated the runway but became immobilised on a taxiway due to deflated tyres on both the left and right main landing gear. The cargo had to be unloaded onto the taxiway before the aircraft could be towed.
A replacement Boeing 767-300 freighter carried the cargo to Miami, arriving approximately 11 hours later. Colombia’s DIACC has initiated an investigation into the incident, citing a potential technical discrepancy as the cause of the rejected takeoff. The occurrence aircraft remains grounded in Bogota.
Aircraft Information
• Type: Boeing 767-300 Freighter
• Engines: General Electric CF6
• Registration: HP-3310DAE
The Boeing 767-300 freighter is a workhorse for medium- to long-haul cargo operations. Equipped with robust systems and redundancy, the aircraft is designed to handle high operational demands, including rejected takeoffs at high speeds.
Sequence of Events
1. Takeoff Roll:
• The aircraft commenced its takeoff roll on runway 14R at El Dorado International Airport.
2. Rejected Takeoff:
• At approximately 160 knots ground speed, the crew initiated a high-speed rejected takeoff due to an unspecified technical issue.
3. Runway Exit and Immobilisation:
• The aircraft vacated the runway safely but became disabled on the taxiway due to the deflation of multiple tyres on both main landing gear assemblies.
4. Cargo Unloading and Replacement Aircraft:
• The cargo was unloaded on the taxiway to allow the aircraft to be towed.
• A replacement Boeing 767-300 freighter carried the cargo to Miami, arriving with an 11-hour delay.
Initial Findings
1. Technical Discrepancy:
• Preliminary information suggests a technical fault prompted the rejected takeoff, although the specific issue is under investigation.
2. Tyre Deflation:
• The high-speed stop likely caused excessive heat buildup in the brakes, resulting in tyre deflation.
3. Crew Actions:
• The flight crew performed a standard rejected takeoff procedure, prioritising safety and minimising risks during the high-speed stop.
Safety Risks
1. Brake and Tyre Stress:
• High-speed rejected takeoffs place significant stress on landing gear components, potentially leading to tyre deflations or brake fires.
2. Runway Incursions:
• Disabled aircraft on taxiways can disrupt airport operations and create congestion.
3. Operational Disruption:
• The incident caused a delay in cargo delivery and required a replacement aircraft, affecting DHL’s logistics chain.
Recommendations
1. Brake and Tyre Maintenance:
• Conduct a detailed inspection of the brake assemblies and tyres to identify potential wear or malfunction.
2. Technical Investigation:
• Investigate the technical issue that prompted the rejected takeoff to determine if it was isolated or indicative of a systemic problem.
3. Rejected Takeoff Training:
• Reinforce crew training for high-speed rejected takeoffs to ensure prompt and effective responses to technical issues.
4. Operational Coordination:
• Review cargo unloading and aircraft recovery procedures to minimise delays during similar occurrences.
Safety Lessons
This incident underscores the importance of rigorous maintenance and effective crew training in managing high-speed rejected takeoffs. Quick decision-making by the flight crew ensured a safe outcome, while the subsequent recovery operation highlights the logistical challenges associated with such events.
Disclaimer
If you are the rightful owner of the photo and wish it to be taken down, please email takedown@cockpitking.com.
Our investigation reports are based on all the evidence and facts available at the time of writing and posting. We apologise if any details are missed or are not fully accurate.
