Flight RO-384 | Registration: YR-BGG
Date: 2 April 2025 | Location: Paris Charles de Gaulle Airport (LFPG), France
⸻
Introduction
On 2 April 2025, a TAROM Boeing 737-700, registration YR-BGG, operating scheduled passenger service RO-384 from Paris Charles de Gaulle Airport (CDG) to Bucharest Otopeni Airport (OTP), initiated a high-speed rejected takeoff on runway 08R. The aircraft decelerated safely and exited the runway via a high-speed taxiway after covering approximately 2,500 metres (8,300 feet).
The flight was aborted due to a suspected technical malfunction. As a consequence of the rejected takeoff, two main landing gear tyres deflated. No injuries were reported, and all occupants remained safe. The cause of the rejected takeoff remains under investigation by TAROM and French aviation authorities.
⸻
Flight Details
• Aircraft Type: Boeing 737-78J
• Engines: 2 × CFM56-7B24
• Operator: TAROM
• Tail Number: YR-BGG
• Flight Number: RO-384
• Departure Airport: Paris Charles de Gaulle (LFPG), France
• Destination Airport: Bucharest Otopeni (LROP), Romania
• Date of Incident: 2 April 2025
• Phase of Flight: Takeoff Roll (High-Speed)
• Occupants: Estimated 130 (passengers and crew combined)
• Weather Conditions: Visual Meteorological Conditions (VMC)
• Runway Used: 08R
⸻
Sequence of Events
Takeoff Roll and Rejection
At approximately 08:45 local time, RO-384 commenced its takeoff roll on runway 08R at CDG under normal operational conditions. As the aircraft accelerated past 80 knots, and approaching high-speed regime (near V1), the flight crew identified a technical anomaly—suspected to be related to engine or system indication—and elected to reject the takeoff.
The aircraft decelerated safely and exited the runway via a high-speed taxiway roughly 2,500 metres into the takeoff roll. The crew brought the aircraft to a controlled stop and requested assistance from ground services.
Post-Abort Findings
Upon inspection by airport ground personnel and maintenance crews, it was determined that two tyres had deflated due to the high-speed rejected takeoff. No fire or smoke was reported, and no injuries were sustained.
⸻
Initial Operator Statement and Investigation
TAROM released a statement confirming the rejected takeoff was due to a technical issue that prompted the captain’s decision. The airline emphasised that the crew acted in full compliance with safety protocols and that the decision to abort was made out of an abundance of caution.
The nature of the technical issue remains under investigation. Possibilities include an erroneous engine or system alert, brake or anti-skid issues, or unstable acceleration performance. The aircraft remains grounded at Paris CDG pending full technical evaluation and tyre replacement.
⸻
Aircraft Status and Operational Impact
• Aircraft Status: Grounded at Paris Charles de Gaulle for post-incident inspection.
• Return to Service: Pending maintenance and investigation findings.
• Flight Disruption: RO-384 was cancelled. Passengers were rebooked on alternative TAROM and partner flights to Bucharest.
• Tyre Damage: Two main gear tyres deflated during the high-energy stop; replacement parts ordered.
⸻
Technical Considerations
Rejected takeoffs above 100 knots impose significant thermal and structural loads on tyres, brakes, and associated systems. Boeing 737 tyres are certified to handle one rejected takeoff at maximum weight without structural failure, but heat buildup can cause pressure release via fusible plugs—likely what occurred here.
The decision to abort a takeoff at high speed (particularly near or above V1) is a serious one and typically occurs only when continuing the takeoff poses more risk than stopping on the available runway length. The captain’s judgment and adherence to SOPs are now central to the ongoing review.
⸻
Conclusion and Safety Considerations
This event underscores the importance of real-time flight crew decision-making during takeoff—a phase known for limited reaction time. The TAROM crew’s actions resulted in a safe stop with no harm to passengers or crew. Investigators will now focus on identifying the root cause of the technical issue that prompted the abort, and assess whether additional training, procedural revisions, or system upgrades are necessary.
A full report will be issued by French BEA or TAROM’s internal safety team depending on the classification of the occurrence.
⸻
Disclaimer
This article is based on publicly available information and official airline statements as of 3 April 2025. Details may evolve as the investigation progresses. If you are the rightful owner of any referenced content and wish it to be removed, please contact takedown@cockpitking.com.
