Narrative:

I was flying the plane on autopilot. ATC called to assign a hold north of iiu on the 360 radial; right hand turns; and 20 mile legs. I programmed the FMS with the details of the hold and asked the ca to verify. The ca verified the input and the autopilot took the plane to iiu; turned to the radial; proceeded outbound; and began a left-hand turn to make a parallel entry into the hold. The ca saw the plane turning left; thought it should turn right; and took the plane out of lateral navigation into heading mode and began a right hand turn. The first officer was confused on several levels -- there had been no transfer of controls; the turn made little sense; and I was unsure of how to both correct the ca and make an appropriate adjustment to the flight route. After a brief discussion; the ca radioed center and said 'the box' was having trouble and we were correcting. Center radioed back a very casual response as their workload was high and didn't appear too concerned with the particulars of our hold. After a while the ca leaned back in his seat and I assumed the controls (again without any transfer of controls). I don't think we ever ended up holding 'correctly' but after about one lap the plane was cleared to another fix and off we went. The crew members had a discussion/disagreement on the ground about what happened; what should have happened; and the basics of holding. I feel the problem originated with a complacent pilot who had forgotten basics of a maneuver he didn't perform often (and usually let automation take care of it). The ca's lack of CRM and rush to 'correct' the issue also played a role. Additionally; my hesitancy to disagree with the ca allowed the problem to continue. That being said; when the PIC rips the controls from the sic and the plane is not in any imminent danger; what's the 'proper' protocol for regaining control and fixing the problem? In short; there was probably a lateral deviation; maybe some flight on the unprotected side of a hold. No terrain or traffic problems were encountered.

Google
 

Original NASA ASRS Text

Title: EMB-145 First Officer reported the Captain failed to follow SOPs during a hold entry resulting in a track deviation.

Narrative: I was flying the plane on autopilot. ATC called to assign a hold North of IIU on the 360 radial; right hand turns; and 20 mile legs. I programmed the FMS with the details of the hold and asked the CA to verify. The CA verified the input and the autopilot took the plane to IIU; turned to the radial; proceeded outbound; and began a left-hand turn to make a parallel entry into the hold. The CA saw the plane turning left; thought it should turn right; and took the plane out of lateral navigation into heading mode and began a right hand turn. The FO was confused on several levels -- there had been no transfer of controls; the turn made little sense; and I was unsure of how to both correct the CA and make an appropriate adjustment to the flight route. After a brief discussion; the CA radioed center and said 'the box' was having trouble and we were correcting. Center radioed back a very casual response as their workload was high and didn't appear too concerned with the particulars of our hold. After a while the CA leaned back in his seat and I assumed the controls (again without any transfer of controls). I don't think we ever ended up holding 'correctly' but after about one lap the plane was cleared to another fix and off we went. The crew members had a discussion/disagreement on the ground about what happened; what should have happened; and the basics of holding. I feel the problem originated with a complacent pilot who had forgotten basics of a maneuver he didn't perform often (and usually let automation take care of it). The CA's lack of CRM and rush to 'correct' the issue also played a role. Additionally; my hesitancy to disagree with the CA allowed the problem to continue. That being said; when the PIC rips the controls from the SIC and the plane is not in any imminent danger; what's the 'proper' protocol for regaining control and fixing the problem? In short; there was probably a lateral deviation; maybe some flight on the unprotected side of a hold. No terrain or traffic problems were encountered.

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.