ATA MD83 at Isfahan on Jan 21st 2018, runway incursion
Last Update: February 14, 2019 / 18:24:32 GMT/Zulu time
Incident Facts
Date of incident
Jan 21, 2018
Classification
Incident
Cause
Runway incursion
Flight number
TBZ-5704
Departure
Mashad, Iran
Destination
Isfahan, Iran
Aircraft Registration
UR-CQC
Aircraft Type
McDonnell Douglas MD-83
ICAO Type Designator
MD83
Airport ICAO Code
OIFM
An Iran Air Avions de Transport Regional ATR-72-212A registration EP-ITH performing flight IR-3366 from Ahwaz to Isfahan, was just touching down on Isfahan's runway 26L when the MD-83 entered the runway.
Iran's AIB rated the occurrence a serious incident and opened an investigation, later adding to The Aviation Herald the aircraft actually vacated the runway via taxiway J.
Iran's AIB released their final report (Editorial note: thanks a lot for the English version!) concluding the probable causes of the serious incident were:
- RWY incursion was occurred by MD-83 with the call sign of TBZ5704 probably by the Pilot Failure to hold short RWY 26L before receiving clearance. It is important to note that entering to and back track on RWY needs additional clearance from TWR controller and shall be read back by pilot, otherwise pilot must stop before all RWY holding position markings until receiving further clearance to continue.
- Regarding presence of A/C on the RWY26L, the Controller failed to cancel landing clearance to ATR72 and issue go-around clearance. It is important to re-consider that the type, position and altitude of arrival aircraft dose not release controller's responsibility to do his tasks.
The AIB reported UR-CQC had landed on runway 26R and was instructed to vacate via taxiway D, however, requested to vacate via taxiway K. The aircraft vacated via K, joined J but did not stop short of runway 26L (editorial note: in the text the AIB clearly writes the aircraft entered 26L via J, however, in the aircraft track map, see below, showed the aircraft vacated via K, touched J and immediately turned onto H entering runway 26L via taxiway H). About 5 minutes after landing the aircraft entered runway 26L and reported they were backtracking the runway, tower in response instructed the aircraft to hold short of 26L. Tower subsequently informed the arriving ATR about the position of the MD-83 at the end of runway backtracking the runway. Without receiving any instruction to go around the ATR crew continued for landing on runway 26L and vacated via taxiway A about 1600 meters/5250 feet down the runway.
The AIB analysed:
The copilot was pilot flying while landing on RWY 26R but due to asymmetric thrust reverse of engines, the pilot took the roll and declared that we are unable to take TWY D at 10:18:45 UTC and the controller replied that to vacate RWY via TWY J without impressing on “Hold short before RWY 26L”.
At 10:19:52UTC the controller requested pilot to confirm vacation of RWY26R and then pilot requested to take TWY J or K and after receiving clearance from TWR controller replied that "we will take TWY K and vacate RWY in 10 sec. in this time, the pilot forgot the previous clearance to hold short before RWY 26L.
Following above communication arrival traffic IRA3366 reported her position and received landing clearance to RWY26L also at 10:23UTC another Local traffic landed on RWY26R.
According to statement of TBZ5704 pilot in command, during turning to the left before back track on RWY26L, and also according to the procedures he has checked right and left of path and realized that there is one visible aircraft on the final of RWY26L , after that he reduced taxi speed and asked co-pilot to confirm back track RWY26L.
The pilot incorrect perception of controller's clearance to vacate RWY26R via TXY J in two times due to another arriving aircraft (local flight) caused to realize a clearance to back track RWY26L. Evidence shows that clearance for back track RWY26L was not issued by the controller.
In spite of RWY incursion, the decision of air traffic controller for landing on occupied RWY are against the standard procedures in this manner.
The Go around procedure should be followed by the tower controller.
Metars:
OIFM 211200Z 08006KT CAVOK 08/M02 Q1019 A3012=
OIFM 211100Z 06008KT CAVOK 08/M03 Q1020 A3012=
OIFM 211030Z 00000KT CAVOK 08/M05 Q1020 A3013=
OIFM 211000Z 29010KT CAVOK 07/M04 Q1020 A3014=
OIFM 210930Z 33004KT CAVOK 07/M04 Q1021 A3015=
OIFM 210900Z 26014KT CAVOK 06/M04 Q1021 A3017=
OIFM 210830Z 29010KT CAVOK 05/M03 Q1022 A3018=
OIFM 210800Z 29010KT 7000 NSC 03/M04 Q1022 A3020=
Incident Facts
Date of incident
Jan 21, 2018
Classification
Incident
Cause
Runway incursion
Flight number
TBZ-5704
Departure
Mashad, Iran
Destination
Isfahan, Iran
Aircraft Registration
UR-CQC
Aircraft Type
McDonnell Douglas MD-83
ICAO Type Designator
MD83
Airport ICAO Code
OIFM
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
Ata MD83 at Tehran on May 8th 2017, runway incursion forces departing F100 to climb over the MD83
An Ata Airlines McDonnell Douglas MD-83, registration UR-CQC performing flight I3-5206 from Tehran Mehrabad to Tabriz (Iran), was preparing for…
Newest articles
Fleet type match
ANA B738 at Yonago on Apr 7th 2024, GPWS saves the day
An ANA All Nippon Airways Boeing 737-800, registration JA69AN performing flight NH-389 from Tokyo Haneda to Yonago (Japan), was on a circling…
Fleet type match
ANA B788 at Sapporo on Apr 24th 2024, hydraulic leak after landing
An ANA All Nippon Airways Boeing 787-8, registration JA804A performing flight NH-71 from Tokyo Haneda to Sapporo Chitose (Japan) with 213 people on…
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