 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
S46 controller switches a heavy jet to a different runway. The jet loses FMC data because of the switch and requests a vector to restart the approach.
| Attributes | |
| ACN | 1232740 |
| Time | |
| Date | 201501 |
| Local Time Of Day | 0001-0600 |
| Place | |
| Locale Reference | S46.TRACON |
| State Reference | WA |
| Aircraft 1 | |
| Make Model Name | Widebody Low Wing 4 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Route In Use | STAR MARNR4 |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 2 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Aircraft X was descending on the MARNR4 arrival. He was issued runway 16R. They usually plan runway 16L; which is what he programmed into his FMS when he began the MARNR4 arrival. (This arrival along with the hawkz has to have a runway loaded to fly it; this is part of the problem.) when I issued runway 16R; his FMS lost lateral and vertical guidance (which is unsafe but normal) and he said 'aircraft X request heading off the arrival due to runway change.' this has been a problem for months and must be fixed if we want to keep using these arrivals. Fortunately there was no traffic around but if these continue we won't always be so lucky.the facility tries to minimize these issues; due to the political pressure behind them. First they said that this issue is only with certain airlines. And we told them they were wrong. Now they say that these issues are an aircraft maker problem and only exist in specified different type aircraft; obviously they are wrong about that too. These issues occur with all types of aircraft on these arrivals. Controllers keep saving the day every time these aircraft lose lateral and vertical guidance on the arrivals. The issue needs to be fixed immediately.
Original NASA ASRS Text
Title: S46 Controller switches a heavy jet to a different runway. The jet loses FMC data because of the switch and requests a vector to restart the approach.
Narrative: Aircraft X was descending on the MARNR4 Arrival. He was issued Runway 16R. They usually plan Runway 16L; which is what he programmed into his FMS when he began the MARNR4 arrival. (This arrival along with the HAWKZ has to have a runway loaded to fly it; this is part of the problem.) When I issued Runway 16R; his FMS lost lateral and vertical guidance (which is unsafe but normal) and he said 'Aircraft X request heading off the arrival due to runway change.' This has been a problem for months and must be fixed if we want to keep using these arrivals. Fortunately there was no traffic around but if these continue we won't always be so lucky.The facility tries to minimize these issues; due to the political pressure behind them. First they said that this issue is only with certain airlines. And we told them they were wrong. Now they say that these issues are an aircraft maker problem and only exist in specified different type aircraft; obviously they are wrong about that too. These issues occur with all types of aircraft on these arrivals. Controllers keep saving the day every time these aircraft lose lateral and vertical guidance on the arrivals. The issue needs to be fixed immediately.
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.