Workload; Training / Qualification; Situational Awareness; Confusion; Human-Machine Interface
Aircraft Equipment Problem Less Severe; Deviation - Altitude Crossing Restriction Not Met; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Flight Crew Took Evasive Action; Flight Crew FLC Overrode Automation; Flight Crew Became Reoriented
Aircraft; Human Factors; Procedure
During our flight into IAH we were assigned the TEJAS3 RNAV arrival from the southwest beginning at the GMANN intersection. When this arrival is loaded from our database it only contains the vertical guidance as far as the TEJAS waypoint even though; according to the chart; there are crossing restrictions at GLAMM; BEEEP; and HOWLN. We assumed that these crossing restrictions would get loaded when we put in an assigned runway. We were cleared to descend via the arrival and put 6000 feet into the altitude alerter. The aircraft began a descent as usual. Shortly after that we were assigned Runway 27 for landing and I put that information in. I checked the points to make sure they were according to the chart; only this time I started from the runway point and worked in reverse back to the GLAMM intersection.  The points checked out ok so I assumed things were correct and returned to the radio page. What I failed to notice was that the FMS had loaded these points a SECOND time for some reason. It had us flying the original three points with no restrictions then had the points listed again; this time;  WITH the restrictions. The aircraft stopped it's descent at 13000 feet thinking it had plenty of time to get to 6000 from TEJAS since it had no other restrictions to follow. We noticed this pretty quick and started a manual decent but ended up crossing the point GLAMM about 1000 feet high.This apparent loading error also caused the guidance to revert to FPA (Flight Path Angle) mode upon reaching HOWLN and wanted to have the aircraft continue on the 058 heading. We caught this problem right away however and turned direct to SHIVV right away.Obviously I should have paid closer attention to the points and noticed that they were put in twice. I checked the NOTAMS twice ahead of time to see if this arrival had a default transition to fly like many at Houston and could not find one. I think this whole situation could have been avoided if the crossing restrictions at GLAMM; BEEP and HOWLN are loaded in regardless of which runway you are using; especially since the three points are the same for all three runways.I'm not sure why the FMS went into basic mode after HOWLN though; and I can only assume it was due to the points not being loaded correctly. I would very much like to know if this loading error was a database issue or if it might be something we did incorrectly; but I firmly believe we loaded everything as we have been taught. If this double loading of points does happen we should definitely make the crews aware before another problem can arise.
While flying the IAH TEJAS3 RNAV; an EMB-175 FMS inserted an arrival duplicate after GLAMM when the runway was assigned. The original points had altitude constraints but the duplicate did not so the aircraft crossed GLAMM high.