37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1713159 |
Time | |
Date | 201912 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 156 Flight Crew Total 659 Flight Crew Type 659 |
Events | |
Anomaly | ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Track / Heading All Types |
Narrative:
This was the last day of a four day trip. Preflight was going as planned until we were informed about a gdp for our destination. Our destination airport had to switch to runways that are rarely used and it was creating some issues. The captain and I took the extra time to discuss how this would affect our flight and kept a good line of communication with the dispatcher. One of the threats that we were trying to mitigate early was the filed STAR was not used for the runways in use at our destination. The captain and I located two stars that utilize the in use runway and planned on having our current STAR changed enroute.during the flight; I asked the dispatcher if she noticed any flights having their stars changed but she said that we were the first aircraft approaching our destination from the north. Shortly thereafter ATC changed our STAR and I attempted to load the new arrival into the box but was unable to since the computer did not associate the STAR with the assigned runway. After several failed attempts at programming the box; I requested ATC to assigned us a different STAR that was associated with the runway to mitigate the obvious threat at hand but they informed me that we would descend via the assigned STAR before receiving vectors for the assigned runway. While the captain and I discussed the situation along with how to mitigate the threat; we heard two other aircraft having the same issue and requesting different stars (one was definitely an airbus).I set up the box as best I could with the assigned STAR and asked for a heading to allow me time to enter the approach when switched to the final controller. At one point during the flight; I asked the dispatcher about the STAR issue in the hopes that he could talk to the ATC desk or other dispatchers to proactively help other flights. The dispatcher replied that there is not much they can do and we always have the ability to say 'unable'. The captain and I discussed what the dispatcher said and could not find a good reason to deny ATC's assignment. Safety of flight was never compromised and we were able to discuss every way to mitigate the threat we perceived. The only thing the captain and I want to know is how to get fif to accept a runway/STAR combination like this without having to manually insert each fix and altitude manually.
Original NASA ASRS Text
Title: First Officer reported difficulty with instructions from ATC for STAR changes on approach.
Narrative: This was the last day of a four day trip. Preflight was going as planned until we were informed about a GDP for our destination. Our Destination airport had to switch to runways that are rarely used and it was creating some issues. The Captain and I took the extra time to discuss how this would affect our flight and kept a good line of communication with the Dispatcher. One of the threats that we were trying to mitigate early was the filed STAR was not used for the runways in use at our Destination. The Captain and I located two STARS that utilize the in use runway and planned on having our current STAR changed enroute.During the flight; I asked the Dispatcher if she noticed any flights having their STARS changed but she said that we were the first aircraft approaching our destination from the north. Shortly thereafter ATC changed our STAR and I attempted to load the new arrival into the box but was unable to since the computer did not associate the STAR with the assigned runway. After several failed attempts at programming the box; I requested ATC to assigned us a different STAR that was associated with the runway to mitigate the obvious threat at hand but they informed me that we would descend via the assigned STAR before receiving vectors for the assigned runway. While the Captain and I discussed the situation along with how to mitigate the threat; we heard two other aircraft having the same issue and requesting different STARs (one was definitely an Airbus).I set up the box as best I could with the assigned STAR and asked for a heading to allow me time to enter the approach when switched to the final controller. At one point during the flight; I asked the dispatcher about the STAR issue in the hopes that he could talk to the ATC desk or other dispatchers to proactively help other flights. The Dispatcher replied that there is not much they can do and we always have the ability to say 'unable'. The Captain and I discussed what the dispatcher said and could not find a good reason to deny ATC's assignment. Safety of flight was never compromised and we were able to discuss every way to mitigate the threat we perceived. The only thing the Captain and I want to know is how to get FIF to accept a Runway/STAR combination like this without having to manually insert each fix and altitude manually.
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.