Flight crew fails to clarify all of taxi clearance at foreign facility. Runway transgression.

Attributes
ACN	158120
Time
Date	199009
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : osa
State Reference	FO
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 4 Turbojet Eng
Flight Phase	ground other : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 220 flight time total : 19500 flight time type : 550
ASRS Report	158120
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance other anomaly other
Independent Detector	other controllera other flight crewa
Resolutory Action	controller : issued new clearance other
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

During taxiout at osa we were cleared to runway 32L and some other clearance we were unable to understand. We read back cleared to runway 32L and controller said 'roger, contact tower, good night.' as we began to taxi we observed a twin engine turbo propeller that appeared to be on approach to runway 32L. As there was a crosswind and he slightly overshot, it soon become evident that he was lining up with 32R. At this tie he retracted the landing gear and made a go around. We had crossed or began to cross runway 32R approach end. Ground control then called us and told us to contact tower. He said he had told us to contact tower before. Due to cockpit duties and distrs, I did not contact tower immediately when requested. We understood we were cleared to 32L and read back that clearance. Ground control and clearance frequencys are very difficult to understand at osa. There is a very loud background noise in their xmissions. I have flown in here previously and the problem is always there. Tower and approach and departure xmissions are much better. Had I switched to tower sooner this may have been prevented. Also lack of standard ground control instruction can lead to problems such as this.

Original NASA ASRS Text

Title: FLT CREW FAILS TO CLARIFY ALL OF TAXI CLRNC AT FOREIGN FAC. RWY TRANSGRESSION.

Narrative: DURING TAXIOUT AT OSA WE WERE CLRED TO RWY 32L AND SOME OTHER CLRNC WE WERE UNABLE TO UNDERSTAND. WE READ BACK CLRED TO RWY 32L AND CTLR SAID 'ROGER, CONTACT TWR, GOOD NIGHT.' AS WE BEGAN TO TAXI WE OBSERVED A TWIN ENG TURBO PROP THAT APPEARED TO BE ON APCH TO RWY 32L. AS THERE WAS A XWIND AND HE SLIGHTLY OVERSHOT, IT SOON BECOME EVIDENT THAT HE WAS LINING UP WITH 32R. AT THIS TIE HE RETRACTED THE LNDG GEAR AND MADE A GAR. WE HAD CROSSED OR BEGAN TO CROSS RWY 32R APCH END. GND CTL THEN CALLED US AND TOLD US TO CONTACT TWR. HE SAID HE HAD TOLD US TO CONTACT TWR BEFORE. DUE TO COCKPIT DUTIES AND DISTRS, I DID NOT CONTACT TWR IMMEDIATELY WHEN REQUESTED. WE UNDERSTOOD WE WERE CLRED TO 32L AND READ BACK THAT CLRNC. GND CTL AND CLRNC FREQS ARE VERY DIFFICULT TO UNDERSTAND AT OSA. THERE IS A VERY LOUD BACKGROUND NOISE IN THEIR XMISSIONS. I HAVE FLOWN IN HERE PREVIOUSLY AND THE PROB IS ALWAYS THERE. TWR AND APCH AND DEP XMISSIONS ARE MUCH BETTER. HAD I SWITCHED TO TWR SOONER THIS MAY HAVE BEEN PREVENTED. ALSO LACK OF STANDARD GND CTL INSTRUCTION CAN LEAD TO PROBS SUCH AS THIS.

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.