![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 1164386 |
| Time | |
| Date | 201404 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | DAL.Airport |
| State Reference | TX |
| Environment | |
| Flight Conditions | IMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Descent |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Pilot Not Flying Captain |
| Experience | Flight Crew Last 90 Days 322 |
| Person 2 | |
| Function | First Officer Pilot Flying |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
We planned an ILS-Y to [runway] 13R into dal. We were asked which runway we preferred and agreed to stick with our plan. Approaching fuz on the arrival; ATC then said cleared the ILS-Z to [runway] 13R; cross hurbs at/above 4;000 ft. First officer (pilot flying) was changing out his approach charts while I (pilot not flying) had the ILS page ready and then selected the ILS-Z 13R on the CDU. When first officer was ready; I asked if he was good with the selection; he said yes; and then I executed it. At that point we were in a turn to hurbs; and got a route discontinuity. As I wasn't positive we had passed fuz yet; I wasn't comfortable selecting hurbs to the top and executing. So we asked for a vector and received one pretty quick; but I'm sure we overturned the turn to hurbs because by the time we got the vector; we were in cws roll and not sure what heading to roll out on. I need to be 100% sure of the next go-to waypoint before executing a runway or approach change; so if this happens; we can correct immediately. It might also be helpful in dal if they publish the ATIS saying expect ILS-Z to 13R and ILS-Y to 13L; or whatever the case is; so we can program much further out. But I need to execute more accurately. Changed to ILS-Z to 13R during descent near fuz/got route discontinuity and asked for vector.
Original NASA ASRS Text
Title: An air carrier crew expected the ILS-Y 13R and programmed the FMS as such but after ATC assigned ILS-Z 13R over FUZ the FMS was reprogrammed and when EXECUTE was selected the FMS reinserted the entire arrival; the autopilot transitioned to CWS and the flight director command bars biased out of view. The aircraft turn about 50 degrees beyond a heading to HURBS from over FUZ.
Narrative: We planned an ILS-Y to [Runway] 13R into DAL. We were asked which runway we preferred and agreed to stick with our plan. Approaching FUZ on the arrival; ATC then said cleared the ILS-Z to [Runway] 13R; cross HURBS at/above 4;000 FT. First Officer (pilot flying) was changing out his approach charts while I (pilot not flying) had the ILS page ready and then selected the ILS-Z 13R on the CDU. When First Officer was ready; I asked if he was good with the selection; he said yes; and then I executed it. At that point we were in a turn to HURBS; and got a route discontinuity. As I wasn't positive we had passed FUZ yet; I wasn't comfortable selecting HURBS to the top and executing. So we asked for a vector and received one pretty quick; but I'm sure we overturned the turn to HURBS because by the time we got the vector; we were in CWS roll and not sure what heading to roll out on. I need to be 100% sure of the next go-to waypoint before executing a runway or approach change; so if this happens; we can correct immediately. It might also be helpful in DAL if they publish the ATIS saying expect ILS-Z to 13R and ILS-Y to 13L; or whatever the case is; so we can program much further out. But I need to execute more accurately. Changed to ILS-Z to 13R during descent near FUZ/got route discontinuity and asked for vector.
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.