Narrative:

We were on a flight to iah. As we were getting close to iah; ATC changed our arrival. We were cleared direct tornn for the GUSHR3. Then right as we were coming up to tornn (5 to 8 miles away); we received a holding clearance. We were told to hold at tornn as published at FL280 and given a efc time. I then checked the chart and saw the hold at tornn had an outbound leg heading of 243 with 10 mile legs. After I set the hold on the FMS I thought the hold depiction looked off set so I asked the captain to take a look and we double checked that I had input the hold correctly. We had the right outbound leg as shown on the chart the turn in the right direction and the leg distance put in so we thought it was correct. I figured the angle looked wrong because we weren't coming in on the arrival. We had been given direct to tornn and therefore were coming at it from a different angle. By this point we were pretty much right over the fix as I activated the hold. The FMS took us on a teardrop entry into the hold. Shortly before we started our turn back inbound the controller asked us if we had started our turn back to tornn. We told him not yet and that we were about to. The controller then told us that we should have done a direct entry into the pattern. This made us question the hold again but thought it still looked right and the error had to do with executing the hold as we were passing over the top off the fix. I was also preoccupied with trying to figure out how long we could stay in the holding pattern and still have fuel to go to the alternate should it come to that. But something was still bothering us about the holding pattern. The captain wanted to ask the controller about it but the radio was very busy and it was hard to get back to him. Fortunately he called us back. Unfortunately; it was to tell us that we were holding west of tornn instead of north. He gave us a couple of vectors to straighten us out then we were cleared back onto the arrival. Before we changed; we heard another flight ask the controller if the outbound leg of the hold was suppose to be 243. He told them no; it is charted as 343. That's when we figured out the chart had a misprint on it. We were off by 100 degrees.the root cause of this event was a misprint on the arrival chart. The gushr 3 arrival actually has two holding patterns with incorrect outbound legs depicted. Also the hold was assigned very close to the fix leaving us little time to check it. With more time we may have noticed 243 leg didn't match up with the northern hold pattern depicted on the chart. Also not contacting the controller about our concerns sooner contributed to the event. I think the biggest thing to stop this from happening again would be to fix the chart. But also; we should have asked the controller for clarification sooner. It looked off to us but we couldn't see what was wrong with our bad information. We should have tried sooner to get the controller's attention.

Related reports:

Google
 

Original NASA ASRS Text

Title: CRJ900 flight crew is issue direct TORNN on the GUSHR3 arrival to IAH then issued a hold as published at TORNN. The pattern does not look correct; but is correctly entered. ATC agrees and issues vectors to reenter the holding pattern at TORNN. It is discovered that the charted out bound course of 243 degrees is off by 100 degrees at CHMPZ and TORNN. It should be 343 degrees.

Narrative: We were on a flight to IAH. As we were getting close to IAH; ATC changed our arrival. We were cleared direct TORNN for the GUSHR3. Then right as we were coming up to TORNN (5 to 8 miles away); we received a holding clearance. We were told to hold at TORNN as published at FL280 and given a EFC time. I then checked the chart and saw the hold at TORNN had an outbound leg heading of 243 with 10 mile legs. After I set the hold on the FMS I thought the hold depiction looked off set so I asked the captain to take a look and we double checked that I had input the hold correctly. We had the right outbound leg as shown on the chart the turn in the right direction and the leg distance put in so we thought it was correct. I figured the angle looked wrong because we weren't coming in on the arrival. We had been given direct to TORNN and therefore were coming at it from a different angle. By this point we were pretty much right over the fix as I activated the hold. The FMS took us on a teardrop entry into the hold. Shortly before we started our turn back inbound the controller asked us if we had started our turn back to TORNN. We told him not yet and that we were about to. The controller then told us that we should have done a direct entry into the pattern. This made us question the hold again but thought it still looked right and the error had to do with executing the hold as we were passing over the top off the fix. I was also preoccupied with trying to figure out how long we could stay in the holding pattern and still have fuel to go to the alternate should it come to that. But something was still bothering us about the holding pattern. The captain wanted to ask the controller about it but the radio was very busy and it was hard to get back to him. Fortunately he called us back. Unfortunately; it was to tell us that we were holding west of TORNN instead of north. He gave us a couple of vectors to straighten us out then we were cleared back onto the arrival. Before we changed; we heard another flight ask the controller if the outbound leg of the hold was suppose to be 243. He told them no; it is charted as 343. That's when we figured out the chart had a misprint on it. We were off by 100 degrees.The root cause of this event was a misprint on the arrival chart. The GUSHR 3 arrival actually has two holding patterns with incorrect outbound legs depicted. Also the hold was assigned very close to the fix leaving us little time to check it. With more time we may have noticed 243 leg didn't match up with the northern hold pattern depicted on the chart. Also not contacting the controller about our concerns sooner contributed to the event. I think the biggest thing to stop this from happening again would be to fix the chart. But also; we should have asked the controller for clarification sooner. It looked off to us but we couldn't see what was wrong with our bad information. We should have tried sooner to get the Controller's attention.

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.