LEVEL 3 Final report

Based on the investigation authority's final report.

Date
Show source
Communication Failure: Gulf Air Boeing 787-9 A9C-FGOccurrence identification | Printed page Cover | PDF page 1Find this passage in evidence search
Occurrence
Serious incident
Location
United Arab Emirates airspace, approach to Dubai Airport
Show source
Communication Failure: Gulf Air Boeing 787-9 A9C-FGOccurrence identification | Printed page Cover | PDF page 1Find this passage in evidence search
Operator
Gulf Air
Show source
Communication Failure: Gulf Air Boeing 787-9 A9C-FGOccurrence identification | Printed page Cover | PDF page 1Find this passage in evidence search
Flight
GF504
Show source
Aircraft
Boeing 787-9
Show source
Communication Failure: Gulf Air Boeing 787-9 A9C-FGOccurrence identification | Printed page Cover | PDF page 1Find this passage in evidence search
Registration
A9C-FG
Show source
Communication Failure: Gulf Air Boeing 787-9 A9C-FGOccurrence identification | Printed page Cover | PDF page 1Find this passage in evidence search
Route
Bahrain International Airport to Dubai International Airport
Show source
People aboard
193: 183 passengers, two pilots and eight cabin crew
Show source
Fatalities
None reported; the aircraft landed safely
Show source
Survivors
193 aboard a safe landing
Show source
Investigating authority
UAE GCAA AAIS, AIFN/0004/2023
Show source
Topics
Communication failure, Tuning control panel malfunction, Bulletin access and briefing procedures

This photograph is cropped for the banner. See the full photograph, credit, licence and what it shows.

Photographs and geographic context

Gulf Air Boeing 787-9 A9C-FG in retro colours at Dhaka.

A9C-FG at Shahjalal International Airport in October 2022.

Photo: Md Shaifuzzaman Ayon, CC BY-SA 4.0

Image info

The incident aircraft, photographed on 8 October 2022, before the Dubai occurrence.

Image source

Responsive WebP copies resized without cropping. The original photograph is unchanged.

Geographic context

Geographical orientation for Gulf Air A9C-FG communication failureBahrain International Airport, departure; Dubai approach area, airport reference. GF504 flew from Bahrain to Dubai. The Dubai marker uses the airport coordinates supplied in the summary; the panel failures occurred in flight during descent. The Bahrain marker gives general airport location.12NORTH UP / SCHEMATIC / NOT A RECORDED FLIGHT TRACK
  1. Bahrain International Airport, departure
  2. Dubai approach area, airport reference
GF504 flew from Bahrain to Dubai. The Dubai marker uses the airport coordinates supplied in the summary; the panel failures occurred in flight during descent. The Bahrain marker gives general airport location. Basemap: Natural Earth, public domain.
Read supporting evidence

What happened

During descent, A9C-FG's three tuning control panels became inoperative and the crew could not change radio frequencies. The pilots searched their manuals, held while troubleshooting, declared a communication emergency and landed safely at Dubai.

Read the full incident Follow what happened, from the flight to the investigation findings.

What investigators concluded

The AAIS could not determine the technical reason for the panel malfunction. It found that the crew could not locate the applicable reset bulletin, and linked the failed recovery to the missed takeoff briefing check and unfamiliarity with the bulletin location.

Evidence behind this explanation

GF504 and the three inoperative tuning control panels

1,102 words / about 6 minutes to read. The official report for this event is short, so this account is shorter than most and covers only what the report documents.

Descent toward Dubai

Gulf Air flight GF504 left Bahrain for Dubai on 10 March 2023 with 193 people aboard its Boeing 787-9, A9C-FG. The occupants were 183 passengers, two pilots and eight cabin crew. The commander flew the aircraft and the copilot monitored the flight. The flight data recorder placed takeoff from runway 30R at 17:28:58 UTC. The aircraft climbed to flight level 250 before beginning its descent toward Dubai at about 17:54.

During the descent, the left, centre and right tuning control panels became inoperative. The crew received engine indicating and crew alerting system messages concerning the transponder, weather radar and traffic collision avoidance system. They could no longer change radio frequencies through the panels. The pilots began the quick reference handbook procedures while continuing their arrival into United Arab Emirates airspace.

The crew still had radio contact with Dubai Approach. The flight history describes communication on a standby frequency of 119.3 MHz, and the analysis records a report of the panel failure to the controller at 17:54:10. At 17:56:23, Dubai Approach cleared the aircraft toward VUTEB and authorised descent to 13,000 feet. The flight subsequently held while the crew worked on the problem and awaited further approach clearance.

Sources for this section

Searching for a reset procedure

The copilot searched the quick reference handbook and the electronic Flight Crew Operations Manual on the company iPad in the electronic flight bag. He was looking for a tuning control panel reset procedure or a flight crew operations bulletin covering the malfunction. He could not locate the relevant information. The two pilots did not discuss the applicable bulletin during their attempts to resolve the failures.

The commander described several unsuccessful attempts to reset and restore the panels. The investigation also found that the communication difficulties prevented the pilots from contacting the company Maintenance Control Center for assistance. The crew therefore continued troubleshooting with the manuals available in the cockpit and coordinated the arrival with Dubai air traffic control.

Dubai Approach asked the crew to declare a radio communication emergency so that landing clearance and standby emergency services could be arranged. At 18:22:15, the pilots made the emergency declaration and continued the descent for landing. Approach and Tower coordinated the aircraft altitude and landing clearance. The aircraft landed safely on runway 12L at 18:35:33, vacated at exit Mike 7 Alpha at 18:36:15, and taxied to stand Charlie 41. The fire commander cancelled the full emergency at 18:42.

The summary records no damage to the aircraft, property or environment. Maintenance personnel reset the panels and performed a ground test. The panels functioned, the alert messages cleared and the aircraft returned to service. The technical records had shown no deferred defects relevant to the occurrence before departure.

Sources for this section
Communication Failure: Gulf Air Boeing 787-9 A9C-FGDamage to Aircraft and Property | Printed page 2 | PDF page 4Find this passage in evidence search

The existing Boeing bulletin

Gulf Air already had a Boeing bulletin addressing inoperative tuning control panels, uncommanded VHF frequency transfers or changes, and uncommanded transponder code changes. Bulletin GUL-38 R1 was dated 28 December 2021 and remained in effect. It described previous events in which two or three panels became inoperative and displayed a system-unavailable message.

The bulletin explained that the affected functions continued operating with their previous selections, but that all three panels being inoperative prevented control until at least one panel was reset. Its list included VHF and HF radios, satellite communications, the cabin interphone, ground proximity warning, weather radar, TCAS and transponder, alternate navigation, and the alerting and transponder control panel.

For three inoperative panels, the published recovery procedure called for all three to be selected off and only the right panel to be selected on. The bulletin also required the crew to confirm the desired system selections after a reset, including radio frequency and transponder code. For one or two failed panels it described a different reset sequence, with a panel that failed again left off for the rest of the flight.

The copilot said he could not recall where to find the bulletin. The takeoff briefing guide required a review of the applicable bulletins and notices. Investigators concluded that reviewing the existing bulletin and following its reset procedure would have restored normal communication. They linked the unsuccessful recovery to the missed briefing check and difficulty locating the information in the electronic manual.

Sources for this section

Evidence and findings

The AAIS could not determine the technical reason for the malfunction of the three panels. Its findings established that both pilots were licensed, qualified, rested and fit for the flight, and that the aircraft was certificated, equipped and maintained to Bahrain requirements. The aircraft was airworthy when released for departure, with no deferred or reported defects identified as contributing to the occurrence.

The weather at Dubai included ten kilometres visibility and a wind from 310 degrees at seven knots at 18:00 UTC. Investigators excluded weather as a contributory factor. Their findings credited Dubai Approach and Tower with providing the information needed for the safe landing and recorded the activation and subsequent cancellation of the airport emergency response.

Flight data were downloaded in Bahrain and analysed at the Abu Dhabi Flight Recorder Laboratory. The incident cockpit voice recording was overwritten during the aircraft return to Bahrain because the recorder stored a maximum of two hours of cockpit audio.

The summary contains conflicting operational details. Its flight history and crew-performance analysis describe communication on 119.3 MHz, while its bulletin discussion identifies a previously selected 121.5 MHz frequency. The flight history describes the transponder as inoperative and radar monitoring unavailable; the bulletin discussion says ATC continued receiving transponder information and that IDENT failed. It also gives different times for the hold. These details remain unresolved in the published summary.

Sources for this section

Safety action and the completed investigation

Bahrain authorities informed the AAIS that Gulf Air had introduced safety measures. The bulletin became a green flag item during the type rating course, and a Flight Crew Operations Notice informed all pilots about new or revised bulletins. The letter also stated that bulletin review was outside the system knowledge validation during licence and operator proficiency checks.

The AAIS considered those measures adequate and issued recommendation SR14/2024 to Gulf Air. It called for better checking of flight crew operations bulletins and NOTAM supplements during the takeoff briefing, adherence to that briefing procedure, and use of the appropriate procedures during flight. The AAIS said its safety recommendation tracking system would assess the recommendation implementation and the effectiveness of the operator actions.

The GCAA published its completed investigation as a serious incident summary report on 13 March 2025, after stakeholder consultation. The investigation scope covered the events leading to the occurrence and excluded in-depth analysis of non-contributing factors. The publication contains findings, causes, safety actions and a recommendation. It provides no component examination results explaining the initiating malfunction, no cockpit voice transcript, no raw flight data tables and no detailed air traffic control transcript.

Sources for this section
Communication Failure: Gulf Air Boeing 787-9 A9C-FGSafety Actions and Safety Recommendations | Printed page 8 | PDF page 10Find this passage in evidence search

Return to the short summary / Source status and limitations

How the sequence developed

Follow the main stages, then open the evidence beneath each step.

  1. Control panels become inoperative

    The pilots lost control through all three tuning panels and could not change radio frequencies.

    Read supporting evidence
  2. Reset information remains inaccessible

    The copilot searched the electronic manuals but could not locate the applicable Boeing bulletin.

    Read supporting evidence
  3. Radio contact supports the arrival

    The crew held, coordinated with Dubai controllers and declared a radio communication emergency before landing safely.

    Read supporting evidence
  4. Maintenance restores panel function

    A ground reset restored all three panels and cleared the alert messages.

    Read supporting evidence

A simplified reading of the investigation findings. The sequence does not replace the full report or imply that every contributing factor is shown.

Sequence of events

All times are UTC. UAE local time was four hours ahead. Expand an event to see its evidence.

  1. 17:28:58 UTCDeparture from Bahrain

    GF504 took off from runway 30R with 193 people aboard.

  2. About 17:54 UTCThree panels become inoperative

    The crew reported tuning control panel failures and inability to change frequency during descent.

  3. 17:56:23 UTCClearance toward VUTEB

    Dubai Approach cleared the aircraft toward VUTEB and down to 13,000 feet. The crew subsequently held while troubleshooting.

  4. 18:22:15 UTCCommunication emergency declared

    The crew declared a radio communication emergency and continued the approach while Approach and Tower coordinated landing clearance.

  5. 18:35:33 UTCSafe landing

    A9C-FG landed on runway 12L, vacated at 18:36:15 and taxied to stand Charlie 41.

  6. 18:42 UTCEmergency response cancelled

    The fire commander cancelled the full emergency after the landing.

  7. After landingGround reset succeeds

    Maintenance reset all three panels, completed a ground test and returned the aircraft to service.

Search the report evidence

Search extracted report prose, with original page references. Short results link to the full document.

Questions readers ask

What reset procedure covered three failed panels?

Bulletin GUL-38 R1 directed the crew to select all three panels off and then select only the right panel on. System selections, including frequency and transponder code, were to be checked after a reset.

What caused the tuning control panels to malfunction?

The AAIS could not determine the technical reason for the three-panel malfunction. Maintenance restored panel function with a ground reset.

Was an incident cockpit voice recording available?

The incident recording was overwritten when the aircraft returned to Bahrain. The recorder had a maximum cockpit audio capacity of two hours. Flight data were downloaded and analysed.

What the evidence can and cannot establish

Conflicting frequency, surveillance and hold details

The flight history and crew-performance sections give 119.3 MHz; the bulletin discussion gives 121.5 MHz. The history describes transponder and radar monitoring loss, while the bulletin discussion reports continuing transponder reception and a failed IDENT switch. Holding times also differ between sections.

Read supporting evidence

Summary publication and recorder limits

The published document is a summary report. It contains no component examination results explaining the malfunction, cockpit voice transcript, raw flight data tables or detailed ATC transcript. The investigation excluded in-depth analysis of non-contributing factors. The incident cockpit audio had been overwritten during the return flight.

Read supporting evidence

Safety follow-up

Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.

Recommendation SR14/2024

The AAIS recommended better bulletin and NOTAM supplement checks during the takeoff briefing and adherence to the applicable procedures. It planned to track implementation and the effectiveness of the operator actions.

Read supporting evidence

Classifications, with reasons

These labels organise the evidence. They are not a ranking of causes. A shared label means a shared research topic, not an identical mechanism.

circumstanceCommunication failure

The panel malfunction prevented frequency changes and led the crew to declare a communication emergency.

circumstanceTuning control panel malfunction

All three tuning control panels became inoperative. The technical origin remained undetermined.

causeBulletin access and briefing procedures

The AAIS linked the failed recovery to the missed bulletin check and inability to locate the reset procedure in the electronic manual.

Read alongside

These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.

G-ONEE

Both flights involved several affected systems and crews working through abnormal procedures before a safe landing. In G-ONEE, the AAIB traced the electrical bus losses to water in generator control units. In A9C-FG, the AAIS left the initiating technical cause undetermined and identified difficulty locating the reset bulletin.

Read supporting evidence
AAIB final reportSynopsis | Printed page 1 | PDF page 1Find this passage in evidence search

Further investigation records

Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.

  • GCAA AIFN/0004/2023 summary report

    NTSB / investigation record

    The completed investigation summary, including flight history, findings, causes, safety actions and recommendation SR14/2024.

Sources and transparency

GCAA completed the investigation and issued its summary report on 13 March 2025.

Source limitations

The published document is a summary report. It contains no component examination results explaining the malfunction, cockpit voice transcript, raw flight data tables or detailed ATC transcript. The investigation excluded in-depth analysis of non-contributing factors.

Communication Failure: Gulf Air Boeing 787-9 A9C-FG

UAE GCAA Air Accident Investigation Sector
Final investigation summary report AIFN/0004/2023, issued 13 March 2025

Official report PDF, hosted by gcaa.gov.ae

Open source document

10 PDF pages.

GCAA report linked for investigation findings. Report illustrations are excluded from the photograph licence. Source terms.

Read the extraction, classification and review methodology.

Suggest a correction to this dossier

Editorial record

Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.

Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed

Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.

Revision history

: Published sourced incident account, timeline, photographs and investigation findings.

Source-based corrections are reviewed before changes appear here. Suggest a correction to this dossier.

Cite or link to this page

Quoting this account or linking to it? Please use the page address below, and credit the investigation report it is built from.

Credit line

AirlineIncidents.com. Gulf Air Flight GF504 accident account. Published 30 October 2026. https://airlineincidents.com/incidents/gulf-air-a9c-fg-2023/

HTML link

<a href="https://airlineincidents.com/incidents/gulf-air-a9c-fg-2023/">Gulf Air Flight GF504 accident account (AirlineIncidents.com)</a>

Select a box to copy it. Spotted something wrong? Send a correction.