 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
At a foreign airport the flight crew of a military C130 taxied into position on the runway and held contrary to the actual tower instructions of 'cleared on following the landing traffic.' this caused the tower to send around a B727 on final.
| Attributes | |
| ACN | 385335 |
| Time | |
| Date | 199711 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : sked |
| State Reference | FO |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : dtw |
| Operator | other |
| Make Model Name | Hercules (C-130) |
| Operating Under FAR Part | other : other |
| Flight Phase | ground : holding |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | B727 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | descent : approach landing : go around |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : military |
| Function | flight crew : single pilot |
| Qualification | pilot : military pilot : instrument pilot : atp pilot : commercial pilot : flight engineer |
| Experience | flight time last 90 days : 60 flight time total : 4700 flight time type : 820 |
| ASRS Report | 385335 |
| Person 2 | |
| Affiliation | government : military |
| Function | flight crew : first officer |
| Qualification | pilot : commercial pilot : instrument pilot : military |
| Experience | flight time last 90 days : 40 flight time total : 1400 flight time type : 700 |
| ASRS Report | 385331 |
| Events | |
| Anomaly | incursion : runway non adherence : clearance other anomaly other |
| Independent Detector | other controllera |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Problem arose due to a misunderstood 'conditional clearance' resulting in a runway conflict between us and a landing B727. The clearance as we perceived was 'cleared onto the runway to wait following air carrier X' (air carrier X being the air carrier that was beginning its takeoff roll). Traffic on a 5-8 mi final was observed but the thought was that we would receive an immediate takeoff and we read back the clearance as we heard it. Upon seeing the aircraft in front commence his departure turn, tower was queried for takeoff clearance. At that time he informed us that we were 'cleared on following the landing traffic.' we asked to clear the runway, which he denied and sent the B727 around. Contributing factors: language problems coupled with problematic VHF radio. Not only do the controllers at el dorado international speak english with an accent very hard to understand, but we also had a degraded VHF on our military C130E (only equipped with one) and there was no UHF capability at el dorado. We are not accustomed to the ICAO conditional clearance and had not given forethought to the hazards involved. Had any of the contributing factors been eliminated this occurrence would likely not have occurred. It is very hard to eliminate the language barrier. I will continue to push for a second VHF radio in our units C130 (with new vigor and with added justification). The conditional clearance has been idented as a problem in the past (as I understand). Let this be my vote against such a clearance. I see very little time saved versus the hazard involved. Although in the VMC conditions we had eliminated much of the safety hazard, it may have contributed to its use and resulted in a hazard and a go around for the landing traffic.
Original NASA ASRS Text
Title: AT A FOREIGN ARPT THE FLC OF A MIL C130 TAXIED INTO POS ON THE RWY AND HELD CONTRARY TO THE ACTUAL TWR INSTRUCTIONS OF 'CLRED ON FOLLOWING THE LNDG TFC.' THIS CAUSED THE TWR TO SEND AROUND A B727 ON FINAL.
Narrative: PROB AROSE DUE TO A MISUNDERSTOOD 'CONDITIONAL CLRNC' RESULTING IN A RWY CONFLICT BTWN US AND A LNDG B727. THE CLRNC AS WE PERCEIVED WAS 'CLRED ONTO THE RWY TO WAIT FOLLOWING ACR X' (ACR X BEING THE ACR THAT WAS BEGINNING ITS TKOF ROLL). TFC ON A 5-8 MI FINAL WAS OBSERVED BUT THE THOUGHT WAS THAT WE WOULD RECEIVE AN IMMEDIATE TKOF AND WE READ BACK THE CLRNC AS WE HEARD IT. UPON SEEING THE ACFT IN FRONT COMMENCE HIS DEP TURN, TWR WAS QUERIED FOR TKOF CLRNC. AT THAT TIME HE INFORMED US THAT WE WERE 'CLRED ON FOLLOWING THE LNDG TFC.' WE ASKED TO CLR THE RWY, WHICH HE DENIED AND SENT THE B727 AROUND. CONTRIBUTING FACTORS: LANGUAGE PROBS COUPLED WITH PROBLEMATIC VHF RADIO. NOT ONLY DO THE CTLRS AT EL DORADO INTL SPEAK ENGLISH WITH AN ACCENT VERY HARD TO UNDERSTAND, BUT WE ALSO HAD A DEGRADED VHF ON OUR MIL C130E (ONLY EQUIPPED WITH ONE) AND THERE WAS NO UHF CAPABILITY AT EL DORADO. WE ARE NOT ACCUSTOMED TO THE ICAO CONDITIONAL CLRNC AND HAD NOT GIVEN FORETHOUGHT TO THE HAZARDS INVOLVED. HAD ANY OF THE CONTRIBUTING FACTORS BEEN ELIMINATED THIS OCCURRENCE WOULD LIKELY NOT HAVE OCCURRED. IT IS VERY HARD TO ELIMINATE THE LANGUAGE BARRIER. I WILL CONTINUE TO PUSH FOR A SECOND VHF RADIO IN OUR UNITS C130 (WITH NEW VIGOR AND WITH ADDED JUSTIFICATION). THE CONDITIONAL CLRNC HAS BEEN IDENTED AS A PROB IN THE PAST (AS I UNDERSTAND). LET THIS BE MY VOTE AGAINST SUCH A CLRNC. I SEE VERY LITTLE TIME SAVED VERSUS THE HAZARD INVOLVED. ALTHOUGH IN THE VMC CONDITIONS WE HAD ELIMINATED MUCH OF THE SAFETY HAZARD, IT MAY HAVE CONTRIBUTED TO ITS USE AND RESULTED IN A HAZARD AND A GAR FOR THE LNDG TFC.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.