Runway incursion by an exiting DC10 that failed to taxi far enough from the runway, creating a go around by arrival traffic on runway 9R at lfpg, first officer.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	543337
Time
Date	200204
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : lfpg.airport
State Reference	FO
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : apf.tower
Operator	common carrier : air carrier
Make Model Name	DC-10 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tower : lfpg.tower
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Flight Phase	ground : position and hold
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : instrument pilot : multi engine pilot : commercial
Experience	flight time last 90 days : 120 flight time total : 13400 flight time type : 1500
ASRS Report	543337
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	incursion : runway non adherence : required legal separation other anomaly other
Independent Detector	other controllera
Resolutory Action	controller : separated traffic controller : issued new clearance flight crew : executed go around
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	Airport Flight Crew Human Performance Company ATC Human Performance Chart Or Publication
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After we cleared runway 9R on taxiway Y10 and received taxi instructions and clarification at taxiway K5, we were informed we had caused an aircraft to go around. (After our landing an aircraft had been cleared into position.) we felt that we had taken taxiway Y10 in a safe and expeditious manner and that at the intersection of taxiway K5 we were clear. We are not sure if taxiing too slow, stopping at taxiway K5, or turning onto taxiway K5 caused the ground controller's statement. If turning on taxiway K5 was the cause, contributing factors would be: my first time to cdg; difficulty in understanding communications because of accent; fatigue from all night oceanic crossing. Our airline has had numerous bulletins regarding exiting the runway after landing.

Original NASA ASRS Text

Title: RWY INCURSION BY AN EXITING DC10 THAT FAILED TO TAXI FAR ENOUGH FROM THE RWY, CREATING A GAR BY ARR TFC ON RWY 9R AT LFPG, FO.

Narrative: AFTER WE CLRED RWY 9R ON TXWY Y10 AND RECEIVED TAXI INSTRUCTIONS AND CLARIFICATION AT TXWY K5, WE WERE INFORMED WE HAD CAUSED AN ACFT TO GO AROUND. (AFTER OUR LNDG AN ACFT HAD BEEN CLRED INTO POS.) WE FELT THAT WE HAD TAKEN TXWY Y10 IN A SAFE AND EXPEDITIOUS MANNER AND THAT AT THE INTXN OF TXWY K5 WE WERE CLR. WE ARE NOT SURE IF TAXIING TOO SLOW, STOPPING AT TXWY K5, OR TURNING ONTO TXWY K5 CAUSED THE GND CTLR'S STATEMENT. IF TURNING ON TXWY K5 WAS THE CAUSE, CONTRIBUTING FACTORS WOULD BE: MY FIRST TIME TO CDG; DIFFICULTY IN UNDERSTANDING COMS BECAUSE OF ACCENT; FATIGUE FROM ALL NIGHT OCEANIC XING. OUR AIRLINE HAS HAD NUMEROUS BULLETINS REGARDING EXITING THE RWY AFTER LNDG.

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.