37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1767499 |
Time | |
Date | 202010 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | LFPG.Airport |
State Reference | FO |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument |
Person 2 | |
Function | First Officer |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Ground Incursion Taxiway |
Narrative:
Initially planned 09R dep as per flight plan and current ATIS. Briefed RANUX4G dep. After obtaining clearance and new ATIS; departure runway was changed to 27L. Runway change procedures followed and new briefing for the RANUX4A from 27L briefed; FMS perf verified; data changed etc. While taxiing out we were told to contact ground at spot (removed). We did so and were given instructions to taxi; spot; Q RWY27L. A discussion ensued with all 3 pilots about whether or not this allowed us to choose our own route to 27L. During this time I slowed to a taxi speed of about 4-5 knots; barely rolling; to give everyone a chance to absorb the call and catch up. We decided to err on the side of clarity and asked if we could taxi spot; B; Q4; 27L. The answer back was no. What I heard was: taxi spot; BD8; D; Q; 27L. Ok; upscale the ipad and look for the route. Everyone else was doing the same. I was having a problem finding BD8; verbalized it and the rfo said I'll give you 'progressive'. We were still going less than 10 KTS when I made the turn to follow M in front of the fire station. Because of the lighting; signage; and the fact that I undershot the turn to stay on M; we rolled barely onto MD2. As soon as I realized my error; I stopped (cursed) and set the brake. I told the crew what happened and that we could not make the turn back to M and we would be unable to make a right turn onto any other taxiway to continue east bound. At that time; ground called and told us that it appeared we undershot our turn and were on MD2. We agreed and asked what she wanted us to do. We were given a standby. During that time we discussed the only way out was to continue on MD2; MD1D; BD6; B and get going the other way. Ground came back on and asked if we could do exactly that. We concurred and we were given that exact clearance plus from B; BD9; Q; Q4 to 27L. It is nitpicking but I don't believe QD1 was ever given between D and Q. In any event. We got turned around. Didn't turn in a prohibited direction; didn't drag a gear truck through the mud or non-stressed area; didn't have to get towed and didn't shut down any taxiways or inhibit any other aircraft from their taxi. We got everyone on the same page and taxied to the end and took off. Once in the air; we debriefed the event as a crew. The initial taxi instructions were vague. The subsequent taxi instructions became confusing. The first officer apparently didn't understand the taxi instruction; confusing BD8 for B; D8. I couldn't find BD8 on my chart while scaling up and sliding the chart around to understand the route. The rfo thought he had the route clarified only to lose the bubble at the end and was unable to communicate clearly what he was seeing. The signage in that area is abysmal. The lighting is glaring and the markings on the taxiways are not very clear/faint. And in our case; by the time we could verify our position; it was too late to fix it.with ongoing construction and changes at cdg; with being there previously and given taxi down B to QB7; Q4; 27L; etc. Even though we reviewed the taxi options and the standard taxi pages; we were given something unexpected and were unable to resolve what should have been a simple problem. I didn't realize how much of a problem it was until I undershot M on M2. I thought we had it resolved. I should have stopped; set the brake and sorted it out. Something that would also help would be to have ATC give instruction similar to ' taxi from spot M via north route 22; hold point XXX; RW27L'. We try to not set expectation bias by briefing taxi routes. When they are given piecemeal instead of as a package; it gets confusing sometimes. We were finally able to alleviate these issues in can with canned routes. Not finger pointing; just a suggestion. It was my fault.
Original NASA ASRS Text
Title: Flight Crew reported unclear taxi instructions which resulted in an incorrect turn on a taxiway at CDG; Charles De Gaulle Airport.
Narrative: Initially planned 09R Dep as per Flight Plan and current ATIS. Briefed RANUX4G Dep. After obtaining clearance and new ATIS; Departure Runway was changed to 27L. Runway change procedures followed and new briefing for the RANUX4A from 27L briefed; FMS perf verified; data changed etc. While taxiing out we were told to contact GND at spot (removed). We did so and were given instructions to taxi; Spot; Q RWY27L. A discussion ensued with all 3 pilots about whether or not this allowed us to choose our own route to 27L. During this time I slowed to a taxi speed of about 4-5 knots; barely rolling; to give everyone a chance to absorb the call and catch up. We decided to err on the side of clarity and asked if we could taxi Spot; B; Q4; 27L. The answer back was no. What I heard was: Taxi Spot; BD8; D; Q; 27L. Ok; upscale the iPad and look for the route. Everyone else was doing the same. I was having a problem finding BD8; verbalized it and the RFO said I'll give you 'progressive'. We were still going less than 10 KTS when I made the turn to follow M in front of the Fire Station. Because of the lighting; signage; and the fact that I undershot the turn to stay on M; we rolled barely onto MD2. As soon as I realized my error; I stopped (cursed) and set the brake. I told the crew what happened and that we could not make the turn back to M and we would be unable to make a right turn onto any other taxiway to continue east bound. At that time; Ground called and told us that it appeared we undershot our turn and were on MD2. We agreed and asked what she wanted us to do. We were given a standby. During that time we discussed the only way out was to continue on MD2; MD1D; BD6; B and get going the other way. Ground came back on and asked if we could do exactly that. We concurred and we were given that exact clearance plus from B; BD9; Q; Q4 to 27L. It is nitpicking but I don't believe QD1 was ever given between D and Q. In any event. We got turned around. Didn't turn in a prohibited direction; didn't drag a gear truck through the mud or non-stressed area; didn't have to get towed and didn't shut down any taxiways or inhibit any other aircraft from their taxi. We got everyone on the same page and taxied to the end and took off. Once in the air; we debriefed the event as a crew. The initial taxi instructions were vague. The subsequent taxi instructions became confusing. The FO apparently didn't understand the taxi instruction; confusing BD8 for B; D8. I couldn't find BD8 on my chart while scaling up and sliding the chart around to understand the route. The RFO thought he had the route clarified only to lose the bubble at the end and was unable to communicate clearly what he was seeing. The signage in that area is abysmal. The lighting is glaring and the markings on the taxiways are not very clear/faint. And in our case; by the time we could verify our position; it was too late to fix it.With ongoing construction and changes at CDG; with being there previously and given taxi down B to QB7; Q4; 27L; etc. Even though we reviewed the taxi options and the standard taxi pages; we were given something unexpected and were unable to resolve what should have been a simple problem. I didn't realize how much of a problem it was until I undershot M on M2. I thought we had it resolved. I should have stopped; set the brake and sorted it out. Something that would also help would be to have ATC give instruction similar to ' Taxi from spot M via North Route 22; hold point XXX; RW27L'. We try to not set expectation bias by briefing TAXI routes. When they are given piecemeal instead of as a package; it gets confusing sometimes. We were finally able to alleviate these issues in CAN with canned routes. Not finger pointing; just a suggestion. It was my fault.
Data retrieved from NASA's ASRS site 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.