 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B757 captain reported he had failed to recognize a change in SOP requiring the landing runway to be selected prior to selection of an RNAV STAR and any associated enroute transition. Prior to becoming aware of the change he was experiencing difficulties programming stars that included 'transitions' from the end of the STAR's common portion to the waypoint from which vectors are to be provided for the associated IAP.
| Attributes | |
| ACN | 1124445 |
| Time | |
| Date | 201310 |
| Aircraft 1 | |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Parked |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
I have run into an issue on [some B757s] when inputting an RNAV STAR on the route page during FMC flight plan loading. If the flight manual FMC procedures are not followed exactly when loading the arrival you get something on the route page that looks like the arrival but is not; and it leaves out the end of the arrival. The RNAV arrivals that I've seen this happen on are the gibbz arrival into iad and stars into my domicile airport. I'm sure it is happening on others. The way most pilots load an arrival is: arrival; transition; and then runway; if you do that you get something like this: mgw approach transition gibbz. If you load: landing runway; arrival; transition you get this: mgw.GIBBZ2 mikej or mattc (depending on runway) which is correct. If you do it the former way the approach ends at gibbz which is wrong; the arrival makes a turn north or south depending on which runway you're landing on. I know I'm not the only one who has made this mistake as I have seen almost every first officer make the same error. I'm sure you are seeing reports with this issue. I'm bringing this up because I think we need to get something out to the pilots about this and how it can rather insidiously look like the FMC is programmed correctly when it is not.
Original NASA ASRS Text
Title: A B757 Captain reported he had failed to recognize a change in SOP requiring the landing runway to be selected prior to selection of an RNAV STAR and any associated enroute transition. Prior to becoming aware of the change he was experiencing difficulties programming STARs that included 'transitions' from the end of the STAR's common portion to the waypoint from which vectors are to be provided for the associated IAP.
Narrative: I have run into an issue on [some B757s] when inputting an RNAV STAR on the route page during FMC flight plan loading. If the Flight Manual FMC procedures are not followed exactly when loading the arrival you get something on the route page that looks like the arrival but is not; and it leaves out the end of the arrival. The RNAV arrivals that I've seen this happen on are the GIBBZ arrival into IAD and STARs into my domicile airport. I'm sure it is happening on others. The way most pilots load an arrival is: Arrival; Transition; and then runway; if you do that you get something like this: MGW Approach transition GIBBZ. If you load: Landing runway; Arrival; Transition you get this: MGW.GIBBZ2 MIKEJ or MATTC (depending on runway) which is correct. If you do it the former way the approach ends at GIBBZ which is wrong; the arrival makes a turn north or south depending on which runway you're landing on. I know I'm not the only one who has made this mistake as I have seen almost every First Officer make the same error. I'm sure you are seeing reports with this issue. I'm bringing this up because I think we need to get something out to the pilots about this and how it can rather insidiously look like the FMC is programmed correctly when it is not.
Data retrieved from NASA's ASRS site as of July 2013 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.