Date: 201210
Local time of day: 1201-1800
Location: ZAU.ARTCC, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger 300
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Climb
Airspace: Class A ZAU
ATC / advisory: Center ZAU
Aircraft component: AHRS/ND
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Human-Machine Interface; Situational Awareness; Troubleshooting
Second reporter function: Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Flight Crew Became Reoriented; Flight Crew Requested ATC Assistance / Clarification; Flight Crew Overcame Equipment Problem
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Upon climb out while receiving vectors from Chicago Center; I noticed that the heading displayed on my PFD differed from the pilot not flying's PFD by more than 90 degrees. I immediately disconnected the autopilot and turned off the windshield heat in order to return to our assigned heading using the wet compass. We then informed the Controller we were experiencing a navigational error and were instructed to turn north to a heading of 360. As this was occurring; a red HDG flag appeared on my primary flight display. Following this indication; the pilot not flying consulted the Emergency/Abnormal Checklist and determined we were experiencing a failure of the #1 AHRS. The pilot not flying continued to accomplish the checklist procedures while I hand flew the airplane. We asked for a final altitude of FL260 in order to remain clear of RVSM airspace. Upon completion of the checklist and the transfer of display indications from the #2 AHRS to my PFD normal operation resumed and we continued to our destination. We briefly discussed returning to our departure airport but decided that entering Chicago's congested airspace with our current mechanical failure was a less viable option than continuing to our destination which was forecast to remain CAVU. I cannot suggest a course of action to prevent recurrence of this event. However I do recommend that we spend more time in the simulator addressing display/navigational issues. The reversion panel of the CL300 can be confusing because it is rarely used. Additional familiarity during training could prove helpful.


Second narrative: The checklist identified the anomaly as the total loss of AHRS #1. We switched primary reference to AHRS #2; as well as Flight Director (FD) #2 and agreed to continue the flight. Autopilot function was restored with the selection of FD #2. I believe I could have expedited a solution to the problem; as pilot not flying; by going straight to the checklist after making sure the aircraft was under control. This would have saved a minute or two. Instead; I elected to try and diagnose the problem visually for too long. Once the checklist was consulted; we restored navigation performance to acceptable levels; albeit with degraded back up.


Synopsis: A CL-300 flight crew was confronted with a Number One AHRS failure shortly after takeoff. ATC provided an assist with track until the appropriate checklist restored on board guidance utilizing AHRS #2.