Zagros MD83 at Queshm on Dec 30th 2023, approached wrong airport
Last Update: April 15, 2024 / 17:31:30 GMT/Zulu time
Incident Facts
Date of incident
Dec 30, 2023
Classification
Report
Airline
Zagros Airlines
Flight number
ZO-4035
Departure
Tehran Mehrabad, Iran
Destination
Queshm, Iran
Aircraft Registration
EP-ZAQ
Aircraft Type
McDonnell Douglas MD-83
ICAO Type Designator
MD83
Iran's CAA released their final report concluding the probable causes of the incident were:
1) Lack of the knowledge of the pilots about existence strip in Qeshm Island,
2) Some pilots of the airline were aware about the strip but no operational warning was issued.
3) Choosing wrong intercepting heading to perform NDB plan turning to the final of RWY05,
4) Failure to use FMS facilities after leaving IAF position,
5) Fluctuation of ADF needle in RMI of the aircraft due to error in NDB aids to navigation in the shore line,
6) Inaccuracy and insufficient supervision of the pilots over the flight instrument,
7) Failure to comply with the standard procedures in accordance with OM-A/OM-B/FCOM (failure to use the automation system), and
8) Lack of CRM and proper communication between the pilot in command and the copilot in accordance with OM-A and OM-B regulations and failure using the Standard Callout, mentioned in the company’s regulations on “disagreement between pilot in command and copilot on recognizing the correct RWY”.
The final report described the sequence of events:
At 08:57 UTC, IZG 4035 in contact with Bandar Abbas Approach (APP) section reported turning final to Qeshm RWY and APP delivered flight to Qeshm Airport Flight information officer (AFISO) on Freq; 118.05.
At 8:58 UTC, pilot contacted with Qeshm AFISO and reported final position for RWY 05. AFISO asked “confirm you have runway insight” that pilot reported “not yet”. After some seconds the pilot reported “RWY insight” and received clearance for landing on RWY 05.
At 08:59 UTC, BND approach controller asked Qeshm AFISO about sawing the flight and AFISO told she reported RWY insight. The controller warned that the flight is going to south the airport and may planned to land on local strip. So, AFISO called the flight and pilot replied” Going around”. BND controller confirmed AFISO about its climbing and joining left downwind.
At the moment, the captain made error and considered a local strip, which was 5 miles away from the main RWY of Qeshm airport, as the intended RWY of Qeshm Airport for landing. Being advised by the first officer that the main RWY might be at the left side, the captain banked to left on heading 34 degree but since he could not see the main RWY of Qeshm airport, he made a banking to the right again to align for the final of the wrong strip. Then, he disconnected the auto pilot and continued to descend, while all the operations were being implemented without any advice to the first officer on DFGC change.
The pilot banked to the left and right for several times to align but finally, due to being un-stabilized, decided to go-around and climbed to 2000 feet above MSL while the landing gears were still extended. Afterwards, the captain asked for left downwind to land on the wrong strip, but by banking to the left, the pilots saw the main RWY of Qeshm airport. Since they were at the right hand downwind of the main RWY, they followed up the visual approach plan and finally landed on the main RWY of Qeshm airport at 09:06 UTC.
The report analysed:
The captain was pilot flying and copilot (PM) was pilot non flying. After passing overhead of Qeshm airport , the captain descended to FL160 with an approximate speed of 220 kts, then he extended landing gears and banked to the right for joining the final RWY 05 on heading 60 deg.
The flight in contact with Bandar Abbas Approach (APP) section reported turning final to Qeshm RWY and APP delivered flight to Qeshm Airport Flight information officer (AFISO). Then the pilot saw a strip and due to good vision on strip thought that the strip is intended RWY so, ignored to follow IFR principles and continue to land on strip with visual references to compensate flight delay. The copilot mentioned that in this time, I reported to the captain that this cannot be Qeshm RWY but the captain did not pay attention to his message. Due to short arc for joining strip final, aircraft had un-stabilized approach to a local strip then EGPWS warning “Terrain, Terrain” was generated on 700 feet from field elevation. EGPWS warning was generated due to operating at airport or runway not in the FMS database.
The captain referred to OM part A, and made go-around;
“An approach that becomes un-stabilized below 1,000 feet above airport elevation in below IMC or 500 feet in VMC requires an immediate go-around. Any time an approach is not stabilized at the minimum stabilized height or becomes un-stabilized below the minimum stabilized height, a go-around should be conducted “
At 08:59 UTC, BND approach controller that was seeing the flight on radar (AMD), asked Qeshm AFISO about the flight and AFISO told: pilot reported RWY insight. The controller warned that the flight is going to south the airport and may planned to land in local strip. So, AFISO called the flight and pilot replied” Going around”. BND controller confirmed AFISO about its climbing and joining left downwind. This communication was made after go-around of the flight.
The pilot made go-around and climbed to 2000 feet above MSL while the landing gears were still extended. Afterwards, the captain asked to join left downwind to attempt again for landing on the wrong strip, but due banking to the left, the copilot saw the main RWY of Qeshm airport and informed the captain. Since they were at the right hand downwind of the main RWY, they followed up the visual approach and finally landed on the main RWY of Qeshm airport at 09:06 UTC.
Incident Facts
Date of incident
Dec 30, 2023
Classification
Report
Airline
Zagros Airlines
Flight number
ZO-4035
Departure
Tehran Mehrabad, Iran
Destination
Queshm, Iran
Aircraft Registration
EP-ZAQ
Aircraft Type
McDonnell Douglas MD-83
ICAO Type Designator
MD83
This article is published under license from Avherald.com. © of text by Avherald.com.
Article source
You can read 2 more free articles without a subscription.
Subscribe now and continue reading without any limits!
Read unlimited articles and receive our daily update briefing. Gain better insights into what is happening in commercial aviation safety.
Send tip
Support AeroInside by sending a small tip amount.
Related articles
Zagros A320 near Isfahan on Dec 7th 2022, loss of cabin pressure
A Zagros Airlines Airbus A320-200, registration EP-ZAV performing flight ZO-4005 from Kish to Isfahan (Iran), was enroute at FL340 about 150nm south…
Zagros A320 at Tehran on Jan 10th 2021, EGPWS alert on ILS intercept
A Zagros Airlines Airbus A320-200, registration EP-ZAV performing flight ZO-4012 from Ahwaz to Tehran Mehrabad (Iran), was on approach to Tehran…
Zagros A320 at Ahwaz on Jun 8th 2018, engine shut down in flight
A Zagros Airlines Airbus A320-200, registration EP-ZAV performing flight ZI-4112 from Ahwaz to Mashad (Iran), was in the initial climb out of Ahwaz's…
Zagros MD83 at Tehran on Oct 19th 2017, burst tyre on departure
A Zagros Airlines McDonnell Douglas MD-83, registration EP-ZAK performing flight ZO-4013 from Tehran Mehrabad to Ahwaz (Iran), burst the left…
Zagros MD82 at Mashad on Oct 14th 2017, engine shut down in flight
A Zagros Airlines McDonnell Douglas MD-82 on behalf of Taban Airlines, registration EP-ZAC performing flight HH-6325 from Mashad to Tehran Mehrabad…
Newest articles
RAM B738 at Tunis on Apr 26th 2024, bird strike
A RAM Royal Air Maroc Boeing 737-800, registration CN-RGG performing flight AT-573 from Tunis (Tunisia) to Casablanca (Morocco), was climbing out of…
Finnair A333 over Canada on Apr 28th 2024, engine shut down in flight
A Finnair Airbus A330-300, registration OH-LTM performing flight AY-10 (dep Apr 27th) from Chicago O'Hare,IL (USA) to Helsinki (Finland) with 194…
Subscribe today
Are you researching aviation incidents? Get access to AeroInside Insights, unlimited read access and receive the daily newsletter.
Pick your plan and subscribePartner
A new way to document and demonstrate airworthiness compliance and aircraft value. Find out more.
ELITE Simulation Solutions is a leading global provider of Flight Simulation Training Devices, IFR training software as well as flight controls and related services. Find out more.
Your regulation partner, specialists in aviation safety and compliance; providing training, auditing, and consultancy services. Find out more.
AeroInside Blog
Popular aircraft
Airbus A320Boeing 737-800
Boeing 737-800 MAX
Popular airlines
American AirlinesUnited
Delta
Air Canada
Lufthansa
British Airways