Human-Machine Interface; Distraction; Situational Awareness; Troubleshooting
Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Aircraft Equipment Problem Dissipated; Flight Crew Rejected Takeoff; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Airport; Aircraft; Environment - Non Weather Related
Taking off we were subject to the same compass deviations as reported previously in a Company newsletter. The compass spun on the takeoff roll and as a result I had to do the math in my head to figure out what heading a 40 degrees to the right would be with our erroneous compass. As a result we missed the next turn by approximately .5 miles. ATC did not query us. Had this event happened in IMC and caused a distraction; so close to NYC; the outcome could have been very different. Do not use Runway 13 when deviations of the compass are noted; especially in IMC. I strongly urge that we look at this as a Company and its effects on the BE40.
The Reporter stated that a compass disagree alert occurred on the first LGA Runway 13 takeoff attempted. The crew acknowledged the Airport's Runway 13 compass alert sign and checked heading before takeoff. After beginning the takeoff roll; the compass fault alerted so they rejected the takeoff and reset the compasses. After the second takeoff; the heading was off 30 to 40 degrees so the crew flew the departure track; which they knew from experience; in VMC conditions. The Company's newsletter had been issued on days prior to this event and so they were well aware that the anomaly might occur. The Reporter stated that the crew would not have departed had IMC conditions existed.
A BE-400XP crew rejected a takeoff on LGA Runway 13 because of a compass anomaly but departed VMC on the second takeoff with a 30 - 40 degree compass error.