B737 flight crew experiences a track deviation on the FOOXX4 arrival to tpa; when a runway change is...

Attributes
ACN	1244845
Time
Date	201503
Local Time Of Day	0601-1200
Place
Locale Reference	TPA.TRACON
State Reference	FL
Environment
Flight Conditions	VMC
Aircraft 1
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	STAR FOOXX4 RNAV
Component
Aircraft Component	FMS/FMC
Person 1
Function	First Officer Pilot Flying
Experience	Flight Crew Last 90 Days 91.5 Flight Crew Type 538.35
Person 2
Function	Pilot Not Flying Captain
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

During descent along FOOXX4 RNAV arrival; we received hand off to tampa approach approaching waypoint dadpe and issued a change of runway from 01L to 01R. PF changed the FMS runway to 01R only (left the arrival the same; FOOXX4). Along with the new runway selection; the FMS added the same RNAV arrival which created an additional discontinuity in the FMS along the arrival. After passing dadpe; the FMS changed the ap to cws roll and allowed to aircraft to maintain current heading of 140-deg towards tpa. About 5-7 sec later; pm discovered the discrepancy while the PF was loading the new runway's landing performance in ACARS. Pm immediately turned heading to rejoin the course into the next waypoint of bayzz. During the turn; tampa approach asked if we were planning to continue the routing as depicted on the RNAV arrival. We replied yes and never heard anything else from tampa approach. We estimated to be off course approximately 2 nm east of dadpe and did not see any traffic conflict both visually or on TCAS. The flight landed on runway 01R uneventfully.

Original NASA ASRS Text

Title: B737 flight crew experiences a track deviation on the FOOXX4 arrival to TPA; when a runway change is entered in the FMC approaching DADPE. A route discontinuity appears and the aircraft does not make the turn to BAYZZ until manually selected by the crew.

Narrative: During descent along FOOXX4 RNAV arrival; we received hand off to Tampa Approach approaching waypoint DADPE and issued a change of runway from 01L to 01R. PF changed the FMS runway to 01R only (left the arrival the same; FOOXX4). Along with the new runway selection; the FMS added the same RNAV arrival which created an additional Discontinuity in the FMS along the arrival. After passing DADPE; the FMS changed the AP to CWS Roll and allowed to aircraft to maintain current heading of 140-deg towards TPA. About 5-7 sec later; PM discovered the discrepancy while the PF was loading the new runway's Landing Performance in ACARS. PM immediately turned heading to rejoin the course into the next waypoint of BAYZZ. During the turn; Tampa Approach asked if we were planning to continue the routing as depicted on the RNAV arrival. We replied yes and never heard anything else from Tampa Approach. We estimated to be off course approximately 2 nm East of DADPE and did not see any traffic conflict both visually or on TCAS. The flight landed on runway 01R uneventfully.

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.

B737 flight crew experiences a track deviation on the FOOXX4 arrival to tpa; when a runway change is entered in the FMC approaching dadpe. A route discontinuity appears and the aircraft does not make the turn to bayzz until manually selected by the crew.