37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 886022 |
Time | |
Date | 201004 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Component | |
Aircraft Component | FMS/FMC |
Person 1 | |
Function | First Officer Pilot Flying |
Experience | Flight Crew Last 90 Days 212 Flight Crew Type 4000 |
Person 2 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 192 Flight Crew Type 11000 |
Events | |
Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
The dispatch release indicated that the route filed was the preferred route. When I received the pre departure clearance; it also cleared us via the preferred route. The line above the cleared route that is used for changes was blank. The line below the cleared route stated the departure; in this case the tbrdg departure; to be flown. Since there were no changes to our route; I had assumed the tbrdg was included in the preferred route when I programmed it. It turned out the tbrdg was not part of the preferred route and was not entered by me. The tbrdg SID had to be entered separately. During the clearance brief; I briefed the pre departure clearance and matched the route on the pre departure clearance with the dispatch release. I included the altitude off the tbrdg and departure frequency. It was my leg to be flown so I also did the departure brief. The first point on the dispatch release matched the first point on the preferred route; ood. My error was that I didn't brief from the tbrdg SID. I have flown this exact route before many times; always on the phl 9 SID which is a heading then vector on course. The tbrdg was a different RNAV SID than I was used to. I could have caught my programming error had I briefed the RNAV SID properly. When we were cleared for takeoff; the controller cleared us to fly the SID. At 400 feet I asked for LNAV to be selected. The aircraft then proceeded to ood instead of the path of the SID. When the departure controller asked where we were going; I discovered my mistake. The pm told the controller we were going to ood and she said; 'okay company; proceed to ood.' luckily it was a slow part of the evening; and no one was around us so we didn't appear to cause a conflict. I believe the SID needs to be in the changes line above the cleared route to highlight to the programmer your preferred route now includes a SID. I need to be more careful programming and briefing.
Original NASA ASRS Text
Title: An air carrier flight crew failed to recognize their PDC clearance had added an RNAV SID to their cleared route out of PHL.
Narrative: The Dispatch Release indicated that the route filed was the preferred route. When I received the PDC; it also cleared us via the preferred route. The line above the cleared route that is used for changes was blank. The line below the cleared route stated the departure; in this case the TBRDG Departure; to be flown. Since there were no changes to our route; I had assumed the TBRDG was included in the preferred route when I programmed it. It turned out the TBRDG was not part of the preferred route and was not entered by me. The TBRDG SID had to be entered separately. During the clearance brief; I briefed the PDC and matched the route on the PDC with the Dispatch Release. I included the altitude off the TBRDG and departure frequency. It was my leg to be flown so I also did the departure brief. The first point on the Dispatch Release matched the first point on the preferred route; OOD. My error was that I didn't brief from the TBRDG SID. I have flown this exact route before many times; always on the PHL 9 SID which is a heading then vector on course. The TBRDG was a different RNAV SID than I was used to. I could have caught my programming error had I briefed the RNAV SID properly. When we were cleared for takeoff; the Controller cleared us to fly the SID. At 400 feet I asked for LNAV to be selected. The aircraft then proceeded to OOD instead of the path of the SID. When the Departure Controller asked where we were going; I discovered my mistake. The PM told the Controller we were going to OOD and she said; 'Okay Company; proceed to OOD.' Luckily it was a slow part of the evening; and no one was around us so we didn't appear to cause a conflict. I believe the SID needs to be in the changes line above the cleared route to highlight to the programmer your preferred route now includes a SID. I need to be more careful programming and briefing.
Data retrieved from NASA's ASRS site as of April 2012 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.