Sunday, April 20, 2025
HomeAircraft IncidentsEVA Air Boeing 777-300 – Nose Gear Malfunction After Departure from Bangkok

EVA Air Boeing 777-300 – Nose Gear Malfunction After Departure from Bangkok

Flight BR-67 | Registration: B-16738

Date: 5 April 2025 | Location: Bangkok Suvarnabhumi Airport (VTBS), Thailand

Flight Details

• Aircraft Type: Boeing 777-300

• Engines: 2 × General Electric GE90-115B

• Operator: EVA Air

• Registration: B-16738

• Flight Number: BR-67

• Callsign: EVA67

• Route: Bangkok (VTBS), Thailand to London Heathrow (EGLL), United Kingdom

• Date of Incident: 5 April 2025

• Total Occupants: 336 (319 passengers, 17 crew)

• Weather Conditions: Reported clear skies, dry runway, light winds

Introduction

On 5 April 2025, an EVA Air Boeing 777-300 operating flight BR-67 from Bangkok to London Heathrow returned to Bangkok Suvarnabhumi Airport following a nose landing gear malfunction shortly after take-off. The aircraft, registered B-16738, had climbed to 10,000 feet before the crew reported a technical issue with the nose gear. The flight entered a holding pattern to troubleshoot and burn fuel before making a safe landing on the departure runway approximately 90 minutes after take-off. The aircraft remained grounded in Bangkok for more than 28 hours following the incident.

Sequence of Events

Flight BR-67 departed Bangkok’s runway 20L during the early morning hours with a full international load bound for London. Climb-out appeared routine until the aircraft reached 10,000 feet, at which point the crew informed Bangkok Departure of a technical issue concerning the nose landing gear.

The aircraft was instructed to enter a holding pattern south of the airport while the crew completed troubleshooting checklists. During this time, fuel burn was increased to reduce landing weight in preparation for a return to Bangkok.

No emergency declaration was made, and no abnormal aircraft performance was reported in cruise or descent. The aircraft returned to runway 20L and landed without incident. Ground crews remained on standby, and the aircraft taxied under its own power back to the gate.

Following arrival, maintenance teams began inspecting the nose gear, and the aircraft was taken out of service pending further evaluation.

Crew & Communication

The EVA Air crew detected the issue during initial climb, likely through ECAM or cockpit indicator flags related to nose gear status. Communication with Bangkok ATC was professional and measured. A holding pattern was requested rather than an immediate return, suggesting the issue was not deemed time-critical.

Flight deck recordings (CVR) and Flight Data Recorder (FDR) will provide insight into system alerts, fault warnings, and crew discussions surrounding the nature of the problem.

ATC logs show that while the aircraft remained in the vicinity of the airport, standard separation was maintained, and no priority emergency traffic was initiated.

Aircraft Systems & Technical Analysis

The Boeing 777-300 features an electrically and hydraulically actuated nose gear assembly, managed via the Landing Gear Control and Interface Unit (LGCIU). Gear status is monitored through position sensors and feedback loops that confirm gear extension, retraction, and door status.

In-flight faults with the nose gear system can stem from:

• Sensor discrepancies (gear not fully retracted or locked)

• Hydraulic actuator malfunction

• Door sequencing errors

• LGCIU failure or miscommunication

• Nose gear uplock failure

In this case, the gear was likely either stuck in a transitional state or unable to confirm full retraction or lock status. There was no indication of gear freefall, asymmetry, or loss of hydraulic pressure during the flight.

Upon return, maintenance teams would have conducted:

• Hydraulic system pressure checks

• Nose gear actuator inspections

• Gear bay sensor verification

• LGCIU diagnostic readout

• BITE (Built-In Test Equipment) analysis

Given the prolonged grounding period of over 28 hours, component replacement or deeper troubleshooting is likely ongoing.

Passenger Experience & Cabin Conditions

Passengers were not immediately informed of the nature of the issue, though the holding pattern and return to Bangkok indicated a deviation from the planned route. According to unconfirmed passenger accounts, the captain later announced a minor technical fault and reassured passengers of a precautionary return.

There were no onboard disturbances, turbulence, or abnormal cabin conditions. Cabin crew remained active throughout, providing updates and resuming services while in the hold.

Upon landing, passengers disembarked normally. EVA Air coordinated rebooking and accommodations as needed due to the overnight grounding and delayed onward travel.

Emergency Response & Aftermath

Airport fire and rescue services were placed on standby for the return landing, but no intervention was required. Runway 20L was cleared promptly following the aircraft’s arrival, and there was no disruption to wider airport operations.

The aircraft was assigned to a maintenance stand, and a detailed inspection was initiated by EVA Air’s engineering division in coordination with Boeing technical support.

Flight BR-67 was cancelled for the day, and passengers were reaccommodated via alternative routings or rebooked on later departures.

Investigation Status

The Civil Aviation Authority of Thailand (CAAT) has been notified of the incident. While the event has not been classified as a serious incident under ICAO Annex 13 definitions, it remains subject to internal investigation by EVA Air and Boeing’s after-sales engineering support.

Digital flight data will be examined to verify gear position indications, LGCIU messages, and hydraulic performance during gear cycles. A report may be issued if any systemic or fleet-wide risk is identified.

Root Cause & Contributing Factors

The likely root cause of the incident lies in one of the following:

• False gear position indication due to sensor failure

• Incomplete nose gear retraction due to hydraulic actuator or uplock issue

• Data miscommunication between the LGCIU and cockpit systems

• Faulty nose gear door sequencing or mechanical interference

No evidence has emerged of flight crew error or procedural deviation.

The contributing factor may include age-related wear on gear components, foreign object obstruction in the gear bay, or software-related data mismatch. Final findings will depend on maintenance and diagnostic outcomes.

Safety Recommendations & Industry Impact

While the incident did not result in injury or damage, it highlights the operational importance of:

• Redundant gear position verification

• Timely fault reporting and conservative decision-making

• Preventive maintenance for sensor alignment and LGCIU reliability

Boeing may consider updating software thresholds for gear status alerts, and EVA Air is likely to enhance technician training on nose gear fault tracing and fault reset protocols.

If further incidents emerge across the 777 fleet involving similar faults, a service bulletin or airworthiness directive could follow.

Conclusion

EVA Air’s decision to return flight BR-67 to Bangkok following a nose gear fault reflects sound operational judgement and a cautious safety culture. The Boeing 777’s redundant systems allowed safe flight, and the flight crew maintained control and composure throughout.

Though the mechanical issue did not escalate, the incident underscores the importance of gear system reliability, especially on long-haul widebody aircraft where early faults can significantly impact operational continuity and passenger itineraries.

Disclaimer

This article is based on publicly available information and reports at the time of writing. While every effort has been made to ensure accuracy, we cannot guarantee the completeness of the information provided.

If you are the rightful owner of any referenced content or images and wish them to be removed, please contact takedown@cockpitking.com.

RELATED ARTICLES

Most Popular