37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1220202 |
Time | |
Date | 201411 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | IAD.Airport |
State Reference | DC |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | STAR DOCCS.2 |
Flight Plan | IFR |
Person 1 | |
Function | Single Pilot Captain |
Qualification | Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 75 Flight Crew Total 8000 Flight Crew Type 800 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance |
Miss Distance | Horizontal 5 Vertical 1000 |
Narrative:
Flight was to iad. Original routing received from ATC was hvq.GIBBZ2. Approximately 100 NM west of hvq; ATC advised that they would need to change our arrival and issued a new clearance which placed us on the DOCCS2 arrival. Once we were established on the arrival (and now working with a different ATC facility) we were told to descend in accordance with the GIBBZ2. I advised that we were not on the GIBBZ2; we had be reassigned to the DOCCS2. Controller responded 'first I've heard of that; in that case proceed direct doccs; descend and maintain 9000 feet.' a few minutes later (and now with a different controller) we were approaching the gibbz intersection (yes; gibbz is an intersection on the doccs arrival); the DOCCS2 arrival procedure indicated that we should expect to cross gibbz at 6000 feet. As I had not yet received a clearance to that altitude I asked ATC 'confirm that you want us to descend on the arrival to cross gibbs at 6000 feet.' controller responded 'affirmative' and I programmed the FMS-VNAV to cross gibbz at 6000 feet. Approximately a minute later; the VNAV glide path had just centered and the aircraft was just pitching down to initiate the descent to 6000 feet (note that we were still west of gibbz at this point) when the controller came on frequency and told us to descend to 6000 feet. This was quickly followed by a 20 degree turn and a request to increase descent rate. Then I was asked if I had the other aircraft in sight (I did) and was told to maintain visual contact with him. Later the controller came on the frequency and asked why I had not descended in accordance with the gibbz arrival and I advised (again) that we were not on the gibbz; we had be reassigned to the doccs arrival. It was night and; although I had him in sight; I really don't have a good feel for how close we were to the other aircraft. My TCAS never alerted either in the TA or the RA mode. This event appears to be the result of a lack of communications between the different ATC facilities involved. Once a revised clearance has been issued a system should be in place which clearly shows all controllers involved what the clearance is for that aircraft. From my perspective; I'm happy to fly whatever arrival I'm assigned and accept revisions to the clearance as they become necessary; but once an arrival is changed everyone in the ATC system needs to have a clear understanding of what procedure has been assigned.
Original NASA ASRS Text
Title: Pilot reports of receiving an amended clearance and having difficulties with other ATC facilities reference the clearance.
Narrative: Flight was to IAD. Original routing received from ATC was HVQ.GIBBZ2. Approximately 100 NM West of HVQ; ATC advised that they would need to change our arrival and issued a new clearance which placed us on the DOCCS2 arrival. Once we were established on the arrival (and now working with a different ATC facility) we were told to descend in accordance with the GIBBZ2. I advised that we were not on the GIBBZ2; we had be reassigned to the DOCCS2. Controller responded 'First I've heard of that; in that case proceed direct DOCCS; descend and maintain 9000 feet.' A few minutes later (and now with a different controller) we were approaching the GIBBZ intersection (yes; GIBBZ is an intersection on the DOCCS arrival); the DOCCS2 arrival procedure indicated that we should expect to cross GIBBZ at 6000 feet. As I had not yet received a clearance to that altitude I asked ATC 'Confirm that you want us to descend on the arrival to cross GIBBS at 6000 feet.' Controller responded 'Affirmative' and I programmed the FMS-VNAV to cross GIBBZ at 6000 feet. Approximately a minute later; the VNAV glide path had just centered and the aircraft was just pitching down to initiate the descent to 6000 feet (note that we were still West of GIBBZ at this point) when the controller came on frequency and told us to descend to 6000 feet. This was quickly followed by a 20 degree turn and a request to increase descent rate. Then I was asked if I had the other aircraft in sight (I did) and was told to maintain visual contact with him. Later the controller came on the frequency and asked why I had not descended in accordance with the GIBBZ arrival and I advised (again) that we were not on the GIBBZ; we had be reassigned to the DOCCS arrival. It was night and; although I had him in sight; I really don't have a good feel for how close we were to the other aircraft. My TCAS never alerted either in the TA or the RA mode. This event appears to be the result of a lack of communications between the different ATC facilities involved. Once a revised clearance has been issued a system should be in place which clearly shows all controllers involved what the clearance is for that aircraft. From my perspective; I'm happy to fly whatever arrival I'm assigned and accept revisions to the clearance as they become necessary; but once an arrival is changed everyone in the ATC system needs to have a clear understanding of what procedure has been assigned.
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.