An emb-145 first officer reported while flying the iah DRLLR4 arrival and after multiple runway chan...

Narrative:

While on the arrival (DRLLR4; we were assigned 26R; and then later assigned a vector for spacing; and then later assigned 26L; with different altitudes than published. Many of these changes were happening late on the arrival. I continued flying; while the captain programmed in the change and we re-briefed the changes. The changes resulted in a lack of turn anticipation from the FMS/autopilot turning the corner intersection (domno) to downwind. As we reached the intersection; I noticed the discrepancy; and immediately overrode the automation; and then placed the autopilot in heading mode to get back to the next course leg without delay and re-engaged navigation mode after a proper intercept had been established. The arrival was resumed without further issue; and there were no comments from ATC.had we not caught the error in time; it could have resulted in a significant overshoot of the turn which should have been started earlier. It is becoming common to have multiple changes in assignments of speed; altitude; crossing restrictions; and runways; often times this is late on the arrival when we are busy complying with the published restrictions. It appears that the FMS may have some shortcomings in handling these changes without introducing errors into the automation.I experienced a similar issue on a recent trip; but at the time thought it may have been a one-time fluke of the FMS; and we corrected in a similar manner. Since I have now seen this scenario twice; I realize it is a shortcoming of the FMS that must be corrected; double-checked and monitored; especially during turns of significance on an arrival. I have now submitted an as soon as possible for the previous occurrence as well. In the future; I specifically intend to watch my distance from the next fix; and if the turn has not begun prior to approximately 1.5 nm from the fix; I will be prepared to override the automation. I feel that the company may also need to address this issue with a software update on the FMS to better handle the frequent changes we encounter on the new arrivals.

Original NASA ASRS Text

Title: An EMB-145 First Officer reported while flying the IAH DRLLR4 Arrival and after multiple runway changes; the aircraft did not make the turn to final so the crew overrode it to prevent an overshoot. The error may be in the FMS design after multiple changes.

Narrative: While on the arrival (DRLLR4; we were assigned 26R; and then later assigned a vector for spacing; and then later assigned 26L; with different altitudes than published. Many of these changes were happening late on the arrival. I continued flying; while the Captain programmed in the change and we re-briefed the changes. The changes resulted in a lack of turn anticipation from the FMS/Autopilot turning the corner intersection (DOMNO) to downwind. As we reached the intersection; I noticed the discrepancy; and immediately overrode the automation; and then placed the autopilot in heading mode to get back to the next course leg without delay and re-engaged NAV mode after a proper intercept had been established. The arrival was resumed without further issue; and there were no comments from ATC.Had we not caught the error in time; it could have resulted in a significant overshoot of the turn which should have been started earlier. It is becoming common to have multiple changes in assignments of speed; altitude; crossing restrictions; and runways; often times this is late on the arrival when we are busy complying with the published restrictions. It appears that the FMS may have some shortcomings in handling these changes without introducing errors into the automation.I experienced a similar issue on a recent trip; but at the time thought it may have been a one-time fluke of the FMS; and we corrected in a similar manner. Since I have now seen this scenario twice; I realize it is a shortcoming of the FMS that must be corrected; double-checked and monitored; especially during turns of significance on an arrival. I have now submitted an ASAP for the previous occurrence as well. In the future; I specifically intend to watch my distance from the next fix; and if the turn has not begun prior to approximately 1.5 nm from the fix; I will be prepared to override the automation. I feel that the company may also need to address this issue with a software update on the FMS to better handle the frequent changes we encounter on the new arrivals.

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.

Attributes
ACN	1234666
Time
Date	201501
Local Time Of Day	0601-1200
Place
Locale Reference	I90.TRACON
State Reference	TX
Aircraft 1
Make Model Name	EMB ERJ 145 ER/LR
Operating Under FAR Part	Part 121
Flight Phase	Descent Initial Approach
Route In Use	STAR DRLLR4
Flight Plan	IFR
Component
Aircraft Component	Flight Environment Data
Person 1
Function	Pilot Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

An emb-145 first officer reported while flying the iah DRLLR4 arrival and after multiple runway changes; the aircraft did not make the turn to final so the crew overrode it to prevent an overshoot. The error may be in the FMS design after multiple changes.