37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1446165 |
Time | |
Date | 201705 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZLC.ARTCC |
State Reference | UT |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Other / Unknown Inflight Event / Encounter Other / Unknown |
Narrative:
Center changed our arrival procedure 4 times; 4 different procedures in approximately 4 minutes. Our clearance was to fly to a fix at a specified altitude and due to the confusing clearances that center was rattling off we missed the crossing restriction and had to be vectored in the descent. The problem was that the crossing restriction was for a clearance that changed. All of this happened because of GPS jamming going on in the area. I'm filling out this report so that you all know that it was extremely busy; ATC was making too many requests; one right after another; and all of this required continuous FMS changes; inputs; and confirmations. How could things have gone better; I'm not sure. We did the best we could but it became task saturated for them and us. They told us that it wasn't a problem; however; I'm still filling out this report to enlighten the team on how screwball things got with 4 different arrival changes in such a short period of time. I don't have any thoughts on how this could have been avoided.
Original NASA ASRS Text
Title: Corporate jet pilot reported receiving several revised clearances in a short amount of time from a very busy ZLC Center Controller due to GPS jamming occurring in the area.
Narrative: Center changed our arrival procedure 4 times; 4 different procedures in approximately 4 minutes. Our clearance was to fly to a fix at a specified altitude and due to the confusing clearances that Center was rattling off we missed the crossing restriction and had to be vectored in the descent. The problem was that the crossing restriction was for a clearance that changed. All of this happened because of GPS jamming going on in the area. I'm filling out this report so that you all know that it was EXTREMELY busy; ATC was making too many requests; one right after another; and all of this required continuous FMS changes; inputs; and confirmations. How could things have gone better; I'm not sure. We did the best we could but it became task saturated for them and us. They told us that it wasn't a problem; however; I'm still filling out this report to enlighten the team on how screwball things got with 4 different arrival changes in such a short period of time. I don't have any thoughts on how this could have been avoided.
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.