37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 875010 |
Time | |
Date | 201002 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | LFPG.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A330 |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Incursion Taxiway |
Narrative:
After landing runway 27R and clearing 27L; we were instructed by ground control to taxi via D; MD3; a; taxi gate 16 to our parking gate. As I taxied east on D looking for MD3 I came upon a taxiway that looked like it should be MD3 (it took a 90 degree right turn southbound); however when I looked down that taxiway it was clearly marked as taxiway a. I proceeded ahead looking for MD3. Almost as soon as I continued past that intersection the ground controller told us that we had missed our turn and gave us an alternate taxi route which we used and taxied to our gate uneventfully. Upon reaching the gate I closely examined the airport charts and could clearly see that the charts and airport markings did not match. I called ground control and mentioned that fact to him and he just gave us a difficult to understand reply that basically dismissed my comment. Interestingly; another inbound flight; which had been assigned the same taxi route as us; heard my comments and piped in and agreed with me that the taxi charts and taxiway markings did not match with regard to MD3. Also; to the best of my recollection; there was not a sign in advance of the intersection in question that told what the upcoming intersecting taxiway was; nor was it painted on the pavement as they do in other instances. While some of lfpg's taxiways are clearly marked; there are instances such as the above; and others; which need to be addressed.
Original NASA ASRS Text
Title: An air carrier flight inbound to the gate at LFPG missed the turn from D to MD3; claimed to be due to the lack of an identifying sign.
Narrative: After landing runway 27R and clearing 27L; we were instructed by Ground Control to taxi via D; MD3; A; taxi gate 16 to our parking gate. As I taxied east on D looking for MD3 I came upon a taxiway that looked like it should be MD3 (it took a 90 degree right turn Southbound); however when I looked down that taxiway it was clearly marked as taxiway A. I proceeded ahead looking for MD3. Almost as soon as I continued past that intersection the Ground Controller told us that we had missed our turn and gave us an alternate taxi route which we used and taxied to our gate uneventfully. Upon reaching the gate I closely examined the airport charts and could clearly see that the charts and airport markings did not match. I called Ground Control and mentioned that fact to him and he just gave us a difficult to understand reply that basically dismissed my comment. Interestingly; another inbound flight; which had been assigned the same taxi route as us; heard my comments and piped in and agreed with me that the taxi charts and taxiway markings did not match with regard to MD3. Also; to the best of my recollection; there was not a sign in advance of the intersection in question that told what the upcoming intersecting taxiway was; nor was it painted on the pavement as they do in other instances. While some of LFPG's taxiways are clearly marked; there are instances such as the above; and others; which need to be addressed.
Data retrieved from NASA's ASRS site as of April 2012 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.