 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
B757 flight crew reports receiving a pre departure clearance from tpa for the BAYPO5 but does not note the transition. ATC questions the routing.
| Attributes | |
| ACN | 1111464 |
| Time | |
| Date | 201308 |
| Place | |
| Locale Reference | ZMA.ARTCC |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Aircraft 1 | |
| Make Model Name | B757 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Climb |
| Route In Use | STAR BAYPO5 |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | FMS/FMC |
| Person 1 | |
| Function | Captain Pilot Flying |
| Experience | Flight Crew Last 90 Days 100 Flight Crew Total 23000 Flight Crew Type 6000 |
| Person 2 | |
| Function | First Officer Pilot Not Flying |
| Experience | Flight Crew Last 90 Days 200 Flight Crew Total 11000 Flight Crew Type 6000 |
| Events | |
| Anomaly | Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
Flight plan was filed direct tay J75 cae J51 fak ... Our clearance said no revisions but gave us the BAYPO5 departure. When we put the BAYPO5 into the FMC and we had two transition choices; the amg transition or the dunkn transition. Since we were filed direct tay and tay was not a transition option; we put tay in after the baypo intersection to couple our route up and get rid of the route discontinuity. After takeoff and after going past baypo intersection; center asked if we were on an assigned heading. We said no we were on the BAYPO5 SID and now heading to tay. He said after baypo; we were supposed to be going to ecake wilon spring camjo carrd dunkn. We pulled up the SID again and verified that there was no tay transition. We looked at the clearance again and in the remarks section; it said the BAYPO5 departure and after that; it said the dunkn transition. We missed the dunkn part. The dunkn transition totally bypasses tay which is on our route and therefore this should have qualified for a reroute and yet our clearance said no revised segment. If you are not going to somewhere listed on your flight plan; it's a reroute plain and simple. In summary; we would have caught our mistake if it said revised segment. In the future; dispatch should be filing us to a SID transition if there is a remote chance that we could get a SID. Not to a VOR that is not connected to the SID.
Original NASA ASRS Text
Title: B757 flight crew reports receiving a PDC from TPA for the BAYPO5 but does not note the transition. ATC questions the routing.
Narrative: Flight plan was filed direct TAY J75 CAE J51 FAK ... Our clearance said no revisions but gave us the BAYPO5 departure. When we put the BAYPO5 into the FMC and we had two transition choices; the AMG transition or the DUNKN transition. Since we were filed direct TAY and TAY was not a transition option; we put TAY in after the BAYPO Intersection to couple our route up and get rid of the route discontinuity. After takeoff and after going past BAYPO Intersection; Center asked if we were on an assigned heading. We said no we were on the BAYPO5 SID and now heading to TAY. He said after BAYPO; we were supposed to be going to ECAKE WILON SPRING CAMJO CARRD DUNKN. We pulled up the SID again and verified that there was no TAY transition. We looked at the clearance again and in the remarks section; it said the BAYPO5 departure and after that; it said the DUNKN transition. We missed the DUNKN part. The DUNKN transition totally bypasses TAY which is on our route and therefore this should have qualified for a reroute and yet our clearance said no revised segment. If you are not going to somewhere listed on your flight plan; it's a reroute plain and simple. In summary; we would have caught our mistake if it said revised segment. In the future; dispatch should be filing us to a SID transition if there is a remote chance that we could get a SID. Not to a VOR that is not connected to the SID.
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.